Installing from Pax Files Using the SAMPJCL Method › Deploy Products › Deploying Event Management on Multiple Systems

Deploying Event Management on Multiple Systems

If you want to run Event Management on multiple systems, you have two choices:

• Do a complete installation on each system. This provides separate CSIs for tracking each system independently.
• Track the software using the existing CSI and simply copy the installation target data sets to the other machines.

Install Event Management on another system after completing all the installation and configuration steps on the first system.

To deploy Event Management on multiple systems

1. If you are using Calendars or Message Actions, see the CA Datacom/AD Installation Guide. Start the repository address space and JAVA GUI before using Event management on your target system.

   Initialize the Repository before the Event Management components start, or you may get startup error messages.

   The Repository address space should be started as a long running batch job or as a started task. The caiopr daemon starts without the Repository address space running, but the Calendar daemon does not.

2. Ensure that the mount points for the READ ONLY and READ/WRITE zFS are identical on the source and target systems.
3. Check the System Requirements on the target system.
4. Back up the READ/WRITE Event Management zFS files, if you have not already done so.
5. Make the BASE CAW0LOAD and CAW0PLD, and the MFNSM CNSMLOAD, CNSMPLD, CNSMPROC and CNSMJCL partitioned data sets accessible, either through shared DASD or by copying the data sets.
6. Allocate new Read/Write zFS data sets on the target system and restore the READ/WRITE Event Management zFS backups into the newly created zFS data sets. Mount the READ ONLY zFS and READ/WRITE zFS.

   Review the bullets carefully to determine proper mount criteria. Remember to update your BPXPRMxx member on the target system to add MOUNT directories for the READ/WRITE zFS (MODE RDWR) and the READ ONLY zFS (MODE READ).

   • If you want to use the Java GUI with the target system, the READ ONLY zFS must be mounted as READ/WRITE, and the READ/WRITE zFS must be mounted as READ/WRITE. Then run the batch yourdeployHLQ.CNSMJCL job D5II0065 on that system.
   • The READ ONLY zFS may be mounted as READ ONLY or READ/WRITE, and the READ/WRITE zFS should be mounted as READ/WRITE. Run the batch yourdeployHLQ.CNSMJCL job D5IFWMIG on the target system. This creates the required directories for this system. Check STDOUT and STDERR for the results. If the READ ONLY zFS was mounted READ ONLY, the STDERR file will contain informational messages which can be ignored. Prior to running this script, ensure that all Event Management tasks are shut down.
7. Ensure that you are using the correct CAIGLBL0000 and STEPLIB by reviewing the Modification made by CA Common Services in /etc/profile. If necessary, remove the sections that do not contain the correct CAIGLBL0000 and STEPLIB. These could be left over from a previous installation.
8. Copy your started tasks or batch job to the new system if you are starting the Repository address space. Review your JCL/PROC to ensure that the correct data sets and libraries are specified.
9. Create a security account for the Java and Web servers with these attributes if you use the JAVA GUI.
   • UID zero - The user identity that runs the Java server and the web server must be defined with real UID zero. You cannot assign a non-zero UID and permit the user access to the BPX.SUPERUSER resource.
   • Any valid group ID (GID)
   • Any valid home directory (the directory where you install for z/OS is a good choice)
   • Any valid shell program, typically /bin/sh
   • READ permission to IBM FACILITY resources BPX.SUPERUSER, BPX.DAEMON, and BPX.SERVER, if you implement any of these features; optionally, surrogate permission to any users that are to be signed on without password checking by the server
10. Copy your started tasks or batch jobs for the web server and Java server to the new system if you use the JAVA GUI.
11. Access the Event Management GUI by starting a web browser session with a URL of this form: http://<host_name>:<port_number> where host_name is the name or IP address of the host running the web server, and port_number is the number you assigned in the httpd.conf file. It is highly recommended that a hostname be used rather than a hardcoded IP address. If you accept the default port of 80, you can omit the port number.