Verifying the Installation

Verifying a Successful Deployment

To check if your deployment has run successfully:

Check if the pod is in Running state by running the following command:
```
kubectl get pods -n namespace_name
```
Check the logs for any errors by running the following command:
```
kubectl logs pod_name -n namespace_name
```
If no errors appear, the deployment has run successfully.
Run the following command to retrieve External IP and Port Number for the services:
```
kubectl get po -n namespace_name -o wide
```
To validate Basic Auth deployment:
- TDS Service: Run the following command to check if the service is accessible:
```
curl http://TDS_NodeIP:port/job
```
  The command should run without errors or connection failures.
- TES Service: Verify TES service accessibility using the following command:
```
curl http://TES_NodeIP:port/taas
```
  The command should return a response without errors.
- UI Service: Open the UI in a browser using the following URL:
```
http://UI_NodeIP:port
```
  If you are able to login to the UI, the deployment is working as expected.
To validate OAuth deployment:
- Use the IDCS credentials to generate an OAuth access token. The token should be included in the Authorization Header as a Bearer Token for subsequent requests.
- Validate Service Accessibility:
  TDS Service
  - Open Postman and create a GET request to the following:
```
https://TDS_NodeIP:port/job
```
  - In the Headers section, add the following:
```
Authorization: Bearer access_token
```
    Send the request. The response should return with no errors or connection failures.
  TES Service
  - Open Postman and create a GET request to the following:
```
https://TES_NodeIP:port/taas
```
  - In the Headers section, add the following:
```
Authorization: Bearer access_token
```
  - Send the request. The response should indicate successful connectivity.
  UI Service
  - Open the UI in a browser using the following URL:
```
https://UI_NodeIP:port
```
  - If required, tunnel the connection locally before accessing the URL. You need to tunnel the connection locally if:
    - You want to access the UI through a browser but don't have VNC set up.
    - Network blocks or firewalls prevent direct access to the UI.
    - You can't set up a load balancer for access.
    - You're working from a location without direct access to the UI.
  - Log in using OAuth credentials. If authentication is successful, the deployment is functioning correctly.

Note:

You can verify if your environment variables are correctly set in the container by following these steps:

Run the following command:

kubectl exec -it pod_name -n namespace -- /bin/sh

Navigate to the config directory and verify variables and values.
If an environment variable is missing, check the deployment manifest or the override-values.yaml file for incorrect configurations.

Setting Up the STAP Design Experience

The STAP Design Experience package simplifies the automation of end-to-end scenarios by offering a user-friendly Behavior-Driven Development (BDD) environment for creating, testing, and deploying automation. For more information on the STAP Design Experience, see "Using the STAP Design Experience Package" in User Operations Guide.

Before setting up the STAP Design Experience, ensure you have installed the correct version of Java. See "Common Software Compatibility" in Compatibility Matrix,

To set up the STAP Design Experience package, follow these steps.

Download the STAP Design Experience package, titled oc-stap-1.25.1.1.zip inside the DE.zip file.
Unzip the files in the package. It contains the following folders:
- lib: Contains the STAP library.
- sampleWorkSpace: Contains the sample automation workspace.
- stap: Contains the STAP command-line script.
- run.sh, compile.sh, run.cmd, and compile.cmd: Contain sample scripts to perform STAP operations.

To set up STAP Design Experience on a Linux or a Mac, see "Configuring the STAP Design Experience on Linux".

To set up STAP Design Experience on Windows, see "Configuring STAP Design Experience on Windows".

Configuring the STAP Design Experience on Linux

To configure STAP Design Experience on Linux, follow these steps:

Set the STAP environment variables using the following command:
```
export STAP_HOME=packageLoc
export PATH=$STAP_HOME:$PATH
```
where:
- packageLoc is the location of your STAP DE package
- STAP_HOME:PATH is the path to your STAP repository
In a new terminal window, start WireMock, which is a mock server to run the sample scenarios.
If you are using the Bourne shell, run the following commands:
```
cd 
$STAP_HOME/sampleWorkSpace/WireMock 
startWireMock.sh
```
If you are using another shell, run the following commands:
```
cd 
$STAP_HOME/sampleWorkSpace/WireMock
sh startWireMock.sh
```
Compile sample automation scenarios.
If you are using the Bourne shell, run the following commands:
```
cd 
$STAP_HOME/
./compile.sh
```
If you are using another shell, run the following commands:
```
cd 
$STAP_HOME/
sh compile.sh
```
In the same terminal window, run the sample automation scenarios.
If you are using the Bourne shell, run the following commands:
```
cd 
$STAP_HOME/
./run.sh
```
If you are using another shell, run the following commands:
```
cd 
$STAP_HOME/
sh run.sh
```

Configuring STAP Design Experience on Windows

To configure STAP Design Experience on Windows, follow these steps:

Set the STAP environment variables by following these steps
- Update the setenv.cmd file with the location where the STAP DE package is extracted, by running the following command:
```
set STAP_HOME=packageLoc
set PATH=%STAP_HOME%;%PATH%
```
- At the command prompt, navigate to design experience folder titled DE.zip in the CNTK folder and set the environment variables using the following command:
```
setenv.cmd
```
In a new terminal window, start WireMock, which is a mock server to run the sample scenarios, by running the following command:
```
cd %STAP_HOME%\sampleWorkSpace\WireMock
startWireMock.cmd
```
In another terminal window, compile sample automation scenarios by running the following command:
```
cd %STAP_HOME%
compile.cmd
```
Note:
If successful, compile.cmd returns with a 100% pass.
In the same terminal window as the previous step, run the sample automation scenarios:
```
cd %STAP_HOME%
run.cmd
```
If successful, run.cmd returns with a scenario summary report in the terminal window, alongside an automation report generated in the STAP UI.

Accessing STAP Microservice URLs

After STAP microservices are deployed, you can access URLs of each microservice.

To access URLs of STAP microservices, follow these steps:

Collect the port details by running the following command:
```
kubectl get svc -n namespace
```
To access each microservice, run the following command:
```
https://node ip:port
```
Note:
If you do not have SSL configured, use http.

6 Verifying the Installation

Verifying a Successful Deployment

Setting Up the STAP Design Experience

Configuring the STAP Design Experience on Linux

Configuring STAP Design Experience on Windows

Accessing STAP Microservice URLs