CDP worksheet for upgrades from 7.7.x, 7.8.x, and 7.9.00 with ASSO to 7.9.01 with RSSO
You can upgrade the configuration distribution peer (CDP) after you upgrade or install the repository. If you are using an external BMC Remedy Single Sign-On instance, it must already be installed.
You can upgrade the optional BMC Atrium Orchestrator Operator Control Panel (OCP), with the CDP. To upgrade the OCP with the CDP, use the Operator Control Panel worksheet for upgrades from 7.7.x, 7.8.x, and 7.9.00 with ASSO to 7.9.01 with RSSO worksheet with the CDP upgrade worksheet.
Note
If you are installing a non-English version of the Operator Control Panel, you must install it separately from the CDP. You must install the non-English OCP and CDP on separate Tomcat servers.
If you choose to modify any settings during the CDP upgrade, use this worksheet to record the new settings. The upgrade parameters in the table correspond to the parameters in the GUI upgrade panels and the options file.
Upgrade Feature Selection panel
Parameter | Default value and notes | Your value |
|---|---|---|
Configuration Distribution Peer | Configuration Distribution Peer |
|
Operator Control Panel | You can also select Operator Control Panel |
|
Root Directory Selection panel
Parameter | Default value and notes | Your value |
|---|---|---|
Destination Directory | Click Browse to navigate to the directory where the CDP is installed. |
|
Authentication panel
Parameter | Default value and notes | Your value |
|---|---|---|
Install Embedded Remedy SSO or Use External Remedy SSO | Select your authentication option and provide the required information to use it.
Remedy SSO Realm: Provide the name of the realm on the external Remedy SSO. |
Connection Details panel
Panel name and setting | Default value and notes | Your value |
|---|---|---|
Web Server Host Name | Fully qualified domain name of the host where the CDP is installed. | |
| Repository HA Address | Provide the repository IP address and port for communication with the enterprise service bus. Use the following format: <IPaddress>:<port> On a machine that has multiple network interface cards (NICs) this must be the IP address that allows access from the CDP and/or the HA-CDP. The default port is the repository web port plus 10. For example, if the repository port is 28080, the Repository HA address is 28090. Notes
| |
| CDP HA Address | Provide the CDP IP address and port for communication with the enterprise service bus. Use the following format: <IPaddress>:<port> On a machine that has multiple network interface cards (NICs) this must be an IP address that allows access from the repository and/or the HA-CDP. The default port is the CDP web port plus 10. For example, if the CDP port is 38080, the CDP HA address is 38090. Notes
|
CDP Server Auto Start panel
Parameter | Default value and notes | Your value |
|---|---|---|
Do you want to start the server after the installation | Yes |
|
Installation Choices Summary panel
Parameter | Default value and notes | Your value |
|---|---|---|
Copy Text to Clipboard | Before you install/upgrade the CDP successfully, you can copy the peer connection details to a clipboard for further use. |
|
Comments
"You must choose the same authentication service option (embedded or external) that you chose when upgrading the repository.".This statement is very misleading. I've selected option of embedded rsso during the upgrade of REPO and again "embedded" during upgrade of the CDP and in result I have to Remedy SSOs. One in the AO_HOME/REPO and one in AO_HOME/CDP directories. I suppose, the right option is to select external RSSO during the CDP upgrade and provide a URL to the RSSO installed with REPO.
SIde note, I tried to chose external RSSO for the second installation and tried various URL syntaxes but each gave me an errors: Invalid connection, invalid realm, invalid user etc.
It would be helpful if the documentation contained example.
Regards,
Ariel
Regarding the following: "I tried to chose external RSSO for the second installation and tried various URL syntaxes but each gave me an errors: Invalid connection, invalid realm, invalid user etc."
Can you provide more details?
I have checked with members of the QA team to verify that if you choose the embedded RSSO option, you will have two embedded RSSO instances: one on the repository and one on the CDP. This is an acceptable configuration. It is also acceptable to install an embedded RSSO on the repo and then choose external RSSO during the CDP install and point to the RSSO on the repo.
I have updated the wiki pages to reflect that information. Thank you for bringing it to our attention.
Installer throws errors if External Remedy SSO option is selected:
What is the realm information provided? Can you attach exception in the file BAO_install_log.txt?
Please send me a direct email (ranga_samudrala@bmc.com) and we can get on a call to discuss this.
Log in or register to comment.