Extension Workshop - Upgrade RTC V3.0.1 to V4.0
I have RTC 3.0.1, that needs to be moved up to V4.
When I set up 301, I used the workshop pdf, the tar files etc available at this link: https://jazz.net/library/article/634 Apparently the equivalents of the tar files are not published yet :(
I am wondering if it is better to uninstall and re-install the whole thing or maybe just do an upgrade by updating the SDKs. The former is probably more straightforward, even if it also consumes more time.
Has anyone done this before? Any tips, ideas, suggestions? Thanks for your time.
Accepted answer
Hi Anita,
the tar files are really only needed if you need to follow the workshop and work with the repository workspace.
If not, just go ahead and set it up fresh following Lab1 and using the 4.0 downloads.
You can try to import the 3.x tar files, I have not tested if that works. The other option would be to do a real upgrade to a 4.0 from the 3.0.1 server. I would suggest to use a new folder e.g. C:/RTC40Dev I do that and I have the dev environment for 3.x and 4.x on the same machine.
There is a new feature based launches jar up there, you can use. I downloaded it and it ended up having the extension .txt. I fixed that and it deployed well in the dropins folder. The launches that come with it are not necessary, you can use the ones that come with the workshop. Just import the project and replace the xml files.
There is an error showing with the launch for the JUnit to setup the DB. Ignore it. The missing bundle is not needed for the JUnit tests.
I am talking to our Web Dev team to get the update published this week, if at all possible.
the tar files are really only needed if you need to follow the workshop and work with the repository workspace.
If not, just go ahead and set it up fresh following Lab1 and using the 4.0 downloads.
You can try to import the 3.x tar files, I have not tested if that works. The other option would be to do a real upgrade to a 4.0 from the 3.0.1 server. I would suggest to use a new folder e.g. C:/RTC40Dev I do that and I have the dev environment for 3.x and 4.x on the same machine.
There is a new feature based launches jar up there, you can use. I downloaded it and it ended up having the extension .txt. I fixed that and it deployed well in the dropins folder. The launches that come with it are not necessary, you can use the ones that come with the workshop. Just import the project and replace the xml files.
There is an error showing with the launch for the JUnit to setup the DB. Ignore it. The missing bundle is not needed for the JUnit tests.
I am talking to our Web Dev team to get the update published this week, if at all possible.
2 other answers
Hi Anita,
I am working on getting the update published. My findings are at the end of the comments section of the article.
You could upgrade the existing database to 4.0 in a new deployed server. That would be the easiest way of doing it, until we can get the new version out. The upgrade would take less than an hour.
If you only want to set up a development environment, you can essentially follow the existing workshop and take my finding in the comments into consideration. Then you can import your existing extensions there.
I am working on getting the update published. My findings are at the end of the comments section of the article.
You could upgrade the existing database to 4.0 in a new deployed server. That would be the easiest way of doing it, until we can get the new version out. The upgrade would take less than an hour.
If you only want to set up a development environment, you can essentially follow the existing workshop and take my finding in the comments into consideration. Then you can import your existing extensions there.
Comments
