8 Configuring Parameters in Helm Charts
This chapter lists and describes the parameters in the Helm charts.
- aia-comms-pv-pvc: This chart creates AIA PV/PVCs and service accounts.
- aia-comms-deploy-aiapip: This chart deploys AIA Foundation Pack and AIA Pre-integrated Packs (PIPs) in SOA and WebLogic servers.
- aia-comms-certs: This chart manages SSL trust certificates of Siebel and OSM in SOA and WebLogic servers.
The charts pick the customized values defined in the custom values.yaml configuration file and map them to the respective Kubernetes yaml files defined in the chart`s /template directory. Each chart can be installed and managed through helm commands.
Global Parameters
Table 8-1 lists the parameters that you configure globally. These are available in the $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/values.yaml file.
Table 8-1 Global Parameters
| Parameter | Description |
|---|---|
| image | AIA Docker image. |
| imagePullPolicy | AIA Docker image pull policy. Valid values are IfNotPresent, Always, Never. |
| containerPort | Kubernetes container port for the kubernetes job to be triggered. |
| namespace | Kubernetes namespace in which domain is created. |
| domainUID | Unique ID that is used to identify this particular domain where AIA needs to be installed. |
| domainName | Unique name that is used to identify this particular domain where AIA needs to be installed. |
| weblogicCredentialsSecretName | Name of the Kubernetes secret for the Administration Server’s user name and password. |
| persistentVolumeClaimName | Name of the persistent volume claim created to host the domain home. |
| domainPVMountPath | Mount path of the domain persistent volume. |
| soaClusterName | Name of the SOA WebLogic Server cluster instance generated for the domain. |
| adminServerName | Name of the Administration Server. |
| adminServerNameSvc |
Name of the Administration Server Base Service. This can be found in create-domain-job.yaml of output folder specified during domain creation. |
| adminPort | Port number for the Administration Server inside the Kubernetes cluster. |
| managedServerNameSvc |
Name of the Managed Server Base Service name. This can be found in create-domain-job.yaml of output folder specified during domain creation. |
| sharedPersistentVolumeClaimName | Name of the persistent volume claim to be created to host the AIA home. |
Parameters for AIA PV-PVC
Table 8-2 lists the parameters that you configure for AIA PV-PVC. These parameters are available in the $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/charts/aia-comms-pv-pvc/values.yaml file.
Table 8-2 Parameters for AIA PV-PVC
| Parameter | Description |
|---|---|
| createPV | To create AIA PV PVC, specify true. |
| persistentVolumeName | Name of the persistent volume to be created to host the AIA home. |
| storageClassName | Kubernetes storage class name of the persistent volume claim to be created to host the AIA home. |
| aiacommsStorageType | Type of storage. Legal values are NFS and HOST_PATH. If using NFS, aiacommsStorageNFSServer must be specified. |
| aiacommsStoragePath |
Physical path of the storage for the PV. When aiacommsStorageType is set to HOST_PATH, this value should be set the to path to the domain storage on the Kubernetes host. When aiacommsStorageType is set to NFS, then aiacommsStorageNFSServer should be set to the IP address or name of the DNS server, and this value should be set to the exported path on that server. Note that the path where the domain is mounted in the WebLogic containers is not affected by this setting; that is determined when you create your domain. |
| aiacommsStorageReclaimPolicy | Kubernetes PVC policy for the persistent storage. Valid values are: Retain, Delete, and Recycle. |
| aiacommsStorageSize | Total storage allocated for the AIA PVC. |
Parameters for AIA PIPs
Table 8-3 lists the parameters that you configure for AIA PIPs. These parameters are available in the $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/charts/aia-comms-deploy-aiapip/values.yaml file.
Table 8-3 Parameters for AIA PIPs
| Parameter | Description |
|---|---|
| Order2Cash_Siebel | Type true if you want to install PIPs for Siebel. |
| SPLIT_XREF | Creates Split XRef schema. The default is
true.
|
| Order2Cash_brm | Type true if you want to install PIPs for BRM. |
| Order2Cash_osm | Type true if you want to install PIPs for OSM. |
| AABC_PIP | Type true if you want to install PIPs for AABC. |
| DOMAIN_LOCATION | Weblogic Domain location for SOA pods. |
| isLaunchIntegrationEnabled | Type true if Launch is integrated. Otherwise, type false. |
| OSM_VERSION | The version of OSM to which you are connecting. This value must be 10 characters or less. For example: 7.5.0.0.9. |
| OSM_PROV_WL_JMS_QUEUE_ACCESS_PORT |
The port assigned to the WebLogic Server host used for accessing inbound JMS queues for OSM SOM. For example: 7080. |
| OSM_CFS_WL_JMS_QUEUE_ACCESS_HOST | The WebLogic Server host used for accessing inbound JMS queues for OSM COM. |
| OSM_CFS_WL_JMS_QUEUE_ACCESS_PORT |
The port assigned to the WebLogic Server host used for accessing inbound JMS queues for OSM COM. For example: 7080. |
| OSM_PROV_WL_JMS_QUEUE_ACCESS_HOST | The WebLogic Server host used for accessing inbound JMS queues for OSM SOM. |
| BRM_PRIMARY_CM_HOST | The IP address or DNS name of the BRM server's primary Connection Manager. |
| BRM_VERSION | The version of BRM to which you are connecting. This value must be 10 characters or less. For example, 15.1.0.0.0. |
| BRM_DB_HOST | The IP address or DNS name of the Oracle Database Advanced Queuing database instance where the BRM Synchronization Queue Manager Data Manager (DM_AQ) is configured. |
| BRM_AQ_DB_SID | The Oracle Database Advanced Queuing database system ID. |
| BRM_PRIMARY_CM_PORT | The port assigned to the BRM server's primary Connection Manager. For example: 11960. |
| BRM_AQ_QUEUE | The name of the queue configured for DM_AQ. For example: AQ_QUEUE. |
| BRM_DB_PORT | The port assigned to the Oracle Database Advanced Queuing database instance. For example: 1521. |
| BRM_DB_JDBC_URL |
BRM Database JDBC URL. JDBC URL is used to connect and configure the corresponding database. Examples are: SID : jdbc:oracle:thin:@host:port:sid Service Name : jdbc:oracle:thin:@//host:port/service_name. |
| SPM_PROXY_PORT | Siebel Session Pool Manager Port Number. Can be empty if one is not available. For example: 1521. |
| SPM_PROXY_HOST | Siebel Session Pool Manager Host. Can be empty if one is not available. |
| XREF_TEMP_TABLESPACE | An existing temp tablespace name, which can be used to create XRef schema. Tablespace must exist before installing AIA cloud native. |
| XREF_DEFAULT_TABLESPACE | An existing users tablespace name, which can be used to create XRef schema. Tablespace must exist before installing AIA cloud native. |
| XREF_SCHEMA_SYS_ROLE | The role of the SOA database administrator. Example: SYSDBA. |
| XREF_SCHEMA_JDBC_URL | The URL to create the cross reference schema. The cross reference schema will be created in the database specified in the JDBC URL. Oracle recommends that you create the cross reference schema in the same database as the SOA database. The JDBC URL can be provided as per the SOA database configuration. If a different database is selected, specify the corresponding JDBC URL. Examples are: SID: jdbc:oracle:thin:@host:port:sid Service Name : jdbc:oracle:thin:@//host:port/service_name. |
| SBL_VERSION | The version of Siebel CRM to which you are connecting. This value cannot be longer than 10 characters. For example: 21.2.0.0. |
| SBL_HOST | The DNS name of the Siebel CRM host. |
| SBL_PROTOCOL | The internet protocol used to connect to the Siebel CRM server. For example: http:// |
| SBL_LANG | The language used by the Siebel application. For example: enu. |
| SBL_ENTERPRISE_SERVER_NAME | The name of the Siebel Enterprise Server on which Siebel CRM is installed. For example: Siebel. |
| SBL_PORT | The port assigned to Siebel CRM. If Siebel is running on Kubernetes, you can use Tomcat's exposed port number. For example: 4432. |
| SBL_DB_HOST | The IP address or DNS name of the Siebel CRM database host. |
| SBL_DB_PORT | The port assigned to the Siebel CRM database. For example: 1521. |
| SBL_DB_SID | The Siebel CRM database system ID. For example: orcl. |
| SBL_DB_JDBC_URL |
The URL to connect to the Siebel database. JDBC URL is used to connect and configure the corresponding database. Examples are: SID : jdbc:oracle:thin:@host:port:sid Service Name : jdbc:oracle:thin:@//host:port/service_name. |
| SOA_WL_MS_PORT | The port assigned to the SOA managed server or cluster
proxy.
This will be the port number of the SOA cluster service inside Kubernetes SOA namespace. |
| SOA_DB_SYS_ROLE | SOA Database System role name. Example: SYSDBA. |
| SOA_WL_ADMIN_PORT | The port assigned to the administration server. This will be the port number of the SOA admin server's service inside the Kubernetes SAO namespace. |
| SOA_WL_DOMAIN_NAME | The name of your SOA domain. |
| SOA_WL_MS_NAME |
The name of the primary SOA managed server or the name of the SOA cluster. For single node WebLogic Server, use the WebLogic managed server's name. For cluster based WebLogic Server configuration, use the name of the SOA WebLogic Server cluster instance generated for the domain. |
| SOA_DB_JDBC_URL |
The URL to connect to the SOA database. Example: SID : jdbc:oracle:thin:@host:port:sidService Name : jdbc:oracle:thin:@//host:port/service_name TNS_ADMIN : jdbc:oracle:thin:@db_name?TNS_ADMIN=tns_admin_location. |
| SOA_WL_MS_HOST | The host of the SOA managed server or the proxy URL for the cluster. This will be SOA cluster service name inside Kubernates SOA namespace. The value can be derived from domain_name-cluster-soa-cluster. |
| SOA_WL_ADMIN_HOST | The host of the administration server for your SOA domain. This will be the service name of admin server inside Kubernetes SOA namespace. |
| ODI_AABC_AGENT_PORT | The port assigned to the agent. For example: 20910. |
| ODI_AABC_REPID | The repository ID of the Oracle Data Integrator work repository for integration artifacts. |
| ODI_AABC_REPNAME | The name of the Oracle Data Integrator work repository for integration artifacts. For example: WORKREP. |
| ODI_AABC_AGENT_APP_NAME | The application name for the standalone or Java EE
agent. For example: oraclediagent
Note: The application name for a standalone agent is always oraclediagent. |
| ODI_DB_HOST | The DNS name of the master repository database host. For
example: odim.example.com |
| ODI_DB_SID | The master repository database system ID. For example: oracle. |
| ODI_DB_PORT | The port assigned to the master repository database. For example: 1521. |
| ODI_HOST | ODI host URL as per ODI Agents WSDL URL (only IP section is required). |
Parameters for AIA Certificates
Table 8-4 lists the parameters that you configure for AIA Certificates. These parameters are available in the $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/charts/aia-comms-certs/values.yaml file.
Table 8-4 Parameters for AIA Certificates
| Parameter | Description |
|---|---|
| certificate.name | Name of the keystore where the certificate operation is to be performed. This value can be either the identityKeyStoreName or trustKeyStoreName. |
| certificate.identityKeyStoreName | Name of the identity KeyStore. |
| certificate.trustKeyStoreName | Name of the Trusted keyStore. |
| certificate.type | The type of certificate to be imported: TrustedCertificate. |
| wlsServerHome |
The root directory of your WebLogic installation. If this is not changed during image creation, then root directory will be used as the default. |
| certificateSecretName | Specify the Kubernetes secret name used to create secrets of certificates to be imported. |
| seibel.alias | Specify the Siebel certificate details to be imported, deleted, or updated. The certificate alias name. |
| seibel.fileName | The file name placed in certificate directory to be imported. |
| seibel.operation | Supported operation types are import, delete, and update. Leave the operation field empty or commented in case no operation is required to be performed. |
| osm.alias | Specify the osm certificate details to be imported, deleted, or updated. The certificate alias name. |
| osm.fileName | Filename placed in certificate directory to be imported. |
| osm.operation | Supported operation types are import, delete, and update. Leave the operation field empty or commented in case no operation is required to be performed. |
Parameters for AIA PIPs Credentials
Table 8-5 lists the parameters that you configure for AIA PIPs credentials. Deployment of AIA PIPs requires Kubernetes secrets for OSM, BRM, Siebel, Xref, and SOA. Do not create a Kubernetes secret for a particular component, if any of the components among OSM, Siebel, or BRM is not being deployed.
Table 8-5 Parameters for AIA PIPs Credentials
| Component | Parameter | Description |
|---|---|---|
| OSM | OSM_CFS_WL_JMS_QUEUE_ACCESS_USER | OSM CFS Weblogic JMS Queue User Name |
| OSM | OSM_CFS_WL_JMS_QUEUE_ACCESS_PSWD | OSM CFS Weblogic JMS Queue Password |
| OSM | OSM_PROV_WL_JMS_QUEUE_ACCESS_USER | OSM Provisioning Weblogic JMS Queue User Name |
| OSM | OSM_PROV_WL_JMS_QUEUE_ACCESS_PSWD | OSM Provisioning Weblogic JMS Queue Password |
| OSM | OSM_CFS_ADMIN_USER | OSM CFS Admin User Name |
| OSM | OSM_CFS_ADMIN_PSWD | OSM CFS Admin Password |
| OSM | OSM_PROV_ADMIN_USER | OSM Provisioning Admin User Name |
| OSM | OSM_PROV_ADMIN_PSWD | OSM Provisioning Admin Password |
| BRM | BRM_AQ_USER | BRM AQ Queue User Name |
| BRM | BRM_AQ_PSWD | BRM AQ Queue Password |
| Siebel | SBL_EAI_USER | Siebel EAI Server User Name |
| Siebel | SBL_EAI_PSWD | Siebel EAI Server Password |
| Siebel | SBL_DB_USER | Siebel Database User Name |
| Siebel | SBL_DB_PSWD | Siebel Database Password |
| Xref | XREF_SCHEMA_NAME | Given Schema name will be used to create XRef |
| Xref | XREF_SCHEMA_PASSWORD | Given password will be used to create Xref |
| Xref | XREF_SCHEMA_SYS_USER | SOA Database SYS user name |
| Xref | XREF_SCHEMA_SYS_PASSWORD | SOA Database SYS password |
| SOA | SOA_WL_ADMIN_USER | SOA Weblogic server admin user name |
| SOA | SOA_WL_ADMIN_PASSWORD | SOA Weblogic server admin password |
| SOA | SOA_DB_USER | SOA DB user name in the format: RCU_Prefix_SOAINFRA |
| SOA | SOA_DB_PASSWORD | SOA DB password |
| SOA | SOA_DB_SYS_USER | SOA DB SYS admin user name |
| SOA | SOA_DB_SYS_PASSWORD | SOA DB SYS admin user password |
| ODI | ODI_USER | The Oracle Data Integrator administrator's user name. For example: SUPERVISOR |
| ODI | ODI_PASSWORD | The password for the Oracle Data Integrator administration user. |
| ODI | ODI_DB_USER | The master repository database user. For example: ODI_REPO |
| ODI | ODI_DB_PSWD | The master repository database password. |