1. Create Logon Group (SMLG)

·         Create a logon group called Workflow

·         Assign the instances of the app servers that you need to the logon group

o    For each instance flag the entry “Ext. RFC-enabled” on the attributes tab

1. Delete RFC Destination (SM59)

·         Delete the Logical RFC destination WORKFLOW_LOCAL_<CLIENT>

1. Create RFC Destination (SM59)

·         Create a new RFC destination of type R/3 called WORKFLOW_LOCAL_<CLIENT>

o    Choose radio button option “Yes” for Balance Load in the Technical Settings tab

o    Type in the applicable message server where your gateway is

o    Type in the logon group name as defined above

o    Maintain the other parameters as per normal

{googleAds}
<script type="text/javascript"><!--
google_ad_client = "pub-2723892367221695";
/* 728x90, created 10/26/08 */
google_ad_slot = "0440586343";
google_ad_width = 728;
google_ad_height = 90;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
{/googleAds}

1. Workflow customizing (SWU3)

The “Configure RFC Destination” entry should be a red cross because the program is hard coded to check for a Logical RFC destination and not an RFC destination of type R/3 like we have defined.

1. Change the “Event Type Linkages” Details (SWETYPV)

For each business object event that kicks off a workflow specify the “Destination of Receiver” as WORKFLOW_LOCAL_<CLIENT>.