How to Promote a Test System › Review Required Changes

Review Required Changes

General

The following items must be changed if the test and product system are on the same LPAR:

• High-level qualifier (HLQ) for the deployed libraries
• UNIX System Services (USS) Runtime Home
• CHORTSF or CHORTSFR instances running on the same LPAR
  • By design, CHORTSF and CHORTSFR communicate across two LPARs and require the same SUFFIX. However, within a single LPAR, multiple CHORTSF or CHORTSFR instances cannot share a SUFFIX.
  • By default, the suffix is PROD. For a second TSF instance on the same LPAR, you need a new suffix. The commands to make this change appear later in this scenario.

Maintenance

Confirm that CA Chorus, its disciplines, and back-end systems have all current maintenance applied.

Port range

CA Chorus has the following port requirements for the JBoss server and Time Series Facility (TSF) components:

• 12 consecutive ports for the CA DSI Server and JBoss server. The JBoss ports consist of one DSI two-way (connecting and listening) port, and 11 server (listening) ports.
• Three one-way ports for TSF (These ports do not need to be consecutive with each other or with the 12 ports from the previous bullet).

  Note: If TSF instances are being used on a remote LPAR, two more one-way ports are required for the instance.

  Note: The TSF Remote Relay uses a third port for monitoring the connection from the TSF relay to the TCP/IP stack. By default, this port is dynamically allocated. To specify this port value instead of having it dynamically allocated, edit the MONPORT parameter in the TSFRPRMS member in your_chorus_hlq.CETJOPTN.

These ports are configured later in the installation during the JBoss server and TSF configuration.

To confirm that the ports you intend to use are available, consult your network management team.

Database

You must create a CA Datacom/AD/CA Chorus MUF. The CA Datacom/AD library may be shared, but you must create a separate CA Datacom/AD CUSLIB for the new CA Chorus environment. For the steps to create a MUF, see the CA Datacom/AD documentation.

H2 Database

Do not copy the H2 database (profile database) into a new environment. When you configure the new environment, JBoss creates an H2 database.

User Documentation

Evaluate any user documentation that has been indexed. Following the promotion, you can index this content in the new environment.

Important! Do not share the user doc file systems between two CA Chorus systems because you cannot mount a file system at two locations.

Started task names

Identify which of the follow uses cases matches your site:

• If the systems are running on a different LPAR, you can use the same Started Task Names. If you do so, place the procs for the started tasks in a separate proclib from the original location.
• If the systems are on the same LPAR, the started task names must be different. The procs can be in the same proclib.

Back-end system

You may want to access a different back-end system for some disciplines. For the instructions to establish access to the back-end systems, see the applicable Site Preparation Guide.