During the setup process, restarting the neoCatalog service is necessary multiple times to ensure the setup and configuration changes take effect. There are two available methods for restarting the neoCatalog service:

(A) Automated Restart via JavaMonitor: This can be performed remotely through a web browser. Utilize JavaMonitor to initiate the automated restart.

(B) Manual Restart from the Terminal on the Server: Access the server's terminal to manually restart the neoCatalog service.

If the neoCatalog service stops, you will observe a "Service Unavailable" message in your web browser. In such cases, it's essential to follow one of the restarting options to restore service functionality.

(A) Restart neoCatalog Service from JavaMonitor

In order to (re)start neoCatalog, please follow the steps:

1. Go to the web browser and enter http://localhost:56789. This path will open the WOMonitor in JavaMonitor, where you can see the installed instances. Click on 'View Details' on the instance that you want to (re)start.

2. Next you will see the detailed instance of neoCatalog.

3. To quit the instance, in case of restarting neoCatalog, press 'Configure' and push 'Force Quit This Instance' (down the page).

4. Now the application is stopped. To go back to the application details and see the running status, you will need to push Details View (up the page):

5. If the quitting instance was successful, the status will be OFF. To start the instance, push the green button in the column Start-Stop, which will restart the instance. The page automatically updates every 60 seconds. To speed up the Status push Refresh Now. If quitting the instance failed here, please restart neoCatalog via terminal, option B.

6. When the instance is restarted the status will be ON and green. Go to http://localhost/. neoCatalog is ready to use.

(B) Manual restart from Terminal

If the instance does not restart from JavaMonitor, please follow the steps.

1. Open the terminal command on the neoCatalog server, type cd /Library/LaunchDaemons/ and confirm by pressing enter.

2. After you enter LaunchDaemons, start typing the commands to quit and restart the neoCatalog Service. These commands must run with sudo and confirm by pressing enter. You are required to enter the system user password:
sudo launchctl unload org.projectwonder.womonitor.plist 
sudo launchctl unload org.projectwonder.wotaskd.plist
sudo launchctl load org.projectwonder.womonitor.plist
sudo launchctl load org.projectwonder.wotaskd.plist
sudo apachectl restart

3. You can go to http://localhost/ and refresh the browser. After a few seconds, the application will start and neoCatalog is ready to use.

Troubleshooting: Cannot Stop/Start neoCatalog Service

(A) Restart JavaMOnitor

If the neoCatalog service does not stop or start following the initial troubleshooting steps (Option A and B), follow these additional steps:

1. Attempt to access the instance service http://localhost:2002 (the port of the distance can differ).

2a. For macOS:

  • If no service is running, open the Activity Monitor.
  • Search for 'Java' and force quit all instances.

2b. For Windows:

  • Open the Task Manager.
  • Restart the JavaMonitor service from the Services tab.

3. Return to http://localhost:56789 and attempt to start the instance.

4. If the issue persists:

  1. Check the last log.
    • For Windows: Navigate to C:\Library\WebObjects\Logs.
    • For macOS: Navigate to /Library/WebObjects/Logs.
  2. Look for the following error: `er.extensions.migration.ERXMigrationFailedException: Migration failed.`

(B) Restart Apache Service

Special cases may arise where instances don't start despite being in the ON state due to ongoing usage. Follow these steps to restart the applications as needed:

  1. Open the Services and stop the Apache service.
  2. Navigate to Task Manager > Details and terminate all java.exe processes, excluding those consuming low memory (less than 200KB).
  3. Return to Services and start the Apache service.
  4. Proceed to start the launcher.

Please note that simply restarting the server will not resolve this issue since users might be attempting to access the application before it fully starts, causing a blockage. Hence, stopping and restarting the Apache service is necessary in this scenario.