Java EE Application Client deployment plan
Java EE application client modules run in client container and also have access to server environment. Usually, Java EE client applications are created to administer the running enterprise applications in the server. Client modules run in a separate JVM and connect to enterprise application resources but have access to all the application resources in standard Java EE way.
The Java EE client module requires application-client.xml as deployment descriptor and geronimo-application-client.xml as deployment plan. In the
application-client.xml, the required ejb names, security role names, resources names etc., are declared while in
geronimo-application-client.xml, the declared names are mapped to actual resources in server.
The following is the deployment descriptor of the Java EE application client module that looks up an ejb and calls a method on it. The ejb converts the Indian Rupess (Rs.) into American Dollars ($). The client sends a double value which is Indian Rupees to ejb. The ejb returns equivalent American Dollars as double value.
The application client declares the ejb name
Following is the corresponding deployment plan of the Java EE client module.
Observe the various xml elements and schemas to which they belong. The plan defines the client environment and the server environment configurations. The server environment configuration runs in the server where as the client environment configuration runs in the client JVM. In the above plan, the ejb name
ejb/Converter is mapped to
ConverterBean ejb in the
The below is the client code that looks up the ejb and calls the method on it.
META-INF/MANIFEST.MF file should contain the following entry for the client to run.
The Java EE client is created by packaging
META-INF/MANIFEST.MF files into a jar file.
The following command illustrates the packaging.
The following commands illustrates the deployment and running of the client module.