We all know that JAM is the most popular social collaboration software from SAP. Now, both C4C and JAM has few things in common. One of which is Feed.
Whatever happens, eventually, feeds make up everything. Conversations, Decisions, Help etc… What if a customer is already using JAM as their Feed system and want to maintain the same in C4C as well ??? C4C does support the JAM integration out of box. You just have to configure it according to your need.
This document gives you detailed steps which you need to follow in order to successfully configure JAM Integration with C4C.
- Basic assumption would be that both tenants work on same User IDs and replace current C4C feed functionality with that of JAM’s.
- Prerequisite would be that you need to have Admin rights in both tenants!
- Recommended Browser: Internet Explorer!
- Every company specific sensitive data will be masked. So, watchout for white spaces!
Step 1: Login into your JAM instance and navigate to Admin page.
Step 2: Check for the option “OAuth Clients” in the left pane and click it. Add a new oAuth client.
Step 3: Create a new OAuth Client by giving below params.
1) Name: Tenant URI without https
2) Feed Filtering: Select none (General Case)
3) Integration URL: C4C tenant URl with https
4) Rest all empty.
Step 4: Let’s see what we’ve created. Go back to OAuth Clients view and now, you should be able to see the client you’ve created. Click on “View”.
Step 5: You should be able to see the Key and Secret values for the OAuth client (C4C tenant). This will be later used by C4C tenant for token exchange. I did mask Secret for security reasons.
Step 6: Click “Security” on the left pane now and get the Domain name (which will be later used as Company ID)
Step 7: Meanwhile in C4C, make sure that you’ve scoped the JAM integration under Communication and Information Exchange –> People Collaboration, Intranet and External Services –> Communities, Document Management and External Services
Step 8: Navigate to Business Configuration –> Implementation Projects and select “Open Activity List”
Step 9: Get the “JAM” activity in Fine-Tuning phase as shown below.
Step 10: Select the “JAM” client and click on “Register Client” which should pop-up a window as shown in the below screenshot and click “Ok”.
1) Client ID: Key from step 5.
2) Client Secret: Secret from step 5.
3) Authentication Server URL: <Your JAM server instance URL>
4) API Server URL: <Your JAM server instance URL>
5) Company ID: Domain name from Step 6.
6) Account Name Origin: Select User ID as our assertion attribute will be having common User IDs in this example.
7) SAML NameID Format: Select Unspecified
Step 11: You should now see the below screen. Things to be noted from this screen for later use.
1) Click on “Show Client Signing Certificate” and copy encoded certificate text.
2) Make a note of “Local IDP ID”.
3) Make a note of “Default Name ID Format”.
Step 12: Coming back to JAM Admin page from where we left previously, click on “SAML Trusted IDPs” and then on “Register your identity provider”.
Step 13: Enter details as explained below and hit “Save”.
1) IDP ID: Local IDP ID from Step 11.
2) Default Name ID Format: Same as Default Name ID Format from Step 11.
3) Default Name ID Policy: Same as Local IDP ID
4) Allowed Assertion Scope: Select “Users in my company”
5) X509 Certificate: Encoded Certificate text copied from Step 11.
6) Rest all empty.
Step 14: It’s done. Now, its time to TEST !!! It is very important that you logout from all successfactors / JAM instances.
Step 15: Login into C4C with your user account and navigate to “Feed” wc. You should see the JAM Feed widget mashup spread over the screen. Key in some Feed and hit the Arrow.
Step 16: Click on “JAM” link on the top of the widget. You should be logged into JAM instance automatically and be able to see your feed there.
JAM integration with C4C actually enables you to do lot of other things such as creating JAM Groups from C4C, Feeds against Opportunity, Account etc.. Check in Help Center with keyword “JAM” for more info.
~~~ End of Document ~~~