iWay Service Manager

In this section:

This section describes new features for iWay Service Manager (iSM) in Version 6.1.6. For a list of resolved cases, see the iWay Service Manager Release Notes.


Top of page

x
iWay Functional Language

To enhance document storage and restoration capabilities at any point during a process and flow, the following iWay Functional Language (iFL) calls have been introduced in iSM Version 6.1.6:

Using _savedoc() and _restoredoc() offers an efficient means of holding the current document while other operations change the document, and then restoring the current document to its saved state. The save and restore functions should not be used across threads of a process flow. Note that since saving a document requires memory, these facilities should be used with caution.

The _savedoc() function uses the following format:

_savedoc(name, {action} [,scope] [,serialization)

The _savedoc() function allows the current document and (optionally) its state to be held while the document is changed for some purpose.

The _restoredoc() function uses the following format:

_restoredoc(name [,disposition])

The _restoredoc() function is meant to be paired with a _savedoc() function that saves a current document or its payload. The _restoredoc() function will restore either the entire document or the payload depending on how the save was performed by the _savedoc() function.

For more information on using the _savedoc() and _restoredoc() functions, see the iWay Functional Language Reference Guide.


Top of page

x
FTP Connection Cache Service

The FTP Connection Cache Service (com.ibi.agents.XDFTPConnectionCacheAgent) is a new service that has been introduced in iSM Version 6.1.6 to facilitate applications that perform multiple FTP operations within a process flow. This service is used to start and stop FTP connection caching for the server.

If the Connection caching parameter for this service is set to start using the host parameters configured by the user, then the service connects to a FTP server and caches the connection. Subsequent FTP services on the same edge will check for the cached connection. If their host parameters match the host parameters of the cached connection, then the cached connection is used instead of making a separate connection to the FTP server. For any FTP services that use a connection cache, the connection that is returned from the cache will point to the root directory of the user just like a fresh connection that would be made to the server.

If the Connection caching parameter for this service is set to stop, then the cached connection of the service is terminated (using the FTP QUIT command) and the pool is deleted from the iSM pools that are managed.


Top of page

x
RVI Gateway Multi-Point Attach

The RVI gateway offers its services to one or more attach points that connect the gateway to potential requestors of the service. In previous iSM releases, the application was limited to configuring a single host, which meant copies of the same channel providing the same service to different hosts. In iSM Version 6.1.6, one or more hosts can be specified, and each can optionally carry a unique port and IP interface connection.

The general format of a host (attach point) connection is:

host[:port][(IP
interface)]

A semicolon (;) can be used to separate a list of hosts. For example:

Server1;Server2:1234

where:

Server1

Uses the default port.

Server2

Uses port 1234 for the connection.

For multiple hosts, it is common to use the _file() function, addressing an external file containing the list. The file can simply hold a line of hosts, or it can be formatted with multiple lines, where each line holds a host entry.

The gateway monitoring has been adjusted to account for the multi-attach point architecture. The gateway appears on the command line monitor as one or more entries under the gateway itself. Each entry represents one attach point connection. For example, consider the following gateway called gw:

The line for the gateway shows the sum of the attach points counts under its control. The attach point connections can be in non-active states such as retry. This is controlled by the gateway itself.


Top of page

x
SQL Service

The SQL Service (com.ibi.agents.XDSQLAgent) has been updated to enable the return of a result set or input as an output document from execution. This enables the application to pass the document through the SQL Service without performing any modifications to the document. This eliminates the need to store and restore the original document. This feature is useful for any applications that are not expecting a result set from the SQL call. You can configure this feature using the Output Document parameter of the SQL Service, as shown in the following image.


Top of page

x
FTP Enhancements

This section describes FTP enhancements that are available in iSM Version 6.1.6.



x
FTP Server IPv4 and IPv6 Support

In iSM Version 6.1.6, the iWay FTP Server provides full support for IPv4 and IPv6. This support has been certified for secure and non-secure FTP server types with passive and active connection modes. Note that the security provider type for a secure FTP server must be a Keystore Provider and not a SSL Context Provider.



x
FTP Zero Byte File Handling

iSM Version 6.1.6 provides configurable support for the FTP Emit Service (com.ibi.agents.XDFTPEmitAgent) to handle the emitting of zero-byte files. The configuration is set by the Emit Zero Bytes parameter of the service and is set to true by default, as shown in the following image.


Top of page

x
Event Flows

This section describes event flow enhancements that are available in iSM Version 6.1.6.



x
Retry Expired

Messages can be queued for retry on channels that support this facility. This includes queue-based channels, the File channel, and the Internal Queue channel. The retries are triggered by logic in the process flow, and in this circumstance, the message is re-executed on a periodic basis until expiration has been reached.

At the expiration point, a process flow can be executed to take recovery actions (including notification) and optionally, changing the destination address or restarting with a changed (extended) expiration time.

Enter the name of a published process flow to be executed for the Expired Retry Flow parameter, as shown in the following image.

The Expired Retry Flow parameter is a common parameter that is available for all iSM listeners.



x
Failed ReplyTo

A reply designation associated with a document triggers an Emit operation following the completion of the process flow. If the Emit operation does not succeed, then Failed ReplyTo Flow is triggered.

Enter the name of a published process flow to be executed for the Failed ReplyTo Flow parameter, as shown in the following image.

The Failed ReplyTo Flow parameter is a common parameter that is available for all iSM listeners.



x
Dead Letter

Messages queued for an Emit operation (using the channel configuration called Reply To and Error To) or the Emit object in a process flow are sent when the outlet of the channel is executed. Messages can have alternate addresses if required.

If all attempts to emit the message fail, then the message is written to a configured dead letter directory by default.

If a dead letter process flow is configured, then the process flow can examine the message, redirect it, replace it, and potentially notify an appropriate authority. It can then send the message to another channel for a retry or continue to allow the message to be written to the dead letter queue.

Enter the name of a published process flow to be executed for the Dead Letter Flow parameter, as shown in the following image.

The Dead Letter Flow parameter is a common parameter that is available for all iSM listeners.


iWay Software