Completing post-installation tasks for Navigator

If you included Navigator in your container deployment, you must do some additional configuration to ensure that the application works with your content services environment.

About this task

After you deploy your Navigator container, use the Navigator administration console to update settings for the container environment.

Procedure

  1. Update the security settings on the Content Platform Engine domain so that Navigator users can access it:
    1. Log in to the Administration Console for Content Platform Engine.
    2. From the navigation pane, open the domain for editing.
    3. Click the Security tab.
    4. Click Add User/Group Permissions.
    5. Add #ALL-AUTHENTICATED to the domain, with the following settings:
      • Source: Direct
      • Permission Type: Allow
      • Permission Group: Custom, with View all properties, Modify all properties, Read permissions, and Modify permissions enabled.
      • Apply to: This Object and Immediate Children
  2. Add the Daeja® Viewer license files to the configuration overrides directory for Navigator.
    For example, icn-cfgstore-pv/configDropins/overrides.
  3. Update the Daeja Viewer log file path, if necessary.
    The default log file is icn-logstore-pv/logs/daeja.log. Confirm that the path is updated to reflect your container deployment location.

    For example: /opt/ibm/viewerconfig/logs/daeja.log.

  4. Update the Sync Services URL:
    1. In the Navigator administration tool, click Sync Services.
    2. Update the default value for the public service URL.
      The URL must include the server IP address and port for the environment.

      For example: http://IP_Address:30557/sync/notify.

  5. (Optional) Improve security for session cookies by adding httpSession configuration to your overrides directory.
    Create an XML file (for example, zHTTPsession.xml) with the following content:
    <server>
       <httpSession
        cookieName="JSESSIONID"
        cookieSecure="true"
        cookieHttpOnly="true"
        cookiePath="/"
       >
       </httpSession>
    </server>
    Note: Some Navigator features are affected by this setting:
    Applets
    The cookieHttpOnly=“true” setting can cause applets to fail. If you plan to use applets, remove this entry from the XML file. Or you can use the HTML-based solution, such as the HTML step processor.
    Additional Navigator features
    For information on what features are affected by this setting and possible mitigation, see the following information in the IBM Documentation for Content Navigator.
  6. (Optional) If needed, change the Navigator mode.
    Navigator has two modes:
    • Platform mode ( mode 1) displays BA Studio applications.
    • Platform and Content (mode 2) displays Navigator features as well as BA Studio applications.

    To change the setting, in the Navigator admin desktop, go to Settings > General tab, and use the radio options to update the Platform Mode setting.