identity manager jcs service does not start

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

On AWS environment, the Identity Manager deployment is not working, the deploy stop while trying to connect to JCS

In the \opt\CA\VirtualAppliance\logs\ca_vapp_main.log file there is the following message:

2018 Oct 15 12:36:44 ip-10-203-5-21 initServices [0;31m[ERROR] The Connector Server service is not accepting connections after waiting for the timeout threshold (600 seconds)[0m
2018 Oct 15 12:36:44 ip-10-203-5-21 initServices [1;31m[ERROR] Initialization script for im_jcs exited with error status 10[0m
2018 Oct 15 12:36:44 ip-10-203-5-21 initServices [1;31m[ERROR] The service im_jcs failed to initialize (error code 10). Please inspect the log file: /opt/CA/VirtualAppliance/logs/ca_vapp_main.log[0m
2018 Oct 15 12:36:44 ip-10-203-5-21 updateMachineJson Entered function updateMachineJson with arguments: ERROR Fatal error: 10 
2018 Oct 15 12:36:44 ip-10-203-5-21 deploySolution_main deploySolution terminated with exit code 10
2018 Oct 15 12:36:44 ip-10-203-5-21 deploySolution_main ========================================================================
2018 Oct 15 12:36:44 ip-10-203-5-21 deploySolution_main deploySolution - program was terminated by signal request - cleaning up...
2018 Oct 15 12:36:44 ip-10-203-5-21 deploySolution_main Terminating background monitoring script (PID: 23607)
2018 Oct 15 12:36:44 ip-10-203-5-21 deploySolution_main Finished sending EXIT request to all SSH sockets
 

Environment

Virtual Appliance 14.2 on AWS 

Cause

Check if the AWS has Public IP, before starting the deployment, check if the AWS instance has a Public IP, if you already deployed Identity Manager, adding the Public IP will not solve the problem.
 

Resolution

Make sure to create the AWS instance with Public IP, and after that, you can start Virtual Appliance to deploy the Identity Manager 14.2