用户指南 取消(C)

Adobe Sign for SAP SuccessFactors: Cockpit Installation Guide

  1. Adobe Acrobat Sign 集成
  2. 新增功能
  3. 产品版本和生命周期
  4. Acrobat Sign for Salesforce
    1. 安装包
    2. 配置包
    3. 用户指南
    4. 开发人员指南
    5. 高级自定义指南
    6. 字段映射和模板指南
    7. 移动应用程序用户指南
    8. 流程自动化指南
    9. Document Builder 指南
    10. 配置大型文档
    11. 升级指南
    12. 发行说明
    13. 常见问题解答
    14. 故障排除指南
    15. 其他文章
  5. Acrobat Sign for Microsoft
    1. Acrobat Sign for Microsoft 365
      1. 安装指南
    2. 适用于 Outlook 的 Acrobat Sign
      1. 用户指南
    3. 适用于 Word/PowerPoint 的 Acrobat Sign
      1. 用户指南
    4. 适用于 Teams 的 Acrobat Sign
      1. 用户指南
      2. Live Sign 指南
      3. 移动用户指南
      4. 发行说明
      5. Microsoft Teams 审批
    5. 适用于 Microsoft PowerApps 和 Power Automate 的 Acrobat Sign
      1. 用户指南
      2. 发行说明
    6. 适用于 Microsoft Search 的 Acrobat Sign 连接器
      1. 用户指南
      2. 发行说明
    7. 适用于 Microsoft Dynamics 的 Acrobat Sign
      1. 概述
      2. Dynamics Online:安装指南
      3. Dynamics Online:用户指南
      4. Dynamics 内部部署版:安装指南
      5. Dynamics 内部部署版:用户指南
      6. Dynamics 工作流程指南
      7. Dynamics 365 for Talent
      8. 升级指南
      9. 发行说明
    8. 适用于 Microsoft SharePoint 的 Acrobat Sign
      1. 概述
      2. SharePoint On-Prem:安装指南
      3. SharePoint On-Prem:模板映射指南
      4. SharePoint On-Prem:用户指南
      5. SharePoint On-Prem:发行说明
      6. SharePoint Online:安装指南
      7. SharePoint Online:模板映射指南
      8. SharePoint Online:用户指南
      9. SharePoint Online:Web 表单映射指南
      10. SharePoint Online:发行说明
  6. Acrobat Sign for ServiceNow
    1. 概述
    2. 安装指南
    3. 用户指南
    4. 发行说明
  7. 适用于 HR ServiceNow 的 Acrobat Sign
    1. 安装指南
  8. 适用于 SAP SuccessFactors 的 Acrobat Sign
    1. 主控室安装指南(已弃用)
    2. 招聘管理安装指南(已弃用)
    3. 招聘管理用户指南
    4. Cloud Foundry 安装指南
    5. 发行说明
  9. 适用于 Workday 的 Acrobat Sign
    1. 安装指南
    2. 快速入门指南
    3. 配置教程
  10. 适用于 NetSuite 的 Acrobat Sign
    1. 安装指南
    2. 发行说明
  11. 适用于 SugarCRM 的 Acrobat Sign
  12. 适用于 VeevaVault 的 Acrobat Sign
    1. 安装指南
    2. 用户指南
    3. 升级指南
    4. 发行说明
  13. 适用于 Coupa BSM Suite 的 Acrobat Sign
    1. 安装指南
  14. Acrobat Sign 开发人员文档
    1. 概述
    2. Webhook
    3. 文本标记
注意:

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.
Main provider


Cockpit Installation

There are 2 possible deployment topologies:

  1. 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.
  2. 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

 

More detailed documentation from SAP:


Standalone Deployment

  1. Create a sub-account.

  2. 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.
  3. 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

  1. Create a provider sub-account and deploy the MTAR to it.

  2. 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)

  3. From the provider sub-account, click into the solution you’ve deployed. You will see an “Entitlements” menu on the left.

  4. Create an Entitlement by providing the global technical name of the to-be subscriber sub-account.

  5. On the subscriber subaccount, select Solutions. You should see the AdobeSign solution as a tile under “Solutions available for Subscription”.

  6. 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
    token

    token

    • From the SuccessFactors Provisioning page, choose your Company and then choose “Extension Management Configuration”.
    • Under “Add New Subaccount”, Add the integration token.
  7. 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

  1. For each subscriber, select the adobe sign solution and open the Entitlements option from the cockpit and press the New Entitlement button:

    SAP Entitlements

  2. In the Create Entitlement panel, enter:

    • The subscriber’s subaccount name
    • The start date
    • The number of entitlements

    When done, click Save

    SAP Create entitlement

  3. From the Subscriptions menu click on the adobesign application:

    SAP Subscriptions

  4. 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
    SAP Destination


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.


Next Steps...

 Adobe

更快、更轻松地获得帮助

新用户?