Most of us have various experiences deploying BMC Cloud Lifecycle Management 3001.
We follow the documentation but depending we don't know what sometime, we are facing some installation failure.
Here is what I managed to have my CLM deployment happening with success.
UNINSTALL EXISTING RSCD
If CLM servers have been provisioned with a RSCD agent, stop & uninstall it and delete the configuration files (exports, users.local & users).
PREVENT 4750 TCP PORT CONFLICT
- Comment ssad Linux services on tcp & udp in /etc/services on CLM IP and remote servers.
- If you are using Oracle, configure the TNSNAME.ORA on the remote servers where oracle client are installed. Test the connection with the databases using TNSPING and connect to the DB using SQLPLUS.
- Using CLM IP you will provide the DB connection information, but the Install Planner will ne configure you remote server, this need to be done previously the installation.
INSTALLATION STAGING DIRECTORY
- use the same path for the CLM install planner and the remote servers (/tmp - /tmp, /var/tmp - /var/tmp)
- The path should be executable on both sides
BMC BLADELOGIC SERVER AUTOMATION
- If you are integrating an existing BBSA infrastructure with CLM and if you are not at the correct build version (8.2.02 323), CLM will update Bladelogic integrated servers. If you do not want to have CLM managing the upgrade, be aware that you will have to perform the update prior to deploy the CLM components which have a dependency with BSA application server & console.
- Verify that your BBSA servers have the following settings
- AppServer DefaultRestVersion = 8.1.02.
- Appserver RestAssetAttributesUseInternalName = false
- AppServer enableWebServices = true
- Temporary give access * rw in exports configuration file and delete all entries in the users & users.local files
IF YOU RESTART A REMOTE SERVER
- Make sure the RSCD agent installed by CLM is up & running before launching a deployment on this target.