17.20 - Properties.xml 文件 - BAR - Data Stream Architecture - Data Stream Utility

Teradata® DSA - DSU 安装、配置和升级指南

Product
BAR
Data Stream Architecture
Data Stream Utility
Release Number
17.20
Published
2021 年 10 月
Content Type
安装
配置
Publication ID
B035-3153-101K-CHS
Language
中文 (简体)

properties.xml 文件包含 DSAMetaDataMigrator 应用程序的输入参数。其中包含 XML 格式的 DSC、系统和媒体服务器的凭据和相关信息。使用该应用程序生成模板文件。

  • 使用 ./runAutoMigration.py -g 生成模板 properties.xml 文件。该文件在当前目录中创建。
  • 生成的文件包括作为 DSC 安装一部分的系统中可用的所有信息。
  • 使用输入文件前,必须先填写缺少的信息。
  • 如果文件中没有密码,系统会在运行应用程序时提示输入凭据。
  • 为避免在执行过程中出现提示,您可以将 <silentmode> 设置为 yes,并且必须在文件中记录密码。
  • 在目标或新 DSC 系统上执行导出操作后,可以为此文件更新媒体服务器和系统详细信息。
  • 云平台:
    • 要使用 .pem 文件通过 ssh 连接到 DSC 虚拟机,您必须在 <private_key_file> 标记中提供 .pem 文件的路径并在 <private_username> 标记中提供用户名。
    • 如果没有 .pem 文件,可以通过 ssh 连接并输入用户名和密码。
    • .pem 文件用于云时,请勿在 properties.xml 文件中输入 <systemusername><systemuserpass> 的值,这些值将覆盖 .pem 文件中的值。

示例 properties.xml 文件

<data>
<!-- This properties.xml is the input file having parameters required during migration
     Credential provided in this file is not encrypted
     Migrator application delete this file after successful migration
     In case of failure or partial migration, file remain present so user should delete  
     when not in use -->
 
<!-- provide path of the pem file along with user name for authentication on cloud platform-->

<!--
<private_key_file>/var/opt/teradata/scripts/access_key.pem</private_key_file>
<private_username>ec2-user</private_username>
-->
 
<!-- set silent mode YES in case don't want to get prompt during migration process -->
<silentmode></silentmode>
 
<!-- provide old DSC detail -->
<olddscserver>
  <systemname></systemname> <!-- system name -->
  <tdrepohost></tdrepohost> <!-- host of the Teradata repo, default is DSC system -->
  <tdrepodbname></tdrepodbname> <!-- name of the Teradata repo DB, default is bar (please do not edit) -->
  <tdrepodbpass></tdrepodbpass> <!-- Teradata repo (bar) DB password (should not include space, single or double quotes) -->
  <brokerurl></brokerurl> <!-- broker URL of the old DSC -->
  <systemusername></systemusername> <!-- user name of the old DSC system -->
  <systemuserpass></systemuserpass> <!-- password of the old DSC system (should not include space, single or double quotes) -->
</olddscserver>
 
<!-- provide new DSC detail -->
<dscserver>
  <dsaresthost></dsaresthost> <!-- system name hosting dsarest, defualt is DSC server -->
  <dsarestport></dsarestport> <!-- port of the dsa rest server -->
  <dsarestwebservice></dsarestwebservice> <!-- dsa rest web service, it can be https or http -->
  <brokerurl></brokerurl> <!-- broker URL of the new DSC -->
  <brokerport></brokerport><!-- broker port of the new DSC -->
  <pgrepohost></pgrepohost> <!-- host of the Postges repo, default is DSC system -->
  <pgrepodbname></pgrepodbname> <!-- name of the Postgres repo DB, default is bar (please do not edit) -->
  <pgrepodbpass></pgrepodbpass> <!-- Postgres repo (bar) DB password (should not include space, single or double quotes) -->
</dscserver>
 
<!-- provide list of media servers to be reconfigured -->
<mediaservers>
  <mediaserver>
    <mediaservername></mediaservername> <!-- name of the media server  -->
    <username></username> <!-- user name for the media server  -->
    <password></password> <!-- password of the media server (should not include space, single or double quotes) -->
  </mediaserver>
</mediaservers>
 
<!-- provide list of systems to be reconfigured -->
<systems>
  <system>
    <systemname></systemname> <!-- system name -->
    <db_username></db_username> <!-- database user name -->
    <db_password></db_password> <!-- database password (should not include space, single or double quotes) -->
    <system_username></system_username> <!-- user name of the system (master node) -->
    <system_password></system_password> <!-- password of the system (master node) -->
  </system>
</systems>
</data>