iWay Service Manager

In this section:

This section contains release information and migration, resolved issues, and known issues for iSM Version 6.1.9.
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.9 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.8 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

Note:

Top of page
x
iWay Functional Language: _timer() Function

As a result of changes in the Java specification with JVM 1.7, the special iSM patterns U, u, and Un available in the iFL _now() command are removed for JVM 1.7 and future iWay 7 releases. These special patterns were used for providing exact execution time of iSM components. The new iFL function _timer() has been introduced to provide these services in a release-independent way. All iSM applications that contain the _now() function with the three patterns specified should be changed to use _timer(). For more information, see the iWay Functional Language Reference Guide.
Top of page
x
Document Insert Service (com.ibi.agents.XDDocInsertAgent)

This service is used to insert data within an XML document. The data can consist of plain text or parsed XML content. The insertion point is specified by an XPath expression with optional namespace support. This service simplifies the function of the previously available Document Update Service (com.ibi.agents.XDDocUpdateAgent) and is the preferred method of inserting data into an XML document. For more information, see the iWay Service Manager Component Reference Guide.
Top of page
x
Web Service HTTP Client Service (com.ibi.agents.XDWSHttpClientAgent)

This service is similar in functionality to the existing Web Service Client Service (com.ibi.agents.XDWSClientAgent) and Web Service object that can be added to a process flow in iWay Integration Tools (iIT). However, unlike its predecessors, the Web Service HTTP Client Service (com.ibi.agents.XDWSHttpClientAgent) enables the use of a HTTP Client Provider for connection management and extended security support available through this provider. This agent is callable as a service and is not tied to the Web Service object that is available in iIT. For more information, see the iWay Service Manager Component Reference Guide.
Top of page
x
Cancelling an Operating Service (com.ibi.agents.XDCancelAgent)

The execution of one or more services on other execution edges of a process flow can be cancelled by using the Cancelling an Operating Service (com.ibi.agents.XDCancelAgent). This service accepts the name of one or more target services. Upon execution, a cancellation request is sent to the named service(s).

The cancellation capability facilitates the construction of caches, in which a slower operation such as accessing a remote database is run in parallel with a faster, local cache search. If the cache finds the required entry in the local database, then it can cancel the slower operation.

A cancel operation can only be directed to a service node (agent) that supports cancellation. In addition, that service must be able to actually cancel. For example, the SQL Object used in process flows can issue a cancel operation, but the effectiveness of the cancellation will depend upon the underlying database interfaces.
x
Sample Application

In the following cache example, the CancelReal node represents the Cancelling an Operating Service (com.ibi.agents.XDCancelAgent).

It is configured to cancel the AccessReal database access, which is anticipated to be slower than the AccessCache operation.

Although the local and remote sides of this process flow each go to the junction and thus to the End node, only one side will reach it.

Caches are very timing dependent. As a result, this example is simplified. It is not intended to show a fully working cache.
Top of page
x
Channel Startup Dependencies

A startup dependencies list has been introduced to all iSM channels and is available on the listener configuration page. This enables the channel to list its dependencies and ensure that they are started before its own initialization. The startup sequence supports multi-level definitions, where a channel can depend on other channels, which in turn have their own dependencies. The application is responsible for ensuring that there are no looping dependencies, where any two channels depend on each other for startup.

The listener configuration provides the Startup Dependencies parameter for defining a list of channels to be started prior to its start, as shown in the following image.
Top of page
x
Oracle REF CURSOR Type

The SQL Object (also referred to as the SQL Agent) now supports the Oracle REF CURSOR type, which allows recordsets to be returned from stored procedures. It also supports the collection of returned user parameters from stored procedures.

iWay Software