RFC Destination Settings for Workflow

[Schroeter, Brad]

You may also want to check OSS note 69355.  This corrects the problem in
SWU3 where you test the RFC destination, log off, and when you log back in
it doesn't remember the successful test.
-Brad
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Monday, July 23, 2001 12:12 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: RFC Destination Settings for Workflow
 
 
Hi Diane,
In some of the older releases particularly, the first time you entered SWU3
after
logging on it would always set the Workflow RFC destination config back to
yellow because you haven't tested it since logging on and,
potentially/theoretically, this is
something that could go wrong at any time.  Of course in practice that's
extremely rare
so they've stopped doing that in later releases.  To make it go green again
all you have to do is run the "test rfc destination" to get a successful
"ping" to
confirm the RFC destination is still ok.  But leaving it yellow doesn't stop
workflow from working.
 
Not all of the entries in the environments are strictly necessary so as long
as everything
is working ok I wouldn't stress about red/yellow lights in SWU3.
By the way they have taken off the requirement for the "T " tasks number
range in
later releases, and just left the general number range for creating WS/TS
tasks.
Regards,
        Jocelyn Dart
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Nobles, Diane [mailto:nobles_dh at naptheon.com]
Sent: Friday, 20 July 2001 11:19 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: RFC Destination Settings for Workflow
 
 
Good morning all!!  I have never been unable to get the green light on the
Workflow development environment in the Customizing area on any client.  Is
this a problem??  IF so, what are we are missing??  Also the green light on
the Workflow Runtime resets itself to red or yellow from time to time and
the RFC test has to be run to reset it.  What causes this??
 
 
Diane H. Nobles
SDE PM Team
(757)380-7250
::::::::::::::::::::::::::::::::::::::::::::::
Blessed are those that hear the word
of the Lord and practice it. Luke 11:28
 
 
 
-----Original Message-----
From: Rickayzen, Alan [mailto:alan.rickayzen at sap.com]
Sent: Friday, July 20, 2001 3:48 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: RFC Destination Settings for Workflow
 
 
Hi Ty,
Check that the WORKFLOW_LOCAL_310 destination is configured to logon to
client 310. The message implies that your ping is logging on to the wrong
client. Are you working in client 310?
But the proof of the pudding is in the eating - does the verification
workflow in SWU3 run properly? Run it twice - once for each option in the
decision.
 
Kind regards,
Alan
 
-----Original Message-----
From: Ea, Ty [mailto:TEa at citgo.com]
Sent: Donnerstag, Juli 19, 2001 11:29 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: RFC Destination Settings for Workflow
 
 
 
Hi Everyone,
 
We are in the process of upgrading from 3.1H to 4.6C.  When AutoCustomizing
the 4.6C workflow environment under transaction SWUD, the RFC destination
continues to show the message 'RFC destination has incorrect client'.
However, when I do a test on the RFC destination, it shows that the ping was
performed successfully and that the RFC destination for SAP Business
Workflow is fully configured.  What am I missing?
 
Also, am I correct to assume from this message that WF-BATCH and password
are fine since SAP did not prompt me for either one during the test?    We
currently have destination WORKFLOW_LOCAL_310 set up on both 3.1H and 4.6C.
 
 
As a side note, our 3.1H settings under SWUD shows that the RFC has been
configured completely.
 
Would appreciate any comments anyone might have.
 
Thanks,
Ty Ea
CITGO Petroleum Corporation
(918) 495-4132
 
 
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.