WebSphere Technical Exchange Web cast

There is web cast organised by IBM on Mediation Module Development in WebSphere Integration Developer (WID). The main contents that to be discussed are creating a Mediation flow, re-using Mediation logic in subflow components, XPath builder, transforming messages, invoking external services using CallOut component, and aggregating and broadcasting messages using Fan-out, Fan-in components.

Web conference URL: link

Password/Conference ID: wste27oct

View presentation click here

For more info click here

Timing : October 27, 2009 11 AM EDT

Error "org.omg.CORBA.portable.UnknownException: vmcid: 0x0 minor code: 0 completed: Maybe]"

I was bugged by this error yesterday. I didn't have any clue. I tried to do clean build on WID (WebSphere Integeration Developer). Its doesn't help. Restarted the server couple of times, removed from the server and published again no way & no improvements not even a single step forward.

Exception stack trace: javax.naming.NamingException: Error during resolve [Root exception is org.omg.CORBA.portable.UnknownException: vmcid: 0x0 minor code: 0 completed: Maybe]
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1939)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1862)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1552)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1354)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:172)
at javax.naming.InitialContext.lookup(InitialContext.java:363)
at com.ibm.ws.sca.internal.ejb.util.EJBLocator$JndiLocator.locate(EJBLocator.java:464)
at com.ibm.ws.sca.internal.ejb.util.EJBLocator.locate(EJBLocator.java:442)
at com.ibm.ws.sca.internal.ejb.util.EJBObjectFactory.createStub(EJBObjectFactory.java:72)
at com.ibm.ws.sca.internal.ejb.util.EJBStubAdapter.getStub(EJBStubAdapter.java:87)
at com.ibm.ws.sca.internal.ejb.util.EJBStubHelper.lookup(EJBStubHelper.java:89)
at com.ibm.ws.sca.internal.ejb.util.EJBStubHelper.lookup(EJBStubHelper.java:82)
at com.ibm.ws.sca.internal.binding.handler.SCAImportBindingHandler.getExportEJBStub(SCAImportBindingHandler.java:146)
at com.ibm.ws.sca.internal.binding.handler.SCAImportBindingHandler.processMessage(SCAImportBindingHandler.java:221)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:725)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1166)
at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:843)
at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.processUOWMessage(ModuleSessionBean.java:338)
at com.ibm.wsspi.sca.ejb.module.impl.ModuleSessionBean.transactionNotSupportedActivitySessionNotSupported(ModuleSessionBean.java:287)
at com.ibm.wsspi.sca.ejb.module.EJSLocalStatelessModule_43132892.transactionNotSupportedActivitySessionNotSupported(EJSLocalStatelessModule_43132892.java:131)
at com.ibm.ws.sca.internal.uow.handler.UOWStrategyImpl.transactionLocalActivitySessionFalse(UOWStrategyImpl.java:386)
at com.ibm.ws.sca.internal.uow.handler.JoinUOWHandler.processMessage(JoinUOWHandler.java:131)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:725)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1166)
at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:834)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.SCAInvocationAction.invokeSync(SCAInvocationAction.java:531)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.RetryControl.invokeByStyle(RetryControl.java:327)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.RetryControl.invokeWithRetry(RetryControl.java:221)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.ServiceInvocation.complete(ServiceInvocation.java:124)
at com.ibm.ws.sibx.mediation.flowaction.impl.sca.FlowActionFactoryImpl.create(FlowActionFactoryImpl.java:667)
at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.invokeFlowAction(ServiceInvokeMediation.java:469)
at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.mediate(ServiceInvokeMediation.java:390)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:323)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.SIBXJavaMediationPrimitive.invoke(SIBXJavaMediationPrimitive.java:93)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:419)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:345)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:419)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:345)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:419)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:345)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.SIBXJavaMediationPrimitive.invoke(SIBXJavaMediationPrimitive.java:93)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:419)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:345)
at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:217)
at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:311)
at com.ibm.ws.sibx.scax.mediation.engine.Input.invoke(Input.java:137)
at com.ibm.ws.sibx.scax.mediation.engine.RequestFlow.invokeFlow(RequestFlow.java:132)
at com.ibm.ws.sibx.scax.mediation.engine.MediationFlow.invokeRequestFlow(MediationFlow.java:135)
at com.ibm.wsspi.sibx.mediation.flow.ejb.MediationFlowBean.invokeRequestFlow(MediationFlowBean.java:230)
at com.ibm.wsspi.sibx.mediation.flow.ejb.EJSLocalStatelessMediationFlow_f5ad87fe.invokeRequestFlow(EJSLocalStatelessMediationFlow_f5ad87fe.java:127)

I got tensed thinking of the whole day, will go in vain in debugging this issue. Search didn't give us much information. Then got some clue from devworks forum. Oops there were lot of unanswered questions, few of them got some suggestions same as clean+build and deploy.

I tried a different combination, removed the project from server. (checked in the admin console). Delete all the projects which are generated by WID (App,EJB and WEB Projects). Then do a clean build and deploy application. Mostly this works b'coz it worked for me.

Note : Even after the below steps your facing the problem check in devworks or open a PMR with IBM.

BO Map Failure at runtime with null pointer Exception

The issue is the BO Map was failing at runtime giving null ponter exception at a custom map, i got really confused looked every thing in the custom map. All the value was checked to null or it is intialized to default. After doing all this again the same error kept on throwing.

Wait i remember something, i checked the right hand side BO (to BO) to which value needs to be assigned. That particular BO was null. Why this ? :-(

There is a file named map.config.properties which is located in runtimes/properties/ folder of your WID/WPS installation location. That file has an important property set which is

createChildBOsbyDefault=false




if this is set to false if there is custom mapping where the value needs to set to a particular field of the BO, at first we need to create the BO otherwise there should be move option to that particular. unless the above two occurs the BO will be always null. If you try to assign a value to field in the BO. It will throw null pointer exception (check the above screenshot)

In order to overcome the issue, before doing a custom assign to variable to the BO, first create that BO or make a move. The move should be always before the custom assign (exceution order) check the below screen shot

using promoted properties websphere enterprise service bus aka ESB

The concept of the promoted property is dynamic change without restarting or reinstalling the application again. ESB is used mostly in integeration space. Each and every down time of app change counts. This is very good feature. The implemenatation example goes like this.

For example there is two type of implementations which will be used in the mediation flow, only one of the implementation will be used which one to use will can be configured using the promoted property.


Use "MessageFilter" primitive. In the details select the distribution as "First" . And in the filters tab using xpath create two terminals "match1" and "match2".Click on the promoted properties you can see the filter property is promoted field. select the two field and give alias name different.

Wire the "match1" terminal to one application and "match2" to other application.


Deploy the application. Log in to the admin console. Go the sca modules. This will display all the applications deployed in the server.Select the application and then select mdoule properties there you can see your two properties



Give the value such that it passes one condition (it will use one application at a time). If you gave both the conditions as true. since you have given distribution as first. The first condtion matched terminal will be fired.

If you want all the terminals to be fired then set the distribution property as "All". It will the check all the conditions and fires which ever matching

Calling Stand alone reference from an EJB

It is as simple as mentioned, calling stand alone reference from an EJB. Create an EJB project let us use stateless session bean here as an example. In the EJB bean add the method which you want to call and use the piece of below code.

ServiceManager serviceManager = new ServiceManager();
(interface) service= (interface)serviceManager.locateService("");

After the lookup, with the help of service call the interface
and the operation with the parameters

service.operationname(parameters);

Add the newly created EJB project to your BEPL/Mediation Module App or project.
While creating the EJB project itself you will see option for
specifying App project,At the place use the ModuleApp Project Name.

For testing the EJB, use universalTestClient http://localhost:9080/UTC/

Business Process not deploying (com.ibm.bpe.util.VersionInfo.(VersionInfo.java:52))

I was trying to publish the application (Business process) module in WID to the server. The server was kept on throwing the error
000000c1 SystemErr R java.lang.NullPointerException 000000c1 SystemErr R at java.util.StringTokenizer.(StringTokenizer.java:197)
000000c1 SystemErr R at java.util.StringTokenizer.(StringTokenizer.java:219)
000000c1 SystemErr R at com.ibm.bpe.util.VersionInfo.(VersionInfo.java:52)
00000c1 SystemErr R at com.ibm.bpe.util.VersionInfo.(VersionInfo.java:47)
000000c1 SystemErr R at com.ibm.bpe.management.application.DeploymentTargetContext.initNodeVersionMap(DeploymentTargetContext.java:565) 000000c1 SystemErr R at com.ibm.bpe.management.application.DeploymentTargetContext.(DeploymentTargetContext.java:98)
000000c1 SystemErr R at com.ibm.bpe.management.application.AbstractDeploymentTask.getDeploymentTargetContexts(AbstractDeploymentTask.java:260) 000000c1 SystemErr R at com.ibm.bpe.processarchive.SCDLProcessComponentConfigureTask.performTask(SCDLProcessComponentConfigureTask.java:301) 000000c1 SystemErr R at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262)
SystemErr R at java.lang.Thread.run(Thread.java:810)

Then i found that i was trying to publish a module to ESB server. I started the websphere process server and published the project. It was successfully published and started. BPEL modules cannot be published on ESB. If you are getting this error first check this and add it to your checklist

Mediation(.mfc) file could not open using Websphere Integeration Developer aka WID

"Unable to create this part due to an internal error,Reason for the failure: An unexcpected exception was thrown" This was the error i got when i opened my mediation flow in WID. I didn't have clue searched and found nothing. Then started looking seriously into the error. One of my collegue got the same error earlier and he solved it by taking previous version from reposirty, he too started getting the same error.The error said Java.lang.NullPointerException at com.ibm.wbit.sib.mediation.flow.ui.tray.editparts.ReferencePartnerTrayEditPart.getModuleChildren(Unknown Source).

Look at this error "ReferencePartner" that is the clue. We saw a pattern here and found something. It seems that the other collegue deleted the an interface. The deleted interface was having a reference in mediation flow. So when iam trying to open i started getting the above error. I manually created the interface and did a clean build. It worked we are able to open the mediation flow. So here is the thumb rule guys if you have decided to delete any interface check whether it has been used in some other components/module. In case if its mediation be carefull, check the reference partner. If its there delete it from your mediation module and go ahead with your final deletion