README
     Progress(R) DataDirect(R)
     Progress(R) DataDirect(R) for JDBC(TM) for Oracle Sales Cloud(TM) Driver
     Release 6.0.0
     January 2019


***********************************************************************
Copyright (c) 1994-2019 Progress Software Corporation and/or its 
subsidiaries or affiliates. All Rights Reserved.

***********************************************************************


CONTENTS

Requirements
Installation directory
Changes since 6.0
Release 6.0 Features
Notes, known problems, and restrictions
Documentation
Installed files


     Requirements

Java SE 7 or higher must be installed and the JVM must be defined on your system
path.


     Installation directory

The default installation directory for the driver is:

* Windows:
  C:\Program Files\Progress\DataDirect\JDBC_60

* UNIX/Linux:
  /opt/Progress/DataDirect/JDBC_60
  Note: For UNIX/Linux, if you do not have access to "/opt", your user's
  directory should be used in place of this directory.


     Changes since 6.0

Certifications
--------------
* The driver has been certified with Oracle JDK 11
  Driver version 6.0.0.000074 (C0112.F000147.U000072)  

* The driver has been certified with OpenJDK 11
  Driver version 6.0.0.000074 (C0112.F000147.U000072) 

* The driver has been certified with OpenJDK 8 on Windows and Linux
  Driver version 6.0.0.000074 (C0112.F000147.U000072) 


     Release 6.0 Features

The driver supports SQL read access to Oracle Sales Cloud. To support SQL access
to Oracle Sales Cloud, the driver creates a relational map of the Oracle Sales
Cloud data model and translates SQL statements provided by the application to
Oracle Sales Cloud queries and web service calls.

* The driver supports all JDBC Core functions.

* The driver supports the core SQL-92 grammar.

* The driver supports connecting through a proxy server.

* The driver supports timeout functionality.

* The driver supports the following data types:
  - BOOLEAN        maps to BOOLEAN
  - DECIMAL        maps to DECIMAL
  - INTEGER        maps to INTEGER
  - LONG           maps to BIGINT
  - LONGSTRING     maps to LONGVARCHAR
  - STRING         maps to VARCHAR


     Notes, known problems, and restrictions

The following are notes, known problems, and restrictions with the Oracle
Sales Cloud driver.

Filter conditions
-----------------
Currently, passing filter conditions only works for simple, single column
conditions. If there are multiple filters with 'AND' and 'OR', only partial or
no filters are passed to Oracle Sales Cloud.

String and Date field metadata
------------------------------
Oracle Sales Cloud reports the data type of String and Date fields as String.
The driver treats these fields as String values. However, when filter conditions
are passed to Oracle Sales Cloud, Oracle Sales Cloud distinguishes between the
actual data types and apply Date specific comparisons to Date fields. Therefore,
query results can differ depending on whether filters have been passed down to
Oracle Sales Cloud or processed by the SQL engine embedded in the driver.

Comparison operators
--------------------
There appears to be a limitation with the Oracle Sales Cloud REST API concerning
the >=, <=, and != comparison operators when querying String fields. Therefore,
the driver has not been optimized to pass these comparison operators to Oracle
Sales Cloud. We are working with Oracle on this issue.

Filter operations on Boolean fields
-----------------------------------
There appears to be a limitation with the Oracle Sales Cloud REST API concerning
queries with filter operations on Boolean fields. Therefore, the driver has not
been optimized to pass filter operations on Boolean fields to Oracle Sales
Cloud. We are working with Oracle on this issue.

Attachment type
---------------
The driver currently reports Attachment type fields in the metadata but does not
support retrieving data for these fields. These fields are set to NULL.

Parent-child join queries
-------------------------
Join queries between parent and child tables are not supported.

Parent table with composite primary key
---------------------------------------
Queries on child tables whose parent has a composite primary key are not
supported. For example, the children of ACTIVITIES_ACTIVITYCONTACT and
LEADS_PRODUCTS are not accessible.

Relationship object queries
---------------------------
Queries on the children of relationship objects are not supported. For example,
the children of ACCOUNTS_RELATIONSHIP, CONTACTS_RELATIONSHIP, and
HOUSEHOLDS_RELATIONSHIP are not accessible.

Grandchildren tables with OR clause filter
------------------------------------------
Queries on grandchildren with multiple sets of Parent IDs and Grand Parent IDs
used in an OR clause are not supported. For example, the following query is
not supported.
   select * from ACCOUNTS_ADDRESS_ADDRESSPURPOSE
      where (ACCOUNTS_PARTYNUMBER = 'OSC_12343' AND
             ACCOUNTS_ADDRESS_ADDRESSNUMBER = 'AUNA-2XZKGH')
         or (ACCOUNTS_PARTYNUMBER = 'OSC_12344' AND
             ACCOUNTS_ADDRESS_ADDRESSNUMBER = 'AUNA-2YZKGH')

Document object queries
-----------------------			 
When querying documented objects like "CATALOGPRODUCTITEMS" and
"CATEGORYPRODUCTITEMS", no more than 500 records are returned, even when
more records may be present. This behavior is also seen with some custom
objects. We are currently working with Oracle support to resolve this issue.

OPPORTUNITIES_CHILDREVENUE_PRODUCTS or LEADS_PRODUCTGROUPS queries
------------------------------------------------------------------
A query on OPPORTUNITIES_CHILDREVENUE_PRODUCTS or LEADS_PRODUCTGROUPS with
a filter on the primary key column returns 0 records even when more records
are present. We are currently working with Oracle support to resolve this issue.

Subqueries with more than 100 records
-------------------------------------
Queries that contain subqueries returning more than 100 records are not
supported. For example, the following query is not supported.
   select * from ACCOUNTS_ADDRESS
   where ACCOUNTS_PARTYNUMBER
   in (select top 101 PARTYNUMBER from ACCOUNTS)

Creating custom objects
-----------------------
When you create custom objects, your Oracle Sales Cloud administrator must
enable these objects for REST API access through Application Composer.
Otherwise, you will not be able to query against these custom objects.

Executing DataDirect shell script
---------------------------------
For UNIX/Linux users: If you receive an error message when executing any
DataDirect for JDBC shell script, make sure that the file has EXECUTE
permission. To do this, use the chmod command. For example, to grant EXECUTE
permission to the testforjdbc.sh file, change to the directory containing
testforjdbc.sh and enter: chmod +x testforjdbc.sh


     Documentation	 	 

PROGRESS DATADIRECT FOR JDBC FOR ORACLE SALES CLOUD DRIVER USER'S GUIDE
------------------------------------------------------------------
The USER'S GUIDE is available as an HTML help system and as a PDF.

* The HTML help system and PDF are installed in the OracleSalesCloudHelp
  subdirectory of your product installation directory.

* The HTML help system and the PDF are also available on this Progress
  DataDirect documentation web page:
  https://www.progress.com/documentation/datadirect-connectors


     Installed Files

When you extract the contents of the installation download package to your
installer directory, you will notice the following files that are required to
install the driver:

*  Windows:
   - PROGRESS_DATADIRECT_JDBC_INSTALL.exe
   - PROGRESS_DATADIRECT_JDBC_ORACLESALESCLOUD_6.0.0_INSTALL.iam.zip
   - PROGRESS_DATADIRECT_JDBC_COMMON_6.0.0_INSTALL.iam.zip
   - PROGRESS_DATADIRECT_JDBC_DOCUMENTATION_6.0.0_INSTALL.iam.zip

*  Non-Windows:
   - PROGRESS_DATADIRECT_JDBC_INSTALL.jar
   - PROGRESS_DATADIRECT_JDBC_ORACLESALESCLOUD_6.0.0_INSTALL.iam.zip
   - PROGRESS_DATADIRECT_JDBC_COMMON_6.0.0_INSTALL.iam.zip
   - PROGRESS_DATADIRECT_JDBC_DOCUMENTATION_6.0.0_INSTALL.iam.zip

When you install the driver, the installer creates the following directories and
files in the product installation directory in the default installation
directory or in an installation directory you specify, represented by
INSTALL_DIR.

INSTALL_DIR/:
-------------
LicenseTool.jar            Product license file manager

ddprocinfo.exe             Windows executable to start the Processor Information
                           Utility

ddprocinfo                 UNIX/Linux script to start the Processor Information
                           Utility


INSTALL_DIR/Examples/Connector/:
--------------------------------
ConnectorSample.ear        J2EE Application Enterprise Archive file containing
                           the ConnectorSample application 

connectorsample.htm        USING DATADIRECT CONNECT FOR JDBC RESOURCE ADAPTERS
                           document

graphics/*.*               Images referenced by the USING DATADIRECT CONNECT FOR
                           JDBC RESOURCE ADAPTERS document

src/ConnectorSample.jsp    Source for the JavaServer Page used to access the
                           ConnectorSample application

src/connectorsample/ConnectorSample.java     
                           Java source file defining the remote interface for
                           the ConnectorSample EJB

src/connectorsample/ConnectorSampleBean.java  
                           Java source file defining the home interface for the
                           ConnectorSample EJB

src/connectorsample/ConnectorSampleHome.java  
                           Java source file containing the implementation for
                           the ConnectorSample EJB


INSTALL_DIR/Examples/JNDI/:
---------------------------
JNDI_FILESYSTEM_Example.java
                           Example Java(TM) source file

JNDI_LDAP_Example.java     Example Java source file


INSTALL_DIR/Examples/OracleSalesCloudSamples/:
----------------------------------------------
buildsamples.bat           Batch file to build the Oracle Sales Cloud example

buildsamples.sh            Shell script to build the Oracle Sales Cloud example

runoraclesalescloudconnectsample.bat
                           Batch file to run the Oracle Sales Cloud example

runoraclesalescloudconnectsample.sh
                           Shell script to run the Oracle Sales Cloud example

bin/com/ddtek/jdbc/samples/OracleSalesCloudConnectSample.class
                           Java example class

bin/com/ddtek/jdbc/samples/SampleException.class
                           Java example class

src/com/ddtek/jdbc/samples/OracleSalesCloudConnectSample.java
                           Java source example


INSTALL_DIR/help/: 
------------------
OracleSalesCloudHelp/index.html
                           HTML help system entry file

OracleSalesCloudHelp/salescloudjdbcug.pdf
                           User's guide PDF file

OracleSalesCloudHelp/*     Support files and folders for the driver help system


INSTALL_DIR/install/: 
---------------------
.psc_dd_inst_reg.xml       Support file for the installation logs

logs/*.*                   Log file generated upon installing or uninstalling


INSTALL_DIR/jre/:
-----------------
*.*                        Windows only. Files associated with the driver.


INSTALL_DIR/lib/:
-----------------
oraclesalescloud.jar       Oracle Sales Cloud Driver and DataSource classes


INSTALL_DIR/NOTICES/:
---------------------
JDBC for Oracle Sales Cloud v6.0 notices.txt
                           Third party agreement information


INSTALL_DIR/pool manager/:
--------------------------
pool.jar                   All DataDirect Connection Pool Manager classes


INSTALL_DIR/READMES/:
---------------------
JDBC for Oracle Sales Cloud v6.0 readme.txt
                           This file


INSTALL_DIR/testforjdbc/:
-------------------------
Config.txt                 Configuration file for DataDirect Test

ddlogging.properties       Logging properties file

testforjdbc.bat            Batch file to start DataDirect Test

testforjdbc.sh             Shell script to start DataDirect Test

lib/testforjdbc.jar        DataDirect Test classes


INSTALL_DIR/uninstall/:
-----------------------
.com.zerog.registry.xml    Support file for the uninstaller

.psc_dd_uninst_reg.xml     Support file for the uninstaller

InstallScript.iap_xml      Support file for the uninstaller

installvariables.properties
                           Support file for the Windows uninstaller

Uninstall_JDBC_60.exe      Windows uninstaller

Uninstall_JDBC_60.lax      Support file for the Windows uninstaller

uninstaller.jar            Java uninstaller

oraclesalescloud/*.*       Support files for the uninstaller

resource/*.*               Resource files for the Windows uninstaller


January 2019
=============
End of README