About Extended Host IDs

Typically, the server application resides with an enterprise customer, serving its pool of licenses within the enterprise. When the server communicates with FlexNet Operations to obtain a pool of licenses, the back office uses the server’s host ID to identify that particular server. This standard host ID is usually the server system’s Ethernet address, or it can be an attached dongle ID or VM UUID. However, there are cases in which the same server is used by an operative of the publisher to distribute features to multiple enterprises. One example is a field engineer whose laptop computer is running the server application; the field engineer takes the laptop computer to multiple sites to distribute licenses to enterprise customers. Because each enterprise’s pool of licenses is different, it is undesirable to use the same server host ID for all enterprises. To enable one server system to have more than one unique host ID, the server application supports extended host IDs. An extended host ID is a standard host ID value, extended with the host ID type (Ethernet/MAC address, dongle, or VM UUID) and an engineer-defined suffix. Using an extended host ID, the field engineer assigns a unique suffix for each enterprise customer visited, which keeps the server instances distinct in the back office. For details on how to create an FNE server with extended host ID, refer to Creating an FNE Server with Extended Host ID.

For example, Engineer 1 has a laptop computer with Ethernet address 11111111. While at Customer A, Engineer 1 uses suffix E1CA, resulting in extended host ID 11111111-3-E1CA (where 3 corresponds to the server’s Ethernet address host ID type). When the server application contacts the back office, this extended host ID is registered and associated with the pool of licenses for Customer A. The engineer then distributes licenses to Customer A’s client systems, and the server’s sync-to-back office settings report usage to the back office.

After finishing synchronization of Customer A’s data and before continuing to the next customer, the field engineer resets the server with the launcher reset command.

At Customer B, Engineer 1 uses suffix E1CB, resulting in extended host ID 11111111-3-E1CB. This second extended host ID is separately registered in the back office and associated with the pool of licenses for Customer B. The server’s sync-to-back office functionality communicates Customer B’s usage information to the publisher. Using this technique, one server host can appear as distinct servers in the back office, enabling each enterprise customer’s entitlements and fulfillments to remain separate.

See Also

Creating an FNE Server with Extended Host ID

Open topic with navigation