Workstation.config and NativeEngineLog.config files

The Workstation.config and NativeEngineLog.config files located in the \ProgramData\Infor\CPM\Workstation directory contain information about current CPM application's configurations. When you make changes to this file, the changes are not reflected in the interface until IIS is restarted. These files are not updated during CPM Server installation. The WorkstationSource.config and NativeEngineLogSource.config files, located in the same folder, contain updated default configurations and are always replaced during CPM Server installation.

By default, CPM Consolidation, Eliminations, and Ownership Calculation processes run as part of the CPM Financial Applications Engine (FAEngine) web service. FAEngine service is hosted, along with other .NET services, in a single IIS web application called CPMServices within the default CPM InforWebApps site. With complex and large consolidations, memory and CPU resources on the CPM web server can be better balanced by spreading the processes across multiple FAEngine(s), where each FAEngine service is assigned a dedicated application pool with each application pool using a dedicated log file. The AdditionalServiceName and AdditionalServiceCount parameters added to the Workstation.config can be used for load balancing purposes.

Configuration steps:

  1. If not yet included in the Workstation.config file, copy the parameter information from the WorkstationSource.config file.

    For example: 

    <Workstation>
    ..............
    
    <AdditionalServiceName value="CPMFAENGINE" desc="start name of additional FAEngineService Virtual Directories. e.g: CPMFAEngine1, CPMFAEngine2,..." />
<AdditionalServiceCount value="0" desc="number of CPMFAENGINE VDs." />
    
    ...........

  </Workstation>
  2. Specify the number of AdditionalServiceCount value as required by your application. For example, <AdditionalServiceCount value="5" desc="number of CPMFAENGINEs." />. In this case, there will be five additional services.
  3. Download and run the PMWebConfig.vbs script. See Knowledge Base article 603596 for further information.

  4. Upon successful execution with AdditionalServiceCount Value="5", the PMWebConfig.vbs script creates:

    • Five CPMFAEngine application pools (CPMFAEngine#AppPool)
    • Five CPMFAEngine services (CPMFAEngine#) within the InforWebApps site
    • Ffive NativeEngineLog.config files (NativeEngineLog_CPMFAEngine#.config)
    Note: The value for # ranges from 1 to 5.
  5. When a request is executed from the consolidation web page, CPM determines the appropriate application pool for the request and consolidation information is logged to the corresponding log file (Consolidation_CPMFAEngine#.log).

    Examples:

    • Consolidation running on CPMFAEngine1 logs into Consolidation_CPMFAEngine1.log
    • Consolidation running on CPMFAEngine2 logs into Consolidation_CPMFAEngine2.log