This appendix provides instructions on how to set up secondary servers for Application Configuration Console. The instructions for each scenario are similar; briefly:

Shut down Application Configuration Console.

Make a copy of the complete Application Configuration Console installation.

Place the copy on the target (secondary) host.

On the primary host, disable the server being deployed.

On the target host, disable the servers that will continue to run on the primary host.

Edit configuration files appropriately.

Restart the primary and secondary servers.

Note:

The scenarios described in this appendix involve setup of another instance of a Tomcat JVM on a separate host machine. This is Oracle's recommendation. If you have any questions, contact Oracle Technical Support.

Before proceeding, ensure that the host where you are setting up a secondary server complies with the hardware and software requirements stated in Table 2-2 in Chapter 2. Oracle recommends that your product implementation be complete before you set up any secondary server instances. So, for example, if you intend to use automation modules, install them prior to secondary server setup.

D.1 Secondary Server Target Environment

The environment where you set up secondary servers should meet or exceed the hardware and software requirements of the Core Server host. The instructions tell you to relocate the entire Core Server installation directory so that everything else—configurations, user IDs and groups and so forth—is in place in the target environment. Additionally, the instructions assume that you are going to the same platform, for example, Linux to Linux.

D.2 Server Redeployment from the Installation Host

An Application Configuration Console installation creates separate deployments of the primary and secondary servers on the host machine. This facilitates server redeployment to another instance of a Tomcat JVM. The ability to redeploy these servers is an important aspect in any discussion of Application Configuration Console performance and scalability. Redeployment of secondary servers reduces the load on the Core Server so that response times are faster for other tasks, such as compare and provision operations.

This section provides instruction on redeploying the Web Reports server and the tracking server from the installation host to a target host.

D.2.1 Redeploying Web Reports Server

Copy the compressed file and unpack it in the same location on the target host. For example, if you installed the Core Server at opt/oracle/oacc/server/ on the primary host, unpack it to opt/oracle/oacc/server/ on the target host.

If the tracking server remains on the primary host, make the same changes to $OACC_INSTALL/appserver/tomcat/webapps/mvtrack/WEB-INF/classes/server_modules_registry.xml

On the target host, back up $OACC_INSTALL/appserver/tomcat/shared/classes/server_modules_registry.xml, then copy the version of server_modules_registry.xml that you edited in Step 6 from the primary host to the same location on the target host.

Linux/UNIX only. Disable automatic startup and shutdown of the SVN server on the target host, as follows:

Navigate to the following directory:

$OACC_INSTALL/appserver/tomcat/bin

Remove the following line from the startup.sh script and save your changes:

D.2.2 Redeploying the Tracking Server

Copy the compressed file and unpack it in the same location on the target host. For example, if you installed the Core Server at opt/oracle/oacc/server/ on the primary host, unpack it to opt/oracle/oacc/server/ on the target host.

Remove the following line from the the shutdown.sh script and save your changes:

cat svn_pid | xargs kill

Start Application Configuration Console on the primary and target hosts.

D.3 Multiple Tracking Server Deployment

The notion in this case is that you have more than one tracking server handling tracking operations in your environment. Introducing multiple tracking servers can relieve resource bottlenecks on particular machines.

For the purposes of this discussion, the current tracking server is the primary tracking server, and any additional deployments are secondary tracking servers. This section considers two possibilities:

Deploying the tracking server on the installation host

Deploying a redeployed tracking server

The system captures as part of the tracking operation record which tracking server instance executed the operation. The information (host name and unique tracking server ID) appears in the appropriate Client scheduled jobs list (tracking, comparisons, provisioning). See the Application Configuration Console Online Help for details.

D.3.1 Deploying the Installed Tracking Server

To deploy a secondary tracking server based on the installed primary tracking server:

Copy the compressed file and unpack it in the same location on the target host. For example, if you installed the Core Server at opt/oracle/oacc/server/ on the primary host, unpack it to opt/oracle/oacc/server/ on the target host.

On the target host, remove the Core Server and Web Reports deployments as follows:

Assign a unique server ID to the secondary tracking server deployment, as follows:

On the target host, open the following file in a text or xml editor:

$OACC_INSTALL/appserver/tomcat/webapps/mvtrack/WEB-INF/web.xml.

Edit the value of the mv.server.id <param-name> element so that it is unique across the global namespace of all server instances. A simple approach is to add a numerical sequence to the mvtrack qualifier of the default tracking server ID; for example:

mvtrack-2:764c1a8796092b09f27a320bdb8d9f2f

Sequentially increase the number for each secondary tracking server deployment. The only stipulation besides uniqueness is that the server ID cannot exceed 255 characters.

Save the file.

Add the secondary tracking server ID to the event distribution list, as follows:

Remove the following line from the the shutdown.sh script and save your changes:

cat svn_pid | xargs kill

Start Application Configuration Console on the primary and target hosts.

Once you have a deployed secondary tracking server, it becomes a simple task to deploy additional tracking servers, based on this deployment. All you have to do is change the server ID on the next deployed tracking server instance, and add the ID to the event distribution list on the Core Server.

D.3.2 Deploying a Redeployed Tracking Server

To deploy a secondary tracking server based on a redeployed primary tracking server:

Copy the compressed file and unpack it in the same location on the secondary tracking server host. For example, if you redeployed to opt/oracle/oacc/server/ on the primary tracking server host, unpack it to opt/oracle/oacc/server/ on the secondary tracking server host.

On the secondary tracking server host, remove the Core Server and Web Reports deployments as follows:

Assign a unique server ID to the secondary tracking server deployment, as follows:

On the secondary tracking server host, open the following file in a text or xml editor:

$OACC_INSTALL/appserver/tomcat/webapps/mvtrack/WEB-INF/web.xml.

Edit the value of the mv.server.id <param-name> element so that it is unique across the global namespace of all server instances. A simple approach is to add a numerical sequence to the mvtrack qualifier of the default tracking server ID:

mvtrack-2:764c1a8796092b09f27a320bdb8d9f2f

Sequentially increase the number for each secondary tracking server deployment. The only stipulation besides uniqueness is that the server ID cannot exceed 255 characters.

Save the file.

Add the secondary tracking server ID to the event distribution list, as follows:

On the Core Server host, open the following file in a text or xml editor:

Once you have a deployed secondary tracking server, it becomes a simple task to deploy additional tracking servers, based on this deployment. All you have to do is change the server ID on the next deployed tracking server instance, and add the ID to the event distribution list on the Core Server.

D.4 Verify Server Redeployment

Use this process to verify Web Reports and tracking server redeployment, as well as secondary tracking server deployment.

Start the Core Server.

Start the tracking server (redeployed and deployed secondary, as appropriate).

Start the Client.

Load some data and enable tracking; be sure to request e-mail notification on alerts.

Verify that the tracking server is handling the requests.

Verify that you can access Web Reports by clicking the URL in an e-mail notification.

For secondary tracking server deployments, verify in the Client that the scheduled jobs list identifies the appropriate host name and server ID of the secondary tracking server.

D.5 Redeployment and Automation Modules

If you install an automation module after deploying secondary servers, you have to port the AM installation to the secondary server host.

On the primary host, navigate to the following location:

$OACC_INSTALL/appserver/tomcat/shared/classes/extensions

Make a copy of the extensions folder.

On the secondary host (Web Reports, tracking, or both, as appropriate), place the copied folder at the following location:

$OACC_INSTALL/appserver/tomcat/shared/classes/

It is not necessary to restart the primary or the secondary server.

Scripting on this page enhances content navigation, but does not change the content in any way.