Previous Topic: Additional InformationNext Topic: Silent Installation

Installation Guide › High Availability › Additional Information › Configurable Parameters For High Availability

Configurable Parameters For High Availability

The following table is a list of configurable parameters for High Availability. Access the parameters from Administration, Site Settings, Advanced, Configuration, then select the entity. The parameters are for both from scratch installations and upgrades.

Entity

Value

SMI Application Server

Tomcat shared network IP Address in application server

Administration

Tomcat shared network IP Address in application server

ACE2

Shared address of application server

Adapter Wizard

Shared address of application server

Queues

(Current status MSMQ machine, Dashboard MSMQ machine, Default MSMQ machine)

Shared address of application server

Reports

Location of shared storage folder/Booklet Path

System

WEB NLB address

Known Issues

There is a known issue where High Availability does not support the Content Transfer feature (Content Transfer, Import, Export, Packages).

To resolve: Follow the below steps to work with a specific web server directly. If this web server fails, change the configuration to work with another server.

  1. Configure a specific server by selecting one of the web servers designated for Content Transfer use. Verify that it is accessible directly, not only through the Load Balancer.
  2. Turn on the Oblicore – Oblisync service on the JBoss Application Server and set it to automatic, on the selected web server.
  3. Point the web browser to the JBoss Service on the selected web server.
  4. Click on Administration, Site Settings, Advanced, Configuration, Content Transfer from the CA Business Service Insight UI.
  5. Change the Content Transfer Server parameter value to point to the server selected in step 1. Use this format: http://ServerName:8180/ObliSyncApi/services/ObliSync.wsdl.
  6. Configure the following parameters in the database: t_system_configurations.

Entity

Value

configuration_directory

<Installation Directory>Packages\Configuration\

input_directory

<Installation Directory>Packages\

log_directory

<Installation Directory>Packages\Log\

output_directory

<Installation Directory>Packages\

temp_directory

<Installation Directory>Packages\Temp\

Note: If you already have exported packages, move the packages from the server that failed to another server.