Workflow Technical Configuration

The following describes the configuration that was required to load a large
amount of data from a legacy system into a SAP WebAS ABAP system. The load
process utilized a custom workflow and the configuration, as describe
allowed the best throughput for this load.
SMLG - Create logon group for workflow
Define a new logon group for workflow. Add all necessary instances, and
make sure that the checkbox Ext. RFC-enabled is selected.

SM59 - Redefine workflow destination as type 3 for load balancing

If WORKFLOW_LOCAL_<CLI> exists as a logical connection, delete it and
manually redefine it as connection type 3. Set the connection for load
balancing rather than a specific server and enter the message server and
logon group (which you created in the first step above). Enter the logon
information for WF-BATCH (you may need to reset the user ID's password in
SU01) and define the connection as a Unicode connection. Test the
authorization to ensure the correct setup.

SE16 - Set workflow load balancing technique to round-robin

Note: system must be open for cross-client configuration changes for this
step
In SE16, bring up table RZLLICLASS and display all entries. The logon
group which was set to Ext. RFC-enabled in step one should be displayed.
Select this entry and click the change button.

Change the FAVTYP field from B to R.

SMQS - Register workflow RFC destination with no tRFC allowed so that

workflows are initiated on a commit rather than periodically by the QOut
scheduler
In transaction SMQS, if the destination WORKFLOW_LOCAL_<CLI> is already
displayed, select that entry and delete it.
Click the Registration button to register the WORKFLOW_LOCAL_<CLI> RFC
destination with the QOut scheduler. Accept defaults for MAXCONN and
MAXTIME. Change the NO_TRFC, set the value to X.

SWU3 - Maintain automatic workflow customizing

In SWU3, other than the first line, Configure RFC Destination, if there are
any red X's, select them and click the Perform Automatic Workflow
Customizing button. Do not perform this step for the first entry as we
have already manually maintained this configuration.

SWE2 - Ensure that the appropriate workflow linkages are active

Most likely, this next step will not be necessary as the configuration is
transportable and it will have reached the client that way, however and
configuration only client copy will not bring this data over, so in those
cases it will have to be manually maintained (or retransported).
Note: This step requires that the client be open for client-specific
customizing
For the following objects workflow linkage needs to be selected. Double
click on the entry and make sure the Linkage Activated field is selected.
Objects:
BO
BO
BO
BO

BUS2080
BUS2080
BUS1065
BUS1065

CREATED
CREATED
HIRED
POSITIONCHANGED

WS99900003
WS99900012
WS99900002
WS99900002