After you deploy the container images for Content Platform Engine and Content Search
Services, you modify the existing FileNet® P8 domain
configuration to incorporate the newly deployed Content Search Service services.
Procedure
To prepare Content Platform Engine to work with Content Search Services:
- Obtain the configuration details for the new CSS services in the container
deployment:
- Use the following command to get a list of all the pods, and determine the pod name for your CSS
server deployment:
kubectl get pod
- From the command line, use your CSS pod name and run the following
command:
kubectl exec -it pod pod_name bash
- From the command line, change to the
/opt/IBM/ContentSearchServices/CSS_Server/bin directory, and run the following
command to get the authentication
token:
./configTool.sh printToken -configPath ../config
Make a note of the
token so you can use it during the configuration.
- Exit out of the pod.
- From the command line, run the following command to get information about the
pod:
kubectl describe pod pod_name
Make a note of the IP
and port (8199) so you can use it during the configuration.
- Configure a text search server for each IBM Content Search Services deployment by navigating to , and complete the wizard:
Server state:
- Ensure all Content Search Services servers in the containerized environment are configured for
Dual: IndexAndSearch
mode.
Communication security:
- Check Enable use of the Secure Socket Layer (SSL) protocol.
- Uncheck Validate the SSL server certificate and Validate the
SSL certificate host.
Server association:
- Set the Affinity Group value to the same affinity group that is set for
your existing on-premises CSS server.
- Save the server settings.
- Repeat the preceding steps for all the newly deployed Content Search Service
services.