Clarity PPM

Expand all | Collapse all

Jaspersoft Key store generation after every DB refresh

  • 1.  Jaspersoft Key store generation after every DB refresh

    Posted 02-24-2016 12:57 AM

    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



  • 2.  Re: Jaspersoft Key store generation after every DB refresh

    Posted 02-24-2016 01:03 AM

    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



  • 3.  Re: Jaspersoft Key store generation after every DB refresh

    Posted 02-24-2016 02:02 AM

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

     

    Thanks

    Bhavani Sankar



  • 4.  Re: Jaspersoft Key store generation after every DB refresh

    Posted 02-24-2016 02:41 PM

    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



  • 5.  Re: Jaspersoft Key store generation after every DB refresh

    Posted 02-29-2016 07:51 AM

    Thanks Suman,

     

    Created an Idea for the same.

     

    Jaspersoft Key store generation after every DB refresh



  • 6.  Re: Jaspersoft Key store generation after every DB refresh

    Posted 05-16-2016 02:04 AM

    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