Diagnosis The system received a response that was not classified as an errormessage. According to the guidelines for wage data transfer, responsesthat are not error messages must be signed by the sender (here: By thedistributor to which you sent the message). The recipient must check thesignature of the response and must not further process responses with aninvalid signature in the usual way. This is most likely to affect the verification of the correctness of theresponse signature. This can be for the following reasons:
- The distributor has not signed the response, or has signed it with an
invalid signature. You can determine whether the signature is missingentirely by displaying the corresponding XML file in the process dataoverview.
- The content of the response was forged or changed, either intentionally
or unintentionally, on the way from the distributor to you.
- The distributor also coded the response
- The signature check does not work or is set up incorrectly (for example,
is checked against the incorrect certificate, or an error message wasincorrectly not identified as such).
- The PI disappeared between receipt of the response and the signature
check, or can no longer be reached.System Response The received response is saved with the process data of the current stepfor further analysis. The data from the response must not be furtherprocessed in the usual way. Procedure You can view or download the received response as an XML file in theprocess data overview for further analysis. You can use theinteroperability check to check whether all systems can be reached. Depending on the cause, contact your system administrator, thedistributor, or support. You can repeat queries on the processing status of sent wagenotifications (meaning a response with a valid signature and OrderID hasalready been received) by manually resetting the process to the "QueryStatus Again" step and restarting. If you need to resend the wage notification and a 'jobkey' element iscontained in the notification with the invalid signature in the XMLdisplay, check with the distributor whether the job should be stoppedbefore it is resent or if you should indicate the new notification as areplacement notification. To indicate the notification as a replacement notification, whenrecreating the notification enter the content of the "OrderID (ELM)"field from the notification context (select step 0 and the "Display"pushbutton) and the content of the 'ResponseID' field from thedistributor's response (use XML file display and search function) in thedata extractor's selection screen (report 'RPLELMC0'). Sending and receiving coded messages is currently only an optional wagestandard option and is not supported. In this case, ask the distributorto send the responses uncoded. (Note: In the configuration, the PIenables the activation the coding/decoding in the same way as for thesignature. This option may work, but it has not been certified andtested). Procedure for System Administration The signature check is performed by the PI. The cause can be furtheranalyzed via the security logs and the message monitor. In particular,this means that it can be checked whether the signature check or thesignature is incorrect. For the signature check to work, the correct distributor's certificatemust be imported into the key store and be configured for thecorresponding integration scenario.
|