You can configure an application client’s properties in EAServer Manager. If you have created an Enterprise archive (EAR) file using another tool and imported it into EAServer, most properties are automatically set during the import process.
Displaying the Application Client Properties dialog
To set the properties described in this section, first open the Application Client Properties dialog.
Expand the Clients folder, then highlight the icon that represents your application client.
Choose File | Application Client Properties.
Enter the application client’s general properties:
Description An optional text description of the application client.
Main Class The main Java class of the application client in dot notation; for
example, com.sybase.appclient.Myclient
.
Add references for the EJBs that the application client accesses in its code. For example, add the EJB reference ejb/acctBean in EAServer Manager and use java:comp/env/ejb/acctBean in your application client code.
“EJB references” describes how to add or configure EJB references.
Resource references are used to obtain connector and database connections, and to access JMS connection factories, JavaMail sessions, and URL links.
“Resource references” describes how to add and configure resource references.
Resource environment references are logical names applied to objects administered by EAServer, such as JMS message queues and topics.
“Resource environment references” describes how to add and configure resource environment references.
Environment properties allow you to specify global read-only data for use by the application client.
Application clients must use JNDI to retrieve environment
properties, using the prefix java:comp/env
in
JNDI lookups.
The deployment descriptor catalogs the environment properties used by the application client, as well as each property’s Java datatype and default value.
“Environment properties” describes how to add and configure environment properties.
The Java Classes tab allows you to specify classes that must be included in the Application Client’s run-time JAR file. “Configuring an entity’s custom class list” describes how to configure this setting.
The settings on the JAXP tab configure the JAXP, DOM, and XSLT parser implementations used in the application client. See Chapter 36, “Configuring Java XML Parser Support,”for more information on these properties.
The Files tab lists all the files in the application client, which are copied to %JAGUAR%\ Repository\<Application_Name>\<Client_Name> when you deploy the application EAR file. When you export the client application, the files listed on this tab, plus the EJB stubs for the application are added to the export JAR file, which you deploy on a client machine to run the application.
Copyright © 2005. Sybase Inc. All rights reserved. |
![]() |