5 Installing and Uninstalling the Configuration Change Console Server

This chapter describes the process for installing the Configuration Change Console Server.

Installing a Non-Clustered Configuration Change Console Server

Follow these steps to install the Configuration Change Console Server without clustering. This environment is suitable for very small deployments with a few agents and a low change rate.

Double-click on the server.exe file from the Configuration Change Console media. The Installer will take a few moments to initialize.
Click Next when the Introduction screen appears
Specify the installation directory or choose the default. Click Next.
Choose server type as Primary (without cluster support). Click Next.
Note that the Oracle database must be installed and running on this machine before the Configuration Change Console can be installed.

Click Next if you have Oracle installed or Cancel if you still must install Oracle. If you click Cancel, you must reinstall the Configuration Change Console at a later time.
The Oracle database instance that is dedicated for Configuration Change Console must already be set up and running. The next screen configures the Configuration Change Console Server to access Oracle.

Enter the following information:
- Database IP. Enter the IP address of the server where the database was installed.
- Database Port. The default value is 1521.
- Database SID. The SID of the database as configured during the database installation. Set this value during database installation. The default and recommended SID is gateway.
- Username. The Oracle database user. Set this value during database installation. The default and recommended username is gateway.
- Password. Enter the user password. The password will be stored in an encrypted form during installation so that it cannot be read by anyone attempting to access the database directly.
Click Next.
Enter the following information:

Note:
If invalid data is entered, an error message will appear. The last statement on the error message indicates the reason for failure. If you receive any errors, review the error messages for details.
Enter your organization name and click Next.
Enter the password for the weblogic console administrator account. The user name for this account is weblogic. This is the account that you can use to log into the Weblogic Administration Console to manage your Weblogic deployment on which Configuration Change Console runs.
Enter the password for the built-in administrator account. This is the account you use to log into the Configuration Change Console user interface initially. You can change the password at a later time through the Administration features of the interface.
Enter the ports to use for the server. There are two ports configured here; HTTP is used for access to the web-based console, and HTTPS is used for secure access to the web-based console and also for agents to communicate with the server. Whatever port you use for HTTPS, you will need to know when you install the agents.
Click Next.
Specify whether you would like the server to start up automatically after it has finished installing. The installation will create a new Windows service called Oracle Configuration Change Console Server. If you do not start this service at install time, you can go to the Services Control Panel at any time to start it.
Specify the minimum and maximum amount of memory allocated to the Configuration Change Console server keeping the recommendations below in mind. Click Next.

Note:
If invalid data is entered, an error message will appear. The last statement on the error message indicates the reason for failure. If you receive any errors, review the error messages for details.

If the Configuration Change Console is the only major application running on your system, you can allocate up to 80% of all system memory to the Configuration Change Console. Remember that you must leave at least 128 MB for the Operating System to operate. If your memory allocation exceeds 1400 MB, be sure to configure your server to support more than 1 GB of memory for any process such as using the Windows 3G/4G tuning capabilities.
Review the Pre-installation Summary screen and click Install. If you would like to make changes to your configuration, click Previous to return to previously viewed screens.
The installation will take a few minutes to complete. A screen will indicate the installation progress. Click Done when the Install Complete screen appears.

Logging Into the Configuration Change Console Server

Once installation of the server has finished at the Oracle Configuration Change Console Server service has been started, you can log into the web-based user interface using a web browser. The URL can be one of the following:

http://hostname:port (where port is the HTTP port configured at installation)

https://hostname:port (where port is the HTTPS port configured at installation)

If you installed using the default HTTP port of 80 and default HTTPS port of 443, you do not need to use the port number in the URL.

The only username that exists out of the box is administrator, all lower case. The password will be the password you set for the administrator account when going through the server installer.

If you connect via HTTPS, you will get an alert about the certificate not being from a trusted certificate authority. The installation will install a certificate that has been created at installation time. This certificate is a self-signed certificate by the server. If you want to continue to use this self-signed certificate, then users will need to accept this certificate in their browser.

If you would like to load your own certificate for HTTPS communication, you can refer to the documentation for Oracle Weblogic Server 10.3 for instructions on how to set your own certificate from a trusted certificate authority (CA).

In a clustered environment, only the primary server provides access to the full web-based interface to use the product.

Logging Into the Oracle Weblogic Console

When you installed the Configuration Change Console Server, the Weblogic console was also configured. You can log into the web-based console interface using a web browser. The URL can be one of the following:

http://hostname:port/console (where port is the HTTP port configured at installation)

https://hostname:port/console (where port is the HTTPS port configured at installation)

Note:

Please consult your system or network administrator to determine which port should be used in your environment. The chosen port number must be used throughout the install process and must be matched when installing the agents. If you alter this value, please alter all entries in this install that reference the default ports (80 for HTTP and 443 for HTTPS.

If you installed using the default HTTP port of 80 and default HTTPS port of 443, you do not need to use the port number in the URL.

The user name will be weblogic and the password will be the one you set during installation for the Weblogic administration account.

If you have installed a clustered Configuration Change Console deployment, the default HTTP port for the admin server will be 8080 and 8090 for HTTP access.

Installing a Clustered Configuration Change Console Environment

This section outlines the steps required to install and configure the Configuration Change Console environment for clustering. In a clustered environment, there will be one primary server and any number of secondary servers. All of these servers will belong to the same domain, ConfigChangeConsole in Oracle Weblogic server.

If you install an environment as clustered, you must have a primary server and at least one secondary. If you do not have at least one secondary, events will not be captured from agents.

All the servers in the cluster (Primary server and Secondaries) should be in the same network segment or else the network connection of all servers in the cluster will be very slow.

All the hosts in the cluster must be able to parse the Fully Qualfied domain name of each other. You can test by pinging the fully qualified name of each server from the primary server and vice-versa.

All servers in the cluster should have the same install path for best performance. For example, the default is C:\oracle\ConfigurationChangeConsoleServer. Throughout this section, $USER_INSTALL_DIR$ refers to the server installation directory.

Installing the Primary Server

Follow these steps to install the primary server for a clustered Configuration Change Console environment:

Double-click on the server.exe file from the Configuration Change Console media. The Installer will take a few moments to initialize.
Click Next when the Introduction screen appears
Specify the installation directory or choose the default. Click Next.
Choose server type as Primary (with clustering support), then click Next.
Note that the Oracle database must be installed and running on this machine before the Configuration Change Console can be installed. Click Next if you have Oracle installed or Cancel if you still must install Oracle. If you click Cancel, you must reinstall the Configuration Change Console at a later time.
The Oracle database instance that is dedicated for Configuration Change Console must already be set up and running. The next screen configures the Configuration Change Console Server to access Oracle.

Enter the following information:
- Database IP. Enter the IP address of the server where the database was installed
- Database Port. The default value is 1521.
- Database SID. The SID of the database as configured during the database installation. Set this value during database installation. The default and recommended SID is gateway.
- Username. The Oracle database user. Set this value during database installation. The default and recommended username is gateway.
- Password. Enter the user password. The password will be stored in an encrypted form during installation so that it cannot be read by anyone attempting to access the database directly. Click Next.
Enter your organization name. Click Next.
Enter a key phrase for the two certificate keystores that the server uses to store SSL certificates. You may need these pass phrases at a later time to import new certificates. Click Next.
Enter the Password for the weblogic console administrator account. The Username for this account is weblogic. This is the account that you can use to log into the Weblogic Administration Console to manage your Weblogic deployment on which Configuration Change Console runs.
Enter the Password for the built-in administrator account. This is the account you use to log into the Configuration Change Console user interface initially. You can change the password at a later time through the Administration features of the interface.
Enter the ports to use for the primary server. There are two ports configured here; HTTP and HTTPS. HTTP is used for access to the web-based console, and HTTPS is used for secure access to the web-based console and also for agents to communicate with the server. Whatever port you use for HTTPS, you will need to know when you install the agents. Click Next.
Enter the ports to use for the cluster admin server. There are two ports configured here; HTTP is used for access to the web-based console. You will need to provide the admin server IP and HTTPS port when you install any secondary servers in your cluster.
Specify whether you would like the server to start up automatically after it has finished installing. The installation will create a new Windows service called Oracle Configuration Change Console Server. If you do not start this service at install time, you can go to the Services Control Panel at any time to start it.
Specify the minimum and maximum amount of memory allocated to the Configuration Change Console server keeping the recommendations below in mind. Click Next.

Note:
If invalid data is entered, an error message will appear. The last statement on the error message indicates the reason for failure. If you receive any errors, review the error messages for details.

If the Configuration Change Console is the only major application running on your system, you can allocate up to 80% of all system memory to the Configuration Change Console. Remember that you must leave at least 128 MB for the Operating System to operate. If your memory allocation exceeds 1400 MB, be sure to configure your server to support more than 1 GB of memory for any process such as using the Windows 3G/4G tuning capabilities.
Review the Pre-installation Summary screen and click Install. If you would like to make changes to your configuration, click Previous to return to previously viewed screens.
The installation will take a few minutes to complete. A screen will indicate the installation progress. Click Done when the Install Complete screen appears.

Installing the Secondary Server

Follow these steps to install a secondary server for a clustered Configuration Change Console environment. You may install one or many secondaries in the cluster to support size of deployment.

Double-click on the server.exe file from the Configuration Change Console media. The Installer will take a few moments to initialize.
Click Next when the Introduction screen appears.
Specify the installation directory or choose the default. Click Next.
Choose server type as Secondary Server, then click Next.
Specify the name of the secondary server. The name should be of the format SecondaryServerX where you replace X with the secondary number starting from 1. For instance, the first secondary server would be called SecondaryServer1.
Enter a key phrase for the two certificate keystores that the server uses to store SSL certificates. You may need these pass phrases at a later time to import new certificates. Click Next.
Enter the hostname and port for the admin server which was installed with the Primary server. The HTTPS port was set when installing the primary server. The default port value was 8090.
Enter the ports to use for the primary server. There are two ports configured here; HTTP and HTTPS. HTTP is used for access to the web-based console, and HTTPS is used for secure access to the web-based console and also for agents to communicate with the server. Whatever port you use for HTTPS, you will need to know when you install the agents. Click Next.
Specify the minimum and maximum amount of memory allocated to the Configuration Change Console server keeping the recommendations below in mind. Click Next.

Note:
If invalid data is entered, an error message will appear. The last statement on the error message indicates the reason for failure. If you receive any errors, review the error messages for details.

If the Configuration Change Console is the only major application running on your system, you can allocate up to 80% of all system memory to the Configuration Change Console. Remember that you must leave at least 128 MB for the operating system to operate. If your memory allocation exceeds 1400 MB, be sure to configure your server to support more than 1 GB of memory for any process such as using the Windows 3G/4G tuning capabilities.
Review the Pre-installation Summary screen and click Install. If you would like to make changes to your configuration, click Previous to return to previously viewed screens.
The installation will take a few minutes to complete. A screen will indicate the installation progress. Click Done when the Install Complete screen appears.

Post Installation Steps for Cluster

After the installation of a secondary is finished, you need to perform the following steps manually in your cluster:

Login to the host which is hosting the Admin server and Primary Server.
Open the following file using notepad or any text editor:

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

Look for the following commented xml segment which defines an example SecondaryServer.

<!--server>
    <name>SecondaryServer1</name>
    <ssl>
      <enabled>true</enabled>
      <listen-port>7002</listen-port>
    </ssl>
    <machine xsi:nil="true"></machine>
    <listen-port>7001</listen-port>
    <listen-port-enabled>true</listen-port-enabled>
    <cluster>CCCC</cluster>
    <listen-address>your host address</listen-address>
    <java-compiler>javac</java-compiler>
    <jta-migratable-target>
      <user-preferred-server>SecondaryServer1</user-preferred-server>
      <cluster>CCCC</cluster>
    </jta-migratable-target>
    <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
  </server-->

In the above block, replace the value in <listen-address>your host address</listen-address> with the Fully Qualified Domain Name of the secondary server.
Replace <listen-port>7001</listen-port> and <listen-port>7002</listen-port> with this secondary server's port and ssl-port respectively that you configured during the secondary server install.
In the block <name>SecondaryServer1</name> and <user-preferred-server>SecondaryServer1</user-preferred-server> replace it with the the name of the Secondary Server that you just installed. You specified the name during installation. For the first secondary server, you should use SecondaryServer1, then next would be SecondaryServer2 and so on.
Uncomment this entire xml block to have the new secondary server defined. You can do this by either:
- Changing the begin tag from  to </server>
You can copy this block for any addtional secondary servers you may want to add, and modify the entries to reflect the settings of the new secondary server.

Look for the following block and uncomment it. Replace SecondaryServer1 with the name of the secondary server you chose.

<!--migratable-target>
    <name>SecondaryServer1 (migratable)</name>
    <notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
    <user-preferred-server>SecondaryServer1</user-preferred-server>
    <cluster>CCCC</cluster>
  </migratable-target-->

To uncomment, change  to </migratable-target>. You need to add this block for any additional secondary servers you add.

Adding An Extra JMS Server For Your Cluster

If you want to add an extra jms server, please find the following two blocks in config.xml and uncomment them. Again replace the name under target which is SecondaryServer1 to reflect the name of your secondary server.

<!--jms-server>
    <name>SlaveJMSServer</name>
    <target>SecondaryServer1</target>
    <persistent-store>SlaveFS</persistent-store>
  </jms-server-->
 
  <!--file-store>
    <name>SlaveFS</name>    <directory>C:\oracle\ConfigurationChangeConsoleServer\domains\ConfigChangeConsole\masterJmsFileStore</directory>
    <target>SecondaryServer1</target>
  </file-store-->

To uncomment, make the following changes:

<!-- jms-server> to <jms-server>
     </jms-server--> to </jms-server>
     <!--file-store> to <file-store> 
    </file-store--> to </file-store>

You will then have an extra jms server.

Configuring SSL

Because all Configuration Change Console Servers communicate over an SSL channel, SSL needs to be configured before starting the secondary server. This can be done through the Admin Server Console by accessing the following URL:

https://IP:PORT/console

The IP is the network IP or host name of the server on which you installed the primary and admin server. The port is the admin server HTTPS port. The default ssl admin server port is 8090, but may have been changed during installation of the primary server.

You need to provide the admin server username(weblogic) and password you set at install time to log in to this console.

In the Change Center of the Administration Console, click Lock & Edit
In the left pane of the Console, expand Environment and select Servers.
Click the name of the server for which you want to configure the identity and trust keystores. This is already configured for the primary server during install.
Select a secodary sever you wish to confgure.
Select Configuration --> Keystores.
In the Keystores field, select the option Custom Identity and Custom Trust. This will be the method for storing and managing private keys/digital certificate pairs and trusted CA certificates.
In the Identity section, define attributes of the identity keystore.

Custom Identity Keystore:

Provide the absolute path of the identity keystore.

Specify the following value where $USER_INSTALL_DIR is the root path that you used for your secondary server installation:

$USER_INSTALL_DIR$\bea\wls\server\lib\weblogicOCC.jks
Custom Identity Keystore Type: The type of the keystore. Specify JKS as the value. JKS stands for Java Key Store. If left blank, it defaults to JKS.
Custom Identity Keystore Passphrase: The password you will enter when reading or writing to the keystore. Input the password that you used when configuring the secondary server's weblogicOCC.jks file.
In the Trust section, define properties for the trust keystore.

Custom Trust Keystore: Provide the absolute path of the trust keystore where $USER_INSTALL_DIR$ is the path where you installed your secondary server.

Enter $USER_INSTALL_DIR$\bea\wls\server\lib\weblogicOCCTrust.jks
Custom Trust Keystore Type: The type of the keystore. Specify JKS as the value.
Custom Trust Keystore Passphrase: The password used for reading or writing to the keystore. Input password that you used for secondary server's weblogicOCCTrust.jks file when installing the secondary server.
Click Save.
Select Configuration --> SSL page.
In the Identity and Trust locations section, choose the Keystores option.
In the Private Key Alias section, input weblogic as alias.
Input the password that you used for secondary server's weblogicOCC.jks file.
Click Save.
In the Change Center of the Administration Console, click Activate Changes.
After all of the above steps are performed using the admin server console, you should import this secondary's certificates into all other server's trust keystore files.
The certs of all other servers must be imported into the secondary's trust keystore file. This can be accomplished using the steps described in the next section.

Exporting And Importing the Certificates Into Servers

Follow these steps to export or import the certificates into servers:

Navigate to the $USER_INSTALL_DIR$\bea\wls\server\lib directory of each server.
Execute the following command:

keytool -export -file primary.test.com.cer -alias weblogic -keystore weblogicOCC.jks

primary.test.com.cer is the file name of cert on primary host

primary.test.com is the domain name of current host.(primary)
In this current scenario, you would execute the above command on the primary server host. primary.test.com is the fully qualified domain name of the primary host.
When prompted to enter the password, please input the password that you had chosen during the server installation for weblogicOCC.jks keystore file.
Bring this cert file into the directory $USER_INSTALL_DIR$\bea\wls\server\lib of the secondary server. If you have more than one secondary server, copy this file to all the secondary servers.
In the secondary server execute the following command:

keytool -import -alias primary.test.com -file primary.test.com.cer -keystore weblogicOCCTrust.jks

primary.test.com will be used as the alias in secondary server's trust keystore(weblogicOCCTrust.jks)file to uniquely identify it.
When prompted to enter the password, please input the password that you had chosen during server installation for the weblogicOCCTrust.jks keystore file. At the prompt to chose either the Yes or No option, choose Yes. Go to all the secondary servers and import the same way.

This completes importing of the new secondary server into all other server's trust key store files.
Now you must export the certificates from all the secondary servers including the new secondary server and import them into rest of the servers including the primary.

For example go to the directory $USER_INSTALL_DIR$\bea\wls\server\lib of the secondary server and export the certificate using the following command where secondary.test.com is the fully qualified domain name of the secondary:

keytool -export -file secondary.test.com.cer -alias weblogic -keystore weblogicOCC.jks
Import this file into primary server and rest of the servers using:

keytool -import -alias secondary.test.com -file secondary.test.com.cer -keystore weblogicOCCTrust.jks
Repeat steps 8 and 9 above to export the certs from each of the servers and import them to other servers. You can remove all the .cer files created for the purpose of importing and exporting.

Copying the Required Files From Primary to the Secondary

Follow these steps to copy the required files from primary to secondary:

Delete all the files in $USER_INSTALL_DIR$\deploy\activereasoning.ear\config\keystore of the secondary.
Copy all the files in $USER_INSTALL_DIR$\deploy\activereasoning.ear\config\keystore of the pirmary server into the same directory location on the secondary server.
Delete all the files in $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\security of the secondary server.
Copy all the files from $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\security of primary into the same location on the secondary server.
Copy the following file from the primary server into the same path on the secondary server:

$USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\fileRealm.properties
Delete all the files and sub-directories of $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\config in the secondary server.
Copy from the primary, the whole of sub-directory structure config into: $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\config of the secondary server. You can use the dos xcopy command to accomplish this.
Create the following new directory in the secondary. {SecondaryServerX} is the server name you have used during install such as SecondaryServer1.

$USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\servers\{SecondaryServerX}\security
Copy the the file from primary server to the directory created in the previous step:

$USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\servers\PrimaryServer\security\boot.properties

Adjusting the JDBC Connection Pool Sizes

Based on the number of secondary servers in the cluster, you need to increase the connection pool size and correspondingly increase the number of connections the database can handle. Also the database must be tuned to work with the increased number of connections.

As an example, if you have:

A primary and secondary, jdbc connection pool requires a max connection setting of 200. This is the default value.
A primary and two secondary servers, jdbc connection pool requires a max setting of 270.

For each additional secondary server, add 120 more connections.

The jdbc connection pool setting can be modified by going through the weblogic admin console. Follow these steps:

Click Lock & Edit
In the Domain Configurations, select jdbc --> Data Sources
Select OracleDS
In the Settings for OracleDS, click on Connection Pool. Set Maximum Capacity to the desired value based on the suggestions above for required number of connections. Click Save.

Also, as mentioned above, the database must be tuned to handle the new connection pool.

Uninstalling the Configuration Change Console

This section describes how to uninstall the Configuration Change Console Server.

Note:

Prior to uninstalling the server, you must first uninstall all agents.

To manually uninstall the Configuration Change Console Server, follow these steps:

Go to Start, choose Control Panel , and then select Add/Remove Programs.
Select Oracle Enterprise Manager Configuration Change Console Server from the list to uninstall the agent.
Follow the prompts to uninstall all parts of the server.