iWay Service Manager

In this section:

This section contains release information and migration, resolved issues, and known issues for iSM Version 6.1.8.
Top of page
x
Release Information and Migration

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. For more information on migration and compatibility, see the iWay Service Manager Migration Guide. In general, when migrating from the iWay Service Manager 5.x version, the key changes are the use of Providers to supply services, such as key store management, SSL Management, and database connectivity, as well as enhanced XPATH implementation. When migrating from iWay Service Manager 6.x, the application should not require any changes.

iSM Version 6.1.8 incorporates all prior delivered patches up to Cumulative Patch 14 for iWay Service Manager 6.0.1. Newly resolved cases since the iSM 6.1.7 release are listed under appropriate components in this document. For any additional cases and latest information, contact iWay Software Customer Support Services (see Customer Support).
Top of page
x
Resolved Issues
Top of page
x
Cross-Origin Resource Sharing (CORS)

iSM Version 6.1.8 introduces XDCorsAgent for use within the process flows managing the applications.

This service implements the server-side processing of Cross-Origin Resource Sharing (CORS) as described in the following website:

http://www.w3.org/TR/cors/

Normally, browsers forbid cross-origin requests for security reasons. CORS specifies a mechanism that allow browsers to make cross-origin requests to resources that opt in to provide access. CORS defines a set of HTTP headers and the rules to process them. Most common browsers implement CORS natively. It is expected that the user agent making the request will be a browser. The CORS service implements the server-side rules to respond to CORS requests received by an nHTTP listener.

For more information, see the section for Cross-Origin Resource Sharing Service (com.ibi.agents.XDCorsAgent) in the iWay Service Manager Component Reference Guide.
Top of page
x
Ordered Queue Subsort

The ordered queue facility allows messages to be categorized by group. A group is any value of meaning to the application. For example, a patient ID, a transaction ID, a shipment number, and so on. The group identifier is passed along with the message from the emitter. Messages within the group will be dispatched by the Ordered Queue listener in the order they are received. The group is defined when it is first presented for a message. There is no need to predefine the group during configuration.

Within a group, subsorting by a designated sequencing field is possible, allowing the ordered queue to resort the messages before passing them to the application process flow. This allows situations, such as the unpredictablility of input order due to communication delays for some messages or unsorted input in general to be handled. The intra-batch subsort key is presented by the emitter. For non-batching queues, subsorting is not available.

For more information, see the iWay Cross-Channel Services Guide.
Top of page
x
Pretty Good Privacy (PGP) Support

Pretty Good Privacy (PGP) components have been extended to better support interchanging messages with other PGP servers. The PGP components now support current PGP standards.

For more information, see the iWay Pretty Good Privacy (PGP) Extension User’s Guide.
Top of page
x
SQL Service (com.ibi.agents.XDSQLAgent) Update for Stored Procedure Calls

The SQL Service supports stored procedures containing a mix of input, output, and IN OUT parameters. To use a stored procedure with output parameters, you must describe each output parameter that is expected. The values returned by these parameters are stored in the response document generated by this service. The syntax for an output parameter is:

?$type(options).name

where:

options

Is optional.

name

Is optional.

The syntax for an IN OUT parameter is:

?#type(option).name

For example, call a stored procedure named sp1 with a string input (perhaps a key) and receive an output of int, numeric, and a result set (Oracle):

{call ?int.result = sp1(?inkey,?$numeric(2).cost,?$cursor)}

This will return three output parameters:

For more information, see the section for SQL Service (com.ibi.agents.XDSQLAgent) in the iWay Service Manager Component Reference Guide.
Top of page
x
Channel Startup Failure Event Flow

The Channel Startup Failure process flow applies only to channels that are not started by a specific manual command. This process flow must be published to the system, and is executed whenever the channel cannot initialize. The process flow can be used to send an email to alert an administrator of the issue.

Enter the name of a published process flow to be executed in the Startup Failure Flow field, as shown in the following image.

This field is a common channel property that is available for all iSM listeners. For more information, see the iWay Service Manager User's Guide.

iWay Software