A license file is used to license Mule. You will obtain the license file from MuleSoft support. The license file ends with extension .lic, such as license.lic.

If you will be licensing two or more Mule application servers, store the license file in a shared location, as the license file will be deleted during the installation.

On the Mule server that will get the new license key file, determine the date that the current license key file will expire. When the Mule application server is restarted, the mule_ee.log will identify the date that the current license key file will expire.

Valid license key --> Evaluation = false, Expiration Date = mm dd hh:mm:ss CST yyyy, Contact Name = John Doe, Contact Email Address = john.doe@example.com, Contact Telephone = 0000000000, Contact Company = Acme Corporation, Contact Country = US, Entitlements = clustering,datamapper

Or, you can use the -verifyLicense command to view the expiration date of the current license.

${mule_home}/your_jvm/bin/mule -verifyLicense

Before updating the Mule application server with the new license, you will need to stop the Mule application server and use the mule command line tool with the -unInstallLicense option to uninstall the current license.

${mule_home}/your_jvm/bin/mule -unInstallLicense

The -unInstallLicense command should delete the muleLicenseKey.lic file. If the file still exists, delete the muleLicenseKey.lic file.

rm ${mule_home}/your_jvm/conf/muleLicenseKey.lic

Then, use the mule command line tool with the -installLicense option to install the new license. Upon completion, a new muleLicenseKey.lic file will be created at ${mule_home}/your_jvm/conf/.

${mule_home}/your_jvm/bin/mule -installLicense /path/to/license.lic

You can now start the Mule application server and check the mule_ee.log to ensure the JVM is using the license with the new expiration date. Or, the mule command line tool with the -verifyLicense option can be used.

${mule_home}/your_jvm/bin/mule -verifyLicense