Page Comparison

...

...

1. You'll need to setup an Aptify user to run the App Server.
   If you do not have a user already setup for this, you can create a new user or update an existing user to have the proper permissions.
   Image RemovedImage Added
2. This user needs to have the Administrators and Application Servers security groups applied. Otherwise, it can use an End User license. Tie this user to an Employee record on the final step of the wizard.
3. Navigate to the Application Servers service under the Process Pipeline application. Create a new record.
   Image RemovedImage Added

4. Under Name, you can enter whatever you'd like to identify this application server record. Under Server Name, enter the Server Name. Note The Server Name field displays the server name as it appears on the network and the server that has the application server service running on it.
   For example, in the below given screenshot, this targets the default instance of the APTIFYDEV server which is the Aptify Development Server in this instance. 
   Image RemovedImage Added

   Info

   If using the Consulting-built Async Processor X, you will have two additional fields. Select Process Untargeted Runs if you wish this application server to pick up open jobs Enter your choice for ServiceName. It can be "AptifyAsyncProcessor" by default, or, if setting up backup async processes, something like "AptifyAsyncBackup1." Make a note of what you choose as it'll be used later. (Note, it must be unique per server, e,g, you cannot have two services named AptifyAsyncService on the same server, but you could have an AptifyAsyncService on two separate servers)

   
   

5. On the Account Information tab, enter in the username and password (including domain) of the Aptify User who will be running this Async service. This should either previously have been setup or setup in Instructions 1→4 above.
   Image RemovedImage Added
6. On the Account Information tab, enter the Account Name and Account Password (including domain) of the Aptify User who will be running this Async service. This should either previously have been setup or setup in Instructions 1→4 as given above.
7. Make a note of the Application Server ID record that was created.

...

1. Run Command Prompt as a Windows Administrator.
2. Copy and paste this value to somewhere on your local machine, e,g, a new tab of a browser.

   1. sc create AptifyAsyncProcessor binPath= "C:\Program Files\Aptify 5.0\AptifyAsyncProcessor.exe" DisplayName= "Aptify 5.0 Asynchronous Processor" start= auto

   2. When run in Command Prompt, this will generate your Async service. First, verify the values are correct per below.
3. The construct of this is sc create YourServiceName binPath= "LocationOfYourAptifyAsyncProcessor.exe file" DisplayName= "YourDisplayName" start=auto
4. Make the following changes to that text, if applicable.
   1. For example, if I want to create an Async Service with a different service name for the Consulting Async Service, my text might be:
      
      1. sc create AptifyAsyncBackupProcessor binPath= "C:\Program Files\Aptify 5.0\AptifyAsyncProcessor.exe" DisplayName= "Aptify Backup Asynchronous Processor" start= auto
      2. You'd then need to make sure your config file and Aptify Application Server record have the ServiceName of AptifyAsyncBackupProcessor and in the config file, appropriate Display Name
   2. If I wanted to create an Async Service running off a different Aptify 5.0 folder, my text might be:
      1. sc create AptifyAsyncProcessor binPath= "E:\Apps\AptifyAsync\AptifyAsyncProcessor.exe" DisplayName= "Aptify 5.0 Asynchronous Processor" start= autoImage RemovedImage Added
         Image RemovedImage Added
5. Once you have the right text, copy it.
6. Right-click and paste it into the Administrator Command Prompt, it should quickly say Success. It will have created your Windows Service here:Image RemovedImage Added
7. Now we need to set up the Async Processor to use the right user. Type Services.msc into the Windows Start Menu. Then double click the Aptify 5.0 Asynchronous Processor (or whatever yours is named).
   Image RemovedImage Added
8. Under the Logon tab, change it from Local System account to This Account and specify the username/password for the Aptify user account that runs the app server. This should be the same values that are on the Application Server Account Information tab.
   Image RemovedImage Added
9. On the Recovery Tab, you can specify optional actions if the service fails. At the minimum, it's recommended to setup Restart for the First and second failure.
10. Click Apply and OK.
    Image RemovedImage Added
11. Right-click the Async Service, and click start. (By default it'll start up with the server in the future) If it starts, great.
12. If it's having trouble logging into the database or executing certain files, it may immediately stop after starting. Check the Event Viewer on the Application Server for more details as well as the Event Viewer on the database server.
    1. The most common issue is usually the Aptify 5.0 folder running the Async service is out of sync with the Object Repository. Try performing a full object repository sync on the folder and logging in to confirm the Desktop client is functional.
       Image RemovedImage Added
    2. If using the Consulting version, double check the Aptify ApplicationServer ServiceName, the config file service name, and the service name in services.msc to confirm all 3 matches.
    3. If you need to delete your Windows Service to try and setup a different one, in an Administrator Command Prompt you can enter sc delete YourServiceName.