[rafikki]

Hi, when I set up a External System for BPEL, and then try to send an interface transmission to that external system I get the error below. I do not think the problem lies with BPEL, since I get the error even if I use an IP adress that doesn't exist. Please help me! ;-)

Rafikki

CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSMISSION OUTBOUND: OTM failed to send BPEL transmission 4 from 10.0.0.11 to Provider opmnrmi://10.0.0.14:6003:OC4J_BPEL/orabpel, Flow xyz with the following Exception: java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused; nested exception is: java.net.ConnectException: Connection refused [Root exception is java.net.ConnectException: Connection refused] at com.evermind.server.rmi.RMIContext.lookup(RMIConte xt.java:16 at javax.naming.InitialContext.lookup(InitialContext. java:347) at com.oracle.bpel.client.util.BeanRegistry.lookupDom ainManagerBean(BeanRegistry.java:21 at com.oracle.bpel.client.auth.DomainAuthFactory.auth enticate(DomainAuthFactory.java:83) at com.oracle.bpel.client.Locator.(Locator.java:140) at com.oracle.bpel.client.Locator.(Locator.java:111) at glog.util.bpel.BPELEvent$Listener.doPost(BPELEvent .java:186) at glog.util.bpel.BPELEvent$Listener.trigger(BPELEven t.java:145) at glog.util.event.MemoryEventQueueRunnable.processEv ent(MemoryEventQueueRunnable.java:111) at glog.util.event.MemoryEventQueueRunnable.run(Memor yEventQueueRunnable.java:70) at glog.util.event.EventThread.run(EventThread.java:7 9) at java.lang.Thread.run()V(Unknown Source) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Ljava.net.I netAddress;II)V(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:15 at java.net.Socket.connect(Socket.java:461) at java.net.Socket.connect(Socket.java:411) at java.net.Socket.(Socket.java:310) at java.net.Socket.(Socket.java:154) at com.evermind.server.rmi.RMIConnection.connect(RMIC onnection.java:2346) at com.evermind.server.rmi.RMIConnection.lookup(RMICo nnection.java:1800) at com.evermind.server.rmi.RMIServer.lookup(RMIServer .java:676) at com.evermind.server.rmi.RMIContext.lookup(RMIConte xt.java:149) ... 11 more ". java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused; nested exception is: java.net.ConnectException: Connection refused [Root exception is java.net.ConnectException: Connection refused] at com.evermind.server.rmi.RMIContext.lookup(RMIConte xt.java:16 at javax.naming.InitialContext.lookup(InitialContext. java:347) at com.oracle.bpel.client.util.BeanRegistry.lookupDom ainManagerBean(BeanRegistry.java:21 at com.oracle.bpel.client.auth.DomainAuthFactory.auth enticate(DomainAuthFactory.java:83) at com.oracle.bpel.client.Locator.(Locator.java:140) at com.oracle.bpel.client.Locator.(Locator.java:111) at glog.util.bpel.BPELEvent$Listener.doPost(BPELEvent .java:186) at glog.util.bpel.BPELEvent$Listener.trigger(BPELEven t.java:145) at glog.util.event.MemoryEventQueueRunnable.processEv ent(MemoryEventQueueRunnable.java:111) at glog.util.event.MemoryEventQueueRunnable.run(Memor yEventQueueRunnable.java:70) at glog.util.event.EventThread.run(EventThread.java:7 9) at java.lang.Thread.run()V(Unknown Source) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Ljava.net.I netAddress;II)V(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:15 at java.net.Socket.connect(Socket.java:461) at java.net.Socket.connect(Socket.java:411) at java.net.Socket.(Socket.java:310) at java.net.Socket.(Socket.java:154) at com.evermind.server.rmi.RMIConnection.connect(RMIC onnection.java:2346) at com.evermind.server.rmi.RMIConnection.lookup(RMICo nnection.java:1800) at com.evermind.server.rmi.RMIServer.lookup(RMIServer .java:676) at com.evermind.server.rmi.RMIContext.lookup(RMIConte xt.java:149) ... 11 more ". at com.oracle.bpel.client.auth.DomainAuthFactory.auth enticate(DomainAuthFactory.java:95) at com.oracle.bpel.client.Locator.(Locator.java:140) at com.oracle.bpel.client.Locator.(Locator.java:111) at glog.util.bpel.BPELEvent$Listener.doPost(BPELEvent .java:186) at glog.util.bpel.BPELEvent$Listener.trigger(BPELEven t.java:145) at glog.util.event.MemoryEventQueueRunnable.processEv ent(MemoryEventQueueRunnable.java:111) at glog.util.event.MemoryEventQueueRunnable.run(Memor yEventQueueRunnable.java:70) at glog.util.event.EventThread.run(EventThread.java:7 9) at java.lang.Thread.run()V(Unknown Source) Caused by: java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused; nested exception is: java.net.ConnectException: Connection refused [Root exception is java.net.ConnectException: Connection refused] at com.evermind.server.rmi.RMIContext.lookup(RMIConte xt.java:16 at javax.naming.InitialContext.lookup(InitialContext. java:347) at com.oracle.bpel.client.util.BeanRegistry.lookupDom ainManagerBean(BeanRegistry.java:21 at com.oracle.bpel.client.auth.DomainAuthFactory.auth enticate(DomainAuthFactory.java:83) at com.oracle.bpel.client.Locator.(Locator.java:140) at com.oracle.bpel.client.Locator.(Locator.java:111) at glog.util.bpel.BPELEvent$Listener.doPost(BPELEvent .java:186) at glog.util.bpel.BPELEvent$Listener.trigger(BPELEven t.java:145) at glog.util.event.MemoryEventQueueRunnable.processEv ent(MemoryEventQueueRunnable.java:111) at glog.util.event.MemoryEventQueueRunnable.run(Memor yEventQueueRunnable.java:70) at glog.util.event.EventThread.run(EventThread.java:7 9) at java.lang.Thread.run()V(Unknown Source) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Ljava.net.I netAddress;II)V(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:15 at java.net.Socket.connect(Socket.java:461) at java.net.Socket.connect(Socket.java:411) at java.net.Socket.(Socket.java:310) at java.net.Socket.(Socket.java:154) at com.evermind.server.rmi.RMIConnection.connect(RMIC onnection.java:2346) at com.evermind.server.rmi.RMIConnection.lookup(RMICo nnection.java:1800) at com.evermind.server.rmi.RMIServer.lookup(RMIServer .java:676) at com.evermind.server.rmi.RMIContext.lookup(RMIConte xt.java:149) ... 11 more ". at com.oracle.bpel.client.util.BeanRegistry.lookupDom ainManagerBean(BeanRegistry.java:232) at com.oracle.bpel.client.auth.DomainAuthFactory.auth enticate(DomainAuthFactory.java:83) ... 8 more

[chrisplough]

Rafikki,

This error, identified by the following string is a fairly generic error, but basically means that for some reason or another, OTM is not able to connect to the BPEL server using the URL specified in your external system.

java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused

This could be for several reasons:

• Your BPEL URL specified in the external system is wrong. The default is usually: opmnrmi://bpel.company.com:6005:OC4J_BPEL/orabpel
• One of the other parameters in your external system is wrong, for instance, the User Name, Password, BPEL Domain, BPEL Flow, or BPEL Operation.
• Your BPEL Server is not running (I'm sure you've checked this one by logging into the BPEL Console, though)
• There is a firewall either on the network or on the BPEL Server OS that is blocking access to the specified ports. This happens often on Linux and Win32, as the OS firewalls are enabled by default.
• The OTM/EBS BPEL Suitcases are not deployed on your BPEL Server.
• Also, if you're running OTM v5.5 CU2, the BPEL options in the External System are different and some people have had better luck with using Web Services instead of a straight BPEL connection.

I'm sure there are other reasons, but I can't think of them right now. Please give these a try and let us know if any of them help.

Hope this helps!

--Chris

[rafikki]

Hi, thanks for the help. But I still can't get it to work. Maybe I can give you some more info on my current situation:

• I dont think the BPEL URL specified in the external system is wrong. It's opmnrmi://10.0.0.14:6003:OC4J_BPEL/orabpel which is the URL found in the context.properties file on the BPEL server.
• I cant think that the parameters in my external system is wrong. And if it was, wouldn't it give a error such as "incorrect password" Also what worries me is I get the SAME error even if I give any IP adress or ANY username, password or parameters.
• Jip, BPEL Server is running.
• No firewall. I can telnet to 10.0.0.14 6003 without an error from the OTM box.
• I'm not sure what you mean by the OTM/EBS BPEL Suitcases? Do you mean the BPEL Flow service that I call? Well that is deployed.
• I am running OTM v5.5 CU2, and I have had some luck using webservices. The problem is that when I use webservices, the XML info isn't received correctly by the Flow service. I think the BPEL flow service has been written to receive a XML directly from BPEL. The flow services we used was created by oracle.

Lastly, do you think my problem might have anything to do with: Note 359390.1 on metalink.

Thanks a lot for the help!

[chrisplough]

Hmm...

It still appears that this is a connection-related issue, because of 2 things:

1. The error you presented earlier states that the connection is being refused (you can ignore the "DomainManagerBean" portion of the error, which is generic and look further down the stacktrace for the true error.
2. If you point the external system at any IP address, you get the same error. So when it's pointed at the BPEL server, it's not even making the initial connection.

Since it doesn't appear to be working at a base level, let's take a step back and verify a couple of things:

• Have you gotten the EBS to OTM integration working correctly? Are you able to sync carriers and send deliveries over from EBS to OTM? This would verify the BPEL configuration and since EBS is the data master, we should start there anyways.
• By BPEL Suitcases, I meant the BPEL deployment jars (WshReceivePShipmentFromOtm, WshSendDlvyToOtmService, WshSendItemRefDataToOtm, etc). I just want to ensure that all of these (8 total, including the PO/AP integration flow) are deployed onto your BPEL server.
• You may want to consider WebServices instead. For all of our CU1 installs, we utilized straight BPEL communication, however in CU2, they changed the BPEL layout form in the External System, making it impossible to duplicate the old settings. Those who had integration working in CU1 and upgraded to CU2 were fine, but all of our clients who started fresh with CU2 had to utilize WebServices.
• If you do use WebServices, you'll need to manually add a couple of elements back into the default outbound XML. This is a known issue that was introduced in OTM v5.5 CU2. Unfortunately, I can't find the Doc ID immediately, but if you're not able to find it - let me know and I'll look it up.

I don't believe it's related to the error in Note 359390.1 (that's appears to be an RMI Context lookup exception, rather than a Connection Refused exception), though I'm glad that you searching Metalink.

Hope this helps!

--Chris

[rafikki]

OK, firstly I am currently working with a guy that said you might know him. He joined us today to help us out, but more on the functional side. Oliver Marx? He also said that you are the right guy to speak to.. :-)

• Yes, I can sync carriers and send deliveries over from EBS to OTM, and it works good.
• BPEL suitcases thats deployed: WshSendTxnToOtmService, WshReceivePShipmentFromOtm, WshSendDlvyToOtmService, WshSendItemRefDataToOtm, WshSendLocRefDataToOtm, WshSendRefDataStlToOtm, WshSendTripToOtmService, PoSendPoToOtm and OtmVoucherToOracleApInvoice.
• We are using CU2. I have tried webservices and got it to start the BPEL process, but the data mapping fails. (I think this is because of an extra tag in the XML when using webservices) so I would really appreciate it if you can find that doc! I will also look for it in the meantime.

Lastly, would it maybe possible for me to contact you directly by email? I would really appreciate it since you are the first person I have come across that can actually help me, and we are really struggeling on this side. You can contact me at marinuss@bluestrata.co.za

Thanks a LOT for the help!
Marinus

[chrisplough]

Marinus,

Yep - he's (Oliver) one of us old G-Log guys - I remember him well. Please tell him that I said, "Hi!"

• Okay - glad the carrier sync works and that you're able to send deliveries from EBS to OTM - at least that proves that base integration is working.
• Yep - those are all of the BPEL Suitcases.
• I definitely think that the Web Services fix will help you - I need to find that. We've been doing so much work with EBS and OTM lately that I have a huge pile of notes to sort through

I'll send you an email, so that we can discuss directly - however I'd still like us to post updates to this forum, so that others can benefit. That's the why I started these forums in the first place

Thanks!
--Chris

[chrisplough]

Just for everyone's benefit, here's the information that I sent to Marinus:

Okay - I couldn't find the original doc, but I was able to put together a list of steps:

1. 5.5CU2 had some material changes to XML integration configuration
2. 5.5CU2 BROKE the standard integration mapping between OTM and EBS - only impacting a newly configured instance not one that was upgraded from CU1
3. To update the XML mapping, navigate to Business Process Automation > Power Data > Out XML Profiles
4. Search for and edit the XML.MIN framework
5. Add the following fields to XML.MIN: Release/ReleaseRefnum and Release/ReleaseStatus
6. This is a known OTM bug 6141674.993
7. Now add the same fields to GLOG.MIN, as that's the one utilized by the OTM > EBS BPEL communication.

BTW - I believe this may be fixed in OTM v5.5 CU2 RP (Rollup Patch) 1.

Hope this helps!

--Chris