Startup and Shutdown of Enterprise and iTopia

Overview

• This topic is intended to address startup and shutdown procedures for the various servers required by Enterprise, iTopia and WMS.

• Previous to version 6.20 of Enterprise iTopia was an optional package. This meant that Enterprise would be a hosted on a single server. As of Enterprise version 6.20 iTopia is an integral component of the solution. Although small installs may see Enterprise and iTopia installed on the same server, typically two servers are required, one for each product. The iTopia product requires Microsoft SQL which can be hosted on third server. With the addition of the Tecsys WMS package another server may be required.

• This topic is intended to address recommended startup and shutdown procedures for the various servers required by Enterprise, iTopia and WMS.

Virtual Servers

• Virtual servers are now very popular. There are several virtualization products available, VMware, Hyper-V and Citrix Zen to name a few. In all cases, the virtual servers must be treated as though they are actual physical machines. In the process of shutting down the physical or host server, all of the virtual servers must first be properly shut down. For startup, the virtualization product can be configured to start the virtual servers in a specific sequence. From this point on it is assumed that all servers will be individual physical servers.

Possible server configurations

• Single server
• Enterprise
• MS SQL
• iTopia
• SSRC Web Server

• PointForce iTopia and TECSYS WMS will usually share one Microsoft SQL server. Usually the WMS product will run on the SQL server. For very large installs the Microsoft SQL may be installed on its own server.

Recommended Startup Sequence of the Enterprise and iTopia Servers

Note: For all configurations, the server or servers hosting MS SQL should be brought up first.

1. SQL Server for PointForce iTopia
   • SSRC Webservice (uses its own single user PVX license)
     • Upon start-up the first Windows user to login will automatically launch 'SSRC’ (web service) – it must then remain active.
     • The Windows user should be the same one used that will be used to start 'nthost' on the Enterprise server (i.e. ‘pfadmin’).

2. WMS Servers (if present)
   • Start the MS SQL server. (If shared with iTopia it should already be running.)

   • Start the WMS application server (usually same server as SQL).
     • The WMS applications all start automatically as system services.

   • Start the WMS Terminal Server.

3. Enterprise Server
   • NTHOST – Windows Server Only (requires 1 PVX license).
     • Upon start-up the first Windows user to login will automatically start the 'NTHOST' program running – it must then remain active.
     • We suggest using 'pfadmin' for this task (although any Windows user with admin privileges on both the Enterprise and the iTopia servers will work).
     • TECSYS and the customer need to know the Windows 'pfadmin' password.
     • DO NOT use the 'pfiuser' account as it is to be used by TECSYS staff only.

   • RP10 (no additional PVX license required).
     • On the console log into Enterprise as the Enterprise operator 'pfadmin'.
     • Select company #11 (live company).
     • Type in RP10 and enter.
     • Select the 'Start' button to launch the application.

At this point the Enterprise application should be running and awaiting Enterprise users to login and begin working on the system. The replication program (RP10) should be running and keeping all Enterprise transactions up to date on the iTopia (SQL) server. The SSRC service should be running on the iTopia server passing information back and forth between the Enterprise data files and the SQL tables.

When Enterprise is installed on a Linux server there will be no 'NTHOST' program. Linux does not have a console that supports the Enterprise Client so RP10 and other service programs will have to be run from the console of one of the Windows Servers.

Additional Services (these can be Started and Stopped as required)

• AR38 (if you have the BluePay Credit Card add-on).
  • On the console log into Enterprise as the Enterprise operator 'pfadmin'.
  • Select company #11 (live company).
  • Type in AR38 and enter.
  • Select the 'Start' button to launch the application.

• CC33 (activates Evolve Event monitoring).
  • On the console log into Enterprise as the Enterprise operator 'pfadmin'.
  • Select company #11 (live company).
  • Type in CC33 and enter.
  • Select the 'Start' button to launch the application.

• EC33 (activates Shopping Cart monitoring).
  • On the console log into Enterprise as the Enterprise operator 'pfadmin'.
  • Select company #11 (live company).
  • Type in EC33 and enter.
  • Select the 'Start' button to launch the application.

• WM32 (activates WMS Data Transfer Server).
  • On the console log into Enterprise as the Enterprise operator 'pfadmin'.
  • Select company #11 (live company).
  • Type in WM32 and enter.
  • Select the 'Start' button to launch the application.

• WM33 (activates WMS Upload Transaction Processor).
  • On the console log into Enterprise as the Enterprise operator 'pfadmin'.
  • Select company #11 (live company).
  • Type in WM33 and enter.
  • Select the 'Start' button to launch the application.

Warning: When connected to a windows server using remote desktop, do not log off -- just disconnect.

• This is especially important when doing a Remote Desktop Session to the console of the Enterprise Server. When installed on a Windows server, ALL Enterprise tasks run as foreground tasks. If you were to log off then ALL Enterprise tasks would be terminated. Simply close the Remote Desktop window leaving all tasks running.

Recommended Shutdown Sequence of the Enterprise and iTopia Servers

Note: For all configurations, the server or servers hosting MS SQL should be shutdown last.

1. Ensure that all Enterprise/iTopia users are properly logged out.
   1. Ensure no Enterprise task icons are displayed on the console task bar.

2. From the Enterprise console stop and exit RP10.
   1. Stop and exit any other services tasks that may be running (i.e. AR38, CC33, EC33, WM32, WM33).
   2. Right click NTHOST icon and select Close.
   3. Perform the shutdown on the Enterprise server.

3. On the iTopia SQL server select SSRC and stop it.

4. Perform the shutdown on the iTopia server.

5. If WMS is installed, ensure all WMS users are properly logged out.
   1. Shutdown the WMS Terminal Server.
   2. Shutdown the WMS Application Server.
   3. Shutdown the WMS SQL Server.

Notes:

• This topic assumes that all services (except SSRC) are running on the Enterprise Server.

• Should you wish to shut down the iTopia Server only:
  • Ensure everyone logs out of iTopia.
  • Stop RP10 on the Enterprise Server.
  • Select SSRC on the iTopia Server and Stop it.
  • Perform normal shutdown of the iTopia Server.
    • Use normal startup procedure to restart - plus restart RP10.

• Should you wish to shut down the Enterprise Server only:
  • Follow options 1 and 2 above.
    • Use normal startup procedure to restart – plus any additional services (I.e. AR38, etc.).

• Where Enterprise is installed on Linux all of the service tasks should be running on one of the Windows Servers, usually the iTopia Server.

• Where WMS is installed and sharing a SQL server with iTopia, do not shut down the SQL server without first properly shutting down WMS and vice versa.