Clarity

Hello All,

We do DB refresh of our QA environment with Production every month. So, after every refresh do we have to regenerate the Jasper Keystore or do we have any workaround ?

Thanks

Bhavani Sankar

Hi Bhavani,

At this point generating Key store is the best possible solution, I will keep you updated once we find out any other workaround.

Regards

Suman Pramanik

Thanks Suman for the quick reply, Please do share when you find the workaround

Thanks

Bhavani Sankar

You would need to regenerate the keystore after any refresh because the key store is saved in PPM database under table CMN_JASPER_KEYSTORES, so once the restore is done the keystore between file and database is not matching which is the reason you would need to do it.

This is how its is designed.

Regards

Suman Pramanik

Thanks Suman,

Created an Idea for the same.

Jaspersoft Key store generation after every DB refresh

Hi Bhavani,

This can be overcome in CA PPM 14.3 onwards with a command below

admin jaspersoft syncPPMContext -userName superuser -password superuser

1. If the ppmjasperadmin does not exist in Jaspersoft or Clarity it will create in both the systems
2. If new keystore is generated in between then the profile attributes will be encrypted using new keystore.
3. If profile attributes related to database properties changed then those profile attributes values will be updated
4. If there are any additional profile needs to be added that will be added
5. Updates the domain schema names for all OOTB domains

Regards

Suman Pramanik