Hi
I am using weblogic JMS queue in my webMethods application.
I need the configuration details of JNDI provider alias and JMS connection alias at webMethods side for sending message into weblogic JMS queue.
Thanks in advance
Avik
Hi
I am using weblogic JMS queue in my webMethods application.
I need the configuration details of JNDI provider alias and JMS connection alias at webMethods side for sending message into weblogic JMS queue.
Thanks in advance
Avik
I have configured and presently getting the following error during JNDI lookup at Test Lookup.
weblogic/security/service/SubjectManagerImpl
I used the following during JNDI configuration
[TABLE=“class: tableView”]
[TR]
[TD=“class: heading, colspan: 2”]JNDI Provider Alias
[/TD]
[/TR]
[TR]
[TD=“class: oddrow-l”]JNDI Alias Name[/TD]
[TD=“class: oddrowdata-l”]:WebLogic_JNDI_Provider[/TD]
[/TR]
[TR]
[TD=“class: evenrow-l”]Description[/TD]
[TD=“class: evenrowdata-l”]:JNDI for WebLogic Provider[/TD]
[/TR]
[TR]
[TD=“class: oddrow-l”]Initial Context Factory[/TD]
[TD=“class: oddrowdata-l”]:weblogic.jndi.WLInitialContextFactory[/TD]
[/TR]
[TR]
[TD=“class: evenrow-l”]Provider URL[/TD]
[TD=“class: evenrowdata-l”]:t3://:7001[/TD]
[/TR]
[TR]
[TD=“class: oddrow-l”][/TD]
[TD=“class: oddrowdata-l”][/TD]
[/TR]
[TR]
[TD=“class: evenrow-l”]If any one has any solution please provide me
Thanks
Avik [/TD]
[TD=“class: evenrowdata-l”]
[/TD]
[/TR]
[/TABLE]
run the following in command prompt
…\BEA103\wlserver_10.3\server\bin>setWLSEnv.cmd
…\BEA103\wlserver_10.3\server\lib>java -jar wljarbuilder.jar -profile wlfullclient
I created the jar using the following java environment
—————–
Java™ SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot™ 64-Bit Server VM (build 20.4-b02, mixed mode)
—————-
and running the jar using the following environment on webMethods7
—————–
jvm=w64_150
Java=jdk1.6.0_26
——————-
and I am getting “bad version # at .class” error, during JNDI test lookup, what change i need to do now ?
should I create the jar in jdk 1.5. or is there any change can I made in server.bat which solve the issue?
Thanks
Avik
The jar build might be higher than webm… So , build jar with IS java.