Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Installing the License Server

    What is the License Server

    Stambia DI Designer refreshes its license token periodically, by querying the License Server using an https URL.

    This License Server can be our stambia.org server, or it can be installed in your organization's network. This way, your Designer can check its license token even in case of communication failures with stambia.org (ISP failure, proxies, firewalls...).


    The License Server is available for Stambia DI customers. Feel free to contact the Support Team if you want to know whether your company can install it.

    Put simply, the License Server is a Java service, usually installed on a Production or Development server, so that all Designers can access it and validate their license token periodically.

    Requirements

    • Any Windows or Linux server
    • Java 8 installed
    • 100MB of RAM
    • 50MB free disk space
    • Network configuration so that the server can be joined on https://<your-server>:<your-port>/

    Installation steps

    The steps are quite simple:

    • Download the License Server
    • Unzip the archive file into the installation directory of your choice
    • Copy the "license.xml" file into this same installation directory.
    • On Linux systems, make sure the bin/*.sh scripts have execution permissions.

    Installation is done.

    Please make sure that it works well before installing it as a service:

    • Execute the bin/start.bat script (or start.sh on Linux)
    • The standard output should look like this:
      2016-03-30 10:18:21.242:INFO::jetty-7.3.1.v20110307
      2016-03-30 10:18:21.275:INFO::started o.e.j.s.ServletContextHandler{/,null}
      2016-03-30 10:18:21.487:INFO::Started SslSocketConnector@0.0.0.0:443
    • The log file "com.stambia.licence.server.log" should contain:
      2016-03-30 10:18:20,989 [INFO ] Loading server properties
      2016-03-30 10:18:21,106 [INFO ] Server properties are loaded
    • From the Designer, try to paste your License URL in the License Manager
      https://<server-hostname>:<server-port>/default

     

    The "license.xml" file was delivered to you when purchasing Stambia. It contains your license data.
    • If you lost this file, please contact your Support Team.
    • If you never received this file (new Customer or first install of the License Server?), please send a request to the support team with:
      • The MAC address of the server which will host the License Server
      • The TCP/IP port (usually 42900 or 443) which will be open on the License Server for https requests

    Installing the License Server as a service

    On Windows:

    • execute the .\bin\serviceInstall.bat (as an administrator).
    • You will find the new Windows Service under the name "Stambia License Server"
    • The Java path can be configured in licenseServer\ext\yajsw\conf\wrapper.conf:
      wrapper.java.command = D:\\apps\\java\\jre1.8.0_121\\bin\\java.exe
    • You can use an environment variable for the Java path like this:
      >set wrapper_java_path=D:\apps\java\jre1.8.0_121\bin\java.exe
      And set wrapper.conf like this:
      wrapper.java.command = ${wrapper_java_path}
      Note that the variable name must be forced to lowercase in wrapper.conf, event if it is defined uppercase in the windows environment.
      A useful syntax is to use the default JAVA_HOME location when it is already set in the system:
      wrapper.java.command = ${java_home}\\bin\\java.exe

    On Linux:

    • make sure the ./bin/*.sh scripts are given the appropriate execution permissions
    • consult your linux's distribution documentation, for registering start.sh and stop.sh into the services
    • here is two sample scripts, please adapt them to your installation:

    Linux Script 1: declaring the service with "systemd"

    $ cat /etc/systemd/system/licenseService.service
    [Unit]
    Description=StambiaLicenseService
    After=network.target
    [Service]
    Type=simple
    Restart=always
    RestartSec=5
    User=username
    WorkingDirectory=/opt/licenseService/bin
    ExecStart=/bin/bash -c 'PATH=/opt/jdk1.8.0_301/bin:$PATH exec /opt/licenseService/bin/start.sh'
    ExecStop=/bin/bash -c 'PATH=/opt/jdk1.8.0_301/bin:$PATH exec /opt/licenseService/bin/stop.sh'
    [Install]
    WantedBy=multi-user.target

     

    Linux Script 2: declaring the service with "/etc/init.d"

    $ cat /etc/init.d/licenseService.sh
    #!/bin/sh

    # Set this to your License Server install directory
    STB_LICSRV_DIR="/opt/licenseServer"

    start()
    {
    cd "$STB_LICSRV_DIR/bin"
    nohup ./start.sh &
    }
    stop()
    {
    cd "$STB_LICSRV_DIR/bin"
    ./stop.sh
    }

    restart()
    {
    stop
    sleep 3
    start
    }

    case $1 in
    start)
    start;;
    stop)
    stop;;
    restart)
    restart;;
    *)
    start;;
    esac

     

    Articles

    Suggest a new Article!