iWay Service Manager

iWay version 8.0 provides full support for JSON-based data processing. This can be seen in several product areas. For example, the listener configuration for channels has an additional option for JSON as an input format. This will ensure that proper JSON processing is enabled on the data bus. There are also several new JSON services, including a JSON Iterator. There are also new JSON functions for parsing out JSON elements. This support is crucial to the implementation of API management and interactions, but can be leveraged across any applicable protocol for data processing.

Certain application development designs may require that the application be updated frequently to accommodate a new or an updated component, such as a process flow or a transformation. For example, on-boarding a new partner might require packaging of the new transform, which must be executed for this specific partner. In previous releases, such updates required the application to be rebuilt and redeployed with the new component. This is still a recommended approach, as it provides a guarantee that all related components to the application execution in production are native to the application and are of a given version.

In this release, a new function called _fetch() is available, which enables an application designer to create a call to a transform or a sub-flow in a main/central application. Instead of providing a name of the local resource, which must be available within the application itself, the application designer can now configure the fetch call to an external resource, which can reside in another application (such as an application library of resources) or even on a different server in a remote configuration. For more information, see the iWay Functional Language Reference Guide.

iWay Business Activity Monitor (BAM) and iWay Trading Partner Manager (TPM) have been repackaged and are now delivered through an iWay Integration Application (iIA) with a corresponding deployment template. For more information, see the iWay Business Activity Monitor User's Guide and iWay Trading Partner Manager User's Guide.

The Token Field parameter was added to the Bearer Token Service (XDBearerTokenAgent). The default value is access_token. As an example, this is the Token Field used by Microsoft Azure. Before the Token Field parameter was created, the hard-coded Token Field name was token. To achieve the same behavior, the configuration of the Bearer Token Service (XDBearerTokenAgent) must be updated to set the Token Field explicitly to token.

The Expiration Field parameter was added to the Bearer Token Service (XDBearerTokenAgent). The default value is expires_in. As an example, this is the Expiration Field used by Microsoft Azure. Before the Expiration Field parameter was created, the service did not look for an expiration field. To achieve the same behavior, the configuration of the Bearer Token Service (XDBearerTokenAgent) must be updated to set the Expiration Token explicitly to none.