on ‎2016 Apr 01 1:27 PM
Hello,
we are searching for documentation and experiences with tenant copies. We have got regulary copies on ERP-side and therefore tenant content has to be adapted.
Now we can't find any documentation which tells us which follow up activitites are neccessary. SAP Support says we have to do all again what's in integration guide - what an effort and not competable with a "normal" system copy.
For example with a full tenant copy all users have to be maintained again - normaly users are different in accounts and authorizations between test and productive system. There are no possibilities with export / import as known from ERP system copies.
In the ERP system copy guides there is a section with follow up activities - for C4C this seems not to exist.
And if we really have to do all acitivities from integration guide again it's really scaring! Because of changing URL and logical system name there are follow up activitities in ERP and PI too!
Who can support us with a check list or experiences with follow up activities after a tenant copy? I think we're not the first company which has to do this.
Regards,
Julia
Request clarification before answering.
Hi Julia
We created a NEW TEST C4C tenant from a copy of our C4C PRODUCTION tenant and the whole activity went very well. We found during our project that our TEST tenant became a mixture of good data and bad because initially you are trying things out to see how the various functions work. This is especially the case with C4C being so new and the fact that not a lot people know about this product as yet.
Set up overview:
- Backend ECC integration
- Backend SAP PI integration
- C4C Administration Changes
So, basic steps include:
- Change LogSysID of Communication System / Business Instance.
Make sure you are pointing to your existing TEST system. In our case it is our ECC TEST environment but previously pointed to PRODUCTION system as it was copied from PROD tenant.
Keep the UUID the same though. This will make sure the ID Mappings are copied from the Production System ID to the Test SYstem ID and save you heaps of work!
- Delete and Re-Create ALL Communication Arrangements.
You will need to create ALL new communication arrangements for all of the relevant scenarios. As part of this process you will also need to generate new certificates.
- Generate Client Certificate Key Pair (PKCS#12) from Communication Arrangement
Create and download a key pair certificate within C4C. This will need to be uploaded into the SAP PI on premise system (in our case).
- Upload C4C Key Pair (PKCS#12 file) into Java Key Store
You will need to load the above C4C certificate into the Java key store in the SAP PI test system.
- Change Value Mapping groups
Within SAP PI there will be value mapping groups that were set up to include the C4C logical system ID. This will need to be changed to the new C4C logical system provided with the new TEST tenant.
- Change C4C Receiver Communication Channels
There will be a number of receiver communication channels that were set up to point to the old tenant. You will need to update these to the NEW TEST tenant URL. Change the Target URL's and save and activate the changes.
You should then be ready to go and test out the interfaces.
Good Luck!
cheers
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Phil, hello SAP Experts,
is it still necessary to completely recreate all communication agreements after a tenant copy?
In my opinion, in most cases only the systemID and paths differ. The problem is that the SystemID cannot be changed.
Wouldn't it make sense to implement a function where executing the adaptation process for the new tenant (Adapt Integration Content for New Tenant) copies the existing communication agreements and overwrites them with the new SystemID?
Or is there already a way to simplify the process just described?
Best regards
Arthur Schewe
Still open.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Julia,
In an integrated landscape, in C4C you should make sure you check the Communication System and all the Communication Arrangements to maintain all the Integration scenario.
As a general rule of thumb when getting a tenant copied you should:
1. Validate that all the Custom fielda and any Custom work or Enhancement is copied or not.
2. Check and maintain the Communication Syatem and Arrangements. Post this do connection tests.
3.Check for any Mashups if you configured any.
4. Give a check and maintain Org model and Job Positions.
5. If data copy has not been requested in tenant copy request then pweform all the data loads.
6. Lastly, do not forget to do a quick check on the configuration and your critical processes should be testwd end to end to ensure the copy has not impacted them.
BR
Ankut
| User | Count |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.