Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

If you want to change an Application Server's configuration after installation, you need to modify the AptifyAsyncProcessor.exe.config file. This file is located in the Aptify program files directly on the Application Server.
Follow these steps to modify the configuration file:

  1. Locate the AptifyAsyncProcessor.exe.config file on the Application Server.
    • If you installed the Aptify Application Server and Client components in the default directory, you can find the file in the following location: C:\Program Files\Aptify 67.40\AptifyAsyncProcessor.exe.config
       
  2. Open AptifyAsyncProcessor.exe.config with Notepad.
  3. Edit the Application Server's configuration settings. The Application Server configures the following parameters:
    • Record Events: (Aptify.Framework.BusinessLogic.ProcessPipeline.AptifyAsyncProcessor.RecordEvents) If you want to record information associated with Application Servers activities to the computer's Application Event Log, change this value from 0 to 1. The Application Event log is available at Start > Control Panel > Administrative Tools > Event Viewer > Application.
    • Process Untargeted Runs: (Aptify.Framework.BusinessLogic.ProcessPipeline.AptifyAsyncProcessor.ProcessUntargettedRuns) When set to 0, the application server will only execute Process Flow Runs that are assigned to it. When set to 1, the application server will execute Process Flow Runs that are unassigned as well as those that are specifically assigned to it. Note that within an organization, at least one Application Server instance should have the Process Untargeted Runs option enabled. See About the Process Untargeted Runs Setting.
    • Maximum Worker Threads: (Aptify.Framework.BusinessLogic.ProcessPipeline.AptifyAsyncProcessor.AvailableWorkerThreads) Specify the maximum number of working threads that the Application Server can process simultaneously. Each Process Flow Run corresponds to one thread on the Application Server. An Application Server will only accept a Process Flow Run for processing if it has a thread available. See About the Maximum Worker Threads Setting.
    • Polling Interval: (Aptify.Framework.BusinessLogic.ProcessPipeline.AptifyAsyncProcessor.ProcessFlowRunsPollingInterval) Specify the Polling Interval in the field provided in milliseconds. See About the Application Server Polling Interval.

      Info

      The Allow Client to Download Objects parameter is configured within the Aptify.xml file (which can be opened and edited with Notepad). See About the Allow Client to Download Objects Parameter for details.


      Note

      The settings in the ClientSettingsProvider.ServiceUri section is to support the introduction of .NET 4.5. The settings in this section are used by the ASP.NET Membership Provider.  The Aptify Application Server does not use the Membership Provider. There is no need to apply any settings to this section.


  4. Add the below-given attribute:

    <add key="Aptify.Framework.BusinessLogic.ProcessPipeline.AptifyAsyncProcessor.GetAttributeValuesFromAptify" value="1"/> <add key="Aptify.Framework.BusinessLogic.ProcessPipeline.AptifyAsyncProcessor.RestartAfterMinutes" value="0"/> <add key="Aptify.Framework.BusinessLogic.ProcessPipeline.AptifyAsyncProcessor.RestartAfterProcessFlowRunsCount" value="0"/>

  5. Save and close AptifyAsyncProcessor.exe.config.

    Note

    When adding an instance, at least one instance will need to have the ProcessUntargetedRuns setting in the AptifyAsyncProcessor.exe.config file updated (set to 1) to process runs that are not targeted at a specific Application Server. See About the Process Untargeted Runs Setting for more information. Users may also need to configure the additional attributes per the specifications in Modifying AptifyAsyncProcessor.exe.config.


  6. Click Start > Control Panel > Administrative Tools > Services.
  7. Right-click the Aptify Asynchronous Processor service.
  8. Select Restart from the drop-down menu to restart the service.
    • Changes to the config file do not take effect until the service is restarted.