The official documentation lists the following jars as requested;

• weblogic.jar
• sb-kernel-api.jar
• com.bea.common.configfwk_version.jar
• com.bea.core.management.core_version.jar
• om.bea.core.management.jmx_version.jar

Unfortunately, this list is not complete (at least for my configuration) . First thing you need is the wlfullclient.jar. This jar needs to be built before being used. In order to build it;

1. Go to $WLHOME/server/lib
2. Issue  java -jar wljarbuilder.jar

After the process completes, you should have it in the same folder.

You still need class DelegatedServiceDomainMBean in your classpath. This class resides in  sb-kernel-impl.jar.

So the final list is;

• weblogic.jar
• sb-kernel-api.jar
• sb-kernel-impl.jar
• com.bea.common.configfwk_version.jar
• com.bea.core.management.core_version.jar
• om.bea.core.management.jmx_version.jar
• wlfullclient.jar

Taken from XKCD.com

Here is what they have to say;

Compatible Changes

• adding a new WSDL operation definition and associated message definitions
• adding a new WSDL port type definition and associated operation definitions
• adding new WSDL binding and service definitions
• adding a new optional XML Schema element or attribute declaration to a message definition
• reducing the constraint granularity of an XML Schema element or attribute of a message definition type
• adding a new XML Schema wildcard to a message definition type
• adding a new optional WS-Policy assertion
• adding a new WS-Policy alternative

Incompatible Changes

• renaming an existing WSDL operation definition
• removing an existing WSDL operation definition
• changing the MEP of an existing WSDL operation definition
• adding a fault message to an existing WSDL operation definition
• adding a new required XML Schema element or attribute declaration to a message definition
• increasing the constraint granularity of an XML Schema element or attribute declaration of a message definition
• renaming an optional or required XML Schema element or attribute in a message definition
• removing an optional or required XML Schema element or attribute or wildcard from a message definition
• adding a new required WS-Policy assertion or expression
• adding a new ignorable WS-Policy expression (most of the time)

HTH.

Disclaimer: As I’ve mentioned, this is work done by the authors of the book and I’m merely sharing it. I’m also not affiliated in anyway; just liked the book

The book takes touches on many subjects and leverages different tools to demonstrate these. At times, it also deviates from what the tools offer and sets on to suggest custom solutions. The examples in the book are sufficiently complex to demonstrate subjects unlike many out there with trivial scenarios which do not in any way relate to what waits out there in the wild. I also particularly like the Process centric approach the writer takes.

I would definitely suggest this book to any serious developer working on integration. There are many good ideas to take from this book, although after reading it you’ll probably end up needing to dig deeper into these ideas.

Here is the amazon page..

My current company has a policy that expires passwords every month, therefore DB2 and WMB services that are tied to this  account to Log On needs to be changed as well. Also the broker instance(s) need to be updated with the new password for the data store. Here is a quick checklist to fix the situation. Please note that this list is not exhaustive;

1. Fix DB2 services – The easiest way to do this is switch to services view in Windows and spot the services that are failing to start. Next right click these services and from the context menu select properties. Select the Log On tab and change the password used for these services. Please note that some services use the local system account while others use a selected account and it is these services which use a selected account that fail. (I don’t know why services use a different approach as of now so if you know I would appreciate if you can tell me)

2. Next you need to fix the service password for your configuration manager. For this you need to issue amqsichangeconfigmgr <config_mgr_name> -a <password>. Start your configuration manager by issuing a mqsistart command following this.

3. The last piece you need to fix is your broker instance. For this you need to fix both service password and data source password. Issue a mqsichangebroker <broker> -a <password> -p <password>. Start your broker instance by issuing a mqsistart command.

Environment: WMB 6.1.0.4 and DB2 v9.1 on Windows XP

It’s been a long time. The past few months were pretty hectic. I haver tons of drafts for new posts including complete tutorials but I guess they will have to wait for at least another month. In the meantime here  is a small quick guide to enabling debugging for Websphere Message Broker flows. If you are like me, aside from tracing you always like a decent debugger for tracing code.

1. Install the Rational Agent Controller

Please remember that you need to choose a JDK other than the IBM JDK installed with the WMB. It is wise to choose a Java 5 JDK. This is the JDK the Rational Agent Controller uses to start a debugger instance and connect to the execution group.

2. Assign debug port to execution group and enable debugging

You need to assign a debug port to the execution group you want the debugger to attach to and enable debugging. Please remember that this can constitute a security vulnerability since the debug port should be accessible from outside.

Next you should enable debugging;

3. Go to tthe command console and shoot;

mqsichangeproperties <broker-name> -e <execution-group-name> -o ComIbmJVMManager -n jvmDebugPort -v <port-number>

4. Restart the broker

5. Restart the broker toolkit

6. Create debug configuration

Create a new debug configuration by going to Debug… / Message Broker Debug / Add…

In the new configuration first click the “Select Execution Group…” which will result in the broker toolkit to query execution groups previously configured to discover the ones which have debugging enabled. Choose the execution group you have configured. Enter the debug port you have picked and add the Source folder to the debug configuration.

7. Add breakpoints to you flow and use the debug configuration you have created to debug your flows.

Environment: Rational Agent Controller v6.0.1, Websphere Message Broker 6.1.0.4

Obviously I haven’t posted anything in a while now. The reason for this is, I have accepted a new job and now working in Switzerland (More info on this later).. Since I have relocated and didn’t have a project for the past 3 months, I didn’t have anything to post. I have recently started my new assignment which is a very cool one so expect to hear a lot more from me in the coming days.  So here is a small tip on changing the langauge settings..

In my case, I have a computer with Windows XP which has German language as it’s primary language. When I installed MQ Explorer it picked up German as it’s main language which is a showstopper for me. Fortunately it is very easy to change it back into English:

• Open <InstallDir>/Eclipse SDK30/eclipse/configuration/config.ini
• Add these two lines before eof

org.osgi.framework.language=en
osgi.nl=en_US

Reboot and there it is

Here are the details: http://www.domainlanguage.com/services/training/index.html

Luckily, it wasn’t very hard to figure out my way. After tweaking the deployment options for a while, I noticed on the third step of the deployment wizard, there was an option to modify classloading. I turned of loading of the toplink library for my app, and voila. It started working like a charm.

A quick note for the people who has no idea about this issue: The antlr.jar version required by the hibernate causes problems since a different version of antlr is included with the toplink library.

My Setup: Oracle IAS 10.1.3.3 on Linux


Exception in thread "main" java.lang.UnsatisfiedLinkError: jnidemojava.Main.nativePrint()V
at jnidemojava.Main.nativePrint(Native Method)
at jnidemojava.Main.main(Main.java:27)

After searching for long hours, inspecting the compiled DLL using Anywhere PE Viewer, etc. I found out that that GCC compiler exports function names in shared libraries with a suffix indicating the number of bytes required to hold the arguments passed to the function which is known as name mangling. Therefore, the JNI bridge cannot locate the necessary method! In order to fix this,

-Wall -D_JNI_IMPLEMENTATION_ -Wl,--kill-at

should be added to compiler options during compilation of the DLL. This is explained on the MinGW frequently asked questions.

Thanks to the folks on the Java forums. Here is the link I found out about this information. There are other posible reasons causing you trouble so I’m including the link here which discusses other possible solutions.

BTW, my setup is:

Win XP + MinGW 5.1.4 + MSYS 1.0 + Netbeans 6.1 + Sun JDK 6