Licensing BIRT iHub : Understanding CPU binding
 
Understanding CPU binding
BIRT iHub System supports CPU binding on a machine with an appropriate CPU-based license. CPU binding restricts a process or processes to run on a subset of CPUs. If you bind the BIRT iHub System to a subset of CPUs, only those CPUs count toward the total number of licensed CPUs. The CPU limit in the license file applies to all CPUs for all machines in the cluster. Depending on the operating system and specific system command, you can restrict other processes from running on the processor to which you bind a process.
You can bind BIRT iHub processes to a specific set of processors on a machine that runs a Windows or Linux operating system. The default configuration does not bind BIRT iHub to a set of processors. In the default configuration, all processors on a BIRT iHub machine count toward the maximum number of licensed CPUs.
To bind BIRT iHub to a set of processors, bind the Actuate Process Management Daemon (PMD) to the processors. The Actuate PMD starts all BIRT iHub processes. The processes inherit the binding from the Actuate PMD.
In a cluster, BIRT iHub counts only the processors on nodes that join the cluster and run the encycsrvr process. An encycsrvr process runs when a node is online. BIRT iHub counts the number of processors on a machine when the first encycsrvr process starts.
When deploying BIRT iHub on a machine with multi-threaded CPUs that use logical processors, the customer receives a license based on the number of physical processors in the system. To accommodate the use of logical processors, the customer receives a license key that specifies two or four times the number of physical processors.
This section contains information on the following topics:
*Binding a BIRT iHub to processors on a Windows machine
*Checking BIRT iHub bound processors
*Configuring e-mail for CPU license problems