instructions_objectspawnr_start.txt=<h3><a name="Start your Object Spawner">Start the object spawner</a></h3> ${line.separator}\

instructions_objectspawnr_start_Windows.txt=<p>The Configuration Wizard created a shortcut in your Start menu at: Programs -&gt; SAS -&gt; Configuration -&gt; ${server.shortcut.folder.display.name} -&gt; <b>${spawner.objectspawnr.shortcut.start.name}</b>.</p>  ${line.separator}\

instructions_objectspawnr_start_Unix.txt=<p>Start the object spawner by executing the following command: </p> ${line.separator}\
  <p><strong>${config.lev.dir}/ObjectSpawner/ObjectSpawner.sh start</strong></p> ${line.separator}\

instructions_objectspawnr_start_verify_head.txt=<h4>Verify that the object spawner is working properly</h4> ${line.separator}\
${line.separator}\
<ul> ${line.separator}\
  <li>From the SAS Management Console toolbar, select <b>View -&gt; Refresh</b></li> ${line.separator}\
</ul>  ${line.separator}\

instructions_objectspawnr_start_verify_workspace.txt=<!--  start objectspawnr_start_verify_workspace.txt  --> ${line.separator}\
${line.separator}\
<p><b>Workspace Server</b></p> ${line.separator}\
${line.separator}\
<ol> ${line.separator}\
  <li>In the SAS Management Console, on the Plug-ins tab, select &quot;+&quot; to expand the Server Manager node. Fully expand all three levels of <strong>${oma.appserver.servercontext.name}</strong>.</li> ${line.separator}\
  <li>Highlight the lowest level, <strong>${oma.appserver.servercontext.name} - Workspace Server.</strong></li> ${line.separator}\
  <li>In the right hand view, you should see a single connection defined. Highlight that connection name, use the right mouse button and select <b>Test Connection...</b></li> ${line.separator}\
  <li>Enter a valid user ID and password, for example ${oma.person.demo.userid}, and select OK.</li> ${line.separator}\
  <li>You should see a Test Connection Successful message.</li> ${line.separator}\
</ol> ${line.separator}\


instructions_objectspawnr_start_verify_storproc.txt=<p><b>Stored Process Server</b></p> ${line.separator}\
${line.separator}\
<ol> ${line.separator}\
  <li>In the SAS Management Console, on the Plug-ins tab, select &quot;+&quot; to expand the Server Manager node. Fully expand all three levels of <strong>${oma.appserver.servercontext.name}</strong>.</li> ${line.separator}\
  <li>Highlight the lowest level, <strong>${oma.appserver.servercontext.name} - Stored Process Server</strong>.</li> ${line.separator}\
  <li>In the right hand view, you should see one connection defined with a Protocol of <b>Bridge</b>. Highlight that connection name, use the right mouse button and select <b>Test Connection...</b></li> ${line.separator}\
  <li>You should see a Test Connection Successful message.</li> ${line.separator}\
</ol> ${line.separator}\

instructions_objectspawnr_head.txt=<h3>${spawner.objectspawnr.name}</h3> ${line.separator}\

instructions_objectspawnr_head_migrated.txt=<h3>Object Spawner</h3> ${line.separator}\

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

instructions_objectspawnr_details_migrated_servers.txt=<tr> ${line.separator}\
      <td class="detailLabel">Servers Migrated</td> ${line.separator}\
      <td class="detailContent">${migrated.servers.names}</td> ${line.separator}\

instructions_objectspawnr_details_host.txt=<tr> ${line.separator}\
      <td class="detailLabel">Host machine</td> ${line.separator}\
      <td class="detailContent">${spawner.objectspawnr.host}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_details_port.txt=<tr> ${line.separator}\
      <td class="detailLabel">Port</td> ${line.separator}\
      <td class="detailContent">${spawner.objectspawnr.operator.port}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_details_ports.txt=<tr> ${line.separator}\
      <td class="detailLabel">Ports</td> ${line.separator}\
      <td class="detailContent">${migrated.servers.ports}</td> ${line.separator}\
   </tr> ${line.separator}\

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

instructions_objectspawnr_details_service_names.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Windows services ${line.separator}\
         <br class="br">${migrated.servers.services}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_objectspawnr_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">${config.lev.dir}${file.separator}${spawner.objectspawnr.config.dir.name}${file.separator}${spawner.objectspawnr.script.name}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_details_scripts_Windows_migrated.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Batch script ${line.separator}\
         <br class="br">${migrated.servers.script.names}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_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">${config.lev.dir}${file.separator}${spawner.objectspawnr.config.dir.name}${file.separator}${spawner.objectspawnr.script.name}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_details_scripts_Unix_migrated.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Shell script ${line.separator}\
         <br class="br">${migrated.servers.script.names}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_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_objectspawnr_details_logging.txt=<tr> ${line.separator}\
      <td class="detailLabel">Log directory</td> ${line.separator}\
      <td class="detailContent"><a href="${objectspawner.logs.dir}">${objectspawner.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/administration" target="_blank">http://support.sas.com/administration</a>.</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_details_log_dirs.txt=<tr> ${line.separator}\
      <td class="detailLabel">Log directories</td> ${line.separator}\
      <td class="detailContent"> ${migrated.servers.log.dirs} ${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/administration" target="_blank">http://support.sas.com/administration</a>.</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_start_Zos.txt=<tr> ${line.separator}\
      <td class="detailLabel">Started task</td> ${line.separator}\
      <td class="detailContent">${zos.high.level.qualifier}.${ENC2}.SRVPROC(${spawner.objectspawnr.stcname})</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_objectspawnr_started_tasks_Zos.txt=<tr> ${line.separator}\
      <td class="detailLabel">Started task</td> ${line.separator}\
      <td class="detailContent">${migrated.servers.stcnames}</td> ${line.separator}\
   </tr> ${line.separator}\

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

warnings_objectspawnr_services.txt=<li><b>WARNING:</b> One or more issues were encountered during the creation of the service <b>${spawner.objectspawnr.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_objectspawnr_shortcuts.txt=<li><b>WARNING:</b> One or more shortcuts for the object spawner 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_objectspawnr_seassignprimarytokenprivilege.set.txt=<li><p>You indicated that security policies could be modified by the SAS Deployment Wizard. As a result, the user <b>${os.localhost.userid}</b> was granted the local security policy <b>Replace a process level token (SeAssignPrimaryTokenPrivilege)</b>. This policy allows a user to initiate a process to replace the default token associated with a started subprocess and is needed by the object spawner when it spawns SAS Application Servers.</p> ${line.separator}\
<p>The policy will take effect the next time <b>${os.localhost.userid}</b> authenticates against the operating system.  Therefore, if <b>${os.localhost.userid}</b> is currently logged on to the system and has not previously had this seceurity policy applied to their account, a reboot will be needed so this user can make use of the object spawner.</p></li> ${line.separator}\

warnings_objectspawnr_seassignprimarytokenprivilege.noset.txt=<li><p>You indicated that security policies could not be modified by the SAS Deployment Wizard. As a result, the user <b>${os.localhost.userid}</b> has not been granted the local security policy <b>Replace a process level token (SeAssignPrimaryTokenPrivilege)</b>. This policy is required to use the object spawner to spawn SAS Application Servers and allows a user to initiate a process to replace the default token associated with a started subprocess.</p> ${line.separator}\
<p>To set this policy now, open the Local Security Policy application via the Control Panel (classic view): Administrative Tools &gt; <b>Local Security Policy</b> or the Control Panel (category view): Performance and Maintenance &gt; Administrative Tools &gt; <b>Local Security Policy</b>.  From the Local Security Policy application, select <b>Replace a process level token</b> and add the user <b>${os.localhost.userid}</b>.</p> ${line.separator}\
<p>The policy will take effect the next time <b>${os.localhost.userid}</b> authenticates against the operating system.  Therefore, if <b>${os.localhost.userid}</b> is currently logged on to the system, a reboot will be needed so this user can make use of the object spawner.</p></li> ${line.separator}\

warnings_objectspawnr_seassignprimarytokenprivilege.set.failed.txt=<li><p>You indicated that security policies could be modified by the SAS Deployment Wizard. However, an error occurred during the attempt to grant the user <b>${os.localhost.userid}</b> the local security policy <b>Replace a process level token (SeAssignPrimaryTokenPrivilege)</b>. This policy allows a user to initiate a process to replace the default token associated with a started subprocess and is needed by the object spawner when it spawns SAS Application Servers.</p> ${line.separator}\
<p>To attempt to set this policy now, open the Local Security Policy application via the Control Panel (classic view): Administrative Tools &gt; <b>Local Security Policy</b> or the Control Panel (category view): Performance and Maintenance &gt; Administrative Tools &gt; <b>Local Security Policy</b>.  From the Local Security Policy application, select <b>Replace a process level token</b> and add the user <b>${os.localhost.userid}</b>.</p> ${line.separator}\
<p>The policy will take effect the next time <b>${os.localhost.userid}</b> authenticates against the operating system.  Therefore, if <b>${os.localhost.userid}</b> is currently logged on to the system, a reboot will be needed so this user can make use of the object spawner.</p></li> ${line.separator}\

errors_objectspawnr_head.txt=<h3>SAS Object Spawner failed to deploy successfully</h3> ${line.separator}\

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

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

errors_objectspawnr_configDirExists.txt=<li><p>A config directory already exists for the object spawner. This indicates that you are attempting to add a second instance of the spawner or you are attempting to reconfigure the original spawner. You should either choose a unique spawner name to add an additional spawner instance or unconfigure the spawner before trying to reconfigure the spawner.</p></li>

errors_objectspawnr_validatePorts.txt=<li><p>SAS Object Spawner failed on host ${spawner.objectspawnr.host}, port ${spawner.objectspawnr.operator.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>Object spawner logs: <a href="${objectspawner.logs.dir}" type="text/plain" target="_blank">${objectspawner.logs.dir}</a></li>  ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_objectspawnr_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>Object spawner logs: <a href="${objectspawner.logs.dir}" type="text/plain" target="_blank">${objectspawner.logs.dir}</a></li>  ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_objectspawnr_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>Object spawner logs: <a href="${objectspawner.logs.dir}" type="text/plain" target="_blank">${objectspawner.logs.dir}</a></li>  ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_objectspawnr_loadMetadata.txt=<li><p>Information about the object spawner 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>Object spawner logs: <a href="${objectspawner.logs.dir}" type="text/plain" target="_blank">${objectspawner.logs.dir}</a></li>  ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_objectspawnr_installServices.txt=<li><p>The object spawner could not be installed as a service.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.command} exists</li> ${line.separator}\
      <li>${error.commandline} is correct</li> ${line.separator}\
   </ul></p> ${line.separator}\
</li>  ${line.separator}\

errors_objectspawnr_removeServices.txt=<li><p>The object spawner 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</li> ${line.separator}\
   </ul></p> ${line.separator}\
</li>  ${line.separator}\

warnings_objectspawnr_without_associated_servers.txt=<li><p>No server(s) are assigned to ${spawner.objectspawnr.servercomponent.name}. This spawner can not be started.</p></li> ${line.separator}\

errors_objectspawnr_startServer.txt=<li><p>No object spawner listener was detected on the specified host (${spawner.objectspawnr.host}) and port (${spawner.objectspawnr.operator.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>Object spawner logs: <a href="${objectspawner.logs.dir}" type="text/plain" target="_blank">${objectspawner.logs.dir}</a></li>  ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

unconfiguration_objectspawnr_summary_head.txt=<h3>SAS Object Spawner</h3> ${line.separator}\

unconfiguration_objectspawnr_summary_item.txt=<p>The object spawner was removed.</p> ${line.separator} \
   <ul> ${line.separator}\
      <li>${objectspawnr.configobj.name} was removed from metadata.</li> ${line.separator}\

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

unconfiguration_objectspawnr_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 Object Spawner could not be stopped and any configuration files in use could not be removed.  Please stop this executable (objspawn.exe) yourself via the Task Manager and remove any unwanted files.</li> ${line.separator}\

unconfiguration_objectspawnr_summary_tail.txt=</ul>

updatePasswords_objectspawnr_summary_head.txt=<h3>SAS Object Spawner</h3> ${line.separator}\
   <ul> ${line.separator}\

updatePasswords_objectspawnr_summary_sastrust_omrconfig_item.txt=<li>The password for ${oma.person.trustusr.person.display.name} (${oma.person.trustusr.login.userid}) was changed in ${spawner.objectspawnr.config.dir.name}${file.separator}${spawner.objectspawnr.omrconfig.file.name}. ${line.separator}\

updatePasswords_objectspawnr_summary_tail.txt=</ul>

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

instructions_objectspawnr_changeHost_manual_head.txt=<h4>Manual Instructions for SAS Object Spawner</h4>

instructions_objectspawnr_changeHost_manual_steps.txt=<ul><li>The SAS Object Spawner has been updated with new host name values. Manually start the SAS Object Spawner by issuing the command: <ul><li><b>${objectspawner.script} ${server.command.start.option}</b></li></ul></li></ul>

instructions_objectspawnr_changeHost_manual_steps_zos.txt=<ul><li>The SAS Object Spawner has been updated with new host name values. Manually start the SAS Object Spawner using one of the following methods: ${line.separator}\
  <ol>${line.separator}\
    <li>If you are running the spawner from the USS shell, issue the command: ${line.separator}\
      <ul>${line.separator}\
        <li><b>${objectspawner.script} ${server.command.start.option}</b></li>${line.separator}\
      </ul>${line.separator}\
    </li>${line.separator}\
    <li>If you are running the spawner as a started task, start the task <b>${spawner.objectspawnr.stcname}</b> from the start system command.</li>${line.separator}\
  </ol>${line.separator}\
</li></ul>${line.separator}\

warnings_objectspawnr_changeHost_shortcuts.txt=<ul><li><b>WARNING:</b> One or more shortcuts for the object spawner were not created. Verify the following: </li></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}\
