For the latest information on upgrading to and from any versions of CICS TS, see CICS TS V5.6.

Changes to options in JVM profiles

When you upgrade to a new release of CICS® TS, there are normally some changes to the options available in JVM profiles and to their possible or suggested settings.

The JVM server supports a variety of Java™ workloads. The following sample JVM profiles are supplied with CICS TS for z/OS®, Version 5.2:
  • DFHJVMAX.jvmprofile is a JVM profile that specifies the options for initializing the JVM server to support SOAP processing by Axis2 applications. Axis2 is an open source web services engine from the Apache foundation that supports a number of the web service specifications and provides a programming model to create Java applications that can run in Axis2.
  • DFHJVMST.jvmprofile is a JVM profile that allows the JVM server to be configured for a Security Token Service.
  • DFHOSGI.jvmprofile is a JVM profile that specifies the options for initializing the JVM server for Java applications that comply with the OSGi specification.
  • DFHWLP.jvmprofile is a JVM profile to run workloads for the Liberty profile, a lightweight application server that can support JSP and servlet applications for developing modern web interfaces for CICS. Liberty profile servers must use a file encoding of ISO-8859-1 or UTF-8. The supplied sample profile DFHWLP is configured to use ISO-8859-1.

JVM profiles must have a file extension of .jvmprofile. The JVM server fails to enable if this extension is not present. The sample JVM profiles that are shipped with CICS TS for z/OS, Version 5.2 have this file extension.

When you upgrade to a new release of CICS TS, there are normally some changes to the options available in JVM profiles and to their possible or suggested settings. A good practice is to use the sample JVM profiles that are shipped with the new release, and reapply the customization that you made to those JVM profiles in previous releases. Using the latest JVM profiles ensures that you do not miss important updates to the options and their settings.

The obsolete, changed, and new options in JVM profiles are summarized here. For more details about the options, see JVM profiles: options and samples .

Table 1. New options in JVM profiles
Option Status CICS and Java launcher action Notes
JNDI_REGISTRATION For CICS sample profiles Accepted Specifies that the JNDI registration JAR files are automatically added to the JVM runtime environment.
SECURITY_TOKEN_SERVICE For CICS sample profiles Accepted Controls whether the JVM server can use security tokens. This option must be set to YES for a JVM server to use security tokens. If this configuration option is set to NO, the JVM server is initialized as an OSGi JVM server and Security Token Service support is disabled for that JVM server. SECURITY_TOKEN_SERVICE=YES is not compatible with JAVA_PIPELINE=YES, which configures the JVM to support Axis2.
WSDL_VALIDATOR For CICS sample profiles Accepted Enables validation for SOAP requests and responses against their definition and schema.
Table 2. Changed and obsolete options in JVM profiles
Option Status CICS and Java launcher action Replace with Notes
OSGI_BUNDLES Not supported in Liberty JVM server Liberty JVM server does not enable with this option n/a Deploy OSGi bundles in a Liberty JVM server as part of an enterprise bundle archive (EBA) or as library bundles.

Changes to JVM profile symbols

&CONFIGROOT;
When you use this symbol in a JVM profile, the absolute path of the directory where the JVM profile is located is substituted at run time.

For information about the other supported JVM profile symbols, see JVM profiles: options and samples.

Parent topic: Upgrading the Java environment

dfhe5_plan_java_jvmprof.html | Timestamp icon Last updated: Saturday, 15 June 2019