Configure Showcase in a RobotHA Environment

 

The following steps are specific to a RobotHA disaster recovery environment, where Showcase is installed on the Production (source) IBM i system and is replicated to a backup (target) system.

Steps

1. Showcase must be installed from scratch on both systems. This ensures that UDF’s and Stored Procedures are created correctly. The version of Showcase on both systems must match. We recommend installing on the Backup system first, that way you can avoid any conflicts if replication starts before you are ready.
2. If you don’t have a Showcase license for the Backup system, then you must request a temporary license to test it and a license transfer to move your license in the event of a disaster recovery. If you have licenses for both systems – either permanent or temporary – then you should enter them BOTH on the PRODUCTION system. The Fortra license commands allow you to enter multiple licenses, and as long as the license is not expired, you can enter licenses for a different system. This means you can maintain all license codes on Production, and will not have to enter new codes on the Backup system if/when there’s a role swap.
3. Once Showcase is installed on both systems, all objects can be replicated between Production and Backup. For Warehouse Builder, you must also replicate the library(ies) and/or file(s) updated by Builder Definitions, as well as the Job Schedule Entries for Distributions.

During a Role Swap:

There are several tasks that may be needed to ensure Showcase runs smoothly. Since all objects are replicated, any reference to the system by name (such as for Showcase security or Warehouse Builder distributions) may need to be updated.

Note: Depending on the Role Swap scenario, you may not need to do any of these. Because the license codes for both systems are already entered, it’s possible to simply connect with a Showcase client without doing anything else.

Steps

1. Use MAPDIST for Warehouse Builder. This is needed if Warehouse Builder Definitions either read from or write to an iASP, and the iASP name will be different after a Role Swap. As long as Warehouse Builder Definitions read from and write to *SYSBASE libraries on the local system, or libraries that are on the same iASP, then this step is not needed.
2. Update Security Files if the Backup system has an iASP. This is needed only if Production and Backup systems connect to different iASP’s. The reason is because Showcase security on iASP objects specifies the iASP name. If no iASP is used, or if the iASP name doesn’t change, then this step is not needed.
3. Use RMVSCTCP/ADDSCTCP to update Showcase TCP/IP configuration settings. This is needed if you will be changing Host Name, Domain Name or Host Table Entry for the Backup System during a Role Swap. If your Role Swap is completed without changing one of those three things, then this step isn’t needed. (See MAPDIST Procedure below for specific instructions)
4. PC data source: This might be needed if the system IP address doesn’t change during a Role Swap. Either use a DNS name that will change to point to the Backup system when a Role Swap occurs, or you will need to update the data source on all PC’s with the new address.

MAPDIST Procedure

Issue the MAPDIST command. The MAPDIST command is included in all Warehouse Manager Server 9.0 libraries. Note: End the Showcase server before running the MAPDIST command.

Parameters:

Server type to map. The server type to be mapped. Possible values include:

*SOURCE - Maps the definition's source data source.

*TARGET - Maps the definition's target data source.

*BOTH - Maps the definition's source and target data source.

Old RDB name - The original name of the RDB to be mapped.

Old SC library name - The original name of the server library to be mapped.

New RDB name - The new RDB name to be mapped. Using *SAME retains the current RDB name. The user also can specify *LOCAL, resulting in local RDB usage (even after it is restored in a different system).

New SC library name - The name of the new server library to be mapped.

New ODBC data source name - The user-defined Showcase data source name. This is the data source name the Warehouse Builder client application uses when connecting to the IBM i.

Notes

• All parameters are required.
• The commands cannot run while the server is running (the user receives an error indicating that the command cannot run).
• A warning message is logged when the old RDB or the old server library is not used by any existing Warehouse Builder definition.
• If the source RDB is changed, source tables must exist in the new system for the definition to work.
• If the target RDB is changed, the user is responsible for creating the target tables in that system. To create the target table, the user must open the definition with Warehouse Builder client and resave.

Example

MAPDIST SVRTYPE(*BOTH) OLDRDB(F7051930) OLDLIB(SCSERVER97) NEWRDB(H21828CV) NEWLIB(SCSERVER97) NEWDSN(PC Data Source Name)

Updating Security files if the Backup System has an iASP:

The Showcase server stores the database name (Relational Database Directory Entry) for the data being secured. When the data security resides on the local/internal ASP of the IBMi system, Showcase stores the database name as "*LOCAL". When the data resides on an iASP, Showcase stores the database name as the name of the iASP. So the the database name must be changed from "*LOCAL" to the name of the iASP. Issue the following commands to make this change:

Warning: The following steps should be completed by an individual with *SECOFR privileges on the IBMi. Under no circumstances should an end user be given these instructions.

In the following commands, replace:

• SCSERVER with the name of your Showcase server library
• IASP1 with the name of your iASP

Commands

SCSERVER/ENDSCSVR

RMVPFTRG FILE(SCSERVER/SCCOLSEC)

RMVPFTRG FILE(SCSERVER/SCFILSEC)

RMVPFTRG FILE(SCSERVER/SCLIBSEC)

RMVPFTRG FILE(SCSERVER/SCROWSEC)

STRSQL

UPDATE SCSERVER/SCCOLSEC SET COCAT = 'IASP1' WHERE COCAT='*LOCAL'

UPDATE SCSERVER/SCFILSEC SET FLCAT = 'IASP1' WHERE FLCAT='*LOCAL'

UPDATE SCSERVER/SCLIBSEC SET LBCAT = 'IASP1' WHERE LBCAT='*LOCAL'

UPDATE SCSERVER/SCROWSEC SET RWCAT = 'IASP1' WHERE RWCAT='*LOCAL'

UPDATE SCSERVER/SCPFCALS SET CACAT = 'IASP1' WHERE CACAT='*LOCAL'

UPDATE SCSERVER/SCPFFALS SET FACAT = 'IASP1' WHERE FACAT='*LOCAL'

UPDATE SCSERVER/SCPFLALS SET LACAT = 'IASP1' WHERE LACAT='*LOCAL'

ADDPFTRG FILE(SCSERVER/SCCOLSEC) TRGTIME(*BEFORE) TRGEVENT(*UPDATE) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCCOLSEC) TRGTIME(*BEFORE) TRGEVENT(*INSERT) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCCOLSEC) TRGTIME(*BEFORE) TRGEVENT(*DELETE) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCFILSEC) TRGTIME(*BEFORE) TRGEVENT(*UPDATE) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCFILSEC) TRGTIME(*BEFORE) TRGEVENT(*INSERT) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCFILSEC) TRGTIME(*BEFORE) TRGEVENT(*DELETE) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCLIBSEC) TRGTIME(*BEFORE) TRGEVENT(*UPDATE) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCLIBSEC) TRGTIME(*BEFORE) TRGEVENT(*INSERT) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCLIBSEC) TRGTIME(*BEFORE) TRGEVENT(*DELETE) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCROWSEC) TRGTIME(*BEFORE) TRGEVENT(*UPDATE) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCROWSEC) TRGTIME(*BEFORE) TRGEVENT(*INSERT) PGM(SCSERVER/SCTRIG)

ADDPFTRG FILE(SCSERVER/SCROWSEC) TRGTIME(*BEFORE) TRGEVENT(*DELETE) PGM(SCSERVER/SCTRIG)

SCSERVER/STRSCSVR

Showcase TCP/IP Configuration

Should it be necessary to change the Showcase TCP/IP configuration, there are two commands: RMVSCTPC and ADDSCTCP. Showcase stores the system’s Host Name and Domain Name from CFGTCP 12. When the server starts, it tries to establish a connection to itself by resolving those names to a Host Table Entry (CFGTCP 10). If the connection is successful, then the server connects to the *LOCAL RDB (Relational Database Entry).

After the Role Swap, verify on the new “Production” system:

• CFGTCP 12: Host Name and Domain Name are correct for the system

• CFGTCP 10: There must be a valid IP address using the above Host Name and Domain-Qualified Host Name (both must be present on the same IP address)

• WRKRDBDIRE: Verify that the *LOCAL entry exists and is correct

If CFGTCP 10 and 12 have not changed, then no action is necessary. If they have changed, then you must perform the following steps:

1. Make a note of existing Showcase server attributes:
   What subsystem does the Showcase server run under? The default is QCMN. You can use WRKACTJOB (of the server is currently active) to verify the subsystem.
   WRKSRVTBLE – Page Down to the bottom, and take note of the three ports reserved for Showcase. The entries will be in this format, and you'll need to know the port numbers associated with each entry.
   SCFIREWALL(+server name) - Firewall Port Number
   SCRMICOMP(+server name) - Compressed Data Firewall Port
   SCSERVER(+server name) - TCP Port Number
2. Issue the command: servername/ENDSCSVR
3. Issue the command: servername/RMVSCTCP FRCRMV(*YES)
4. Issue the command: servername/ADDSCTCP and press F4. Enter the information obtained in Step 1
   Example:
   servername/ADDSCTCP SBSD(QCMN) TCPPORT(43419) FWPORT(43420) RMICPORT(43421)
5. Verify that the server started automatically at the completion of the ADDSCTCP command. This resets the server info, so that it will run correctly on the system.