DCI ISPF client no longer connects after AT-TLS implementation
search cancel

DCI ISPF client no longer connects after AT-TLS implementation

book

Article ID: 205307

calendar_today

Updated On:

Products

Dynamic Capacity Intelligence

Issue/Introduction

The communication between Dynamic Capacity Intelligence (DCI) Agents and Controller has been encrypted via Application Transparent-Transport Layer Security (AT-TLS) and it works fine.

However, the ISPF clients are no longer working as they get the message: "Connect to the Controller Task with IP-address xxx.xxx.xxx.xxx failed."

Environment

Release : 2.0

Component : CA DYNAMIC CAPACITY INTELLIGENCE

Cause

The ISPF client too uses TCP/IP to connect to the Controller

Resolution

Every user that have to start the DCI ISPF interface must be set up for AT-TLS too.