bea.com | products | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
e-docs > WebLogic Platform > WebLogic Integration > Deploying Solutions > Deploying WebLogic Integration Client Applications |
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:
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:
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://download.oracle.com/docs/cd/E13222_01/wls/docs70/programming/classloading.html
For information about developing BPM client applications, see Programming BPM Client Applications.
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |