Server
Modifying this entity requires certain user authorization. For more information, see User Groups.
The iCore system runtime consists of one or more Servers. Each Server takes on one or several roles and each server role is specified by setting which vital Server parts and which Application pools (if any) it implements.
The vital server parts set up on a Server are:
- Event generator
- Event listener
- Event processor
- Job manager
Each individual Server part can only be implemented by one Server at any given time. Any Server can be configured to implement none or several Server parts. If no vital server part is implemented by a Server it should implement at least one Application pool to contribute to runtime.
In a multi-server configuration it is also possible to configure fail-over priority for each vital Server part.
Properties
| Name | Type | Description |
|---|---|---|
| Application pool implementations | ApplicationPoolImplementations | Specifies the Application pools implemented by the Server. |
| Component cache directory | String | The directory where the Server puts its executable components. |
| Created | DateTime | Date and time of the creation of the Server. |
| Description | String | A brief description of the purpose of the server. |
| Enabled | Boolean | Displays whether the Server is active or not. |
| Event generator priority | Short | Specifies the priority number of the Event generator on the Server, where 1 is the highest priority (0=disabled). In a one-server configuration this should be set to 1. In a clustered system this value specifies the start-up and fail-over priority. |
| Event listener priority | Short | Specifies the priority number of the Event listener on the Server, where 1 is the highest priority (0=disabled). In a one-server configuration this should be set to 1. In a clustered system this value specifies the start-up and fail-over priority. |
| Event processor priority | Short | Specifies the priority number of the Event processor on the Server, where 1 is the highest priority (0=disabled). In a one-server configuration this should be set to 1. In a clustered system this value specifies the start-up and fail-over priority. |
| IP address | String | Specifies the local IP-address to listen on for inter-server communications with this Server. Use '0.0.0.0' or '::' to listen on all available interfaces. |
| Job manager priority | String | Specifies the priority number of the Job manager on the Server, where 1 is the highest priority (0=disabled). |
| Machine ID | String | The computer name of the Server. |
| Modified | DateTime | Date and time of the latest modification of the Server. |
| Name | String | The name of the Server in the iCore system. |
| Port | Short | Specifies the local port to use for inter-server communication. Leave blank to use system default (specified as "Inter-server comm. port" in system settings). |
| Server ID | Guid | The identity of the Server. |
| User | IUser | The iCore user name under which the Server will execute. This property is read-only. |
If you have multiple iCore systems running on the same machine and listening on the same network interface (IP address), you need to specify different Ports for each Server. You can also achieve this by modifying the inter-server communication port setting for each system (see system settings).
Remarks
Including a Server in a running iCore system requires that:
- Property Enabled is set to 'True'.
- The iCore service is installed on the NT server specified by property Machine ID (see Installing iCore Windows service).
When implementing an Application pool for a Server, you need to specify:
- The number of worker processes handled by the Application pool ('Worker process count', default = 3).
- The maximum number of concurrent Jobs each process can execute simultaneously ('Slots in each process', default =3).
When creating a Server, a new "non-interactive" User is automatically added under which the Server will run. The User will be automatically deleted when the Server is deleted, if no tracking data is associated with it. Otherwise it will be marked for deletion. For more information, see User.
See Also
Technical architecture & Runtime
Entities
Application pool
Attached machines