|
PageGate can be configured to run in three different styles: Application, Windows Service and PG Service.
We strongly recommend using the Windows Service or PG Service run styles.
Application
In this mode, PageGate is started and stopped just like any other program and can be automatically run at startup by putting a shortcut to it in the Windows "Startup" group. The disadvantage to this run style, is that if the computer is configured to show a login screen at startup, PageGate cannot automatically start until someone logs onto the computer.
Windows Service or PG Service
The 'Windows Service' run style tells PageGate to create a service for each component of the program.
The 'PG service' run style tells PageGate to create a single, master service that all elements of the program are run from.
Server 2016 and 2019: Use the 'PG Service' run style.
Desktop and Previous Server Versions: Use the 'Windows Service' or 'PG Service' run styles.
1)Right click on the shortcut for the PageGate Admin and select "Run as Administrator". 2)Go to the Program - Settings section of the Admin. 3)Under 'Run PageGate As', select: Windows Service or PG Service 4)Click Apply. 5)You should then be prompted for credentials. *See notes below. 6)When "Switching Run Styles" goes away, open the Windows Service list. 7)Find and start the PageGate service.
*Windows Credentials and PageGate
This is where things might get a little complicated because this part has more to do with how your network and/or domain are configured than anything native to PageGate; you're interacting with the Windows System Services. Having said that, you can typically use the Windows System Account to run PageGate's services. To do so, when you're prompted for credentials in step 5, leave the username and password fields blank and click on Apply again.
If leaving the username and password fields blank returns an "Invalid account or password" error, that means that the Windows System Account has been disabled and you must provide an appropriate username and password that has the "Create service" and "Log on as service" policies.
However, the Windows System Account typically has no network privileges and cannot access cross-network information.
If you have any component of the PageGate server referencing a network resource, like a file path by GetASCII or GetWeb APIs, the corresponding service must have sufficient rights to access those resources (in addition to the 'run as service' right).
In our experience, the easiest thing to do when you want to run PageGate as a service but need to have an interface or connector reference a network path is to have the system services created with the Windows System Account. Then, after the services exist, go in to the properties of the service that corresponds to the API or Connector and assign the service account under the Log On tab of the service.
When using the PG Service run style, you will only have a single, master PageGate service that will need a service account assigned to it.
|