13 Post Installation Tasks

This chapter documents tasks that you may need to perform after the agent installation.

Reconnecting the Agent

There are two ways to reconfigure the Configuration Change Console Agent in order to disconnect it from one Configuration Change Console and re-connect it to another.

The first is to uninstall and re-install the agent using the new Configuration Change Console values. Consult the uninstallation and installation sections pertaining to your platform if you choose to perform a clean install.

The second method requires reconfiguration of the agent manually, which involves editing two configurations files under the agent installation directory structure. In order to make the change in this manner, follow the instructions in the following section.

Reconfiguring the Agent Manually

Follow these steps to reconfigure the agent manually.

Stop the agent on each device to be switched to the new Configuration Change Console Server. Use the Devices screen in the User Interface to STOP the agent or On the device where the agent is installed, STOP the agent in one of the following ways:
1. For Windows. Stop the service.
  
  One approach is to go to Control Panel --> Administrative Tools --> Computer Management --> Services and Applications --> Services. Double-click on the Oracle Configuration Change Console Agent service and click STOP.
2. For Unix. Run the following command where agent_install_dir is the directory of your agent installation:
  
  <agent_install_dir>/bin/arprobe stop
Change the configuration. Edit the following lines in the <agent_install_dir>/config/probe.properties file:
- java.naming.provider.url=t3s://server_address:port
  
  The variable inputs include the new Configuration Change Console server IP JMS port that was specified during installation.
- probe.device.id=<PROBE_ID>
  
  Clear the variable value so the new Configuration Change Console Server can reassign appropriately.
Change the baseline value (initiate baseline update). Edit the <agent_install_dir>/config/schedule.xml file and change the following variable value from false to true where agent_install_dir is the directory of your agent installation:

<Schedule doInitialBaseline="true">
Delete (or move to another location) the contents of <agent_install_dir>/log directory
Start the agent from the managed server.

Adding Additional Messaging Brokers in a Clustered Environment

If you have previously set up a clustered environment with some number of messaging brokers, you already configured your agents Messaging Broker URL to include the host and SSL port for each broker similar to the following:

t3s://host1:443,host2:443,host3:443…

If you want to add another broker to your cluster, you must first go to each agent and manually modify the {agent_intsall_dir}/config/probe.properties file to add the new broker to the field java.naming.provider.url before you actually add the new broker to the cluster.

If you add the new broker first, the agent will become aware of the new broker through the cluster, but will not have retrieved that broker's security certificate to be able to communicate with it. This will mean that the broker will not be able to take messages from any agents without being uninstalled and reinstalled again. The agent needs to know of the Messaging Broker server before the server is available.

Changing the Ports Of the Configuration Change Console Servers

Use the following sections to learn more about changing the ports of the configuration change console servers.

Reconfiguring the Server

The ports for the Configuration Change Console server were set at installation time. If you would like to change the ports after installation, you can edit the Oracle Weblogic config.xml file. This file is located on the Primary Server in the following location:

$USER_INSTALL_DIR$/bea/user_projects/domains/ConfigChangeConsole/config/config.xml

In this XML file, you will see server configuration for all servers. If this server belongs to a cluster, you will also see the server configuration for all other cluster members. The XML tag <listen-port> defines the port on which the server is listening to request. There are two for each server installation: one for non-ssl and one for SSL. The following is a sample fragment for a Primary Server installation:

<server>
        <name>PrimaryServer</name>
        <max-http-message-size>-1</max-http-message-size>
        <ssl>
                <enabled>true</enabled>
                <listen-port>443</listen-port>
                (…. Additional content removed …. )
        </ssl>
        <listen-port>80</listen-port>
        <listen-port-enabled>true</listen-port-enabled>
        (…. Additional content removed …. )
      
</server>

The port 443 in the example above is the SSL port that is used for HTTPS access to the web-based interface and also for cluster communication. The port 80 is the non-secure HTTP port.

On a non-clustered environment, you can simply save this config.xml file and restart the Primary Server for the change to take affect. You must also make sure your agents are reconfigured as explained below.

In a clustered environment, once you save the changes to config.xml, you must copy this config.xml file to the same directory path for all other members of your cluster. All config.xml files in all cluster members should be the same. Then you can restart each cluster server to see the changes take effect. You must also make sure your agents are reconfigured as explained below.

Reconfiguring the Agent Ports

When you change the port the servers are using, the agents may also have to be changed to point to the new ports.

For a non-clustered environment, changing the Primary Server's SSL/HTTPS port will require a change to be made on the agent.

For a clustered environment, only a change to the SSL/HTTPS port of a Messaging Broker server will require the change to be made on the agent.

To make the required change on the agents, edit the file {agent_install_dir}/config/probe.properties and find the entry java.naming.provider.url. For each host, ensure that the port matches the desired ports now configured on the servers.