Verify the installation

To verify your installation, follow these guidelines:

Set environment variables

Set the following environment variables that are initialized in the script file called when starting processing (Example: . rdjenv):

  • RDJ_HOME
  • RDJ_EXEC
  • RDJ_LANG
  • QMGR_NAME
  • QRDJ_PREF
  • MQ_URL

The following variables give information necessary for the execution of Oracle exits during the transformation phase.

  • RDJ_EXIT501_ORACLE_USER
  • RDJ_EXIT501_ORACLE_PWD
  • RDJ_EXIT501_ORACLE_SRV

Check the installation of Rule Engine

All of the following tasks are automatically done by the installer. However, if during installation the rdjsic.bat procedure fails, you will need to complete the following tasks manually before using AccountingIntegrator.

Rule Engine file

To begin using AccountingIntegratorRule Engine, complete the following tasks:

  1. Open a session.
    • A Telnet session for a UNIX platform
    • An MS-DOS session for a Windows platform
  2. Check each runtime site created during installation. Repeat the following steps for each Runtime Site:
    1. Access the script installation directory: …\…\<Runtime Site directory>\script
    2. Check that the user has write permissions on the installation directories.
    3. Enter the command: rdjsic
    4. This procedure runs the AccountingIntegrator test deck that copies the product files and validates the installation.
    5. Environment variables are only modified for the duration of your Telnet or MS-DOS session. You must launch the rdjenv command every time you start a new session.
    6. If you always work in the same environment, it is recommended that you modify permanently the value of environment variables.
    7. Caution: The rdjsic command fills the database. Use the rdjraz command to erase the data the test generates and to delete the sys.dat and usr.dat files.

Rule Engine MQSeries

To validate the installation, you must first create the queues needed by the Rule Engine using the script rdjadmmqs located in the directory <Core directory>/envref/script. To use this script, you need a MQSeries user (mqm by default). The options available are:

  • create: create Rule Engine File queues
  • delete: delete Rule Engine File queues
  • setaut: update access rights on the Rule Engine MQSeries queues
  • disaut: display of access rights to the Rule Engine MQSeries queues

UNIX platforms

To begin using AccountingIntegratorRule Engine on UNIX platforms, complete the following tasks in the order below.

Validation - Administration

  1. Connect with the MQSeries Admin user.
  2. Specify the:
    • Name of the Queuer Manager via the variable QMGR_NAME.
      export QRDJ_NAME=<Queuer_name>
    • Prefix of the Queuer Manager via the variable QRDJ_PREF.
      export QRDJ_PREF=<Queuer_pref>
  3. If needed:
    1. Create the Rule Engine queuer Manager
      ctrmqm <queuer_name>
    2. Launch the Rule Engine queuer Manager
      strmqm <queuer_name>
  4. Set the variable RDJ_EXEC.
  5. Access the directory $RDJ_EXEC/script via the command:
    cd $RDJ_EXEC/script
  6. Launch the command rdjadmmqs create.

    The following messages are displayed:
    AMQ8006: MQSeries queue created.
    One MQSC command read.
    No commands have a syntax error.
    All valid MQSC commands were processed.
  7. Assign access rights to Rule Engine queues via the variable GROUP.
    This variable contains the name of the UNIX user group that will execute Rule Engine.
  8. Launch the command:
    rdjadmmqs setaut

    You can assign access permissions to several groups. Execute the command for each group.

Validation - User

All of the following can be done automatically using the options in the Installer. However, if you choose not to launch rdjsic automatically or if during installation the rdjsic.bat procedure fails, you will need to complete the following tasks manually before using AccountingIntegrator.

Then, for each new Runtime Site that you create, repeat the following steps:

  1. Connect with the installation user.
  2. Access the script installation directory:
    …/…/<Runtime Site directory>/script

Environment variables are only modified for the duration of your Telnet or MS-DOS session. You must launch the rdjenv command every time you start a new session.

If you always work in the same environment, it is recommended that you permanently modify the value of environment variables.

Caution: The rdjsic command fills the database. Use the rdjraz command to erase the data the test generates and to delete the sys.dat and usr.dat files.

Windows platforms

To begin using AccountingIntegratorRule Engine on Windows platforms, complete the following task:

Validation

  1. Access the script installation directory:
    …\…\<Runtime Site directory>\script
  2. Enter the following commands:
  3. rdjenv to set the internal variables (RDJ_HOME, RDJ_EXEC, RDJ_LANG, QMGR_NAME, QRDJ_PREF)
    • cd %RDJ_HOME%\envref\script
    • crtmqm %QMGR_NAME%)to create the Rule Engine Queue
    • strmqm %QMGR_NAME%)to launch the Rule Engine Queue
    • rdjadmmqs createto create the queues
    • rdjadmmqs setaut to update the access rights on the queues
    • cd %RDJ_EXEC%\script

All of the following can be done automatically using the options in the Installer. However, if you choose not to launch rdjsic automatically or, if during installation the rdjsic.bat procedure fails, you will need to complete the following tasks manually before using AccountingIntegrator.

  1. Enter rdjsic.
    This procedure runs the AccountingIntegrator test deck that copies the product files and validates the instalaltion.

Environment variables are only modified for the duration of your Telnet or MS-DOS session. You must launch the rdjenv command every time you start a new session.

If you always work in the same environment, it is recommended that you modify permanently the value of environment variables.

Caution: The rdjsic command fills the database. Use the rdjraz command to erase the data the test generates and to delete the sys.dat and usr.dat files.

Check the installation of Rule Engine Server

Verify that the Axway Installer created a sub-directory named ruleserver in the AccountingIntegrator folder.

Check that the folder contains the start/stop/status scripts. If you run the status script, it should display that the rule engine server is not started.

Check the installation of AI Enabler

Verify that the Axway Installer has created a sub-directory for each of the selected enablers located by default at:

<Synchrony installation directory>\<Composer installation directory>\enablers\

Each Enabler provides a specific set of functions in Composer. If the Enablers and Servers are correctly installed and started, you can now exchange objects between Composer and the execution servers.

For details on the use of individual Enablers and their dedicated objects, refer to the product online documentation.

Start and stop AccountingIntegrator

Be sure that databases are started before starting Axway products.

When installing with the Rule Engine Serverin standard mode, Axway Installer adds the following shortcut to the UNIX/Linux menu: Start > Programs > Axway Software > [installation name] > AIS.

  • Start Https Administration
  • Start Https Designer
  • Start Repository Console
  • Start Tomcat
  • Stop Tomcat

During installation in standard mode, Axway Installer adds the following shortcuts to the Windows menu: Start > Programs > Axway Software > [installation name] > AccountingIntegrator:

  • Rule Engine Server startConsole
  • Rule Engine Server startServer
  • Rule Engine Server statusServer
  • Rule Engine Server stopServer

To be able to execute administrative commands on Repository on Windows operating systems, you must use the: [Installation_Path]/AIS/Repository/startConsole.bat(sh) script set up during installation.

To use Designer, Report Server and Administration, you must start the Tomcat server delivered with AccountingIntegrator. You can start the accounting web server using the windows program shortcuts: Start > Programs > Axway Software > [installation name] > AIS > Start tomcat

You can stop the accounting web server using the windows program shortcuts: Start > Programs > Axway Software > [installation name] > AIS > Stop tomcat

You can start the Rule Engine Server using the windows program shortcuts: Start > Programs > Axway Software > [installation name] > AccountingIntegrator > Rule Engine Server startServer

Command line

To start the embedded Apache Tomcat web server manually, go to [Installation_Path]/AIS/Tools/apache-tomcat/startTomcat.bat(sh)

To stop the embedded Apache Tomcat web server manually, go to [Installation_Path]/AIS/Tools/apache-tomcat/stopTomcat.bat(sh)

To open the Repository client console, go to [Installation_Path]/AIS/Repository/startConsole.bat(sh)

To start the Rule Engine Server, go to [Installation_Path]/AccountingIntegrator/RuleServer/startServer.bat

To stop the Rule Engine Server, go to [Installation_Path]/AccountingIntegrator/RuleServer/stopServer.bat

To open the Rule Engine Server console, go to [Installation_Path]/AccountingIntegrator/RuleServer/startConsole.bat

Start Composer

To start Composer, execute the following tasks.

  1. Start the Composer database
  2. Start the Composer server
  3. Start the Composer client

Start the Composer database

Start the database associated with Composer.

Note: If you need assistance with this task, please contact your DBA (Database Administrator).

Start the Composer server

In Windows environments, do one of the following:

  • Execute the script: startAxwayComposerServer.bat or Composer.bat start
  • Execute the Windows shortcut (available if you installed Composer in normal mode):
    Programs > Axway Software> Axway [installation name] > Composer > Start Composer Server
  • Open the Windows Services utility (available if you installed Composer in Service mode), select the Composer service and then select Start.

In UNIX environments:

  1. Navigate to the directory: [Composer installation directory]/composer
  2. Execute the script: startAxwayComposerServer or Composer start

Start the Composer client

From an Internet browser on any machine in your network, enter the URL for the WebStart port. This URL has the format:

http://<server host machine name>:<Composer Server Web port>

For example:

http://myServer.myNet:7081/

Stop Composer

To stop Composer, execute the following tasks.

  1. Stop the Composer client - From the Composer File menu, select Exit.
  2. Stop the Composer server
  3. Stop the Composer database

Stop the Composer server

In Windows environments, do one of the following:

  • If you selected to install Composer in Windows services mode, Composer stops automatically when you shut down your computer.
  • Execute the script:
    stopAxwayComposerServer.cmd or Composer stop
  • Execute the Windows shortcut (available if you installed Composer in normal mode):
    Programs > Axway Software > Axway [installation name] > Composer > Stop Composer Server

In UNIX environments:

  1. Navigate to the directory:
    [Composer installation directory]/composer
  2. Execute the script:
    stopAxwayComposerServer.cmd or Composer stop

Stop the Composer database

Stop the database associated with Composer.

Start the Rule Engine Server

To start the Rule Engine Server, you can:

  • Use the scripts available in the folder [InstallFolder]/AccountingIntegrator/RuleServer
  • Use the windows shortcut in Programs > Axway Software> Axway [installation name] >AccountingIntegrator > RuleEngineServer startserver.

Verify connections

To create links between the different InterPlay components, in the Repository console, use Administration.

For more information, refer to "Repository component scripts" in the AccountingIntegrator User Guide.

Check log files

Check install.log file at the root of the installation folder.

Administration logs: [Installation_Path]/AIS/Tools/apache-tomcat/logs/admin-ui.log

Designer logs: [Installation_Path]/AIS/Tools/apache-tomcat/logs/designer.log

Report Server logs: [Installation_Path]/AIS/Tools/apache-tomcat/logs/reporting.log

Repository console log: [Installation_Path]/AIS/Repository/log/config-api.log

Rule Engine Server logs: [Installation_Path]/AccountingIntegrator/RuleServer/logs

Related Links