Moving CLM 5.x from iSeries to Windows Server and Migrating from DB2 to SQL Server
Hello,
One answer
In general see https://jazz.net/wiki/bin/view/Deployment/DeploymentMigratingAndEvolving
Comments
Thanks for the response.
https://jazz.net/wiki/bin/view/Deployment/DeploymentMigratingAndEvolving didn't work and gets me to a page "cannot find" error.
When we migrate CLM application from IBM i (Full WAS) to Windows 2012 server (Liberty Profile) I am listing things to do.
A) I am thinking a two step Migration. CLM 502 Platform Migration from IBM i to Windows. (Can I switch from full WAS in IBM i to Liberty Profile CLM 502)
B) Upgrade from 502 to 603 in the Windows Environment. (Final resting place for CLM 603 should be liberty profile instead of the Full WAS).
Steps I am thinking :
1) Install CLM 502 in Windows Servers & Reverse Proxy. Switch the DNS alias pointing to the new IHS Reverse Proxy Server machine.
Question: Can we use liberty Profile in 502 as eventually have to migrate from 502 to 603 after moving to Windows environment? or should I switch from Full WAS to Liberty profile during my migration from 502 to 603 all in Windows environment?
2) Copy the Teamserver.properties, *.rdf & log4j.properties, the indices directory and LDAP settings from IBM i to Windows 2012 servers for RM, CCM etc.
3) The existing databases on DB2 for i shouldn't need change to connect from Windows Environment (except the drivers that needs to be on the windows side)?
4) Start the application servers & run through setup.
Is this enough to make the platform migration be successful?
Final step is Upgrade from CLM 502 to CLM 603.
BTW, the backup procedures are almost very old. Is there a more updated version of Backup for CLM 502 & 603?
Backup: There is not, except additional nodes there are not a lot of changes I am aware of. I use the same strategies successful for years now. If you don't have a proven backup and restore strategy yet, I would suggest to hurry up and get one.