This article contains steps on setting up a Multi-Instance Server in which  a single server could have several registered instance servers to accommodate multiple clients.



Creating Instances.cfg file


This instances configuration file contains setup information on each server instances that will be created. But before creating this file, we need to know how many instances can be created by checking the registered Olation server license.


Based on this example, I have a limit of 10 instance that I can create.


The Instances.cfg should be created on C:\ProgramData\Olation, below is an example of the setup information of a single instance server.


[Olation Service 9990]

Port=9990

Secure=0

Description= Olation Server Description 9990

Configuration=Server_9990.cfg

License=Olation_9990.olf

LogSettings=Settings_9990.cfg



FlagPurpose

[Olation Service 9990]

The Olation Service instance name to be used
Port
The port number to be used  by the Olation Service instance
Secure
Setting the instance whether  is Olation Studio OpenSSL enable or not. 1 for enable and for disable
Description
Olation Service  Description
Configuration
This will be created upon creating or opening a Olation Database and it contains the database connection info.
License
This will be the file name of the license to be used on this  server instance
LogSettings
This setting configuration file is manually created to set the log file information to be use on this server instance.



For this example let create 4 Instance on the Instances.cfg file as shown below.


Base on this example I have setup the instance information for 4 Instances which has it on ports, license file, server config file, and log setting files.

NOTE: it is best practice have a naming convention on the  instance information with the port number as suffix.



Creating the log Settings.cfg files for each sever instance


The log settings files which are indicated on each instances on the Instances.cfg would not hinder the setup/installation of the server instances but it is a good practice to create them before hand.


These log settings config files should be created on C:\ProgramData\Olation.  To consolidate all the log file per server instance it is best to create a Log folder on  C:\ProgramData\Olation


Base on the Instance.cfg LogSettings info per instance, I have created 4 log setting file which are

Settings_9990.cfg
Settings_9991.cfg
Settings_9992.cfg
Settings_9993.cfg

Have also created a Logs folder to consolidate all the log files
The content for each log setting file are as follows
Settings_9990.cfg

[Logging]

Enabled=1

File=C:\ProgramData\Olation\Logs\olationlog_9990.txt

MaxSize=10

Advanced=1

Settings_9991.cfg

[Logging]

Enabled=1

File=C:\ProgramData\Olation\Logs\olationlog_9991.txt

MaxSize=10

Advanced=1

Settings_9992.cfg

[Logging]

Enabled=1

File=C:\ProgramData\Olation\Logs\olationlog_9992.txt

MaxSize=10

Advanced=1

Settings_9993.cfg

[Logging]

Enabled=1

File=C:\ProgramData\Olation\Logs\olationlog_9993.txt

MaxSize=10

Advanced=1



Setup/Creating the Olations Server Service instances


To create the Olation Server Service Instances we need to run a OLAService.exe command on the command prompt which is run as administrator.


Open command prompt as Administrator
Run command CD C:\Program Files\Olation to change directory to C:\Program Files\Olation.
Run command OLAService.exe -install to read the Instance,cfg file  and create the Olation Server Service Instances
Go to Task Manager to confirm all the Olation Server Service Instance are created and start the services



Register Olation Server Instance on Olation Studio


This is where we will create or register the Olation Server Instance to license it and create a sample database per instance for our slice testing later powerexcel. 



Open Olation Studio and Register a Server
Let register the Olation Server Instance with the port number 9990 by setting it up as follows.

Display Name: 9990_Server
ServerName/IP: localhost
Port: 9990
Secure Connection: Disable
Repeat this step to register all the Olation Server instances
Note: Change the port per each server instances
For our test, Let us create 4 Nexus DB Panda Model for each  Server Instance and name them using the instance port as its suffix.



Creating Server Reference Key on Olation WebService per Server Instance


A Server Reference Key is used to identify which machine and instance the Olation WebService will connect to.



- Open IIS
- Select Olation WebService Site
- Open Application Settings
Let us Add a Server Reference Key for the 4 instance we created.
- Click Add
- On Name - Input a Server Reference Key
- On Value - Input the Server IP address where the Olation server is located then followed by colon ":" then the port number used by the specific server instance.
For our 4 Olation Server Instance example the we going the Server Reference Key Below

9990-SVR
localhost:9990
9991-SVR
localhost:9991
9992-SVR
localhost:9992
9993-SVR
localhost:9993