UIM OSM Integration Issue - SAF Is Not Forwarding Message From UIM To OSM In Cluster Server (Doc ID 1500684.1)

Last updated on APRIL 03, 2017

Applies to:

Oracle Communications Unified Inventory Management - Version 7.1.2 to 7.1.2 [Release 7.1.0]
Information in this document applies to any platform.
***Checked for relevance on 23-Apr-2014***
***Checked for relevance on 3-Apr-2017***

Symptoms

UIM-OSM Integration issue - SAF is not forwarding message from UIM to OSM in Cluster Server.

UIM is getting request from OSM and processing it and generating the response but OSM is not getting response from UIM using SAF. We have configured the SAF as suggested by Oracle documentation.

OSM Version: OSM 7.0.3 with Weblogic 10.3.1
Clustered Env with Active-Active approach.

UIM Version: UIM 7.1.2 with Weblogic 9.2.3
Clustered Env with Active-Active approach.

We have configured the similar SAF for non clustered env and it is working fine but it is not working for Clustered Env.

 

Error messages observed in the UIM logs :

 

ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1350036101984> <BEA-040507> <The JMS SAF forwarder failed to connect to the remote destination "t3://x.x.x.x:7001,x.x.x.x:7002/UIM_ResponseSAF", because of javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic, failed to be authenticated.]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:53)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
    at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:670)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:466)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:373)
    at weblogic.jndi.Environment.getContext(Environment.java:307)
    at weblogic.jndi.Environment.getContext(Environment.java:277)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
    at weblogic.jndi.Environment.getContext(Environment.java:207)
    at weblogic.jms.forwarder.Forwarder.getInitialContext(Forwarder.java:352)
    at weblogic.jms.forwarder.Forwarder.connectTarget(Forwarder.java:370)
    at weblogic.jms.forwarder.Forwarder.reconnect(Forwarder.java:231)
    at weblogic.jms.forwarder.Forwarder.timerExpired(Forwarder.java:279)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: java.lang.SecurityException: User: weblogic, failed to be authenticated.
    at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:116)
    at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
.>



Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms