If an existing CCS Tomcat installation or instance is used, you can proceed to Create Application Specific Instance of CCS Tomcat (create an instance specifically for CA OM Web Services) or Deploy CA OM Web Services (use a shared instance).
To build a Tomcat instance to support CA OM Web Services on the mainframe, the supported version of Apache Tomcat can be installed from CA Common Services for z/OS. For more information about this process, see the CA Common Services for z/OS Installation Guide.
When installing the CCS Tomcat, the following (Tomcat-specific) information is required:
Specifies the IBM Java Runtime Path. This is the location (parent folder) of a pre-existing IBM Java installation. The SMP/E APPLY processing requires the use of applications under this Path (in the /bin folder).
Example: /sys/java31bt/v6r0m1/usr/lpp/java/J6.0.1
Specifies the top-level USS folder for the Tomcat installation. Sub-folder /CCS/tpv is created under this folder. The tpv folder is used as the mount point for the allocated zFS file system. The Tomcat files and folder are under the tpv folder.
Example: /cai/CASoftware
The actual mount point: /cai/CASoftware/CCS/tpv
Specifies the data set high-level qualifier for the zFS file to be allocated. This defaults to the Data Set Name Prefix previously specified for the SMP/E Target data sets.
Important: This zFS file system must be mounted. The MSM Installation mounts this when created. However, this is a one-time mount that does not persist following an IPL. If this Tomcat is to be used for production, this zFS dataset must be added to the system’s auto-mount table.
|
Copyright © 2013 CA.
All rights reserved.
|
|