iway iway New Features Bulletin Version 6.0.1 Service Manager (SM) DN3501946.0909

iway iway New Features Bulletin Version 6.0.1 Service Manager (SM) DN3501946.0909

Cactus, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iway, iway Software, Parlay, PC/FOCUS, RStat, TableTalk, Web390, and WebFOCUS are registered trademarks, and Magnify is a trademark of Information Builders, Inc. Due to the nature of this material, this document refers to numerous hardware and software products by their trademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by their respective companies. It is not this publisher s intent to use any of these names generically. The reader is therefore cautioned to investigate all claimed trademark rights before using any of these names other than to refer to the product described. Copyright 2009, by Information Builders, Inc. and iway Software. All rights reserved. Patent Pending. This manual, or parts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc.

iway Contents iway New Features Bulletin...5 Overview...6 iway Service Manager...7 Providers...8 Message Security...8 New HTTP Services...8 New AS2 Services...9 Telnet Management Connection...9 Adapter Persistence...9 Process Flow Improvements...9 Standards...9 iway Functional Language...10 Metrics...10 XML Parsing...10 Preparsers...10 File Listener...10 Migration Considerations...11 Compatibility Settings...11 Parsing...12 Compatibility Extension (iwxcompat)...12 Providers...12 XPATH...13 Activity Facility...13 User-defined iway Functional Language Functions...13 iway Adapters...14 iway Transaction Adapter for IMS...14 iway Protocol Adapter for LDAP...14 iway Protocol Adapter for SFTP...14 iway Adapter for SWIFT...15 iway New Features Bulletin 3

Contents iway Adapter for EDI X12...15 iway Data Quality Center...15 iway Trading Partner Manager...15 4 iway Software

iway New Features Bulletin This document describes the new features that have been introduced in the iway 6.0 Service Manager (SM) release. It is intended for all levels of users, including system integrators, application developers, and administrators. The iway 6.0 SM release is a part of the iway SOA Middleware initiative, a new enterprise integration product suite. This bulletin is directed to the 6.0.1 release, which is a major upgrade of the base 6.0 server. Topics: Overview iway Service Manager Migration Considerations iway Adapters iway Data Quality Center iway Trading Partner Manager iway New Features Bulletin 5

Overview Overview iway Software's integration technology achieves loose coupling among applications by focusing on Service Enablement, Service Composition, and Service Consumption, three critical areas of integration. The general availability of iway 6.0 Service Manager (SM) offers improvements in: Standards Compliance ism 6.0 meets current RFC requirements for XML, protocols and security controls. This includes a new, fully-compliant XPATH capability. XPATH 1.0 Currently in use in high-security installations, ism 6.0 is based on accepted standards for encryption, document digital signature, user authentication, and authorization. Performance Significant improvements in throughput and latency make ism 6.0 a prime component of high-performance networks and business processing solutions. New HTTP and AS2 solutions significantly improve message rates and transaction volumes along with full RFC compliance. Protocol Enhancements iway 6.0.1 provides support for HTTP 1.1 including support for REST messages allowing for integration in a Web-Oriented Architecture (WOA). Controllability A new telnet-based facility permits remote control of the server for STCU activities, such as starting and stopping listeners, setting run-time options, investigating server operations, and so on. Data Quality A new, integrated Data Quality engine offers advances in data validation and Master Data management situations. Trading Partner Management A new trading partner manager offers extended control of trading partner-specific information. Complex Event Processing A new real-time data feeder supports detailed analysis of business activity passing through the iway Service Manager. Transactionality 6 iway Software

iway New Features Bulletin Advances in iway transactionality improve integrity of business processes. The Communication Resource Manager (CRM) Gateway in conjunction with iway Service Manager supports two-phase commit processing for the IMS and CICS adapters. iway Service Manager In this section: Providers Message Security New HTTP Services New AS2 Services Telnet Management Connection Adapter Persistence Process Flow Improvements Standards iway Functional Language Metrics XML Parsing Preparsers File Listener In this release, iway Service Manager is optimized for Java 1.6 and certified to run on z/os. In addition, iway Service Manager is also certified for SOAP integration with IBM WebSphere Process Server, WebSphere ESB, and WebSphere Message Broker. While every effort has been made to ensure compatibility with regard to the execution of existing process flows and channels, the server configuration has changed. Among the key changes are the use of providers to supply services such as key store management, SSL management, and database connectivity. iway New Features Bulletin 7

iway Service Manager Providers Configuration of central resources has been moved to the Providers section of the iway Service Manager Administration Console. All new and updated components obtain central services through these providers. Providers enable the centralization of resource definitions, avoiding the need to configure each component individually, and allow for improvements in managing resources shared across channels. These providers include: Database Connection Providers, which control the allocation of connections to databases. Use of this provider reduces the number of open connections at any point, and makes it possible for multiple users within a single process flow to share a connection in order to improve transactionality. LDAP Connection Providers, which offer multiple paths to individual directories. This increases the functional use of LDAP within the server and improves performance. SSL Providers, which manage SSL connections, avoiding the need to reestablish sessions with a single endpoint. These providers handle all negotiations with the client. By selecting the desired provider for the channel, the degree of security can be managed on a common basis. Key Store Management Providers, which centralize key store and trust store control to reduce the need to define this information on a channel-by-channel basis. Authentication Providers, which offer user identification and password validation to components such as new HTTP and the new Telnet Management Channel. Authentication can be performed through various resources such as an SQL database, LDAP, a local properties file, or through Java-standard JAAS. An authorized and authenticated user can hold one or more roles, which can be used to control that user within a process flow. Message Security Message flows and the server itself can be configured to be secure. A secure server uses signed configurations, preventing changes other than through the use of authorized tools by authorized personnel. The server can generate and check digital signatures and handles secure S/MIME attachments. New HTTP Services A new HTTP service offers HTTP 1.1 compliance along with full support for persistent connections. The protocol is designed to be non-blocking and offers a significant reduction in the use of system services, especially during high load applications. 8 iway Software

iway New Features Bulletin All HTTP verbs are supported (based on configuration) with any verb able to be passed through the channel for execution within a process flow. This includes GET, POST, DELETE, PUT, OPTIONS, TRACE, and so on. Secure Sockets Layer (SSL) support is available through the use of a centralized SSL provider. New AS2 Services A new AS2 protocol, based on the new HTTP facilities, is available. This feature fully implements the latest AS2 specifications, and additionally allows for deferral of AS2 Message Disposition Notification (MDN) until the message is handled by a process flow. Telnet Management Connection To improve the management of iway Service Manager instances running as a service or remotely, an optional channel can be configured to handle Telnet clients. Security can be configured including SSL using lists and an authentication provider. Most control commands previously available only through the command shell on a local machine, are now available via the configured remote Telnet session. Operations through the Telnet Management Console are overseen by the server's security facilities. Adapter Persistence When using multiple instances (nodes) of a single iway Adapter (for example, SAP or IMS) within a process flow, the iway Adapters can now be pooled at the target level. This enables a single commit/rollback to be sent to the target at the end of the process flow. As a result, transactionality within the process flow is improved and simplified. Process Flow Improvements Many improvements have been made to the execution of process flows, which result in reduced memory overhead and faster handing. Specific changes have been made to fully support passing of status from a sub-flow to the parent flow. Additionally, a CATCH service enables you to capture error situations for additional handling by the process flow. CATCH is significant when developing AS2-based process flows that defer sending of an MDN. This allows the server to always send the MDN even in the even of a failure during the process flow. Standards iway Service Manager conforms with standards strongly, including offering full XPATH access to documents and XSLT XML to XML transformations. Traces from third-party components used by applications (through Log4J and Java Logging), even when not directly supported by ism, can be captured and included in the standard ism trace logs. iway New Features Bulletin 9

iway Service Manager iway Functional Language iway Service Manager provides new and extended iway Functional Language (ifl) facilities For example, the _urlparse() function now accepts additional parameters to extract a keyword from within the query component. New functions are available to examine the security role token associated with an authenticated principal, enabling routing on a security level to be performed in a process flow. Metrics A new stateful and persistent special register is available, which is called a metric. It is used to maintain statistics at the server or channel (protocol) level. Examples include the maximum value of transactions received or the number of errors of a certain type. iway Functional Language (ifl) is used to set and update metrics in the familiar XDSREGAgent. Metrics can be locked for simultaneous update and reference. The new ifl function _lock() can reference one or more metrics under the appropriate lock to prevent obtaining inconsistent values from multiple metrics. XML Parsing A new setting in the channel (listener) configuration allows the inclusion of white space in the parsed document. Earlier editions of ism eliminated what appeared to be extraneous white space. XML Parsing is now compliant to current XML standards. This includes full name space support. Preparsers Preparsers are channel inlet exits that perform initial work on a message. In prior releases, because it was assumed that the task of a preparser is to prepare the message for XML parsing, preparsers were not called on channels configured for flat (non-xml) documents. In response to many requests, preparsers now run on flat input messages. Naturally, the selection of the appropriate preparser for the particular message remains a configuration task. The most commonly expected use case for running preparsers on flat documents is the use of splitting preparsers that divide a message into sections for processing in a single transaction. File Listener The File listener has been upgraded to offer continuous read capabilities. In prior releases, the File listener read files from a specified input directory in batches, waited until the list of files had been exhausted by the configured channels, and then went back to the disk for another batch. In ism 6.0, file access is not directly tied to the exhaustion of the input list. Therefore, a slower channel will not prevent access to files by faster channels. 10 iway Software

iway New Features Bulletin IA new setting on the File listener enables you to switch the batching behavior that was used in earlier releases, if required. In ism 6.0, the default is configured for continuous read. Migration Considerations In this section: Compatibility Settings Parsing Compatibility Extension (iwxcompat) Providers XPATH Activity Facility User-defined iway Functional Language Functions Every effort has been made to ensure that migrating to ism 6.0 is a seamless process. However, there are some changes that must be made, which are impossible to avoid and this section highlights many of them. Many ism components now strictly conform to newer public standards, and this can result in unexpected behavior throughout the system. Unless an application has been coded to specifically take advantage of, or workaround earlier standards adherence, most applications will function the same as in earlier ism releases. Tools are available from iway Software to assist in migrations from earlier server releases (for example, 5.5, 5.6) and can be requested from iway Product management. The tools help to identify areas of concern in existing applications and in upgrading ifl expressions to the stricter standards of 6.0. These tools will continue to be upgraded; contact Information Builders Customer Support for the current latest tool set. Several areas of concern to applications that are being transferred to the 6.0 series of servers are discussed in FAQs that can be accessed from the What's New information in the iway Service Manager Administration Console. Compatibility Settings A new Compatibility section is available in the General Settings section of the iway Service Manager Administration Console. The settings offered here can assist in ensuring that ism 6.0 remains compatible with earlier releases. iway New Features Bulletin 11

Migration Considerations Prior servers performed special processing for EDA-formatted XML documents. This special processing is rarely used, and complicates some other areas of the server processing path. By default, ism 6.0 no longer performs this special processing. To reinstate the special EDA processing, set the Compatibility property to true. Parsing iway Service Manager parses XML documents in compliance with XML 1.0, as specified by the XML RFC. Earlier releases supported a mode of XML parsing that accounted for attempts to "pretty print" documents, and condensed white space. Some services, such as XML digital signature normalization require that parsing be strictly compliant with "mixed mode" specifications. To accommodate this, each channel can be set to preserve or condense mode in ism 6.0. Condense mode reproduces the intent of the parsing systems that were used in earlier releases. Preserve mode, in compliance with the XML RFC, is now set by default. To accommodate "mixed mode" specifications, new methods have also been added to the XML document APIs. Existing API methods have been mapped such that prior behavior can be expected in most instances. Compatibility Extension (iwxcompat) A new Compatibility extension (iwxcompat) is provided with ism 6.0. This extension contains older components (for example, XDHotScreenAgent and XDJythonAgent) that are no longer distributed as an integral part of the server. The Compatibility extension (iwxcompat) must be installed in the etc/manager/extensions directory. Providers The introduction of providers in ism 6.0 adds many conveniences and improvements to server handling of documents. In earlier releases, services such as key stores were configured directly in the components that used these objects. However, as more server objects begin to take advantage of providers, runtime configuration must change to: Define the provider. Reference the provider in the appropriate components using these objects. In general, there are: Listener/channel configuration such as new HTTP that reference the SSL provider. Process flow objects/nodes that reference provider services. In most cases the earlier objects remain in place, unchanged, so that unless you need to take advantage of provider services the server's configuration will not change. 12 iway Software

iway New Features Bulletin XPATH Previous releases of ism supported the XPATH() function, which implemented a subset of the formal XPATH specification (modified to better fit with the iway requirements). Generally this followed the RFC (http://www.w3.org/tr/1999/rec-xpath-19991116, subsection 2.5, Abbreviated Syntax). As of ism 6.0, the XPATH() function implements the complete XPATH namespaces in compliance with XML 1.0 as specified in the XML RFC. Strict adherence to the XPATH specification may introduce some incompatibilities in function use. This is especially true in XPATH() expressions that included namespaces. To help avoid the need to make changes in existing application logic, the new function _IWXPATH() is introduced that implements the original iway XPATH() implementation. Please note that the _IWXPATH() function is available in ism 5.6 as well, where it is identical to the XPATH() implementation. An additional function, _xpath1(), is available that is never mapped through the compatibility settings. This function is the new XPATH 1.0 standard functionality. iway recommends that users review applications for use of XPATH functions, and ensure that XPATH is properly used, rather than relying upon the compatibility settings. Users should pay particular attention to the use of documents with no namespace specification and documents that use a default namespace specification. Activity Facility In previous releases, the transaction log was configured using the iway Service Manager Administration Console. This log was a serial flat binary file, which could eventually fill a hard disk. In ism 5.5, the Activity Facility was introduced that offered the option to select from several types of log writes, including writing to a relational data base. In ism 6.0, the main console log is no longer supported. An Activity Facility driver is available to emulate the previously supported log file structure. User-defined iway Functional Language Functions User-defined iway Functional Language (ifl) functions should continue to function as in prior releases. However, these functions must be upgraded to the ism 6.0 specification. For more information, see the iway Service Manager Programmer's Guide. It is the responsibility of the developers of the user-defined ifl functions to thoroughly test their functionality when migrating to ism 6.0. The changes to the functions are generally mechanical. iway New Features Bulletin 13

iway Adapters iway Adapters In this section: iway Transaction Adapter for IMS iway Protocol Adapter for LDAP iway Protocol Adapter for SFTP iway Adapter for SWIFT iway Adapter for EDI X12 The following section describes new features and enhancements for iway Adapters in the ism 6.0 release. iway Transaction Adapter for IMS The iway Transaction Adapter for IMS is enhanced in the ism 6.0 release: Message Format Service (MFS) Support Message Format Service (MFS) is now supported by the iway Transaction Adapter for IMS. XML schema documents define the data type based on some or all of the fields in an MFS map. As a result, a series of documents in a process flow can be constructed to drive a 3270/MFS IMS application. CRM Gateway Support The CRM Gateway for the iway Transaction Adapter for IMS is a component that supports the CRM Gateway communication option of the adapter. This component runs as a standalone process on the mainframe under z/os. The CRM serves as a TCP/IP to SNA gateway. The IMS adapter, within iway Service Manager, communicates via TCP/IP to the CRM, which calls into IMS via APPC (SNA). The CRM must run on a node in the same SNA network as the target IMS system. The IMS/APPC facility and appropriate SNA nodes must be configured and enabled. The CRM Gateway supports the two phase commit protocol. This is used by the IMS adapter LocalTransaction feature, which aggregates multiple IMS calls into a single Logical Unit of Work (LUW). iway Protocol Adapter for LDAP The iway Protocol Adapter for LDAP provides directory services for standard LDAP directories. iway Protocol Adapter for SFTP The iway Protocol Adapter for SFTP enables ism to exchange files with Secure Shell (SSH) enabled servers. 14 iway Software

iway New Features Bulletin iway Adapter for SWIFT The iway Adapter for SWIFT has been enhanced to provide support for SWIFT 2009 Standard Specifications. iway Adapter for EDI X12 The iway Adapter for EDI X12 incorporates in-depth knowledge of EDI message structures and transaction sets for ANSI X12 to streamline and optimize the integration of EDI trans actions with internal enterprise applications and third-party trading partners. iway Data Quality Center iway Data Quality Center (DQC) is an essential tool for complex data quality management. iway DQC is designed not only to evaluate, monitor, and manage data quality in different information systems, but also to prevent incorrect data from entering these systems in the first place. iway DQC is bundled with a specific set of business rules and localized dictionaries. Banks, insurance, health care, and telecommunications companies choose iway DQC for easy implementation and tangible business results. iway Trading Partner Manager iway Trading Partner Manager (itpm) is an essential tool for managing trading partners and centralizing the definition of all trading partners for an enterprise in one repository. itpm is designed not only to create a central repository for all the trading partners, but also to associate the trading partners with iway components (such as channels and adapters), and provide mapping between trading partners and ism. itpm integrates with the iway Integration Solution for EDI and MFT solution to give enterprises the capability to manage partners across industry verticals and reduce the time to start EDI integration for a better return on investment. Companies dealing with business-to-business activities can choose itpm for quick EDI adaptation. iway New Features Bulletin 15

iway Trading Partner Manager 16 iway Software