Create locally defined objects for message destination references and message destinations

 

Before you begin

After developing an application client, deploy this application on client machines. Deployment consists of pulling together the various artifacts that the application client requires.

The Application Client Resource Configuration Tool (ACRCT) defines resources for the application client. These configurations are stored in the application client .ear file. The application client run time uses these configurations for resolving and creating an instance of the resources for the application client.

Note: This task only applies to J2EE application clients. Only perform this task if you configured your J2EE application client to use resource references.

 

Overview

When a local object definition is created using the ACRCT, the JNDI name of the local object definition points to the reference for which the local object definition applies. The object might be a resource-ref, resource-env-ref or message-destination-ref. If the message-destination-ref has a message-destination-link, then point the local object definition to the message-destination. Local object definitions either point to the message-destination-ref (if the message-destination-ref has no link) or to the message-destination (if the message-destination-ref has a link). Any local object definitions pointing to message-destination-refs that have a link are ignored.

 

Procedure

1. Start an assembly tool such as Application Server Toolkit (AST) or Rational Web Developer, and open an EAR file.

2. Create a locally defined object.

3. Point the object to the appropriate message destination.

4. Save the EAR file.

---

 

Related Tasks

Deploying J2EE application clients on workstation platforms
Starting an assembly tool

 

---

 

 

Rational is a trademark of the IBM Corporation in the United States, other countries, or both.