Clarity

  • 1.  CA PPM 14.3 and Jaspersoft 6.1 Load balancing

    Posted Nov 10, 2016 04:21 PM

    Hi,

     

    We have CA PPM 14.3 and Jaspersoft 6.1.  We couple of Linux servers clustered for Jaspersoft.  They are load balanced by F5.  It uses cookie persistence. The Jaspersoft load balnacer URL is configured in CSA under reporting session. But when we click the Advanced reporting, it throws a message "User is not registered on the reporting server."

     

    We are sure all the individual servers in the cluster have correct keystore file copied.  We ran Create and Users job and Load Datawarehouse job successfully.

     

    Then we tested each individual server by changing CSA page. They all worked.   We changed it to load balancer URL again in CSA page, we restarted application and BG and again it shows the error "User is not registered on the reporting server." when we try to click the Advanced Reporting.

     

    The load balancer works when we try to access the jaspersoft portal directly using "http://<load balancer URL>/<webapp>/login.html and I am able to login as superuser and browse the repository content.

     

    Issue is only when we try to access from PPM application.

     

    I am not familiar with all the load balancing concepts and terminology and also not familiar how CA PPM to Jaspersoft authentication is done and sessions are handled.  Is this issue related to load balancer persistence?  Do we need to change to some other persistence like source IP persistence?  or any other issue

     

    Please let me know if you have experienced same issue or share your thoughts

     

    Thank you

    Regards

    Ravi Chandramouli



  • 2.  Re: CA PPM 14.3 and Jaspersoft 6.1 Load balancing

    Posted Nov 30, 2016 05:30 AM

    Hi Ravi,

     

    Do you have any updates about this issue?

    If the problems sill persists, you could use nmap and wireshark in PPM and Jasper servers to see how the traffic differs when using F5 and when calling directly. I'm not yet sure how the PPM to Jaspersoft authentication is handled. F5 might drop or change http-headers and/or cookies which could mess things up.

    We are going to build same kind of F5 load balancing environment for clustered Jasper (Linux), but with CA PPM 15.1.

     

    Regards

    Sami