Configuring Business Automation Navigator

After you update your Navigator to a container deployment, use the Navigator administration desktop to update settings for the container environment.

To configure Navigator after moving to the Cloud Pak:

1. Add the Daeja®® Viewer license files to the configuration overrides directory for Business Automation Navigator.
   For example, /opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides.
2. Update the Daeja Viewer log file path, if necessary.
   The default log file in the on-premises system before upgrade is install_dir/ibm/viewerconfig/logs/daeja.log, where install_dir is the directory where Navigator is installed. Update the path to reflect your container deployment location, for example, /opt/ibm/viewerconfig/logs/daeja.log.
3. Update the Sync Services URL:
   1. In the IBM Content Navigator administration desktop, click Sync Services.
   2. Update the default value of the public service URL to use the Navigator service URL, for example: https://$deployment_name-navigator-svc:9443/sync/notify.
      Note: If you are using container versions of the applications side by side with on-premises versions, you can leave your Sync Services URL to the on-premises setting, or change the public service URL to use the Navigator service URL.
4. For any Navigator instance that references a FileNet®® P8 repository that is managed by a container deployment of Content Platform Engine, modify the server URL value to incorporate the Content Platform Engine service, for example, icp4a-cpe-svc:
   1. Log in to the Navigator administration desktop.
   2. Open the Repositories view, select the FileNet P8 repository, and choose an action of edit.
   3. Modify the Server URL field to reflect the host and port values from the Administration Console for cpe stateless service endpoint, for example: https://icp4adeploy-cpe-stateless-svc.cp4ba.svc:9443/wsi/FNCEWS40MTOM. The cp4ba namespace is where CP4BA is deployed.
   4. To determine the correct stateless CPE service endpoint, run the following command:

      $ oc get svc | grep cpe-stateless
        icp4adeploy-cpe-stateless-svc

   5. Repeat this procedure for every FileNet P8 repository in the IBM Content Navigator configuration.
5. Update custom plug-ins:
   1. Copy the IBM Content Navigator plug-in files from your on-premises location to the /opt/ibm/plugins path in the IBM Content Navigator volume:

      podname=$(oc get pod | grep navigator pod name | awk '{print $1}')
      kubectl cp path to plugin files NAMESPACE/$podname:/opt/ibm/plugins

   2. Open the administration desktop in the web client.
   3. Click Plug-ins, choose the plug-in you want to update, and then click Edit.
   4. Reload the plug-in from the new path in the IBM Content Navigator volume.
      The plug-in file must be in the /opt/ibm/plugins path in the volume.
   5. Provide any additional configuration updates that the plug-in requires.
   6. Save your changes.
6. Add the master encryption key from your old environment to your new environment.
   In the configDropins/overrides volume for Navigator, replace the master encryption key file with extension .ika with the master encryption key file from the traditional WebSphere® Application Server environment.