The procedure to deploy the connector is divided across three stages namely preinstallation, installation, and postinstallation.
The following topics provide details on these stages:
Preinstallation involves setting up a developer sandbox and obtaining the consumer key value. It also involves registering your partner application with Concur for accessing user management APIs.
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 Concur connector:
You can run the connector code either locally in Oracle Identity Manager or remotely in a Connector Server.
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 Configuring the IT Resource for the Target System.
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. For information about installing, configuring, and running the Connector Server, and then installing the connector in a Connector Server, see Using an Identity Connector Server in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
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.
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.
This section contains the following topics:
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.
Table 2-1 displays each parameter of the Concur IT resource in an alphabetical order.
Table 2-1 IT Resource Parameters
Parameter | Description |
---|---|
authenticationServerUrl |
Enter the URL of the authentication server that validates the consumer key for your target system. Sample value: |
authenticationType |
Type of authentication that is used by your target system. This connector supports the OAuth 2.0 custom authentication type. Default value: Do not modify the value of the parameter. |
customAuthHeaders |
Enter the consumer key in the following format:
In this format, replace CONSUMER_KEY with the consumer key that is assigned to you after you register for the Concur developer sandbox. Sample value: See Preinstallation for more information on obtaining the consumer key. |
Configuration Lookup |
Name of the lookup definition that stores configuration information used during the reconciliation and provisioning operations. Default value: Lookup.Concur.Configuration |
Connector Server Name |
If you have deployed the Concur connector in the Connector Server, then enter the name of the IT resource for the Connector Server. |
host |
Enter the host name of the computer hosting your target system. Sample value: |
password |
Enter the password for connecting to the Connector platform. This is the password that you specified while registering for the Concur developer sandbox. |
port |
Enter the port number at which the target system is listening. |
proxyHost |
Enter the name of the proxy host that is used to connect to an external target. Sample value: |
proxyPort |
Enter the proxy port number. |
proxyUser |
Enter the proxy user name of the target system user account that Oracle Identity Manager uses to connect to the target system. |
proxyPassword |
Enter the password of the proxy user ID of the target system user account that Oracle Identity Manager uses to connect to the target system. |
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: |
username |
Enter the user name for connecting to the Concur platform. This is the email address that you specified while registering for the Concur developer sandbox. |
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 steps are divided across the following sections:
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 the entitlement and catalog synchronization jobs.
The following topics describe the procedures to configure Oracle Identity Manager:
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 Creating a Sandbox and Activating and Deactivating a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
You can use Form Designer in Oracle Identity System Administration to create and manage application instance forms. See Creating Forms By Using the Form Designer in Oracle Fusion Middleware Administering Oracle Identity Manager.
While creating the UI form, ensure that you select the resource object corresponding to the Concur connector that you want to associate the form with. In addition, select the Generate Entitlement Forms check box.
By default, an application instance named Concur Application Instance is automatically created after you install the connector. You must associate this application instance with the form created in Creating a New UI Form. See Modifying Application Instances in Oracle Fusion Middleware Administering Oracle Identity Manager.
After updating the application instance, you must publish it to an organization to make the application instance available for requesting and subsequent provisioning to users.
As a best practice, perform the following procedure before publishing the application instance:
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.
See Also:
Predefined Scheduled Tasks in Oracle Fusion Middleware Administering Oracle Identity Governance for a description of the Entitlement List and Catalog Synchronization Job scheduled jobs.
You can localize UI form field labels by using the resource bundle corresponding to the language you want to use. The resource bundles are available in the connector installation media.
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.
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:
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.
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_SERVER are the domain name and server name specified during the installation of Oracle Identity Manager.