After installing Business Objects Enterprise 3.1 SP6 (CABI 3.3SP1), Tomcat is upgraded from Tomcat 6.0 to Tomcat 7.0, but the Central Configuration Manager (CCM) shows both Tomcat 6 and Tomcat 7.

Products

• CA IT Asset Manager
• CA Software Asset Manager (CA SAM)
• ASSET PORTFOLIO MGMT- SERVER
• SUPPORT AUTOMATION- SERVER
• CA Service Desk Manager - Unified Self Service
• CA Service Desk Manager
• CA Service Management - Asset Portfolio Management
• CA Service Management - Service Desk Manager

Issue/Introduction

After installing Business Objects Enterprise 3.1 SP6 (CABI 3.3SP1), Tomcat is upgraded from Tomcat 6.0.24 to Tomcat 7.0.23, but the Central Configuration Manager (CCM) shows both Tomcat 6 and Tomcat 7.

<Please see attached file for image>

 

Environment

CA Business Intelligence 3.xAll Supported Windows Operating Systems

Resolution

1.  Check the service name for Tomcat 6 in the Windows Services Control Panel by right clicking on the service and selecting Properties.  Normally the name is like BOE102Tomcat

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKT6AAO" alt="607970b.gif" width="576" height="287">

 

2.  Navigate to the CA\SC\Commonreporting3\tomcat6\bin folder.  Locate and edit the services.bat file with a text editor and change the following line specifying the service name:

set SERVICE_NAME=<service name>

(normally BOE102Tomcat)

3.  Via a command prompt, execute the following command from the CA\SC\Commonreporting3\tomcat6\bin folder

service remove

4.  Open the Central Configuration Manager (CCM) to verify that the Tomcat 6 service no longer appears

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKT7AAO" alt="607970c.gif" width="576" height="236">

Additional Information

TEC592444 - How to install CABI r3 SP6 (also referred to as CABI r3.3 SP1)