cancel
Showing results for 
Search instead for 
Did you mean: 

very urgent Connecting weblogic queue from sap xi

Former Member
0 Kudos

Hi Experts,

I am sending the file to Weblogic queue from SAP XI. I am getting the error message. I couldn't figure out where i made a mistake. Could you please help me.

Error during channel initialization; exception trace:

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://newyork:7001: Destination unreachable; nested exception is:

java.net.ConnectException: Connection refused; No available router to destination]

at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47) ...

Advance Thanks

Ramidi

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hey

>>Destination unreachable

this clearly says you have some routing issue,please check the user id/pwd if any used,also check if the weblogic system is reacheable from SAP XI machine,secondly make sure all connections are working properly.

Thanx

Ahmad

Former Member
0 Kudos

Hi,

The connections are fine and sucessfull i and 3 rd party is able t ping..I am getting eror related to t3 protocol Ahamed are you aware of it.

Regards

Ramidi

Former Member
0 Kudos

your weblogic server is not enabled for http tunneling. you must do this for whatever you are trying to achieve...instructions here

http://e-docs.bea.com/wls/docs81/adminguide/web_server.html#111163

after this, you can use http:// instead of t3:// in your communication channel configuration. the root cause is , the client i.e. XI doesnt understand what t3 protocol is.

agasthuri_doss
Active Contributor
0 Kudos

Hi Amol Joshi,

Great, Can you Elaborate in detail..

May I know what all settings to be done... if we are sending the senda to the Weblogic Queue.

Regards

Agasthuri Doss

agasthuri_doss
Active Contributor
0 Kudos

Dear SDN Friends,

Kindly Share your Knowledge,

Regards

Agasthuri Doss

Former Member
0 Kudos

Hi Friends,

Can you help us on this problem. when we r trying to pit the message into weblogic queue. but there is some error . i mention it above the error. t3:
newyork:7001 not reachable. do we need to load any jar files . any help it's valuable.

Thank you

Ramidi

agasthuri_doss
Active Contributor
0 Kudos

Dear SDN Friends,

May I know what all settings to be done... if we are sending the data to the Weblogic Queue.

Weblogic can accept T3 protocol..From SAP XI how we can send T3 Protocol.

Regards

Agasthuri Doss

Former Member
0 Kudos

Hey

please have a look at the following

/message/600019598#600019598 [original link is broken]

also look at page 4 of the following

http://h71028.www7.hp.com/ERC/downloads/SAP%20XI%20adapters_DS.pdf

make sure you have the required jar files installed.

also try posting the question in weblogic forums too

http://forums.bea.com/bea/index.jspa

Thanx

Aamir

Former Member
0 Kudos

Hey

you may also wanna have a look at the following

Thanx

Aamir

Former Member
0 Kudos

the link specified in my earlier reply explains the setting required for http tunneling .once you do that you could access your JNDI registry using http:// instead of t:// in the provider URL.

agasthuri_doss
Active Contributor
0 Kudos

Thanks Amol,

Still some Issue I am facing....even after doing the settings you have mentioned..I missing some configuration..This is the following error I am facing...

Cna you spent some time on this following error

Error during channel initialization; exception trace: javax.naming.CommunicationException [Root exception is java.net.ConnectException: http://nyc:0000: Destination unreachable; nested exception is:

java.net.ProtocolException: Tunneling result unspecified - is the HTTP server at host: 'nyc' and port: '0000' a WebLogic Server?; No available router to destination]

at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47) ...

Regards

Agasthuri Doss

Former Member
0 Kudos

Hi,

Thank you,

When I try with http:// I am facing the error.

Error during channel initialization; exception trace: javax.naming.CommunicationException [Root exception is java.net.ConnectException

Regards

Ramidi

Former Member
0 Kudos

Thank you for all

We load SP12.

My problem was solved

Regards

Ramidi S

Answers (1)

Answers (1)

agasthuri_doss
Active Contributor
0 Kudos

Hi,

Since you are sending the messages to the 3 rd party Queue. Kindly check out whether you have mention JMS Connector information in the Visual Admin.

Regards

Agasthuri Doss