Consider the following information as you record the values for your
deployment environment in the CR file:
- Shared configuration settings
-
Un-comment and update the values for the shared configuration, LDAP, datasource, monitoring, and
logging parameters, as applicable.
Remember: Set shared_configuration.sc_deployment_platform to
other if you are deploying on a non-OpenShift certified Kubernetes platform.
Use the secrets that you created for the root_ca_secret and
trusted_certificate_list values.
Remember: If you plan to use External Share with the 2 LDAP model for configuring
external users, update the LDAP values in the ext_ldap_configuration section of the
YAML file with the information about the directory server that you configured for external users. If
you are not using the 2 LDAP model of external share, leave this section commented out.
Important: If you are using Oracle pluggable databases, you must update the default
value for the
dc_os_datasources.database_name parameter in the
shared_configuration section. This value must be a single-word name and cannot be a
DNS name like mydb.engineering.ibm.com. For example, instead of
mydb.engineering.ibm.com, an invalid database name for this parameter, use
mydb, which is a valid database name value for the parameter.
Then, confirm that
your value for the dc_oracle_os_jdbc_url parameter contains your full database DNS
name, for example,
jdbc:oracle:thin:@//myhostname.ibm.com:1521/mydb.engineering.ibm.com.
For more information about the shared parameters, see the following topics:
- Content Platform Engine settings
-
Use the cpe section of the custom YAML to provide values for the configuration
of Content Platform Engine. You provide details for configuration settings that you have already
created, like the names of your persistent volume claims. You also provide names for pieces of your
Content Platform Engine environment, and tuning decisions for your runtime environment.
For more information about the settings, see Content
Platform Engine parameters
- Content Search Services settings
-
Use the css section of the custom YAML to provide values for the configuration
of Content Search Services. You provide details for configuration settings that you have already
created, like the names of your persistent volume claims. You also provide names for pieces of your
Content Search Services environment, and tuning decisions for your runtime environment.
For more information about the settings, see Content
Search Services parameters
- Content Management Interoperability Services settings
-
Use the cmis section of the custom YAML to provide values for the configuration
of Content Search Services. You provide details for configuration settings that you have already
created, like the names of your persistent volume claims. You also provide names for pieces of your
Content Search Services environment, and tuning decisions for your runtime environment.
For more information about the settings, see Content
Management Interoperability Services parameters
- Content Services GraphQL settings
-
Use the graphql section of the custom YAML to provide values for the
configuration of the Content Services GraphQL API. You provide details for configuration settings
that you have already created, like the names of your persistent volume claims. You also provide
names for pieces of your Content Services GraphQL environment, and tuning decisions for your runtime
environment.
The section includes a parameter for enabling the GraphiQL development interface. Note the
following consideration for including GraphiQL in your environment:
- If you are deploying the GraphQL container as part of a test or development environment and you
want to use GraphiQL with the API, set the
enable_graph_iql parameter to true.
- If you are deploying the GraphQL container as part of a production environment, it is
recommended to set the
enable_graph_iql parameter to false.
For more information about the settings, see Content
Services GraphQL parameters
- External Share settings
-
Use the es section of the custom YAML to provide values for the configuration of
External Share. You provide details for configuration settings that you have already created, like
the names of your persistent volume claims. You also provide names for pieces of your External Share
environment, and tuning decisions for your runtime environment.
Remember: If you are using the 2 LDAP approach for managing your external users for
external share, you must configure the ext_ldap_configuration section in the shared parameters with
information about your external user LDAP directory service.
Remember: If you are deploying the External Share container as an update instead of as
part of the initial container deployment, note that both the Content Platform Engine and the
Business Automation Navigator containers will undergo a rolling update to accommodate the External
Share configuration.
For more information about the settings, see External
Share parameters
For more information about settings for an OIDC/OAuth provider, see Identity
provider parameters.
- Task Manager parameters
-
Use the tm section of the custom YAML to provide values for the configuration of
Task Manager. You provide details for configuration settings that you have already created, like the
names of your persistent volume claims. You also provide names for pieces of your Task Manager
environment, and tuning decisions for your runtime environment.
New in 20.0.3 You can also remotely load JAR
files containing job implementations with the TM_JOB_URL parameter in the
tm_production_setting section of the YAML file.
If you want to deploy Task Manager, you must also deploy IBM Business Automation Navigator. The Task Manager uses the same database as IBM Business Automation Navigator. Database settings must match between these two components.
For Task Manager, pay particular attention to any relevant values in the
jvm_customize_options parameter.
For more information about the settings, see Task
Manager parameters
- Initialization settings
-
Use the initialize_configuration section of the custom YAML to provide values for the automatic initialization and setup of Content Platform Engine and IBM Business Automation Navigator. The initialization container creates initial instances of your FileNet Content Manager components, such as the P8 Domain, one or more object stores, and configuration of IBM Business Automation Navigator. You also provide names for pieces of your FileNet Content Manager environment, and make decisions for your runtime environment.
Remember: If you want to enable the content event emitter on your object store, use the
following
setting:
ic_obj_store_creation:
object_stores:
oc_cpe_obj_store_enable_content_event_emitter: true
Important: If you are using the initialization capability as part of your Automation
Document Processing deployment, leave the value for the following parameter
empty:
oc_cpe_obj_store_basic_user_groups:
You can edit the YAML to configure more than one of the available pieces in your automatically
initialized environment. For example, if you want to create an additional Content Search Services
server, you copy the stanza for the server settings, paste it below the original, and add the new
values for your additional object store:
ic_css_creation:
# - css_site_name: "Initial Site"
# css_text_search_server_name: "{{ meta.name }}-css-1"
# affinity_group_name: "aff_group"
# css_text_search_server_status: 0
# css_text_search_server_mode: 0
# css_text_search_server_ssl_enable: "true"
# css_text_search_server_credential: "RNUNEWc="
# css_text_search_server_host: "{{ meta.name }}-css-svc-1"
# css_text_search_server_port: 8199
You can create additional object stores, Content Search Services indexes, IBM Business Automation Navigator repositories, and IBM Business Automation Navigator desktops.
For more information about the settings, see Initialization parameters
- Verification settings
-
Use the verify_configuration section of the custom YAML to provide values for the automatic verification of your Content Platform Engine and IBM Business Automation Navigator. The verify container works in conjunction with the automatic setup of the initialize container. You can accept most of the default settings for the verification. However, compare the settings with the values that you supply for the initialization settings. Specific settings like object store names and the Content Platform Engine connection point must match between these two configuration sections.
For more information about the settings, see Verify
parameters