Error getting Cluster Config Set URLs for uri (JDeveloper 10.1.3)

The error Error getting Cluster Config Set URLs for uri appeared when I was created Application Server Connection from JDeveloper. Application Server version 10.x. Please note that, this is a clustered environment.

The following workaround solution worked for me.

I used the IP address instead of the server name in the Host Name filed. It's worth looking at /etc/host entries to for the IP address. Retested the connection and getting this. I ignored this error. As long as you can use this Application Server Connection to create an Integration Server connection, its ok to ignore... worked for me  :-)



I find these links very helpful. Mentions some other workaround...

http://www.thisisahmed.com/tia/bpel/sslhandshakefailed.html

https://forums.oracle.com/thread/368201

Connection issue: No route to host

A nice step by step investigation and solution on this problem from OTN. Wanted to share... :)

------------------------
Hi all,

I have a problem with my BPEL process (vers. 10.1.3.4).
I am trying to call an external web service and I get the following error (I can access the web service just using its URL):

exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: No route to host

I have tried pinging the remote server with success, so I should be able to connect (no proxy issue or something like that).

I have tried looking in the BPEL logs found at:
<oracle home>/opmn/logs
<oracle home>/bpel/system/logs
<oracle home>/bpel/domains/default/logs
This did not give anything useful either.

I deploy using JDeveloper. I have checked the proxy settings here - and there are none set.

Does anybody have any ideas as to what can be wrong?
Any help or hints will be much appreciated.

Regards,
Aagaard

------------------------

Hi Aagaard,

Maybe some open doors to kick in, but you say that you're able to ping the host of the webservice and can access it using it's url. Did you test it on you development machine or on the machine that is running Application Server? Since these need not be the same (often they're not, of course) it might be that you're server might have other routes thatn your development machine.

If the remote webservice is running on http://<webserver>:<port>/webservice I would open a terminal session on the server that's running your soasuite and not only do a ping but also a:
prompt>telnet <webserver> <port>
Note there is a space in stead of a colon between webserver and port.
This way you particularly connect to the webserver using on the given port. If there is no service listening on that port you would get a connection refused error.

Regards,
Martien

------------------------
Hi Martien,

Thank you for the swift reply.

Yes, I tried pinging from both development machine and from application server. Both successful.

Tried the telnet approach and interestingly enough that failed.

[oracle@prima logs]$ telnet csc2835139 18111
Trying 172.19.205.69...
telnet: connect to address 172.19.205.69: No route to host
telnet: Unable to connect to remote host: No route to host

So I guess that means that I can access the remote machine, but that no service is listening on the given port?
Even though I can access the web service via a web browser?

Regards,
Aagaard
------------------------

Correct Answer by MartienvandenAkker  on Oct 6, 2008 10:49 AM

 

Well it could also mean that from the server which is running your applicationserver the port 18111 is blocked. So I would check with your network-managers if this port is open from your applicationserver. They should check the firewalls (if you have no control on that yourself).

Often the situation at a customer is that your development pc is at one LAN while your (development, test, acceptance, production) application server is in a datacenter on a different sub-lan. With another fire-wall. From your development PC you need to access internet-http and maybe other protocols. But these are usually forbidden on the datacenter lan. You'll have a separate route from your development lan to the datacenter. Probably the server has 2 NICs: one for the internal network and one connected to the Demilitarized Zone. Within the DMZ probably a proxy/reverseproxy configuration routes the requests from outside to your application server and visa versa. So the proxy should also be checked.

This should normally the case at a customer-site, even when its a development environment. Because you don't want to have intruders hacking into your systems, even on development. And although you might not care, the dev-env should reflect your prod-env. So it should also use a dmz with a proxy/reverseproxy setup. If it is a setup on your laptop or your home lan your setup might be simpeler. But then again you might have to cope with different firewalls. If it is all on your laptop (using VMWare for example) I would try when temporarly shutdown all Firewalls.

You told that you did not have a proxy. Does that count for both your dev-pc as well as the application server?

------------------------

Hi Martien,

You were right. I did not have access to the port from the BPEL server.
Getting access solved my problem.

Thank you very much for the assist.

Cheers,
Aagaard

 

Source: https://forums.oracle.com/thread/716347#2801592

 

Oracle SOA ESB: Quick start

The overall process and tasks required for designing the enterprise service bus are outlined in the following list. Links to step-by-step instructions are specified for each task:

1. Start the ESB Server and open Oracle JDeveloper
   The key Oracle Enterprise Service Bus design components are the ESB Server, Oracle JDeveloper, and the database that serves as the ESB Metadata Server. For information about starting ESB components, see "Starting, Stopping, and Accessing Oracle Enterprise Service Bus Components".
   
2. Create the necessary server and database connections.
   See "Creating and Testing Connections".
   
3. Create the Oracle JDeveloper applications and projects
   See "Creating Applications and ESB Projects".
   
4. Create ESB systems and, optionally, service groups.
   See "Creating ESB Systems and Service Groups"
   
5. Add or import into an ESB project.
   See "Adding Project Content" and "Importing Files into a Project".
   
6. Create the inbound and outbound services, or invoke external services.
   See Chapter 4, "Creating Inbound and Outbound Services".
   
7. Create routing services and configure the routing rules to:
   
   • Apply conditional expressions to the message instance payload
     
   • Transform the structure of the message payload
     
   • Specify where a response in a request/response scenario be sent
     
   • Specify where faulted messages be sent
   See Chapter 5, "Creating Routing Services and Routing Rules".
   
8. Register services with the ESB repository.
   See "Registering ESB Projects and Services with the ESB Server".
   
9. Sync services with the ESB Server.
   See "Syncing Services From ESB Server".

If you no longer need a service, you can remove it. See "Deleting ESB Projects".

The text above is an extract from
Oracle® Enterprise Service Bus Developer's Guide
10g (10.1.3.3.0)Part Number E10295-01
http://docs.oracle.com/cd/E11036_01/doc.1013/e10295/esb_jdev.htm

I find its a pretty short but handy overview. Hope it helps.