Checking the Status of a Requested Environment

To find the latest status of a requested environment, run GET API using the selfLink. The selfLink is displayed when you execute the payload, as shown in Executing the Payload to Deploy Siebel CRM. The output JSON will have a status section with the stages, such as those shown below. This topic is part of Additional Administrative Tasks in Siebel Cloud Manager.

GET https://<IP Address>:<Port>/scm/api/v1.0/environment/4QVRX5

Siebel CRM Application URLs

At the end of the Ansible workflow publish stage, URLs for the Siebel CRM applications are populated, similar to the following:

"urls": [
    "https://<IP Address>/siebel/app/callcenter/enu",
    "https://<IP Address>/siebel/app/eservice/enu",
    "https://<IP Address>/siebel/app/sservice/enu",
    "https://<IP Address>/siebel/smc"
]

Siebel CRM URLs can be viewed using the environment query (GET).

If the URLs are not populated, they can be formed by finding the IP address of the Loadbalancer (Kubernetes service or Load Balancer instance in OCI). For example:

https://<IP Address from LB>/siebel/app/callcenter/enu

To connect using kubectl, check the log files mentioned below.

Viewing Logs

Different kinds of logs are useful for capturing the flow and debugging. For any failures, you can review logs and correct issues. For example, you can correct policy issues in OCI and rerun the workflow.

SCM application logs (retrieve using GET API). For example:

Retrieve consolidated logs using a URL like this:
```
GET https://<CM_Instance_IP>:16690/scm/api/v1.0/environment/<env_id>/logs
```
Retrieve logs for specific stages using a URL like this:
```
GET https://<CM_Instance_IP>:16690/scm/api/v1.0/environment/<env_id>/logs/<stage_name>
```
You can obtain the <stage_name> from GET info stages section. For example, a URL like the following provides the log of the import database stage:
```
GET https://<CM_Instance_IP>:16690/scm/api/v1.0/environment/<env_id>/logs/import-siebel-db
```
You can also view logs by connecting to the SCM instance using SSH and the following command:
```
sudo podman exec -it cloudmanager bash
```
Ansible logs (retrieve using GET API). For example:
```
GET https://<CM_Instance_IP>:16690/scm/api/v1.0/environment/<env_id>/logs/ansible
```
You can also find Ansible logs inside the working directory of a given environment, as follows:
- SSH to the SCM application instance using opc user.
- Exec into the container using the command:
```
- sudo podman exec -it cloudmanager bash
```
- Change directory to /home/opc/siebel/<env_id>/ (for example, /home/opc/siebel/4QVRX5 is the working directory for an environment with environment ID 4QVRX5).
- You can find Ansible logs inside the artifacts directory, such as /home/opc/siebel/4QVRX5/artifacts. Multiple folders might be found, such as if the workflows ran multiple times.
- Review the stdout file and the rc file under the given run folder to see failure and debug information.