Configuring a JVM server for Axis2

Configure the JVM server to run Axis2 if you want to run Java web services or process SOAP requests in a pipeline.

About this task

Axis2 is a Java SOAP engine that can process web service requests in provider and requester pipelines. When you configure a JVM server to run Axis2, CICS automatically adds the required JAR files to the class path.

Start of changeYou can define the JVM server either with CICS® online resource definition or in a CICS bundle.End of change

Procedure

  1. Create a JVMSERVER resource for the JVM server.
    1. Specify a name for the JVM profile for the JVM server.
      Start of changeOn the JVMPROFILE attribute of JVMSERVER, specify a 1 - 8 character name. This name is used for the prefix of the JVM profile, which is the file that holds the configuration options for the JVM server. You do not need to specify the suffix, .jvmprofile, here.End of change
    2. Specify the thread limit for the JVM server.
      On the THREADLIMIT attribute of JVMSERVER, specify the maximum number of threads that are allowed in the Language Environment enclave for the JVM server. The number of threads that are required depend on the workload that you want to run in the JVM server. To start with, you can accept the default value and then tune the environment. You can set up to 256 threads in a JVM server.
  2. Create the JVM profile to define the configuration options for the JVM server.
    You can use the sample profile, DFHJVMAX.jvmprofile, as a basis. This profile contains a subset of options that are suitable for starting the JVM server. All options and values for the JVM profile are described in JVM profile validation and properties. Follow the coding rules, including those for the profile name, in Rules for coding JVM profiles.
    1. Set the location for the JVM profile.
      The JVM profile must be in the directory that you specify on the system initialization parameter, JVMPROFILEDIR. For more information, see Setting the location for the JVM profiles.
    2. Make the following changes to the sample profile:
      • Set JAVA_HOME to the location of your installed IBM Java SDK.
      • Set JAVA_PIPELINE to run Axis2.
      • Set CLASSPATH_SUFFIX to specify classes for Axis2 applications and SOAP handlers that are written in Java.
      • Set WORK_DIR to your choice of destination directory for messages, trace, and output from the JVM server.
      • Set TZ to specify the timezone for timestamps on messages from the JVM server.Start of changeAn example for the United Kingdom is TZ=GMT0BST,M3.5.0,M10.4.0.End of change
    3. Save your changes to the JVM profile.
      The JVM profile must be saved as EBCDIC on the z/OS UNIX System Services file system.
  3. Install and enable the JVMSERVER resource.

Results

CICS creates a Language Environment enclave and passes the options from the JVM profile to the JVM server. The JVM server starts up and loads the Axis2 JAR files. When the JVM server completes startup successfully, the JVMSERVER resource installs in the ENABLED state.

If an error occurs, for example CICS is unable to find or read the JVM profile, the JVM server fails to start. The JVMSERVER resource installs in the DISABLED state and CICS issues error messages to the system log. See Troubleshooting Java applications for help.

What to do next

  • Specify any directories that contain native C dynamic link library (DLL) files, such as DB2 or WebSphere MQ. You specify these directories on the LIBPATH_SUFFIX option in the JVM profile.
  • Configure CICS to run web service requests in the JVM server, as described in Using Java with web services.