2 Deploying the SAP SuccessFactors Connector

The procedure to deploy the connector is divided across three stages namely preinstallation, installation, and postinstallation.

The following topics provide details on these stages:

Note:

Some of the procedures described in this chapter must be performed on the target system. To perform these procedures, you must use a SuccessFactors account with administrator privileges.

2.1 Preinstallation

Preinstallation for the SuccessFactors connector involves registering a client application (that is, the SuccessFactors connector) with the target system so that the connector can access REST APIs. The preinstallation step includes client application registration, certificate generation, and obtaining clientid and client secret attributes.

Preinstallation involves performing the following tasks on the target system:

Note:

The detailed instructions for performing these preinstallation tasks are available in SuccessFactors product documentation at https://support.sap.com/documentation.html/
  1. Register your client application with SuccessFactors to provide a secure sign in and authorization of your services. You can register your client application by creating an application in the SuccessFactors Manage OAuth2 Client Applications page.
  2. While creating an application, ensure that you provide information in the mandatory fields. Fields such as Application Name, Description, Application URL, Common Name (CN), and Validity (Days) are mandatory fields required for the SuccessFactors connector. As a best practice, SuccessFactors recommends to use your company ID as the Common Name (CN) field information. As part of registering your client application, a Certificate.pem file gets generated.
  3. Make a note of the clientId and client secret information. Post application registration, from the Manage OAuth2 Client Application page you can view the clientId and client secret information. The clientId and client secret information is required during the IT resource configuration of the SuccessFactors connector.

2.2 Installation

You must install the connector in Oracle Identity Manager. If necessary, you can also deploy the connector in a Connector Server.

The following topics provide details on installing the connector:

2.2.1 Understanding Installation of the SAP SuccessFactors Connector

You can run the connector code either locally in Oracle Identity Manager or remotely in a Connector Server.

Depending on where you want to run the connector code (bundle), the connector provides the following installation options:

  • Run the connector code locally in Oracle Identity Manager.

    In this scenario, you deploy the connector in Oracle Identity Manager. Deploying the connector in Oracle Identity Manager involves performing the procedures described in Running the Connector Installer and IT Resource Parameters.

  • Run the connector code remotely in a Connector Server.

    In this scenario, you deploy the connector in Oracle Identity Manager, and then, deploy the connector bundle in a Connector Server. See Using an Identity Connector Server in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager for information about installing, configuring, and running the Connector Server, and then installing the connector in a Connector Server.

2.2.2 Running the Connector Installer

When you run the Connector Installer, it automatically copies the connector files to directories in Oracle Identity Manager, imports connector XML files, and compiles adapters used for provisioning.

To run the Connector Installer:

  1. Copy the contents of the connector installation media into the following directory: OIM_HOME/server/ConnectorDefaultDirectory.

    Note:

    If this is the first time you are running the Connector Installer for deploying the connector bundle in a Connector Server, then place the bundle in the connector server bundle directory.
  2. Log in to Oracle Identity System Administration.
  3. From the left pane, expand the Provisioning Configuration tab and click Manage Connector.
  4. In the Manage Connector page, click Install.
  5. From the Connector List, select SuccessFactors Connector RELEASE_NUMBER.
    This list displays the names and release numbers of connectors whose installation files you copy into the default connector installation directory in Step 1.

    If you have copied the installation files into a different directory, then:

    1. In the Alternative Directory field, enter the full path and name of that directory.

    2. To repopulate the list of connectors in the Connector List list, click Refresh.

    3. From the Connector List list, select SuccessFactors Connector RELEASE_NUMBER.

  6. Click Load.
  7. To start the installation process, click Continue.
    The following tasks are performed in sequence:

    1. Configuration of connector libraries

    2. Import of the connector XML files (by using the Deployment Manager)

    3. Compilation of adapters

    On successful completion of a task, a check mark is displayed for the task. If a task fails, then an X mark and a message stating the reason for failure are displayed. If a task fails, then make the required correction and perform one of the following steps:

    1. Retry the installation by clicking Retry.

    2. Cancel the installation and begin again from Step 3.

  8. Click Exit to finish the installation procedure.
    If all three tasks of the connector installation process are successful, then a message indicating successful installation is displayed. In addition, a list of the steps that you must perform after the installation is displayed. These steps are as follows:

    1. Configuring the IT resource for the connector.

    2. Configuring the scheduled tasks that are created when you installed the connector.

    When you run the Connector Installer, it copies the connector files and external code files to destination directories on the Oracle Identity Manager host computer. These files are listed in Files and Directories on the SAP SuccessFactors Connector Installation Media.

2.2.3 Configuring the IT Resource for the Target System

An IT resource for your target system is created after you install the connector. You configure this IT resource to enable the connector to connect Oracle Identity Manager with your target system.

The following topics are discussed in this section:

2.2.3.1 IT Resource Parameters

An IT resource is composed of parameters that store connection and other generic information about a target system. Oracle Identity Manager uses this information to connect to a specific installation or instance of your target system.

The SuccessFactors IT resource is automatically created when you run the Connector Installer. To specify values for the parameters of the IT resource:
  1. Log in to Oracle Identity System Administration.
  2. In the left pane, under Configuration, click IT Resource.
  3. In the IT Resource Name field on the Manage IT Resource page, enter SuccessFactors and then click Search.
  4. Click the Edit icon for the IT resource.
  5. From the list at the top of the page, select Details and Parameters.
  6. Specify values for the parameters of the IT resource. Table 2-1 describes each parameter.

    Table 2-1 Parameters of the SuccessFactors IT Resource

    Parameter Description

    Configuration Lookup

    Name of the lookup definition that stores configuration information used during reconciliation and provisioning operations.

    Default value: Lookup.SuccessFactors.Configuration

    Connector Server Name

    If you have deployed the SuccessFactors connector in the Connector Server, then enter the name of the IT resource for the Connector Server.

    authenticationType

    Type of authentication used by your target system. This connector supports OAuth2.0 and Basic authentication mechanisms.

    Default value: oauth_saml

    If OAuth2.0 is enabled, set the parameter value to oauth_saml; otherwise, set the parameter value to basic.

    clientId

    Enter the client identifier (a unique string) issued by the authorization server to your client application during the registration process. You obtained the client ID while performing the procedure described in Preinstallation.

    authenticationServerUrl

    Enter the URL of the authentication server that validates the client ID and client secret for your target system.

    Sample value: https://apisalesdemo4.successfactors.com/oauth/token?
    authorizationUrl

    Authorization URL is the URL which returns the access token. Ensure that you provide correct parameters and their values to receive an access token.

    Sample value: https://apisalesdemo4.successfactors.com/oauth/idp
    clientUrl

    This is the attribute that provides the Sandbox URL. This Sandbox URL needs to be registered with the target resource.

    Sample value: https://apisalesdemo4.successfactors.com
    companyId Enter the company ID for user provisioning. During licensing of SuccessFactors solution, a unique company ID is provided. The OData API uses the company ID attribute to validate your access token.

    Host

    Enter the host name of the computer hosting your target system.

    Sample value: apisalesdemo4.successfactors.com
    privateKeyLocation Enter location of the certificate.

    During the client application creation process, a certificate gets stored. For certificate information, refer to the procedure described in Preinstallation.

    Port

    Enter the port number at which the target system is listening.

    Sample value: 443

    sslEnabled

    If the target system requires SSL connectivity, then set the value of this parameter to true. Otherwise set the value to false.

    Default value: true
    username Enter the username which has permissions to perform all the Identity Management features using APIs.

    When you purchase a Sandbox, this username is provided by the SAP SuccessFactors organization.

    Sample value: johnsmith
  7. To save the values, click Update.

2.2.3.2 Specifying Values for the IT Resource Parameters

The IT resource for the target system contains connection information about the target system. Oracle Identity Manager uses this information during provisioning and reconciliation.

The SuccessFactors IT resource is automatically created when you run the Connector Installer. You must specify values for the parameters as follows:

  1. Log in to Oracle Identity System Administration.
  2. In the left pane, under Configuration, click IT Resource.
  3. In the IT Resource Name field on the Manage IT Resource page, enter SuccessFactors and then click Search.
  4. Click the edit icon for the IT resource.
  5. From the list at the top of the page, select Details and Parameters.
  6. Specify values for the parameters of the IT resource, SuccessFactors. See IT Resource Parameters for information about IT resource parameters.
  7. To save the values, click Update.

2.3 Postinstallation

Postinstallation for the connector involves configuring Oracle Identity Manager, enabling logging to track information about all connector events, and configuring SSL. It also involves performing some optional configurations such as localizing the user interface.

The postinstallation tasks are divided across the following sections:

2.3.1 Configuring Oracle Identity Manager

You must create a UI form and an application instance for the resource against which you want to perform reconciliation and provisioning operations. In addition, you must run entitlement and catalog synchronization jobs.

These procedures are described in the following sections:

2.3.1.1 Creating and Activating a Sandbox

You must create and activate a sandbox to begin using the customization and form management features. You can then publish the sandbox to make the customizations available to other users.

See Managing Sandboxes in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager for instructions on creating and activating a sandbox.

2.3.1.2 Creating a New UI Form

You can use Form Designer in Oracle Identity System Administration to create and manage application instance forms.

See Managing Forms in Oracle Fusion Middleware Administering Oracle Identity Manager for instructions on creating a new UI form. While creating the UI form, ensure that you select the resource object corresponding to the SuccessFactors connector that you want to associate the form with. In addition, select the Generate Entitlement Forms check box.

2.3.1.3 Creating an Application Instance

Create an application instance as follows. For detailed instructions, see Managing Application Instances in Oracle Fusion Middleware Administering Oracle Identity Manager.

  1. In the left pane of the System Administration console, under Configuration, click Application Instances. The Application Instances page is displayed.
  2. From the Actions menu, select Create. Alternatively, click Create on the toolbar. The Create Application Instance page is displayed.
  3. Specify values for the following fields:

    • Name: The name of the application instance.

    • Display Name: The display name of the application instance.

    • Description: A description of the application instance.

    • Resource Object: The resource object name. Click the search icon next to this field to search for and select SuccessFactors User.

    • IT Resource Instance: The IT resource instance name. Click the search icon next to this field to search for and select SuccessFactors.

    • Form: Select the form name. See Creating a New UI Form.

  4. Click Save. The application instance is created.
  5. Publish the application instance to an organization to make the application instance available for requesting and subsequent provisioning to users. See Managing Organizations Associated With Application Instances in Oracle Fusion Middleware Administering Oracle Identity Manager for detailed instructions.

2.3.1.4 Publishing a Sandbox

Before you publish a sandbox, perform the following procedure as a best practice to validate all sandbox changes made till this stage as it is hard to revert changes once a sandbox is published:
  1. In the System Administration, deactivate the sandbox.
  2. Log out of the System Administration.
  3. Log in to the Self Service using the xelsysadm user credentials and then activate the sandbox that you deactivated in Step 1.
  4. In the Catalog, ensure that the SuccessFactors application instance form appears with correct fields.
  5. Publish the sandbox. See Publishing a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager for instructions on publishing a sandbox.

2.3.1.5 Harvesting Entitlements and Sync Catalog

You can populate Entitlement schema from child process form table, and harvest roles, application instances, and entitlements into catalog. You can also load catalog metadata.

To harvest entitlements and sync catalog:
  1. Run the scheduled jobs for lookup field synchronization listed in Scheduled Jobs for Lookup Field Synchronization.
  2. Run the Entitlement List scheduled job to populate Entitlement Assignment schema from child process form table.
  3. Run the Catalog Synchronization Job scheduled job. See Predefined Scheduled Tasks in Oracle Fusion Middleware Administering Oracle Identity Manager.

2.3.1.6 Updating an Existing Application Instance with a New Form

For any changes you do in the Form Designer, you must create a new UI form and update the changes in an application instance. To update an existing application instance with a new form:
  1. Create a sandbox and activate it as described in Creating and Activating a Sandbox.
  2. Create a new UI form for the resource as described in Creating a New UI Form.
  3. Open the existing application instance.
  4. In the Form field, select the new UI form that you created.
  5. Save the application instance.
  6. Publish the sandbox as described in Publishing a Sandbox.

2.3.1.7 Updating an Existing Field for Provisioning

During a user provisioning operation, the target system requires a few mandatory fields. When these fields, which are required to be mandatory in the target system, are not mandatory fields in the Oracle Identity Manager, in such a scenario the provisioning operation will not be successful.

For the provisioning operation to be successful, you need to edit an existing field in the Oracle Identity Manager and make it mandatory. Using the Form Designer, you can modify fields and update them from an optional type to a mandatory type.

Note:

When you perform any changes in the Form Designer, you must create a new UI form and update the changes in an application instance.
To edit a field within a new form:
  1. Log in to Oracle Identity Manager Design Console.
  2. Expand Development Tools and double-click Form Designer.
  3. Click Create New Version from the Form Designer pane.
  4. Enter a name for the newly created form.
  5. On the Properties tab:
    1. Scroll and select the field which is under consideration.
    2. Click Add Property. The Add Property dialog box appears.
    3. In the Add Property dialog box, select Required from the Property Name drop-down list and enter a new value in the Property Value box.
    4. Click Save.
  6. Click Make Version Active.
  7. Click Save.

2.3.1.8 Updating an Existing Field for Reconciliation

During a reconcile operation, the target system requires a few mandatory fields to be present in Oracle Identity Manager. The reconciliation operation will not be successful when these mandatory fields are not present in Oracle Identity Manager.

For the reconciliation operation to be successful, you need to edit an existing field in the Oracle Identity Manager and make it mandatory. Using Design Console and Resource Objects, you can modify fields and update them from an optional type to a mandatory type.

To edit an existing field:

  1. Log in to Oracle Identity Manager Design Console.
  2. Expand Resource Objects and then double-click Resource Objects.
  3. Scroll and double-click the field under consideration. The Add Reconciliation Field dialog box appears.
  4. In the Add Reconciliation Field dialog box, select the Required check box to modify the attribute as a required type.
  5. Click Save to save changes in the Add Reconciliation Field dialog box.
  6. Click Create Reconciliation Profile after a successful save operation.
  7. Scroll and double-click the field under consideration. The Edit Reconciliation Field Mapping dialog box appears.
  8. In the Edit Reconciliation Field Mapping dialog box, select the Key Field for Reconciliation Mapping check box to modify the attribute as a required type.
  9. Click Save to save the changes in the Edit Reconciliation Field Mapping dialog box.
  10. Click Save.

2.3.2 Localizing Field Labels in UI Forms

You can localize UI form field labels by using the resource bundle corresponding to the language you want to use. Resource bundles are available in the connector installation media.

To localize field label that you add to in UI forms:
  1. Log in to Oracle Enterprise Manager.
  2. In the left pane, expand Application Deployments and then select oracle.iam.console.identity.sysadmin.ear.
  3. In the right pane, from the Application Deployment list, select MDS Configuration.
  4. On the MDS Configuration page, click Export and save the archive to the local computer.
  5. Extract the contents of the archive, and open the following file in a text editor: 
    SAVED_LOCATION\xliffBundles\oracle\iam\ui\runtime\BizEditorBundle_en.xlf"
  6. Edit the BizEditorBundle.xlf file in the following manner:

    1. Search for the following text:

      <file source-language="en" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">

    2. Replace with the following text:

      <file source-language="en" target-language="LANG_CODE" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">
      In this text, replace LANG_CODE with the code of the language that you want to localize the form field labels. The following is a sample value for localizing the form field labels in Japanese: 
       <file source-language="en" target-language="ja" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">

    3. Search for the application instance code. This procedure shows a sample edit for SuccessFactors Application instance. The original code is:

       <trans-unit id="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBundle']
['persdef.sessiondef.oracle.iam.ui.runtime.form.model.user.entity.userEO.UD_USER_NAME__c_description']}
"><source>User Name</source><target/></trans-unit><trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.
RSAForm.entity.SuccessFactorsFormEO.UD_USER_NAME __c_LABEL"><source>First Name</source><target/></trans-unit>
    4. Open the resource file from the connector package, for example SuccessFactors_ja.properties, and get the value of the attribute from the file, for example, 
      global.udf.UD_GA_USR_ USER_NAME =\u30A2\u30AB\u30A6\u30F3 \u30C8\u540D.

    5. Replace the original code shown in Step 6.c with the following:

      <trans-unit id="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBu ndle']
['persdef.sessiondef.oracle.iam.ui.runtime.form.model.user.entity.use rEO.UD_GA_USR_ USER_NAME __c_description']}
"><source>Account Name</source> <target>u30A2\u30AB\u30A6\u30F3\u30C8\u540D</target></trans-unit> 
<trans-unitid="sessiondef.oracle.iam.ui.runtime.form.model.SuccessFactors.entity sEO.UD_GA_USR_ACCOUNT_NAME__c_LABEL">
<source>Account Name</source> <target>\u30A2\u30AB\u30A6\u30F3\u30C8\u540D</target> </trans-unit>

    6. Repeat Steps 6.a through 6.d for all attributes of the process form.

    7. Save the file as BizEditorBundle_LANG_CODE.xlf. In this file name, replace LANG_CODE with the code of the language to which you are localizing. Sample file name: BizEditorBundle_ja.xlf.

  7. Repackage the ZIP file and import it into MDS.
  8. Log out of and log in to Oracle Identity Manager.

2.3.3 Clearing Content Related to Connector Resource Bundles from the Server Cache

When you deploy the connector, the resource bundles are copied from the resources directory on the installation media into the Oracle Identity Manager database. Whenever you add a new resource bundle to the connectorResources directory or make a change in an existing resource bundle, you must clear content related to connector resource bundles from the server cache.

To clear content related to connector resource bundles from the server cache:
  1. In a command window, switch to the OIM_HOME/server/bin directory.
  2. Enter one of the following commands:

    • On Microsoft Windows: PurgeCache.bat All

    • On UNIX: PurgeCache.sh All

    Note:

    You can use the PurgeCache utility to purge the cache for any content category. Run PurgeCache.bat CATEGORY_NAME on Microsoft Windows or PurgeCache.sh CATEGORY_NAME on UNIX. The CATEGORY_NAME argument represents the name of the content category that must be purged.
    For example, the following commands purge Metadata entries from the server cache:

    • PurgeCache.bat MetaData

    • PurgeCache.sh MetaData

    Before running the PurgeCache utility, ensure the WL_HOME and JAVA_HOME environment variables are set.

    When prompted, enter the user name and password of an account belonging to the SYSTEM ADMINISTRATORS group. In addition, you are prompted to enter the service URL in the following format:

    t3://OIM_HOST_NAME:OIM_PORT_NUMBER

    In this format:

    • Replace OIM_HOST_NAME with the host name or IP address of the Oracle Identity Manager host computer.

    • Replace OIM_PORT_NUMBER with the port on which Oracle Identity Manager is listening.

2.3.4 Managing Logging for the SAP SuccessFactors Connector

Oracle Identity Manager uses the Oracle Diagnostic Logging (ODL) logging service for recording all types of events pertaining to the connector.

The following topics provide detailed information about logging:

2.3.4.1 Understanding Log Levels

When you enable logging, Oracle Identity Manager automatically stores in a log file information about events that occur during the course of provisioning and reconciliation operations. ODL is the principle logging service used by Oracle Identity Manager and is based on java.util.Logger. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:

  • SEVERE.intValue()+100

    This level enables logging of information about fatal errors.

  • SEVERE

    This level enables logging of information about errors that might allow Oracle Identity Manager to continue running.

  • WARNING

    This level enables logging of information about potentially harmful situations.

  • INFO

    This level enables logging of messages that highlight the progress of the application.

  • CONFIG

    This level enables logging of information about fine-grained events that are useful for debugging.

  • FINE, FINER, FINEST

    These levels enable logging of information about fine-grained events, where FINEST logs information about all events.

These message types are mapped to ODL message type and level combinations as shown in Table 2-2

Table 2-2 Log Levels and ODL Message Type:Level Combinations

Java Level ODL Message Type:Level

SEVERE.intValue()+100

INCIDENT_ERROR:1

SEVERE

ERROR:1

WARNING

WARNING:1

INFO

NOTIFICATION:1

CONFIG

NOTIFICATION:16

FINE

TRACE:1

FINER

TRACE16

FINEST

TRACE32

The configuration file for OJDL is logging.xml, which is located at the following path: DOMAIN_HOME/config/fmwconfig/servers/OIM_SERVER/logging.xml

Here, DOMAIN_HOME and OIM_SEVER are the domain name and server name specified during the installation of Oracle Identity Manager.

2.3.4.2 Enabling Logging

To enable logging in Oracle WebLogic Server:
  1. Edit the logging.xml file as follows:

    1. Add the following blocks in the file:

      <log_handler name='SuccessFactors-handler' level='[LOG_LEVEL]'class='oracle.core.ojdl.logging.ODLHandlerFactory'> 
        <property name='logreader:' value='off'/> 
        <property name='path' value='[FILE_NAME]'/>     
        <property name='format' value='ODL-Text'/>        
        <property name='useThreadName' value='true'/> 
        <property name='locale' value='en'/> 
        <property name='maxFileSize' value='5242880'/> 
        <property name='maxLogSize' value='52428800'/>
        <property name='encoding' value='UTF-8'/>
</log_handler> 

      <logger name="ORG.IDENTITYCONNECTORS.SuccessFactors" level="[LOG_LEVEL]" useParentHandlers="false">
        <handler name="SuccessFactors-handler"/>
        <handler name="console-handler"/>
</logger>
    2. Replace both occurrences of [LOG_LEVEL] with the ODL message type and level combination that you require. Table 2-2 lists the supported message type and level combinations. Similarly, replace [FILE_NAME] with the full path and name of the log file in which you want log messages to be recorded. The following blocks show sample values for [LOG_LEVEL] and [FILE_NAME]: 
      <log_handler name='SuccessFactors-handler' level='NOTIFICATION:1'class='oracle.core.ojdl.logging.ODLHandlerFactory'> 
        <property name='logreader:' value='off'/> 
        <property name='path' value='F:\MyMachine\middleware\user_projects\domains\base_domain1\servers\oim_server1\logs\oim_server1-diagnostic-1.log'/>
        <property name='format' value='ODL-Text'/>        
        <property name='useThreadName' value='true'/> 
        <property name='locale' value='en'/> 
        <property name='maxFileSize' value='5242880'/> 
        <property name='maxLogSize' value='52428800'/> 
        <property name='encoding' value='UTF-8'/>
</log_handler>
        
<logger name="ORG.IDENTITYCONNECTORS.SuccessFactors" level="NOTIFICATION:1" useParentHandlers="false">
        <handler name="SuccessFactors-handler"/> 
        <handler name="console-handler"/>
</logger>

    With these sample values, when you use Oracle Identity Manager, all messages generated for this connector that are of a log level equal to or higher than the NOTIFICATION:1 level are recorded in the specified file.

  2. Save and close the file.
  3. Set the following environment variable to redirect the server logs to a file:

    • For Microsoft Windows: set WLS_REDIRECT_LOG=FILENAME

    • For UNIX: export WLS_REDIRECT_LOG=FILENAME

    Replace FILENAME with the location and name of the file to which you want to redirect the output.

  4. Restart the application server.

2.3.5 Configuring SSL for the SAP SuccessFactors

You configure SSL to secure data communication between Oracle Identity Manager and the target system.

To configure SSL:
  1. Obtain the SSL public key certificate of SuccessFactors.
  2. Copy the public key certificate of SuccessFactors to the computer hosting Oracle Identity Manager.
  3. Run the following keytool command to import the public key certificate into the identity key store in Oracle Identity Manager:
    keytool -import -alias ALIAS -trustcacerts -file CERT_FILE_NAME -keystore KEYSTORE_NAME -storepass PASSWORD
    In this command:

    • ALIAS is the public key certificate alias.

    • CERT_FILE_NAME is the full path and name of the certificate store (the default is cacerts).

    • KEYSTORE_NAME is the name of the keystore.

    • PASSWORD is the password of the keystore.

    The following is a sample value for this command:

    keytool -import -alias serverwl -trustcacerts -file supportcert.pem -keystore client_store.jks -storepass weblogic1

    Note:

    • Change the parameter values passed to the keytool command according to your requirements. Ensure that there is no line break in the keytool arguments.

    • Ensure that the system date for Oracle Identity Manager is in sync with the validity date of the SSL certificate to avoid any errors during SSL communication.