Accepted, Not Yet Planned

This is something we are looking into for XPP Cloud. In the meantime, our Professional Services team has confirmed they have been working with you on your specific use cases and will continue to support that effort.

Support for multi-server licensing

As part of a project to streamline the creation of both production and development resources, I would like to be able to automate the creation of XPP servers. Part of this would include validating the installation, which would include having the server properly licensed. 

This would be used for both dev and production resources, each "pool" would have different resources assigned. Being able assign license tokens based on the presence of a small licensing server in a subnet or by using certain criteria (server name prefix/suffix, IP address etc...) would be very useful. 

Would it be possible to have a single license file (or alternative activation method) that could support a scenario like the one described above (also in support ticket 00733661)? 

Thanks for considering this. 

Kind regards,

  • Quick follow up to offer an alternate approach to having a single XPP license server allocate production/dev/test licenses to each respective environment. 

    In the following scenario, three different license files would be present on a single XPP/RLM license server. 

    Each license would contain the features, token counts etc... as they do today -- however the port that's specified on the HOST line of the .lic file would be different depending on the environment.

    Pointing the XPP application servers to the right license would be done by specifying a different port to use in the sdlxysoft_LICENSE environment variable.

    Production licenses would query the RLM licensing server on port 5053
    Each production application server would point to the RLM licensing server using the environment variable:

    Development licenses would query the RLM licensing server on port 6053 
    Each development application server would point to the RLM licensing server using the environment variable:

    Test licenses would query the RLM licensing server on port 7053 
    Each test application server would point to the RLM licensing server using the environment variable:

    The port would be submitted to RWS along with the rest of the information as part of a standard license request. The returned .lic file would have the customer specified port as the list thing on the HOST list.