Issue setting up Peoplesoft & openJMS Integration
Krishna. <[email protected]> Wed, 19 Sep 2007 23:01:56 -0500
| Newsgroups | gmane.comp.java.openjms.user |
|---|---|
| Message-ID | <[email protected]> |
--===============1733189568== Content-Type: multipart/alternative; boundary="----=_Part_27821_31616608.1190260916734" ------=_Part_27821_31616608.1190260916734 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Just checking in to see if anyone in this group have experience setting up Peoplesoft & openJMS integration. We are having issues on the peoplesoft side setting up the integration. If this is not the right group to post such messages please let me know. We are facing issues configuring an external node setting up openJMS integration with a 3rd party system. We created an external node with JMSTargetConnect and specified the following properties. JMSFactory to ConnectionFactory JMSProvider to openJMS JMSQueue to queuename JMSUrl to URL provided by 3rd party Above properties were set based on the info provided by Vendor. I modified the integration gateway properties file to include the following string ig.jms.JMSProvider.JNDIFactory.openJMS=org.exolab.jms.jndi.InitialContextFactory When i try to ping the node i get the following error "Integration Gateway: Invalid Queue/Topic Name" I cross checked with the vendor to make sure that Queue Name and the other info. provided to was accurate. Any ideas/thoughts on what might be wrong? Any help is appreciated. Thanks! ------=_Part_27821_31616608.1190260916734 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Just checking in to see if anyone in this group have experience setting up Peoplesoft & openJMS integration. We are having issues on the peoplesoft side setting up the integration.<br><br>If this is not the right group to post such messages please let me know. <br><br><br>We are facing issues configuring an external node setting up openJMS integration with a 3rd party system. We created an external node with JMSTargetConnect and specified the following properties.<br><br>JMSFactory to ConnectionFactory <br>JMSProvider to openJMS<br>JMSQueue to queuename<br>JMSUrl to URL provided by 3rd party <br><br>Above properties were set based on the info provided by Vendor.<br><br>I modified the integration gateway properties file to include the following string <br><br>ig.jms.JMSProvider.JNDIFactory.openJMS=org.exolab.jms.jndi.InitialContextFactory<br><br><br>When i try to ping the node i get the following error<br><br>"Integration Gateway: Invalid Queue/Topic Name"<br> <br>I cross checked with the vendor to make sure that Queue Name and the other info. provided to was accurate.<br><br><br>Any ideas/thoughts on what might be wrong? Any help is appreciated.<br><br>Thanks!<br><br><br><br> ------=_Part_27821_31616608.1190260916734-- --===============1733189568== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ --===============1733189568== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ openjms-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openjms-user --===============1733189568==--