Pages

Download SAP Certification Material for FREE @ http://sap-ebooks-den.blogspot.com

Tuesday, July 5, 2011

Parallelizing Send Processes for Improved Performance


To improve performance for busy message periods, you have the option of parallelizing the SAPconnect send process. This enables send requests to be processed on multiple work processes that can run on different application servers. Only one background job is executed, which starts multiple work processes. This divides the send requests into packages and sends them in parallel over different servers. These work processes are dialog work processes that are started in addition to the work process on which the send job (report RSCONN01) is running.
 

The option of dividing up send requests requires additional control parameters, however these do not normally have to be changed. These are parameters of report RSCONN01. These parameters are job-specific, meaning that different parameters can be set for different send jobs. They can be set when creating a send job in the job maintenance. They are always stored as variants of report RSCONN01.

Prerequisites

You must only implement parallelization if a very large number of send requests have to be processed, subsequently hindering the performance.

Procedure

To parallelize the send process, proceed as follows:

...

       1.      Call transaction SCOT and choose Settings  ® Send Jobs  or symbol This graphic is explained in the accompanying text (send jobs).

       2.      Choose Schedule Job.

You are given a menu for the different address types (FAX, INT and so on). You use this to preselect the job name and the standard variant delivered by SAP that are to serve as a template for the job. You can still change these values in the subsequent dialog box Send Job: Select Variant.

       3.      If required, adjust the job values or variant values in the dialog box Send Job: Select Variant.

If individual parameters of the selected variant are changed, a prompt appears after confirming the changes, asking you to save the variant. Here you can still change the variant name, which creates a new variant with this name.

The values in the Job Values group box always depend on the variant chosen above. If you change the values here, you also have to save a new variant for them.

As the same thing happens during parallelization, from a technical point of view, as when starting the send process, the fields in the Variant Values group box are the same as those that are displayed under Utilities ® Start Send Process:

Field

Variant Value

Number of Work Processes

If a value greater than 1 has been entered in the Number of Work Processes field for an SAPconnect send job, the processing of the messages being sent is distributed across the corresponding number of dialog work processes.

If the value for Number of Work Processes is set to 1, or if the number of waiting messages lies below a defined threshold value, no parallelization takes place, and no additional dialog work process is used. You configure this threshold value using the Minimum Packet Size parameter (under Details).

 

Server Group

The Server Group parameter specifies the application server that is used for the send process. If no value has been entered, then all available servers are used.

If the number of work processes is set to 1, this parameter can be ignored.

 

Details

Under Details you can find parameters for maximum and minimum packet size, maximum number of send requests to be read at once from the queue, timeout factor for each send request, timeout offset for aRFCs and Commit Work.

In most cases, you do not have to change the predefined settings for these details parameters that were delivered by SAP. For help about the individual fields, see the system documentation (F1 help) or the info buttons on the user interface.

 

 

 


No comments:

Post a Comment

Related Posts Plugin for WordPress, Blogger...