The PX Notification component Web service delivers the notification or a Mobile Originated message, to the requester endpoint, through the Access Gateway or directly to the requester endpoint.
The PX Notification component uses the Statistics Publishing Client for publishing delivery statistics in success and failure scenarios. This statistic can be used by the administrator to monitor the traffic from the back-end to the Service Implementation.
The PX Notification component adds a SOAP header called the DeliveryContext, which has information like the requester ID, the notification destination, and whether Access Gateway should be bypassed. This information is used by the Access Gateway, or it can be used by the requester to match the responses with the requests that were sent. The SOAP header can be extracted from the MessageContext for use in a SOAP handler.
Service implementations that use the PX Notification component Web service may need to ensure that the interface URL endpoints and port address pointing to the PXNotification Web service are correct.
The requester ID is the link between the requests and responses. Service implementations should include this ID in their logging for tracking purposes. When a Service implementation uses a Delivery Confirmation Callback endpoint, items such as the global transaction ID, correlation ID, action, and failure message are all sent back to the Web service implementation. This information may also be logged to keep track of the delivery status of notifications or of Mobile Originated messages.