(SM) support tip: Best Practice by migration from one environment (physical/virtual) to another
In many cases it is neded to migrate or move the HP Service Manager installation from one physical or virtual environment to another (migrating from one data center to another i.e.) At this point a plan needs to be done of what steps will be performed and what needs to be taken in to consideration.
Basically it is recommendet from the development team to use the existing documentation for SM installation and reconfigure the SM to point at the right database.
That being said we would suggest a couple of important things that you can use as a guidance in such cases:
- Check if the SM is pointing at the right Database (open the configure.batch file in your SM Server installation directory and confirm if all fields are filled out correctly; test the connection to the DB as mentioned in the Installation notes that are part of the Release Notes)
- If a different IP address will be assigned to the HP Service Manager server after the migration you should contact the License Team so they can regenerate the SM licenses with the new IP address that will be used.
- If you have a change in the FQDN and / or IP address you should reconfigure all other modules that are present in your system (Web Tier, Service Request Catalog, Mobility etc.) to use the new FQDN and / or IP address values. For more detailed steps on how to change them you should take a look at the Installation notes for each and every module.
If you find that this or any post resolved your issue, please be sure
to mark it as an accepted solution.
Please also give kudo if you find it interesting 🙂
1. Any integration that physically points to the SM Servers will need to be modified to point to the new servers.
2. Any F5 or Hardware Loadbalancers being used in the environment will now need to point to the new servers.
3. If the new servers have different node names than the other environment, and SSL is being used in the environment, new certificates will mostly likely need to be generated.
4. If the new environment is a horizontally scaled environment, the servers will all need to be on the same subnet (same first three octets) due to Jgroups. I think HP is releasing a new version which supports TCP communication, and then this won;t be a requirement.