Storing Workbench Credentials in OCS

The last-mile-crawl.xml file by default specifies that Workbench credentials are to be stored in OCS.

To create Dgidx-compatible data and load it into the Dgidx pipeline, a baseline update runs a crawl named the last mile crawl. By default, last-mile-crawl.xml specifies that Workbench credentials are to be stored in OCS.

Oracle recommends that all credentials be stored in OCS for all new applications, and that they be stored in clear text only for backward compatibility.

Storage of Workbench credentials in OCS is enabled by the following lines in last-mile-crawl.xml: 

<moduleProperty>
  <key>JpsConfigPath</key>
  <value>D:\Endeca\TF\ToolsAndFrameworks\11.2.0\server\workspace\credential_store\jps-config.xml</value>
</moduleProperty>
<moduleProperty>
  <key>OcsMapName</key>
  <value>endecaToolsAndFrameworks</value>
</moduleProperty>
<moduleProperty>
  <key>OcsKeyName</key>
  <value>ifcr</value>
</moduleProperty>

To store Workbench credentials in clear text, comment out the lines in the example immediately above and uncomment the following lines: 

<moduleProperty>
 <key>configRepositoryUserName</key>
 <value>admin</value>
</moduleProperty>
<moduleProperty>
 <key>configRepositoryPassword</key>
 <value>admin</value>
</moduleProperty>

Before you run the run the last mile crawl, you must complete two additional steps:

  1. Copy the credential_store folder from %ENDECA_TOOLS_ROOT% location and jps-config.xml from %ENDECA_TOOLS_ROOT%\server\workspace\credential_store to any location in CAS.

  2. Run the manage_credentials.bat|sh utility to store the workbench credentials in OCS using the following command: 

    manage_credentials.bat add --config D:\temp\jps-config.xml --key ifcr

    For information on using the manage_credentials.bat utility, see the Oracle Commerce Guided Search Administrator's Guide.

Example 1. 


Copyright © Legal Notices