Packaging and Deploying Java Based Solutions to WebSphere Message Broker V7

Size: px

Start display at page:

Download "Packaging and Deploying Java Based Solutions to WebSphere Message Broker V7"

Gloria Morton
6 years ago
Views:

1 IBM Software Group Packaging and Deploying Java Based Solutions to WebSphere Message Broker V7 Jeff Lowrey WebSphere Message Broker L2 Support 15 September 2010 WebSphere Support Technical Exchange

2 Agenda A short overview of classloading Four methods of deploying java files BAR file Classpath Shared Classes JavaClassLoader configurable Service Q&A Thanks WebSphere Support Technical Exchange 2 of 14

3 Introduction Message Broker supports multiple transformation interfaces, including support for the Java TM programming language in the JavaCompute node. Managing the deployment of Java based solutions requires more thought and effort than ESQL or PHP based solutions. WebSphere Support Technical Exchange 3 of 14

4 Overview of classloading A class loader is an object that is responsible for loading classes. A class is a compiled java file that represents the implementation of an object. Class loaders can delegate to other classloaders. Classes are discovered from the current classloader and it's delegate. The first match found stops the lookup. WebSphere Support Technical Exchange 4 of 14

5 Broker Class loaders EGShared classloader: Loads jars from BAR files Shared classloader: Loads jars from shared-classes Broker classloader: Loads private broker classes and CLASSPATH System class WebSphere Support Technical Exchange 5 of 14

6 Packaging in the BAR file Any Java project marked as a regular Project dependency is compiled into a JAR file and added to the BAR file when a Message Flow Project is built. Any JAR file added directly to the Message Flow Project is added to the BAR file when the Project is built. Any JAR file added as an External Jar to the Java Build Path is NOT added to the Bar. JAR files can be manually removed from the BAR file with the BAR File Editor or otherwise with ZIP utilities. WebSphere Support Technical Exchange 6 of 14

7 Deploying JARs in the BAR file Pros: This is EASY to do JAR files are visible in Admin tooling No restart of Broker or EG is needed Only affects specified EGs Cons: JAR files are loaded by the EGShared classloader. This classloader is refreshed fully at each deployment. JAR files increase the size of the BAR file. This affects deployment time. deploys might fail if jar resources are locked static classes and variables might cause big problems when the hot replace is attempted. It is best to avoid using static classes and variables or spawn user threads when using this mechanism. WebSphere Support Technical Exchange 7 of 14

8 Putting JARs on the CLASSPATH Pros: It's the normal Java mechanism JARs are loaded by the Broker classloader at startup BAR files are reduced in size Cons: Not visible in Admin tooling Not logged in startup tracing May affect non-broker Java processes or Broker command line tools Affects all EGs and all Brokers under the same environment Requires a full broker restart for changes to CLASSPATH take effect. Requires an EG reload to load changed jars. WebSphere Support Technical Exchange 8 of 14

9 Putting JARs in shared-classes Pros: It's the normal Broker mechanism JARs are loaded by the Shared classloader at startup BAR files are reduced in size JAR loading is logged to service trace Cons: Not visible in Admin tooling Affects all EGs and all Brokers under the same workpath Requires an EG restart/reload for a changed class or JAR to be loaded. Only affects Broker, not the command line environment. WebSphere Support Technical Exchange 9 of 14

10 JavaClassLoader Configurable Service Pros: Straightfoward to configure Visible in Admin Tooling JavaCompute property is configurable and overrideable at deploy time BAR files are reduced in size Active only in an EG that uses it. Cons: Requires additional effort at initial creation time. Requires specific configuration in each broker Requires an EG restart/reload for a changed class to be loaded. Application-level isolation of jars and class loading WebSphere Support Technical Exchange 10 of 14

11 Summary This talk discussed different options to package and deploy Java based solutions in Message Broker. For version 7 and later, use a JavaClassLoader configurable service for Java based solutions For version 6.1 and earlier, use shared-classes for Java based solutions. WebSphere Support Technical Exchange 11 of 14

12 Additional WebSphere Product Resources Learn about upcoming WebSphere Support Technical Exchange webcasts, and access previously recorded presentations at: Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Join the Global WebSphere Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: View a webcast replay with step-by-step instructions for using the Service Request (SR) tool for submitting problems electronically: Sign up to receive weekly technical My Notifications s: WebSphere Support Technical Exchange 12 of 14

13 We Want to Hear From You! Tell us about what you want to learn Suggestions for future topics Improvements and comments about our webcasts We want to hear everything you have to say! Please send your suggestions and comments to: WebSphere Support Technical Exchange 13 of 14

14 Questions and Answers WebSphere Support Technical Exchange 14 of 14

Advanced Integration Services In IBM Business Process Manager

IBM Software Group Advanced Integration Services In IBM Business Process Manager Pratima Ahuja (pratima@us.ibm.com) Software Engineer 09/11/2012 WebSphere Support Technical Exchange Agenda What is an AIS