Verify the Platform is Running Correctly
Once you have completed the installation and configuration of the One37 Platform components, you should verify that the platform is running correctly. This involves checking that the Business Studio, Business Connector, and Workflow Engine are all running and communicating correctly.
Verify the Business Studio
To verify that the Business Studio is running correctly, open a web browser and navigate to the URL of the Business Studio.
You should see the Business Studio dashboard, which will display the status of the Business Connector your created in the previous steps.
If you are unable to access the Business Studio, check the logs of the Business Studio container for any errors. You can do this by running the following command:
- Docker Compose
- Kubernettes
Studio Kubernetes environment
You can do this by accessing the logs of the Business Connector pod in your Kubernetes management UI or via the cli by running the following command:
kubectl namespace one37id get pods
kubectl logs [studio-pod-name]
Verify the Business Connector
To verify that the Business Connector is running correctly, first check if it has a green shield icon under the business logo indicating that it is connected.
Additional checks can be performed by click on the Business Connector link in the Business Studio dashboard.
Log in using the Business Admin user credentials that you configured during the installation process.
This will open the Business Connector dashboard, where you can navigate in the sidebar to the Operations/Server Instances
menu to view the status and drill down to the exported logs of the instance and check for any errors.
If you are unable to access the Business Connector, check the container logs of the Business Connector container for any errors.
- Docker Compose
- Kubernettes
BC Kubernetes environment
You can do this by accessing the logs of the Business Connector pod in your Kubernetes management UI or via the cli by running the following command:
kubectl namespace one37 get pods
kubectl logs [business-connector-pod-name]