search cancel

When syncing Clarity's Oracle JDBC URL (with native encryption) onto JSFT datasource Url, the protocol info is getting wrongly appended.

book

Article ID: 255516

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

Post enabling encryption at database connection the protocol in the Jaspersoft changes to TCP 

Steps to Reproduce: 

  1. Set up a clarity 16.1. or higher with database native encryption
  2. In the CSA Database Connection URL set to below parameters
    • jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=*****)(PORT=****))(CONNECT_DATA=(SERVICE_NAME=***)(SERVER=dedicated))(SECURITY=(ENCRYPTION_CLIENT=requested)(ENCRYPTION_TYPES_CLIENT=AES256)))
  3. Stop and start all the clarity services
  4. Navigate to clarity_home\bin folder and run admin jaspersoft syncPPMContext -userName *** -password ***

Expected Results: The admin command of jaspersoft should be successful and protocol should be TCPS

Actual Results: The admin command is successful however protocol is TCP

$ admin jaspersoft syncPPMContext -userName *** -password ***
Syncing PPM context to jaspersoft..
Updating user profile attributes..
Data Warehouse Bean DS URL : jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=***)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=***)))
PPM Bean DS URL : jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=***)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=***)))
Updating domain schema name..
Processing domain...Application Management

Environment

Release : 16.1.0

Cause

DE67481

Resolution

The DE67481 is fixed in upcoming release i.e. 16.1.1 (targeted to release in March 2023)