• you can get into websphere and restart the individual services, or

 

  • you can launch the command prompt from the desktop on cobauthappl and choose 1 (for LIVE - its the only option), then 



  1. Log into the application server as the auth user
  2. On the desktop, double click on the WSENV
  3. Select the LIVE environment and shutdown AWP applications as follows


 

    • appstop iservice
    • appstop eservice
    • appstop fgl-live
    • appstop gws-live (if webservice error occur like below - 502)


Then  once each of those has completed

 

    • appstart iservice
    • appstart eservice
    • appstart fgl-live
    • appstart gws-live (if webservice error occur)

 

  • you can launch the command prompt from the desktop on cobauthappl and choose 1 (for LIVE - its the only option), then WASSERVICE -STOP LIVE, then when it returns to the prompt WASSERVICE -START LIVE (each can take a minute to do) ... this is effectively stopping and restarting websphere completely which should include the services within it, effectively doing the job of the above appstop and appstart commands.
  • you can simply reboot the servers - this is obviously more comprehensive at a server level but as restarting e&i services stops access anyway, I like to give the servers a restart when i do it. (you might want to check with your network guys if you want to do this one in case there's a reason not to)



Whichever method you choose I wouldn't do this until after hours


(or)

  • another way for IBM WebSphere restart ->go to COBAUTHAPP-> Application Server->services(Local)-> IBM WebSphere Application service for V9.0 Live-> below use Stop and Start button (marked in purpule and green).




----------------------------------------------------------------------------------------------------------------------------------------


After the patch upgrade some time API server does not restart automatically, So we need to check and manually start it again (if will 404-page error occurs in somewhere in randomly in Authority or some Modules):


Sometimes the application pools will automatically start after a reboot. To check, log on to the API server and open IIS. Expand the Sites tab


The screenshot shows the auth.app.live pool in a stopped state. From the menu on the right-hand side, you can select start.