JCS Connector Status is not 'Active'

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Risk Analytics
• CA Secure Cloud SaaS - Arcot A-OK (WebFort)
• CLOUDMINDER ADVANCED AUTHENTICATION
• CA Secure Cloud SaaS - Advanced Authentication
• CA Secure Cloud SaaS - Identity Management
• CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

The OSGI bundles have the following life cycle states: 

1. Installed 

2. Resolved 

     a. Starting 

     b. Active 

     c. Stopping 

3. Uninstalled 

 

After a JCS restart, the specified bundles should be in an 'active' state instead of 'resolved'. 

 

After restarting the Java Connector Server (JCS) some servers show a status of 'Resolved' rather than 'Active' in the JCS connector web interface.

For example, connectors with Resolved Status after JCS restart: 

1)  JCS :: Connector :: Common (com.ca.jcs. conectors.common) 

2)  JCS :: Connector :: CsvEmailSender (com.ca.jcs.csv.emailsender) 

3)  JCS :: Connector :: JNDI (com.ca.jcs.jndi) 

 

 

Environment

Release: CAPUEL99000-12.5-Identity Manager-Blended upgrade to Identity &-Access Mgmt Ente
Component:

Resolution

Change the order of the featuresBoot options in the file org.apache.karaf.features.cfg  (located by default in the connector server home, ..\CA\Identity Manager\Connector Server\etc).

Move these two options: jcs-connector-jdbc, jcs-connector-jndi  before  jcs-connector-gab.

The featuresBoot section should look like this:

 

# servicemix-smpp,servicemix-snmp,servicemix-vfs

featuresBoot=karaf-framework,xml-specs,activemq-broker,activemq-spring,camel,camel-activemq,camel-nmr,saaj,camel-cxf,jbi-cluster,war,servicemix-cxf-bc,servicemix-ftp,servicemix-http,servicemix-jms,servicemix-smpp,servicemix-snmp,servicemix-vfs,camel-jms,camel-activemq,camel-spring-security,jcs-osgi,jcs-certificate-service,jcs-management,jcs-dirsync,jcs-tenantws,jcs-ldap-binding,jcs-connector-as400,jcs-connector-ca-dlp,jcs-connector-csproxy,jcs-connector-csv,jcs-connector-csvemailsender,jcs-connector-jdbc,jcs-connector-jndi,jcs-connector-gab,jcs-connector-lnd,jcs-connector-ora,jcs-connector-pps,jcs-connector-rsa7,jcs-connector-sap,jcs-connector-sfdc,jcs-connector-sql,jcs-connector-arcot,jcs-connector-sap-ume,jcs-connector-krbscript,jcs-connector-unix,jcs-connector-common,jcs-connector-tss,jcs-connector-racf,jcs-connector-acf2,jcs-connector-acf2acfesage,jcs-connector-racfirrdbu00,jcs-connector-tsscfile,jcs-connector-o365,jcs-connector-scim

 

Restart JCS. Changes take effect after restarting the JCS services.