Chapter 9: Importing and Exporting Application Components
You can export application clients from EAServer Manager to deploy them on a client machine. You can import application clients into EAServer as part of a J2EE EAR file or an EAServer JAR file. Typically, you may want to import the EAR file, edit the application client properties, export the JAR file, and deploy and run the application on a client machine.
For information on creating and running application clients, see Chapter 10, “Creating Application Clients,” in the EAServer Programmer’s Guide.
Importing an application client
Highlight the top-level Applications folder.
To import a J2EE EAR file, choose File | Deploy | J2EE EAR. To import an EAServer JAR file, choose File | Deploy | EAServer JAR. This starts the Deploy wizard.
In the Deploy wizard, provide the following information:
Enter the path and file name of the EAR or JAR file or click Browse and select the file from the system.
Select a deployment strategy. Table 9-1 describes the deployment strategy options.
Deployment Options – check to enable:
Prompt before overwriting existing objects
Automatically generate EJB stubs and skeletons
Use interoperable naming, which configures interoperable naming URLs for the EJB Reference properties, as described in “Intervendor EJB interoperability” in the EAServer Programmer’s Guide. Select this option when your EJBs have EJB references that link to another vendor's EJB 2.0 server and you need to use the RMI/IIOP protocol for the connection.
Click Next. The Deploy wizard reads the file and creates the application client. Any errors are displayed in the status window. Review the status information, then click Close.
Exporting an application client
Expand the icon that represents your application, open the Clients folder, and highlight the icon that represents your application client.
Choose File | Export Client JAR. This starts the Export wizard.
In the Export wizard:
Enter a path for the JAR file to be created or click Browse and select the file path.
Optionally deselect the Export with EAServer XML Configuration File option if you do not want the archive to include an EAServer XML configuration file.
Specify whether to automatically generate EJB stubs. To run the JAR file on a standalone client machine, generate the stubs. If you plan to deploy the JAR file in another application server, you do not need to generate the stubs.
Click Next to continue. EAServer exports the application client. Any errors are displayed in the status window. Review the status information, then click Close.
If you make changes to EJB references, resource references, or environment properties after you export the application client, you must export the client again to update the JAR file.
|Copyright © 2005. Sybase Inc. All rights reserved.|