Start WebLogic and the Node Manager

Previous Topic

Next Topic

Book Contents

Start WebLogic and the Node Manager

Perform these steps using the non-privileged user account on the application server.

  1. In a command shell, navigate to the WebLogic default /bin directory, for example:

    $ cd u01/app/oracle/product/fmw12c/user_projects/domains/empirica/bin

    Note: The example command is for Oracle WebLogic Server 12c. If you use Oracle WebLogic Server 11g, the path to the WebLogic default bin directory might differ as follows: /u01/app/oracle/Middleware/user_projects/domains/empirica/bin.

  2. If WebLogic is running, stop WebLogic, for example:

    $ ./stopWebLogic.sh

  3. Start WebLogic, for example:

    $ nohup ./startWebLogic.sh > /dev/null &

    Note: Informational messages might appear. You might need to press Enter to see the command prompt.

  4. Based on your version of WebLogic, do the following:
    • For WebLogic 11g:
      1. Identify the process ID for the Node Manager service:

        $ bash -c 'pgrep -f "java.+NodeManager -v$"'

      2. Stop the Node Manager:

        $ kill -9 <process_id_for_the_Node_Manager_service>

      3. Navigate to the $WL_HOME/server/bin directory, for example:

        $ cd /u01/app/oracle/Middleware/wlserver_10.3/server/bin

    • For WebLogic 12c, stop the Node Manager:

      $ ./stopNodeManager.sh

  5. Restart the Node Manager:

    $ nohup ./startNodeManager.sh > /dev/null &

  6. Verify that the Node Manager is reachable:
    1. In an Internet browser, navigate to the WebLogic Server Administration Console, for example:

      https://<servername>:7002/console

    2. Log in using the administrator credentials provided to you by the system administrator.
    3. In the Domain Structure pane, expand Environment, and select Machines.

      The Summary of Machines page appears.

    4. Select SignalMachine.

      The Settings for SignalMachine page appears.

    5. Select the Monitoring tab.
    6. Review the Status field.

      If the Status is Reachable, the Node Manager is reachable. If the Status is Inactive, the Node Manager is not running.

  7. In the Domain Structure pane, select Servers.
  8. Select the Control tab.
  9. Start or restart the Empirica Signal server using the Node Manager:
    1. In the table, review the State property for the Empirica Signal server.
    2. If the State of the server is RUNNING, shut down the server:
      1. Select the SignalServer checkbox.
      2. Expand the Shutdown drop-down menu, and then select Force Shutdown Now.
      3. If prompted to confirm, click Yes.

        After a few moments, the State of the server changes to SHUTDOWN.

        Note: The page does not refresh automatically. To refresh the page, you can click the refresh button located above the table.

    3. Select the SignalServer checkbox.
    4. Click Start.
    5. If prompted to confirm, click Yes.

      After a few moments, the State of the server changes to RUNNING.

      Note: The page does not refresh automatically. To refresh the page, you can click the refresh button located above the table.

  10. If you use Empirica Topics, start or restart the Empirica Topics server using the Node Manager:
    1. In the table, review the State property for the Empirica Topics server.
    2. If the State of the server is RUNNING, shut down the server:
      1. Select the TopicsServer checkbox.
      2. Expand the Shutdown drop-down menu, and then select Force Shutdown Now.
      3. If prompted to confirm, click Yes.

        After a few moments, the State of the server is SHUTDOWN.

        Note: The page does not refresh automatically. To refresh the page, you can click the refresh button located above the table.

    3. Select the TopicsServer checkbox.
    4. Click Start.
    5. If prompted to confirm, click Yes.

      After a few moments, the State of the server is RUNNING.

      Note: The page does not refresh automatically. To refresh the page, you can click the refresh button located above the table.

Send Feedback