Question

I am unable to establish connection with WebMethods using Software AG (Nirvana).

  • 1 August 2017
  • 2 replies
  • 7 views

I am unable to send the json output to WebMethods (Using Software AG - Nirvana). Placed the below jar files into the location - <FME Server Installed loaction>\\Server\\lib\\jms

1. nClient.jar

2. nAdminAPI.jar

3. nAdminXMLAPI.jar

4. nJMS.jar

Subscriptions details provided - (Protocol, Topic to Subscribe, Provider URL, Connection Factory) but when providing provider type, after clicking on OK, it disappears. Validation says successful.

Now when I am running my Job successfully from FME Server, WebMethods is not able to receive any data from FME.

Please help me if I am missing any configuration.


2 replies

Userlevel 3
Badge +13

It sounds like you are trying to add JMS support for WebMethods using Software AG (Nirvana). We don't have any experience with this software at the moment. The JMS libraries we have tested with are listed here:

https://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/Installing_JMS_Libraries.htm

There might be some members of the community that have added other JMS libraries like you're looking to do. In that case, it would be good to share some of the pertinent documentation on WebMethods using Software AG (Nirvana).

Userlevel 3
Badge +13

It sounds like you are trying to add JMS support for WebMethods using Software AG (Nirvana). We don't have any experience with this software at the moment. The JMS libraries we have tested with are listed here:

https://docs.safe.com/fme/html/FME_Server_Documentation/Content/ReferenceManual/Installing_JMS_Libraries.htm

There might be some members of the community that have added other JMS libraries like you're looking to do. In that case, it would be good to share some of the pertinent documentation on WebMethods using Software AG (Nirvana).

Here is an example of another JMS library being used with FME:

 

 

https://knowledge.safe.com/questions/31256/rabbitmq-jms-client-configuration.html

Reply