|
Function The function module SWF_XI_WORKLOAD_BY_TIME> provides statisticalinformation about process instances, and the messages sent to orreceived by those process instances during a specific time interval,that is, information about the workload of the integration processes. The function module has the following import parameters:
IM_START_TS>: Beginning of time interval (inclusive)
IM_END_TS>: End of time interval (exclusive)
IM_SINGLE_SECTION>: Specifies whether the data is subdivided into 3600-second intervals within the specified time interval. If thisparameter has the value 'X' then the time period is not subdivided intohour intervals. The default value is space; that is, the time intervalis divided. This parameter is for internal use only (for example, tests)and must not be used in productive operation. The function module has the following export parameters:
EX_WORKLOAD_TABLE>: This parameter contains the statistical information and is of table type SWFXIWLSTATBYTIMET, which is based onthe structure SWFXIWLSTATBYTIME>. The export parameter EX_WORKLOAD_TABLE> is populated by thefunction module as follows. The structure components START_TS> andEND_TS> in each line specify the beginning and end of the righthalf-open interval. Structure component PARTY> specifies theparty, the structure component SERVICE> specifies the service, andthe structure component TASK> specifies the name of thecorresponding Workflow pattern of the process service, the statisticalinformation for which is contained in the remaining structurecomponents. TASK> alone specifies the process service uniquely, while PARTY> and SERVICE> can only do so together. Thestatistical information is based on those process instances of theprocess service that were completed during the time interval, or whichwere logically deleted. If IM_SINGLE_SECTION> is not set,START_TS> in the first entry is set to the start of the previoushour, if this is not already the case. In the following, 'interval'always refers to the process instance and not to the correspondingcorresponding step type or message delivery. The componont COUNT> for a line of EX_WORKLOAD_TABLE>contains the number of evaluated process instances. The sub component MIN> in component RUNTIME> contains theminimum runtime of a process instance in the given interval inmilliseconds. Sub component MAX> specifies the maximum runtime,sub component AVG> the average runtime, and sub component ABS > the sum of all runtimes. The runtime of a process instancecorresponds to the realtime which begins with the creation of theprocess instance and finishes when it is completed. Component DATA_ERRORS> contains the number of process instances inwhich errors were found. A process instance contains data errors if dataerrors are found in the remaining components of EX_WORKLOAD_TABLE>(see description of remaining components) or if inconsistencies arefound in the component values calculated for a process instance, forexample inconsistencies in the number of send steps and the number ofmessages sent. Data errors such as these generally occur as a result ofprogramming errors, or when accessing process instances that werecreated before the workload statistics were implemented. The component MESSAGES_IN> in EX_WORKLOAD_TABLE> containsinformation about the messages received by the process instances in theinterval. The sub components BE>, EO>, EOIO>, andUNKNOWN> contain information about the messages received withquality-of-service BestEffort, ExactlyOnce, ExactlyOnceInOrder, or withan unknown quality-of-service. All of these sub components in turn havetheir own sub component RECEIPTS>, which contains informationabout the number of messages received, as well as the sub componentWAITTIMES>, which contains information about the time between whenthe messages were received by the BPE and when they were processed by aprocess instance, that is, the waiting times resulting from queuing orscheduling mechanisms. The sub components ABS>, AVG>,MIN>, or MAX> of RECEIPTS> specify the total, average,minimum, and maximum number of messages received by process instancesduring the specified interval with the appropriate quality of service asspecified by the component name. The sub components of WAITTIMES>specify the average, minimum, maximum, and sum of waiting times ofmessages received by a process instance during the interval inmilliseconds for the specified quality of service. The DATA_ERRORS > of MESSAGES_IN> component contains the number of data errorsthat were found in the messages received during the interval. An erroris considered to be a data error if the quality-of-service of a messagecannot be determined, that is, it is placed in the UNKNOWN>component, or if the waiting time cannot be determined. The MESSAGES_OUT> component in table EX_WORKLOAD_TABLE>contains information about the messages sent by the process instancesduring the interval. Like in MESSAGES_IN>, the sub componentsBE>, EO>, EOIO>, and UNKNOWN> containinformation about the messages sent with the corresponding quality ofservice. All sub components contain the SENDINGS> component,which, for the corresponding quality of service, specifies the total,average, maximum, and minimum number of messages sent by processinstances during the interval. Messages with a quality of service thatcould not be determined increase the count for data errors, which isrecorded in the DATA_ERRORS> of MESSAGES_OUT > component. The MAPPINGS> component in the EX_WORKLOAD_TABLE > containsinformation about the transformation steps executed by the process instances during the interval. The components ABS>, AVG>,MIN> and MAX> of the sub component COUNT> specify thetotal, average, minimum, and maximum number of transformation stepsexecuted by process instances during the interval. The sub componentsABS>, AVG>, MIN> and MAX> of the RUNTIME>sub component in EX_WORKLOAD_TABLE > specify the total, average,minimum, and maximum runtimes for transformation steps executed byprocess instances during the interval. In the case of transformationsteps that are executed in a separate transaction, runtime includespreparation times, execution time of the transformation step, andpersistence times. Note that persistence times are only included intransformation steps executed in separate transaction. TheRUNTIME_DATA_ERRORS> sub component of the MAPPINGS>component specifies the number of transformation steps that contain dataerrors. Only incorrect information about the runtime of the steps, orother incorrect time information is considered as a data error in thiscase. The SENDSTEPS> component in the EX_WORKLOAD_TABLE > containsinformation about the send steps executed by the process instances during the interval. The SYNC>, ASYNC>, and ACK> subcomponents contain information about the send steps in Synchronous >, Asynchronous> Acknowledgment> modes, is, for thesending of synchronous, asynchronous, or acknowledgment messages.Asynchronous send steps contain send steps that request acknowledgmentsand send steps that do not request acknowledgments. These sub componentseach contain the COUNT> and RUNTIME> sub components. TheABS>, AVG>, MIN>, and MAX> sub components of theCOUNT> sub component contain the total, average, maximum, andminimum number of send steps of the relevant type executed by processinstances during the interval. The ABS>, AVG>, MIN>,and MAX> sub components of the RUNTIME> sub componentcontain the total, average, maximum, and minimum number of send steps ofthe relevant type executed by process instances during the interval.Assuming acknowledgments are not requested, in Asynchronous>,Synchronous>, and Acknowledgement> modes, runtime refersonly to the synchronous runtime, that is, the time from the creation tothe completion of the send step; it does not include the asynchronousparts of qRFC processing. In the case of Synchronous> mode,runtime also include the processing times in the target system. In thecase of send steps in Asynchronous> mode which do requestacknowledgments, the waiting time for acknowledgments to arrive is alsoincluded in the runtime. In the case of send steps that are executed ina separate transaction, runtime includes preparation times, executiontime of the send step, and persistence times. Note that persistencetimes are only included in transformation steps executed in separatetransaction. The RUNTIME_DATA_ERRORS > sub component ofSENDSTEPS> component specifies the number of sends steps thatcontain data errors, irrespective of the mode. Only incorrectinformation about the runtime of the steps, or other incorrect timeinformation is considered as a data error in this case. The RECEIVES > component in EX_WORKLOAD_TABLE> contains information about thereceive steps executed by process instances during the interval. TheCOUNT> and RUNTIME> sub components contain information aboutthe number of and runtime of the receive steps. The ABS>, AVG >, MIN>, and MAX> sub components of the COUNT> subcomponent contain the total, average, maximum, and minimum number ofreceive steps executed by process instances during the interval. TheABS>, AVG>, MIN>, and MAX> sub components of theRUNTIME> sub component contain the total, average, maximum, andminimum runtime of receive steps executed by process instances duringthe interval. The runtime of a receive step is the time from itscreation to its completion. This usually corresponds to the waiting timefor an expected message. In the case of receive steps that start aprocess, the value corresponds to a technically limited and shortruntime although the starting of the process, creation of the receivestep, and its completion all take place at the same logical point intime. In the case of receive steps, which, due to message packaging arecreated and processed in the same transaction, the runtime alsocorresponds to the technical processing time and does not include anywaiting times. The RUNTIME_DATA_ERRORS> sub component of theRECEIVES> component specifies the number of receive steps thatcontain data errors. Only incorrect information about the runtime of thesteps, or other incorrect time information is considered as a data errorin this case.
|