The perfect match: SAP Jam & SAP Mobile Documents

SAP Jam is SAP's collaboration platform. SAP Mobile Documents is the integration platform for content repositories, both for SAP and non-SAP, on-premise and cloud repositories.

So what if you could use the collaboration features of SAP Jam together with the content integration capabilities of SAP Mobile Documents?

Guess what! It is already possible today.

SAP Jam has shipped the integration with SAP Mobile Documents in the latest release.

This is what you can get with the integrated solution:

Image may be NSFW.
Clik here to view.

Using the trial of the SAP HANA Cloud Platform, you can test the solution yourself (the configuration steps will vary if you use SAP Jam and SAP Mobile Documents in a productive environment).

Prerequisites:

SAP Mobile Documents Account on HCP (e.g. Mobile Documents HCP Trial)

SAP Jam Account (e.g. Jam on HCP Trial)

These are the steps that are described in this blog:

I. Setting up Trust Between SAP Jam and SAP Mobile Documents

II. Connecting SAP Jam to SAP Mobile Documents

III. Adding Mobile Documents Repositories into Jam Groups

IV. Onboarding Additional Users

I. Setting up Trust between SAP Jam and SAP Mobile Documents

1. In SAP Jam, when logged in as a company administrator:

Go to the Admin menu:

Image may be NSFW.
Clik here to view.

2. Click on SAML Local Identity Provider, near the bottom of the left menu

Image may be NSFW.
Clik here to view.

3. Press Generate Key Pair if the X509 Certificate field is empty. Then click Save.

Image may be NSFW.
Clik here to view.

Leave this window open, you will need the values in “Issuer” and “X509 Certificate”.

4. In the HCP tenant admin cockpit, click on Trust in the left navigation menu

5. On the tab Local Service Provider, Ensure that Principal Propagation is set to Enabled

6. Go to tab Trusted Identity Provider and click Add Trusted Identity Provider

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

6a. Copy the value from the Issuer field of the Jam SAML Local IdP page to the Name field.

6b. Set the Assertion Consumer Service field to Application Root.

6c. Set the Single Sign-on URL field to http://<Jam_deployment_host>/saml/saml_acs. Replace <jam_deployment_host> with the DNS name the Jam deployment you are using (e.g. developer.sapjam.com).

6d. Leave Single Sign-on Binding as HTTP-POST, leave Signature Algorithm as SHA-1.

6e. Copy the X509 Certificate field from the Jam SAML Local IdP page to the Signing Certificate field.

6f. Set User ID Source to subject.

6g. Check enabled.

It should look like this:

Image may be NSFW.
Clik here to view.

II. Connecting SAP Jam to SAP Mobile Documents

1. In SAP Jam, when logged in as a company administrator:

Go to the Admin menu:

Image may be NSFW.
Clik here to view.

2. Click on External Applications near the bottom of the left menu

Image may be NSFW.
Clik here to view.

3. Select SAP Mobile Documents (cloud version)

Image may be NSFW.
Clik here to view.

4. Provide a meaningful name for the connection.

For the value of the Service Document URL, copy and paste the DNS name of your Mobile Documents instance. You get this URL, when you open the Mobile Documents Web UI (HCP Cockpit - Services - Mobile Documents - Go to Service - Copy the URL after you are logged on. Only copy the part of the URL up to … ondemand.com)

This DNS name looks like https://mdocs-p1941693435trial.hanatrial.ondemand.com

The name identifier is used to define whether the Email address or the User Identifier is unique for both Mobile Documents and Jam. In case both email address and User Identifier for both Jam and Mobile Documents are in sync, it does not matter which option you choose. Both will work in this case.

Image may be NSFW.
Clik here to view.

Now that Mobile Documents is connected, you can select which repositories connected to Mobile Documents should be available for your Jam instance

5. On the newly created entry select Action - Manage CMIS Repositories

Image may be NSFW.
Clik here to view.

6. Click on Add Repository and choose Select From List

Image may be NSFW.
Clik here to view.

In the next screen, select the repositories you want to expose to SAP Jam

Image may be NSFW.
Clik here to view.

III. Adding Mobile Documents Repositories into Jam Groups

1. Log on to your Jam Group (that you want to map Mobile Documents content to) as a Group Administrator

In the lower left navigation menu, select Group Admin - Edit Group

Image may be NSFW.
Clik here to view.

2. Go to Setup

Image may be NSFW.
Clik here to view.

Optional: You can de-select the Content Section for the group in case you only want to access the external content in this group and skip the Jam-internal content:

Image may be NSFW.
Clik here to view.

3. Scroll down to SAP Mobile Documents - click Add External Folder

Image may be NSFW.
Clik here to view.

4. Select the folder or root level of the repository

Image may be NSFW.
Clik here to view.

5. Don't forget to save the changes.

Image may be NSFW.
Clik here to view.

and finally 6. The content is now available in the navigation as new SAP Mobile Documents entry.

Image may be NSFW.
Clik here to view.

IV. On-boarding Additional Users

Adding new Users into SAP Mobile Documents

All users need to have authorizations for both SAP Jam and SAP Mobile Documents. When enabling the Services Jam and Mobile Documents, by default the roles are assigned for the admin. To add additional users, you need to conduct the steps described in the blog Adding additional users to Mobile Documents.

Adding new Users into Jam

The required steps in Jam to assign the required role and add a new user are described in section Setting up new users of James Penfold's blog Welcome to your new SAP Jam developer edition

V. Enjoy your day!

Do what you like most Image may be NSFW.
Clik here to view.