Integrating CA Identity Manager and JasperReports

book

Article ID: 210078

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

What are the requirements to integrate CA Identity Manager (IM) running on IBM WebSphere Application Server (WAS) and JasperReports Server?

Environment

Release : 14.2 CP5 or 14.3 CP2

Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)

Resolution

The basic requirements for IBM Websphere Application Server (WAS) are defined in the platform support matrix (link below):

 

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-3/platform-support-matrix/server-environments.html#concept.dita_94374130b9803dd0ebc3c24dddda05882c2f2170_Supported64bitApplicationServers

 

and the installation instructions to deploy CABI (CA Business Intelligence) through JasperReports Server can be found below:

 

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-3/installing/install-and-configure-ca-business-intelligence-jasperreports-server.html

 

Additional Requirements.

JasperReports Server 7.1.1 is supported on 14.2 and 14.3 with the following patches

 

Minimum requirements for 14.3 are CP1 

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-3/platform-support-matrix/reporting-server.html

 

Minimum requirements for 14.2 are CP5 + hotfix (available for the standalone and vApp versions via the link below)

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-2/platform-support-matrix/reporting-server.html

 

Below are additional considerations specific to a WAS installation where IM and JasperReports Server are installed on separate machines.

 

IBM and Oracle versions of Java use a different keystore so it is important to install the IBM Java JDK on the JasperReports Server to ensure that the jks (key files) can be decrypted.

 

1. The .jks files need to be generated with IBM JDK (C:\IBM\WebSphere\AppServer\java_1.8_64) shipped along with WAS and then copied over to the report server.


2. Make sure you have the following java versions in your WAS and Report Server.


WAS JDK: (1.8.0)
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr4fp5-20170421_01(SR4 FP5))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20170419_344392 (JIT enabled, AOT enabled)
J9VM - R28_20170419_1004_B344392
JIT  - tr.r14.java_20170419_344392
GC   - R28_20170419_1004_B344392_CMPRSS
J9CL - 20170419_344392)
JCL - 20170420_01 based on Oracle jdk8u131-b11
Jasper JDK:
java version "1.8.0_74"
Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)

 

3. Jasper 7.1.1 can be run as a service and it ships with its own java (C:\Program Files\CA\SC\CA Business Intelligence\java), which is Oracle JAVA 1.8.191 version, which the report server uses as its default.  Make sure that you point %JAVA_HOME% variable to the IBM Java 1.8.0_74 version on Jasper Report Server.
 

Set the JAVA_HOME variable in

 

(a) the Windows environment settings and 

(b) the setenv.bat/sh file under tomcat/bin directory and restart the Jasper Server from the command prompt, but not as a service.