Table of Contents

Search

  1. Preface
  2. PowerExchange Navigator Introduction
  3. Data Maps
  4. Data Maps for Specific Data Sources
  5. Copybooks
  6. Registration Groups and Capture Registrations
  7. Extraction Groups and Extraction Maps
  8. Personal Metadata
  9. Database Row Test
  10. PowerExchange Navigator Examples
  11. Appendix A: PowerExchange Functions for User-Defined Fields
  12. Appendix B: User Access Method Programs
  13. Appendix C: Application Groups and Applications
  14. Appendix D: Data Map Properties
  15. Appendix E: Record, Field, and Table Properties
  16. Appendix F: DTL__CAPXTIMESTAMP Time Stamps
  17. Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook

Navigator User Guide

Navigator User Guide

Resource Configuration

Resource Configuration

A PowerExchange Navigator resource configuration defines the location of data maps, personal metadata profiles, and any locally stored capture registrations and extraction maps. Optionally, a resource configuration also defines the locations of the DBMOVER configuration file and PowerExchange license key file.
PowerExchange maintains a set of user-defined resource configurations in the Windows registry for each PowerExchange version that is installed on the machine.
If you are starting PowerExchange Navigator for the first time after installing or upgrading PowerExchange, the
Resource Configuration
dialog box appears. Click
OK
to create a resource configuration named
Default
that stores PowerExchange resources in the following default directory:
installation_directory
/Examples
You can add or edit a resource configuration. If you define multiple resource configurations, select a specific resource configuration as the current configuration. You can delete any configuration except the current configuration. You can also import resource configurations from a previous PowerExchange version.
Do not import resource configurations from a later PowerExchange version into an earlier version. Resource files that were created or updated with the later version might not work with the earlier version.

0 COMMENTS

We’d like to hear from you!