Skip to main content
Solved

JMS Connection to WebMethods using Software AG (Nirvana) - FMEFlow2024.1

  • October 15, 2024
  • 2 replies
  • 177 views

ebygomm
Influencer
Forum|alt.badge.img+32

Recently upgraded our Dev environment to FME Flow 2024.1 (in situ)

Previously we were connecting to WebMethods using Software AG(Nirvana)

After installation, relevant .jar files have been added to the jms directory on the server

However, there is no connectivity.

The error received is

OM.safe.fmeserver.plugin.jms.JMSClientException: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsps:REDACTED [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - 0]

This doesn’t appear to be hugely helpful as you get the exact same error if you use an incorrect provider URL. I can’t see anything in the logs that provides any additional information

All evidence points to the location being reachable (testnet connection in powershell from the server)

 

@steveatsafe - any ideas?

Best answer by ebygomm

Just to update this, in case anyone stumbles across a similar problem.

 

We got this working eventually in both FME Form 2024.1 and FME Flow 2024.1

 

It required some newer JAR files sourced from a later version of Universal Messenger, and an additional jar file that wasn’t required for our 2021 FME Server installation (jakarta.jms-api-2.0.3) along with installation of certificates to the relevant cacerts file.

 

View original
Did this help you find an answer to your question?

2 replies

ebygomm
Influencer
Forum|alt.badge.img+32
  • Author
  • Influencer
  • Best Answer
  • December 4, 2024

Just to update this, in case anyone stumbles across a similar problem.

 

We got this working eventually in both FME Form 2024.1 and FME Flow 2024.1

 

It required some newer JAR files sourced from a later version of Universal Messenger, and an additional jar file that wasn’t required for our 2021 FME Server installation (jakarta.jms-api-2.0.3) along with installation of certificates to the relevant cacerts file.

 


ebygomm
Influencer
Forum|alt.badge.img+32
  • Author
  • Influencer
  • December 10, 2024

And to get workspaces using JMSReceivers/Senders working, the jar files had to also go in the plugins directory and a different cacerts file updated...


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings