AccountingIntegrator Enabler Rule Engine: Start here

What is an AccountingIntegrator Enabler  Rule Engine

Where is an AccountingIntegrator Enabler  Rule Engine

How you define an AccountingIntegrator Enabler  Rule Engine

How you use an AccountingIntegrator Enabler  Rule Engine

What is an AccountingIntegrator Enabler  Rule Engine

An AccountingIntegrator Enabler  Rule Engine represents the execution environment that transforms the Input-Events you define in Composer. This execution environment includes:

  • Set of rules used
  • Production programs
  • Exits and external calls

Logically, an AccountingIntegrator Enabler  Rule Engine is a Axway Server that you define in the Topography layer of Composer. [FOR DETAILS: Axway Server: Start here]. An AccountingIntegrator Enabler  Rule Engine always belongs to a main Host object.

Via the Topography objects, you set up and configure the execution environment:

  • The communication networks (CommNetworks)
  • The machines that host the software (Hosts)
  • The AccountingIntegrator Enabler  Rule Engines that transform the Input-Events

After you define the Topography objects and set up the production environment where you execute your configuration, you rarely modify these objects.

You physically install the AccountingIntegrator Enabler  Rule Engine on a separate machine, and you deploy it from the Composer for AccountingIntegrator Enabler. When you send objects to Production, you send them to Production on a specific AccountingIntegrator Enabler  Rule Engine. When you send an AccountingIntegrator Enabler  Rule Engine to Production, you send the configuration parameters of that AccountingIntegrator Enabler  Rule Engine to Production.

For more information, refer to AccountingIntegrator Enabler  Rule Engine Reference Manual.

Where is an AccountingIntegrator Enabler  Rule Engine?

Axway module

AccountingIntegrator Enabler

Workbench

The AccountingIntegrator Enabler  Rule Engine forms part of the Topography workbench. To define an AccountingIntegrator Enabler  Rule Engine, you must have access to the Topography workbench.

Object dependencies

When you define or import an object, it is stored in the metadata repository and is available for reuse by other objects. Typically, the objects that you define exist in a specific object hierarchy. That is, objects:

  • use objects below them in the hierarchy
  • are used by objects above them in the hierarchy

To help you manage the interlinked network of objects, the software provides the Object Dependencies Browser that displays the object dependencies for a selected object.

This table lists the objects that use and that are used by AccountingIntegrator Enabler  Rule Engine.

AccountingIntegrator Enabler  Rule Engine objects

Use

Are used by

Hosts

  • Broadcast Agents to update the parameter settings and functional contexts stored in:

 

How you define an AccountingIntegrator Enabler  Rule Engine

Before you define an AccountingIntegrator Enabler  Rule Engine

Before you define an AccountingIntegrator Enabler  Rule Engine, you must create a:

  • HostGroup: Organizational object to group a set of Hosts, or machines, where AccountingIntegrator Enabler  Rule Engine modules are installed. Typically represents a geographical site. You can group sub-HostGroups.
  • Host: Contains Axway Server objects that are associated with AccountingIntegrator Enabler  Rule Engines running on this Host

Defining an AccountingIntegrator Enabler Axway Server.

Create the AccountingIntegrator Enabler Axway Server object from the Topography tab.

To define a new AccountingIntegrator Enabler Axway Server object, first complete the:

AccountingIntegrator Enabler  Rule Engine architectures

Operating requirements

  • You must install the Broadcast Agent on either a UNIX or Windows machine even when the AccountingIntegrator Enabler  Rule Engine Server is installed on MVS or AS/400.
  • You can install several agents on the same machine provided you configure separate port numbers and directories for each of them.
  • You can install the AccountingIntegrator Enabler  Rule Engine applications and the Broadcast Agent on the same or separate machines. For a given Axway Server, you can customize the common.xml script to update AccountingIntegrator Enabler  Rule Engine directly. If an error occurs while the agent is executing a transaction or when updating AccountingIntegrator Enabler  Rule Engine via the rdjmaj and rdjrch scripts, the system considers the transaction incorrect and canceled.
  • The Uninstallation feature available in the Axway Composer workstation only uninstalls the environment of the current Axway Server. It does not delete either the installed Agent or the installed environments  specific to other Axway Servers managed by the same Agent. The uninstallation operation executes the  ANT Remove_Product.xml from where you installed the Agent.
  • The Install feature available in the Axway Composer workstation only installs the execution environment for an Axway Server. It does not install AccountingIntegrator Enabler  Rule Engine itself. If an execution environment already exists, the Install program does not overwrite it. The Install program runs the ANTCreate_Product.xml from where you installed the Agent. This script creates a file structure based on the parameters that you defined in the General and AccountingIntegrator Enabler Parameters tabs. Specifically, the file structure creates a root directory defined as follows:
    • directory location you define in the Agent path parameter on the AccountingIntegrator Enabler Parameters tab.
    • directory name you define in the Name parameter on the General tab.

The resulting file structure includes the directories:

Directory Contents

ToBeCommited

Directory not used for AccountingIntegrator Enabler 1.1.0 or later.

Commited

All Checked data available to update AccountingIntegrator Enabler  Rule Engine.

Shell

Script files called during the execution of status commands in Composer. You can customize the Shell scripts to automate the processing sequence.

Tmp

Temporary files and directories created and deleted by the broadcasting functions. After an error occurs, these files and directories can remain in this directory. However, at the start of each new action, the system purges the contents of this directory.

Example of an AccountingIntegrator Enabler  Rule Engine architecture

Here, the Broadcast Agent is installed on a single host via the AccountingIntegrator Enabler installation kit. The Agent manages four Axway Servers, Server 1, Server 2, Server 3 and Server 4. The Agent processes transactions from each of these Axway Servers in separate environments specific to each Server. That is, in the Server 1, Server 2, Server 3 and Server 4 sub-directories in the Agent root directory. These environments are created and deleted via the Install and Uninstall features available on the Axway Composer workstation in the contextual menu of the Axway Server concerned.

After you define an AccountingIntegrator Enabler  Rule Engine

After you define an AccountingIntegrator Enabler  Rule Engine:

How you use an AccountingIntegrator Enabler  Rule Engine

You can perform all basic operations on AccountingIntegrator Enabler  Rule Engine objects. [FOR DETAILS: Working with objects: Start here]

This object follows the standard object life cycle.

Back to top

Related Links