Configuration flow

In AI Suite, business configurations are defined at design time and depend on the customer needs.

The configuration is defined mainly through two components:

  • Composer: defines the structure configuration and the accounting business rules (transformation, aggregation and audit of financial data)
  • Designer: defines new attributes of the configuration structure for defining editors, dictionaries, report templates, exits, and other AI Suite settings like importers and data lifecycle.

The following graphic illustrates the configuration lifecycle:

Configuration flow

  1. Define structure and rules: In Composer, the user defines the data structure (business events) and the different business rules (transformation, aggregation and audit).
  2. Send configuration files to Repository (mvt and ctx): From Composer, the Rule Engine configuration is sent to Repository using Administration. The configuration is then stored as AI Suite configuration in the Repository database.
  3. The mvt and the ctx configuration files use a custom fixed flat format.
  4. Export financial XML file: From Composer, the user exports an XML Financial Export file that defines the formats used in the Rule Engine. This file is sent to Designer that transforms and loads this configuration as Designer configuration formats.
  5. Define editors and AI Suite settings: In Designer, the formats are enriched with different attributes such as spaces, tags, lifecycle configuration, and exits. In addition to the data structure configuration, Designer is used to configure many aspects of AI Suite: editors, dictionaries, exits, event processor rules (data flow rules), importers and different global settings.
  6. Publish configuration to Repository: From Designer, the configuration (formats, editors, dictionaries, etc.) is published to Repository. Report templates are sent to Repository through Report Server. These configuration files are mainly in XML format.
  7. Define the runtime configuration: The runtime configuration (Event Processor listeners) is defined in Administration.
  8. Store the runtime configuration: The runtime configuration (Event Processor listeners) is stored as XML configuration in the Repository database.
  9. Define custom report templates: Custom report templates are defined using the BIRT Designer. These custom report templates are imported in Repository using repository command tools to be used by the AI Suite components.
  10. Store the runtime configuration: The Repository API is used to store the runtime configuration and to provide access to it to different components.
  11. Send the configuration to Rule Engine Server (mvt and ctx): The AccountingIntegrator configuration is read from Repository and used by Rule Engine Server.
  12. Use the AccountingIntegrator configuration (mvt and ctx): Rule Engine Server uses mvt & ctx configuration files to process input financial events. Rule Engine Server uses embedded Rule Engine runtimes to perform processing jobs. A Rule Engine runtime is also able to regenerate its configuration into an mvt.xml file containing structure, rules and labels.
  13. Send the mvt.xml configuration file to AI Suite Studio: Using a command scrip, the user sends the mvt.xml configuration file produced by Rule Engine and embedded in Rule Engine Server to AI Suite.
  14. Use the mvt.xml configuration: AI Suite Studio imports the mvt.xml configuration file provided by Rule Engine and transforms it into documentation.
  15. Read the AI Suite configuration: The configuration (formats, editors, report templates, etc) is read from Repository and used by different components (InterPlay, Datastore or AI Suite Studio)
  16. Use the AI Suite configuration: Components InterPlay, Datastore or AI Suite Studio) use the configuration from Repository to perform specific operations. Some of the configuration is used by all components (formats) while other configuration is used only by one component (for example, only InterPlayuses editors). Multiple configuration sets (grouped in application) can be stored in Repository and a component can use one or several configuration sets.

Related topics

Main data flow

Related Links