Endevor web service can not connect to Zowe

Products

• Endevor
• Zowe

Issue/Introduction

After enabling the Zowe caching service in the test environment, the Endevor web service is unable to connect.

08:53:58.158 <main> INFO  (c.n.d.s.t.d.RedirectingEurekaHttpClient) Request execution error. endpoint=DefaultEndpoint{ serviceUrl='https://xxxxg1.xxx.net:7553/eureka/}, exception=java.net.ConnectException: EDC8128I Connection refused. stacktrace=com.sun
 .jersey.api.client.ClientHandlerException: java.net.ConnectException: EDC8128I Connection refused.
     at com.sun.jersey.client.apache4.ApacheHttpClient4Handler.handle(ApacheHttpClient4Handler.java:187)

Environment

Endevor V19

ZOWE v3.4

Cause

In Endevor APIML.properties

apimlDiscoveryURL=https://xxxxg1.xxx.net:7553/eureka   << xxxxg1.xxx.net is a DVIPA address

Currently Endevor does not accept a list of URLs, Endevor only accept the direct URL of the API ML instances involved in the HA cluster.

 

Resolution

Each LPAR has an API ML instance and an EWS instance that registers to its local API ML

Update APIML.properties and set 

apimlDiscoveryURL=https://xxxxg1a.xxx.net:7553/eureka << the direct URL of local APIML instance for EWS instance

Restart Endevor web services. 

Additional Information

If the Zowe certificate's Subject Alternative Name (SAN) only contains the old DVIPA address, you may encounter the following error after updating apimlDiscoveryURL and restart Endevor web services:

 

javax.net.ssl.SSLPeerUnverifiedException: Certificate for <xxxxg1a.xxxx.net> doesn't match any of the subject alternative names:

 

To resolve this, create a new certificate and ensure that the new SAN includes all necessary hostnames to avoid connectivity issues.