Start of change

Configuring the SOAP Gateway installation properties file

Modify the installVars.properties file to specify the variable values for installing, configuring, and starting SOAP Gateway if you are installing all three SOAP Gateway components on one mount point.

  • Determine the disk space that you need based on the number of web services you plan to host, your trace level setting for logging, and whether transaction logging must be enabled. For more information, see Configuration and setup planning.
  • IMS Enterprise Suite Base Services (HAHF320) and SOAP Gateway (JAHF321) must be already processed by SMP/E.
  • IBM® Installation Manager V 1.8.3 or later is installed on the target system where SOAP Gateway is installed.
  • The Installation Manager IBM Installation Manager instance must be able to access the file system where the SOAP Gateway repository file is located.
After the SMP/E processing of the IMS Enterprise Suite Base Services FMID, the following files are located in the /usr/lpp/ims/imses/V3R2/soap_gateway_sample_jcl/ directory:
  • installVars.properties
  • SGWInstall.jar

All the variables are described in the properties file, with the JCL jobs or procedure that use these values described in the comments. The generated jobs, by default, are stored in the /usr/lpp/ims/imses/V3R2/soap_gateway_sample_jcl directory. A variable is provided for you to specify a different data set to store a copy.

The following sample jobs and configuration member are provided to assist your configuration and installation of SOAP Gateway by using the IBM Installation Manager command line.
Table 1. Sample installation jobs to install SOAP Gateway
Job name Data set Description
AEWAINST AAEWSAMP Sample job to run the SGWInstall.jar file that generates a copy of the JCL jobs and procedure based on the values in installVars.properties.
AEWTSCFS AAEWBASE Sample job to create the file system, HFS or zFS, for installing SOAP Gateway on one mount point.
AEWTSINS AAEWBASE Sample job to install SOAP Gateway using the Installation Manager. You must modify the sample job to install the three SOAP Gateway packages in three separate imcl -install commands.
AEWTSUNI AAEWBASE Sample job to uninstall SOAP Gateway. You must modify the sample job to uninstall the three SOAP Gateway packages in separate imcl -uninstall commands.
Table 2. Sample runtime and configuration jobs in the AAEWSAMP data set for SOAP Gateway
Job name Description
AEWIOGCF Sample configuration member that specifies the SOAP Gateway server runtime settings.
AEWIOGBP Sample job to execute SOAP Gateway management utility commands from BPXBATCH and to configure the IBM Java™ SDK location.
AEWIOGPR Sample job to start the SOAP Gateway server.
AEWPOSIN Sample job to specify the configuration information for the locations of the following components: imsserver, imsbase, imssoap, and Java.

Take the following steps:

  1. Make a copy of the installVars.properties file as a backup.
  2. Open the installVars.properties file for editing.
  3. Identify the appropriate values for the following variables:
    Start of change
    Table 3. Variables to be specified
    Variables Description
    HOST, USER, PASSWD The host system where the generated copy of the JCL jobs is to be transferred to. A user ID and its password are required.

    The script generates a new copy of the JCL jobs at each run. It does not overwrite the original copy.

    Jobcard information Standard JOBCARD information for submitting and running a job.
    Location to mount the file system for SOAP Gateway:
    • SGDataSet: The HFS that SOAP Gateway is to be installed to
    • tvolfs: The volume serial (volser) to be used for the target file system
    • SGMountPoint: The mountpoint for the SOAP Gateway file system
    • SGOwner: The SAF user ID that owns files in this package group. This user ID is usually the same user ID and group that owns the Installation Manager instance to which the package group belongs.
    • SGGroup: The SAF group that owns files in this package group. This group is usually the same user group that owns the Installation Manager instance to which the package group belongs.
    This information is used by AEWTSCFS to allocate and mount the file system for SOAP Gateway. The SGMountPoint info is also used by AEWTSINS
    Installation repository information:
    • repoPath: The path for the IBM Installation Manager repository
    • repoName: The name of the SOAP Gateway repository file
    • IMPathPrefix: The path for IBM Installation Manager binaries
    • sharedResourcesDir: The path for the IBM Installation Manager shared resources directory
    This information is used by AEWTSINS and AEWTSUNI that call the IBM Installation Manager command line to install and uninstall SOAP Gateway..
    SOAP Gateway components and Java location:
    • imsserverPathPrefix
    • imsbasePathPrefix
    • imssoapPathPrefix
    • javaPath
    The path prefix for where each of the three SOAP Gateway components and IBM Java are to be installed.

    This information is used by AEWTSINS, AEWIOGCF, and AEWPOSIN.

    Java information for running the SOAP Gateway management utility:
    • jarch: Java architecture level
    • LoadModName: Java load module name
    This information is used by AEWIOGBP to run the SOAP Gateway management utility commands from BPXBATCH.

    Set the Java architecture to J7.0 for 31 bit, or J7.0_64 for 64 bit. Set the load module to JVMLDM70 for 31 bit, and JVMLDM76 for 64 bit.

    • hlqualBase: The high-level qualifier for the data set that contains the AEWIOGCF configuration member
    • hlqualJava: The high-level qualifier for the data set that contains IBM Java.
    This information is used by AEWIOGPR, the procedure to start or shut down the SOAP Gateway server.
    Data set to upload the generated JCL jobs:
    • uploadJCLs: true to upload the generated jobs to the specified data set
    • hlqualJava: The data set to store a copy of the generated jobs.
    This information is used by the SGWInstall.jar program to upload the generated jobs.
    By default, the generated jobs are stored in the same location as the SGWInstall.jar file. To save a copy in a different location:
    1. Set uploadJCLs to true.
    2. Specify the data set value for INSTDATASET.
    End of change
  4. Save your changes.
Run the installation job generation script to generate the SOAP Gateway installation and configuration jobs.
End of change