Starting and Stopping Theatre Manager

Theatre Manager consists of a few components that may be on one or more servers. It is a good idea to start and stop then in the appropriate order. If you do not and something is not working, then the best approach is to start at the beginning and perform the steps in the suggested order.

Order to Start Up components

Start the various server components of Theatre Manager in the following order:

1. The postgres database server, apache, and PC Charge credit card server are independent of each other. You can really start them in any order you want. They must all be running before you can start Theatre Manager on any machines.
2. Start Theatre Manager running on the web listeners
3. Allow other Theatre Manager users to log in on their machines or to connect to terminal services if using it remotely

Order to Stop components

Generally, you stop the components of Theatre Manage in the reverse order that you start it up.

1. Have all users quit Theatre Manager on all workstations
2. Stop Theatre Manager running on the web listener machines
3. Shut down or restart postgres, credit card server and apache server in any order you wish.

Some exceptions to the above

• If you want to restart apache server, you should stop all the web listeners first. You don't have to do anything special with the postgres or PC Charge servers. While the above is recommended, you can sometimes just:
  • restart the apache server
  • go to each web listener and click the 'stop server' button on the web listener interface
  • then click the 'start server' button on the web listener interface
• If you are not processing a credit card at an exact moment in time, you can stop and start PC Charge independently if you need to. Anybody trying to process a credit card while PC Charge is stopped will get a decline message.