Implementing TLS Security in a PowerExchange Network

Back Next

Step 2C. Configure the DBMOVER File on the z/OS TLS Server

In the DBMOVER configuration file, include a LISTENER statement with the port that you associated with the PowerExchange Listener task in the AT-TLS policy file. On z/OS, the LISTENER statement does not include any additional parameters for TLS processing.

For example, you might run the PowerExchange Listener in non-TLS mode on port 13131 to connect to the PowerExchange Navigator and PowerCenter Developer and run the Listener in TLS mode on port 13132 to connect to the PowerCenter Integration Service. In this case, the AT-TLS policy file includes a rule for the Listener job that uses TLS on port 13132, and the DBMOVER file includes the following statements:

LISTENER=(node1,TCPIP,13131)
LISTENER=(node1,TCPIP,13132)

Because PowerExchange uses AT-TLS to implement TLS on z/OS, do not include the SSL parameter in the LISTENER statement in the DBMOVER file on z/OS. Also, do not include SSL-related statements, such as SSL_REQ_CLNT_CERT, in the file. Including SSL-related parameters or statements in the DBMOVER file cause processing to fail.

Rename Saved Search

Table of Contents

Implementing TLS Security in a PowerExchange Network

Implementing TLS Security in a PowerExchange Network

Step 2C. Configure the DBMOVER File on the z/OS TLS Server

Step 2C. Configure the DBMOVER File on the z/OS TLS Server