1.7.2 Possible Issues While Logging in and Launching Screen

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

Login Page is not Launching

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

  1. Check whether the app-shell war file is deployed.
  2. Make sure that the war file is up and running in the deployed managed server and try to login again.
  3. Check whether the user has logged in with the appshell URL according to the war file deployed.
  4. 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 the above URL, the name app-shell is dynamic which depends on the name of war file deployed.

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.

Unable to login after restarting the services

Perform the following check if you are not able to login after restarting the services.
  • Make sure that the LDAP server is up and running, and check if the entered credentials are correct.

Retail Banking menus are not displayed after logging in

After you log in, if the Retail Banking menus are not displayed, map the functional activity codes in the table SMS_TM_ROLE_ACTIVITY. Once it is mapped, check if the corresponding role is assigned to your user ID.

Screens are not launching after logging in

If you are not able to launch the screens after logging in, make sure that the respective services are up and running.

Note:

Verify the VPN connection while trying to troubleshoot the issues related to page launching, etc.