Previous Topic: Install CCS TomcatNext Topic: IBM WebSphere Considerations

Post-Installation and Configuration Tasks › Prepare your Java Web Application Server › Create Application Specific Instance of CCS Tomcat

Create Application Specific Instance of CCS Tomcat

With CCS Tomcat installed, an application-specific instance of it can be created for CA OM Web Services. If an existing CCS Tomcat instance is used, you can proceed and Deploy CA OM Web Services.

To create an application-specific instance, the installed CCS Tomcat folders and files without the Tomcat programs are copied. This copy is configured to run as a started task and CA OM Web Services is deployed here.

Follow these steps:

  1. Indentify the CCS Tomcat installation that is used as the basis for this new instance. The name of the folder is ‘/cai/CASoftware/CCS/tpv/tomcat’. The folder ending at tpv is, later referred to as INSTALL_HOME.

    Note: The tpv folder contains a ‘tomcat’ symbolic link to a folder named either ‘apache-tomcat-6.0.29 or ‘apache-tomcat-7.0.34’.

  2. Indentify the JAVA_HOME folder. The name of the folder is ‘/sys/java31bt/v6r0m1/usr/lpp/java/J6.0.1’.

    Note: I t is recommended to use the same ‘SPMJHOME Directory’ value that is used when CCS Tomcat was installed.

  3. In the CAI.CDUZJCL, edit and submit job TOMC@IN1. This job allocates a new zFS dataset and mounts it. This zFS dataset must be added to the auto-mount table. Alternatively, you can use an existing file system – bypass all steps (delete or comment) expect the last step, CR8TDIR, which creates to ‘tomcat’ folder for the instance. Refer to instructions in the JCL. Make note of the PRODDIR value as it is needed in subsequent steps and it is referred to as PRODUCT_HOME.

    Review the results of the job. A new USS folder is created, PRODDIR/tomcat where PRODDIR is a folder of your choice.

    Important: This zFS file system must be mounted. This job mounts this when created. However, this is a one-time mount that does not persist following an IPL. If this Tomcat is used for production, this zFS dataset must be added to the systems' auto-mount table.

  4. In the CAI.CDUZJCL, edit and submit job TOMC@02. This job copies the CCS Tomcat installation to the PRODDIR/tomcat folder created in the previous step.

    Review the results of the job. Under the USS folder that is created in the previous step, there are several new sub-folders and files. This is a copy of the CCS Tomcat installation. The /lib folder is removed and /bin is with only one file.

  5. In the CAI.CDUZJCL, edit member TOMCPROC. This is the started task JCL for Tomcat. Do the following:
    1. Rename the member as per your site standards for a started task name. This can be done when the PROC is copied to a system data set such as SYS1.PROCLIB.
    2. Set the STDENV DD DSN value to reference the configured copy of TOMCPARM.

      Note: The started task needs security permissions for read/execute access to the installed CCS Tomcat (INSTALL_HOME) and read/write/execute access to the product-specific instance (PRODUCT_HOME).

  6. In the CAI.CDUZJCL, edit member TOMCPARM. This is the parameter file that contains the environment variables for the Tomcat for the task that is started. Do the following:
    1. Rename this member as per your site standards. This can be done when this member is copied to a system data set such as SYS1.PARMLIB.
    2. Set INSTALL_HOME to the parent of the CCS Tomcat installation. This is the value from step 1 less the "tomcat" sub-folder. This folder should have a sub-folder named tomcat a symbolic link to a release-specific tomcat folder. If there is a release specific tomcat folder and not a tomcat symbolic link, you will need to modify CATALINA_HOME to use the release-specific folder.
    3. Set PRODUCT_HOME to the parent of the product-specific Tomcat instance. This is the PRODDIR value from step 4.
    4. Set JAVA_HOME to the JAVA_HOME folder. This is the value from step 2.
  7. Update the product specific Tomcat’s server.xml file.
    1. Edit (ASCII) file server.xml in folder ${INSTALL_HOME}/tomcat/conf.
    2. If there are other instances of Tomcat running on the same mainframe system, the ports that are used must be changed. At a minimum, shut down the connector ports.

      Note: For more information, see the Apache Tomcat web site (http://tomcat.apache.org).

  8. (Optional) Update the product-specific Tomcat’s tomcat-users.xml file.
    1. Edit (ASCII) file tomcat-users.xml in folder ${INSTALL_HOME}/tomcat/conf.

      Note: By default, Tomcat users are not defined. I t is recommended to define at least one password-protected user with roles="manager,manager-gui,admin".

    2. Once the product-specific instance of Tomcat is configured, start the task verify Tomcat is working by accessing the Tomcat Web Application Manager page using the URL . You are prompted for Tomcat user and password.

      Note: The verification is possible only if a Tomcat user was defined.