DMS Content Server migration to BTP DMS Repository

[ALLAMPRABHU]

General Introduction

ABCD company - DMS Content Server migration to BTP DMS Repository - 

Steps

1. Upgrade existing non-production Content Server 6.5 to Content Server 7.5x
2. Connect non-production upgraded Content Server 7.5x to ECC6 non-production System(s).
1. Please verify with Basis team that you can connect upgraded Content Server 7.5x to ECC6 system.
3. BASIS team shall test and validate upgraded server in ECC6 non-production System(s).
4. Connect non-production upgraded Content Server 7.5x to S/4 non-production System(s).
5. Migrate limited number of attachments from upgraded Content Server connected to S/4 non-production System to BTP DMS Repository option.
6. Upgrade existing production Content Server 6.5 to Content Server 7.5x
7. Connect production Content Server 7.5x to existing ECC6 Production System.
1. Please verify with Basis team that you can connect upgraded Content Server 7.5x to ECC6 system.
8. During S/4 go-live cutover activities, we should change connection of upgraded production Content Server 7.5x from ECC6 Production to S/4 Production System.
9. After go-live, migrate attachments from upgraded Content Server connected to S/4 production System to BTP DMS Repository option.

Please find the Architecture diagram below 

STEP 1:
create a new BTP subaccount or use the existing BTP subaccount 

SAP BTP Cockpit 

1. Sub-account Overview > Enable Cloud Foundry

2. Create an SPACE > add users to SPACE
3. Entity Assignments and select Entities

Global Account > Entitlements > Entity  Assignments

Click on Configure Entitlements

Click on Add service Plans

Sub-Account > Entitlements > Add Service Plans

Go to SUB account and add into the account

you can see the Services in Entity Assignments

in service marketplace you can see the Application

Instance and Subscription > Create New instance or subscription

click on new instance or subscription & click Next

Instance creating is in progress it took 3 mins to complete 

create Key for instance

 Before that u need to create an Role

Create Role Collection and assign roles

Click on ROLE, select on required Roles need to be added to Role collections

add to Role collection

After save click on back on the DMS_PRD and select another role and ADD

Click on Instances and Subscriptions

Service key need to create

after that login to POST man or Accelerator to create an API 

i have used the Accelerator 

Login to Accelerator: please find the link below for the Accelerator 

Try Out | Administrative Operations | SAP Business Accelerator Hub 

RUN the API successful

STEP 2 

login to S/4 HANA system 

Login to BACKEND system S/4 and execute the T-code

OA2C_CONFIG

Activate the services Json

RFC is successful now create the OACO

Create Content Repository in OACO

OR

you can use Onboard Repository using POST man 

 You may use https://www.base64encode.org/  in case encoding is not working in POST / POSTMAN

Note--------------------------------------

Ensure that user executing 'list repositories' or 'onboard repositories' in 'SAP Business Accelerator Hub' shall have required roles assigned in respective sub-account

-------------------------------------------------------------------------

technical configuration steps for BTP DMS, based on my experience. I recently had the opportunity to configure DMS for a client, where I faced several challenges. Through this process, I documented my learnings, and the steps involved.

Please feel free to reach out if you have any questions or need further clarification.

Best regards,
Allam Prabhu