Error While Processing Order "Cannot create automator javax.naming.NameNotFoundException" (Doc ID 1631668.1)

Last updated on JANUARY 05, 2016

Applies to:

Oracle Communications Order and Service Management - Version 7.2.2 and later
Information in this document applies to any platform.
**** Currency checked on 05-Jan-2016********

Symptoms

Observing these errors in the OSM logs :

2014-02-06 10:09:57,515 ERROR[ExecuteThread: '22' for queue: 'oms.automation']. Cannot create automator
javax.naming.NameNotFoundException: While trying to lookup 'automation.plugin/internal/task/Siebel_Postpaid/1.0.0.0.0/T251_Check_Post_S2K_Num_Avai/do' didn't find subcontext 'automation'. Resolved ''; remaining name 'automation/plugin/internal/task/Siebel_Postpaid/1/0/0/0/0/T251_Check_Post_S2K_Num_Avai/do'


Occurrence of this error is nondeterministic but always occurs after restarting OSM. A redeployment of the cartridges will usually help.

Steps:
1. Deploy Siebel_Postpaid cartridge.
2. Restart OSM application ( undeploy /deploy oms.ear through WebLogic Console)
3. Proceed file 'CreateNewOrder3.xml' (this new one) to create order. After this step you should see new order in the worklist.
4. Proceed file 'CompleteOrder.xml' - After doing this you should have requested error 'cannot lookup automator' logged in osm.stdout log. The order on the worklist should be in tast T202_Valid_Transf_BSS as in attached screen 'order_management.png'

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