Tech Tip - After upgrading to Spectrum 10.2.3, integration with CAPC may break

Document created by rontr01 Employee on Mar 9, 2018
Version 1Show Document
  • View in full screen mode

This scenario will happen if you have Spectrum and CAPC integrated together and Spectrum is set up to utilize HTTPS communication.  The reason is due to the axis2.xml file within Spectrum.  See below for more details as well as how to make the simple edit of the axis2.xml file to allow the integration to work once again:


After CA Spectrum Upgrade, Integration Breaks with CA Performance Management in SSL Environment


CA Spectrum and CA PM integration breaks after CA Spectrum upgrade. This happens when SSL is enabled and CA Spectrum is connected to CA PM using https.

Solution (for Spectrum 10.2.2 and previous versions):

Verify whether SSL is enabled on the OneClick web server host in the CA Spectrum environment. If so, verify that the "axis2.xml" file is updated with HTTPS protocol and appropriate port number.

Follow these steps:

  1. Open the "axis2.xml" file in an editor from "$SPECROOT/tomcat/webapps/axis2/WEB-INF/conf".
  2. Add the following section in axis2.xml after 'http' transportReceiver:

    <transportReceiver name="https" class="org.apache.axis2.transport.http.AxisServletListener"> <parameter name="port">8443</parameter> </transportReceiver>
  3. Restart the Webserver for these changes to take affect.

Solution (for Spectrum 10.2.3)

The "axis2.xml" file contains the following section in commented format. After CA Spectrum upgrade, you can uncomment this code and update the port number to integrate CA Spectrum with CA PM using https. You must restart the Webserver for these changes to take affect.

<transportReceiver name="https" class="org.apache.axis2.transport.http.AxisServletListener"> <parameter name="port">8443</parameter> </transportReceiver>


This document was generated from the following discussion: After upgrading to Spectrum 10.2.3, integration with CAPC may break

1 person found this helpful