If an Automated Task is Placed into a User-Defined State Then Receiver Could Not Process the Message
Last updated on SEPTEMBER 05, 2017
Applies to:Oracle Communications Order and Service Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
OSM 7.3.5 B388
Design Studio Version: 7.3.5 Build b10 for Neon3
If an automated task is placed into a user-defined state, which then has an associated external receiver, the receiver could not process the message.
Example: OSM COM not accepting Job Closure, Sodi Closure and SOM Completion notifications from SOM.
SOM sending Job Closure, Sodi Closure and SOM Completion notifications were not accepted automatically by COM even though correlation ID and responses are correct.
Below OSM Tasks are not accepting responses received from SOM and the tasks remain in Do mode.
Task Name / Task State / Process
1. Job Check In From SOM Wait / WaitForJobCheckInFromSom / JobClosureProcess [configured Message XML body as correlation]
2. SODI Check In From SOM Wait / WaitForSodiCheckinFromSOM / SodiClosureProcess [configured jmsCorrealationId as correlation]
3. SOM Completion Wait / WaitForProvisioningCompleted / SOMCompletionProcess [configured Message XML body as correalation]
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