Configuration Parameters

This section contains the information that this connector uses to connect and interact with the application. Each application type requires different information to create and maintain a connection. The configuration parameters for the Oracle HRMS connector are as follows.

Note
Attributes marked with an asterisk (*) are mandatory.

Note
The Oracle HRMS connector only aggregates organizational data with active persons and assignments.

A rule that is called for each row in the data file.

The password of the Connection User.

Oracle user minimum permissions mentioned in Required Permissions section.

For example, "apps"

URL for server which directly interacts with the Managed system.

For example, jdbc:oracle:thin:@xxx.xx.xx.xxx:xxxx:SID

Provide a valid EBS user name from FND_USER table that creates employee records in the HRMS application.

Note
The provisioning transactions to the Oracle HRMS system would be identified with this user name.

Name of the Driver class supported by JDBC Type 4.

For example:

oracle.jdbc.driver.OracleDriver

Additional Configuration Parameter

The following are additional configuration parameters that must be set in the application debug page:

To load certificates from custom truststore, add the sensitive attributes in the application debug page as follows:

Copy 
<entry key="additionalConnProperties">
    <value>
        <List>
            <String><trust store file parameter>=<path of trust store></String>
            <String><trust store type parameter>=<trust store type></String>
            <String><trust store password parameter>=$<placeholder variable>$</String>
        </List>
    </value>
</entry>
<entry key="encrypted" value="$<placeholder variable>$"/>
<entry key="$<placeholder variable>$" value="<actual password>"/>

  • If checked, it will include accounts that don't have a supervisor ID associated with them.

  • If unchecked, supervisor association is mandatory for the account to be aggregated.

  • If checked, this will aggregate persons whose user person type is not the default for the current system person type, along with persons whose user person type is default to the system person type.

  • If unchecked, this will aggregate only persons whose user person type is default to the system person type.

  • If this is checked, it will populate the HRMS inactive Record Effective From text field to enter the inactive offset date. It will include inactive accounts in aggregation from the inactive offset date to present day.

  • If this is unchecked, it will only include active accounts in aggregation.