Using RFC destination groups as the workflow RFC destination

[Quenzer, Kenneth]

Hi Kjetil,
 
You can delete the logical destination and create an r/3 connection that
uses load balancing.  This is what we do to localize workflow to specific
application servers in our production system.  When you create the r/3
connection you must use the same name (workflow_local_xxx) that you used as
the logical desitination.  After creating the r/3 connection you can turn on
load balancing and enter the load balancing group that you want to use for
workflow.  Basis should define the load balancing group to use the
application servers that you want workflow to use.
 
Kenny
 
-----Original Message-----
From: Kjetil Kilhavn [mailto:KJETILK at statoil.com]
Sent: Tuesday, March 06, 2001 1:17 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Using RFC destination groups as the workflow RFC destination
 
 
In my course documentation I have made a short note on the page about
creating
the RFC user (the chapter is about configuring the workflow system). It just
says "also possible to use RFC destination group". There is no further
information about this possibility, neither in the course documentation or
the
online help. So I was hoping a shot in the dark into this group could shed
some
light on the matter. Perhaps the end result is that I have to strike out the
note :-(
 
Background:
When we had finished upgrading our production copy from 3.1H to 4.6C
recently
about 1.500 work items had expired on deadline. These are in a workflow
where
this expiration leads to cancellation of the step and execution of a
subsequent
background step. As deadline monitoring kicked in this occupied nearly all
the
system resources (all dialog processes), and we want to eliminate the risk
of
the same situation occuring in our production system.
 
One way of preventing the situation is to limit the servers which are
influenced, and this can be done via the definitions of RFC destinations,
thus
my question.
 
Since the logical destination (workflow_local_xxx) could not be modified we
have
tried deleting it and creating a RFC destination group with the same name.
This
does not work. It seems the _logical_ RFC destination has to be defined,
otherwise the runtime system refuses to function properly.
--
KjetilK
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended
for the addressee only. Any unauthorised use, dissemination of the
information
or copying of this message is prohibited. If you are not the addressee,
please
notify the sender immediately by return e-mail and delete this message.
Thank you.