TCC – Upgrade to 17

This post is to consolidate the information about the required update of TCC to version 17.x

TCC: Does TCC Need To Be Upgraded When A Zone Is Upgraded? (Doc ID 2086226.1)
This article addresses the question of whether TCC needs to be upgraded when a zone is upgraded.

  • TCC is backward compatible with earlier zone versions and earlier TCC script versions.
    • TCC version that is higher than the zone version is OK
    • TCC version that is higher than the TCC script version is OK
  • Best practice is to use the latest version of TCC when it is released to take advantage of any known or unknown fixes.
  • Each version of TCC comes with a readme.txt that contains additional information about the release.  To get this please download TCC and then unzip/unpack it.
  • It is always recommended to use the latest available Product Integration Pack (PIP) when authoring new import/export TCC scripts or after a major zone upgrade.  The PIP/data model will have the latest data model features and changes.
  • Compatibility information can be found here.
  • OTAC may require TCC upgrade for connectivity reason.  For example, TCC 17 adds support for TLS 1.1 and 1.2 cryptographic protocols, used for HTTPS connections with OTAC 17 zones.  When OTAC 15B becomes end-of-life support for existing TLS 1.0 protocol will end.  At that point TCC 15B and earlier will not be able to connect to the OTAC zone.  For this reason, as announced elsewhere, clients who use TCC must upgrade to TCC 17 before 15B becomes end-of-life.
  • Testing is always recommended.  TCC supports having multiple TCC installed on the same machine, same or different versions.

This is the end of life statement for 15B

Oracle Talent Acquisition Cloud 15B End of Life
15B EOL is effective September 30, 2018. All customers must upgrade to release 17 prior to this date when 15B will be decommissioned.


Announcing Oracle Talent Acquisition Cloud Transition to Transport Layer Security 1.1 and 1.2 Protocols
Announcing Oracle Talent Acquisition Cloud Transition to Transport Layer Security 1.1 and 1.2 Protocols
Transition to TLS 1.1 and TLS 1.2. Decommission of TLS 1.0.
Oracle Talent Acquisition Cloud (OTAC/TEE) is transitioning to enable TLS 1.1 and TLS 1.2 protocols for enhanced communication encryption and subsequently decommission TLS 1.0. Transport Layer Security (TLS) is a cryptographic protocol that provides encryption and endpoint identity verification between Oracle servers and end users.
OTAC/TEE release 17.0 and above supports TLS 1.1 and TLS 1.2 protocols as well as the current TLS 1.0 protocol. The TLS 1.0 protocol will be decommissioned with 15B End of Life (EOL) which is set to Sept 30, 2018. The decommissioning of TLS 1.0 is a network operation not tied to an OTAC/TEE release.
Impact to OCM Integration Partners.
OCM integration partners are impacted by the transition. Partners are required to support TLS 1.1 and TLS 1.2 no later than Sept 30, 2018.

Impact to OTAC/Taleo Customers

  • It is imperative to upgrade to TEE release 17.x no later than Sept 30, 2018, to ensure service continuity.
  • Upgrade to TEE 17.x is required before TCC can be upgraded.
  • If you use Taleo Connect Client (TCC) for integrations, note the following important points:
    • Upgrade TCC to release 17.x to support TLS 1.1 and TLS 1.2.
    • Upgrade no later than Sept 30, 2018 to ensure service continuity and prevent failure of TCC jobs.
    • Download TCC from Oracle Software Delivery Cloud. Search for “Taleo Connect Client Application 17” and select the applicable version along with the Linux or Microsoft Windows Platform.
    • TCC 17.x is certified on TEE 17.x. The backward or forward compatibility of TCC with different annual releases is not certified (e.g. TCC 15.x with TEE 17.x is not supported).
    • Upgrading TCC has no impacts on your TCC scripts.
  • If you use Taleo Connect Broker (TCB), no action is required on your part regarding TCB.
  • If you use Taleo Social Sourcing (TSS), it will be upgraded to TSS 17.x by Sept 30, 2018 – no action required on your part.
  • TLS 1.1 and TLS 1.2 have no browser impacts.
Your Action:
Please log a Service Request via My Oracle Support to schedule your OTAC/TEE 17.x upgrade.  Refer to MOS knowledge article 1603034.1 for release availability.  Plan for your TCC upgrade following the OTAC/TEE upgrade if you are a TCC user.
When your OTAC/TEE instance is upgraded, work with your OCM integration partner(s) to ensure that they enable their TEE integration end points to add communication over TLSv1.1 and TLSv1.2 protocols. This must be completed before Sept 30, 2018 to ensure service continuity. A communication was sent to all the partners to notify them of the TLS transition.


Comments are closed.