Customizing the supplied sample JVM profiles and JVM properties files

Follow this procedure if you want to keep the existing name for the JVM profile or JVM properties file that you are customizing. When you keep the existing name for the file, applications that are already set up to use that JVM profile or JVM properties file will use your customized file right away. If you want to change the name of the file, follow the procedure in Creating your own JVM profiles and JVM properties files; if you do this, applications will not use your new JVM profile or JVM properties file unless you make further changes to inform the applications of the new file name. If you are customizing DFHJVMPR, bear in mind that DFHJVMPR is the default if no JVM profile is specified in a PROGRAM resource definition, and it is used by sample programs. Either make sure that all your Java programs which specify DFHJVMPR, or no JVM profile, in their PROGRAM resource definitions are suited to the changes that you are making, or copy DFHJVMPR and change its name before carrying out any customization.

To customize the supplied sample files, keeping the file names the same, follow this procedure:
  1. Open the JVM profile or JVM properties file in a standard text editor, and change the options that you want to change, using the lists of options in the CICS® System Definition Guide for reference. Each parameter or property is specified on a separate line, and the parameter or property value is delimited by the end of the line. Follow the coding rules in the CICS System Definition Guide.
  2. If you want to enable Java 2 security, you need to specify some options in the JVM properties file, and set up one or more security policy files to define security properties for the JVM. Protecting Java applications in CICS by using the Java 2 security policy mechanism tells you what options you need to specify in the JVM properties file, how to set up a security policy file, and about the CICS-supplied sample security policy file dfjejbpl.policy, which defines security properties that are suitable for JVMs that are used by enterprise beans.
  3. For JVM profiles, store the customized JVM profile in the HFS directory that is specified by the JVMPROFILEDIR system initialization parameter. CICS loads the JVM profiles from this directory. Enabling CICS to locate the JVM profiles and JVM properties files explains how to identify and change this directory. If this directory is set to be the directory containing the supplied sample JVM profiles, you can simply store your customized profiles in the samples directory, replacing the supplied samples. (If you do this, keep a copy of the original supplied sample JVM profiles in another folder for future reference.) Ensure that CICS has read and execute access on HFS for your JVM profile and the directory containing it. Giving CICS regions permission to access HFS directories and files tells you how to do this.
  4. For JVM properties files, it is simplest to store the customized JVM properties file in the HFS directory /usr/lpp/cicsts/cicsts31/props, where the supplied sample JVM properties files were placed at installation. (Keep a copy of the original supplied sample JVM properties files in another folder.) You need to specify the full path name for the JVM properties file, using the JVMPROPS option, in all the JVM profiles that reference that JVM properties file. For example, a JVM profile that states JVMPROPS=/usr/lpp/cicsts/cicsts31/props/dfjjvmpr.props references the JVM properties file dfjjvmpr.props in the directory that contains the supplied sample JVM properties files. If you place the customized JVM properties file back in its original directory, the correct path name will already be specified in the JVM profiles. If you prefer to store your customized JVM properties file in a different directory, change the JVMPROPS option on all the relevant JVM profiles to state the new path name for the file. Also ensure that CICS has read and execute access on HFS for your JVM properties file and the directory containing it. Giving CICS regions permission to access HFS directories and files tells you how to do this.

Now that you have customized the JVM profiles or JVM properties files, if you have specific applications (standard Java programs, CORBA stateless objects or enterprise beans) to run, Enabling applications to use a JVM tells you how to set up applications to use a JVM profile, and how to add the classes for the application to the class paths. If you are following a procedure to set up IIOP support or support for enterprise beans, and you do not yet have any specific applications to run, you can return to the procedure Setting up the host system for IIOP or Setting up an EJB server.