Руководство пользователя Отмена

Adobe Sign for SAP SuccessFactors: Cockpit Installation Guide

Поиск

Последнее обновление 9 авг. 2024 г. | Также применяется к Adobe Acrobat Sign

Интеграции Adobe Acrobat Sign
Новые возможности
Версии и жизненный цикл продуктов
Acrobat Sign для Salesforce
Acrobat Sign для Microsoft
1. Acrobat Sign для Microsoft 365
  1. Руководство по установке
2. Acrobat Sign для Outlook
  1. Руководство пользователя
3. Acrobat Sign для Word/PowerPoint
  1. Руководство пользователя
4. Acrobat Sign для Teams
5. Acrobat Sign для Microsoft PowerApps и Power Automate
  1. Руководство пользователя
  2. Заметки о выпуске
6. Соединитель Acrobat Sign для Microsoft Search
  1. Руководство пользователя
  2. Заметки о выпуске
7. Acrobat Sign для Microsoft Dynamics
8. Acrobat Sign для Microsoft SharePoint
Acrobat Sign для ServiceNow
Acrobat Sign для HR ServiceNow
1. Руководство по установке
Acrobat Sign для SAP SuccessFactors
Acrobat Sign для Workday
Acrobat Sign для NetSuite
1. Руководство по установке
2. Заметки о выпуске
Acrobat Sign для SugarCRM
Acrobat Sign для VeevaVault
Acrobat Sign для Coupa BSM Suite
1. Руководство по установке
Документация для разработчиков Acrobat Sign

Примечание.

Adobe Sign for SAP SuccessFactors: Cockpit Installation Guide has been deprecated. Refer to the Adobe Sign for SAP SuccessFactors: Cloud Foundry Installation Guide for integrating Adobe Acrobat Sign with SAP SuccessFactors.

This document outlines the installation and setup for Adobe Sign for SuccessFactors using the SAP Cloud Cockpit.

Примечание.

Extension of SuccessFactors to include Adobe Sign requires an SAP Cloud Platform account with a NEO based subaccount AND a java compute entitlement.

Technical Overview

The Adobe Sign for SuccessFactors integration extends SuccessFactors (SFSF) via the SAP Cloud Platform (SCP). We have an integration for Recruiting Management (RCM) that enables the sending of Offer Letters from within SFSF to a single recipient. Signed documents are stored on the Candidate Profile. All signing occurs via email notification.

The installation consists of:

1. Configuring one or more sub-accounts within SCP

2. Deploying an MTAR Solution

An MTAR is an archive specific to SCP that contains the web app jar file and other metadata

3. Configuring the SFSF Application Extension via SFSF Provisioning

This is a very complex setup and really should only be performed by someone with expert level experience with SCP.

Примечание.

When deploying to a subscriber-provider topography, only the provider subaccount is running the webapp. The subscriber account is just facilitating the connection between SCP and the SuccessFactors instance.

Prerequisites

1. Access to SFSF provisioning (e.g. https://mysfsfdemo.successfactors.com/provisioning_login)

This is UNCOMMON for customers. Generally, SAP does not allow customers to have access to provisioning.
SAP requires that a ‘certified expert’ be the only person to have access. This isn’t an issue with development/trial accounts but will be for production deployments.

2. A Java compute unit

At the minimum, a Java Lite compute entitlement is required.
If deploying in a provider-subscriber model, this needs to be assigned to the provider sub-account.

Cockpit Installation

There are 2 possible deployment topologies:

Standalone: Deploy the Adobe Sign for SAP SuccessFactors as a stand-alone Solution within a single subaccount. In this situation there is a 1:1 relationship between the deployment subaccount and your SuccessFactors instance.
Subscriber-Provider: Deploy the Adobe Sign for SAP SuccessFactors as a Solution into a ‘provider’ subaccount that can subscribed to by a number of SuccessFactors instances. This allows you to have the app managed at a single location while providing integration services to a number of SuccessFactor instances via corresponding sub-account.

With either deployment strategy, you will need to deploy the Adobe Sign MTAR file. The solution is packaged as a Multi-Target Application Archive (MTAR) and contains both stand-alone and provider/subscriber options.

Download the MTAR file here

Standalone Deployment

Create a sub-account.
Before deploying the MTAR, you will need to connect the subaccount to your SuccessFactors instance.
- Select Integration Tokens. And then create New Token. Copy the token (e.g. 92d13db51c779448f96c8b83d7ef1a8.eu3)
- From the SuccessFactors Provisioning page, choose your Company and then choose “Extension Management Configuration”.
- Under “Add New Subaccount”, Add the integration token.
Deploy the MTAR file as a Solution.

Once deployed, the Solution will complete the installation of the Recruiting and Onboarding Tiles within your SuccessFactors instance.

Subscriber-Provider Deployment

Create a provider sub-account and deploy the MTAR to it.
Create a subscriber sub-account. You will need one for each SuccessFactors instance. Make a note of the “Technical Name” for this sub-account (e.g. hiwyrm997q)
From the provider sub-account, click into the solution you’ve deployed. You will see an “Entitlements” menu on the left.
Create an Entitlement by providing the global technical name of the to-be subscriber sub-account.
On the subscriber subaccount, select Solutions. You should see the AdobeSign solution as a tile under “Solutions available for Subscription”.
Before you can subscribe to the solution, you need to connect this subscriber subaccount to your SuccessFactors instance.
- Select Integration Tokens.
  
  Create New Token
  
  Copy the token (e.g. 92d13db51cxxxxxxxc8b83d7ef1a8.eu3)
- Select Use SAP SuccessFactors identity report
- From the SuccessFactors Provisioning page, choose your Company and then choose “Extension Management Configuration”.
- Under “Add New Subaccount”, Add the integration token.
Click on it and then choose Subscribe. There’s no need to provide a MTAR description file. Just select Subscribe.

Once subscribed, the subscription solution will complete the installation of the Recruiting and Onboarding Tiles within your SuccessFactors instance.

Within SuccessFactors, you can now move the Adobe Sign Recruiting and/or Onboarding Tiles from “not-used” to the default.

See Admin > Tools > Manage Home Page.

Entitle the solution

For each subscriber, select the adobe sign solution and open the Entitlements option from the cockpit and press the New Entitlement button:
In the Create Entitlement panel, enter:
- The subscriber’s subaccount name
- The start date
- The number of entitlements
When done, click Save
From the Subscriptions menu click on the adobesign application:
From the Destinations menu, configure a new destination:
- Name: sap_hcmcloud_core_tech
- Type: HTTP
- Description: sap_hcmcloud_core_tech
- URL: <same URL from the existing destination sap_hcmcloud_core_odata>
- Proxi Type: Internet
- Authentication: BasicAuthentication
- User: <SFSF API User>
- Password: <SFSF API User password>
- Use default JDK Keystore: optional

Typical problems

Typically, 500 errors indicate the lack of database setup.

Please verify your database is available and configured.

This is a wide family of error codes.

Find and inspect the system log files.

Look at the sub-account that is running the web app. This is the provider subaccount
Inspect the java app’s Default Trace: Provider Sub-account-> Solution (adobesign) -> Component (adobesign)-> Java App (adobesign)
Choose Monitoring->Default trace

Problems may be rooted in resource availability (database) or access rights (entitlements).

For resource issues, make sure you have a Schema and binding created
For access rights, make sure you created the Integration Token for SAP SuccessFactors

You may need to disconnect the entitlement from SuccessFactors and create a new one.

If everything appears to be set up properly, stop and re-start the java app on the provider.