Introduction
This document describes how the integration Web Service should be implemented by the customer so that the MPS Portal can communicate with the system being integrated.
The Web Service must be implemented in accordance with the methods described below so that the MPS Portal can execute them when an event is created or modified in the MPS Portal. It must also be published on a server with an IP address or domain name that the server can access. After publication, the partner must configure the address where the Web Service was published in the actions to be executed by the MPS Portal.
The name of the virtual folder where the Web Service will be published and the name of the asmx class can be changed, but it is recommended to use the same ones found in the sample project.
Methods that can be implemented as needed
|
Method |
Description |
|
Will be called by the MPS Portal whenever a printer event is opened or reopened. Implementation of this method in the Web Service is mandatory |
|
|
Will be called by the MPS Portal when a printer event is closed |
|
|
Will be called by the MPS Portal when a printer event is marked as Pending Resolution |
|
|
Will be called by the MPS Portal when a printer event is ignored |
|
|
Will be called by the MPS Portal when a printer event is commented on |
|
|
Will be called by the MPS Portal whenever a system event is opened or reopened |
|
|
Will be called by the MPS Portal when a system event is closed |
|
|
Will be called by the MPS Portal when a system event is marked as Awaiting Resolution |
|
|
Will be notified by the MPS Portal when a system event is ignored |
|
|
Will be notified by the MPS Portal when a system event is commented on |
Important
During implementation, it is extremely important to observe the case sensitivity of the method names created in the Web Service.
Example of Web Service Implementation
Click here for an example of how to implement the Web Service to receive notifications from the MPS Portal.