Installing EAI Manager

About Installing EAI Manager

You can install EAI Manager on Linux operating systems. The EAI Manager includes these three EAI features:

EAI Connection Manager (CM) module
EAI Data Manager
Payload Generator External Module (EM) (also called the EAI Java Server or eai_js)

When you install EAI Manager, the installation program assigns default values in the CM and EAI DM configuration (pin.conf) files and the Payload Generator properties (Infranet.properties) file. For information about changing the entries in the pin.conf and properties files, see "Configuring EAI Manager".

Software Requirements

Before installing EAI Manager, you must install:

Third-Party software, which includes the Perl libraries and JRE required for installing BRM components. See "Preparing for BRM Installation" in BRM Installation Guide.
BRM. See "BRM Installation Overview" in BRM Installation Guide.

Installing EAI Manager

To install EAI Manager:

Go to the directory where you installed the Third-Party package and source the source.me file.

Caution:

You must source the source.me file to proceed with installation, otherwise "suitable JVM not found" and other error messages appear.

Bash shell:
```
source source.me.sh
```
C shell:
```
source source.me.csh
```
Follow the instructions in "Installing BRM" in BRM Installation Guide to install the full build package (brmserver_15.0.0.x.0_linux_generic_full.jar).
When the Installation Type screen appears during the installation process, do one of the following:
- To install all BRM components, including the EAI Manager, select the Complete installation option.
- To install the EAI Manager, along with other individual BRM components, select the Custom installation option, select EAI Manager 15.0.0.x.0, and then select any other optional managers you want to install.
Follow the instructions displayed during installation.

Note:

The installation program does not prompt you for the installation directory if BRM or EAI Manager is already installed on the machine and automatically installs the package at the BRM_home location, where BRM_home is the directory in which the BRM server software is installed.
Go to the directory where you installed the EAI Manager package and source the source.me file:

Bash shell:
```
source source.me.sh
```
C shell:
```
source source.me.csh
```
Go to the BRM_home/setup directory and run the pin_setup script.
Open the BRM_home/sys/cm/pin.conf file in a text editor, change the value of the enable_publish entry to 1, and then save and close the file.
Load information for EAI Manager into your system's event notification list.

See "Configuring Event Notification for EAI Manager".
Stop and restart all BRM processes.

Increasing Heap Size to Avoid "Out of Memory" Error Messages

To avoid "Out of Memory" error messages, increase the maximum heap size used by the Java Virtual Machine (JVM). The exact amount varies greatly with your needs and system resources. By default, the JVM used has a maximum heap size of 60 MB. Increase the maximum heap size to 120 MB by entering the following sample code in a text editor:

%IF_EXISTS%("INIT_JAVA_HEAP", "@INIT_JAVA_HEAP@20m") %IF_EXISTS%("MAX_JAVA_HEAP", "@MAX_JAVA_HEAP@120m")

where 20m and 120m indicate the minimum and maximum heap sizes respectively.

Save the file as Packagename.ja in the temporary directory to which you downloaded the installation software. Packagename indicates the name of the installation software.

Configuring Event Notification for EAI Manager

When a BRM event that is included in a business event occurs, EAI Manager uses event notification to call the opcode that caches the BRM event in the Payload Generator.

Before you can use EAI Manager, you must configure the event notification feature as follows:

If your system has multiple configuration files for event notification, merge them. See "Merging Event Notification Lists".
Ensure that the merged file includes the entire event notification list in the BRM_home/sys/data/config/pin_notify_eai file.

Note:

The BRM events listed in the pin_notify_eai file are not business events. A business event comprises one or more BRM events. You define business events in the payloadconfig.xml file. See "Configuring Business Events".
If you configured EAI Manager to publish to an HTTP port, ensure that the merged file also includes the entire event notification list in the BRM_home/sys/data/config/pin_notify_plugin_http file.

See "Configuring EAI Manager to Publish to an HTTP Port".
(Optional) If necessary, add, modify, or delete entries in your final event notification list. See "Editing the Event Notification List".

Note:

If you changed the default set of BRM events to be published by adding business events or by modifying the existing business events, you must edit your final event notification list to include all the BRM events in the new or modified business events.
Load your final event notification list into the BRM database. See "Loading the Event Notification List".

For more information, see "Using Event Notification".