How do I interpret the MDUS log?
sdg.marinusvz
2012-02-14 09:42
The most important part is the last column: the Result Message. For example, if it cannot identify the MDUS, you can expect the message: 'CANNOT IDENTIFY PNPSCADA MDUS ENTITY'.
The other various columns are more information about the web service call.
The web services between Plug and Play Scada and SAP utilizes SOAP, in message mode. That means that it doesn't really act like a remote function call, that returns a value, but more like an email, that basically 'sends and forgets'. If there is a reply to a 'message', it will be in a seperate message that is sent afterwards.
A reply message will have a UUID in the Reference UUID column. Otherwise it is a 'first' message in a conversation.
The UUID is to uniquely identify each message. The Reference UUID can be looked up in the UUID field to see which message happened before the one with the Reference UUID.
The UUID is essentially a big random number.
The Direction shows whether the message travelled from SAP to Plug and Play Scada (MDUS); or vice versa.
The LOG time is when Plug and Play Scada logged the message. The CreationDateTime is when the message was created (e.g. in SAP).
The Source IP is where the message came from (172.XXX.XXX.XXX is the SAP Production PI server); and the Destination IP (e.g. localhost is Plug and Play Scada) is where the message is headed.
Function is the SOAP function being called. Functions do various functions, e.g. add smart meters to MDUS, add billing registers to MDUS, delete the same from MDUS, create meter reading documents, etc.
Depending on the function, there are various other parameters, e.g. the meter serial number, or the SAP specific device id, or the meter reading document number, etc. To see these additional fields, click on the link under UUID. That will display the fields exactly as SAP has named them.
The UUID is useful to give the people in the SAP department, as well as various other fields like meter reading document number etc.