- Contents
Oracle Service Cloud Integration Installation and Configuration Guide
Installation overview and requirements
Review the following information before you install the Oracle Service Cloud Integration.
Installation files
Both CIC and Oracle Service Cloud publish releases multiple times a year. The CIC release version and Oracle Service Cloud Integration release version must match. For example, if you use CIC 2018 R1, you must use the Oracle Service Cloud Integration on the Integrations 2018 R1 .iso file.
Starting with CIC 2015 R2, the installs and related files for IC Integration with Oracle Service Cloud (formerly Oracle RightNow) are:
-
Released separately from CIC 2015 R2 or later, but on the same release schedule.
-
The installs and related files for the integration are included in the Integrations_YYYY_R#.iso file for the particular release (for example, Integrations_2015_R2.iso).
- Check the Downloads page for the latest Integrations (Oracle Service Cloud) release.
Important:
-
IC Integration with Oracle Service Cloud 2015 R1 or later can be applied to any IC Integration with Oracle Service Cloud 4.0 SU.
-
IC Integration with Oracle Service Cloud 2015 R1 or later supports Oracle Service Cloud's SOAP API instead of the Connect Data API.
Note: Beginning April 1, 2015, basic functionality testing for integrations will be performed only against the most current version of third party products under manufacturer support and the latest version of CIC software.
- See the CRM Software Integrations page in the Testlab site to identify which versions of CIC were tested with different versions of Oracle Service Cloud.
Release Documents and Feature Information
PureConnect/CIC Integration with Oracle Service Cloud is available in CIC 4.0 SU 3 to SU 6 and CIC 2015 R1 and later. Starting with the 2015 R2 release, IC Integration with Oracle Service Cloud is released separately from CIC, but on the same release schedule.
-
For specific feature questions, see Appendix A: Oracle Service Cloud Integration FAQs.
-
PureConnect Integration to Oracle Service Cloud Data Dictionary
-
Interaction ScriptAssist for Oracle Service Cloud Technical Reference
Validation
We test the Oracle Service Cloud integration against the current Oracle Service Cloud release. For example, we validated the Oracle Service Cloud integration for CIC 2015 R3 against the Feb 2015 version of Oracle Service Cloud.
For more information about testing and validation, see Appendix A: Oracle Service Cloud Integration FAQs.
Note:
Oracle Service Cloud/RightNow has two different console modes. The Enhanced
Console has been the default for several years now, as Oracle phases out
the use of the Legacy Console, which customers can still choose to use
instead. Although the Legacy Console is not fully deprecated by Oracle,
Genesys recommends that you use only the Enhanced Console, as Genesys
does not support the Legacy Console. Use of the Legacy Console is at the
customer's own risk. If issues arise for a customer who is attempting
to use the Legacy Console, they will need to retest with the Enhanced
Console to see if the issue persists.
Integration Service
The Integration Service is only needed if you are routing incidents or chats. When choosing where to install the Integration Service, consider these points:
-
It cannot be installed on the CIC server.
-
It could be installed on a database server or other non-IC server.
-
It does not require excessive CPU or memory resources.
Verify that the required software is installed:
-
.NET Framework 4.5.2 or later
-
Windows Server 2012 R2, 2016 or 2019
-
External Web Access (port 80)
-
Socket communication accessibility to/from the CIC server (TCP/IP, port assigned in the install)
Handlers
The integration relies on handlers present on the server.
PureConnect Media Bar and EmailConfig.Views Add-Ins
When installing the PureConnect Media Bar and EmailConfig.Views Add-Ins, consider these points:
-
They require installation of the Oracle Service Cloud client.
-
They require an Oracle Service Cloud administrative user.
-
They require the .NET Framework 4.5.2 or later.
-
They require installation of Interaction Desktop on the client machine.
Note:
Agents should use the PureConnect Media Bar for call controls, not the
embedded Interaction Desktop client. The PureConnect Media Bar, not the
embedded Interaction Desktop client, drives interactions.
Interaction ScriptAssist utility
Interaction ScriptAssist utility is optional.
When choosing where to install the ScriptAssist utility, consider these points:
-
It cannot be installed on the CIC server.
-
It should be installed on a CIC administrator's client machine.
-
It can be installed on an operating system that Genesys has validated and supports.
-
It requires .NET Framework 4.5.2 or later.
-
It requires socket communication accessibility to/from CIC server (uses IceLib- TCP/IP Port 3952).