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.
Code:
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: opmn
rmi://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