Since it is atop a J2EE server that will have Java Engineers working with it, why not doing all the Service Bus processing in Java. It would be faster than the flowcharting plug-ins they offer now and the XSLT translations you need to do.

Update I expanded on the issue.

Update. We have the OSB running in Eclipse 3.3 and the EAR running in Eclipse 3.5; as long as they aren't started or republished at the same time they are ok. We start one and then the other. It is a pretty laborious process to get it all set up and working flawlessly. We went through a couple of days of unhelpful eclipse errors and oracle's plugins crapping out with no understanding as to why. Once we got it working we left it alone.

We have embarked upon the process of getting all our weblogic configuration into scripting as part of continuous integration. So we can build a server for any environment from our scripts and then test that the configuration is correct.

I must admit, I am struggling with WLST and JMX. I am not having a fun time of it. I thought that WLST being python/jython based I would be enjoying myself since it is probably my favorite language to work in when I am not making a living in Java. That has not been the case. The WLST environment has some weird rules that I have not fully worked out yet.

For instance the cmo object which is exposed as part of the wlstModule appears to behave differently when the WLST module is called as part of __main__ or not. MBeans are returning as None when I call them from a module, despite having the same cmo when I do a dumpVariables on them. If I run the same script as a stupid procedural program - rather than modularized - calling from main; it works.

Super, super frustrating.

I am guessing JMX was an attempt to make something SNMP like with Java and Beans. The mibs in SNMP were always a bit of a pain to work with as they changed and usually had to be defined before hand if they were to be manipulated as part of a program. It seems the same with the MBeans. They change as the cursor goes up and down the MBeans tree with the cmo reflecting whatever MBean the cursor is currently on.

To create a new Queue, you still have to know which directory you have to go to, which keywords, variables etc you have to set and so forth. It might just be easier with a fixed API to create the Queue rather than a floating MBean tree that has to be parse, navigated, etc.

I have spent a couple of days trying to create a modularized script for creating JMS queues with WLST. Time is running out and given that it is scripting I shouldn't have spent this much time on it. It expected it to be simpler. I am probable going to have to hook something up where each Queue is in its own WLST module and run as __main__.

Frustrating.

The NonCatalogLogger is in the wls-api.jar which can be found under SERVER_HOME/server/lib for Weblogic 10.3