Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Urgent
-
Resolution: Fixed
-
Component/s: FN
-
Labels:None Labels
-
Customer:OMAN-Tel
-
Defect Category:Integration
-
Product:NEP
Description
Dear @Sara Saddik@Abir Messaikeh,
While creating BONT WO customer is facing below issue.
Its seems that its happening because of process imported meant for stagging for testing BONT SWITCHING AUOTMISATON.
Please support on urgents basis
Note:: @Sara Saddik latest process you share to upload on prod is not replacing process process which I have imported meant for staging.
<NS1:Envelope xmlns:NS1="http://schemas.xmlsoap.org/soap/envelope/">
<NS1:Header>
<NS2:Security
xmlns:NS2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<NS2:UsernameToken>
<NS2:Username>nep-api-key</NS2:Username>
<NS2:Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">
mobinets@2017</NS2:Password>
</NS2:UsernameToken>
</NS2:Security>
</NS1:Header>
<NS1:Body>
<NS3:createBONT xmlns:NS3="http://server.api.nep.mobinets.com/">
<fWOID>B2025052802</fWOID>
<bontSerialNbr>485754436905EAB0</bontSerialNbr>
<bontName>AA44_01_B650G</bontName>
<bontAlias>FM2442_01_10_081_00_AA44_01_B650G_Royal Academy of Management_MUSCAT_OMT
Fiber</bontAlias>
<bontType>B650G</bontType>
<bontVendor>Huawei</bontVendor>
<longitude>23.600044</longitude>
<latitude>58.424375</latitude>
<fUserID>global-admin</fUserID>
</NS3:createBONT>
</NS1:Body>
</NS1:Envelope>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:Security
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
soap:mustUnderstand="1">
<wsse:UsernameToken wsu:Id="UsernameToken-7e4e1a35-34c2-4a3d-94a9-16b956282ccd">
<wsse:Username>nep-api-key</wsse:Username>
<wsse:Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">
mobinets@2017</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<soap:Body>
<ns2:createBONTResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
<return>
<responseCode>1</responseCode>
<responseMessage>Transaction silently rolled back because it has been marked as
rollback-only</responseMessage>
</return>
</ns2:createBONTResponse>
</soap:Body>
</soap:Envelope>
2025-06-26 13:02:58.083 [https-jsse-nio-8451-exec-5] INFO c.m.n.api.server.AuditServiceAdvice - >>> Start calling > createBONT
2025-06-26 13:02:58.083 [https-jsse-nio-8451-exec-5] INFO c.mobinets.toolbox.app.EventProducer - Event was added to the queue: [global-admin], [CREATEBONT_API_ACTION]
2025-06-26 13:02:58.083 [Thread-4] INFO c.m.t.a.EventProducer$EventConsumer - ...consuming event [global-admin], [CREATEBONT_API_ACTION]
2025-06-26 13:02:58.091 [https-jsse-nio-8451-exec-5] ERROR c.m.n.a.s.NepFixedNetworkServiceImpl - An error occured while getting Process Mapping of null
java.lang.Exception: An error occured while getting Process Mapping of null
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
An investigation revealed misaligned Flowable expressions in the "Minimal_Switching_for_BONT_Task" in in the "Minimal Switching for BONT" task . The necessary updates have been made.
getActiveNeDetailsBontOrderResponse.cvlanIp is now ==> getActiveNeDetailsBontOrderResponse.dataInnerVlan
getActiveNeDetailsBontOrderResponse.gponDataVlanid is now ==> getActiveNeDetailsBontOrderResponse.dataVlanId
getActiveNeDetailsBontOrderResponse.gponVoiceVlanid is now ==> getActiveNeDetailsBontOrderResponse.voiceVlanId
The updated process is attached ( Minimal_Switching_for_BONT_Task.zip )
From: Shamim Ahmed
Sent: 30 June 2025 23:06
To: Natnael Asfaw <Natnael.Asfaw@mobinets.com>; Sara Saddik <Sara.Saddik@nuiva.com>; Abir Messaikeh <Abir.Messaikeh@nuiva.com>; integration <integration@mobinets.com>; Zein Trabelsi <Zein.Trabelsi@nuiva.com>
Cc: Khaled Khalil <Khaled.Khalil@nuiva.com>; Khaled Ayoubi <khaled.ayoubi@omantel.om>; Salem Dannawi <Salem.Dannawi@mobinets.com>
Subject: RE: Create BONT Integration WO issue-----------Urgent----------------------
Dear @Abir Messaikeh@Zein Trabelsi,
I'm writing to follow up on the BONT creation process. It appears that the "Create BONT" and subsequent order creation are now functioning correctly. However, the process is being interrupted at the "switching" stage.
Upon investigation, it seems that while the getActiveNeDetailsBontOrder API is returning a successful response internally, the attributes within this response are different from what was previously expected or received. This discrepancy is causing the interruption at the switching phase.
To assist with debugging and resolution, I've noted the success and failed cases below. Please let me know if you require further details on these cases.
Your urgent support in fixing this issue is greatly appreciated.
after zein patch on Saturday , order created but it was interrupted
From: Shamim Ahmed
Sent: 28 June 2025 01:50
To: Natnael Asfaw <Natnael.Asfaw@mobinets.com>; Sara Saddik <Sara.Saddik@nuiva.com>; Abir Messaikeh <Abir.Messaikeh@nuiva.com>; integration <integration@mobinets.com>; Zein Trabelsi <Zein.Trabelsi@nuiva.com>
Cc: Khaled Khalil <Khaled.Khalil@nuiva.com>; Khaled Ayoubi <khaled.ayoubi@omantel.om>; Salem Dannawi <Salem.Dannawi@mobinets.com>
Subject: RE: Create BONT Integration WO issue-----------Urgent----------------------
Dear @Abir Messaikeh@Zein Trabelsi,
Below is the successful example of BONT create workorder on prod before prod upgrade.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header />
<SOAP-ENV:Body>
<ns3:createWorkOrder xmlns:ns3="http://server.api.nep.mobinets.com/">
<woNo>B2025052703</woNo>
<appType>INSTALLATION</appType>
<woOperation>BONT Activation</woOperation>
<autoCreateTasks>false</autoCreateTasks>
<login>global-admin</login>
</ns3:createWorkOrder>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>"
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:createWorkOrderResponse xmlns:ns2="http://server.api.nep.mobinets.com/">
<return>
<responseCode>0</responseCode>
<responseMessage>SUCCESS</responseMessage>
</return>
</ns2:createWorkOrderResponse>
</soap:Body>
</soap:Envelope>[\r][\n]"
after sara patch below is the status
Dear @Abir Messaikeh@Zein Trabelsi,
While calling Create BONT API on .80 getting successful response as shown below.
But after that NEP call createWorkOrder for which which we are getting failed response that’s why
B2025052802 is not getting created.
Please support to check.
Updated process applied on PROD ( root cause a regress while executing BONT automation CR)