Starting WebLogic and the Node Manager
Perform these steps using the non-privileged user account on the application server.
- 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.
- If WebLogic is running, stop WebLogic, for example:
$ ./stopWebLogic.sh
- 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.
- Identify the process ID for the Node Manager service, for example:
$ bash -c 'pgrep -f "java.+NodeManager -v$"'
- Stop the Node Manager, for example:
$ kill -9 <process_id_for_the_Node_Manager_service>
- For WebLogic 11g only, navigate to the
$WL_HOME/server/bin
directory, for example:$ cd /u01/app/oracle/Middleware/wlserver_10.3/server/bin
- Restart the Node Manager:
$ nohup ./startNodeManager.sh > /dev/null &
- Verify that the Node Manager is reachable:
- In an Internet browser, navigate to the WebLogic Server Administration Console, for example:
https://<servername>:7002/console
- Log in using the administrator credentials provided to you by the system administrator.
- In the Domain Structure pane, expand Environment, and select Machines.
The Summary of Machines page appears.
- Select SignalMachine.
The Settings for SignalMachine page appears.
- Select the Monitoring tab.
- 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.
- In an Internet browser, navigate to the WebLogic Server Administration Console, for example:
- In the Domain Structure pane, select Servers.
- Select the Control tab.
- Start or restart the Empirica Signal server using the Node Manager:
- In the table, review the State property for the Empirica Signal server.
- If the State of the server is RUNNING, shut down the server:
- Select the SignalServer checkbox.
- Expand the Shutdown drop-down menu, and then select Force Shutdown Now.
- 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.
- Select the SignalServer checkbox.
- Click Start.
- 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.
- If you use Empirica Topics, start or restart the Empirica Topics server using the Node Manager:
- In the table, review the State property for the Empirica Topics server.
- If the State of the server is RUNNING, shut down the server:
- Select the TopicsServer checkbox.
- Expand the Shutdown drop-down menu, and then select Force Shutdown Now.
- 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.
- Select the TopicsServer checkbox.
- Click Start.
- 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.
Copyright © 2002, 2017 Oracle and/or its affiliates. All rights reserved.