Local log for the Process Step Journal Component Each logical system that participates in the logging and evaluation of a business process (business process ID) by the Process Step Journal has its own process activity log. Services, as well as any external systems that may be connected, write the data for all relevant process steps that run in these systems into the log during Logging. The occurrence of a process step is equivalent to sending and receiving a service message that contains this process step. The log entries for a process step can contain the activity categories Service Call, Error Handling, or Event Processing.
During the Evaluation, the Process Step Journal transfers the data for the individual, local process activity logs into the Process Activity Overview . When doing so, it aggregates the collected entries into one technical status for each process step, that is, for each service message.
The process activity log contains the following technical information for the progress of the process:
Log Entry ID
The identifies the log entry uniquely.
Log entry ID of a previous log entry
In some cases this information may not be available.
Business Process ID
The business process ID groups the log entries for all process steps that belong to one cross-system business process together. At the time of evaluation, it enables the identification of log entries that belong together.
Message ID/Process Step ID
This uniquely identifies the process step (service message) on which the log entry is based.
Message ID/Process Step ID of a Predecessor
This contains the ID of the process step that initiated the previous process step. In some cases this information may not be available.
Activity Status
Together with the activity category, this specifies the processing status of an activity in the process activity log. The following values are possible: Started, Completed, and Failed.
Activity Category
The activity category provides information about whether the entry is based on a service call, error handling, or the occurrence of an event.
Process Step Description
Based on the process step description you can identify the processing contents of this step. The process step description is made up of the technical name of the service interface and the service operation of the underlying service message of each process step. For example, Event Processing.
. You may not be able to determine the process step description for entries in the activity categoryMessage Direction
This provides information about whether the logical system for the current log entry has assumed the role of the sending or the receiving system. The message direction in the log entry of a receiving system is inbound. The message direction in the log entry of a sending system is outbound.
System ID
The system ID identifies the system in which the log entry was written.
Administration Specifications
You receive the time stamp and the user name.
Technical Reference ID
This differs depending on the activity category and also contains technical specifications about the relevant underlying process step. The XI runtime environment assigns these for service calls. Example: d0e4da50-4c2a-11de-8a39-0800200c9a66
Each of the following table shows a section from the fictitious and simplified process activity logs in three systems, that participate in the processing of two process steps. In this example, Systems A and B in the role of sending systems, each send a service message to Systems B and C, which have the receiving role here, for each each process step. In one case System B has the receiving role in the other case it has the sending role, for the different process steps, S1 and S2.
Process Activity Log System A:
Log Entry ID |
Business Process ID |
Message ID/Process Step ID |
Activity Status |
Name |
Message Direction |
Activity Category |
System ID |
Time Stamp |
---|---|---|---|---|---|---|---|---|
Entry 1 |
BP1 |
S 1 |
Started |
Read Business Partner Data |
Outbound |
Service Call |
SysA |
Start Time |
Entry 1 System A has read the business partner data and sent a service message to System B regarding this data.
Process Activity Log System B:
Log Entry ID |
Business Process ID |
Message ID/Process Step ID |
Activity Status |
Name |
Message Direction |
Activity Category |
System ID |
Time Stamp |
---|---|---|---|---|---|---|---|---|
Entry 2 |
BP1 |
S 1 |
Completed |
Read Business Partner Data |
Inbound |
Service Call |
SysB |
Start Time +1 |
Entry 3 |
BP1 |
S 2 |
Started |
Read Line of Credit (Facility) |
Outbound |
Service Call |
SysB |
Start Time +2 |
Entry 2 System B has accepted the service message thereby completing the first process step.
Entry 3 It then readthe line of credit (facility) for the bank customer, and informed System C thereof by means of a service message.
Process Activity Log System C:
Log Entry ID |
Business Process ID |
Message ID/Process Step ID |
Activity Status |
Name |
Message Direction |
Activity Category |
System ID |
Time Stamp |
---|---|---|---|---|---|---|---|---|
Entry 4 |
BP1 |
S 2 |
Completed |
Read Line of Credit (Facility) |
Inbound |
Service Call |
SysC |
Start Time +3 |
Entry 4 System C has received the service message and thereby completed the process step read line of business (Facility).