Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Order and Service Management (Communications Industry) (MOSC)

OSM 7.3.x Fallout Management: Automation Execution Errors

Dec 30, 2015 4:21AM edited Dec 30, 2015 4:22AM in Order and Service Management (Communications Industry) (MOSC)

Scenario

Automation sender or receiver throws an exception
- Unable to deliver JMS message
Target destination unavailable
- XQuery/XSLT throws an exception
Automation/Order/TaskContext API invocation results in an exception
- Custom Java plug-in throws exception

Automation Exception Management

Every automation plug-in executes within a transaction context
- Transaction begins when a message is picked up for processing off a JMS destination
- Internal plug-ins are triggered from oms_events
OSM generates messages for oms_events when automation tasks are ready to execute
- External plug-ins are triggered from either a custom JMS destination or oms_events
External systems send responses to these receiver destinations

Tagged:

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

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

Category Leaderboard

Top contributors this month