Broker Configuration and Deployment (Magic xpa 2.x)
The broker must be aware that some of the enterprise servers are "Query-Only" and they will then be marked as such. Query-only enterprise servers can only send status information and can neither accept requests from the broker nor be assigned to requesters.
If the Broker is terminated when EJB is supported, it will send XML-based termination requests to Query-only enterprise servers.
You can load an AppServer during initialization, from command line requesters or from RQ functions.
Magic xpa must serialize or deserialize Java objects passed in the EJB request or response. This can be done by:
-
Specifying JAVA_HOME in the MAGIC_JAVA section in the Magic.ini file
-
Defining the JAVA_HOME environment variable
-
Setting the PATH environment variable to include the directory with the jvm.dll file
The Java classes used in the EJB method must be accessible to Magic xpa by including the classes or the JAR file in either:
When the enterprise server receives a request from the EJB, it automatically deserializes each Java object and passes it to the called Magic xpa program as a Java pseudo reference. The BLOB’s parameters of the program have a Java reference for each object. If the return value is a Java object, the engine automatically serializes the Java object when responding to the EJB request.
