OptionFileName (new Startup Option to be placed in SSLIP_Options.txt or Control_options.txt)

• With the new CHAPI / SSLIP config, each database a customer wants will need its own instance of SSLIP. One CHAPI service can handle multiple SSLIPS.
• This does not mean you’ll need one copy of SSLIP.exe for each database, or that you’ll need separate folders for the extra SSLIPs.
• Multiple SSLIPs can be run off of one copy of the SSLIP.exe file by using the Command Line Parameter OptionFileName to point the SSLIP at various different Options files, which each contain a different Port Offset.
  • Example: Create a shortcut to SSLIP.exe. In the shortcut’s ‘Target’ field, add the following to the end:
    • (insert one space)-OptionFileName:OtherOptions.txt
      • This shortcut will now start a SSLIP that ignores Control_Options.txt and SSLIP_Options.txt and instead looks to OtherOptions.txt for its parameters. As long as OtherOptions.txt contains a Port offset that no other Options files are using, this SSLIP will not affect any others.
• To connect Control to these new SSLIPs, create shortcuts to Control.exe that contain the exact same OptionFileName value.
  • Much like we used to match the PortOffset values in the SSLIP_Options and Control_Options files, now we will also match the OptionFileName values in the Target fields of Control shortcuts and SSLIP shortcuts.

DatabaseName

The DatabaseName option can be included in an Options file in order to direct the SSLIP.exe using that option file to choose that database from any available as its default connection.

*NOTE: This is NOT the name of the database in SQL Server.* *NOTE: If spaces are placed immediately to either side of the =, the option will not work.

• Example: DatabaseName=Old Store Data

The above example would direct the SSLIP to use Old Store Data as its default database.