EEM integration gets disabled after eHealth upgrade

Products

• CA eHealth

Issue/Introduction

Issue:

When eHealth is integrated with EEM and upgraded to a later version, the EEM integration will get disabled after the upgrade.

 

 

Environment:

Any Operating System

eHealth version 6.3.x onward

eHealth integrated with EEM

 

 

Cause:

For SSO, eHealth uses  $NH_HOME\web\webCfg\sso.properties file, and during upgrade it gets replaced with a new file, which has EEM disabled by default.

 

Before upgrade this file will contain EEM parameters with EEM server hostname, but, after upgrade the file will have only the following line, which indicates the integration is set to disabled.

WEB_SSO_ENABLED=no 

 

 

Resolution:

This issue is fixed via Rally defect ticket DE129994, and the fix will be included in eHealth 6.3.2.13.

 

 

Workaround:

As a workaround, nhWebSso command must be run again to integrate eHelath with EEM again.

 

Environment

Release: LHDEVC99000-6.3-eHealth-Live Health Upgrade Elements
Component: