after installing SOI 4.3 with custom installation path, the catalyst registry is unavailable in SOI

Products

• CA Service Operations Insight (SOI)

Issue/Introduction

After installing a fresh SOI 4.3 CU1, the Catalyst Registry seems to be unavailable in UI.
Neither using the link in the SOI Dashboard - Administration - CA Service Operations Insight Manager Configuration - <server> - Catalyst Registry - Launch Catalyst Registry,
nor using the direct link https://<server>:9443/registry/carbon/admin/login.jsp.
 
This was fixed in SOI 4.2 CU4, but in SOI 4.3 it still seems to be there

Environment

SOI 4.3 CU1

Cause

This issue was caused by the problem with WSO2 service installation - after installing SOI, the WSO2 service was not present in services window. This issue seems to occur only if the custom path of the installation is used. 

 

 

Resolution

A potential workaround would be to use the following commands before installation:

fsutil 8dot3name set <drive letter>: 0
  
eg. in case of D drive 
 
fsutil 8dot3name set D: 0

 

When the SOI is already installed and WSO2 is not there, you can follow this procedure:

 

Please verify the file path for WSO2Registry is like WSO2RE~1, then please update
D:\CA\SOI\jsw\conf\wso2registry.conf

Wrong case  ->
# set the working directory to the CARBON_HOME
wrapper.working.dir=D:\CA\SOI/WSO2RE~1

Please modify it as follows:

Correct case - >
# set the working directory to the CARBON_HOME
wrapper.working.dir=D:/CA/SOI/wso2registry

And, also please update WSO2RE~1 with wso2registry in the remaining places in wso2registry.conf file

After updating the file, you would need to run SAM_Services.cmd install
from jsw/bin directory, which will install the WSO2 service 

 

However, the fix for this issue will be available in the SOI 4.3 CU2.