IP IM connector fail to start when Node 3 up and running

book

Article ID: 195880

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

After added 3rd Vapp appliance to existing setup.  IM /IP are starting but IM connector fail to start when IM node 3 is up.

Cause

1. Binaries were not in syn on 3rd node
 
2. Custom objectclasses not applied to third node userstore

Environment

Release : 14.2

Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)

Resolution

1) Make sure all the CP/HF applied across all nodes.

 

2) Copy custom objectclasses  im_user_aux.dxc under/opt/CA/Directory/dxserver/config/schema  from node1 to node3