Deploying AIA Cloud Native

4 Deploying AIA Cloud Native

This chapter provides information about deploying AIA cloud native. AIA cloud native deployment leverages the SOA cloud native deployment scripts and uses Helm charts for configuration management.

The configuration details for AIA cloud native are the same as the configuration of standard deployments such as connection details, credentials, and XRef details of edge applications.

Along with AIA configuration details, SOA configuration details, such as RCU schema, domain parameters and other configurations are also managed by Helm charts. Helm charts are organized in a hierarchy and a master chart holds the references to several child charts for better management.

Deploying SOA Cloud Native

Deploy SOA cloud native as per the instructions provided in the Oracle SOA Suite documentation.

Deploying SOA cloud native has the following tasks:

Preparing the environment
For instructions, refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/.
Perform all required steps and as per your requirement. For example, the following are some steps you perform based on your requirements:
- Installing WebLogic Operator:
  1. Get dependent images. Refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/#get-dependent-images.
  2. Install the WebLogic Kubernetes Operator. Refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/#install-the-weblogic-kubernetes-operator.
- Preparing the environment for Oracle SOA Suite domains:
  1. Create a namespace. Refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/#create-a-namespace-for-an-oracle-soa-suite-domain.
  2. Create a persistent storage. Refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/#create-a-persistent-storage-for-an-oracle-soa-suite-domain.
  3. Create a Kubernetes secret with domain credentials. Refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/#create-a-kubernetes-secret-with-domain-credentials.
  4. Create a Kubernetes secret with the RCU credentials. Refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/#create-a-kubernetes-secret-with-the-rcu-credentials.
  5. Configure access to your database. Refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/#configure-access-to-your-database.
  6. Run the Repository Creation Utility to set up your database schemas (create schemas).
    
    Note:
    Use the AIA cloud native image with the utility (command).
    
    Refer to the information at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/prepare-your-environment/#run-the-repository-creation-utility-to-set-up-your-database-schemas.
Creating the SOA domain

Note:
Use the AIA cloud native image for deploying the SOA domain. Also, ensure that you include the -Dweblogic.rjvm.allowUnknownHost=true parameter. For more information, refer to the WKO documentation on Oracle GutHub at: https://oracle.github.io/weblogic-kubernetes-operator/managing-domains/accessing-the-domain/external-clients/#enabling-unknown-host-access.
Refer to the instructions at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/installguide/create-soa-domains/.
Configuring a load balancer
Configure a load balancer as per your requirement. Refer to the instructions at: https://oracle.github.io/fmw-kubernetes/23.1.2/soa-domains/adminguide/configure-load-balancer/.

Creating PV-PVCs

You can create AIA PV-PVCs by using the values.yaml files.

To create AIA PV-PVCs:

Update the following values.yaml files as per your requirement:
- $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/values.yaml. See "Global Parameters" for details about the parameters.
- $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/charts/aia-comms-pv-pvc/values.yaml. See "Parameters for AIA PV-PVC" for details about the parameters.
Run the following command to install the Helm chart:
```
$ cd $AIA_DIR/oc-cn-aia-comms/helm-charts/
$ helm install aia-comms-pv-pvc \
     aia-comms-chart/charts/aia-comms-pv-pvc/ \
     --namespace namespace \
     --values ./aia-comms-chart/values.yaml
```
This creates the following:
- Kubernetes PV PVC
- Kubernetes job aia-comms-create-home-job to populate AIA PV
- Service Account with name domain_name-cluster-kubectl
- ClusterRole of name domain_name-access-pod-cluster-role
- RoleBinding of name domain_name-access-pod-role-binding
Wait till the aia-comms-create-home-job job completes.
```
$ kubectl wait --for=condition=complete job.batch/aia-comms-create-home-job -n namespace
```
Alternatively, this can also be confirmed by checking the status of the Kubernetes job or pod by running the following commands:
```
$ kubectl get pods -n namespace
$ kubectl get jobs -n namespace
```

Updating the Oracle SOA Suite Domain

To update the Oracle SOA Suite domain with the AIA PV:

Stop the Oracle SOA Suite domain:

$ cd $AIA_DIR/fmw-kubernetes/OracleSOASuite/kubernetes/domain-lifecycle/
$ sh stopDomain.sh -d domain -n namespace -v

(Optional. This does not add extra time.) To get more information on the shutdown process, you can run:

$ cd $AIA_DIR/oc-cn-aia-comms/scripts/common
$ sh waitForCluster.sh -a shutdown -d domain -n namespace

Confirm all servers are down.

Do any one of the following to update the AIA PV with domain:

Run the following AIA cloud native scripts:

$ cd $AIA_DIR/oc-cn-aia-comms/scripts
# Remove any existing domain.yaml file from the folder
$ rm domain.yaml
$ sh register-AIAPV.sh \
    -n namespace \
    -d domain_name \
    -c cluster_name \
    -w SOA_PVC_name \
    -p AIA_PVC_name \
    -f $WORKDIR/create-soa-domain/domain-home-on-pv/path_to_output-directory/weblogic-domains/domainUID/domain.yaml

This script does the following:

Appends the volumes and volumeMounts with the AIA PVC details to the Oracle SOA Suite domain
Runs the kubectl apply operation
Waits till all the managed servers are available

Update manually:

$ cd $WORKDIR/create-soa-domain/domain-home-on-pv/
$ vi path_to_output-directory/weblogic-domains/domainUID/domain.yaml
# Take a backup of YAML file before making any changes.
#
# Append volumes in volumes section
#    - name: aia-comms-shared-storage-volume
#      persistentVolumeClaim: 
#        claimName: AIA_PVC_name
 
# Append volumeMounts in volumeMounts section
# Do not change the mount path here.
#    - mountPath: /u01/shared
#      name: aia-comms-shared-storage-volume
 
# Apply the new changes
$ kubectl apply -f path_to_output-directory/weblogic-domains/domainUID/domain.yaml

Wait till all the managed servers are up.

Deploying the AIA PIPs

This section provides instructions for deploying the AIA PIPs.

Configuring AIA PIP Credentials

Deployment of AIA PIPs requires Kubernetes secrets for OSM, BRM, Siebel, Xref, and SOA. Do not create a Kubernetes secret if you are not configuring OSM, Siebel or BRM with AIA.

To configure AIA PIP credentials, navigate to the $AIA_DIR/oc-cn-aia-comms/scripts folder and then run the create-aiapip-credentials.sh script with updated values for each component. See "Parameters for AIA PIPs Credentials" for details about the parameters.

(Optional) For OSM, run the script with the following parameters:

$ cd $AIA_DIR/oc-cn-aia-comms/scripts/
$ sh create-aiapip-credentials.sh \
    -c osm \
    -n namespace \
    -d domain_name \
    -OSM_CFS_WL_JMS_QUEUE_ACCESS_USER username \
    -OSM_CFS_WL_JMS_QUEUE_ACCESS_PSWD password \
    -OSM_PROV_WL_JMS_QUEUE_ACCESS_USER username \
    -OSM_PROV_WL_JMS_QUEUE_ACCESS_PSWD  password \
    -OSM_CFS_ADMIN_USER username \
    -OSM_CFS_ADMIN_PSWD password \
    -OSM_PROV_ADMIN_USER username \
    -OSM_PROV_ADMIN_PSWD password

(Optional) For BRM, run the script with the following parameters:

$ cd $AIA_DIR/oc-cn-aia-comms/scripts/
$ sh create-aiapip-credentials.sh \
    -c brm \
    -n namespace \
    -d domain_name \
    -BRM_AQ_USER username \
    -BRM_AQ_PSWD password

(Optional) For Siebel, run the script with the following parameters:

$ cd $AIA_DIR/oc-cn-aia-comms/scripts/
$ sh create-aiapip-credentials.sh \
    -c siebel \
    -n namespace \
    -d domain_name \
    -SBL_EAI_USER username \
    -SBL_EAI_PSWD password \
    -SBL_DB_USER username \
    -SBL_DB_PSWD password

For Xref, run the script with the following parameters:

Note:

Ensure that you specify a working DB SYS username and password for the Xref scripts.

$ cd $AIA_DIR/oc-cn-aia-comms/scripts/
$ sh create-aiapip-credentials.sh \
    -c xref \
    -n namespace \
    -d domain_name \
    -XREF_SCHEMA_NAME schema_name \
    -XREF_SCHEMA_PASSWORD schema_password \
    -XREF_SCHEMA_SYS_USER sys_user \
    -XREF_SCHEMA_SYS_PASSWORD sys_password

For SOA, run the script with the following parameters:

Note:

Ensure that you specify a working DB SYS username and password for the SOA scripts.

$ cd $AIA_DIR/oc-cn-aia-comms/scripts/
$ sh create-aiapip-credentials.sh \
    -c soa \
    -n namespace \
    -d domain_name \
    -SOA_WL_ADMIN_USER username \
    -SOA_WL_ADMIN_PASSWORD password \
    -SOA_DB_USER username \
    -SOA_DB_PASSWORD password \
    -SOA_DB_SYS_USER username \
    -SOA_DB_SYS_PASSWORD password

Deploying the BRM JCA Adapter

Deploy the BRM JCA Adapter by downloading Patch 35353279 from My Oracle Support and apply it.

For instructions, see "Deploying and Configuring JCA Resource Adapter on Oracle WebLogic Server" in the BRM JCA Adapter guide.

Configuring and Deploying the AIA PIPs

The AIA PIPs Helm chart requires the following:

aia-comms-pv-pvc helm chart
AIA PIP credentials
BRM JCA adapter deployed

Note:

This chart requires a minimum Java heap size of 4 GB, upto a maximum of 8 GB on the Kubernetes node.

If this configuration is not available in Kubernetes cluster, update the templates YAML file as follows:

$ vi $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/charts/aia-comms-deploy-aiapip/templates/aia-comms-deploy-aiapip-job.yaml
 
# Update the value for USER_MEM_ARGS environment variable
# "-Djava.security.egd=file:/dev/./urandom -Xmsinitial_heap_size -Xmxmax_heap_size "
# -Xmsinitial_heap_size is the initial size of the heap.
# -Xmxmax_heap_size is the max size of the heap.

To deploy the AIA PIPs:

Update the following values.yaml files as per your requirement:
- $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/values.yaml. See "Global Parameters" for details about the parameters.
- $AIA_DIR/oc-cn-aia-comms/helm-charts/aia-comms-chart/charts/aia-comms-deploy-aiapip/values.yaml. See "Parameters for AIA PIPs" for details about the parameters.
Run the following command to install the Helm chart:

Note:
This chart requires all of the configured managed servers up and running.
```
$ cd $AIA_DIR/oc-cn-aia-comms/helm-charts/
$ helm install aia-comms-deploy-aiapip \
     aia-comms-chart/charts/aia-comms-deploy-aiapip/ \
     --namespace namespace \
     --values ./aia-comms-chart/values.yaml
```
This chart restarts the managed servers as required during the installation.
Wait till aia-comms-deploy-aiapip-job completes before proceeding to the next step.

Depending on the configuration, this job may take hour(s) for completion.

To validate PIPs deployment, see "Validating the AIA Cloud Native Deployment".

If there are any errors encountered during the deployment, delete and recreate the domains before redeploying the PIPs. For instructions about deletion, see "Deleting the AIA Cloud Native Instance".