Connectors → Oracle B2C Service

About Oracle B2C Service

Oracle B2C Service delivers comprehensive customer experience applications that drive revenue, increase efficiency, and build loyalty.

You can easily extract from Oracle B2C Service REST API into Incorta. Using the Data Wizard or Schema Wizard, the connector supports extracting data from the Connect Common Object Model (CCOM).

In addition, the connector also supports read-only extraction from the RightNow Object Query Language (ROQL) managed tables. After creating your initial physical schema, you can create additional physical schema tables for your Oracle B2C external data source. In the table data source properties, you can specify both a Discovery Query and normal Query using ROQL.

About the Oracle B2C Connector

The Oracle B2C connector supports the following Incorta specific functionality:

Feature	Supported
Chunking	✔
Data Agent
Encryption at Ingest
Incremental Load	✔
Multi-Source
OAuth
Performance Optimized	✔
Remote
Single-Source	✔
Spark Extraction
Webhook Callbacks	✔

Note

The Oracle B2C Connector is available starting with the 5.1.2 release.

Steps to connect Oracle B2C and Incorta

To connect Oracle B2C and Incorta, here are the high level steps, tools, and procedures:

Create an external data source
Create a physical schema with the Schema Wizard
or, Create a physical schema with the Schema Designer
Load the physical schema
Explore the physical schema

Create an external data source

Here are the steps to create a external data source with the Oracle B2C connector:

Sign in to the Incorta Direct Data Platform.
In the Navigation bar, select Data.
In the Action bar, select + New → Add Data Source.
In the Choose a Data Source dialog, in Application, select Oracle B2C.
In the New Data Source dialog, specify the applicable connector properties.
To test, select Test Connection.
Select Ok to save your changes.

Oracle B2C Service connector properties

Your Oracle B2C administrator can assist you with the connector properties such as the Domain, Username, and Password. Here are the properties for the Oracle B2C Service connector properties:

Property	Control	Description
Data Source Name	text box	Enter the name of the data source source
Domain	text box	Enter the HTTPS URL, for example: `https://mycompany.custhelp.com/services/rest/connect/v1.4`
Username	text box	Enter the username
Password	text box	Enter the password
Max Number Of Concurrent Requests	text box	Enter the maximum number of current request. The default is 10.
Max Number Of Requests Per Minute	text box	Enter the maximum number of request per minute. The default is 45.

Create a physical schema with the Schema Wizard

Here are the steps to create an Oracle B2C physical schema with the Schema Wizard:

Sign in to the Incorta Direct Data Platform.
In the Navigation bar, select Schema.
In the Action bar, select + New → Schema Wizard.
In (1) Choose a Source, specify the following:
- For Enter a name, enter the schema name.
- For Select a Datasource, select the Oracle B2C external data source.
- Optionally create a description.
In the Schema Wizard footer, select Next.
In (2) Manage Tables, in the Data Panel, first select the name of the Data Source, and then check the Select All checkbox.
In the Schema Wizard footer, select Next.
In (3) Finalize, in the Schema Wizard footer, select Create Schema.

Create a physical schema with the Schema Designer

Here are the steps to create an Oracle B2C physical schema using the Schema Designer:

Sign in to the Incorta Direct Data Platform.
In the Navigation bar, select Schema.
In the Action bar, select + New → Create Schema.
In Name, specify the physical schema name, and select Save.
In Start adding tables to your schema, select Oracle B2C.
In the Data Source dialog, specify the Oracle B2C table data source properties.
Select Add.
In the Table Editor, in the Table Summary section, enter the table name.
To save your changes, select Done in the Action bar.

Oracle B2C table data source properties

For a physical schema table in Incorta, you can define the following Oracle B2C specific data source properties as follows:

Property	Control	Description
Data Source Name	text box	Enter the name of the data source
Host URL	text box	Enter the URL of the Oracle Sales Cloud server
ROQL Managed Table	toggle	Enable to enter a discovery query for tables that are not exposed in the Connect Common Object Model (CCOM).
ROQL Managed Table → Discovery Query	text box	For a table that is not exposed in the CCOM, enter a query to discover the table and its columns using the `DESCRIBE` command. If `DESCRIBE` is not supported, use a `SELECT` command with a `LIMIT 1` clause.
Query	text box	Enter the ROQL query using SQL syntax. For examples, see Query ROQL Managed Tables.
Use Reporting Database	toggle	Enable to use the reporting database
Enable chunking	toggle	Enable to chunk the query. If you receive the `This query is not supported: Poor performing query - too many rows examined` message, enable chunking and configure the chunk to at least 5 days of rows.
Enable chunking → Use Parallel Processing For Chunking	toggle	Enable to support parallel processing
Enable chunking → Chunking Column	drop down list	Select a supported column that is of the type Date or Timestamp
Enable chunking → Full Load Start Date	text box	Enter the start date using the Java date format: `yyyy-MM-dd`, for example: `2019-01-01`)
Enable chunking → Full Load End Date	text box	Specify an end date for the query chunk using the Java date format: `yyyy-MM-dd`, for example: `2021-01-01`. To specify the current date, leave this property empty.
Incremental	toggle	Enable to support incremental loads using a `SELECT` command for the Update Query Property
Incremental → Update Query	text box	Enter the ROQL query using a `SELECT` command . For examples, see Query ROQL Managed Tables.
Callback	toggle	Enable post extraction callback, that is, enable callback on the data source data set(s) by invoking a certain callback URL with parameters containing details about the load job.
Callback URL	text box	Enable Callback to configure this property. Specify the callback URL.

View the schema diagram with the Schema Diagram Viewer

Here are the steps to view the schema diagram using the Schema Diagram Viewer:

Sign in to the Incorta Direct Data Platform.
In the Navigation bar, select Schema.
In the list of schemas, select the Oracle B2C physical schema.
In the Schema Designer, in the Action bar, select Diagram.

Load the physical schema

Here are the steps to perform a Full Load of the Oracle B2C physical schema using the Schema Designer:

Sign in to the Incorta Direct Data Platform.
In the Navigation bar, select Schema.
In the list of schemas, select the Oracle B2C physical schema.
In the Schema Designer, in the Action bar, select Load → Load Now → Full.
To review the load status, in Last Load Status, select the date.

Explore the physical schema

With the full load of the Oracle B2C schema complete, you can use the Analyzer to explore the schema, create your first insight, and save the insight to a new dashboard.

To open the Analyzer from the schema, follow these steps:

In the Navigation bar, select Schema.
In the Schema Manager, in the List view, select the Oracle B2C physical schema.
In the Schema Designer, in the Action bar, select Explore Data.

Additional considerations

Here are some examples of ROQL Managed Tables and related queries for the table data source properties:

Table Name	Discovery Query	Query
AnswerStatistics	`describe statsInformation.AnswerStatistics.statsInformationAnswerStatisticsList;`	`select AnswerStatistics.* from statsInformation;`
ArchivedIncidents	`describe archivedincidents;`	`select * from archivedincidents;`
ChatQueues	`describe chatQueues;`	`select * from chatQueues;`
PerformanceRecords (Incident)	`describe incidents.performancerecords.incidentPerformanceList;`	`select performancerecords.* from incidents;`
PerformanceRecords (Opportunity)	`describe opportunities.performancerecords.opportunityPerformanceList;`	`select performancerecords.* from opportunities;`
Transactions (Incidents)	`describe incidents.transactions.incidentTransactionList;`	`select transactions.* from incidents;`
Transactions (Opportunity)	`describe opportunities.transactions.opportunityTransactionList;`	`select transactions.* from opportunities;`
Transactions (Contacts)	`describe contacts.transactions.contactTransactionList;`	`select transactions.* from contacts;`
flows	`describe flows;`	`select * from flows;`
profiles	`describe profiles;`	`select * from profiles;`
surveyQuestions	`describe surveyQuestions;`	`select * from surveyQuestions;`
SurveyQuestionResponses	`describe surveySessions.Responses;`	`select Responses.* from surveySessions;`
surveys	`describe surveys;`	`select * from surveys;`
slas	`describe slas;`	`select * from slas;`
salesstages	`describe salesstages;`	`select * from salesstages;`
Profile2Queue	`describe Profiles.ChatQueues.ProfileToChatQueueList;`	`select IncidentQueues.* from Profiles;`
IncidentQueues	`describe incidentQueues;`	`select * from incidentQueues;`
FlowQuestions	`describe flowQuestions;`	`select * from flowQuestions;`
flows	`describe flows;`	`select * from flows;`
DistributionEmailLists	`describe distributionEmailLists;`	`select * from distributionEmailLists;`
DistributionEmailAddresses	`describe distributionEmailAddresses;`	`select * from distributionEmailAddresses;`
SurveyQuestionResponses	`describe surveySessions.responses.surveyQuestionResponseList;`	`select responses.* from surveySessions;`
DeletedRecordInformation	`describe deletedRecordInformation;`	`select * from deletedRecordInformation;`
organizations_addresses	`select addresses.* from organizations limit 1;`	`select addresses.* from organizations;`

Content