Possible Issues in Login and Screen Launch

1.3.2 Possible Issues in Login and Screen Launch

This topic describes the possible issues that may occur while logging in and launching the screens.

Perform the following checks if the login page is not launching.

Check whether the app-shell war file is deployed.
Make sure that the war file is up and running in the deployed managed server and try to login again.
Check whether the user has logged in with the app-shell URL according to the war file deployed.
Check whether the required component-server wars like cmc-component-server, obvam-component-server etc., are also deployed along with the app-shell.
Example: http://<ip-address>:<Port>/app-shell/index.jsp will load the login page of the application.

In this URL, the name app-shell is dynamic which depends on the name of war file deployed.

Figure 1-6 Sign In

Unable to login after launching the application

Perform the following check if you are not able to login after the application is launched.

Make sure that the plato-api-gateway service, plato-ui-config service, sms-core-service, and common core services are up and running.

Figure 1-7 Services

Unable to login after restarting the services

Perform the following check if you are not able to log in after restarting the services.

Make sure that the LDAP server is up and running, and check if the entered credentials are correct.

Screens are not launching after logging in

Perform the following check if you are not able to launch the screens after logging in.

Make sure that the respective services are up and running.
Verify the VPN connection while trying to troubleshoot the issues related to page launching, etc.

Parent topic: Troubleshooting Environmental Issues