PONR XML File Is Not Getting Generated In OSM 220.127.116.11.1. In Debug Mode
(Doc ID 2114260.1)
Last updated on MAY 29, 2018
Applies to:Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.
OSM upgraded from version 18.104.22.168.7 to 22.214.171.124.1
PONR_<Order_Id>.xml file is not generated in OSM 126.96.36.199.1. in Debug Mode under Domain folder. It worked fine in 188.8.131.52.7 version.
To troubleshoot order change management modelling , the PONR_<Order_Id>.xml file must be generated when debug mode is enabled and the amendment transaction happens.
Business Impact: Not able to analyze the significant changes when the order is revised. It is blocker for the analysis of failed revision orders.
STEPS TO REPLICATE
1. Login to http://hostname:portno/OrderManagement/admin/log4jAdmin
2. In the "Filter Loggers" , use "CompleteOrderHandlerEJB" as search string. Click on "Begins With" and find the entry "com.mslv.oms.handler.completeorder.CompleteOrderHandlerEJB".
3. Set the log level to DEBUG mode as seen in right side of page.
4. When revising the order, PONR_<Order_Id> should be generated under Domain folder but is not.
Expected OOTB (Out of the Box) behaviour:
PONR_<Order_Id>.xml should be generated under Domain folder.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!