#===================================================================================================
# This file contains text for both the metadatasrv and metadatasrvn 12-bytes.  Metadata server
# configuration knows to only use "metadatasrv", but cfgwizard configuration utilities generate 
# property names blindly based on the 12-byte name.  Hence, a duplicate set of "metadatasrvn" 
# properties are necessary, and dual maintenance rears its ugly head.
#===================================================================================================

#=============================================================
#  metadatasrv 12-byte
#=============================================================
instructions_metadatasrv_head.txt=<h3>${iomsrv.metadatasrv.name}</h3> ${line.separator}\

instructions_metadatasrv_details_table_head.txt=<table class="detailTable" border=0 cellPadding=0 cellSpacing=0>  ${line.separator}\

instructions_metadatasrv_details_host.txt=<tr> ${line.separator}\
      <td class="detailLabel">Host machine</td> ${line.separator}\
      <td class="detailContent">${iomsrv.metadatasrv.host}</td> ${line.separator}\
   </tr> ${line.separator}\
   <tr> ${line.separator}\
      <td class="detailLabel">Port</td> ${line.separator}\
      <td class="detailContent">${iomsrv.metadatasrv.port}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_metadatasrv_details_services.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Windows service ${line.separator}\
         <br class="br">${iomsrv.metadatasrv.service.name}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_metadatasrv_details_scripts_Windows.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Batch script ${line.separator}\
         <br class="br">${metadatasrv.config.lev.appservercontext.dir}${file.separator}${iomsrv.metadatasrv.config.dir.name}${file.separator}${iomsrv.metadatasrv.script.name}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_metadatasrv_details_scripts_Unix.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Shell script ${line.separator}\
         <br class="br">${metadatasrv.config.lev.appservercontext.dir}/${iomsrv.metadatasrv.config.dir.name}/${iomsrv.metadatasrv.script.name}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_metadatasrv_details_shortcuts_Windows.txt=<tr> ${line.separator}\
      <td class="detailLabel">Shortcuts</td> ${line.separator}\
      <td class="detailContent">Programs &gt; SAS &gt; Configuration &gt; ${server.shortcut.folder.display.name}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_metadatasrv_details_logging.txt=<tr> ${line.separator}\
      <td class="detailLabel">Log directory</td> ${line.separator}\
      <td class="detailContent"><a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> ${line.separator}\
       <br class="br">For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the <em>SAS Intelligence Platform: System Administration Guide</em> at <a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>.</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_metadatasrv_start_Zos.txt=<tr> ${line.separator}\
      <td class="detailLabel">Started task</td> ${line.separator}\
      <td class="detailContent">${z64.high.level.qualifier}.${ENC2}.SRVPROC(${iomsrv.metadatasrv.stcname})</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_metadatasrv_details_table_tail.txt=</table> ${line.separator}\

instructions_metadatasrv_details_SAS_Account_Section.txt=<h4>SAS Accounts:</h4>

instructions_metadatasrv_details_SAS_admin_account.txt=<p>&quot;${metadatasrv.instructions.details.admin.name}&quot; (${metadatasrv.instructions.details.admin.sdwlogin}) is the metadata server Unrestricted Administrator identity.</p>

instructions_metadatasrv_details_logins_admin.txt=<p>These additional logins exist for the Unrestricted Administrator identity:</p> ${metadatasrv.instructions.details.admin.loginlist} <blockquote><i>Some of the logins above may be different as a result of subsequent processing.</i></blockquote>

instructions_metadatasrv_details_SAS_demo_account.txt=<p>&quot;${metadatasrv.instructions.details.demo.name}&quot; (${metadatasrv.instructions.details.demo.sdwlogin}) is the metadata server First User identity.</p>

instructions_metadatasrv_details_logins_demo.txt=<p>These additional logins exist for the First User identity:</p> ${metadatasrv.instructions.details.demo.loginlist} <blockquote><i>Some of the logins above may be different as a result of subsequent processing.</i></blockquote>

instructions_metadatasrv_details_SAS_trustusr_account.txt=<p>&quot;${metadatasrv.instructions.details.trustusr.name}&quot; (${metadatasrv.instructions.details.trustusr.sdwlogin}) is the metadata server Trusted User identity.</p>

instructions_metadatasrv_details_login.txt=Login

instructions_metadatasrv_details_auth_domain.txt=authentication domain

instructions_metadatasrv_details_logins_trustusr.txt=<p>These additional logins exist for the Trusted User identity:</p> ${metadatasrv.instructions.details.trustusr.loginlist} <blockquote><i>Some of the logins above may be different as a result of subsequent processing.</i></blockquote>

instructions_metadatasrv_details_notes_head.txt=<h4>Notes:</h4> ${line.separator}\
<ul> ${line.separator}\

instructions_metadatasrv_details_backups.txt=<li>The metadata server is configured to perform unassisted metadata server backups. ${line.separator}\
The backups are performed every day at 1 a.m. except on Sunday and stored in the ${line.separator}\
&quot;${metadatasrv.backup.dir.absolutepath}&quot; directory. Backups are retained ${line.separator}\
for seven days. To learn about the metadata server backup facility, see &quot;Backing Up ${line.separator}\
and Recovering the SAS Metadata Server&quot; in the <em>SAS Intelligence Platform: System Administration Guide</em> at ${line.separator}\
<a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>. </li> ${line.separator}\

instructions_metadatasrv_details_alertemail.txt=<li>The metadata server is configured to send an alert e-mail message to ${line.separator}\
<b>${server.mailsrv.email.to.address}</b> in the event of a system, backup, or recovery  failure. You can test that the ${line.separator}\
alert-email notification subsystem is configured properly by opening the Properties sheet for the active metadata server ${line.separator}\
in the SAS Management Console Metadata Manager and sending a test message. If the system is configured properly, you will receive a ${line.separator}\
test e-mail from <b>${iomsrv.metadatasrv.name} ${config.dir.name} - ${config.level.name} &lt;${server.mailsrv.email.sender.address}&gt;</b>. ${line.separator}\
If you want to change your alert e-mail options, see the section &quot;Managing Alert E-mail Options for the SAS Metadata Server&quot; ${line.separator}\
in the chapter &quot;Metadata Server Configuration Tasks&quot; of the <em>SAS Intelligence Platform: System Administration Guide</em> ${line.separator}\
at <a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>. </li> ${line.separator}\

instructions_metadatasrv_details_zos.txt=<li>All of the SAS Business Intelligence servers on z/OS are configured and ${line.separator}\
initially run from the UNIX System Services (USS) shell using /bin/tso.  SAS recommends that servers run as started ${line.separator}\
tasks in a production environment, and preconfigured started task definitions have been provided. All currently running ${line.separator}\
USS servers can be terminated by running the shell script: <b>${config.lev.dir}${file.separator}sas.servers stop</b>. ${line.separator}\
Then the started tasks can be copied into the started task library, and started with the start command.  Have all servers ${line.separator}\
running, either as started tasks or under USS shell, before performing the following validation steps.</li> ${line.separator}\

instructions_metadatasrv_details_notes_tail.txt=</ul>  ${line.separator}

instructions_metadatasrv_additionalinfo.txt=<h4>Backing Up Your SAS Deployment</h4>${line.separator}\
${line.separator}\
<p>The SAS system now includes a Deployment Backup utility that can back up the following ${line.separator}\
components of your SAS deployment:  ${line.separator}\
<ul> ${line.separator}\
<li>the metadata server</li> ${line.separator}\
<li>selected data and configuration directories on any SAS server tier</li> ${line.separator}\
<li>the SAS Content Server repository</li> ${line.separator}\
<li>any SAS Web Infrastructure Data Server databases</li> ${line.separator}\
<li>custom directories configured for your site</li> ${line.separator}\
</ul> ${line.separator}\
If the Deployment Backup utility is configured on your system, it will automatically run ${line.separator}\
every Sunday at 1 a.m.  The automatic backup schedule can be changed or disabled.  For more ${line.separator}\
information, see &quot;Using the Deployment Backup and Recovery Tool&quot; in the ${line.separator}\
<em>SAS Intelligence Platform: System Administration Guide</em> at ${line.separator}\
<a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>.</p> ${line.separator}\
${line.separator}\
<p><b>Caution:</b> Regular backups of your SAS system ${line.separator}\
are crucial to ensuring the health of your SAS ${oma.server.softwareversion.version} ${line.separator}\
Intelligence Platform configuration. It is recommended that you schedule ${line.separator}\
regular system backups to occur just after the SAS metadata or deployment backups so that each system backup ${line.separator}\
includes a timely backup of your SAS components. For more information, see &quot;Best ${line.separator}\
Practices for Backup and Restore&quot; in the <em>SAS Intelligence Platform: System Administration Guide</em> at ${line.separator}\
<a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>.</p> ${line.separator}\

instructions_metadatasrv_host_specific_login.txt=You should be logged on as the SAS Installer user (${oma.person.bootstrap.login.userid}).&nbsp;

warnings_metadatasrv_services.txt=<li><b>WARNING:</b> One or more issues were encountered during the creation of the service <b>${iomsrv.metadatasrv.service.name}</b>.  Typically this occurs when a service with the same name already exists.  The dependency chain for this service, and any other services that might depend on it, could be compromised.  Use the Services Manager to verify that the properties of this service are correct.  If they are incorrect, uninstall this configuration and reconfigure.</li> ${line.separator}\

warnings_metadatasrv_shortcuts.txt=<li><b>WARNING:</b> One or more shortcuts for the metadata server were not created. Verify the following: </li> ${line.separator}\
  <ul> ${line.separator}\
    <li>${error.command} exists</li> ${line.separator}\
    <li><b>${error.commandline}</b> is correct and any files specified exist</li> ${line.separator}\
  </ul> ${line.separator}\
  
errors_metadatasrv_head.txt=<h3>SAS Metadata Server failed to deploy successfully</h3> ${line.separator}\

errors_metadatasrv_list_head.txt=<ol> ${line.separator}\

errors_metadatasrv_list_tail.txt=</ol> ${line.separator}\

errors_metadatasrv_validateUserHostAccount_installer.txt=<p>The user ID, ${error.user}, specified as the installer account, is invalid.  Either the account does not exist or the given password is invalid.  Metadata server configuration cannot continue.</p>${line.separator}\

errors_metadatasrv_validateUserHostAccount_sasadm.txt=<p>The user ID, ${error.user}, specified as the SAS administrator account, is invalid.  Either the account does not exist or the given password is invalid.  Metadata server configuration cannot continue.</p>${line.separator}\

errors_metadatasrv_validateUserHostAccount_sastrust.txt=<p>The user ID, ${error.user}, specified as the SAS trusted user account, is invalid.  Either the account does not exist or the given password is invalid.  Metadata server configuration cannot continue.</p>${line.separator}\

errors_metadatasrv_validatePorts.txt=<li><p>SAS Metadata Server failed on host ${iomsrv.metadatasrv.host}, port ${iomsrv.metadatasrv.port}. ${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrv_backup.txt=<li><p>Backup of files in both ${error.srcdir} and ${error.deploydir} failed. The directory may be read only, the directory may not exist, or the permissions are insufficient for this process.${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrv_moveOrigFiles.txt=<li><p>The copying and configuring of files from ${error.srcdir} to ${error.deploydir} failed. ${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrv_loadMetadata.txt=<li><p>Information could not be loaded into the metadata server. ${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li> ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
      ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrv_installShortcuts.txt=<li><p>Metadata server shortcuts were not created.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.command} exists</li> ${line.separator}\
      <li>${error.commandline} is correct and any files specified exist</li> ${line.separator}\
   </ul></p> ${line.separator}\
 </li>  ${line.separator}\
  
errors_metadatasrv_installServices.txt=<li><p>The metadata server could not be installed as a service.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.command} exists</li> ${line.separator}\
      <li><b>${error.commandline}</b> is correct and any files specified exist</li> ${line.separator}\
   </ul></p> ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrv_removeServices.txt=<li><p>The metadata server service could not be removed.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.serviceName} exists and is a valid service</li> ${line.separator}\
      <li>${error.command} exists</li> ${line.separator}\
      <li>${error.commandline} is correct and any files specified exist</li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\
  
errors_metadatasrv_startMetadataServer.txt=<li><p>The metadata server could not be started and no listener was detected on the specified host (${iomsrv.metadatasrv.host}) and port (${iomsrv.metadatasrv.port}). ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
      <li>Verify that all path references are correct, up to and including shortcuts, service definitions, shell scripts, symbolic links, etc. as applicable.  An invalid path can result in the metadata server failing to start.</li> ${line.separator}
   </ul> ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrv_restartMetadataServer.txt=<li><p>The metadata server could not be restarted and no listener was detected on the specified host (${iomsrv.metadatasrv.host}) and port (${iomsrv.metadatasrv.port}). ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
      <li>Verify that all path references are correct, up to and including shortcuts, service definitions, shell scripts, symbolic links, etc. as applicable.  An invalid path can result in the metadata server failing to start.</li> ${line.separator}
   </ul> ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrv_migrationMetadatasrvMigrate.txt=<li><p>Metadata server migration failed on host ${iomsrv.metadatasrv.host}, port ${iomsrv.metadatasrv.port}. ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
   </ul> ${line.separator}\
</li>  ${line.separator}\

# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#  unconfigure target
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

unconfiguration_metadatasrv_summary_head.txt=<h3>SAS Metadata Server</h3> ${line.separator}\

unconfiguration_metadatasrv_summary_item.txt=<p>The metadata server was removed.</p> ${line.separator} \
   <ul> ${line.separator}\
         <li>${metadatasrv.configobj.name} was removed from metadata.</li> ${line.separator}\
         <li>The following directories and their content were not removed as they contain both user content and a record of metadata transactions: ${line.separator}\
            <ul> ${line.separator}\
            <li>${metadatasrv.journal.dir}</li> ${line.separator}\
            <li>${metadatasrv.rposmgr.dir}</li> ${line.separator}\
            <li>${metadatasrv.repository.root.dir} ${line.separator}\
            <li>${metadatasrv.backup.dir.absolutepath}</li> ${line.separator}\
         </ul> </li> ${line.separator}\
   <li>The metadata server's foundation repository was not removed because it contains user content. If you want to configure a new deployment and retain none of your previous content or settings, then you must rename or delete the ${metadatasrv.config.dir} directory prior to creating your new deployment.</li> ${line.separator}\

unconfiguration_metadatasrv_summary_Windows_services_item.txt=<li>The service named ${iomsrv.metadatasrv.service.name} was stopped and removed.</li> ${line.separator}\
      <li>Shortcuts were removed.</li> ${line.separator}\

unconfiguration_metadatasrv_summary_Windows_scripts_item.txt=<li>Shortcuts were removed.</li> ${line.separator}\

unconfiguration_metadatasrv_summary_tail.txt=</ul>

# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#  updatePasswords target
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

updatePasswords_metadatasrv_summary_head.txt=<h3>SAS Metadata Server</h3> ${line.separator}\
   <ul> ${line.separator}\

updatePasswords_metadatasrv_summary_sasadm_item.txt=<li>The password for ${oma.person.admin.person.display.name} (${oma.person.admin.login.userid}) was changed in the ${oma.repository.foundation.name} repository.</li> ${line.separator}\

updatePasswords_metadatasrv_summary_sastrust_item.txt=<li>The password for ${oma.person.trustusr.person.display.name} (${oma.person.trustusr.login.userid}) was changed in the ${oma.repository.foundation.name} repository.</li> ${line.separator}\

updatePasswords_metadatasrv_summary_sasadm_script_item.txt=<li>The password for ${oma.person.admin.person.display.name} (${oma.person.admin.login.userid}) was changed in metaparms.sas. ${line.separator}\

updatePasswords_metadatasrv_summary_mailsrv_item.txt=<li>The password for the E-mail Server Authentication User (${server.mailsrv.userid}) was changed in sasv9.cfg. ${line.separator}\

updatePasswords_metadatasrv_summary_tail.txt=</ul>

# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#  changeHost target
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

instructions_metadatasrv_changeHost_manual_head.txt=<h4>Manual Instructions for SAS Metadata Server</h4> ${line.separator}\
<p>Warnings were encountered updating host name references. Review this section and correct any warnings reported.</p> ${line.separator}\
<ul> ${line.separator}\

instructions_metadatasrv_backup_failure_txt=<li><b>WARNING:</b> The backup of metadata server <b>${local.metadatasrv.host}</b> failed.</li> ${line.separator}\

instructions_metadatasrv_changeHost_manual_tail.txt=</ul>

#=============================================================
#  metadatasrvn 12-byte
#=============================================================

instructions_metadatasrvn_details_services.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Windows service ${line.separator}\
         <br class="br">${iomsrv.metadatasrvn.service.name}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_metadatasrvn_start_Zos.txt=<tr> ${line.separator}\
      <td class="detailLabel">Started task JCL</td> ${line.separator}\
      <td class="detailContent">${metadatasrv.config.dir}${file.separator}MetadataServer.jcl</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_metadatasrvn_details_backups.txt=<li>This metadata server node will be backed up during any ${line.separator}\
automatic or manual metadata server cluster backup.  See &quot;Managing a Clustered Metadata Server&quot; ${line.separator}\
in the <em>SAS Intelligence Platform: System Administration Guide</em> at ${line.separator}\
<a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a> ${line.separator}\
for more information.</li> ${line.separator}\

instructions_metadatasrvn_details_zos.txt=<li>All of the SAS Business Intelligence servers on z/OS are configured and ${line.separator}\
initially run from the UNIX System Services (USS) shell using /bin/tso.  SAS recommends that servers run as started ${line.separator}\
tasks in a production environment, and preconfigured started task definitions have been provided.  For this metadata ${line.separator}\
server node, the JCL exists in the MetadataServer.jcl file shown in the table above.  The task name ${line.separator}\
(${iomsrv.metadatasrv.stcname}) is the same as the task for the first metadata server configured.  You may want to edit ${line.separator}\
the JCL to change the task name.  All currently running USS servers can be terminated by running the shell script: ${line.separator}\
<b>${config.lev.dir}${file.separator}sas.servers stop</b>. Then the started tasks can be copied into the started task ${line.separator}\
library, and started with the start command. Have all servers running, either as started tasks or under USS shell, before ${line.separator}\
performing the following validation steps.</li> ${line.separator}\

warnings_metadatasrvn_services.txt=<li><b>WARNING:</b> One or more issues were encountered during the creation of the service <b>${iomsrv.metadatasrvn.service.name}</b>.  Typically this occurs when a service with the same name already exists.  The dependency chain for this service, and any other services that might depend on it, could be compromised.  Use the Services Manager to verify that the properties of this service are correct.  If they are incorrect, uninstall this configuration and reconfigure.</li> ${line.separator}\

warnings_metadatasrvn_shortcuts.txt=<li><b>WARNING:</b> One or more shortcuts for the metadata server were not created. Verify the following: </li> ${line.separator}\
  <ul> ${line.separator}\
    <li>${error.command} exists</li> ${line.separator}\
    <li><b>${error.commandline}</b> is correct and any files specified exist</li> ${line.separator}\
  </ul> ${line.separator}\
  
errors_metadatasrvn_head.txt=<h3>SAS Metadata Server failed to deploy successfully</h3> ${line.separator}\

errors_metadatasrvn_list_head.txt=<ol> ${line.separator}\

errors_metadatasrvn_list_tail.txt=</ol> ${line.separator}\

errors_metadatasrvn_validateUserHostAccount_installer.txt=<p>The user ID, ${error.user}, specified as the installer account, is invalid.  Either the account does not exist or the given password is invalid.  Metadata server configuration cannot continue.</p>${line.separator}\

errors_metadatasrvn_validateUserHostAccount_sasadm.txt=<p>The user ID, ${error.user}, specified as the SAS administrator account, is invalid.  Either the account does not exist or the given password is invalid.  Metadata server configuration cannot continue.</p>${line.separator}\

errors_metadatasrvn_validateUserHostAccount_sastrust.txt=<p>The user ID, ${error.user}, specified as the SAS trusted user account, is invalid.  Either the account does not exist or the given password is invalid.  Metadata server configuration cannot continue.</p>${line.separator}\

errors_metadatasrvn_validatePorts.txt=<li><p>SAS Metadata Server failed on host ${iomsrv.metadatasrv.host}, port ${iomsrv.metadatasrv.port}. ${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrvn_backup.txt=<li><p>Backup of files in both ${error.srcdir} and ${error.deploydir} failed. The directory may be read only, the directory may not exist, or the permissions are insufficient for this process.${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrvn_moveOrigFiles.txt=<li><p>The copying and configuring of files from ${error.srcdir} to ${error.deploydir} failed. ${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrvn_loadMetadata.txt=<li><p>Information could not be loaded into the metadata server. ${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li> ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
      ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrvn_installShortcuts.txt=<li><p>Metadata server shortcuts were not created.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.command} exists</li> ${line.separator}\
      <li>${error.commandline} is correct and any files specified exist</li> ${line.separator}\
   </ul></p> ${line.separator}\
 </li>  ${line.separator}\
  
errors_metadatasrvn_installServices.txt=<li><p>The metadata server could not be installed as a service.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.command} exists</li> ${line.separator}\
      <li><b>${error.commandline}</b> is correct and any files specified exist</li> ${line.separator}\
   </ul></p> ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrvn_removeServices.txt=<li><p>The metadata server service could not be removed.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.serviceName} exists and is a valid service</li> ${line.separator}\
      <li>${error.command} exists</li> ${line.separator}\
      <li>${error.commandline} is correct and any files specified exist</li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\
  
errors_metadatasrvn_startMetadataServer.txt=<li><p>The metadata server could not be started and no listener was detected on the specified host (${iomsrv.metadatasrv.host}) and port (${iomsrv.metadatasrv.port}). ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
      <li>Verify that all path references are correct, up to and including shortcuts, service definitions, shell scripts, symbolic links, etc. as applicable.  An invalid path can result in the metadata server failing to start.</li> ${line.separator}
   </ul> ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrvn_restartMetadataServer.txt=<li><p>The metadata server could not be restarted and no listener was detected on the specified host (${iomsrv.metadatasrv.host}) and port (${iomsrv.metadatasrv.port}). ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
      <li>Verify that all path references are correct, up to and including shortcuts, service definitions, shell scripts, symbolic links, etc. as applicable.  An invalid path can result in the metadata server failing to start.</li> ${line.separator}
   </ul> ${line.separator}\
</li>  ${line.separator}\

errors_metadatasrvn_migrationMetadatasrvMigrate.txt=<li><p>Metadata server migration failed on host ${iomsrv.metadatasrv.host}, port ${iomsrv.metadatasrv.port}. ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>Metadata server logs: <a href="${metadatasrv.logs.dir}">${metadatasrv.logs.dir}</a> </li> ${line.separator}\
   </ul> ${line.separator}\
</li>  ${line.separator}\

# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#  unconfigure target
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

unconfiguration_metadatasrvn_summary_head.txt=<h3>SAS Metadata Server</h3> ${line.separator}\

unconfiguration_metadatasrvn_summary_item.txt=<p>The metadata server was removed.</p> ${line.separator} \
   <ul> ${line.separator}\
         <li>${metadatasrv.configobj.name} was removed from metadata.</li> ${line.separator}\
         <li>The following directories and their content were not removed as they contain both user content and a record of metadata transactions: ${line.separator}\
            <ul> ${line.separator}\
            <li>${metadatasrv.journal.dir}</li> ${line.separator}\
            <li>${metadatasrv.rposmgr.dir}</li> ${line.separator}\
            <li>${metadatasrv.repository.root.dir} ${line.separator}\
            <li>${metadatasrv.backup.dir.absolutepath}</li> ${line.separator}\
         </ul> </li> ${line.separator}\
   <li>The metadata server's foundation repository was not removed because it contains user content. If you want to configure a new deployment and retain none of your previous content or settings, then you must rename or delete the ${metadatasrv.config.dir} directory prior to creating your new deployment.</li> ${line.separator}\

unconfiguration_metadatasrvn_summary_Windows_services_item.txt=<li>The service named ${iomsrv.metadatasrvn.service.name} was stopped and removed.</li> ${line.separator}\
      <li>Shortcuts were removed.</li> ${line.separator}\

unconfiguration_metadatasrvn_summary_Windows_scripts_item.txt=<li>Shortcuts were removed.</li> ${line.separator}\

unconfiguration_metadatasrvn_summary_tail.txt=</ul>

# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#  updatePasswords target
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

updatePasswords_metadatasrvn_summary_head.txt=<h3>SAS Metadata Server</h3> ${line.separator}\
   <ul> ${line.separator}\

updatePasswords_metadatasrvn_summary_sasadm_item.txt=<li>The password for ${oma.person.admin.person.display.name} (${oma.person.admin.login.userid}) was changed in the ${oma.repository.foundation.name} repository.</li> ${line.separator}\

updatePasswords_metadatasrvn_summary_sastrust_item.txt=<li>The password for ${oma.person.trustusr.person.display.name} (${oma.person.trustusr.login.userid}) was changed in the ${oma.repository.foundation.name} repository.</li> ${line.separator}\

updatePasswords_metadatasrvn_summary_sasadm_script_item.txt=<li>The password for ${oma.person.admin.person.display.name} (${oma.person.admin.login.userid}) was changed in metaparms.sas. ${line.separator}\

updatePasswords_metadatasrvn_summary_mailsrv_item.txt=<li>The password for the E-mail Server Authentication User (${server.mailsrv.userid}) was changed in sasv9.cfg. ${line.separator}\

updatePasswords_metadatasrvn_summary_tail.txt=</ul>

# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
#  changeHost target
# = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

instructions_metadatasrvn_changeHost_manual_head.txt=<h4>Manual Instructions for SAS Metadata Server</h4> ${line.separator}\
<p>Warnings were encountered updating host name references. Review this section and correct any warnings reported.</p> ${line.separator}\
<ul> ${line.separator}\
  
instructions_metadatasrvn_changeHost_manual_tail.txt=</ul>
