Configuration of BeanConnect

The BeanConnect proxy communicates with the BeanConnect resource adapter running within the application server on the one hand and with the EIS partner on the other hand. The proxy is not used for outbound communication via UPIC.

To ensure communication between an EJB deployed in the application server and a partner application, the proxy and the proxy components must be configured properly.

The BeanConnect Management Console allows you to carry out the configuration tasks for the BeanConnect proxy and the proxy components. It is also possible to change the configuration of the proxy clusters, EIS partners, the outbound services, the outbound communication endpoints and the inbound message endpoints, inbound services and Management Console command handlers (MC-CmdHandlers). The Management Console can also be configured as a JMX client for the display of MBeans

You can add new objects and change or delete existing objects.

This chapter provides information on the following topics:

• Adding a BeanConnect proxy to the Management Console

• Configuring the BeanConnect proxy

• Configuring a BeanConnect proxy cluster

• Configuring the BeanConnect resource adapter

• Configuring the EIS partners

• Configuring outbound communication

• Configuring inbound communication

• Saving and activating the configuration of the BeanConnect proxy

• Configuring the Management Console command handler (MC-CmdHandler)

• Configuring the Management Console as a JMX client

Detailed information on using the BeanConnect Management Console can be found in BeanConnect Management Console and in the online help system.