License Administration Guide - norsar

Chapter 16: Licensing in a Cloud-Computing EnvironmentUse Cases for Licensing Software in the CloudBinding Elements Required for Case 3In the Amazon EC2 environment, this use case involves binding licenses to the machine on which the lmbindcomponent of the license server resides and, for any served node-locked licenses, to the AMI instance on whichthe specific license client resides. The required binding elements include the following:• The lmbind binding identity for the physical enterprise machine where you intend lmbind to run. Thesoftware publisher specifies the type of lmbind hostid needed.• For any served node-locked licenses, the AMI instance ID for the AMI instance containing the license client.For a description of these binding elements and how to obtain them, see the Hostids for Binding section.License Administrator Tasks for Case 3Perform the following basic tasks for traditional served and unserved licensing in a virtual private cloud:1. Set up a separate AMI instance for each license client and for the license server.Note • A large-sized AMI instance is recommended for the license server.2. On the AMI instance for the license server, perform the following additional tasks:• Ensure that the ports for the license server, vendor daemon, and the webport (for the license servermanager user interface) allow incoming connections.• Set the appropriate EC2 security group to control access to the license server port.3. Download the platform-specific lmhostid utility from the Flexera Software website to these locations:• The physical machine in your enterprise on which you intend to run lmbind• For any served node-locked licenses, each license-client AMI instance to which you intend to bindlicenses4. To obtain the hostids listed in Binding Elements Required for Case 3, run the appropriate lmhostid commandon the AMI instances and on the physical machine running lmbind.See Hostids for Binding for information about the different lmhostid commands.5. Send the hostids to the software publisher, who then uses this information to generate the license certificate.6. When you receive the license file from the publisher, modify the license certificate to configure serverparameters (like TCP port number, options file, or other parameters.)7. Install the required FlexEnabled components on the AMI instances, using methods similar to on-premisesdeployment.For served licenses, continue with these steps:8. Install lmbind on the physical enterprise machine, and launch it on port 27010. (Enter lmbind -port 27010 -llmbind.log).196 FNP-11111-LAG01 License Administration Guide