No proxy container needs to be running in order to administer objects. A distinction is made between the following objects:
MC-CmdHandler Client Instances
One object for each administered MC-CmdHandler. An MC-CmdHandler enables you to access the filesystem at the relevant host and execute scripts there.
Communication Services
One object for each administered communication service. A communication service is required for communications with CICS partners. It can run either locally or on a remote host.
openUTM-LU62 Gateways
One object for each managed openUTM-LU62 Gateway. An openUTM-LU62 Gateway is required alongside the communication service for communications with CICS partners. In each case, it runs on the same host as the associated communication service.
BeanConnect Proxy Clusters
One object for each administered BeanConnect proxy cluster. A proxy cluster consists of one or more proxies which must be configured beforehand.
BeanConnect Proxies
One object for each administered BeanConnect proxy which is not located in a proxy cluster.
Only "administrable" BeanConnect proxies can be managed using the Management Console. A BeanConnect proxy is considered administrable if one of the following applies:
The proxy is a local proxy.
The proxy is a remote proxy and the MC-CmdHandler associated with the proxy is available and can be accessed via the Management Console.
Resource Adapters
One or more resource adapters is assigned to each proxy. A resource adapter runs on an application server instance.
MBean Clients
An MBean client can be defined for each resource adapter. The Management Console can use the MBean client to access the MBeans of the relevant JMX server (display attributes and modify their values, run operations and receive notifications).
It is also possible to define "free" (stand-alone) MBean clients which are not assigned to any resource adapter. Free MBean clients are displayed on the topmost level of the navigation tree.
EIS Partners
One object for each administered EIS partner.
Inbound Users
The user information (user name and password) may be passed by the EIS partner on inbound communication. This user information must be known to the proxy.
Inbound Message Endpoints
An inbound message endpoint represents a communication endpoint for inbound communication. A proxy can manage several inbound message endpoints.
Inbound Services
An inbound service is a service which an EIS partner addresses during inbound communication. A service is always assigned to precisely one inbound message endpoint. However, it is possible to assign multiple services to an inbound message endpoint. You can also define coding properties for a service.
Outbound Services
An outbound service represents a service (transaction code (TAC) or CICS transaction) that is provided by the EIS partner.
Outbound Communication Endpoints
For each (symbolic) service that is specified in the connectionURL configuration property in the application server, you must configure a corresponding outbound communication endpoint of the same name in the proxy. The outbound communication endpoint definition maps the symbolic service name onto a real service name in the EIS partner application.
Outbound communication endpoints are specific to the EIS partners. Several outbound communication endpoints can be assigned to one EIS partner.
For detailed information see section Configuring outbound communication endpoints .