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 Order Creation Failure Scenarios

Dec 28, 2015 4:43AM edited Dec 28, 2015 4:43AM in Order and Service Management (Communications Industry) (MOSC)

Order Creation Failure Scenarios

Scenario 1: Message Send To OSM Web Service Queue Fails

Upstream sender receives a JMSException on MessageSender.send()
OSM and/or WebLogic is unavailable
Message ownership remains with upstream sender
- Upstream system can retry message delivery when OSM is back online

Scenario 2: Invalid Credentials

The client side receives an exception when trying to initiate context
Message ownership remains with upstream sender
- Upstream client needs to fix credentials and retry

Scenario 3: Message Send To OSM Accepted But No Order Created – Database or Other Internal Application Error

OSM retries request based on JMS redelivery limit of web service queue

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