9 Running the Enterprise Integration Platform

9.1 Testing the Enterprise Integration Platform

The purpose of the test tool is to perform a first sanity check after you have made modifications in the configuration of the Integration Platform.

Therefore, it is recommended to ALWAYS run the test tool after the configuration (e.g. in eai_ini.xml) was changed.

Shell scripts are provided for testing the Enterprise Integration Platform application. Since the software can run on any platform, which provides a Java Runtime Environment and supports the application specific connectors, shell scripts for different operating systems are provided.

In order to test the Enterprise Integration Platform on Microsoft Windows, please start the script test.cmd in the directory bin. On UNIX servers, please start the script test.sh in the directory bin.

The following startup options are available (you will get this by adding the -h option to the shell script):

Usage: Enterprise Integration Platform Manager [-c <conf-dir>] [-f] [-h] [-p <props-file>] [-t]

Options:

-c | --conf-dir	Specifies the configuration directory
-f | --flush	Flushes the queue at startup
-h | --help	Shows this help
-p | --props-file	Specifies the properties file
-t | --test	Tests the connections

Note: The test is the same as calling the manager with option -t.

When running the application you should get an output similar to this (in case everything is configured correctly):

[<date>] TRACE (Controller) - Checking connectors ... 
[<date>] TRACE (Controller) - Checking synchronous connectors ... 
[<date>] TRACE (Controller) - Checking pipes ... 
[<date>] TRACE (Controller) - Checking workflows ... 
[<date>] TRACE (Controller) - Checking queue ... 
[<date>] TRACE (Controller) - Testing connectors ... 
[<date>] TRACE (Controller) - Testing connector: erp 
[<date>] TRACE (Controller) - Testing connector: plm 
[<date>] TRACE (Controller) - Terminating tests ... 
[<date>] TRACE (Controller) - Tests done.

The following checks are performed when running the test routine:

1. Checks the structure and content of the configuration files, e.g. eai_ini.xml.

2. Checks the definition of the workflows and pipes in eai_ini.xml.

3. Checks the availability of the XSL mapping files (pipes.)

4. Checks connectivity to the queue database.

5. Reads in the configuration parameters of the connectors, which have been activated and tries to test-start the connector.

6. In case the Agile EDM Connector is activated: tries to connect to PLM and reads the PLM repository information; also creates the PLM schema file <eai.home>/conf/exi_plm.xsd.

7. In case the ERP connector is activated, please refer to the respective ERP documentation for detailed information regarding this step.

9.2 Integration Platform

Startup scripts are provided for running the Enterprise Integration Platform application. Since the software can run on any platform which provides a Java Runtime Environment and supports the application specific connectors, startup scripts for different operating systems are provided.

In order to start the Enterprise Integration Platform on Microsoft Windows, please start the script manager.cmd in the directory bin. On UNIX servers, please start the script manager.sh in the directory bin.

The following startup options are available (you will get this by adding the -h option to the startup script):

Usage: Enterprise Integration Platform Manager [-c <conf-dir>] [-f] [-h] [-p <props-file>] [-t]

Options:

-c | --conf-dir	Specifies the configuration directory
-f | --flush	Flushes the queue at startup
-h | --help	Shows this help
-p | --props-file	Specifies the properties file
-t | --test	Tests the connections

The following steps are performed when starting up the Integration Platform:

Startup of the EIP Controller

1. Connecting to the queue database

2. Initializing and starting up all active connectors incl. the BPM engine

3. Reading in all current business processes (if BPM engine is active)

4. "Polling" all asynchronous source connectors for new data (infinite loop until shutdown)