**Note: This article pertains only to Control versions 5.1 and later.**

====== Reasoning ====== Control can be deployed with multiple SSLIPs if configured correctly. They will all talk to the same CHAPI, who will relay messages between them as necessary. Multiple SSLIPs are particularly useful for: * Users doing a lot with SQL Bridge, especially Order Recomputes. Recomputing an Order on the SSLIP is an intensive process and may slow response of the primary SSLIP. When importing orders or otherwise making calls to SQL Bridge's Recompute function, is it recommended to have a second SSLIP without users to handle these background functions. * Splitting users on multiple SSLIPs. This may be used to split the load or increase stability, though it is not yet determined if this has a noticeable effect. If multiple SSLIPs are set up, __all but one must be set to DisableBackgroundProcesses__. This is important or else Macros and other background tasks may be duplicated on multiple SSLIPs. ====== How It Works ====== The SSLIP has many options that can be altered using an Options/Configuration file. In this approach, we create two (or more) configuration files and run a copy of the SSLIP using each of the configuration. The configuration files change the following options: * [[startup_options]] . The port is the channel by which Control communicates with the SSLIP. No two programs on the same computer can use the same port, so each SSLIP running must use its own. If you don't specify the port, it uses the default. To change that, we give it a port offset, which adds or subtracts from the base port. * **Disable Background Processing**. Only one SSLIP running can process Macros and handle other background functions (like Recompute). If you set this wrong, you'll have duplicate background macros and other trouble. * **Install SQL Bridge**. Only one SSLIP should install SQL Bridge. * **Nickname**. You will want to name each SSLIP uniquely or you won't know which one you are shutting down! * **Delay**. We recommend you start the main SSLIP first and add a delay for each of othe other SSLIPs. You can find more information on startup options for Control and the SSLIP here: [[startup_options]] ====== Steps ====== ===== Modify Existing SSLIP Options File ===== This will be the main SSLIP that is not performing background operations. - Open Windows Explorer and navigate to the C:/Program Files (x86)/Cyrious/Control folder. - Edit the file Control_Options.txtControl and the SSLIP share the same options files. (if one does not exist create one). - Add the following option: * DisableBackgroundProcesses=1 - Save it and Close the Editor. ===== Create Macro SSLIP Options File ===== This is a SSLIP for performing background operations. It is not recommended for users. - Open Windows Explorer and navigate to the C:/Program Files (x86)/Cyrious/Control folder. - Create a file **MacroSSLIP_Options.txt** with the following options:The PortOffset may be any number, but we recommend keeping it between 1 and 1000. A different number is required for each additioanl SSLIP.


NickName=MacroSSLIP
PortOffset=10
DisableBackgroundProcesses=0
InstallSQLBridge=0
Delay=15

- Save it and Close the Editor ===== Create a ShortCut to Run the Macro SSLIP ===== - Right-click on SSLIP and create a shortcut. Leave this shortcut in the Control folder. - Edit this shortcut. - In the "Target" field, add the following option to the target location (Normally, this will be at the end of "C:\Program Files (x86)\Cyrious\Control\SSLIP.exe"). * -OptionFileName:MacroSSLIP_Options.txt

Example: "C:\Program Files (x86)\Cyrious\Control\SSLIP.exe" -OptionFileName:MacroSSLIP_Options.txt

- Save the changed. - Rename the new SSLIP shortcut to: **MacroSSLIP** - Create a copy of this shortcut and place it in the Startup folder for Windows so that the SSLIP will automatically start when the computer is turned on.