Connect Document Management Service, Application Option to DMS
In this blog post, I will describe the steps required to connect Document Management Service, Application Option running on cloud foundry to on-premise DMS repository.
Before proceeding, if you do not already have DMS setup, follow the steps mentioned in this blog post by Jens Koster to configure DMS.
PART I : Setting up Cloud Connector
For information on installing cloud connector, see this documentation .
Once your cloud connector is up and running, follow the below steps.
Step 1: Connect Cloud Connector with cloud foundry subaccount
- Go to your cloud foundry subaccount and click on the “information” icon on subaccount tile. Copy the subaccount id.
- Now, use this subaccount id in cloud connector subaccount configuration. Go to cloud connector administration UI and click on “Add Subaccount”.
- Enter Region Host. CF regions host are the cf.<region>.hana.ondemand.com ones. Example: cf.eu10.hana.ondemand.com for Europe (Frankfurt) – AWS.
- Enter your Cloud Platform Email Id and password and save the configuration. Optionally, enter location id..
Step 2: Connect Cloud Connector with ABAP system
- Go To Cloud To On-Premise in cloud connector UI under your subaccount and click on plus ( + ) sign.
- Choose ABAP System as backend type and click on Next.
- Choose HTTPS as protocol and click on Next.
- Enter the internal Host and Port of your ABAP system. To find out the internal host and port of your ABAP system, Go To transaction SMICM in backend ABAP system -> Click on services -> Copy the Host and Port for HTTPS protocol.
- Enter the virtual host and port. Click on Next.NOTE: For Document Management Service, the internal host and virtual host should be same in order for the integration to work.
- Choose Principal Type as None. Click on Next.
- Choose Virtual host in request. Click on Next.
- Click on Finish
Step 3: Allow access to ABAP resources
- In the Access Control tab of Cloud Connector, under the Resources section, click on plus (+) sign.
- Provide the URL path /sap/bc/mcm/json.
- Select Access Policy as path and all sub paths.
- Click on Save.
PART II : Connecting Repository to Associated ABAP class
- Go to backend ABAP system.
- Use transaction SM30.
- Enter CMISD_SERVICE in the Table/View.
- Choose Maintain.
- Choose New Entries.
- Edit the fields as described in the following table:
Enter a name for the repository
- Save your changes.
PART III : Setting up Destination
- Go to your Cloud Foundry subaccount -> Destinations.
- Click on New Destination.
- Provide a destination name.
- In URL, Enter http://<host>:<port>/sap/bc/mcm/json/<repositoryId> . Here host and port are the same as configured in cloud connector in previous steps. The repositoryId is the name configured in PART II.
- Select Proxy Type as OnPremise.
- Select Authentication as BasicAuthentication and Enter your ABAP system user and password.
- Click on Save.
Your DMS repository is now ready to be consumed in Document Management Service.
PART IV : Onboarding DMS repository via Document Management Service, Application Option
Pre-requisite : Follow the steps mentioned in this documentation to do initial configuration of Document Management Service, Application Option.
Steps to onboard DMS repository:
- Go to Admin url, https://<your-document_management-endpoint>/admin.html
- Click on Plus sign(+) to add repository.
- Provide any Display Name.
- Provide repository Id used in PART II, Step 5.
- Provide the name of destination created in PART III.
- Click on Add. After successful onboard, you should see a message ‘Repository Added’.
Now, you can access your repository at https://<your-document_management-endpoint>/web.html
- Getting Access denied error while accessing application at endpoint, /web.htmlResolution : Check your Role Collection that you created in PART III during the initial configuration of Application Option. Make sure you have the following roles added to your role collection:SDM_AdminSDMWeb_AdminSDM_UserSDMWeb_UserToken_Exchange
- Getting 403 Forbidden error while accessing repositoryResolution: After you have onboarded the repository, if trying to access the repository by clicking on the repository tile gives you 403 forbidden error, this means that the cloud connector host is not configured properly.Check the ABAP system host for HTTPS protocol as described in PART I, Step 2 ( 4 ) from SMICM transaction.Now check the host configured in your Cloud Connector. Both hosts should be same.