4 Performing the Postconfiguration Tasks for the Concur Connector
These are the tasks that you must perform after creating an application in Oracle Identity Governance.
4.1 Configuring Oracle Identity Governance
During application creation, if you did not choose to create a default form, then you must create a UI form for the application that you created by using the connector.
Note:
Perform the procedures described in this section only if you did not choose to create the default form during creating the application.The following topics describe the procedures to configure Oracle Identity Governance:
4.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 Creating a Sandbox and Activating a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance.
4.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 Creating Forms By Using the Form Designer in Oracle Fusion Middleware Administering Oracle Identity Governance.
While creating the UI form, ensure that you select the resource object corresponding to the newly created application that you want to associate the form with. In addition, select the Generate Entitlement Forms check box.
4.1.3 Publishing a Sandbox
Before publishing a sandbox, perform this procedure as a best practice to validate all sandbox changes made till this stage as it is difficult to revert the changes after a sandbox is published.
-
In Identity System Administration, deactivate the sandbox.
-
Log out of Identity System Administration.
-
Log in to Identity Self Service using the xelsysadm user credentials and then activate the sandbox that you deactivated in Step 1.
-
In the Catalog, ensure that the application instance form for your resource appears with correct fields.
-
Publish the sandbox. See Publishing a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance.
4.1.4 Updating an Existing Application Instance with a New Form
For any changes that you do in the schema of your application in Identity Self Service, 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:
-
Create and activate a sandbox.
-
Create a new UI form for the resource.
-
Open the existing application instance.
-
In the Form field, select the new UI form that you created.
-
Save the application instance.
-
Publish the sandbox.
See Also:
-
Creating a Sandbox and Activating a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance
-
Creating Forms By Using the Form Designer in Oracle Fusion Middleware Administering Oracle Identity Governance
-
Publishing a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance
4.2 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.
- Run the Entitlement List scheduled job to populate Entitlement Assignment schema from child process form table.
- Run the Catalog Synchronization Job scheduled job.
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.
4.3 Managing Logging for the Connector Server
Oracle Identity Governance 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:
4.3.1 Understanding Log Levels
When you enable logging, Oracle Identity Governance 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 Governance 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 Governance 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 4-1.
Table 4-1 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 |
TRACE:16 |
FINEST |
TRACE:32 |
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 Governance.
4.4 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 Governance with your target system.
This section contains the following topics:
4.4.1 IT Resource Parameters
An IT resource is composed of parameters that store connection and other generic information about a target system. Oracle Identity Governance uses this information to connect to a specific installation or instance of your target system.
Table 4-2 displays each parameter of the Concur IT resource in an alphabetical order.
Table 4-2 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. Sample 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 Configuring the Target System 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. Sample 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 Governance 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 Governance 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. Sample 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. |
4.4.2 Specifying Values for IT Resource Parameters
- Log in to Identity System Administration.
- Create and activate a sandbox. See Creating a Sandbox and Activating and Deactivating a Sandbox in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
- In the left pane, under Configuration, click IT Resource.
- In the IT Resource Name field on the Manage IT Resource page, enter Concur and then click Search.
- Click the Edit icon for the IT resource.
- From the list at the top of the page, select Details and Parameters.
- Specify values for the parameters of the IT resource. IT Resource Parameters describes each parameter.
- To save the values, click Update.