Event Management Configuration › Deploying Event Management on Additional Systems

Deploying Event Management on Additional Systems

To run Event Management on other systems in addition to the first deployment system, copy the zFS files from the first deployment system to the additional systems. The first deployment (source zFS) files have already been configured. The new deployments require a small amount of system-specific reconfiguration.

Important! Do not proceed with the following steps until after you have configured the first deployment files and completed all previous steps in this chapter.

Follow these steps:

1. Verify that the mount points for the READ ONLY and READ/WRITE zFS are identical on the source and target systems.
2. (Skip this step if you are not using Calendars or Message Actions). 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 to avoid startup error messages.

   Start the Repository address space 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.

3. Verify that the System Requirements on the target system are filled.
4. Back up both the Event Management zFS files on the source system, 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. Verify that you are using the correct CAIGLBL0000 and STEPLIB by reviewing the modification that CA Common Services made in /etc/profile on the new system. If necessary, remove the sections that do not contain the correct CAIGLBL0000 and STEPLIB. These changes could be left over from a previous installation.
7. Allocate new zFS data sets on the new system and restore the previously saved 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, mount the READ ONLY zFS as READ/WRITE, and the READ/WRITE zFS as READ/WRITE. Then run the batch yourdeployHLQ.CNSMJCL job D5II0065 on that system to establish some system-specific information for the Java GUI.
   • Mount the READ ONLY zFS as READ ONLY or READ/WRITE, and the READ/WRITE zFS as READ/WRITE. Run the batch yourdeployHLQ.CNSMJCL job D5IFWMIG on the target system. The required system-specific directories for the new system are then created. Verify the results in STDOUT and STDERR. If the READ ONLY zFS is mounted READ ONLY, ignore informational messages in the STDERR file. Before you run any jobs on the new system, verify that all Event Management tasks are shut down (such as from a prior release).
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 verify that the correct data sets and libraries are specified.
9. Create a security account for the Java and web servers with the following attributes if you use the JAVA GUI.
   • UID zero - Define the user identity that runs the Java server and the web server with real UID zero. Users with a non-zero UID are denied access to the BPX.SUPERUSER resource.
   • Any valid group ID (GID)
   • Any valid home directory. A good choice is the directory where you install for z/OS.
   • 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, assign surrogate permission to users to log in without server checking passwords.
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>

    host_name

    The name or IP address of the host running the web server. Use a hostname rather than a hard-coded IP address.

    port_number

    The number that is assigned in the httpd.conf file. If you accept the default port of 80, you can omit the port number.