IBM Content Collector for SAP Applications parameters
Update the custom YAML file with the details of your Content Collector for SAP Applications deployment.
For a more focused YAML file that contains the default value for each Content Collector for SAP Applications parameter, see the iccsap_sample_cr.yaml file. You can use this shorter sample resource file to compile all the values you need for your Content Collector for SAP Applications environment, then copy the sections into the iccsap_v1_iccsap_cr_template.yaml file before you deploy.
The following is a list of Content Collector for SAP Applications configuration parameters:
| Parameters | Description | Default value | Required |
|---|---|---|---|
Replica count
|
Specify the number of Content Collector for SAP replicas to deploy. |
|
No |
Image
|
Specifies the image to be used. |
|
No |
Secrets
|
Contains information about the keystore password, the Transport Layer Socket (TLS)
certificate, and the Certificate Authority (CA) certificate. Set the TLS key if you have an external TLS certificate. Leave it empty if you do not have an external TLS certificate, and the operator generates one for you. Set the CA key if you have a CA to sign the external TLS certificate. Leave the parameter empty if you do not have the CA of your external TLS certificate, and the operator generates one for you. |
ibm-iccsap-secret {{ meta.name}}-iccsap-ext-tls-secret {{ meta.name}}-iccsap-auth-ca-secret |
No |
Log
|
The format for workload logging. |
|
No |
Resources > requests
|
|
|
No |
Resources > limits
|
|
|
No |
Auto scale
|
enabled: Specify whether to enable auto scaling. max_replicas: The upper limit for the number of pods that can be set by the autoscaler. min_replicas: The lower limit for the number of pods that can be set by the autoscaler. If it is not specified or negative, the server will apply a default value. target_cpu_utilization_percentage: The target average CPU utilization (represented as a percent of requested CPU) over all the pods. If it is not specified or negative, a default autoscaling policy is used. |
|
No |
Route public hostname
|
Provide a hostname that the operator uses to create an OpenShift route definition to access
the application, most often the host name of the infrastructure node in Open Shift. This parameter does not apply for non-OpenShift platforms. |
<hostname> | No |
|
iccsap_production_setting
|
The value must be set to 'accept' to deploy. |
accept |
No |
| Storage license dba_license |
The value must be set to 'accept' to deploy. |
accept |
No |
| License license |
The value must be set to 'accept' to deploy. | accept | No |
Run as user
|
User to run the deployment. If run_as_user is commented out, the deployment uses a UID auto-assigned by Open Shift. | No | |
| Logs PVC name datavolume
|
|
|
No |
probe > readiness
|
The behavior of readiness probes to know when the containers are ready to start accepting traffic. |
|
No |
probe > liveness
|
The behavior of liveness probes to know when to restart a container. |
600 5 5 6 |
No |
| iccsap_configuration.storage.size_for_logstore | Specify the size for Content Collector for SAP Applications log store. | 1Gi | |
| iccsap_configuration.storage.storage_class | Specify the storage class for Content Collector for SAP Applications log store persistent volume claim (PVC). | ||
node_affinity
|
Node affinity for the container. | Empty | No |
| custom_annotations | Specify the custom annotations. | Empty | No |
| custom_labels | Specify custom labels. | Empty | No |