ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Catalyst Connector 3.4.1 not appearing in SOI Admin console

book

Article ID: 41366

calendar_today

Updated On:

Products

CA Service Operations Insight (SOI)

Issue/Introduction

Symptoms:

After installing CA Catalyst Container 3.4.1 & Connector on a Windows 2008 Server, the container & connector doesn't appear in SOI Dashboard

Environment:

SOI 3.3 or 4.0

Catalyst Container 3.4.1

Cause:

The following exceptions found in container & problem.log files on the container server.

ERROR [Blueprint Extender: 3] impl.UCFSecurityManager -135-com.ca.ucf.core.bind-3.3.0.50 - Unable to Obtain SecurityService after 25 retries. Bailing out on retries for now, check logs to investigate why SecurityService is un-available 

ERROR [Blueprint Extender: 3] container.BlueprintContainerImpl -13-org.apache.aries.blueprint-0.3.1 - Unable to start blueprint container for bundle com.ca.ucf.node org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to intialize bean NodeContainer

Resolution:

The problem is with EEM, as we noticed the EEM UI takes much time to open and it appears that the connection is very slow. 

1) Check if there is any connectivity issues between Catalyst Container & EEM. 

2) Restart EEM Services, then restart Catalyst Container service and check if that works

3) Point it to another working EEM server

Environment

Release:
Component: SOICTR