This section discusses the basic upgrade configuration of all Cloud Manager Orchestration components after each is upgraded. Component configuration is done either with a text-based configuration tool or with a GUI Wizard configuration tool.
The text-based configuration script detects which RPM patterns are installed, but the GUI Configuration Wizard requires that you specify the components to be configured, whether the patterns have been installed on the server or not.
Both the text-based tool and the GUI Wizard tool produce a configuration file (/etc/opt/novell/novell_zenworks_orch_install.conf).
The section includes the following information:
If you have only a keyboard to navigate through the pages of the GUI Configuration Wizard, use the Tab key to shift the focus to a control you want to use (for example, a Next button), then press the Spacebar to activate this control.
When you have finished answering the configuration questions in the wizard, the Cloud Manager Orchestration Configuration Summary page displays. Although this page of the wizard lets you navigate by using the Tab key and the Spacebar, you need to use the Ctrl+Tab combination to navigate past the summary list. Click Back if you accidentally enter the summary list, and re-enter the page to navigate to the control buttons.
By default, the Configure now check box on the page is selected. If you accept this default, the wizard starts the Orchestration Server and applies the configuration settings. If you deselect the check box, the wizard writes out the configuration file to /etc/opt/novell/novell_zenworks_orch_install.conf without starting the Orchestration Server or applying the configuration settings. For more information, see Using the GUI Configuration Wizard to Run a Delayed Configuration of the Orchestration Server.
Because so much of Cloud Manager’s operations depends on the Orchestration Server, we recommend that you configure it before you configure any other Orchestration component. Use either of the following methods to configure your upgraded Orchestration Server.
Ensure that you are ready with the information that you will be prompted for during the configuration procedure (GUI or text-based):
|
Server Upgrade Configuration Requirement |
Explanation and Action |
|---|---|
|
Configuration Selection |
This section discusses upgrade, so specify u (for upgrade) in the configuration script, or select the Upgrade check box in the wizard. |
|
Configuration Type |
Your answer here determines whether this configuration takes place on a standard installation or on a High Availability installation. This section discusses standard installation, so specify s (for standard) or press Enter to accept the default. For more information about High Availability configuration, see Section IV, Advanced Installation and Integration Topics. |
|
Administrator User |
IMPORTANT:Do not change the administrator name from the name you used in the original installation. |
|
Administrator Password |
Enter the password of the Cloud Manager Orchestration Server administrator you used in the previous installation (for Cloud Manager 2.4/Orchestration Server 3.4). IMPORTANT:Do not change the administrator password from the password you used in the original installation. |
|
Confirm Password / Retype Password |
Re-enter the administrator password. |
|
Automatic Agent Upgrade |
If there are existing Orchestration Agents configured to use this server, they will normally be placed on a pending upgrade list to be approved for automatic upgrade by the administrator. You can enable automatic upgrade of old agents to avoid this approval step if you enter yes or check the Automatic Agent Upgrade check box (wizard). If you choose to automatically upgrade the agents later, you can do so in the Orchestration Console. For more information, see |
|
Upgrade Auditing Database |
If you previously enabled auditing, you need to upgrade the database schema. If you use a PostgreSQL database, you can use the configuration utility to upgrade it. If you use a different RDBMS, you need configure it separately. If you select the Upgrade Audit Database check box (wizard), or if you enter yes for this prompt, you must specify
If you want to manually configure the database after upgrade, see Section 22.6, Configuring the Remote Audit Database after Orchestration Components Are Upgraded. |
|
Admin Info Port |
You need to verify the port you previously configured for access to the Administration Information page. Ensure that you specify the port used previously, not necessarily the default. |
|
Orchestration Agent Port |
You need to verify the port you previously configured for communication between the Orchestration Server and the Orchestration Agent. Ensure that you specify the port used previously, not necessarily the default. |
|
Path to License File |
As you upgrade, you need a license key (90-day evaluation license or a full license) to use this product. Depending on your arrangements with NetIQ, you either received a new key or you were given permission to reuse your old key. Specify the path to the network location of either your existing key or the new key that was issued to you. |
At the computer where you installed the upgraded Cloud Manager Orchestration Server pattern, run the Cloud Manager Orchestration configuration utility of your choice:
/opt/novell/zenworks/orch/bin/config
or
/opt/novell/zenworks/orch/bin/guiconfig
Follow the prompts to complete the configuration.
If you want to delay the upgrade of an Orchestration Server, you can capture the configuration parameters in the Cloud Manager Orchestration GUI Configuration Wizard and apply them at your discretion.
To run the delayed configuration:
Run the script for the Orchestrate Configuration Wizard as follows:
/opt/netiq/ncm/orch/bin/guiconfig
Configure the parameters of the server upgrade as described in Configuring the Upgraded Orchestration Server.
When you are ready to commit the configuration, deselect the Configure now check box so that the wizard can write the configuration file to /etc/opt/netiq/netiq_ncm_orch_install.conf without starting Orchestrate or applying the configuration settings.
NOTE:You can use this .conf file to start the Orchestrate Agent and apply the settings either manually or with an installation script. Use the following command to run the configuration:
/opt/netiq/ncm/orch/bin/config -rs
Click Next to display a message asking whether you want to overwrite the .conf response file.
To upgrade, you need to overwrite the existing file. When prompted, click Yes to overwrite the file and display the configuration page.
Click Next to begin the upgrade configuration for the Cloud Manager Orchestration Server 3.4 to the Orchestration Server 3.5.
The configuration does not require any input from you as you upgrade the Cloud Manager Monitoring Server.
At the computer where you installed the Cloud Manager Monitoring Server pattern, run the configuration utility of your choice:
/opt/novell/zenworks/orch/bin/config
or
/opt/novell/zenworks/orch/bin/guiconfig
Select the Monitoring Server as the component that you want to upgrade.
Follow the prompts to complete the configuration of the Monitoring Server.
The configuration does not require any input from you if you are upgrading Cloud Manager Orchestration Agent on the same machine where the Orchestration Server is installed.
At the computer where you installed the Cloud Manager Orchestration Agent pattern, run the configuration utility of your choice:
/opt/novell/zenworks/orch/bin/config
or
/opt/novell/zenworks/orch/bin/guiconfig
Select the Orchestration Agent as the component that you want to upgrade.
Follow the prompts to complete the configuration of the Orchestration Agent.