Table of Contents

Search

  1. Preface
  2. Using Metadata Manager
  3. Configuring Metadata Manager
  4. Application Resources
  5. Business Glossary Resources
  6. Business Intelligence Resources
  7. Custom Resources
  8. Data Integration Resources
  9. Data Modeling Resources
  10. Database Management Resources
  11. Universal Resources
  12. Managing Resources
  13. Loading and Monitoring Resources
  14. Managing Permissions
  15. Resource Migration
  16. Repository Migration
  17. Appendix A: Metadata Manager Login
  18. Appendix B: Metadata Manager Properties Files
  19. Appendix C: Resource Configuration Files
  20. Appendix D: Glossary

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

Configure PowerExchange

Configure PowerExchange

To configure PowerExchange, complete the following tasks:
  • Configure PowerExchange to connect to the z/OS machine where the Metadata Manager Service runs.
  • Configure the PowerExchange DBMOVER configuration file on the machine where the Metadata Manager Service runs. Add a NODE statement that points to the PowerExchange Listener on z/OS. For example:
    /*********************************************************************/ /* PowerExchange Configuration File /*********************************************************************/ LISTENER=(node1,TCPIP,2480) LISTENER=(BGQALST,TCPIP,30080) LISTENER=(BGQALST_new,TCPIP,448) LISTENER=(DB2zOS_SPEDDUR,TCPIP,448) /***********************************************************************/ NODE=(DB2zOS_SPEDDUR,TCPIP,mhz890-2,3156) NODE=(local,TCPIP,000.0.0.1,2480) NODE=(node1,TCPIP,000.0.0.1,2480) NODE=(BGQALST,TCPIP,mhz890-2,30080)
  • Configure the DBMOVER configuration member on the z/OS system to control access to the DB2 for z/OS system. Add the following SECURITY statement with option 2 to use an MVS user ID and password or PowerExchange passphrase, along with your z/OS security product:
    SECURITY=(2,N)
Optionally, configure the PowerExchange Listener on z/OS to recognize logins that are known to the operating system. More specifically, option 2 causes PowerExchange to control access based on the following:
  • MVS user ID and password or a valid PowerExchange passphrase
  • Access control features of your z/OS security product, such as RACF or ACF2
By default, PowerExchange on z/OS uses the user ID under which the PowerExchange Listener runs.

0 COMMENTS

We’d like to hear from you!