Access to services by inbound messages
Enterprise services, object structure services, and standard services can all function in a server cluster.
An inbound transaction can access the relevant service with any of the following communication methods:
- REST API, Internet Inter-ORB Protocol (IIOP), and enterprise beans
- HTTP and HTTPS servlet
- SOAP, HTTP, and HTTPS servlet
Enterprise beans
With a single server, the provider URL for accessing the JNDI tree is the single server URL. With a server cluster, the provider URL can be the URL of any of the servers that has the enterprise beans deployed. All members of the cluster share the JNDI tree and any member of the cluster can look for and retrieve a cluster.
Following a cluster look up, the client retrieves a cluster-aware proxy of the enterprise beans which load balances all the subsequent calls that use that proxy. Load balancing happens transparently to the client code. There is no difference between the code for a single server and for a cluster setup. A separate enterprise bean is deployed for each type of service: object structure service, enterprise service, and standard service.
HTTP servlet
The integration servlet is deployed across all members of the cluster. With a single server configuration, the URL is the HTTP and HTTPS URL of that server. With a cluster server configuration, the URL is the HTTP and HTTPS URL of the load balancer for the cluster. A separate servlet is deployed for each type of service: object structure, enterprise, and standard service.
The URL formats for each service are shown in the following table. The meaweb variable in the URL represents the value you specify for the mxe.int.webappurl
in the System Properties application. The global administrator configures this value.
Service | URL |
---|---|
Object structure service | http://hostname:port/meaweb/os/object structure name |
Enterprise service (bypassing queue) | http://hostname:port/meaweb/es/extsysname/enterprise service name |
Enterprise service (through the queue) | http://hostname:port/meaweb/esqueue/extsysname/enterprise service name |
Standard service | http://hostname:port/meaweb/ss/standard service name |
Web services
Integration web services are homogeneously deployed across all the server members in the cluster. Web service access for a cluster is the same as for a single server, except that the web service URL and Web Service Definition Language (WSDL) URL point to the cluster instead of to a specific server in the cluster.
The following properties must point to the cluster URL:
- Web application URL
mxe.int.webappurl
- UDDI registry inquiry URL
mxe.int.uddiinurl
- UDDI registry publish URL
mxe.int.uddipuburl
The global administrator configures these system properties.
The URL to access a web service is http://hostname:port/meaweb/services/web service name. The meaweb variable in the URL represents the value you specify for the mxe.int.webappurl
in the System Properties application. The global administrator configures this value.