5.3 Validating the OHS Deployment

Validate the Oracle HTTP Server (OHS) container and check you can access OHS using the nodeport.

Validating the OHS Container File System

To validate the OHS container file system:
  1. Run the following command to get the name of the OHS container:
    kubectl get pods -n <namespace>
    For example:
    kubectl get pods -n ohsns
    The output will look similar to the following:
    NAME                         READY   STATUS    RESTARTS   AGE
ohs-domain-d5b648bc5-vkp4s   1/1     Running   0          5m34s
  2. Run the following command to create a bash shell inside the container:
    kubectl exec -n <namespace> -ti <pod> -- /bin/bash
    For example:
    kubectl exec -n ohsns -ti ohs-domain-79f8f99575-8qwfh -- /bin/bash
    This will take you to a bash shell inside the container:
    [oracle@ohs-domain-75fbd9b597-z77d8 oracle]$
  3. Inside the bash shell navigate to the /u01/oracle/user_projects/domains/ohsDomain/config/fmwconfig/components/OHS/ohs1/ directory:
    cd /u01/oracle/user_projects/domains/ohsDomain/config/fmwconfig/components/OHS/ohs1/
    From within this directory, you can navigate around and list (ls) or cat any files you configured using the ConfigMaps.

Validating the OHS Nodeport

Validate the OHS nodeport by accessing the OHS URL's.

In the examples below, ${OHS-HOSTNAME} refers to the hostname.domain of the server where the OHS nodeport was deployed. ${OHS-NODEPORT} refers to the nodePort specified in your ohs-service.yaml, for example 31777 for HTTP, or 31443 for HTTPS.

Note:

If OHS is accessed via a loadbalancer, replace ${OHS-HOSTNAME} and ${OHS-NODEPORT} with the loadbalancer hostname.domain and port.

If you have any problems accessing the URL’s, refer to Troubleshooting and Common Problems.

  1. Launch a browser and access the following:

    Note:

    If you have deployed OHS with Oracle WebGate, then it will depend on your policy setup as to whether the URL’s below are accessible or not.
    • The OHS homepage http(s)://${OHS-HOSTNAME}:${OHS-NODEPORT}.
    • Any other files copied in your ohs-htdocs ConfigMap, for example: http(s)://${OHS-HOSTNAME}:${OHS-NODEPORT}/mypage.html.
    • Any files from directories created under htdocs, for example the ohs-myapp ConfigMap: http(s)://${OHS-HOSTNAME}:${OHS-NODEPORT}/myapp.
    • Any URI’s defined for mod_wl_ohs in your httpd.conf, ssl.conf or moduleconf/*.conf files, for example: http(s)://${OHS-HOSTNAME}:${OHS-NODEPORT}/console.
    • If Oracle WebGate is deployed, any protected applications, for example: http(s)://${OHS-HOSTNAME}:${OHS-NODEPORT}/myprotectedapp.