Integrate Bing Search Results in Your Informatica Cloud Instance

Informatica Cloud allows you to perform extract, transform, and load (ETL) tasks in the cloud. With the Cloud Secure Agent and the CData JDBC Driver for Bing Search, you get live access to Bing Search results, directly within Informatica Cloud. In this article, we will walk through downloading and registering the Cloud Secure Agent, connecting to Bing Search through the JDBC Driver and generating a mapping that can be used in any Informatica Cloud process.

Informatica Cloud Secure Agent

To work with the Bing Search results through the JDBC Driver, install the Cloud Secure Agent.

1. Navigate to the Administrator page in Informatica Cloud
2. Select the Runtime Environments tab
3. Click "Download Secure Agent"
4. Make note of the Install Token
5. Run the installer on the client machine and register the Cloud Secure Agent with your username and install token

NOTE: It may take some time for all of the Cloud Secure Agent services to get up and running.

Connecting to the Bing Search JDBC Driver

With the Cloud Secure Agent installed and running, you are ready to connect to Bing Search through the JDBC Driver.

Adding the JDBC Driver to the Secure Agent Machine

1. Navigate to the following directory on the Secure Agent machine:
   %Secure Agent installation directory%/ext/connectors/thirdparty/
2. Create a folder and add the driver JAR file (cdata.jdbc.bing.jar) based on the type of mapping that you want to configure.

   For mappings, create the following folder and add the driver JAR file:

   informatica.jdbc_v2/common

   For mappings in advanced mode, also create the following folder and add the driver JAR file:

   informatica.jdbc_v2/spark
3. Restart the Secure Agent.

Connecting to Bing Search in Informatica Cloud

• Connection Name: Name your connection (i.e.: CData Bing Search Connection)
• Type: Select "JDBC_V2"
• Runtime Environment: Select the runtime environment where you installed the Secure Agent
• JDBC Driver Class Name: The name of the JDBC driver class: cdata.jdbc.bing.BingDriver
• JDBC Connection URL: Set this to the JDBC URL for Bing Search. Your URL will look similar to the following:
  
  jdbc:bing:APIKey=MyAPIKey;

  To connect to Bing, set the ApiKey connection property. To obtain the API key, sign into Microsoft Cognitive Services and register for the Bing Search APIs.

  Two API keys are then generated; select either one.

  When querying tables, the SearchTerms parameter must be supplied in the WHERE clause.

  Built-In Connection String Designer

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

  java -jar cdata.jdbc.bing.jar

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

• Username: Set this to a placeholder value (since Bing Search does not require a username)
• Password: Set this to a placeholder value (since Bing Search does not require a password)

Create a Mapping for Bing Search Results

With the connection to Bing Search configured, we can now access Bing Search results in any Informatica process. The steps below walk through creating a mapping for Bing Search to another data target.

1. Navigate to the Data Integration page
2. Click New.. and select Mapping from the Mappings tab
3. Click the Source Object and in the Source tab, select the Connection and set the Source Type
4. Click "Select" to choose the table to map
5. In the Fields tab, select the fields from the Bing Search table to map
6. Click the Target object and configure the Target source, table and fields. In the Field Mapping tab, map the source fields to the target fields.

With the mapping configured, you are ready to start integrating live Bing Search results with any of the supported connections in Informatica Cloud. Download a free, 30-day trial of the CData JDBC Driver for Bing Search and start working with your live Bing Search results in Informatica Cloud today.