Testing the Integration Flows
The following table lists the end point URLs for respective applications in which these endpoints need to be configured. Configure the same and perform an end-to-end testing.
Integration Name
End Point URL to be Configured
Application to be Configured
Oracle Utilities NMS OFSC Admin Sync
https://OICHost:port/ic/api/integration/ic/api/integration/v1/integrations/OUTL-BA-NMS_OFSC_ADMIN_SYNC%7C01.23.1000/schedule/jobs
Scheduled base or kicked off manually from OIC.
 
OFS fields should mimic the NMS fields.
Oracle Utilities OFSC NMS Resources Sync
https://OICHost:port/ic/api/integration/ic/api/integration/v1/integrations/OUTL-BA-OFSC_NMS_RESOURCES_SYNC%7C01.23.1000/schedule/jobs
Scheduled base or kicked off manually from OIC.
 
NMS crews should show the OFS 'NMS' assigned crews.
Oracle Utilities NMS OFSC Activity Process
https://OICHost:port/ic/api/integration/ic/api/integration/v1/flows/rest/OUTL-BA-NMS_OFSC_ACTIVITY_PROCES/1.0/orders
Create an event in NMS and this will trigger this integration.
 
Make sure the NMS ces_parameters have been setup.
Oracle Utilities NMS OFSC Activity Async Processor
https://OICHost:port/ic/api/integration/ic/api/integration/v1/flows/rest/OUTL-BA-NMS_OFSC_ACT_ASYNC_PROC/1.0/orders
The above test will also trigger this integration and the activity should be in OFS if successful.
Oracle Utilities NMS OFSC Ping
https://OICHost:port/ic/api/integration/v1/flows/oracleutilities/OUTL-BA-NMS_OFSC_PING/1.0/ping
When NMS is starting up it will call this integration.
 
Make sure the NMS ces_parameters have been setup.
Oracle Utilities NMS OFSC Chat Notification
https://OICHost:port/ic/api/integration/ic/api/integration/v1/flows/rest/OUTL-BA-NMS_OFSC_CHAT_NOTIFICATN/1.0/chatNotificaiton
This integration will be triggered when the chat flag has been set in the lookup and an error occurs.
 
It can be tested from the TEST menu or postman with:
{
"instanceId": "11111",
"recipients": ["ofsUserExternalId"],
"errorCode": "500",
"message": "Testing the chat integration"
}
 
Leave recipients off and it will use the in lookup configured default dispatcher.
Oracle Utilities NMS OFSC Attachment
https://OICHost:port/ic/api/integration/v1/flows/rest/OUTL-BA-NMS_OFSC_ATTACHMENTS/1.0/process
After NMS to OFS flow has been confirmed. Add an attachment into an NMS Event and these will be sent to the OFS activity.
Oracle Utilities OFSC NMS Activity Create
https://OICHost:port/ic/api/integration/v1/flows/ofsccloudadapter/OUTL-BA-OFSC_NMS_ACTIVITY_CREATE/1.0/notify
As OFS is event based, there is no need to configure the integration endpoint URLs. Subscription for the event will be created once the respective integration is activated. Assign an NMS Event to 2 crews will trigger this integration via OFS or create a linked activity in OFS.
Oracle Utilities OFSC NMS Activity Update
https://OICHost:port/ic/api/integration/v1/flows/ofsccloudadapter/OUTL-BA-OFSC_NMS_ACTIVITY_UPD/1.0/notify
As OFS is event based, there is no need to configure the integration endpoint URLs. Subscription for the event will be created once the respective integration is activated.
 
Making a change to the OFS activity such as start will kick off this integration.
Oracle Utilities OFSC NMS Event Details Update
https://OICHost:port/ic/api/integration/v1/flows/ofsccloudadapter/OUTL-BA-OFSC_NMS_ACT_EVTDTLUPD/1.0/notify
As OFS is event based, there is no need to configure the integration endpoint URLs. Subscription for the event will be created once the respective integration is activated.
 
Making a change to the Event Details form will trigger this integration and reflect in NMS.
Oracle Utilities OFSC NMS Failed Equipment Update
https://OICHost:port/ic/api/integration/v1/flows/ofsccloudadapter/OUTL-BA-OFSC_NMS_ACT_FEUPD/1.0/notify
As OFS is event based, there is no need to configure the integration endpoint URLs. Subscription for the event will be created once the respective integration is activated.
 
Making a change in the Failed Equipment form will trigger this integration and reflect in NMS.
Oracle Utilities OFSC NMS Attachments
https://OICHost:port/ic/api/integration/v1/flows/rest/OUTL-BA-OFSC_NMS_ATTACHMENT/1.0/process
As OFS is event based, there is no need to configure the integration endpoint URLs. Subscription for the event will be created once the respective integration is activated.
 
Adding attachments to the OFS activity will trigger this integration and reflect in NMS.
Oracle Utilities OFSC NMS Resource Create Update
https://OICHost:port/ic/api/integration/v1/flows/ofsccloudadapter/OUTL-BA-OFSC_NMS_RESOURCE_CR_UPD/1.0/notify
As OFS is event based, there is no need to configure the integration endpoint URLs. Subscription for the event will be created once the respective integration is activated.
 
When the OFS crew, such as adding a mobile phone, is updated by the administrator it will trigger this integration and reflected in NMS.
Oracle Utilities OFSC NMS Resource Route
https://OICHost:port/ic/api/integration/v1/flows/ofsccloudadapter/OUTL-BA-OFSC_NMS_RESOURCE_ROUTE/1.0/notify
As OFS is event based, there is no need to configure the integration endpoint URLs. Subscription for the event will be created once the respective integration is activated.
 
When the OFS crew activated its queue, it will trigger this integration and be reflected in NMS.
Oracle Utilities OIC OFSC Find Resource Bucket
https://OICHost:port/ic /ic/api/integration/v1/flows/rest/OUTL-BA-OIC_OFSC_RESOURCE_BUCKET/1.0/resourceBucket
This is an internal OIC call and will be triggered by the previous Oracle Utilities OFSC NMS Resource integrations to find the NMS instance.