instructions_workspacesrv_head.txt=<h3>${iomsrv.workspacesrv.name}</h3> ${line.separator}\

instructions_workspacesrv_head_migrated.txt=<h3>SAS Workspace Server</h3> ${line.separator}\

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

instructions_workspacesrv_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_workspacesrv_details_host.txt=<tr> ${line.separator}\
		<td class="detailLabel">Host machine</td> ${line.separator}\
		<td class="detailContent">${iomsrv.workspacesrv.host}</td> ${line.separator}\
	</tr> ${line.separator}\

instructions_workspacesrv_details_port.txt=<tr> ${line.separator}\
		<td class="detailLabel">Port</td> ${line.separator}\
		<td class="detailContent">${iomsrv.workspacesrv.port}</td> ${line.separator}\
	</tr> ${line.separator}\

instructions_workspacesrv_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_workspacesrv_details_logging.txt=<tr> ${line.separator}\
		<td class="detailLabel">Log directory</td> ${line.separator}\
		<td class="detailContent"><a href="${workspacesrv.logs.dir}">${workspacesrv.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_workspacesrv_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_workspacesrv_details_validation_header.txt=<tr> ${line.separator}\
		<td class="detailLabel">Validation steps</td> ${line.separator}\
		<td class="detailContent">${line.separator}\
			<ol> ${line.separator}\

instructions_workspacesrv_details_validation.txt=\
  				<li>In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node.</li> ${line.separator}\
  				<li>Expand ${oma.appserver.servercontext.name}.</li> ${line.separator}\
  				<li>Highlight the  ${iomsrv.workspacesrv.logical.name}.</li> ${line.separator}\


instructions_replicationworkspacesrv_details_validation.txt=<tr> ${line.separator}\
		<td class="detailLabel">Validation steps</td> ${line.separator}\
		<td class="detailContent">The ${iomsrv.workspacesrv.name} should be used for only a few designated administrative tasks. It is appropriate to defer validation of this server until you have set up the SAS users who will perform these tasks. This server requires an external account and is available to only the SAS Administrators group. ${line.separator}\

instructions_workspacesrv_details_validation_migrated.txt=\
			        <li>In the SAS Management Console, select "${migrated.server.repository.name}" repository.</li> ${line.separator}\
			        <li>On the Plug-ins tab, select "+" to expand the Server Manager node.</li> ${line.separator}\
  				<li>Expand ${migrated.servers.server.context}.</li> ${line.separator}\
  				<li>Highlight the ${migrated.servers.logical.server}.</li> ${line.separator}\

instructions_workspacesrv_details_validation_sasdemo.txt=<li>Right mouse click this server and select Validate (you can enter ${oma.person.demo.login.userid} for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_workspacesrv_details_validation_sassrv.txt=<li>Right mouse click this server and select Validate (you can enter the SAS Spawned Servers account for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_workspacesrv_details_validation_sasdemosassrv.txt=<li>Right mouse click this server and select Validate (you can enter ${oma.person.demo.login.userid} or the SAS Spawned Servers account for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_workspacesrv_details_validation_novaliduser.txt=<li>Right mouse click this server and select Validate. You can enter a user ID and password that meet all of these requirements: ${line.separator}\
	<ol> ${line.separator}\
		<li>the account is known to the host of the standard workspace server. (An ID that ends in @saspw does not meet this requirement.)</li> ${line.separator}\
		<li>the account has the Windows right Log on as a batch job (if the server is on Windows).</li> ${line.separator}\
		<li>the account has a corresponding metadata identity.</li> ${line.separator}\
	</ol> ${line.separator}\
You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_workspacesrv_details_validation_migrated_1.txt=<br> ${line.separator}\
		<br> Repeat all the above steps for the following servers\
		<br><table border=1><tr><th>Repository </th><th>Server Context</th><th> Logical Server</th></tr>\
		${migrated.servers.pairs}</table>\


instructions_workspacesrv_details_validation_tail.txt=</ol> ${line.separator}\
		</td> ${line.separator}\
	</tr>  ${line.separator}\

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

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

instructions_workspacesrv_details_log4sas.txt=<li>The ${workspacesrv.logs.dir} directory is intended to serve as a placeholder for workspace server logs. Workspace server logs may be directed to this directory in the event that your SAS or IT administrator enables logging. The following default attributes are associated with the Logs directory: ${line.separator}\
		<ul> ${line.separator}\
			<li>Universal read, write or execute access is disabled for the directory in order to comply with default installation security requirements</li> ${line.separator}\
			<li>Execution of a workspace server does not populate the Logs directory</li> ${line.separator}\
			<li>The Logs directory serves as a placeholder should you enable logging for workspace servers</li> ${line.separator}\
		</ul> ${line.separator}\
		<br class="br">Enabling workspace server logging should be carefully considered, due to the proliferation of workspace server logs, as well as the requirement to grant universal write access to the Logs directory.  To enable workspace server logging, perform the following steps: ${line.separator}\
		<ul> ${line.separator}\
			<li>Enable read, write and execute access to the Logs directory</li> ${line.separator}\
			<li>Modify the workspace server logconfig.xml to enable the desired levels of logging</li> ${line.separator}\
			<li>Alternatively, enable the logconfig.trace.xml logging file to capture workspace server diagnostic logging</li> ${line.separator}\
		</ul> ${line.separator}\
</li>${line.separator}\

instructions_workspacesrv_details_log4sas_migrated.txt=<li>The directory or directories shown above are intended to serve as a placeholder for workspace server logs. These logs may be directed here in the event that your SAS or IT administrator enables logging. The following default attributes are associated with a given Logs directory: ${line.separator}\
		<ul> ${line.separator}\
			<li>Universal read, write or execute access is disabled for the directory in order to comply with default installation security requirements</li> ${line.separator}\
			<li>Execution of a workspace server does not populate the Logs directory</li> ${line.separator}\
			<li>The Logs directory serves as a placeholder should you enable logging for workspace servers</li> ${line.separator}\
		</ul> ${line.separator}\
		<br class="br">Enabling workspace server logging should be carefully considered, due to the proliferation of workspace server logs, as well as the requirement to grant universal write access to a given Logs directory.  To enable workspace server logging, perform the following steps: ${line.separator}\
		<ul> ${line.separator}\
			<li>Enable read, write and execute access to the Logs directory</li> ${line.separator}\
			<li>Modify the workspace server logconfig.xml to enable the desired levels of logging</li> ${line.separator}\
			<li>Alternatively, enable the logconfig.trace.xml logging file to capture workspace server diagnostic logging</li> ${line.separator}\
		</ul> ${line.separator}\
</li>${line.separator}\

instructions_workspacesrv_details_unix_iwa.txt=<li>In order to use Integrated Windows Authentication (IWA) for servers on UNIX, additional configuration is required.  Please see the "Configuring Integrated Windows Authentication" chapter in the <i>Configuration Guide for SAS Foundation for UNIX Environments</i>, located at <a href="http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf" target="blank">http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf</a>.</li> ${line.separator}

instructions_workspacesrv_details_restartspawner.txt=<li>Restart the object spawner so that it can be associated with the new workspace server.</li>  ${line.separator}\

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

warnings_workspacesrv_setbatchloginright.set.txt=<li><p>You indicated that security policies could be modified by the SAS Deployment Wizard. As a result, the user ${oma.person.demo.login.userid} was granted the local security policy <b>Log on as a batch job (SeBatchLogonRight)</b>. This policy allows a user to be logged on by means of a batch-queue facility and is required when this account is used with ${iomsrv.workspacesrv.name}.</p> ${line.separator}\
<p>The policy will take effect the next time ${oma.person.demo.login.userid} authenticates against the operating system.  Therefore, if ${oma.person.demo.login.userid} is currently logged on to the system, a reboot will be needed for this policy to take effect.</p></li> ${line.separator}\

warnings_workspacesrv_setbatchloginright.noset.txt=<li><p>You indicated that security policies could not be modified by the SAS Deployment Wizard. As a result, the user ${oma.person.demo.login.userid} has not been granted the local security policy <b>Log on as a batch job (SeBatchLogonRight)</b>. This policy is required when this account is used with ${iomsrv.workspacesrv.name} and allows a user to be logged on by means of a batch-queue facility.</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>Log on as a batch job</b> and add the user ${oma.person.demo.login.userid}.</p> ${line.separator}\
<p>The policy will take effect the next time ${oma.person.demo.login.userid} authenticates against the operating system.  Therefore, if ${oma.person.demo.login.userid} is currently logged on to the system, a reboot will be needed for this policy to take effect.</p></li> ${line.separator}\

warnings_workspacesrv_setbatchloginright.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 ${oma.person.demo.login.userid} the local security policy <b>Log on as a batch job (SeBatchLogonRight)</b>. This policy allows a user to be logged on by means of a batch-queue facility and is required when this account is used with ${iomsrv.workspacesrv.name}.</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>Log on as a batch job</b> and add the user ${oma.person.demo.login.userid}.</p> ${line.separator}\
<p>The policy will take effect the next time ${oma.person.demo.login.userid} authenticates against the operating system.  Therefore, if ${oma.person.demo.login.userid} is currently logged on to the system, a reboot will be needed for this policy to take effect.</p></li> ${line.separator}\


errors_workspacesrv_head.txt=<h3>SAS Workspace Server failed to deploy successfully</h3> ${line.separator}\

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

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

errors_workspacesrv_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}\		
	</ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_workspacesrv_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}\		
	</ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_workspacesrv_loadMetadata.txt=<li><p>Information about the workspace server 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}\
	</ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_workspacesrv_loadmetadata.init.txt=<li><p>Information about the workspace server 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}\
	</ul></p>  ${line.separator}\
</li>  ${line.separator}\

unconfiguration_workspacesrv_summary_head.txt=<h3>SAS Workspace Server</h3> ${line.separator}\

unconfiguration_workspacesrv_summary_item.txt=<p>The workspace server was removed.</p> ${line.separator} \
   <ul> ${line.separator}\
      <li>${workspacesrv.configobj.name} was removed from metadata.</li> ${line.separator}\
   </ul> ${line.separator}
