# Connecting SailPoint and Oracle PeopleSoft HCM Database To connect SailPoint with Oracle PeopleSoft HCM Database, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Configure**. 5. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 6. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 7. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 8. Under **Connection Type**, select **Direct Connection** or **Flat File**. - **Direct Connection** - A direct connection fetches data from the **Virtual Appliance Cluster** you choose as the application connector for the source. A direct connection configuration allows for real-time updates. For more information about configuring and deploying virtual appliances, refer to the [Virtual Appliance Reference Guide](). - **Flat File** - Select the flat file if no connector is available, or if another system restricts the connection. This option allows only reading and aggregating data as a generic/delimited application. Provisioning activity is unsupported, and additional configuration pages like connection settings and aggregation settings are unavailable. 9. If you selected **Direct Connection**, in **Virtual Appliance Cluster**, select the virtual appliance cluster that will be used as the application connector for the source. 10. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 11. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 12. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. In the **Virtual Appliance Cluster** dropdown list, select the virtual appliance to use when communicating with your organization's systems. For more information, refer to [SailPoint Virtual Appliances](). 4. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 5. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 6. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 7. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 8. Select **Save**. ## Connector Files 1. Select **Upload Files** to upload the .jar file used for the source. Depending on your database upload the following .jar files: > **Screenshot** > > [![Connector Files]()]() - Upload the SQL server jar file for Microsoft SQL Server database. For more information, refer to [Download - JDBC Driver for SQL Server](). - Visit the Oracle website and download an appropriate Oracle JDBC driver. > **Warning** > > Ensure that the file you upload is not vulnerable or malicious. > **Note** > > You must download the library from a trusted source and validate the authenticity of the download location via inspection of valid SSL/TLS certificates. You must also validate the authenticity of the library by inspecting digital signatures or validating checksums when that information is made available. 2. Select **Save**. ## Connection Settings Provide the information required to connect and interact with the source. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Enter the **User Name** and **Password** for the user that connects to the host of the database. 2. Enter the **Database URL** that connects to the database. 3. Enter the JDBC **Driver Class** to use for the connection. - For Oracle - oracle.jdbc.driver.OracleDriver - For Microsoft SQL Server - com.microsoft.sqlserver.jdbc.SQLServerDriver - For IBM DB2 - com.ibm.db2.jcc.DB2Driver ### Provisioning Credentials > [!NOTE] > > **Screenshot** > > [![Provisioning Credentials]()]() 1. Enter the **Host** and **Port** of the PeopleSoft server. 2. Enter the **Username** and **Password** used to authenticate with the PeopleSoft server. 3. If your PeopleSoft server requires a domain connection password for authentication, enable the option for **Domain Connection Password Enabled** and enter the **Domain Connection Password**. 4. Select **Save**. ## Aggregation Settings For more information about aggregation, refer to [Loading Account Data](). Provide the settings for your aggregation. > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() To configure your aggregation, complete the following: 1. In **SQL Query**, enter a SQL statement to aggregate personal records. The default query fetches personal records including email and phone numbers. > **Note** > > If **SQL Query** has the where clause with "?", then you must specify the ORDER BY clause to aggregate all records correctly. 2. In **getObjectSQL Query**, enter a SQL statement to aggregate only one person record at a time. SailPoint recommends updating this query when you update the **SQL Query**. 3. In **Person Sub Query**, enter a SQL statement to aggregate job records from the database. 4. Select the **Exclude Inactive Persons** checkbox to exclude inactive persons from aggregation. 5. Enter the **Page Size** to specify the number of records to display per page. Default: 1000, Minimum value: 50. 6. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation.