Configuring IBM Content Navigator
After you update your Navigator to a container deployment, use the Navigator administration desktop to update settings for the container environment.
Procedure
To configure Navigator after moving to containers:
- 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.
- 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.
- Update the Sync Services URL:
- In the IBM Content Navigator administration desktop, click Sync Services.
- Update the default value for the public service URL. Note: If you are using container versions of the applications side-by-side with on-premises versions, you have the option to leave your Sync Services URL to the on-premises setting, or to change it to the public service URL.
- 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 cpe
service, for example, icp4a-cpe-svc:
- Log into the Navigator administration desktop.
- Open the Repositories view, select the FileNet P8 repository, and choose an action of edit.
- Modify the Server URL field to reflect the host and port values from the Administration Console for Content Platform Engine, for example: https://icp4a-cpe-svc/wsi/FNCEWS40MTOM
- Repeat this procedure for every FileNet P8 repository in the IBM Content Navigator configuration.
- Update custom plug-ins:
- 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
- Open the administration desktop in the web client.
- Click Plug-ins, choose the plug-in you want to update, and then click Edit.
- 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.
- Provide any additional configuration updates that the plug-in requires.
- Save your changes.
- 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:
- 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.