[Close]

Number of Licenses Required

• One license for each person that directly or indirectly invokes the LMX executable. (Such a person is called a USER in the license agreement.) (A licensed user may execute LMX on any number of machines as long as those machines are for the sole use of that user.)
• One license for each machine that invokes the LMX executable without direct intervention of a user (such as a nightly build machine).
• A person that uses the code generated by the LMX executable, but does not run the program directly (or indirectly) does NOT require a license. (Such a person is called an INTEGRATOR in the license agreement.)

N.B. This section is paraphrased from the license agreement. If there is any discrepancy between this and the license agreement, the license agreement text is definitive.

Examples

Alice has a machine at work, a machine at home and a laptop for the road. She runs the LMX executable on all three of these machines. As all three of these machines are for her sole use, Alice only requires one license file.

Bob uses make (possibly indirectly via his development environment) for his builds, which conditionally runs the LMX executable. Bob is a USER and needs a license file.

Carol uses the code generated by Bob, but never runs the LMX executable either directly or indirectly (e.g. via make). She is an INTEGRATOR and does NOT need a license file.

Marvin is a nightly build machine to whom all developers check in their code, including schemas that are compiled by the LMX executable. Marvin needs a license file.

Adam is Marvin's administrator and doesn't do code development. He occasionally has to re-boot Marvin. Adam does NOT need a license file.

Robby is also a nightly build machine (in another department) to whom developers check in their code. However, Robby never runs the LMX executable, so Robby does not need a license file.

[Close]