OSM-AIA SAF Not Working (Doc ID 1929191.1)

Last updated on JULY 11, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.
Review relevance July 06, 2016

Symptoms

OSM-AIA SAF Integration is not working, SAF is defined in OSM WLS domain and message will be sent by SAF to AIA WLS domain.

From OSM domain,messages are seen forwarded

osm\safagents\O2A_SAFAgent\jms\jms.messages.log
####<Sep 19, 2014 1:16:56 PM IST> <> <> <1411112816092> <194924> <ID:<120829.1411112816051.0>> <> <oms_jms_module!O2A_SAFImportedDestinations!AIA_CRTCUST_OUT_JMSQ@O2A_SAFAgent@OSMAdminServer> <Stored> <osmadmin> <> <> <>
####<Sep 19, 2014 1:16:56 PM IST> <> <> <1411112816128> <310827> <ID:<120829.1411112816124.0>> <> <oms_jms_module!O2A_SAFImportedDestinations!AIA_CRTCUST_OUT_JMSQ@O2A_SAFAgent@OSMAdminServer> <Stored> <osmadmin> <> <> <>
####<Sep 19, 2014 1:16:56 PM IST> <> <> <1411112816159> <243807> <ID:<120829.1411112816051.0>> <> <oms_jms_module!O2A_SAFImportedDestinations!AIA_CRTCUST_OUT_JMSQ@O2A_SAFAgent@OSMAdminServer> <Forwarded> <<WLS Kernel>> <> <> <>
####<Sep 19, 2014 1:16:56 PM IST> <> <> <1411112816169> <899803> <ID:<120829.1411112816124.0>> <> <oms_jms_module!O2A_SAFImportedDestinations!AIA_CRTCUST_OUT_JMSQ@O2A_SAFAgent@OSMAdminServer> <Forwarded> <<WLS Kernel>> <> <> <>

But in AIA WLS domain,expected logs like below are not seen

logs/jmsServers/AIAJMSServer $ more jms.messages.log
####<Sep 22, 2014 10:16:07 AM EDT> <BEA1-000069E49AE9DAFCE545-574C53746F72655F4149415F5341465F746573745F4149414461746153746F7265> <> <
1411395367063> <932631> <ID:<491170.1410898089576.0>> <> <AIAJMSModule!AIA_CRTCUST_OUT_JMSQ> <Produced> <system> <> <> <>
####<Sep 22, 2014 10:16:07 AM EDT> <BEA1-000069E49AE9DAFCE545-574C53746F72655F4149415F5341465F746573745F4149414461746153746F7265> <> <
1411395367066> <78171> <ID:<491170.1410898163333.0>> <> <AIAJMSModule!AIA_CRTCUST_OUT_JMSQ> <Produced> <system> <> <> <>

Creating same SAF in a new OSM / AIA environment, the problem could not be re-produced, so this is not configuration issue.

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