This chapter describes the process for installing the Configuration Change Console Server on Microsoft Windows.
When installing any of the server components (Primary server, Secondary server, or Messaging Broker server), the file server_win32.part2 must be in the same directory where server_win32.exe is located. This additional file is required for installation of the server elements.
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-win32.exe file from the Configuration Change Console media. The Installer will take a few moments to initialize. Ensure that the same directory from where you are running this installation also has the file server-win32.part2 as this file is also required for installation. The installer will not proceed if this file is missing.
Click Next when the Introduction screen appears
Specify the installation directory or choose the default. Click Next.
Choose the type of installation being performed. In this case, you would choose Non-Clustered, then click Next.
Choose server type as Primary (with bundled Admin Server), then click Next.
Note that the Oracle database must be installed and running properly before the Configuration Change Console can be installed.
Click Next if you have the Oracle database installed and followed the steps to create the gateway database or Cancel if you still need to perform these steps.
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 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 your organization name and click Next. If you will be installing multiple instances of Configuration Change Console, the organization name should reflect the name of your IT organization, such as "West Coast Operations" versus "East Coast Operations". This organization name can be used if creating BI Publisher Reports that span multiple instances of Configuration Change Console Server.
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 Config Change Console PrimaryServer. Additionally, the Weblogic admin console service called Oracle Config Change Console AdminServer is created. 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. If you specify the maximum memory to be larger than your server OS is configured to handle, the service will fail to start.
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.
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.
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.
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 and any number of messaging broker servers. All of these servers will belong to the same Oracle Weblogic domain called ConfigChangeConsole. This domain is set up automatically when you start performing the installation steps in this chapter.In a clustered environment, you must be sure you install all three types of servers (primary, secondary, and messaging broker) to ensure that the product will operate properly. In environments with many agents, there may be more messaging brokers installed in the cluster than there are secondary servers. As a guideline, there should be at least one messaging broker for every 3000 agents. Adding too many messaging brokers and secondaries, however, will also put more load on your database as the number of simultaneous writes of events to the database is based on the number of Messaging Brokers multiplied by the number of Secondaries. If you do not define enough brokers and secondaries, then messages will back up in the Messaging Brokers and the processing of them will be delayed.
If you install an environment as clustered, you must have a primary server with its built in admin server, at least one secondary, and at least one messaging broker. If you do not have at least one secondary and messaging broker, events will not be captured from agents.
All of the servers in the cluster (Primary server, Secondary Servers, and Messaging Broker Servers) should be in the same network segment to reduce the chance of connection problems or slow performance due to network latency. The ping latency should be less than 0.5ms between the servers.
You cannot install a Secondary Server on the same physical host as the Primary Server.
All the hosts in the cluster must be able to parse the Fully Qualified domain name of each other. You can test by pinging the fully qualified name of each server from the primary server and vice-versa.
Throughout this section, $USER_INSTALL_DIR$ refers to the server installation directory.
Follow these steps to install the primary server for a clustered Configuration Change Console environment:
Double-click on the server-win32.exe file from the Configuration Change Console media. The Installer will take a few moments to initialize. Ensure that the same directory from where you are running this installation also has the file server-win32.part2 as this file is also required for installation. The installer will not proceed if this file is missing.
Click Next when the Introduction screen appears
Specify the installation directory or choose the default. Click Next.
Choose the type of installation being performed. In this case you would choose Clustered, then click Next.
Choose server type as Primary (with bundled Admin Server), then click Next.
Note that the Oracle database must be installed and running properly before the Configuration Change Console can be installed. Click Next if you have the Oracle database installed and followed the steps to create the gateway database or Cancel if you still need to perform these steps. 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. If you will be installing multiple independent instances of Configuration Change Console, the organization name should reflect the name of your IT organization, such as "West Coast Operations" versus "East Coast Operations". This organization name can be used if creating BI Publisher Reports that span multiple instances of Configuration Change Console Server.
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 CCC PrimaryServer. 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. If you specify the maximum memory to be larger than your server OS is configured to handle, the service will fail to start.
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.
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 the size of the deployment. Note: The Secondary Server cannot be installed on the machine on which the Primary Server is installed.
Double-click on the server-win32.exe file from the Configuration Change Console media. The Installer will take a few moments to initialize. Ensure that the same directory from where you are running this installation also contains the file server-win32.part2 as this file is also required for installation. The installer will not proceed if this file is missing.
Click Next when the Introduction screen appears.
Specify the installation directory or choose the default. Click Next.
Choose the type of installation being performed. In this case, you would choose Clustered, then click Next.
Choose a server type of Secondary, then click Next. Note that installing a secondary server will not include any messaging broker servers, so you must install one or more messaging brokers after installing your secondaries. The secondary and messaging brokers are separated so that each can have the most amount of memory available for a java process. A Java virtual machine will be limited in how much memory is available to it based on Java and the Operating System (typically about 1.4 GB for Windows 32-bit).
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 ports for the admin server which was installed with the Primary server. The HTTP and HTTPS port was set when installing the primary server. The default HTTP port is 8080 and the HTTPS port value is 8090. You may have provided different port numbers for the admin server at the time the Primary Server was installed.
Enter the ports to use for the secondary 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. You will need to know which port you use for HTTPS 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. If you specify the maximum memory to be larger than your server OS is configured to handle, the service will fail to start.
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.
After the installation of a secondary server is finished, open a DOS window and navigate into the $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole directory. Then run the setServer.cmd command from the command line. You will need to enter the password for the Admin Server console (This password was set for the weblogic admin user when installing the Primary Server). You will also need to enter the key phrase you chose for the two certificate keystores that this secondary server uses to store SSL certificates. After responding to the prompts, this secondary server will be merged into the existing domain that was created when installing the Primary Server.
The installation will create a new Windows service called Oracle Config Change Console X where X will be replaced with the name you gave to the secondary server installation (for example: SecondaryServer1). You can go to the Services Control Panel to start this secondary server after you have finished all other components and followed the steps under Post Installation Steps for Cluster Installation.
Follow these steps to install the messaging broker server. You can install multiple standalone brokers on the same physical host and they can be on the same host as other cluster components.
Double-click on the server-win32.exe file from the Configuration Change Console media. The Installer will take a few moments to initialize. Ensure that the same directory from where you are running this installation also has the file server-win32.part2 as this file is also required for installation. The installer will not proceed if this file is missing.
Click Next when the Introduction screen appears.
Specify the installation directory or choose the default. Click Next.
Choose the type of installation being performed. In this case you would choose Clustered, then click Next.
Choose server type as Messaging Broker, then click Next.
Specify the name of the messaging broker instance. The name should be of the format MessagingBrokerX where you replace X with the broker number starting from 1. For instance, the first standalone broker server would be called MessagingBroker1.
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 ports for the admin server which was installed with the Primary server. The HTTP and HTTPS port was set when installing the primary server. The default HTTP port is 8080 and HTTPS port value is 8090. You may have provided different port numbers for the admin server at the time the Primary Server was installed.
Enter the ports to use for this messaging broker server. There are two ports configured here; HTTP and HTTPS. HTTPS is used for agents to communicate with this messaging broker server. You will need to know the port you use for HTTPS when you install the agents. Click Next.
Specify the minimum and maximum amount of memory allocated to the Configuration Change Console Messaging Broker 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. If you specify the maximum memory to be larger than your server OS is configured to handle, the service will fail to start.
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.
After the installation of a secondary server is finished, open a DOS window and navigate to the $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole directory. Then run the setServer.cmd command from the command line. You will need to enter the password for the Admin Server console (This password was set for the weblogic admin user when installing the Primary Server). You will also need to enter the key phrase you chose for the two certificate keystores that this secondary server uses to store SSL certificates. After responding to the prompts, this secondary server will be merged into the existing domain that was created when installing the Primary Server.
The installation will create a new Windows service called Oracle Config Change Console X where X will be replaced with the name you gave to the messaging broker server installation (for example: MessagingBroker1). You can go to the Services Control Panel to start this secondary server after you have finished all other components and followed the steps under Post Installation Steps for Cluster Installation.
The following steps must be performed after installing all of the components of the cluster. If you add another member to the cluster at a later time, these steps must be performed for the new member as well.
Because all Configuration Change Console Servers communicate over an SSL channel, SSL needs to be configured before starting a secondary server or messaging broker. Follow the steps below to export or import the certificates into servers. If keytool is not in your path, then use the full path name to access the tool that was installed along with the server (for example: C:\oracle\ConfigurationChangeConsoleServer\bea\jrockit_160_05\bin\keytool):
Navigate to the $USER_INSTALL_DIR$\bea\wls\server\lib directory of the currently installed secondary server or messaging broker.
Execute either of the following two commands:
keytool -export -file SecondaryServerX.cer -alias weblogic -keystore weblogicOCC.jks
keytool -export -file MessagingBrokerX.cer -alias weblogic -keystore weblogicOCC.jks
SecondaryServerX.cer or MessagingBrokerX.cer is the file name of cert of current server SecondaryServerX or MessagingBrokerX is the server name that you just installed.
Copy this cert file into the directory $USER_INSTALL_DIR$\bea\wls\server\lib of the Primary Server.
Navigate to the $USER_INSTALL_DIR$\bea\wls\server\lib directory of the primary server.
On the server on which the Primary Server is installed, execute either of the following two commands:
keytool -import -alias SecondaryServerX -file SecondaryServerX.cer -keystore weblogicOCCTrust.jks
keytool -import -alias MessagingBrokerX -file MessagingBrokerX.cer -keystore weblogicOCCTrust.jks
SecondaryServerX or MessagingBrokerX will be used as the alias in the primary 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 the Primary Server installation for the weblogicOCCTrust.jks keystore file. At the prompt when choosing either the Yes or No option, choose Yes.
This completes importing of the new secondary server or messaging broker into the primary server's trust key store files. You can remove the .cer files created for the purpose of importing and exporting.
Repeat the above steps for all Secondary servers and Messaging Broker Servers.
Copy the weblogicOCCTrust.jks file of Primary Server to all Secondary Servers or Messaging Brokers. You need to overwrite all the weblogicOCCTrust.jks files of those servers.
Note:
Each time you install a new Secondary Server or JMS Broker, you must repeat these steps. Following that, you should restart all servers.Follow these steps to copy the required files from Primary to Secondary Servers.
Delete all the files in $USER_INSTALL_DIR$\deploy\activereasoning.ear\config\keystore on the secondary server.
Copy all the files in $USER_INSTALL_DIR$\deploy\activereasoning.ear\config\keystore of the primary server into the same directory location on the secondary server.
Delete all the files in $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\security on the Secondary Server.
Copy all the files from $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\security of the Primary Server into the same directory 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 all files from $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\config of the Primary Server into the same directory location on the Secondary Server.
Copy the file $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\servers\PrimaryServer\security\boot.properties from the Primary Server to the directory $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\servers\{SecondaryServerX}\security on the Secondary Server.
Follow these steps to copy the required files from Primary to Messaging Broker Servers:
Delete all the files in $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\security of the Messaging Broker.
Copy all the files from $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\security of Primary to the same directory on the Messaging Broker.
Copy the following file $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\fileRealm.properties from the Primary Server to the same location on the Messaging Broker.
Delete all the files and sub-directories of $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\config in the Messaging Broker.
Copy all files from $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\config of the Primary Server into the same directory location on the Messaging Broker.
Copy the file $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\servers\PrimaryServer\security\boot.properties from Primary Server to the directory $USER_INSTALL_DIR$\bea\user_projects\domains\ConfigChangeConsole\servers\{MessagingBrokerX}\security on the Messaging Broker.
The Configuration Change Console database must be tuned to work with the increased number of secondary servers and/or Messaging brokers.The database pool configuration for the Weblogic cluster is set based on a single server, but the connection pool size applies to each Primary and Secondary server in the cluster. For example, if you set the JDBC connection pool size to 200 and have 1 primary server and 5 secondary servers, a total of 1200 JDBC connections will be available across the cluster.The number of JDBC connections to specify in the database settings is based on several factors. One major factor is the number of Message Driven Beans (MDBs) configured for the servers. An MDB is the processing unit that handles incoming messages from the Messaging Broker Servers. With the out-of-box configuration, a non-clustered installation has less than 110. To support the MDBs, and other internal processing as well as user UI connections, the JDBC pool should be set to 200 connections for the non-clustered installation.With the out-of-box configuration, each Primary and Secondary server has no more than 60 MDBs. For the clustered environment, the maximum consumed MDBs for each secondary must be multiplied by the number of Messaging Broker servers installed in the cluster since each secondary server will have MDBs that connect to each Messaging Broker. As an example, if you have a clustered environment with a Primary Server, 3 Secondaries and 4 Messaging brokers, each secondary server will have 60 x 4 = 240 MDBs. To support other internal processing as well as user UI connections, the JDBS pool size should be set to 300 connections for the clustered-installation. If you add another Messaging broker to the cluster, then at least 60 more connections should be added to the Weblogic JDBC pool size. This setting applies to each Primary and Secondary in the cluster.Adding a Messaging broker can help for failover and handling high loads, but it also will result in more parallel executions into the database which requires your database to be scaled to handle the larger load.The Weblogic JDBC pool size setting can be configured through the Weblogic administrative console or by editing the file {install dir}/bea/user_projects/domains/ConfigChangeConsole/config/jdbc/OracleDS-jdbc.xml and adjusting the max-capacity setting.You will need to ensure that your database is properly sized to match the size of the Configuration Change Console cluster you need for your environment. The number of agents does not affect how many database connections are needed as only the Primary Server and Secondary servers will connect to the database.
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 CCC PrimaryServer from the list to uninstall the primary server. If you are uninstalling a component in a cluster other than the primary server, each component will start with Oracle Enterprise Manager CCC.
Follow the prompts to uninstall all parts of the server.