Edward Whalen

This information describing how to configure a Windows DIPC Agent for SQL Server is entirely based on Autonomous DIPC 18.4.3 which is the latest version as of the time of publication.  Recently, DIPC was renamed to DIPC Classic and Autonomous DIPC was renamed to DIPC.

Prior to configuring the DIPC agent you must setup the agent as a confidential application in the Oracle Identity Cloud.  How to do this is covered in the Oracle Documentation “Using Data Integration Platform Cloud” under “Set up an Agent”.  This will be also covered in additional document from me.

Setting up the Windows DIPC agent for SQL Server involves downloading the agent, collecting information from the Identity Cloud and Setting up the agent.  Once the agent is up and running there are a few steps to setup GoldenGate replication that will be covered in subsequent blogs.

From the DIPC Console select Agents, then click on the Download button.  Select the OS (Linux or Windows) and products to be replicated to/from.  Note:  Some can only be targets (Big Data) and others both source and target.

Next download the agent by clicking the Download button.  Once you have downloaded it, unzip it in the desired location.  I prefer c:\oracle\dicloud but any location will work.

Prior to configuring the agent, you must download and install the Java Development Kit (JDK) and add it to the Windows environment.  JAVA_HOME must be set to the location of the JDK and the path must be modified to include the JAVA_HOME\bin directory.

Note:  Do not install the JDK under c:\Program Files or c:\Program Files (x86) or any directory that has a space in its name.  This will cause a problem with Oracle programs.

Once the agent has been downloaded you will need the following information in order to configure the Windows DIPC agent on SQL Server:

JAVA_HOME                 The 1.8 JDK must be installed and the JAVA_HOME environment variable must be configured.  The java executable must also be in the user’s path.

DICLOUD service host    This is the URL of your DIPC instance.  You can find this on the top of the browser that you are using to manage DIPC.

DICLOUD service port    This is usually 443 unless you have changed this in the DIPC console.

IDCS server URL            This is found at the bottom of the page under Services Instances of the Identity Cloud Service.  This, along with the agentIdcsScope are also provided as output from the Autonomous DIPC instance creation.

Agent IDCS Scope          This is also found in the end of the creation of the ADIPC instance.

IDCS Client ID                This is taken from the Confidential Application that you have created as part of the Identity Cloud.

IDCS Secret                   This is also taken from the Confidential Application that you have created as part of the Identity Cloud.

Username                     This is your DIPC username.

Password                      This is your DIPC password.

Once you have completed these tasks change directories to .\agent\<instance>\bin under the dicloud directory.  Here startup the agent using  .\startAgentInstance.sh  in order to start up the.  Once you have started the agent you should see it show up in the DIPC console as shown here:

Once the Windows DIPC agent for SQL Server is up and running you can create a connection to the database and/or Kafka or other source/target from the DIPC console.  Setting up connections and tasks will be covered in another paper.