Clarity

Dear all,

the Installation Guide for CA PPM 14.2 tells me to install the Jaspersoft Advanced Reporting content.

The admin command supports the parameter content-jaspersoft, but this needs a contentPackId, which I have no clue where to get from.

Thank you in advance for your help!

Hi Georg,

• Installation of PMO Accelerator 14.2 is required for the Content

Did you install and PMO yet.

Regards
Suman Pramanik

Refer "Import the Jaspersoft advanced Reporting Content" topic in PMO Accelerator Release Notes of CA PPM v14.2.. This topic provides the step by step procedure to import the content.

Dear Namita,

could you please post a link to the release notes?

Do I have to install the demo-content as well?

Hi GeorgSchmid2014 ,

Here is the document link

https://support.ca.com/cadocs/0/CA%20Clarity%20PPM%2014%202%2000%20%20On%20Premise%20-ENU/Bookshelf.html

Here is the command

admin content-jaspersoft csk -userName superuser -password <password> -fileName jaspersoft_csk.zip

Regards

Suman Pramanik

Hi Suman,

after installing the PMO Accelerator, I get following exception in the Jaspersoft Tomcat when starting up.

Before, I could successfully login at Jaspersoft:

2015-03-23 14:50:21,777 ERROR ContextLoader,localhost-startStop-1:318 - Context initialization failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'themeSource' defined in ServletContext resource [/WEB-INF/applicationContext-themes.xml]: Cannot resolve reference to bean 'themeCache' while setting bean property 'themeCache'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'themeCache' defined in ServletContext resource [/WEB-INF/applicationContext-themes.xml]: Cannot resolve reference to bean 'unsecureRepositoryService' while setting bean property 'repositoryService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateRepositoryService' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'auditContext' while setting bean property 'auditContext'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'auditContext' defined in ServletContext resource [/WEB-INF/applicationContext-audit.xml]: Cannot resolve reference to bean 'mtLoggingContextProvider' while setting bean property 'loggingContextProvider'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtLoggingContextProvider': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.jaspersoft.ji.license.LicenseManager com.jaspersoft.ji.logging.context.BasicProLoggingContextProvider.licenseManager; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'applicationContextLicenseConfiguration': Injection of resource dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'multiTenancyRepositoryService' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy.xml]: Cannot resolve reference to bean 'hibernateRepositoryServiceProxy' while setting bean property 'repository'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateRepositoryServiceProxy': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateRepoServiceSecurity' defined in ServletContext resource [/WEB-INF/applicationContext-security.xml]: Cannot resolve reference to bean 'authenticationManager' while setting bean property 'authenticationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticationManager' defined in ServletContext resource [/WEB-INF/applicationContext-security.xml]: Cannot resolve reference to bean 'mtDaoAuthenticationProvider' while setting bean property 'providers' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtDaoAuthenticationProvider' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy.xml]: Cannot resolve reference to bean 'internalUserAuthorityService' while setting bean property 'userDetailsService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtUserAuthorityServiceTarget' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy-security.xml]: Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'dataSource' while setting bean property 'dataSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/applicationContext-webapp.xml]: Invocation of init method failed; nested exception is javax.naming.NamingException: KeystoreManager.init was never called or there are errors instantiating an instance.

Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'proReportSchedulerService' defined in ServletContext resource [/WEB-INF/applicationContext-pro-web-services.xml]: Cannot resolve reference to bean 'proReportSchedulerServiceImpl' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'proReportSchedulerServiceImpl' defined in ServletContext resource [/WEB-INF/applicationContext-pro-web-services.xml]: Cannot resolve reference to bean 'jobsService' while setting bean property 'jobsService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jobsService': Injection of resource dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportOptionsSchedulingService' defined in ServletContext resource [/WEB-INF/applicationContext-report-options.xml]: Cannot resolve reference to bean 'mtJobPersistenceService' while setting bean property 'persistenceService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtJobPersistenceService' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy.xml]: Cannot resolve reference to bean 'reportOptionsJobsPersistenceService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportOptionsJobsPersistenceService': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportOptionsJobSecurity' defined in ServletContext resource [/WEB-INF/applicationContext-report-options.xml]: Cannot resolve reference to bean 'authenticationManager' while setting bean property 'authenticationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticationManager' defined in ServletContext resource [/WEB-INF/applicationContext-security.xml]: Cannot resolve reference to bean 'mtDaoAuthenticationProvider' while setting bean property 'providers' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtDaoAuthenticationProvider' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy.xml]: Cannot resolve reference to bean 'internalUserAuthorityService' while setting bean property 'userDetailsService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtUserAuthorityServiceTarget' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy-security.xml]: Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'dataSource' while setting bean property 'dataSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/applicationContext-webapp.xml]: Invocation of init method failed; nested exception is javax.naming.NamingException: KeystoreManager.init was never called or there are errors instantiating an instance.

Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulerService' defined in ServletContext resource [/WEB-INF/applicationContext-web-services.xml]: Cannot resolve reference to bean 'reportSchedulerServiceImpl' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulerServiceImpl' defined in ServletContext resource [/WEB-INF/applicationContext-web-services.xml]: Cannot resolve reference to bean 'jobsService' while setting bean property 'jobsService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jobsService': Injection of resource dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportOptionsSchedulingService' defined in ServletContext resource [/WEB-INF/applicationContext-report-options.xml]: Cannot resolve reference to bean 'mtJobPersistenceService' while setting bean property 'persistenceService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtJobPersistenceService' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy.xml]: Cannot resolve reference to bean 'reportOptionsJobsPersistenceService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportOptionsJobsPersistenceService': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportOptionsJobSecurity' defined in ServletContext resource [/WEB-INF/applicationContext-report-options.xml]: Cannot resolve reference to bean 'authenticationManager' while setting bean property 'authenticationManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticationManager' defined in ServletContext resource [/WEB-INF/applicationContext-security.xml]: Cannot resolve reference to bean 'mtDaoAuthenticationProvider' while setting bean property 'providers' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtDaoAuthenticationProvider' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy.xml]: Cannot resolve reference to bean 'internalUserAuthorityService' while setting bean property 'userDetailsService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mtUserAuthorityServiceTarget' defined in ServletContext resource [/WEB-INF/applicationContext-multiTenancy-security.xml]: Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'dataSource' while setting bean property 'dataSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/applicationContext-webapp.xml]: Invocation of init method failed; nested exception is javax.naming.NamingException: KeystoreManager.init was never called or there are errors instantiating an instance.

Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/applicationContext-webapp.xml]: Invocation of init method failed; nested exception is javax.naming.NamingException: KeystoreManager.init was never called or there are errors instantiating an instance.

Hi GeorgSchmid2014 ,

With the error "failed; nested exception is javax.naming.NamingException: KeystoreManager.init was never called or there are errors instantiating an instance."

I would check if the keystore file is correctly set up

Generate the Key Store File

To authenticate CA Clarity PPM and Jaspersoft, generate a trusted key store for each organization.

Follow these steps:

1. Go to <clarity_home>/bin.

2. Run the following command to generate a key store from CSA:

admin jasper keystore

To generate key and password, enter:

admin jasper keystore [-key <key> -password <password>]

These commands generate the following files in <install>/config/ and <install>/META-INF/reporting/store.

■ <orgname>.jks (key store file)

■ <orgname>. properties (information about the key)

The available file is used depending on the J2EE server such as IBM WebSphere or Tomcat.

Chapter 10: How to Set Up CA Clarity PPM Reports 139

3. Copy these files to <Tomcat>/webapps/<jasperwebcontext>/WEB-INF/config where Jaspersoft is installed. For example, <Tomcat>/webapps/reportservice/WEB-INF/config.

Note: For clustered environments, copy these files in the same location on each of the nodes in the cluster.

4. Start the Tomcat service where the Jaspersoft reporting server is deployed.

Note: The Jaspersoft content cannot be imported without starting the reporting service.

5. (Optional) Repeat the steps to regenerate key or change the organization.

Regards

Suman Pramanik

Agreed with Suman's reply I would check the keystore generation step.

You can download the guide mentioned in my previous comment from below link. Check under "Installation Information" topic.

PMO Accelerator Release Notes - On Premise Release 14.2.00

I already performed the steps to generate the keystore. The files are where they should be and the content looks good.

Is there anything else I could check or take into account? E.g., I names the key after the organization name.

Is <Tomcat>/webapps/reportservice/WEB-INF/config really the only place where the keystore files have to be located?

Something else:

Do I have to perform the steps from chapter "If Jaspersoft is HTTPS Enabled"? It is not refered in the installation steps.

By calling keytool -keystore, I checked that the keystore is not a Java keystore. Is this correct? If yes, I guess it's OpenSSL?

Thank you so much for your support

Hi GeorgSchmid2014

The organization name specifies its as a valid tenant which helps to identify. are you installing jasper as single tenant/ cluster? Once you generate the key store files you need to place only at the path mentioned in the guide.

The HTTPS settings are only for those who wants to implement HTTPS for jaspersoft?

Regards

Suman Pramanik

Hi Suman,

Thanks for your quick replies!

I am installing Jaspersoft as single tenant.

Do I have to install openssl? The keystore seems to be an invalid Java keystore:

When running keytool -keystore <my-keystore>.jks -list, I get following exception:

java.io.IOException: Invalid keystore format

I guess the file is located correctly, but it is invalid.

Hi GeorgSchmid2014,

No you don't need open SSL as its java key Store, try generating using the below

To generate key and password, enter:

admin jasper keystore [-key <key> -password <password>]

Make sure the format is correct and the syntax is correct when generating the key store and make sure you have the correct java installed provided with Jaspersoft

Regards

Suman Pramanik

In addition to checking the above points, also make sure that keystore path point to a valid keystore file.

"Invalid keystore format" error could be seen when Keystore path points to a file that is not a keystore..

In fact keystore should be generated after settng the Organization in the CSA.

So,

first fill the organization name in the CSA -> Reporting section.

Then

Generate the keystore

Check file is valid means it is not empty.

In addition to what Namita asked can you redo the following steps

1. Fill in the organization in CSA and save

2. Generate the key store using admin jasper keystore [-key <key> -password <password>]

3. check the Keystore file by opening in notepad to see its not empty.

Regards

Suman Pramanik

The organization name in the Jaspersoft reporting section in CSA is set to <mycompany>.

The <mycompany>.jks is not empty but contains binary data

This is the content of <mycompany>.properties:

#Jaspersoft Keystore Properties.

#Mon Mar 23 18:26:40 GMT+01:00 2015

ks.storepass=<mypassword>

ks.storealias=<mycompany>

ks.storename=<mycompany>.jks

Is this really a java keystore as the extension .jsk indicates?

Hi GerofSchmid,

JKS is the default keystore type in the Sun/Oracle Java security provider

Now delete the old key store and replace with the newly generated and try starting the tomcat. Hoping you had set the Java home path in environment variable .

Regards
Suman Pramanik

Hi Suman,

after uninstalling Tomcat and Jaspersoft and repeating the installation, the setup of the keystore worked

I assume the problem was that I had not installed the PMO Accelerator before installing Jaspersoft.

Is this assumption correct?

Thanks again for your support!

Hi GeorgSchmid2014,

I am glad to hear, PMO installation has nothing to do with the key store, I am assuming its was the problem with tomcat/jasper soft installation. Happy new reporting and 14.2

Regards

Suman Pramanik

In fact, the problem was related to the keystore:

The webapp only started up when I ran tomcat as command line process but not if I started the installed service.

The reason:

The service had no access to the user directory where the *.jrsks and *.jrsksp files are located.

The solution:

Configure the service so that its runs under the user account also used for the installation of Jaspersoft. Additionally, the Java heap space has to be extended.

Hi Suman,

I got Jaspersoft installed and configured properly.

I can create a windows service for the Tomcat application and run it as the same user which installed Jaspersoft.

If I try to change the user to another user (local system account or a domain service account), I struggle to get Jaspersoft running.

I get this error: java.lang.RuntimeException: KeystoreManager.init was never called or there are errors instantiating an instance.

You say: "you need to use the same account to start or stop the services which you used for installation."

Is there no way of changing the service account after the installation?

Thanks for your help.

Kind regards,

Knut Hole

Hi Georg,

I am getting the same error message (keystore) as you mentioned above . My webapp only starts when i run tomcat as command line.

I tried your solution to run the service under user account but getting  OutofMemory Error : PermGen Space.

I tried to add CATALINA_OPTS="-Xms512M -Xmx1024M" in catalina.sh. But its not working me.

How you extended the Java Heap Space?

-Gurjeet

Hi Gurjeet,

The JVM parameters you added are not going to affect the PermGen memory size, only Java heap memory.

Please try adding the following JVM parameters as well to increase the PermGen memory:
-XX:PermSize=128m
-XX:MaxPermSize=256m

Please let me know how it goes.

Kind Regards

Nika Hadzhikidi
CA Technologies
Principal Support Engineer

Hi,

Thanks for the input, Jaspersoft works after extending the  maximum memory pool to 2048 in Tomcat properties.

Thanks

Hi Knut,

Here is the solution:

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

By default, the Jaspersoft service will only run using the logon account which installed Jaspersoft.

Assume 'user1' is the installation user and 'user2' is the service account.

In order to let the Jaspersoft service run under a different account, copy files from user1's personal folder to user2's.

Note that user2's profile may not exist on the server until the service has been started (unsuccessfully) using that account.

The objects to copy are:

Folders:

.jasperserver

Files:

Jasperserver.license

.jslic

.jrsks

.jrsksp

The service user needs to have local admin privileges on the server.

Change the service logon credentials and restart the service.

Hope this helps

Regards

Suman Pramanik

Suman,

Thanks for the quick reply.

I had allready tried moving all the files to the service account users folder, but forgot to give the service account local priveleges.

This was indeed the solution!

Thanks again.

Knut

Great to hear

Regards

Suman

Hi,

I'm facing the same kind of issue.

User1 is the installation user.

User2 is the Tomcat service identity user.

I copied files :

Jasperserver.license

.jslic

.jrsks

.jrsksp

from my installing user's profile to User2 profile. I do not have any .jasperserver folder.

Then added User2 to the local Administrators group.

This worked.

BUT this is not correct.

This worked because giving User2 administrative rights allowed him to access the User1 profile.

I removed the files from User1 profile, then the report server is not working anymore.

While ProcMonitoring the service, I can see it trying to access to User1 profile.

I perhaps missed something ?

If not, this can't be correct because if User1 profile disappears, the service won't work anymore.

Regards,

Julien