You can create application clients with Ant, Eclipse, and popular IDEs such as Borland JBuilder. Code your application clients as an EJB client or a JMS client. For more information, see:
Chapter 3, “Developing JMS Clients,” in the JMS Users Guide
Application clients can be packaged as a standalone JAR file or as part of an enterprise application archive (EAR) file. You can deploy the JAR file to EAServer using several tools including:
The Management Console
The deploy utility, as described in Chapter 12, “Command Line Tools,” in the System Administration Guide
The jagant and jagtool utilities
Deploying application client JAR files with the Management Console
Start the Management Console and connect to EAServer as described in Chapter 1, “Getting Started,”in the System Administration Guide.
In the Management Console, right-click the Application Clients folder in the left pane and choose Deploy. The Deploy wizard pages appear in the right pane. Fill in the Wizard settings as listed in the table below.
Setting |
Explanation |
|---|---|
File Name |
Enter the full path to the EJB-JAR file, or browse to select the file. |
Module Name |
Enter a name for the application to be created. The default is the base name of the JAR file. This name will appear in the Management Console and in configuration files. |
Overwrite If This Name Already Exists. |
Enable to overwrite an existing application client that has the same name. |
Do Validation During Deployment |
Enable to enforce validation of the XML deployment descriptor. In accord with the J2EE specification, this option is enabled by default. Disabling validation may allow you to deploy archives that have invalid XML but are otherwise correctly packaged. |
Server Name |
The name of the server to install the module to. The default is the name of the server that you are connected to. |
Install Module Into Selected Server |
Deselect if you don’t want the package installed into any server. The package must be installed in a server before clients of that server can call the components. |
Directory Name |
If you specify a directory name, EAServer creates a copy of the archive file in the specified directory. The copy is identical to the source, except that an EAServer configuration file is added to the META-INF directory. The directory must exist and be a full path or a path relative to the EAServer bin directory. |
Click Finish on the final wizard page. The Management Console deploys the EJB-JAR and shows the deployment status in the right pane. When your browser finishes downloading the status page, scroll to the bottom. You see Build Successful if everything went ok.
