Proper process to bounce User App service/server...?


Hi Guys,

We are going to have come maintenance activity scheduled in the coming
week.
I know that there are certain steps that one needs to follow while
bouncing User Server/service.

As far as I know, the steps would be:
Stop Jboss.
Stop mysql.
Stop User Application and Roles driver.
Reboot the server.
Start User Application and Roles driver.
Verify the Jboss and mysql are up and running.
Verify the connectivity.

Are these the rights steps?


--
ddgaikwad
------------------------------------------------------------------------
ddgaikwad's Profile: https://forums.netiq.com/member.php?userid=5917
View this thread: https://forums.netiq.com/showthread.php?t=51570

  • On 08/20/2014 03:48 PM, ddgaikwad wrote:
    >
    > Hi Guys,
    >
    > We are going to have come maintenance activity scheduled in the coming
    > week.
    > I know that there are certain steps that one needs to follow while
    > bouncing User Server/service.
    >
    > As far as I know, the steps would be:
    > Stop Jboss.
    > Stop mysql.
    > Stop User Application and Roles driver.
    > Reboot the server.
    > Start User Application and Roles driver.
    > Verify the Jboss and mysql are up and running.
    > Verify the connectivity.
    >
    > Are these the rights steps?


    Yes, that should work. The only part that I have seen matter is having
    the RDBMS up before JBoss loads the web application (UserApp) since that
    is a direct dependency; of course the RDBMS should also stay up until the
    application exits. The rest should connect on its own in a timely fashion
    but otherwise it should not matter.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • ab <ab@no-mx.forums.netiq.com> wrote:

    > The rest should connect on its own in a timely fashion
    > but otherwise it should not matter.


    Be sure to identify any drivers that call rbpm via policy (do-add-role,
    start workflow etc). I'd stop these drivers unless these rules also check
    for an error status and can re-attempt the same logic until the user app
    returns success.

    --
    If you find this post helpful and are logged into the web interface, show
    your appreciation and click on the star below...