A special authentication for connection to Infor Mongoose can also be selected.
Note that all the original event information is sent together with this additional message as a JSON message linked to the web service call.
From both a performance and volume perspective, it is important that the filters are defined correctly and thoroughly tested in an environment with fewer transactions than a production environment. Since a normal M3 environment generates several hundred events per second, poorly defined filters can quickly generate massive amounts of alert messages.
An error log is connected to the web service call. Erroneous calls are logged with reason sent back from the receiver, the primary key of the event as well as the function resulting in the original event. Based on this information, the originating action can be reprocessed if required when the problem has been corrected.
An alternate way to troubleshoot is to turn on the concept log for the autojob in the server view, or admin pages in a cloud environment. Once activated, generate a new event and then view the concept log written to the autojob log. Every validation performed within the autojob is written to the log as a readable text.