InterPlay 2.3.0 Release Notes

New features and enhancements

New features specific to InterPlay


The attached files are checked, for their types and size, in order to avoid 'pollution' of the database (zip and xml 'bombs').

Axway AIS communication protocol is now TLS 1.2.

The system does not allow browsers to store passwords.

The number of connections per user is limited, in order to protect the system against denial of service attack. The limitation is configured through the Admin UI.

The command line tools request for user authentication.

Performance and usage

Default editor automatic generation on InterPlay side:

Some customers use only default editors for the objects they manage and they could have a huge number of objects in the configuration. The deployment consumes a lot of time in this case (objects + editors).

In order to spend less time in the deployment action, it is now possible to deploy only the object types, and the concerned default editor is now generated on the InterPlay side.

AI Internal tables support

InterPlay allows its users to create the AI internal table rows and to generate the tables mvt.mvt file to update the Rule Engine configuration. The table structure is automatically synchronized from the AI Enabler definition, in order to provide to the user the proper list of columns to be populated:

  • Collection type, containing all 'AI internal table' objects
  • Object type per AI internal table
  • Default editors (updatable) for each AI internal table

On the InterPlay side, the user is able to manage the content of the internal tables:

  • by importing values from csv files
  • by updating, creating rows
  • generating an mvt.mvt file for AI Rule Engine at export time

Date management

The user is now able to define java patterns for dates from an AI format:

  • Rule Engine authorizes only: YYYYMMDD, CYYMMDD, YYMMDD
  • Java patterns are authorized for dates in AI formats for InterPlay and Datastore usages

REST connectivity

The operations automation may be enriched, by using new REST calls available for following actions:

  • Collection ChangeStatus
  • Force unlock
  • Purge

DB management

The Purge command is optimized in order to reduce the redo log usage.

Common features to AI Suite

Configuration Repository

The AI configuration management is enhanced :

  • To take into consideration the Financial export in the AI configuration
  • To automate its import through a REST operation

AI Suite main changes:

  • The configurationRepository is compliant with 2.3.0 audit trace header structures
  • Relationship definitions are upgraded to Datastore definitions
  • The configuration administrator should be able to manager on an easier way the configuration deployments, because the configuration version is now incremented when the formatter is changed
  • The user is able to configure the new AI Suite Studio component

The installation and configuration are easier, the topography links are automatically generated between the components, taking into consideration their types:

  • Designer is linked to all InterPlay, Datastore Runtime components
  • Datastore Client is linked to all Datastore Runtime components
  • Report Server is linked to all Datastore Client, InterPlay, Designer, Rule Engine Server, and Administration components.


Event management now offers new facilities:

  • An access through a list of interactions are available.
  • The selection of one interaction provides the list of the events concerned with that interaction
  • User preferences can be set for the list display : customizing the columns order, their size and width ...
  • Display all details of an event

Report Server security

The security of all communications between Report Server and Datastore or InterPlay is ensured through REST API.

The user can now automate the reports templates management through a REST API.


Navigation is now easier, using direct links between the objects

The user can configure the new AI Suite features:

  • AI Suite Studio sampler configuration
  • Datastore reconciliation configuration

The importDocuments and exportDocuments operations now allow Designer to handle remote data, using a URL for the files to be imported or exported:

  • importDocuments and exportDocuments: URL support for data file transfer.

The automatic configuration synchronization with the AI Enabler is now possible using new operations: transformConfiguration

The automatic configuration synchronization with configurationRepository is now possible using new operations :

  • deployConfiguration: deploys the configuration from Designer to the configurationRepository.

Event Processor news

The InterPlay import operation is now able to take into consideration a collection properties file, to be consistent with the manual action.

The test and production TimeListener and FileListener management is easier with the possibility to enable/disable a listener.

The user may be able to define a context variable to be taken into consideration in the rule executions.

The automation configuration by rest API provides now the possibility to automate the cleanup after the files are managed.


This section describes documentation enhancements and related documentation.

Documentation enhancements

A set of documents has been added to AI Suite, relating to the new product AI Suite Studio:

  • AI Suite Studio Installation Guide
  • AI Suite Studio Configuration Guide
  • AI Suite Studio User Guide

The InterPlay documentation set includes the following documents:

AI Suite

Composer - AccountingIntegrator Enabler




AI Suite Studio

  • AI Suite Studio Installation Guide HTML
  • AI Suite Studio Configuration Guide HTML
  • AI Suite StudioUser Guide HTML
  • Axway Supported Platforms
  • Axway Interoperability Matrix

Support services

The Axway Global Support team provides worldwide 24x7 support for customers with active support agreements.
Email or visit Axway Support at


Related Links