After a move to a container environment, you update your administrative settings to
account for the environment changes.
Procedure
To configure the Content Platform Engine after moving to containers:
- For any standard file store areas you have defined, edit the root path property to
reflect the mountPath as viewed from inside the container.
- Log in to the Administration Console for Content Platform Engine, and navigate to
- Choose the File Storage Area.
- On the Properties tab, edit the property Root
Directory path based on the Content Platform Engine filestore volume mapping to the
mountPath /opt/ibm/asa.
For example, if a file storage area exists
at /data/FMdomain_Marketing/FS1 and the Content Platform Engine filestore
volume claim is to /data/FMdomain_Marketing, the new value for the
Root Directory Path is opt/ibm/asa/FS1.
- Repeat these steps for every file storage area in the Content Cortex domain.
- For any advanced storage device that is defined as a file system storage device, edit the
advanced storage device root path.
- Log in to the Administration Console for Content Platform Engine, and navigate to
.
- Choose the Advanced Storage Device.
- On the Configuration tab, edit the value for Root
Directory path based on the Content Platform Engine filestore volume mapping to the
mountPath /opt/ibm/asa. For example, if an advanced storage device exists at
/data/FMdomain_Marketing/ASAD1 and the Content Platform Engine filestore volume
claim is to /data/FMdomain_Marketing, the new value for the Root
Directory Path will be /opt/ibm/asa/ASAD1.
- Repeat these steps for every advanced storage device in the Content Cortex domain.
What to do next
To configure Content Search Services, see topic Configuring Content Search Services.