Migrating Solutions to SAP HANA Cloud: Migrate Document Service from Neo to Cloud Foundry

Attention: The content of this blog was not created by SAP. It was written by a non-SAP consultant, Fatema Patel (HANA Consultant, Pythian) to help your migration journey to the cloud. Therefore, please keep in mind that it might take some more time to get answer for your question in case you leave any to this blog.

This blog describes the technical steps needed to migrate Document Service from the Neo environment to Document Management Service in the Cloud Foundry environment.

The Document Service stores, manages, and secures your business documents and attachments in the cloud.

1. Prerequisites

Several services and roles are required which will be discussed in the subsequent steps. It’s assumed that SAP HANA Cloud database is provisioned and read/execute access has been provided for the source database.

Please note that the SAP BTP user in the NEO environment must have the manageECM role.

In addition, you will need to use the Postman tool to test the setup.

2. Provision of the target services in Cloud Foundry

The below services need to be provisioned in the SAP BTP, Cloud Foundry environment as shown below:

• Document Management Service, Integration Option
• Document Management Service, Repository Option

3. Roles required for User in Cloud Foundry

The below role is required:

• SDM_MigrationAdmin

Note: A new role collection has to be created with the above role to assign it to the BTP users.

4. Create Destinations

Create destination in the target subaccount (in Cloud Foundry) as per the below parameters:

• Name: <Any name for the destination>
• Type: HTTP
• URL: https://ecm.<subaccount region>.hana.ondemand.com
• Authentication: BasicAuthentication
• User: <Neo User Name>
• Password: <Password>

5. Create Instances

Create an instance for the Document Management Service, Integration Option.

1. Navigate to Service Market Place.
2. Click on Document Management Service, Integration Option.
3. Create Instance.

Create a Service Key for the Document Management Service instance.

6. Generate and get Authentication Token using Postman

Please refer to this document for the information about the Postman.

Open Postman and provide the following parameters:

• Request
• HTTP Method: (Get)
• Client
• Access Token URL

The inputs can be found by entering environment variables in any application (VCAP_SERVICES). The screenshot below can be used as a reference:

Once the above parameters are provided in the postman, then click on GET NOW ACCESS TOKEN.

7. Generate Report URL

In the postman tool, give the following parameters to generate a report URL:

• URL: <“endpoints”:”migrationservice”:”URL”>/v1/report/<accountId>/<repoId>
• Method: GET
• Authorization: Bearer Token

8. Perform Migration

In the postman tool, give the following parameter:

• URL: <“endpoints”:”migrationservice”:”URL”>/v1/migrate

The URL for the request is fetched from the Service Key of the Document Management Service instance created in Cloud Foundry.

• Method: POST
• Authentication: Bearer Token
• AccountId: <Neo subaccount>
• RepoID: <Neo repository name>
• RepoKey: <Neo repository password>
• Destination: <Destination which we created above>

On executing, if everything works well, you should get the below response:

Check migration status at /status

9. Check Status

In the postman tool, give the following parameters:

• URL: <“endpoints”:”migrationservice”:”URL”>/v1/status
• Method: POST
• Authentication: Bearer Token
• AccountId: <Neo subaccount>
• RepoID: <Neo repository name>
• RepoKey: <Neo repository password>
• Destination: <Destination which we created above>

The sample request looks like below:

The migration of the Document Service content from Neo to Cloud Foundry is now complete!

Please feel free to leave any comments/questions. It might take some time as this content is not from SAP, but we will do our best to get back to you with accurate and reliable information.