1. Connectivity and Knowledge Modules Guide for Oracle Data Integrator
  2. Applications
  3. Oracle Sales Cloud

34 Oracle Sales Cloud

It is important to understand how to work with Oracle Sales Cloud in Oracle Data Integrator.

This chapter includes the following sections:

34.1 Introduction

Oracle Sales Cloud delivers high-value, industry-specific sales automation and sales performance management solutions.

Oracle Data Integrator (ODI) seamlessly integrates with Oracle Sales Cloud. Oracle Data Integrator features are designed to work best with Oracle Sales Cloud, including reverse-engineering and mappings.

34.1.1 Concepts

The Oracle Sales Cloud technology concepts map the Oracle Data Integrator concepts as follows: An Oracle Sales Cloud Instance corresponds to a data server in Oracle Data Integrator. Within this instance, a schema maps to an Oracle Data Integrator physical schema.

34.1.2 Knowledge Modules

Oracle Data Integrator provides no Knowledge Module (KM) specific to the Oracle Sales Cloud technology. You can use the generic SQL KMs to perform the data integration and transformation operations of Oracle Sales Cloud data. See Generic SQL for more information.

34.2 Installation and Configuration

Make sure you have read the information in this section before you start working with the Oracle Sales Cloud technology:

34.2.1 System Requirements and Certifications

Before performing any installation, you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing.

The list of supported platforms and versions is available on Oracle Technical Network (OTN):

http://www.oracle.com/technetwork/middleware/data-integrator/documentation/index.html

34.2.2 Technology Specific Requirements

There are no technology-specific requirements for using Oracle Sales Cloud in Oracle Data Integrator.

34.2.3 Connectivity Requirements

This section lists the requirements for connecting to the Oracle Sales Cloud database.

Oracle Sales Cloud JDBC Driver

Oracle Data Integrator uses the Oracle Sales Cloud JDBC Driver to connect to the Oracle Sales Cloud database.

34.3 Setting up the Topology

Setting up the topology consists of:

34.3.1 Creating an Oracle Sales Cloud Data Server

Create a data server for the Oracle Sales Cloud technology using the standard procedure, as described in Creating a Data Server of Administering Oracle Data Integrator. This section details only the fields required or specific for defining an Oracle Sales Cloud data server:
  1. In the Definition tab, enter the following fields:
    1. Name : Name of the data server that will appear in Oracle Data Integrator.
    2. User: User name for connecting to the data server.
    3. Password: Password for connecting to the data server.
  2. In the JDBC tab, enter the following values:
    1. JDBC Driver: weblogic.jdbc.oraclesalescloud.OracleSalesCloudDriver
    2. JDBC URL : jdbc:weblogic:oraclesalescloud://<base_url>;WSCompressData=none

    where base_url specifies the base URL of the Oracle Sales Cloud site to which you are connecting (for example, mysite.custhelp.com). This value should not include an internet protocol such as 'http://' or 'https://'.

  3. Click Test Connection, to test the established connection.

    Note:

    In some cases, you may encounter the following error: "The configuration options used to open the database do not match the options used to create the database"

    If such an error occurs, you need to add "CreateDB=forceNew" to the JDBC URL (that is, jdbc:weblogic:oraclesalescloud://<base_url>;WSCompressData=none;CreateDB=forceNew). Once the connection is successful, you need to remove "CreateDB=forceNew" and keep only "WSCompressData=none" in the JDBC URL.

34.3.2 Creating an Oracle Sales Cloud Physical Schema

Create a physical schema for the Oracle Sales Cloud data server using the standard procedure, as described in Creating a Physical Schema in Administering Oracle Data Integrator.
Create a logical schema for this physical schema using the standard procedure, as described in Creating a Logical Schema in Administering Oracle Data Integrator, and associate it in a given context.

34.4 Creating and Reverse-Engineering an Oracle Sales Cloud Model

This section contains the following topics:

34.4.1 Creating an Oracle Sales Cloud Model

Create an Oracle Sales Cloud model using the standard procedure, as described in Creating a Model of Developing Integration Projects with Oracle Data Integrator.

34.4.2 Reverse-engineer an Oracle Sales Cloud Model

Oracle Sales Cloud supports Standard reverse-engineering - which uses only the abilities of the JDBC driver.

To perform a Standard reverse-engineering on an Oracle Sales Cloud model, use the usual procedure, as described in Reverse-engineering a Model of Developing Integration Projects with Oracle Data Integrator.

34.5 Designing a Mapping

You can use Oracle Sales Cloud as a source or a target of a mapping. The KM choice for a mapping determines the abilities and performance of this mapping.

Oracle Data Integrator does not provide specific knowledge modules for Oracle Sales Cloud. Use the Generic SQL KMs or the KMs specific to the technology used as the staging area.