cli:mapping
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cli:mapping [2019/11/04 22:18] – Scott Cunliffe | cli:mapping [2025/01/21 22:07] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Customer Mapping ====== | ====== Customer Mapping ====== | ||
- | The Customer Mapping file contains a mapping of your TapeTrack Customer-ID to your Iron Mountain Account Code and vise versa. | + | The Customer Mapping file contains a mapping of your TapeTrack |
The mapping from TapeTrack to Iron Mountain is used when sending data to Iron Mountain and the reverse mapping, from Iron Mountain to TapeTrack, is used for the reconciliation process. | The mapping from TapeTrack to Iron Mountain is used when sending data to Iron Mountain and the reverse mapping, from Iron Mountain to TapeTrack, is used for the reconciliation process. | ||
Line 7: | Line 7: | ||
===== Location ===== | ===== Location ===== | ||
- | An example of a Customer Mapping file can be found under the TapeTrack installation directory TapeTrack\TapeTrack SecureSync\etc\CustomerMapping.txt | + | An example of a Customer Mapping file can be found under the TapeTrack installation directory |
===== Example ===== | ===== Example ===== | ||
- | CustomerMapping.txt | + | CustomerMapping.txt, showing mapping between [[object: |
- | <sxh> | + | The table values are searched sequentially, |
+ | |||
+ | It is important that entries are present to both match the [[object: | ||
+ | |||
+ | <code> | ||
# | # | ||
- | # This file contains a mapping of your TapeTrack Customer-ID to your IRM Account Code and vise versa. | + | # This file contains a mapping of your TapeTrack Customer-ID to your Iron Mountain |
# | # | ||
# * In the example below, ACME is your TapeTrack Customer-ID and 99999 is your IRM Account Code. | # * In the example below, ACME is your TapeTrack Customer-ID and 99999 is your IRM Account Code. | ||
# * The mapping from TapeTrack to Iron Mountain is used when sending data to IRM | # * The mapping from TapeTrack to Iron Mountain is used when sending data to IRM | ||
- | # * The mapping from Irom Mountain to TapeTrack is used during reconciliation | + | # * The mapping from Iron Mountain to TapeTrack is used during reconciliation |
# * You can use wildcards on the left hand side (eg. *=99999) | # * You can use wildcards on the left hand side (eg. *=99999) | ||
# * The table is search sequentially so once a left hand value has been found searching stops | # * The table is search sequentially so once a left hand value has been found searching stops | ||
Line 25: | Line 29: | ||
ACME=99999 | ACME=99999 | ||
99999=ACME | 99999=ACME | ||
- | </sxh> | + | </code> |
- | ===== Technical Support ===== | ||
- | The TapeTrack Software is commercially supported by a full time help desk staff. If you are experiencing problems or want some advice on how to configure or use the product please see the [[common: |
cli/mapping.1572905887.txt.gz · Last modified: 2025/01/21 22:07 (external edit)