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

instructions_dproserver_details_host.txt=<tr> ${line.separator}\
      <td class="detailLabel">Host machine</td> ${line.separator}\
      <td class="detailContent">${server.dproserver.host}</td> ${line.separator}\
   </tr> ${line.separator}\
   <tr> ${line.separator}\
      <td class="detailLabel">Port</td> ${line.separator}\
      <td class="detailContent">${server.dproserver.port}</td> ${line.separator}\
   </tr> ${line.separator}\

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

instructions_dproserver_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">${dproserver.script}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_dproserver_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">${dproserver.script}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_dproserver_details_scripts_Zos.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Started task ${line.separator}\
         <br class="br">Copy DeploymentTesterServer.jcl to your started task procedure library, for example <br class="br">\
         cp ${dpro.config.dir}/DeploymentTesterServer.jcl "//'SYS1.PROCLIB(SASDTSVR)'"</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_dproserver_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_dproserver_details_logging.txt=<tr> ${line.separator}\
      <td class="detailLabel">Log directory</td> ${line.separator}\
      <td class="detailContent"><a href="${dproserver.logs.dir}">${dproserver.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_dproserver_details_validation_steps.txt=<tr> ${line.separator}\
      <td class="detailLabel">Validation steps</td> ${line.separator}\
      <td class="detailContent"><ol> ${line.separator}\
			<li>In SAS Management Console, on the Plug-ins tab, select "+" to expand the Application Management node.</li>${line.separator}\
			<li>Select "+" to expand Deployment Tester</li>${line.separator}\
			<li>Highlight the host machine: ${server.dproserver.host}</li> ${line.separator}\
			<li>Right mouse click and select Run All Test Suites.</li>  ${line.separator}\
			<li>Select "+" to expand the Results.</li>  ${line.separator}\
			<li>Validate the results for each test suite.  All tests should pass.</li> ${line.separator}\
		</ol> ${line.separator}\
          If you are prompted for credentials, select the "Help" button in the Credentials dialog box to display the accounts that can be used for each test \
          suite.${line.separator}\
	  </td> ${line.separator}\
   </tr>  ${line.separator}\

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


instructions_dproserver_details_notes_head.txt=<h4>Notes:</h4> ${line.separator}\
<ul> ${line.separator}\
<li>Deployment Tester Server is used to run tests on SAS products and servers to validate functionality and proper operation. ${line.separator}\
The Deployment Tester Server in conjunction with the Deployment Tester SASMC plug-in allows for tests to be executed on remote ${line.separator}\
systems from a single SASMC instance.</li>${line.separator}\
<li>When you are done validating your deployment with SAS Deployment Tester, the Deployment Tester Server can safely be ${line.separator}\
shut down without affecting the rest of your SAS deployment.  Deployment Tester Server is a stand-alone server, ${line.separator}\
independent of the rest of SAS, that can be started and used periodically to verify the health of your SAS deployment.  You should ${line.separator}\
consider verifying the health of your SAS deployment after initial installation, after applying maintenance and hot fixes, or ${line.separator}\
when you make any other significant changes to the deployment.</li>${line.separator}\
<li>More detailed information on validating your SAS deployment with Deployment Tester can be found in the ${line.separator}\
"Using the Deployment Tester" section of the SAS 9.4 Intelligence Platform: System Administration Guide, which is available at ${line.separator}\
<a href="http://support.sas.com/94administration">http://support.sas.com/94administration</a>.<p></li>${line.separator}\

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

warnings_dproserver_services.txt=<li>One or more issues were encountered during the creation of the service <b>${dproserver.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_dproserver_shortcuts.txt=<li>One or more shortcuts for the Deployment Tester 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}\
  
warnings_dproserver_junit.txt=<li><p>You did not specify the location of the JUnit jar file for Deployment Tester during installation and configuration.  ${line.separator}\
Deployment Tester tests other products that use JUnit for validation.  Without JUnit these products may operate properly, but you will not be able to validate them using Deployment Tester.<br class="br"><br class="br"> ${line.separator} \
The JUnit jar is available from the <a href="http://support.sas.com/resources/thirdpartysupport/index.html">Third Party Software Requirements Web page</a>. <br class="br"><br class="br">${line.separator}\
Place the JUnit jar in this location: <b>${dproserver.junitlocation}</b> </p></li>${line.separator}\

warnings_dproserver_jre.txt=<li><p>You did not specify a value for the Java Runtime Environment (JRE). ${line.separator}\
The Deployment Tester Server requires a JRE to run.  To enable the Deployment Tester server, edit the script ${line.separator}\
${dproserver.script} and replace the text "@java.jre.command@" with the path to the java executable.</p></li>${line.separator}\


errors_dproserver_head.txt=<h3>SAS Deployment Tester Server failed to deploy successfully</h3> ${line.separator}\

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

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

errors_dproserver_validatePorts.txt=<li><p>The requested port (${server.dproserver.port}) is in use on the specified host (${server.dproserver.host}). ${line.separator}\
   <ul>  ${line.separator}\
      <li>Error log file: <a href="file://${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_dproserver_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="file://${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_dproserver_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="file://${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

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

errors_dproserver_installShortcuts.txt=<li><p>SAS Deployment Tester 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_dproserver_installServices.txt=<li><p>The SAS Deployment Tester 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_dproserver_removeServices.txt=<li><p>The SAS Deployment Tester 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_dproserver_startDproServer.txt=<li><p>The SAS Deployment Tester Server could not be started and no listener was detected on the specified host (${server.dproserver.host}) and port (${server.dproserver.port}). ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="file://${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
   </ul> ${line.separator}\
</li>  ${line.separator}\

errors_dproserver_restartDproServer.txt=<li><p>The SAS Deployment Tester Server could not be restarted and no listener was detected on the specified host (${server.dproserver.host}) and port (${server.dproserver.port}). ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="file://${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
   </ul> ${line.separator}\
</li>  ${line.separator}\

unconfiguration_dproserver_summary_head.txt=<h3>SAS Deployment Tester Server</h3> ${line.separator}\

unconfiguration_dproserver_summary_item.txt=<p>The Deployment Tester Server was removed.</p> ${line.separator} \
	<ul> ${line.separator}\
		<li>${dproserver.configobj.name} was removed from metadata.</li> ${line.separator} \

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

unconfiguration_dproserver_summary_Windows_scripts_item.txt=<li>Shortcuts were removed.</li> ${line.separator}\
      <li>Because you selected to run as management scripts, the executable for the SAS Deployment Tester Server could not be stopped and any configuration files in use could not be removed.  Please stop this application (SAS Deployment Tester Server - Port ${server.dproserver.port}) yourself via the Task Manager and remove any unwanted files.</li> ${line.separator}\

unconfiguration_dproserver_summary_tail.txt=</ul>

#=============================================================
#  changeHost target
#=============================================================
instructions_dproserver_changeHost_manual_head.txt=<h4>Manual Instructions for SAS Deployment Tester Server</h4> ${line.separator}<p>${line.separator}\

instructions_dproserver_changeHost_manual_steps.txt=${line.separator}\
	<ul>${line.separator}\
		<li>The SAS Deployment Tester Server has been updated with new host name values. ${line.separator}\
			Manually start the SAS Deployment Tester Server by issuing the command: <br> ${line.separator} \
			<b>${dproserver.script} ${server.command.start.option}</b></li> ${line.separator}\
	</ul> ${line.separator}\

warnings_dproserver_changeHost_shortcuts.txt=${line.separator}\
	<ul>${line.separator}\
		<li><b>WARNING:</b> One or more shortcuts for the Deployment Tester Server were not created. Verify the following: </li> ${line.separator}\
	</ul> ${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}\ 
