Tech Tip: OpenAPI with SSL configured in CA Performance Center SSO

Document created by polmi05 Employee on Jul 9, 2015Last modified by SamCreek on Dec 17, 2016
Version 4Show Document
  • View in full screen mode

With the new r2.5 CA Performance Center (CAPC) release there is now the fully supported OpenAPI tool.


These are powerful tools and are great additions to the product.


If you are running an upgraded CAPC system that was running SSL, you may find that OpenAPI shows an error when it attempts to communicate with the CAPC host from the Data Aggregator (DA), where OpenAPI is launched from.


The common error observed is an HTTP 500 error.


The common cause for this is that the Data Aggregator is not aware of the appropriate ports to contact the CAPC host with.


There is a new step in the SSL configuration for CAPC and the DA introduced in the 2.5 release. If that step is missed it will cause these HTTP 500 errors. It is easy to overlook this step if post r2.5 upgrade your SSL implementation continues to function giving no strong reason to review the SSL configuration documentation for the new release.


The new steps involved a new file on the CAPC host. It is the CADataAggregator.xml file and is found in: the directory:



The changes necessary in that file are:


     Replace the <Scheme> and <Port> values for SingleSignOnWebServiceUrl with settings appropriate for SSL (Do not change values for SignInPageProductDefaultUrl)


For more details the new step is further documented in (as of the time this is written) steps 18 and 19 in the CAPC SSL configuration documentation in the CAPC documentation Wiki. It can be found here:


Alternatively search the r2,5 documentation Wiki for the term "Configure CA Performance Center to Use HTTPS"


Here is a view of those steps in the Wiki showing what is needed to resolve this OpenAPI problem. Note it also displays the specific subsection this information can be found in within the new documentation Wiki.