Create Informatica Mappings From/To a JDBC Data Source for PingOne

Informatica provides a powerful, elegant means of transporting and transforming your data. By utilizing the CData JDBC Driver for PingOne, you are gaining access to a driver based on industry-proven standards that integrates seamlessly with Informatica's powerful data transportation and manipulation features. This tutorial shows how to transfer and browse PingOne data in Informatica PowerCenter.

Deploy the Driver

To deploy the driver to the Informatica PowerCenter server, copy the CData JAR and .lic file, located in the lib subfolder in the installation directory, to the following folder: Informatica-installation-directory\services\shared\jars\thirdparty.

To work with PingOne data in the Developer tool, you will need to copy the CData JAR and .lic file, located in the lib subfolder in the installation directory, into the following folders:

• Informatica-installation-directory\client\externaljdbcjars
• Informatica-installation-directory\externaljdbcjars

Create the JDBC Connection

Follow the steps below to connect from Informatica Developer:

1. In the Connection Explorer pane, right-click your domain and click Create a Connection.
2. In the New Database Connection wizard that is displayed, enter a name and Id for the connection and in the Type menu select JDBC.
3. In the JDBC Driver Class Name property, enter:

   cdata.jdbc.pingone.PingOneDriver

4. In the Connection String property, enter the JDBC URL, using the connection properties for PingOne.

   To connect to PingOne, configure these properties:

   • : The region where the data for your PingOne organization is being hosted.
   • : The type of authentication to use when connecting to PingOne.
   • Either (required when using the default PingOne domain) or , configured as described below.

   Configuring WorkerAppEnvironmentId

   is the ID of the PingOne environment in which your Worker application resides. This parameter is used only when the environment is using the default PingOne domain (auth.pingone). It is configured after you have created the custom OAuth application you will use to authenticate to PingOne, as described in Creating a Custom OAuth Application in the Help documentation.

   First, find the value for this property:

   1. From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
   2. Find the environment in which you have created your custom OAuth/Worker application (usually Administrators), and click Manage Environment. The environment's home page displays.
   3. In the environment's home page navigation sidebar, click Applications.
   4. Find your OAuth or Worker application details in the list.
   5. Copy the value in the Environment ID field. It should look similar to:
      

      WorkerAppEnvironmentId='11e96fc7-aa4d-4a60-8196-9acf91424eca'

   Now set to the value of the Environment ID field.

   Configuring AuthorizationServerURL

   is the base URL of the PingOne authorization server for the environment where your application is located. This property is only used when you have set up a custom domain for the environment, as described in the PingOne platform API documentation. See Custom Domains.

   Authenticating to PingOne with OAuth

   PingOne supports both OAuth and OAuthClient authentication. In addition to performing the configuration steps described above, there are two more steps to complete to support OAuth or OAuthCliet authentication:

   • Create and configure a custom OAuth application, as described in Creating a Custom OAuth Application in the Help documentation.
   • To ensure that the driver can access the entities in Data Model, confirm that you have configured the correct roles for the admin user/worker application you will be using, as described in Administrator Roles in the Help documentation.
   • Set the appropriate properties for the authscheme and authflow of your choice, as described in the following subsections.

   OAuth (Authorization Code grant)

   Set to OAuth.

   Desktop Applications

   Get and Refresh the OAuth Access Token

   After setting the following, you are ready to connect:

   • : GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the each time you connect, use .
   • : The Client ID you obtained when you created your custom OAuth application.
   • : The Client Secret you obtained when you created your custom OAuth application.
   • : The redirect URI you defined when you registered your custom OAuth application. For example: https://localhost:3333

   When you connect, the driver opens PingOne's OAuth endpoint in your default browser. Log in and grant permissions to the application. The driver then completes the OAuth process:

   1. The driver obtains an access token from PingOne and uses it to request data.
   2. The OAuth values are saved in the location specified in , to be persisted across connections.

   The driver refreshes the access token automatically when it expires.

   For other OAuth methods, including Web Applications, Headless Machines, or Client Credentials Grant, refer to the Help documentation.

   Built-in Connection String Designer

   For assistance in constructing the JDBC URL, use the connection string designer built into the PingOne JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

   java -jar cdata.jdbc.pingone.jar
   

   Fill in the connection properties and copy the connection string to the clipboard.

   👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
   

   A typical connection string is below:

   jdbc:pingone:AuthScheme=OAuth;WorkerAppEnvironmentId=eebc33a8-xxxx-4f3a-yyyy-d3e5262fd49e;Region=NA;OAuthClientId=client_id;OAuthClientSecret=client_secret;InitiateOAuth=GETANDREFRESH;

Browse PingOne Tables

After you have added the driver JAR to the classpath and created a JDBC connection, you can now access PingOne entities in Informatica. Follow the steps below to connect to PingOne and browse PingOne tables:

1. Connect to your repository.
2. In the Connection Explorer, right-click the connection and click Connect.
3. Clear the Show Default Schema Only option. 👁 The driver models PingOne entities as relational tables. (Salesforce is shown.)
   

You can now browse PingOne tables in the Data Viewer: Right-click the node for the table and then click Open. On the Data Viewer view, click Run.

Create PingOne Data Objects

Follow the steps below to add PingOne tables to your project:

1. Select tables in PingOne, then right-click a table in PingOne, and click Add to Project.
2. In the resulting dialog, select the option to create a data object for each resource.
3. In the Select Location dialog, select your project.

   Create a Mapping

   Follow the steps below to add the PingOne source to a mapping:

   1. In the Object Explorer, right-click your project and then click New -> Mapping.
   2. Expand the node for the PingOne connection and then drag the data object for the table onto the editor.
   3. In the dialog that appears, select the Read option.
   👁 The source PingOne table in the mapping. (Salesforce is shown.)
   

   Follow the steps below to map PingOne columns to a flat file:

   1. In the Object Explorer, right-click your project and then click New -> Data Object.
   2. Select Flat File Data Object -> Create as Empty -> Fixed Width.
   3. In the properties for the PingOne object, select the rows you want, right-click, and then click copy. Paste the rows into the flat file properties.
   4. Drag the flat file data object onto the mapping. In the dialog that appears, select the Write option.
   5. Click and drag to connect columns.

   To transfer PingOne data, right-click in the workspace and then click Run Mapping.

   👁 The completed mapping. (Salesforce is shown.)