Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

Configuring the PowerExchange Listener on the z/OS SSL Server

Configuring the PowerExchange Listener on the z/OS SSL Server

In the DBMOVER configuration file, include a LISTENER statement for 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 SSL processing.
You can separate PowerExchange Listeners in SSL mode and non-SSL mode. For example, you might run the PowerExchange Listener in non-SSL mode on port 13131 to connect to the PowerExchange Navigator and PowerCenter Developer, and in SSL 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 using SSL on port 13132, and the DBMOVER file includes these statements:
LISTENER=(node1,TCPIP,13131) LISTENER=(node1,TCPIP,13132,,,16384,16384)
Because PowerExchange uses Application Transparent-TLS to implement SSL on z/OS, do not include the SSL parameter in the LISTENER statement in the DBMOVER file on z/OS. In addition, 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 causes processing to fail.
For good performance, it is important that the packet sizes specified in comma positions 6 and 7 of the LISTENER statement do not exceed 16384.

0 COMMENTS

We’d like to hear from you!