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

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

book

Article ID: 77703

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

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

ERROR | qtp258341854-136128      | 2022-01-04 11:15:55,944 | com.ca.im.portal.api.services.datasource.DataSourcePoll          
INFO   | jvm 1    | 2022/01/04 11:15:55 |       | javax.xml.ws.soap.SOAPFaultException: Response was of unexpected text/html ContentType.  Incoming portion of HTML stream:

 

Environment

All supported Performance Management and Spectrum releases

Resolution

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 and newer releases:

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>

Additional Information

See the following documentation here: