Configuring performance tuning parameters

You can configure the performance tuning parameters on the Certified Container deployments using a basic approach or an advance approach. For more information, see the following sections.

Configuring performance tuning parameters

Important:

If the resources section is disabled, any custom tuning configurations is not applied and the system starts with the default settings, which comes as part of IIM installations.

After installation, you can refer below files generated under the volume mapped to Certified Container’s resources directory, /ibm/resources, to check for calculated and suggested settings for Performance Tuning parameters.

This is the same volume specified via appResourcesPVC section in values.yaml.
asi-tuning-suggested
asi-tuning-calulated 
ac-tuning-suggested
ac-tuning-calulated 

The asi-tuning-suggested and ac-tuning-suggested files contains the system suggested values for all the tuning properties which are available on the Performance Tuning UI for ASI server nodes and Adapter Container nodes respectively.

The asi-tuning-calulated and ac-tuning-calulated files contains the calculated and applied values for all the tuning properties which are available on the Performance Tuning UI for ASI server nodes and Adapter Container nodes respectively.

The calculated and suggested tuning properties only for ASI containers/pods can also be seen on the existing Performance Tuning UI in VIEW mode.

In some cases, during the product installation using certified containers, somehow, if any invalid configurations found around the performance tuning values which disregards the functional validations, then installation would be aborted with proper validation error message.

For example:

In basic approach, if you just provides the Initial Heap Size, using override sections in values.yaml then during install time, it will be compared to Maximum Heap Size and if that Initial Heap Size happens to be greater than Maximum Heap Size, then installation will be aborted.

Note:
  • If appdefinedPVCs are present, then they will be reused.
  • If you already have custom defined or pre defined PVCs, then it can be configured using the key: preDefinedResourcePVCName, preDefinedLogsPVCName, or preDefinedDocumentPVCName.
  • In case you have both appdefinedPVCs and preDefinedPVCs, then the preDefinedPVCs will take precedence.
  • To support pod level PVC, set enableVolumeClaimPerPod to true in appDocumentsPVC, extraPVCs, asi.extraPVCs, ac.extraPVCs, and api.extraPVCs.
  • When enableVolumeClaimPerPod is enabled, make use of the dynamic storage class so that PVs and PVC's are created dynamically based on the storage provisioner used.
  • The default value for enableVolumeClaimPerPod is false.

Basic Approach

The basic approach is used to configure the performance tuning parameters for Certified Container deployments. You can edit the asi.performanceTuning and ac.performanceTuning sections in the Sterling B2B Integrator helm chart values.yaml file to configure the basic tuning parameters for ASI and AC respectively. This is required to boot up the Sterling B2B Integrator environment with the recommended tuning settings.

Option to override the recommended settings is also available for ASI Certified Container.
For example:
asi:  
  performanceTuning:
    allocateMemToBI: false
    allocateMemToSAP: true
    allocateMemToCLA: true
    threadsPerCore: 4
    override:
      - NOAPP.INITIAL_CYCLES_7=10
      - NOAPP.EXEC_CYCLE_7=10

In the above example, you are setting the flags for allocateMemToBI , allocateMemToSAP and allocateMemToCLA to control the allocation of the memory for BI Listeners, SAP Adapter and Command Line Adapter respectively. If not specified, the default value is false for all the three flags.

threadsPerCore determines the number of threads per core which usually helps in calculating Desired Global Threads and Distribution Cache Minimum. If not specified, the default value is 4.

override section will help you to override the suggested value by the system.

In the given example, you are overriding Initial Steps in the first Execution Cycle (NOAPP.INITIAL_CYCLES_7) and Number of Steps in the Execution Cycle (NOAPP.EXEC_CYCLE_7) for Queue 7 with our own custom values.

Refer to Sample properties template to know the property names. You can also find out the mapping between fields on Performance Tuning UI and the properties using the UI_LABEL tag.

The fundamental properties needed to calculate the tuning parameters which are memory and cores, are fetched internally from asi.resources.requests and ac.resources.requestssections in values.yaml.

If you need to update the basic performance tuning properties on a running instance of ASI or AC, then you must edit the same in values.yaml , and run below helm upgrade command to apply the changes.
helm upgrade <release-name> /path/to/chart 

Advance Approach

The advance approach can also be used to configure the performance tuning parameters for Certified Container deployments.

Under advance approach, we are introducing a new tuning utility which user can run to calculate the performance tuning parameters.

This utility is a standalone independent runnable jar which can be executed on any java platform which satisfies the minimum JRE version requirement.

Note: JRE 8 or later must be used to use this utility.
You can download tuning-utils-1.0.jar and follow these steps to start using it:
  1. Place the tuning-utils-1.0.jar at any location on your local machine.
  2. Make sure to fulfill the minimum JRE version requirement.
  3. Run below command.
    java -jar /path/to/tuning-utils-1.0.jar
  4. Provide the inputs to the queries asked by utility.
After the setup is complete, based on the server type selected, the system creates a folder that contains calculated tuning and suggested tuning files under the current working directory.
tuningoutput/
	ac-tuning-calculated  
       ac-tuning-suggested
asi-tuning-suggested
asi-tuning-suggested

<serverType>-tuning-calculated holds the performance tuning values which are calculated based on the user inputs.
<serverType>-tuning-suggested holds the performance tuning values which are suggested by the utility.
If you use the suggested values for spare memory and ASI/AC memory, then calculated and suggested files holds the same tuning values.
sample execution for server type ac
$> java -jar .\tuning-utils-1.0.jar
Provide server type [asi|ac] ?
ac
Total memory in MB ?
4000
Spare memory in MB to deduct from total memory. Leave blank to use default value(500 MB) ?

Allocate memory to SAP Adapter [true|false]?
true
Number of Processors in the system ?
2


Net total memory :3500
Suggested memory for AC = 3116 MB


AC memory (Leave blank to use suggested value) ?

Tuning Configuration started.

Initialisation done for AC tuning handler.
All properties file loaded.
Recommended Tuning calculation done.
Total time to configure Tuning parameters :271 ms.
Note:
  • Total Memory is the memory allocated to the Pod in MB.
  • Spare Memory is the amount of memory to be deducted from total memory allocated to the Pod, so that Pod has some free space to cater some internal processes if any.
  • Number of Processors are the cores allocated to the Pod.
  • Number of threads per core is needed to calculate Desired Global Threads and Distribution Cache Minimum.

After you have successfully run the tuning-utils-1.0.jar and calculated the Performance tuning parameter, you can use the same configurations for your Sterling B2B Integrator Certified Container deployment.

Follow these steps:

  1. Select either <serverType>-tuning-calculated or <serverType>-tuning-suggested file based on your requirement decision and rename it to <serverType>-tuning.properties where <serverType> can be either asi or ac.
  2. You can override some values in the file if needed. (Optional)
  3. Copy the asi(ac)-tuning.properties to the config folder in the B2BI/SFG helm charts.
  4. Perform a helm upgrade to apply the tuning parameters inside application pods (ASI/AC).
    helm upgrade <release-name> /path/to/chart –-recreate-pods

Sample properties template

You can refer the below sample properties template to check what tuning properties can be configured using either basic or advance approaches.

ac-tuning.template:

############################################################################
#(C) Copyright 2021 Syncsort Incorporated. All rights reserved.
############################################################################
## PROPERTY_FILE_NAME
## tuningDefaults.properties (for initialization and operations)
## PROPERTY_FILE_DESCRIPTION
##

## PROPERTY_START
## PROPERTY_NAME: MEMORY 
## PROPERTY_TYPE: Integer
## UI_LABEL: Physical memory (MB) allocated to Sterling B2B Integrator
## PROPERTY_DESCRIPTION
## Amount of memory allocated for use in processing operations.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END

## PROPERTY_START
## PROPERTY_NAME: PROCESSORS 
## PROPERTY_TYPE: Integer
## PROPERTY_DESCRIPTION
## Number of processor cores in the system, where each core is an 
## independent processing engine.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.INIT_HEAP_CONTAINER 
## PROPERTY_GROUP: JVM Memory Settings for Container Nodes
## PROPERTY_TYPE: Integer
## UI_LABEL: Initial Heap Size (MB)
## PROPERTY_DESCRIPTION
## Initial heap - 64 bit container.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.MAX_HEAP_CONTAINER 
## PROPERTY_GROUP: JVM Memory Settings for Container Nodes
## PROPERTY_TYPE: Integer
## UI_LABEL: Maximum Heap Size (MB)
## PROPERTY_DESCRIPTION
## Maximum heap - 64 bit container.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.MAX_PERM_SIZE_CONTAINER 
## PROPERTY_TYPE: Integer
## UI_LABEL: Maximum Permanent Generation Size (MB)
## PROPERTY_DESCRIPTION
## Maximum permanent generation size - 64 bit.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.STATIC_STACK_CONTAINER 
## PROPERTY_TYPE: Integer
## UI_LABEL: Thread Stack Size (KB)
## PROPERTY_DESCRIPTION
## Controls the maximum Java stack size for any thread in a 64-bit environment (KB).
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: ENABLE_VERBOSE_GC_CONTAINER 
## PROPERTY_GROUP: Heap Dump Container
## PROPERTY_TYPE: Boolean
## UI_LABEL: Enable VerboseGC
## PROPERTY_DESCRIPTION
## Indicates whether to generate verbose garbage collection data for container JVM.
## Valid values:
## true : Generate verbose garbage collection data.
## false : (default) Disable verbose garbage collection. 
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: JVM_ARGS_SUFFIX_CONTAINER 
## PROPERTY_GROUP: JVM Parameters for Container Nodes Page 
## PROPERTY_TYPE: String
## UI_LABEL: JVM Arguments Suffix
## PROPERTY_DESCRIPTION
## JVM arguments suffix container.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: JVM_ARGS_PREFIX_CONTAINER 
## PROPERTY_GROUP: JVM Parameters for Container Nodes Page 
## PROPERTY_TYPE: String
## UI_LABEL: JVM Arguments Prefix
## PROPERTY_DESCRIPTION
## JVM arguments prefix container.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: ENABLE_HEAP_DUMP_OOM_CONTAINER
## PROPERTY_GROUP: JVM Parameters for Container Page 
## PROPERTY_TYPE: Boolean
## UI_LABEL: Enable Heap Dump on Out of Memory
## PROPERTY_DESCRIPTION
## Indicates if you want to generate a heap dump when the container JVM
## encounters an out of memory error.
## Valid values:
## true :  (default) Generate a heap dump.
## false : Do not generate a heap dump.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: ENABLE_HEAP_DUMP_SGQTCRTLBRK_CONTAINER
## PROPERTY_GROUP: JVM Parameters for Container Page 
## PROPERTY_TYPE: Boolean
## UI_LABEL: Enable Heap Dump on Sigquit/Ctrl-break
## PROPERTY_DESCRIPTION
## Indicates whether to enable the heap dump on Sigquit/Ctrl-break.
## Valid values:
## true :  (default) Enable the heap dump.
## false : Do not enable the heap dump.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.INIT_AGE_CONTAINER 
## PROPERTY_TYPE: Integer
## UI_LABEL: Initial Size of New (Nursery) Heap (MB)
## PROPERTY_DESCRIPTION
## The initial size of the new heap area allocated to each server JVM.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.MAX_AGE_CONTAINER
## PROPERTY_TYPE: Integer
## UI_LABEL: Maximum Size of New (Nursery) Heap (MB)
## PROPERTY_DESCRIPTION
## Maximum new age.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: MEMORY_CONTAINER
## PROPERTY_TYPE: Integer
## UI_LABEL: Physical Memory Allocated to Container (MB)
## PROPERTY_DESCRIPTION
## 
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END

## PROPERTY_START
## PROPERTY_NAME: IS_DEDUCT_MEM_SAPADAPTER 
## PROPERTY_TYPE: Boolean
## UI_LABEL: Allocate memory for SAP Adapter
## PROPERTY_DESCRIPTION
## Indicates if you want to allocate memory for the SAP adapter
## from the physical memory allocated to the application.
## Valid values:
## true : Allocate memory for the SAP adapter.
## false : (default) Do not allocate memory for the SAP adapter.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END

## PROPERTY_VALUE_ALL

MEMORY=##MEMORY##
PROCESSORS=##PROCESSORS##
IS_DEDUCT_MEM_SAPADAPTER=##IS_DEDUCT_MEM_SAPADAPTER##

###########################################################
#Performance Tuning: JVM Parameters Container Nodes
###########################################################

MEMORY_CONTAINER=##MEMORY_CONTAINER##
Linux-64.INIT_HEAP_CONTAINER=##Linux-64.INIT_HEAP_CONTAINER##
Linux-64.MAX_HEAP_CONTAINER=##Linux-64.MAX_HEAP_CONTAINER##

Linux-64.INIT_AGE_CONTAINER=##Linux-64.INIT_AGE_CONTAINER##
Linux-64.MAX_AGE_CONTAINER=##Linux-64.MAX_AGE_CONTAINER##

Linux-64.MAX_PERM_SIZE_CONTAINER=##Linux-64.MAX_PERM_SIZE_CONTAINER##
Linux-64.STATIC_STACK_CONTAINER=##Linux-64.STATIC_STACK_CONTAINER##

ENABLE_HEAP_DUMP_OOM_CONTAINER=##ENABLE_HEAP_DUMP_OOM_CONTAINER##
ENABLE_HEAP_DUMP_SGQTCRTLBRK_CONTAINER=##ENABLE_HEAP_DUMP_SGQTCRTLBRK_CONTAINER##
ENABLE_VERBOSE_GC_CONTAINER=##ENABLE_VERBOSE_GC_CONTAINER##

JVM_ARGS_SUFFIX_CONTAINER=##JVM_ARGS_SUFFIX_CONTAINER##
JVM_ARGS_PREFIX_CONTAINER=##JVM_ARGS_PREFIX_CONTAINER##

asi-tuning.template:

############################################################################
#(C) Copyright 2021 Syncsort Incorporated. All rights reserved.
############################################################################
## PROPERTY_FILE_NAME
## tuningDefaults.properties (for initialization and operations)
## PROPERTY_FILE_DESCRIPTION
##

## PROPERTY_START
## PROPERTY_NAME: MEMORY 
## PROPERTY_TYPE: Integer
## UI_LABEL: Physical memory (MB) allocated to Sterling B2B Integrator
## PROPERTY_DESCRIPTION
## Amount of memory allocated for use in processing operations.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: PROCESSORS 
## PROPERTY_TYPE: Integer
## UI_LABEL: Number of Processor Cores
## PROPERTY_DESCRIPTION
## Number of processor cores in the system, where each core is an 
## independent processing engine.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.INIT_HEAP 
## PROPERTY_TYPE: String
## UI_LABEL: Initial Heap Size (MB)
## PROPERTY_DESCRIPTION
## The initial size of a Java heap allocated to each server JVM - 64-bit.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.MAX_HEAP 
## PROPERTY_TYPE: String
## UI_LABEL: Maximum Heap Size (MB)
## PROPERTY_DESCRIPTION
## Maximum heap - 64-bit.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.MAX_PERM_SIZE 
## PROPERTY_TYPE: Integer
## UI_LABEL: Maximum Permanent Generation Size (MB)
## PROPERTY_DESCRIPTION
## Maximum permanent generation size - 64-bit.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.STATIC_STACK 
## PROPERTY_TYPE: Integer
## UI_LABEL: Thread Stack Size (KB)
## PROPERTY_DESCRIPTION
## Controls the maximum Java stack size for any thread in a 64-bit environment (KB).
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: ENABLE_HEAP_DUMP_OOM 
## PROPERTY_GROUP: Heap Dump
## PROPERTY_TYPE: Boolean
## UI_LABEL: Enable Heap Dump on Out of Memory
## PROPERTY_DESCRIPTION
## Indicates whether to generate a heap dump when the server JVM
## encounters an out-of-memory error.
## Valid values:
## true : (default) Generate a heap dump. 
## false : Do not generate a heap dump.  
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: ENABLE_HEAP_DUMP_SGQTCRTLBRK 
## PROPERTY_GROUP: Heap Dump
## PROPERTY_TYPE: Boolean
## UI_LABEL: Enable Heap Dump on Sigquit/Ctrl-break
## PROPERTY_DESCRIPTION
## Indicates if you want to request a heap dump for the server
## JVM by using the Sigquit command or by pressing Ctrl+Break 
## for the server JVM.
## Valid values:
## true : (default) Request a heap dump. 
## false : Do not request a heap dump.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: ENABLE_VERBOSE_GC 
## PROPERTY_GROUP: Heap Dump
## PROPERTY_TYPE: Boolean
## UI_LABEL: Enable VerboseGC
## PROPERTY_DESCRIPTION
## Indicates whether to generate verbose garbage collection data for server JVM.
## Valid values:
## true : Generate verbose garbage collection data.
## false : (default) Disable verbose garbage collection. 
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: NOAPP.JMS_PAGING_MAX 
## PROPERTY_TYPE: Integer
## UI_LABEL: Disk cache size (MB) Maximum
## PROPERTY_DESCRIPTION
## JMS paging maximum.  This is now the DISK cache size. It is set twice to the memory size of the 
## application.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: NOAPP.JMS_PAGING_HIGH 
## PROPERTY_TYPE: Integer
## UI_LABEL: In memory cache size (MB) for small contexts
## PROPERTY_DESCRIPTION
## JMS paging high.  The memcache size.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: MULTICAST_INTERVAL                   
## PROPERTY_GROUP: BP Queue and Cluster                
## PROPERTY_TYPE: Integer
## UI_LABEL: Broadcast Interval (ms)              
## PROPERTY_DESCRIPTION                
## Broadcast interval (in milliseconds).               
## (For property value, see PROPERTY_VALUE_ALL section at end of file)      
## PROPERTY_END                
                       

## PROPERTY_START              
## PROPERTY_NAME: DISTRIBUTION_CACHE_MIN               
## PROPERTY_GROUP: BP Queue and Cluster                
## PROPERTY_TYPE: Integer
## UI_LABEL: Distribution Cache Minimum              
## PROPERTY_DESCRIPTION                
## Minimum distribution cache.                 
## (For property value, see PROPERTY_VALUE_ALL section at end of file)      
## PROPERTY_END                

                       
## PROPERTY_START              
## PROPERTY_NAME: SWITCH_INTERVAL              
## PROPERTY_GROUP: BP Queue and Cluster                
## PROPERTY_TYPE: Integer   
## UI_LABEL: Switch Interval (ms)           
## PROPERTY_DESCRIPTION                
## Switch interval (in milliseconds).                  
## (For property value, see PROPERTY_VALUE_ALL section at end of file)     
## PROPERTY_END                

   
## PROPERTY_START              
## PROPERTY_NAME: MAX_SHADOW_CACHE_SIZE                
## PROPERTY_GROUP: BP Queue and Cluster
## PROPERTY_TYPE: Integer
## UI_LABEL: Shadow Cache Size (MB) Maximum              
## PROPERTY_DESCRIPTION                
## Maximum shadow cache size (MB).             
## (For property value, see PROPERTY_VALUE_ALL section at end of file)       
## PROPERTY_END                

 
## PROPERTY_START              
## PROPERTY_NAME: USE_SHADOW_CACHE             
## PROPERTY_GROUP: BP Queue and Cluster                
## PROPERTY_TYPE: Boolean   
## UI_LABEL: Use Shadow Cache           
## PROPERTY_DESCRIPTION                
## Indicates whether to use shadow cache.              
## Valid values:               
## true : (default) Enable shadow cache.               
## false : Enable shadow cache.                
## (For property value, see PROPERTY_VALUE_ALL section at end of file)     
## PROPERTY_END                

                     
## PROPERTY_START              
## PROPERTY_NAME: WF_IN_TRANSIT_TIMEOUT_LIST                   
## PROPERTY_GROUP: BP Queue and Cluster
## PROPERTY_TYPE: Integer     
## UI_LABEL: Workflow in transit list timeout (ms)         
## PROPERTY_DESCRIPTION                
## Workflow in transit list (in milliseconds).                 
## (For property value, see PROPERTY_VALUE_ALL section at end of file)     
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: MAP_CACHE 
## PROPERTY_TYPE: String
## UI_LABEL: Translation maps
## PROPERTY_DESCRIPTION
## Translation map cache.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: ENVELOPE_CACHE 
## PROPERTY_TYPE: String
## UI_LABEL: Envelopes
## PROPERTY_DESCRIPTION
## Envelope cache.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START   		 
## PROPERTY_NAME: BP_SIZE 
## PROPERTY_TYPE: Integer
## UI_LABEL: Memory Cache Threshold (MB)
## PROPERTY_DESCRIPTION
## The average business process size in bytes.  This size  
## is bigger on Windows.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: JMS_LISTNERS 
## PROPERTY_TYPE: String
## UI_LABEL: Desired Global Threads
## PROPERTY_DESCRIPTION
## Queue threads.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: NOAPP.MAX_POOL_SIZE_[number]
## PROPERTY_TYPE: Integer
## UI_LABEL: Maximum Threads
## PROPERTY_DESCRIPTION
## Maximum number of threads available for the queue.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: NOAPP.MIN_POOL_SIZE_[number]
## PROPERTY_TYPE: Integer
## UI_LABEL: Minimum Threads
## PROPERTY_DESCRIPTION
## Minimum number of threads available for the queue.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: NOAPP.EXEC_CYCLE_[number]
## PROPERTY_TYPE: Integer
## UI_LABEL: Number of Steps in the Execution Cycle 
## PROPERTY_DESCRIPTION
## Number of business process steps that are run before returning to the queue.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: NOAPP.INITIAL_CYCLES_[number]
## PROPERTY_TYPE: String
## UI_LABEL: Initial Steps in the first Execution Cycle 
## PROPERTY_DESCRIPTION
## Number of steps executed before returning a business process to the queue 
## on its first execution cycle.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: NOAPP.RESOURCE_ALLOCATION_[number]
## PROPERTY_TYPE: Integer
## UI_LABEL: Resource Allocation
## PROPERTY_DESCRIPTION
## Amount of resources to allocate to a specific queue for fair share scheduling.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.INIT_AGE 
## PROPERTY_TYPE: Integer
## UI_LABEL: Initial Size of New (Nursery) Heap (MB)
## PROPERTY_DESCRIPTION
## The initial size of the new heap area allocated to each server JVM.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: [operating system]-64.MAX_AGE 
## PROPERTY_TYPE: Integer
## UI_LABEL: Maximum Size of New (Nursery) Heap (MB)
## PROPERTY_DESCRIPTION
## Maximum new age.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: JVM_ARGS_SUFFIX
## PROPERTY_TYPE: String
## UI_LABEL: JVM Arguments Suffix
## PROPERTY_DESCRIPTION
## JVM arguments suffix.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: JVM_ARGS_PREFIX
## PROPERTY_TYPE: String
## UI_LABEL: JVM Arguments Prefix
## PROPERTY_DESCRIPTION
## JVM arguments prefix.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: DISTRIBUTION_CACHE_MAX
## PROPERTY_GROUP: BP Queue Page
## PROPERTY_TYPE: Integer
## UI_LABEL: Distribution Cache Maximum
## PROPERTY_DESCRIPTION
## Maximum distribution cache.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: EDI_CACHE 
## PROPERTY_GROUP: Cache Page 
## PROPERTY_TYPE: Integer
## UI_LABEL: Other EDI
## PROPERTY_DESCRIPTION
## EDI cache.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: WFD_CACHE
## PROPERTY_GROUP: Cache Page 
## PROPERTY_TYPE: Integer
## UI_LABEL: Workflow Definition
## PROPERTY_DESCRIPTION
## Workflow definition cache.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: USER_CACHE
## PROPERTY_GROUP: Cache Page 
## PROPERTY_TYPE: Integer
## UI_LABEL: User Cache
## PROPERTY_DESCRIPTION
## User cache.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: GROUP_CACHE
## PROPERTY_GROUP: Cache Page 
## PROPERTY_TYPE: Integer
## UI_LABEL: Group Cache
## PROPERTY_DESCRIPTION
## Group cache.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: PERM_CACHE
## PROPERTY_GROUP: Cache Page 
## PROPERTY_TYPE: Integer
## UI_LABEL: Permission Cache
## PROPERTY_DESCRIPTION
## Permission cache.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: PURGE.DEADLOCK_RETRIES
## PROPERTY_GROUP: Purge Settings Page
## PROPERTY_TYPE: Integer
## UI_LABEL: Number of Purge Deadlock Retries
## PROPERTY_DESCRIPTION
## Number of purge deadlock retries.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: PURGE.MAX_PURGE_THREADS
## PROPERTY_GROUP: Purge Settings Page
## PROPERTY_TYPE: Integer
## UI_LABEL: Maximum Purge Threads
## PROPERTY_DESCRIPTION
## Maximum purge threads.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: PURGE.PURGE_DOCS_ON_DISK
## PROPERTY_GROUP: Purge Settings Page
## PROPERTY_TYPE: Boolean
## UI_LABEL: Purge Documents on Disk
## PROPERTY_DESCRIPTION
## Indicates whether to purge documents on disk.
## Valid values:
## true : (default)
## false : 
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: MEMORY_ASI
## PROPERTY_TYPE: Integer
## UI_LABEL: Physical Memory Allocated to Server (MB)
## PROPERTY_DESCRIPTION
## Memory values for various JVMs.
## (For property value, see PROPERTY_VALUE_ALL section at end of file)
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: IS_DEDUCT_MEM_BI 
## PROPERTY_TYPE: Boolean
## UI_LABEL: Allocate memory for BI Listeners
## PROPERTY_DESCRIPTION
## Indicates if you want to allocate memory for BI listeners
## from the physical memory allocated to the application.
## Valid values:
## true : Allocate memory for BI listeners.
## false : (default) Do not allocate memory for BI listeners.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: IS_DEDUCT_MEM_CLADAPTER 
## PROPERTY_TYPE: Boolean
## UI_LABEL: Allocate memory for Command Line Adapter
## PROPERTY_DESCRIPTION
## Indicates if you want to allocate memory for the command line adapter
## from the physical memory allocated to the application.
## Valid values:
## true : Allocate memory for the command line adapter.
## false : (default) Do not allocate memory for the command line adapter.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: IS_DEDUCT_MEM_SAPADAPTER 
## PROPERTY_TYPE: Boolean
## UI_LABEL: Allocate memory for SAP Adapter
## PROPERTY_DESCRIPTION
## Indicates if you want to allocate memory for the SAP adapter
## from the physical memory allocated to the application.
## Valid values:
## true : Allocate memory for the SAP adapter.
## false : (default) Do not allocate memory for the SAP adapter.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END


## PROPERTY_START
## PROPERTY_NAME: THREADS_PER_CORE 
## PROPERTY_TYPE: Integer
## PROPERTY_DESCRIPTION
## Number of threads per core. Default is 4.
## (For property value, see PROPERTY_VALUE_ALL section at end of file) 
## PROPERTY_END

## PROPERTY_VALUE_ALL


#######################################################
#Performance Tuning: System
#######################################################

MEMORY=##MEMORY##
IS_DEDUCT_MEM_BI=##IS_DEDUCT_MEM_BI##
IS_DEDUCT_MEM_CLADAPTER=##IS_DEDUCT_MEM_CLADAPTER##
IS_DEDUCT_MEM_SAPADAPTER=##IS_DEDUCT_MEM_SAPADAPTER##
THREADS_PER_CORE=##THREADS_PER_CORE##

#######################################################
#Performance Tuning: JVM Parameters for Server
#######################################################

MEMORY_ASI=##MEMORY_ASI##

Linux-64.INIT_HEAP=##Linux-64.INIT_HEAP##
Linux-64.MAX_HEAP=##Linux-64.MAX_HEAP##

Linux-64.INIT_AGE=##Linux-64.INIT_AGE##
Linux-64.MAX_AGE=##Linux-64.MAX_AGE##

Linux-64.MAX_PERM_SIZE=##Linux-64.MAX_PERM_SIZE##
Linux-64.STATIC_STACK=##Linux-64.STATIC_STACK##
ENABLE_HEAP_DUMP_OOM=##ENABLE_HEAP_DUMP_OOM##
ENABLE_HEAP_DUMP_SGQTCRTLBRK=##ENABLE_HEAP_DUMP_SGQTCRTLBRK##
ENABLE_VERBOSE_GC=##ENABLE_VERBOSE_GC##

JVM_ARGS_SUFFIX=##JVM_ARGS_SUFFIX##
JVM_ARGS_PREFIX=##JVM_ARGS_PREFIX##

#######################################################
#Performance Tuning: BP Queue
#######################################################

PROCESSORS=##PROCESSORS##
JMS_LISTNERS=##JMS_LISTNERS##

NOAPP.JMS_PAGING_HIGH=##NOAPP.JMS_PAGING_HIGH##
NOAPP.JMS_PAGING_MAX=##NOAPP.JMS_PAGING_MAX##
BP_SIZE=##BP_SIZE##

USE_SHADOW_CACHE=##USE_SHADOW_CACHE##
MAX_SHADOW_CACHE_SIZE=##MAX_SHADOW_CACHE_SIZE##

DISTRIBUTION_CACHE_MAX=##DISTRIBUTION_CACHE_MAX##
DISTRIBUTION_CACHE_MIN=##DISTRIBUTION_CACHE_MIN##

MULTICAST_INTERVAL=##MULTICAST_INTERVAL##
SWITCH_INTERVAL=##SWITCH_INTERVAL##
WF_IN_TRANSIT_TIMEOUT_LIST=##WF_IN_TRANSIT_TIMEOUT_LIST##


#######################################################
#Performance Tuning: Cache
#######################################################


MAP_CACHE=##MAP_CACHE##
ENVELOPE_CACHE=##ENVELOPE_CACHE##
EDI_CACHE=##EDI_CACHE##
WFD_CACHE=##WFD_CACHE##
USER_CACHE=##USER_CACHE##
GROUP_CACHE=##GROUP_CACHE##
PERM_CACHE=##PERM_CACHE##


#######################################################
#Performance Tuning: Purge Settings
#######################################################


PURGE.DEADLOCK_RETRIES=##PURGE.DEADLOCK_RETRIES##
PURGE.MAX_PURGE_THREADS=##PURGE.MAX_PURGE_THREADS##
PURGE.PURGE_DOCS_ON_DISK=##PURGE.PURGE_DOCS_ON_DISK##


#######################################################
#Performance Tuning: Queue Settings
#######################################################


## Queue 1

NOAPP.INITIAL_CYCLES_1=##NOAPP.INITIAL_CYCLES_1##
NOAPP.EXEC_CYCLE_1=##NOAPP.EXEC_CYCLE_1##
NOAPP.MIN_POOL_SIZE_1=##NOAPP.MIN_POOL_SIZE_1##
NOAPP.MAX_POOL_SIZE_1=##NOAPP.MAX_POOL_SIZE_1##
NOAPP.RESOURCE_ALLOCATION_1=##NOAPP.RESOURCE_ALLOCATION_1##

## Queue 2

NOAPP.INITIAL_CYCLES_2=##NOAPP.INITIAL_CYCLES_2##
NOAPP.EXEC_CYCLE_2=##NOAPP.EXEC_CYCLE_2##
NOAPP.MIN_POOL_SIZE_2=##NOAPP.MIN_POOL_SIZE_2##
NOAPP.MAX_POOL_SIZE_2=##NOAPP.MAX_POOL_SIZE_2##
NOAPP.RESOURCE_ALLOCATION_2=##NOAPP.RESOURCE_ALLOCATION_2##

## Queue 3

NOAPP.INITIAL_CYCLES_3=##NOAPP.INITIAL_CYCLES_3##
NOAPP.EXEC_CYCLE_3=##NOAPP.EXEC_CYCLE_3##
NOAPP.MIN_POOL_SIZE_3=##NOAPP.MIN_POOL_SIZE_3##
NOAPP.MAX_POOL_SIZE_3=##NOAPP.MAX_POOL_SIZE_3##
NOAPP.RESOURCE_ALLOCATION_3=##NOAPP.RESOURCE_ALLOCATION_3##

## Queue 4

NOAPP.INITIAL_CYCLES_4=##NOAPP.INITIAL_CYCLES_4##
NOAPP.EXEC_CYCLE_4=##NOAPP.EXEC_CYCLE_4##
NOAPP.MIN_POOL_SIZE_4=##NOAPP.MIN_POOL_SIZE_4##
NOAPP.MAX_POOL_SIZE_4=##NOAPP.MAX_POOL_SIZE_4##
NOAPP.RESOURCE_ALLOCATION_4=##NOAPP.RESOURCE_ALLOCATION_4##

## Queue 5

NOAPP.INITIAL_CYCLES_5=##NOAPP.INITIAL_CYCLES_5##
NOAPP.EXEC_CYCLE_5=##NOAPP.EXEC_CYCLE_5##
NOAPP.MIN_POOL_SIZE_5=##NOAPP.MIN_POOL_SIZE_5##
NOAPP.MAX_POOL_SIZE_5=##NOAPP.MAX_POOL_SIZE_5##
NOAPP.RESOURCE_ALLOCATION_5=##NOAPP.RESOURCE_ALLOCATION_5##

## Queue 6

NOAPP.INITIAL_CYCLES_6=##NOAPP.INITIAL_CYCLES_6##
NOAPP.EXEC_CYCLE_6=##NOAPP.EXEC_CYCLE_6##
NOAPP.MIN_POOL_SIZE_6=##NOAPP.MIN_POOL_SIZE_6##
NOAPP.MAX_POOL_SIZE_6=##NOAPP.MAX_POOL_SIZE_6##
NOAPP.RESOURCE_ALLOCATION_6=##NOAPP.RESOURCE_ALLOCATION_6##

## Queue 7

NOAPP.INITIAL_CYCLES_7=##NOAPP.INITIAL_CYCLES_7##
NOAPP.EXEC_CYCLE_7=##NOAPP.EXEC_CYCLE_7##
NOAPP.MIN_POOL_SIZE_7=##NOAPP.MIN_POOL_SIZE_7##
NOAPP.MAX_POOL_SIZE_7=##NOAPP.MAX_POOL_SIZE_7##
NOAPP.RESOURCE_ALLOCATION_7=##NOAPP.RESOURCE_ALLOCATION_7##

## Queue 8

NOAPP.INITIAL_CYCLES_8=##NOAPP.INITIAL_CYCLES_8##
NOAPP.EXEC_CYCLE_8=##NOAPP.EXEC_CYCLE_8##
NOAPP.MIN_POOL_SIZE_8=##NOAPP.MIN_POOL_SIZE_8##
NOAPP.MAX_POOL_SIZE_8=##NOAPP.MAX_POOL_SIZE_8##
NOAPP.RESOURCE_ALLOCATION_8=##NOAPP.RESOURCE_ALLOCATION_8##

## Queue 9

NOAPP.INITIAL_CYCLES_9=##NOAPP.INITIAL_CYCLES_9##
NOAPP.EXEC_CYCLE_9=##NOAPP.EXEC_CYCLE_9##
NOAPP.MIN_POOL_SIZE_9=##NOAPP.MIN_POOL_SIZE_9##
NOAPP.MAX_POOL_SIZE_9=##NOAPP.MAX_POOL_SIZE_9##
NOAPP.RESOURCE_ALLOCATION_9=##NOAPP.RESOURCE_ALLOCATION_9##