FULL upgrade for 3.0.1.x demo environment to 4.0.x production question
2 answers
I don't think there's a precise order you need to take here, but I think I would do what you described. Upgrade to 4.0 first, verify the data there on Derby. Then get the WAS install up and running, you can use the new WAS scripts in 4.0 to help. Do the export/import to DB2 after WAS is happy. And finally add RRDI to the mix.
Change one thing at a time and don't move on until you can test and verify that step is good.
Scott
Hello Sterling
v4.0 only supports 64-bit OSes. So, you would need to plan for that as the location where v4.0 code should be installed.
The easiest setup is if you can mount drives between the v3.01 system and the v4.0 system.
Next, regarding your question for RRDI. For evaluation and trial deployments, a single server topology is OK. However, for production environments, a two server topology is preferable.
See this topic:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/topic/com.ibm.rational.rrdi.admin.doc/topics/c_install_topology_overview.html
v4.0 only supports 64-bit OSes. So, you would need to plan for that as the location where v4.0 code should be installed.
The easiest setup is if you can mount drives between the v3.01 system and the v4.0 system.
Next, regarding your question for RRDI. For evaluation and trial deployments, a single server topology is OK. However, for production environments, a two server topology is preferable.
See this topic:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/topic/com.ibm.rational.rrdi.admin.doc/topics/c_install_topology_overview.html