...
Validate if the Adeptia Connect helm is deployed.
Click the menu icon at the top left corner, and then click Local.
Go to Apps > Installed Apps.
In the Installed Apps, verify if the chart entry for adeptia-connect is in Deployed state.
Check the status of the deployed pods of adeptia-connect.
Click the menu icon at the top left corner, and then click Local.Anchor a-through-c a-through-csteps steps Go to Workloads > Pods.
In the Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.
Validate if all the listed pods are in Running state.
Check the status of each microservice by following the steps given below.
Follow the steps a through c.
Click on more options icon of a pod and select view logs.
Search for message “Microservice started successfully” in each pod logs except runtime deployment manager and rabbitmq pods.
Note: This screenshot is reference from runtime pod
Verify shared Runtime pod is launched and running
From rancher UI click on more option button at top left corner > Local > Workloads > pods
From the namespace dropdown (at top aligned at entre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).
Pod for ac-runtime microservice is present and in running state
Access the adeptia-connect application UI and login to the application.
Open the browser and enter adeptia-connect domain.
Enter the username & password
User should successfully navigate to home page after successful sign in operation.
Verify shared NFS volumes are attached with required pods
From rancher UI click on more option button at top left corner > Local > Workloads > Deployments.
From the namespace dropdown (at top aligned at centre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).
Click on name link of required deployment(On which we need to verify the mounted volumes)
Click on config
Click on storage > It will list down all the mounted volumes to the pods
Verify the shared NFS volumes are attached to below pods:
Runtime
Event
Archival and cleanup
Portal
Webrunner
Listener
...