Customizing issues with WF-BATCH password after client copies .

[Morris, Eddie]

Hi Rick,
 
Each time you perform a client copy, you will
have to run SWUB to create the proper RFC destination for that client.
The client copy does not copy the RFC information. This information
is client-independent, a client copy (on the same machine) of this
information would not be useful (because it is a client independent
table). Additionally, copying this information in the case of a
remote client copy would not be useful because the RFC destinations
/definitions of one system may not apply to another. To correct your
problem of the missing RFC destination, again, you can run SWUB or
go to SWU3 and run the option for reconfiguring the RFC destination
once more. The workflow runtime system will look for
WORKFLOW_LOCAL_<Client #> first (which is unique to a client). If it
cannot find this, it will then look for the RFC destination of
WORKFLOW_LOCAL.
 
 
This information gets deleted during a client copy as the relevant
table, SWWCUSTOM, is class L (see note 2857).  The way you are currently
dealing with it is correct, using SWU3 after the client copy.  However,
a way to speed this process up is to copy the client and run a recorded
CATT via the report RSSTARWC in the background. Execute the
transaction SWU3 in the CATT.
 
Hope this helps.
 
Regards,
 
Eddie
 
-----Original Message-----
From: Rick Sample [mailto:Rick.Sample at gbe.com]
Sent: 24 February 2003 15:26
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Customizing issues with WF-BATCH password after client copies.
 
 
We have Training clients set up. They get client copied once a week for new classes.
Every time we do these client copies, we have to go into all the training clients and
reset the pwd for WF-BATCH. Why?
 
>From what I read:
We have to create a logical destination in transaction SM59 (typ 'L') called workflow_local_<client>.
Looks like they are there:
WORKFLOW_LOCAL_500
WORKFLOW_LOCAL_511
...
 
User-ID: WF-BATCH, password: the same as in SU01 for user wf-batch.
User wf-batch have to be a 'SYSTEM' User in SU01.
Confirmed.
 
I have a question. Is the SU01 password for WF-BATCH the same as the WF-BATCH password
in SWU3 customizing for the RFC?  I thought they were the same.
 
I looked at the document for the "Create logical destination for tRFC":
>>The logical RFC destination "WORKFLOW_LOCAL_xxx" is created automatically.
>>If this logical destination did not yet exist, a user is requested (including password). Specify the background user
>>WF-BATCH, which must have been created in the current client.
The "If this logical destination did not yet exist, a user is requested (including password)." raises a question.
We are wiping out (client coping) our training boxes. If this is so and WORKFLOW_LOCAL_511, 512, etc, do not
exist yet, would this be a reason as to why I have to reset / sync WF-BATCH?
I am just taking a stab at understanding how this works.
 
 
4.6c
Thanks!