<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Additional Information on</title><link>https://docs.protegrity.com/dsg/4.0.0.0/docs/dsg_appendix/</link><description>Recent content in Additional Information on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/dsg/4.0.0.0/docs/dsg_appendix/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating pepserver.cfg Settings to New Configuration Files</title><link>https://docs.protegrity.com/dsg/4.0.0.0/docs/dsg_appendix/dsg_migration_of_pepserver_file/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/dsg/4.0.0.0/docs/dsg_appendix/dsg_migration_of_pepserver_file/</guid><description>&lt;p>The &lt;em>pepserver.cfg&lt;/em> file is now deprecated. This section explains how its parameters are automatically migrated and handled in other configuration files.&lt;/p>
&lt;h2 id="parameter-migration-mapping">Parameter Migration Mapping&lt;/h2>
&lt;p>The following table details the migration of settings from &lt;em>pepserver.cfg&lt;/em> to new configuration files.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Deprecated Setting&lt;/th>
 &lt;th>New Parameter&lt;/th>
 &lt;th>Target Configuration File&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>policymanagement.shufflecodebooks&lt;/td>
 &lt;td>shuffle_codebook&lt;/td>
 &lt;td>bms_client.json&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>pkcs11.provider_library&lt;/td>
 &lt;td>BMS_PKCS11_LIBRARY&lt;/td>
 &lt;td>blobconfig.env&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>pkcs11.slot&lt;/td>
 &lt;td>BMS_PKCS11_SLOT&lt;/td>
 &lt;td>blobconfig.env&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>pkcs11.userpin&lt;/td>
 &lt;td>BMS_PKCS11_USERPIN_FILE&lt;/td>
 &lt;td>blobconfig.env&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>policymanagement.randomfile&lt;/td>
 &lt;td>BMS_RANDOM_FILE_PATH&lt;/td>
 &lt;td>blobconfig.env&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>ChrystokiConfigurationPath (dps.env)&lt;/td>
 &lt;td>ChrystokiConfigurationPath&lt;/td>
 &lt;td>blobconfig.env&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table></description></item><item><title>Updating the Host Details</title><link>https://docs.protegrity.com/dsg/4.0.0.0/docs/dsg_appendix/dsg_update_host_files/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/dsg/4.0.0.0/docs/dsg_appendix/dsg_update_host_files/</guid><description>&lt;h2 id="updating-the-host-details-of-dsg-on-the-esa-node">Updating the host details of DSG on the ESA node&lt;/h2>
&lt;p>Perform the following steps to update the host details of DSG on the the ESA node:&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Note the IP Address and FQDN of DSG.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>On the ESA CLI manager, go to &lt;strong>Administration &amp;gt; OS Console&lt;/strong>.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Edit the hosts file using the following commmand.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-fallback" data-lang="fallback">&lt;span style="display:flex;">&lt;span>nano /etc/ksa/hosts.append
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;/li>
&lt;li>
&lt;p>Add the IP Address and FQDN of DSG.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Run the following command.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-fallback" data-lang="fallback">&lt;span style="display:flex;">&lt;span>/etc/init.d/networking restart 
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;/li>
&lt;li>
&lt;p>Exit the command prompt.&lt;/p></description></item></channel></rss>