Enterprise Server Layer - J2EE Integration (Magic xpa 2.x)
The Enterprise server layer has three settings which are important for determining how the EJB interacts with the enterprise server. These settings are Initialization, License Validation, and Status Messages to the Broker.
When Gateway=5, the messaging server passed from the enterprise server is optional. If a broker exists at the specified address, it will be used for login or administration purposes. If a broker is not present, the enterprise server filters out all messages sent to the broker when Gateway=1.
The AppServer will be loaded on a port, specified in
[MAGIC_COMMS]TCP/IP.
The license can limit the number of hits or concurrent requests on an enterprise server. When Gateway=1, this task is performed by the broker. However, when EJB is supported, license validation is carried out in the enterprise server.
When the number of hits or concurrent requests is exceeded, the enterprise server will self-terminate on the next request (error 136), and subsequent hits will be returned with error 109. If the enterprise server is unable to serve a request because the number of concurrent requests was reached, it will return error 104.
For more information, see Error Types.
When Gateway=5, and the messaging server sent from the enterprise server is acknowledged as an active Broker, it will be used for the enterprise server’s logging or administration purposes. Request completion messages will not be sent as they have no request ID and are therefore meaningless to the Broker.
