As an implementation partner, you install and configure the extension applications that you want to make available for customers.
SAP Business Technology Platform, Neo environment will sunset on December 31, 2028, subject to terms of customer or partner contracts.
For more information, see SAP Note 3351844.
This documentation refers to SAP Business Technology Platform, Neo environment. If you are looking for documentation about other environments, see SAP Business Technology Platform
↗️ .
You deploy your extension application, configure its connectivity to the SAP SuccessFactors system and map the roles defined in your extension application to the roles in the corresponding SAP SuccessFactors system.
-
You have an SAP BTP extension subaccount and the corresponding SAP SuccessFactors customer instance connected to it. For more information about extension subaccounts, see Extensions.
-
You are either an administrator of the SAP BTP subaccount or have а platform role with the following platform scopes defined for it:
-
manageExtensionConfigurations
-
readExtensionConfigurations
-
readJavaApplications
-
readSubscriptions
-
readAccount
-
manageDestintaions
-
readDestinations
-
readJavaApplications
-
readHTML5Applications
-
manageApplicationRoleProvider
-
readSubscriptionConfiguration
-
-
You have downloaded and set up the console client for SAP BTP, Neo environment. For more information, see Console Client for the Neo Environment.
You deploy your extension application in your SAP BTP extension. Then you need to configure the application connectivity to SAP SuccessFactors and to enable the use of the HXM Suite OData API. To ensure that only approved applications are using the SAP SuccessFactors identity provider for authentication, you need to register the extension application as an authorized assertion consumer service in SAP SuccessFactors. Then you register the extension application home page tiles and import the extension application roles in the SAP SuccessFactors customer instance connected to the extension subaccount.
To finalize the configuration on SAP BTP side, you change the default role provider to the SAP SuccessFactors one. To finalize the configuration on SAP SuccessFactors side, you assign user groups to the permission roles defined for your extension application.
In the Neo environment, you can alternatively deploy your extension application as a solution. You can package all artifacts that are needed for your extension solution – Java applications, HTML5 application, database bindings, destinations, even SAP SuccessFactors roles and home page tiles into a Multi-Target Application (MTA) archive that includes a deployment descriptor file, and then deploy the MTA archive in your account. See:
Task |
Description |
---|---|
Register the extension application as an authorized assertion consumer service. |
|
Configure the connectivity between your Java extension application and the SAP SuccessFactors system associated with your SAP BTP extension subaccount. |
|
Register a home page tile for the extension application in the extended SAP SuccessFactors system |
|
Create the resource file containing the SAP SuccessFactors HXM role definitions. |
|
Import the application-specific roles from the SAP BTP system repository into to the SAP SuccessFactors customer instance connected to your extension subaccount. |
|
Assign the extension application roles you have imported in the SAP SuccessFactors systems to the user to whom you want to grant access to your application. |
|
Change the default SAP BTP role provider of your Java application to the SAP SuccessFactors role provider.
|
|
Try to access the application with the users with different level of granted access to test the role assignments. |