Servers

The servers tab is designed to provide administrators with the ability to manage BI Office application server nodes. Administrators can also add Web Site nodes when they want to deploy two or more web authentication models on the same web server.

Web Server

The "client router" web server routes all client queries and meta data requests. There must be at least 1 client router server node for the application to function. In an enterprise model, with load balancing and fail-over requirements, you may wish to deploy 2 or more client router/web servers to 2 or more separate web machines (physical or virtual). In this scenario, it is important to ensure that the environment is running with an Active Directory. Alternatively, you can add the second web site for a given machine if you choose to deploy 2 or more web sites on the same web server with different web authentication models.

Each client router/web site must at the very least have the following key elements in its record:

• a unique machine name.
• a machine address - preferably the machine's name or fully qualified domain name. As a last resort you can use its IP4 address which should be static.

Optionally, you can also add

• a server description

Admin Web Site

Identical to the main client router / web sit, the admin "Client Router Admin" handles all the admin console requests. Like the web server, it too must have the following in its record:

• a unique machine name.
• a machine address - preferably the machine's name or fully qualified domain name. As a last resort you can use its IP4 address which should be static.

Optionally, you can also add

• a server description

Application Server

The Application Server is the main rendering engine that handles all queries (including print and export jobs) and meta data requests. There must be at least 1 application server node for the application to function. In an enterprise model, with load balancing and fail-over requirements, you may wish to deploy 2 or more application servers to 2 or more separate machines (physical or virtual). In this scenario, it is important to ensure that the environment is running with an Active Directory.

Each application server must have (at the very least) the following key elements in its record:

• A unique machine name.
• A machine address - preferably the machine's name or fully qualified domain name. As a last resort, you can use its IP4 address which should be static.
• The port on which the application web service will operate. This needs to be something unique that does not interfere with another service.
• Maximum number of threads for handling incoming jobs.

Optionally, you can also add

• A server description

NOTE: When needed, you can check the Service Health Check option to enable a series of application server health checks at 3:00 AM each morning.

Router Server

The Router routes all queries and meta data requests to application and publication servers. There must be at least 1 router server node for the application to function.

Each router server must at the very least have the following key elements in its record:

• a unique machine name.
• a machine address - preferably the machine's name or fully qualified domain name. As a last resort you can use its IP4 address which should be static.
• the port on which the router web service will operate. this needs to be something unique that does not interfere with another service.
• Maximum number of threads for handling incoming jobs.

Optionally, you can also add

• a server description

Publication Server

The optional Publication Server is the rendering engine that handles all bioWriter publication and alert requests. There must be at least 1 publication server node for the publication rendering to function. In an enterprise model, with load balancing and fail-over requirements, you may wish to deploy 2 or more publication servers to 2 or more separate machines (physical or virtual). In this scenario, it is important to ensure that the environment is running with an Active Directory.

Each publication server must at the very least have the following key elements in its record:

• a unique machine name.
• a machine address - preferably the machine's name or fully qualified domain name. As a last resort you can use its IP4 address which should be static.
• the port on which the publication web service will operate. this needs to be something unique that does not interfere with another service.
• Maximum number of threads for handling incoming jobs during PEAK hours.
• Maximum number of threads for handling incoming jobs during OFF-PEAK hours.

Optionally, you can also add

• a server description

NOTE: Multiple nodes of each server above can be added to create a load-balanced cluster for BI Office for Enterprise licensees.