bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Deploying Solutions

Deploying WebLogic Integration Client Applications

WebLogic Integration provides application programming interfaces (APIs) that developers can use to create client applications. Client applications in which WebLogic Integration APIs are used can import WebLogic Integration classes, look up Enterprise Java Beans (EJBs), and so on.

This section provides information to help you deploy your WebLogic Integration client applications successfully.

JAR Files

Specify the following JAR files in the client CLASSPATH:

- %BEA_HOME%\integration\lib\wliclient.jar—Contains EJB remote interfaces, home classes, and signature classes for EJBs that have published APIs.

- %BEA_HOME%\integration\lib\wlicommon.jar—Contains classes common to server and client.

In the preceding lines, BEA_HOME is the environment variable that represents the directory in which WebLogic Platform is installed.

Requirements and Recommendations

In addition to specifying the JAR files, as described in the previous section, consider the following requirements and recommendations when you deploy your client applications:

- When the client is a simple Java application, you can specify the wliclient.jar and wlicommon.jar files in the system CLASSPATH.

- When you deploy an enterprise application such that it runs in the same Java Virtual Machine (JVM) as WebLogic Integration, you must specify the JAR files in the manifest classpath.

The J2EE specification provides the manifest Class-Path entry for a component to specify that it requires an auxiliary JAR of classes. When you create a JAR or WAR file for your application, you include a manifest file with a Class-Path element that references the required JAR files. For information about how to use this manifest file, see WebLogic Server Application Classloading in BEA WebLogic Server Developers Guide, which is available at the following URL:

>     http://e-docs.bea.com/wls/docs70/programming/classloading.html

- Although doing so is not required, we recommend that you specify the wliclient.jar and wlicommon.jar files in the manifest Class-Path for a deployment scenario in which WebLogic Integration and your WebLogic Integration client application do not run in the same JVM. By listing these JAR files in the manifest Class-Path, you can ensure that both applications are self-contained.

- You must maintain the same versions of the JAR files on the server and the client.

For information about developing BPM client applications, see Programming BPM Client Applications.