IMS Enterprise Suite Version 2.2 SOAP Gateway README

Product readme


Abstract

This readme file contains a list of known issues and workarounds for IBM® IMS™ Enterprise Suite Version 2.2 SOAP Gateway, for both z/OS® and distributed platforms.

Content

Last update: March, 2014

This document contains the latest information about known issues, workarounds, changed product behavior, and updates for IBM IMS Enterprise Suite Version 2.2 SOAP Gateway. Use this document to help you determine if there are pre-installation or post-installation steps that you need to be aware of before the installation.

This document supplements the IMS Enterprise Suite V2.2 SOAP Gateway information in the IBM Information management Software for z/OS Solutions Information Center.

Fixes and enhancements for SOAP Gateway are made available as Authorized Program Analysis Reports (APARs) for z/OS systems. Fixes and enhancements for distributed systems are available for download.



Contents


Cumulative list of fixes and updates

V2.2.0.3 fixes and updates

V2.2.0.3 is equivalent to APAR PI11108 for the z/OS platform. APARs PI10937, PI10940, PI10942 and PI11338 for IMS Enterprise Suite V2.2 Base Services are required for the updated version of IBM SDK Java™ Technology Edition, Version 7.
  • V2.2.0.3 contains the following fix:
    Deploying a business event service failed with the following error:
    IOGD0705E: The deploy command failed with the following reason: null.

    This issue is addressed.

Important: To APPLY the service PI11108 successfully, the target library must have 100 cylinders available, and distribution library must have 50 cylinders available.


V2.2.0.2 fixes and updates

V2.2.0.2 is equivalent to APARs PM88068, PM86769, PM88962, and PM86773 for the z/OS platform. An updated version of IBM Java SDK V7 is provided, and an internal issue is addressed.

Important: To APPLY the services PM86769 and PM88962 successfully, the SMPPTS data set must have at least 260 cylinders free. To APPLY the service PM86773, the SMPPTS data set must have at least 45 cylinders free.




V2.2.0.1 fixes and updates

V2.2.0.1 is equivalent to APAR PM78757 for the z/OS platform. V2.2.0.1 contains the following fixes and updates:
  1. In V2.2, the SOAP Gateway management utility iogmgmt -migrate command cannot migrate correlator files that have more than 4 entries (roughly larger than 4KB).

    This issue is addressed in V2.2.0.1. Note that if the target SOAP Gateway server was running during the migration, the target server must be restarted.

  2. In V2.2, when the operation name of a correlator entry is a subset of another operation name, deployment of the web service fails, with the following error message:
    IOGD0705E: The deploy command failed with the following reason: IOGX0012W: The correlator (path_to_the_correlator_file) cannot be stored in the cache because the operation is already associated with the (path_to_the_associated_wsdl_file) file.

    In the following example:
    <correlatorEntry operationName="RetrieveAgentIdsForDelegate"
    portName="RetrieveAgentIdsForDelegatePort"
    serviceName="RetrieveAgentIdsForDelegateService">
    <correlatorEntry operationName="RetrieveAgentIds"
    portName="RetrieveAgentIdPort"
    serviceName="RetrieveAgentIdService">
    The second web service RetrieveAgentIdService, when deployed, would receive an error.

    This issue is fixed in V2.2.0.1.

  3. In V2.2, no error message is provided when the iogmgmt -migrate command is incorrectly issued without an argument.

    In V2.2.0.1, a new message, IOG00031E, is added and issued in this case:

    IOG00031E = IOG00031E: The -migrate command requires one argument. Specify either the correlator keyword for correlator migration, or the source SOAP Gateway installation location for server and web services migration.

  4. In V2.2, the iogmgmt -view -sgp command does not show the shutdown port for Windows and Linux on System z platforms.

    This issue has been addressed in V2.2.0.1, and the shutdown port information is now provided through this command on all supported platforms.

  5. In V2.2, after a new installation of SOAP Gateway, setting the Java directory or running a management utility command on the z/OS platform generates several EDC5129I errors (No such file or directory) from the installation script that looks as follows:

    + grep ?SG_LOG_FILE_DIR = C\:\Documents and Settings\user1\test\imsbase
    /conf/native.env.properties
    + sed s%SG_LOG_FILE_DIR =\(.*\)%\1%
    grep: FSUM6003 input file "C\:\Documents": EDC5129I No such file or directory.
    grep: FSUM6003 input file "and": EDC5129I No such file or directory.
    grep: FSUM6003 input file "Settings\user1\Desktop\test\imsbase/conf/native.en
    v.properties": EDC5129I No such file or directory.
    ...

    This issue indicates that either the imssoap or imsbase component is not installed correctly.

    This issue is addressed in V2.2.0.1. In addition, two new messages are provided to better identify the cause:
    • IOG00029E: The SOAP Gateway imsbase directory is not found based on the current setting: SG_BASE_DIR=imsbase_dir. The imsbase directory might have been deleted or altered. Correct the directory name, or reinstall SOAP Gateway.
    • IOG00030E = IOG00030E: The SOAP Gateway imssoap directory is not found based on the current setting: SG_SOAP_DIR=imssoap_dir. The imssoap directory might have been deleted or altered. Correct the directory name, or reinstall SOAP Gateway.

  6. In V2.2, if the imsserver component installation directory is configured as read-only, you will not be able to run the -iogmgmt -migrate correlator command to migrate correlator files in the v2.2_install_dir/imsserver/tools/migration/xml directory. You must change the directory access permission to read/write mode before you migrate the correlator files.

    In V2.2.0.1, the migration utility now backs up the XML directory into the imssoap component directory (imssoap/tools/migration/xml) rather than in the imsserver component directory. The imssoap component directory is required to be always in read/write mode, and there is no longer the need to change the access permission for the imsserver component.

  7. In V2.2, for the provider scenario, invoking a web service with a SAML signed token of the Trust One trust type (SAML11SignedTokenTrustOne or SAML20SignedTokenTrustOne) using the PKCS12 security type resulted in a CWWSS6521E error message:
    CWWSS6521E: The Login failed because of an exception: javax.security.auth.login.LoginException: PKIXCertPathBuilderImpl could not build a valid CertPath.: java.security.cert.CertPathValidatorException: The revocation status of the certificate with subject (CN=XXXXXXX, OU=XXXXXXX, O=XXXXXXX, L=XXXXX, ST=XXXXXXX, C=XX) could not be determined.

    This issue has been fixed in V2.2.0.1.

  8. In V2.2, running the migration tool (iogmgmt -migrate V2.1_install_dir command to migrate server properties and web services from V2.1 to V2.2 also migrates the log file location, which results in writing V2.2 log entries to the V2.1 log file.

    This issue is addressed in V2.2.0.1. To prevent from incorrectly writing to the V2.1 log file, the migration tool no longer migrates the log file location and the associated trace level setting. You must manually customize the log file location and trace level setting by using the SOAP Gateway management utility, or the default values for the log file location and trace level are used.

  9. In V2.2, the soapLogDelete.sh script shipped in install_dir/imsserver/tools is not updated for the V2.2 installation path. You get an error indicating the path does not exist or the file is not found.

    This issue is corrected in V2.2.0.1.

  10. In V2.2, the last sentence in message IOGD0113I about no action is required is confusing. It contradicts with the main message "The changes will be reflected in the runtime configuration of the server after the next time that the SOAP Gateway server starts."

    This last sentence is removed in V2.2.0.1.

  11. In V2.2, the purged idle connections information is viewable with the iogmgmt -view -cp command. However, the properties pertaining to idle connection cleanup are related to the server, not just for the callout scenario.

    Starting V2.2.0.1, the purged idle connections information is now viewable with the iogmgmt -view -sgp command.

  12. In V2.2, the IOG30013I message ("The SOAP Gateway Windows Service IMSSOAPGateway is now up and running") that is issued as a result of checking the Windows service status with the iogmgmt -service -status command can be confusing.

    In V2.2.0.1, a new message is created and issued as a result of the Windows service status check:
    IOG30024I: The SOAP Gateway Windows Service IMSSOAPGateway is up and running.

  13. In V2.2, when the iogmgmt -tranLog command is issued in the wrong cases, the error message does not explain that the command is case-sensitive and what the correct command is.

    In V2.2.0.1, a new message IOGD0025E is added when the iogmgmt -tranLog command is issued in the wrong cases:
    IOGD0025E: The incorrect_cases command is not valid. The valid command is -tranLog and is case sensitive.

  14. After installing V2.2, running the iogmgmt -migrate /path/to/source command to migrate web services and server properties would also automatically deploy migrated web services. When a migrated web service is enabled with web services security with any supported token types, the next service deployed, if it is a non-secure web service, is incorrectly populated with the same security token type as the previous secure web service.

    This issue has been addressed in V2.2.0.1.



V2.2 fixes and updates
  • PMR 50267,019,866: In V2.1, the -iogmgmt -stop -force command on the Linux™ on System z® platform unnecessarily shows the stack trace.

    This issue is addressed in V2.2. Stack trace is no longer showing with this command on the impacted platform.


Known issues and workarounds:
  1. Issue: If you are on V2.1 SOAP Gateway, after installing V2.2 and running the SOAP Gateway migration utility to migrate server properties and services, a warning might occur when you start up the server:
    WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'maxSpareThreads' to '75' did not find a matching property.

    Explanation: This property is no longer supported in the new version of the underlying Apache Tomcat server in V2.2 SOAP Gateway.

    Solution: If you encounter this warning, remove the maxSpareThreads property from server.xml and restart the server.
  2. Issue: When the Application Transparent Transport Layer Security (AT-TLS) feature in IBM® z/OS Communications Server is used to manage secured connections to IBM IMS™ Enterprise Suite SOAP Gateway, you get "Connection Interrupted" instead of a list of web services when viewing deployed web services in the SOAP Gateway administrative console.

    Workaround: Modify the httpbase.jsp file in install_dir/imsserver/server/webapps/imssoap/axis2-web/include/ to explicitly set the scheme to HTTPS. See the technote at http://www.ibm.com/support/docview.wss?uid=swg27024607 for details.

  3. Issue: On Windows platforms, after the SOAP Gateway code is successfully installed, further installation as a Windows service or starting the server as a Windows service results in an IOG000024E (the service failed to install) or IOG00026E (Windows service failed to start) error.

    Explanation: The user installing or starting the SOAP Gateway server as a Windows service is not an administrator. This issue is most likely to happen on the Windows 7 platform because of its enhanced security to keep non-system related files to run in a restricted mode.

    Solution: Add the user responsible for installing and starting the SOAP Gateway server as a Windows service to the administrators' group. Alternatively, a non-administrator user can start the server as an administrator by selecting Start > All Programs > IBM IMS Enterprise Suite V2.2 > SOAP Gateway > Management Utility > Run as administrator, and then issue the command:
    iogmgmt -service -start

  4. Issue: Stopping callout threads takes a long time and the thread pool doesn't stop in the pre-defined 5 minutes.

    Workaround: If for any reason, the thread pool does not stop gracefully, you can restart the SOAP Gateway server to restart the callout threads. However, after the restart, the first synchronous callout request on each tpipe to SOAP Gateway is returned to OTMA with a NAK response. Subsequent synchronous callout requests are processed normally.

  5. Issue: SOAP Gateway does not support passing of timestamp information in the response messages for web services security if the IncludeTimestamp element is included in the server policy file.

    Workaround:
    You must modify your client applications or client policy files to not send the timestamp element in the request. Do not add the includeTimestamp element back to the server policy file.

  6. Issue: For installation on the z/OS platform, the recommended code page is CP1047. For systems with other code pages, some characters in the installation sample jobs, such as \, ^, ~, !, [, ], {, }, #, |, `, $, and @ in AEWIOGBP, might be interpreted differently.

    Workaround: Change the following statements in AEWIOGBP:
    CMD[0]="iogmgmt -prop -u -java -h $IOGJH";+
    CMD[1]="iogmgmt -view -java -h";+
    CMD[2]="iogmgmt -view -sgp";+
    for _CMD in "${CMD[@]}"; +
    do $MGM/$_CMD >>$OUT 2>>ERR;+
    done


    into 3 single calls:
    $MGM/iogmgmt -prop -u -java -h $IOGJH
    $MGM/iogmgmt -view -java -h
    $MGM/iogmgmt -view -sgp


  7. Issue: The migration utility does not prevent users from setting a shutdown port to port 0. Port 0 is reserved and should not be allowed. Valid port values should be 1 - 65535.

    Workaround: Ensure that you set the shutdown port to a valid value.

  8. Issue: If a custom fault message is configured and an error occurs, the error message provided by SOAP Gateway incorrectly includes the name of the XML converter for processing the requests rather than the name of the converter for the fault message, causing confusion about the root cause of the problem. When a custom fault message is configured and an error during request processing occurs, the XML converter for request processing would call the fault converter. When such an error occurs, SOAP Gateway reports the incorrect converter name.

    Workaround: If you are getting an error message reporting issues with a converter and you have custom SOAP fault messages, check the IMS Connect console message for HWSA0380E to identify the actual converter that caused the failure.

  9. Issue: If you undeploy a service while the server is down, you get an incorrect, partial error message:
    "Unable to connect to the runtime server (EDC8128I Connection refused.)" instead of the IOGD0751W message, which says "The undeploy command successfully removed the service associated with correlator_file_name from the SOAP Gateway master configuration. However, it encountered the following error(s): Unable to connect to the runtime server EDC8128I Connection refused.)."

    Workaround: The service is already removed, so if the server is stopped, no action is required. If the server is started when you encountered this error, restart the server.
  10. Issue: When a callout service with callout WS-Security is deployed while the server is up, the iogmgmt -view -cf correlator_filename command does not reflect the callout WS-Security type.

    IOGD0301I: List of correlator entries from correlator file (filename.xml) in the runtime configuration:

    Correlator Type: Callout
    Service name: HELLOService
    Operation name: HelloOperation
    XML adapter type: IBM XML Adapter
    Converter name: HELLOD
    Transaction code:
    Callout connection bundle name: cb_callout
    Socket timeout: 0
    Execution timeout: 0
    Callout web services timeout: 7500
    Connection bundle: null
    Callout WS-Security Type:

    Workaround: Restart the server, and the Callout WS-Security Type will be reflected with the callout WS-Security token type information.

    Correlator Type: Callout
    Service name: HELLOService
    Operation name: HelloOperation
    XML adapter type: IBM XML Adapter
    Converter name: HELLOD
    Transaction code:
    Callout connection bundle name: cb_callout
    Socket timeout: 0
    Execution timeout: 0
    Callout web services timeout: 7500
    Connection bundle:
    Callout WS-Security Type: SAML20Token



Installation and potential migration tasks

Upgrading from V2.2 to the latest maintenance release

Because each maintenance release might update only one or two of the three SOAP Gateway installation components, previous maintenance versions are required before you can install the latest version.
  • V2.2.0.1 updates the IMSSERVER and IMSSOAP components.
  • V2.2.0.2 updates the IMSSERVER component and the IBM Java SDK.
  • V2.2.0.3 updates the IMSSERVER component and the IBM Java SDK

On the distributed platforms, you must be on the previous maintenance version, or the repository files for all previous maintenance releases must be stored in the same IBM Installation Manager repository location. Then use Update function in IBM Installation Manager to install the latest maintenance.

If you install the updated Java in a location other than the default location, after installation, you must use the SOAP Gateway management utility to specify the Java location.
  1. Go to the location of the SOAP Gateway management utility at <install_dir>\imsserver\deploy. For example:
    cd C:\Program Files\IBM\IMS Enterprise Suite V2.2\SOAP Gateway\imsserver\deploy
  2. Issue the following command to specify the Java location. For example:
    iogmgmt -prop -u -java -h C:\Program Files\IBM\IMS Enterprise Suite V2.2\SOAP Gateway\java

On z/OS, after applying the PTFs, modify the AEWTSGIN sample job to point to the new repository.

In AEWTSGIN:
  1. Change the line that contains the repository name to point to the new repository file:
    export repository="$RepoPath/IMSES_SOAPGateway_zOS_V2.2.0.x.zip";
    where x is the maintenance level.
  2. If you are currently on V2.2.0.1 or V2.2.0.2, comment out the lines for $CMD1 and $CMD2, which are used to install the IMSBASE and IMSSOAP components. This maintenance release contains no updates to the IMSBASE or IMSSOAP components, so you do not need to reinstall it. To comment out $CMD1 and $CMD2, prepend "//*" as follows:
    //* $CMD1;
    //* $CMD2;
  3. In you are still on V2.2.0.0, comment out the line for $CMD1, which is used to install the IMSBASE component. This maintenance releases contain no updates to the IMSBASE component, so you do not need to reinstall it. To comment out $CMD1, prepend "//*" as follows:
    //* $CMD1;
  4. Submit the AEWTSGIN installation job.

If you use the silent installation approach:
  1. Modify the following line in IMSES22SOAPConfig.dtd to point to the 2.2.0.x repository file:
    <!ENTITY repolocation "Path to the SOAP Gateway Repository here">
  2. To upgrade from V2.2.0.1 or V2.2.0.2 to V2.2.0.3, modify IMSES22SOAPResponseFile.xml by commenting out the following two lines for the IMSBASE and IMSSOAP components and for Java. The V2.2.0.3 maintenance does not impact the IMSBASE and IMSSOAP components.
    <!--
    <offering id='com.ibm.im.ims.soap.gateway.imsbase' profile='&imsbaseProfile;' features='com.ibm.im.ims.soap.gateway.imsbase' installFixes='none'/ -->

    <!--
    offering id='com.ibm.im.ims.soap.gateway.imssoap' profile='&imssoapProfile;' features='com.ibm.im.ims.soap.gateway.imssoap' installFixes='none'/ -->

  3. If you are still on V2.2.0.0, upgrade to the latest version by modifying IMSES22SOAPResponseFile.xml and commenting out the following two lines for the IMSBASE component and for Java. None of the maintenance releases impact the IMSBASE component.
    <!--
    <offering id='com.ibm.im.ims.soap.gateway.imsbase' profile='&imsbaseProfile;' features='com.ibm.im.ims.soap.gateway.imsbase' installFixes='none'/>

    <offering id='com.ibm.im.ims.soap.gateway.java.sdk' profile='&javaProfile;' features='javasdk' installFixes='none'/>
    -->


  4. Ensure the IMSES22SOAPConfig.dtd and IMSES22SOAPResponseFile.xml files are stored in the InstallationManager_dir\eclipse\tools directory.
  5. Run the imcl command to install:
    imcl input IMSES22SOAPResponseFile.xml -acceptLicense
  6. Important: If you install the updated version of the IBM Java SDK, the Java location would be different. You must specify the Java SDK location after the installation by using the SOAP Gateway management utility.
    1. Go to the location of the SOAP Gateway management utility at <install_dir>/imsserver/deploy.
    2. Issue the following command to specify the Java location. For example:
      iogmgmt -prop -u -java -h -PathPrefix-/usr/lpp/ims/imses/V2R2/java170/SRx/FPx/IBM/

The current data or configuration will not be overwritten. In the IMSSERVER component, configuration files are backed up when the updated files are laid down by Installation Manager. After the updates are applied, the configuration files are restored.

Any files that are not installed by IBM Installation Manager are not touched. Therefore, any web service artifacts or other files that were added post installation will remain.


New installation

For fresh installation, see the installation roadmaps in the information center for planning and installation instructions for your platform and installation scenario.
Installation of V2.2.0.3 maintenance requires the V2.2.0.0 base code, V2.2.0.1, and V2.2.0.2. You can install the base code and the maintenance codes at the same time by adding the repository files for the base code and the maintenance codes to the IBM Installation Manager repository locations and click Install.

For z/OS, in AEWTSGIN:
  1. Under the line that lists the repository location, add another line for the additional repository file:
    export repository="$RepoPath/IMSES_SOAPGateway_zOS_V2.2.0.zip";
    export repository="$RepoPath/IMSES_SOAPGateway_zOS_V2.2.0.1.zip";
    export repository="$RepoPath/IMSES_SOAPGateway_zOS_V2.2.0.2.zip";
    export repository="$RepoPath/IMSES_SOAPGateway_zOS_V2.2.0.3.zip";
  2. Submit the AEWTSGIN installation job.

If you use the silent installation approach:
  1. Add another repository location to the following line in IMSES22SOAPConfig.dtd to point to the 2.2.0.3 repository file:
    <!ENTITY repolocation "Path to the SOAP Gateway Repository here">
    <!ENTITY repolocation2 "Path to the SOAP Gateway Maintenance Repository here">
    For example:
    <!ENTITY repolocation "/u/usr01/imses22repo/IMSES_SOAPGateway_zOS_V2.2.0.zip">
    <!ENTITY repolocation2 "/u/usr01/imses22repo/IMSES_SOAPGateway_zOS_V2.2.0.1.zip">
    <!ENTITY repolocation3 "/u/usr01/imses22repo/IMSES_SOAPGateway_zOS_V2.2.0.2.zip">
    <!ENTITY repolocation4 "/u/usr01/imses22repo/IMSES_SOAPGateway_zOS_V2.2.0.3.zip">
  2. In IMSES22SOAPResponseFile.xml, under another repository location:
    <repository location='&repolocation;'/>
    <repository location='&repolocation2;'/>
    <repository location='&repolocation3;'/>
    <repository location='&repolocation4;'/>
  3. Ensure these two files are stored in the InstallationManager_dir\eclipse\tools directory.
  4. Run the imcl command to install:
    imcl input IMSES22SOAPResponseFile.xml -acceptLicense

Potential migration tasks :
  1. Starting V2.2.0.1, the SOAP Gateway migration tool ( iogmgmt -migrate source_install_dir ) no longer retains the log file location and trace level setting from V2.1. This behavior prevents V2.2 information from being appended to the V2.1 log file. You must explicitly change the default log file location and trace level by using the SOAP Gateway management utility. To change the log file location, for example:
    iogmgmt -prop -u -f absolute_path_to_the_directory
    If you are upgrading from V2.2.0.x, or using the iogmgmt -migrate path_to_source_install_dir command to clone additional instances of the V2..2 servers, the migration tool will migrate the log file location and trace level setting.

  2. Starting V2.2.0.1, the IncludeTimestamp element is removed from the web services security policy file. This change would impact your existing web service clients. Previously, this element was included in the policy file and a timestamp was needed only for request messages. In V2.2.0.1, this element is removed.

    However, the SOAP Gateway migration tool would copy the includeTimestamp attribute from 2.1 back to the server policy file. If you are using the WS-Security feature, you must manually remove this element. If the IncludeTimestamp element exists, then a timestamp is required for both the request and the response messages. Because SOAP Gateway does not support passing of the timestamp element in the response message, you would encounter the following error message:

    CWWSS5730E: A required timestamp is not found.
    You must modify your client accordingly.
  3. The SAML token type for web services with WS-Security enabled might not get migrated from 2.2.0.1. Check the correlator files for web services that have WS-Security enabled, and update the correlator files with the SAML token type information. If the SOAP Gateway server is already running, restart the server for the changes to take effect.
If you are upgrading from V2.1, see the Migrating from IMS Enterprise Suite Version 2.1 SOAP Gateway topic for more general migration information.


Rollback

If situations arise that, after upgrading, you need to back out of the update, you can use the rollback feature in IBM Installation Manager.

When you install the upgrade, IBM Installation Manager makes a backup copy of your resources. When you roll back a package, Installation Manager uninstalls the updated resources, and reinstalls the resources from the previous version. You can roll back only one version level. The rollback feature requires that you do not alter or move the IBM Installation Manager backup directory.

To roll back an updated package:
  1. In Installation Manager, click Roll Back to start the Roll Back wizard.
  2. From the Package Group Name list, select the package group that contains the packages that you want to roll back. Click Next.
  3. Select the version of the package that you want to roll back to. Click Next.
  4. Read the summary information and click Roll Back to roll back the package.

You might need to reset your Java location by using the SOAP Gateway management utility after the rollback.

Rolling back by using the response file
To roll back using the response file, you specify the offering that is being rolled back. You must delete or comment out the other offerings.

V2.2.0.3 updates the IMSSERVER component and the Java SDK. Here is an example of how you can modify the IMSES22SOAPResponseFile.xml file to roll back to 2.2.0.2:

1. Specify the offerings (IMSSERVER and Java) to roll back to using the <rollback> tag. Comment out or delete the other ones.
    By default, the response file contains the <install> tag. You can replace the "install" keywords with "rollback" (make sure you keep a copy of your original response file for future installation or updates).
    In the offering tags of the components to roll back, the "features" and "installFixes" attributes must be removed. In the following example, the IMSSERVER and Java components are being rolled back so they have these attributes removed. The offerings that will not be rolled back must be commented out. Below, the IMSBASE and IMSSOAP components are commented out because they will not be rolled back.
    <rollback>
    <offering id='com.ibm.im.ims.soap.gateway.imsserver' profile='&imsserverProfile;' />
    <!-- offering id='com.ibm.im.ims.soap.gateway.imsbase'
    profile='&imsbaseProfile;' features='com.ibm.im.ims.soap.gateway.imsbase' installFixes='none'/> -->
    <!-- offering id='com.ibm.im.ims.soap.gateway.imssoap'
    profile='&imssoapProfile;' features='com.ibm.im.ims.soap.gateway.imssoap' installFixes='none'/> -->
    <offering id='com.ibm.im.ims.soap.gateway.java.sdk' profile='&javaProfile;' />
    </rollback>
2. Comment out the corresponding profiles (IMSBASE and IMSSOAP) that you are not rolling back:
    <profile id='&imsserverProfile;' installLocation='&imsserverpath;'>
    <data key='eclipseLocation' value='&imsserverpath;'/>
    <data key='user.import.profile' value='false'/>
    &sysconfig;
    </profile>
    <!-- <profile id='&imsbaseProfile;' installLocation='&imsbasepath;'> -->
    <!-- <data key='eclipseLocation' value='&imsbasepath;'/> -->
    <!-- <data key='user.import.profile' value='false'/> -->
    <!-- &sysconfig; -->
    <!-- </profile> -->
    <!-- <profile id='&imssoapProfile;' installLocation='&imssoappath;'> -->
    <!-- <data key='eclipseLocation' value='&imssoappath;'/> -->
    <!-- <data key='user.import.profile' value='false'/> -->
    <!-- &sysconfig; -->
    <!-- </profile> -->
    <profile id='&javaProfile;' installLocation='&javapath;'>
    <data key='eclipseLocation' value='&javapath;'/>
    <data key='user.import.profile' value='false'/>
    &sysconfig;
    </profile>

Notes:
  1. If you are rolling back Java from the update, you need to reset the Java location by using the SOAP Gateway management utility.
  2. If you did not install the updated Java, then you only need to roll back the IMSSERVER component.


Contacting IBM software support

Contact IBM software support at: http://www.ibm.com/support/entry/portal/Overview/Software/Information_Management/IMS_Enterprise_Suite



Notices and trademarks

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
UNIX® is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.


Third Party Notices

The Program may include third party code that IBM, not the third party, licenses to Licensee under this Agreement. Notices, if any, for the third party code ("Third Party Notices") are included for Licensee's information only. These notices can be found in the Program's NOTICES file(s). Information on how to obtain source code for certain third party code can be found in the Third Party Notices. If in the Third Party Notices IBM identifies third party code as "Modifiable Third Party Code," IBM authorizes Licensee to 1) modify the Modifiable Third Party Code and 2) reverse engineer the Program modules that directly interface with the Modifiable Third Party Code provided that it is only for the purpose of debugging Licensee's modifications to such third party code. IBM's service and support obligations, if any, apply only to the unmodified Program.

(c) Copyright IBM Corporation 2012, 2013. All Rights Reserved.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IMS Enterprise Suite
SOAP Gateway

Software version:

2.2

Operating system(s):

Linux on System z, Windows, z/OS

Reference #:

7027299

Modified date:

2014-03-07

Translate my page

Machine Translation

Content navigation