Set-up SLM with Quick Install Script

Customers who have Schrödinger software installed and where the SLM license server will be running on the same machine can use the SLM Quick Install Script to quickly run through the necessary procedures to use Schrödinger License Manager.

 

Running the Quick Installation Script:

  • the license server process is run as a service when going through the quick SLM setup

  • the script will set up the SLM license server process (requires a valid license key or license file)

  • bundles all the SLM administration tasks (SLM install, client setup, uninstall) platform-independently

 

REQUIRES ADMIN PRIVILEGES (both installation and uninstall routines requires the script to be invoked with admin privileges)

 

For further information also have a look at the help text of the individual subtasks:

$SCHRODINGER/licadmin quick-slm-setup install -h

If you are Windows, you can omit the $SCHRODINGER prefix from the command above.

 

NOTE: Run script on the server machine.
  • Windows
  • Mac
  • Linux

Open a Command Prompt or Power Shell via “Run as Administrator”

If SLM license was shared as a license key:

Open a Command Prompt or Power Shell via “Run as Administrator” 

licadmin quick-slm-setup install -lickey <slm_lickey>

 

If SLM license was shared as a license file: 

licadmin quick-slm-setup install -licfile <slm_licfile>

 

By default, the SLM license server process will be configured to communicate on TCP/IP port 53000.

If this port is already in use by another application/process, then the next larger port number will be tried (53001 etc.).

The TCP/IP port number, over which the SLM license communication should take place, can be explicitly set by providing the -port <port> flag.

 

By default, the installation routine will install the SLM license server executables into the following directory:

C:\ProgramData\Schrodinger\licserver

 

If you prefer to use a different installation directory for the SLM installation (not recommended!), you can provide an alternative path via the -path <path> flag.

Next Step: Server Identifier Client Configuration Instructions

Open a Terminal

If SLM license was shared as a license key: 

sudo $SCHRODINGER/licadmin quick-slm-setup install -lickey <slm_lickey>

 

If SLM license was shared as a license file: 

sudo $SCHRODINGER/licadmin quick-slm-setup install -licfile <slm_licfile>

 

By default, the SLM license server process will be configured to communicate on TCP/IP port 53000.

If this port is already in use by another application/process, then the next larger port number will be tried (53001 etc.).

The TCP/IP port number, over which the SLM license communication should take place, can be explicitly set by providing the -port <port> flag.

 

By default, the installation routine will install the SLM license server executables into the following directory:

/Library/Application Support/Schrodinger/licserver

 

If you prefer to use a different installation directory for the SLM installation (not recommended!), you can provide an alternative path via the -path <path> flag.

Next Step: Server Identifier Client Configuration Instructions

 

Open a terminal

If SLM license was shared as a license key: 

sudo $SCHRODINGER/licadmin quick-slm-setup install -lickey <slm_lickey>

 

If SLM license was shared as a license file: 

sudo $SCHRODINGER/licadmin quick-slm-setup install -licfile <slm_licfile>

 

By default, the SLM license server process will be configured to communicate on TCP/IP port 53000.

If this port is already in use by another application/process, then the next larger port number will be tried (53001 etc.).

The TCP/IP port number, over which the SLM license communication should take place, can be explicitly set by providing the -port <port> flag.

 

By default, the installation routine will install the SLM license server executables into the following directory:

/opt/schrodinger/licserver

 

If you prefer to use a different installation directory for the SLM installation (not recommended!), you can provide an alternative path via the -path <path> flag.

Next Step: Server Identifier Client Configuration Instructions