Release Notes for SPE for z/OS, V. 8.5.1

Content

=====================================================================
CONTENTS
=====================================================================

1. About this release
2. Installation and configuration information
3. Upgrade and migration information
4. Known limitations, problems, and workarounds
5. New and changed behavior
6. Contacting customer support
7. Notices and trademarks

=====================================================================
1. ABOUT THIS RELEASE
=====================================================================

Where to find the software to download

To download the software for SPE for Healthcare Payer for z/OS v8.5.1 and SPE for Supply Chain EDI for z/OS v8.5.1, go to Passport Advantage® Online.

Documentation notes

Online documentation is provided for the product in the IBM Knowledge Center. Installation procedures that are specific to z/OS installations are located in the Program Directory.

Translated documentation
Based upon country requests, the online product documentation has been translated from the original English (United States) version into various native languages.

See the English documentation for the most recent documentation.

Inquiries about translating documents into specific languages should be directed to an IBM representative of the respective country.

Back to top

=====================================================================

2. INSTALLATION AND CONFIGURATION INFORMATION
====================================================================

Installation prerequisites

You can install IBM Standards Processing Engine portfolio products on any supported version of the z/OS platform. Both SPE for Healthcare Payer for z/OS V.8.5.1 and SPE for Supply Chain EDI for z/OS V.8.5.1 are included in a single installer.

The Standards Processing Engine for z/OS products include components that run on z/OS, and components that run on distributed platforms such as Windows and UNIX. The SPE runtime server components are installed and run on z/OS. The instructions below describe the installation process for the SPE runtime components on z/OS.

The SPE Trading Partner User Interface can be installed on either Windows or UNIX. The SPE Design components and SPE Packs are installed on Windows only. For more information on installing the SPE Trading Partner User Interface and the SPE Design components, see the installation procedure in the IBM Knowledge Center.

SPE for z/OS requires a database, which is installed separately. Supported databases include IBM DB2 Advanced Enterprise Server Edition and Apache Derby. DB2 is recommended for production environments. Apache Derby can be used for development and test environments, and can be downloaded from http://db.apache.org/derby/.

z/OS installation

To install Standards Processing Engine on the z/OS platform:

1. Install the Standards Processing Engine common components on z/OS as described in the Program Directory for your solution: GI13-3433-01 - IBM Standards Processing Engine for Healthcare Payer for z/OS or
   GI13-3434-01 - IBM Standards Processing Engine for Supply Chain EDI for z/OS.
2. Update the database configuration to use your preferred database.
   
   By default, the database settings use the SPE Derby database, an Apache Derby database. To use a different database for production, update the database configuration to use your preferred database.
3. Deploy your industry pack from the Windows system where it is installed to the z/OS server. See the installation procedure in the IBM Knowledge Center.

SPE with IBM Integration Bus
To run SPE with IBM Integration Bus on the z/OS platform, you must set the environment variables that are required by the IBM Integration Bus plugin. This is done by registering the SPE profile with the IBM Integration Bus.

To register the SPE profile:

1. Append the following line to the end of the BIPBPROF profile member located in the PDSE for the brokers:
   . /spe_install_dir/IIB/runtime/speiib_200.sh
   
   where
   
   spe_install_dir is your SPE installation directory
   Requirement: The command must start with the period, space, forward slash (. /) characters.
2. Run the BIPGEN JCL that is located in the PDSE for the brokers to recreate the ENVFILE environment file. The BIPGEN JCL invokes the shell script that you added to the BIPBPROF profile member in step 1, which sets the required environment variables.
   
   For information on editing the BIPBPROF member and running the BIPGEN JCL, see Creating the environment file or the overview topic Creating a broker on z/OS in the IBM Integration Bus information center.

After starting IBM Integration Bus, look at the broker admin agent log. (For the location of this log, see the Standard system logs article in the IBM Integration Bus information center.) If a "Failed to instantiate SLF4J LoggerFactory" exception appears, see Technote 1663931 .

If IBM Integration Bus runs on a different user ID than the ID under which SPE was installed, you might see errors in the integration log that write permissions to the spe_storage, tmp, and txcache directories are denied. To resolve the errors, change the permissions to give the IIB ID write permissions for those directories.

Back to top

=====================================================================

3. UPGRADE AND MIGRATION INFORMATION
=====================================================================

For upgrade or migration procedures, contact Customer Support.

Back to top

=====================================================================

4. KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
=====================================================================
[SPE Console window menu item is missing from Start menu if prior SPE version is present]

Issue: On the Windows 2012 operating system, the SPE Console window Start menu item is not visible for a new SPE 2.0.1.0 installation if a prior version of SPE is already installed.

Details: On a Windows 2012 system with SPE 2.0.0.1 already installed, all Start menu items display correctly. SPE 2.0.1.0 is then installed successfully and the new directory structure (C:\IBM\Standards Processing Engine 2.0.1) is visible. However, when the new application is started, the “SPE Console window” item is missing on the Start menu "IBM Standards Processing Engine 2.0.1" group.

Workaround:

1. Browse to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\IBM Standards Processing Engine 2.0.1 (or to the specified program folder).
2. Right-click on SPE Console window and click on Pin to Start.
3. Search for applications that start with "SPE," and verify that the SPE Console window shortcut is displayed.

Alternately, you can start the SPE console manually from a command line: start a cmd window and run the command speconsolestart.bat from the bin directory of your new SPE install.

[Transformation correlations are not captured during X12 outbound processing]

Issue: You specified a map in your outbound ST envelope that creates correlations, but you do not see correlation data in the response.

Workaround: Contact Customer Support for a patch. Alternately, you can run the map as a separate step prior to running the enveloping step. This allows you to capture the correlations in a transform step and later associate them with the document that is returned from the enveloping step.

[Single sign on to SPE does not work from Sterling B2B Integrator over TLS 1.2 in NIST STRICT mode]

Issue: A user attempt to access SPE from the Sterling B2B Integrator Launch SPE Trading Partner UI button. The user is taken to the SPE login screen instead of to the enveloping tasks. When the user attempts to log in to SPE, an error results.

Cause: This occurs when SPE is integrated with Sterling B2B Integrator over TLS 1.2 in NIST STRICT mode. Single sign on does not work.

Workaround:

1. Set the following values in the security.properties.in file in Sterling B2B Integrator:
• Set NIST mode = transition
• Set TLS protocol range to a value from TLS 1 .0 to TLS 1.2
• (Optional) Enable FIPS mode
2. In the SPE server.xml file, set the SSL protocol value: sslProtocol="TLSv1.2";
3. In the SPE server.xml file, set the additional values needed to set up SSL. Example:

<featureManager>
  <feature>ssl-1.0</feature>
</featureManager>

<!--  keystore path is relative to <member_root>/usr/servers/<member>/resources/security -->
  <keyStore id="defaultKeyStore" location="C:\IBM\key.jks" password="password" />
  <!-- Sets TLS 1.0 as the SSL Protocol -->
  <ssl id="defaultSSLConfig" keyStoreRef="defaultKeyStore" sslProtocol="TLS" />
  <!-- Enables https port -->
  <httpEndpoint id="defaultHttpEndpoint" host="*" httpPort="-1"  httpsPort="19443" />

For more information on configuring SSL and TLS1.2, see the Liberty documentation at https://developer.ibm.com/wasdev/docs/configuring-ssl-liberty/.

[WebSphere Transformation Extender does not recognize SPE after a subsequent WebSphere Transformation Extender installation]

Issue: A customer installs WebSphere Transformation Extender after SPE has been installed, and WebSphere Transformation Extender does not recognize SPE.

Background: When SPE is installed, it checks if WebSphere Transformation Extender is installed. If WebSphere Transformation Extender is installed, SPE updates the WebSphere Transformation Extender dtx.ini file.

If a customer installs WebSphere Transformation Extender after SPE has been installed, the dtx.ini file does not contain the location of the prior SPE installation.

Workaround: Manually update the WebSphere Transformation Extender dtx.ini file by appending the following lines:

[SPE]
SPE_INSTALL_DIR=C:/IBM/Standards Processing Engine 2.0.1

[Some characters are not available for use in naming a resource]

Issue: The following characters are reserved by the SPE Trading Partner UI, and therefore should not be used when naming a resource: "|" (pipe), "^" (caret), and ":" (colon).

Workaround: None

[Known issues in non-English versions of SPE documentation]

These issues appear in non-English versions of the documentation only. See the English version of the SPE documentation in the IBM Knowledge Center for the most recent documentation.

1. "Installing SPE V.8.5.1 on the Windows operating system": SPE can be installed with either the 32 bit version or the 64 bit version of IBM Installation Manager. Uninstalling any existing 64 bit installations of IBM Installation Manager is not necessary. If you use the 64 bit version of IBM Installation Manager and see the following warning, it can be ignored.
   
   The following packages do not support the 64-bit version of Installation Manager that you are using . . . If you continue, you might have issues with installation and deployment.
   
   Use of the 64 bit IBM Installation Manager does not interfere with installation or deployment of SPE common components or packs.
   
   The topic location is SPE core functionality > Installing, configuring and deploying > Installing, configuring and deploying SPE 8.5.1 > Installing and configuring the Standards Processing Engine > Installing SPE.
2. "Changing the SPE database or database driver after deployment": The reference to dynamicclasspath.cfg file in the UNIX operating system should read dynamicclasspath.cfg.in.
   
   The topic location is Using SPE with host applications > Using SPE with Sterling B2B Integrator > Installing SPE for Sterling B2B Integrator.

Back to top

=====================================================================
5. NEW AND CHANGED BEHAVIOR
====================================================================
Standards Processing Engine V.8.5.1 includes the following new features.

[Integration with Sterling B2B Integrator V.5.2.5]

The integration of SPE with Sterling B2B Integrator combines the comprehensive B2B integration of Sterling B2B Integrator with the robust healthcare solution provided by SPE and its "out of the box" Level 6 HIPAA validation.

Sterling B2B Integrator users can use single sign on to access SPE directly from their UI. From SPE, they can use the new Trading Partner UI features that substantially simplify onboarding. They can use new SPE enveloping, deenveloping, and transformation services in their business processes. In turn, SPE services can invoke Sterling B2B Integrator processes. Sterling B2B Integrator business processes, contract, and mailbox information can be configured in SPE envelopes

Sterling B2B Integrator users can be configured for use in SPE without being re-entered.

[Simplified installation]

The IBM Installation Manager is now used for installation of Standards Processing Engine common components, and to simplify installation and configuration of industry packs. A new pack installer is also available for pack components that are needed on the runtime server. This eliminates manual steps when assembling, transferring, and deploying these components on a runtime server.

[Trading Partner user interface enhancements]

Enhancements to the Trading Partner UI include the following features:

• Envelope-to-envelope references to speed navigation between envelopes
• Greater consistency with the IBM B2B Advanced Communications UI, as part of the effort to increase ease of use between products

[Additional features]

• Map conversion on file import from the UI or from the command line
• Envelope creation from sample data, which creates all 6 inbound and outbound envelopes from a file of sample data
• A custom transformation engine API and sample for user implementation in addressing specialized migration and translation needs

[Support for updates to industry standards]

SPE for Healthcare Payer V.8.5.1 supports these updates to industry standards:

• SPE Pack for Healthcare Payer, providing HIPAA WED/SNIP Level 6 support and UI screens for use in configuring HIPAA rules
• SPE Pack for Supply Chain EDI, with new standards version (X12 7010 and EDIFACT D13A and D13B), plus outbound validation for X12/EDIFACT

Back to top

=====================================================================

6. CONTACTING CUSTOMER SUPPORT
=====================================================================

Contact Customer Support at 1-800-IBM-SERV, or go to the Support Portal.

Back to top

=====================================================================

7. NOTICES AND TRADEMARKS
=====================================================================

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

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 states 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.

Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information
Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Privacy Policy Considerations
IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.

For more information about the use of various technologies, including cookies, for these purposes, see the IBM Privacy Policy, the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement.

Trademarks and service marks
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
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.
Microsoft and Windows are trademarks of Microsoft Corporation 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 product and service names might be trademarks of IBM or other companies.


This product includes software developed by the Eclipse Project
(http://www.eclipse.org/).