FDA Module Licenses
The FDA Module components request licenses from a license server. The following licenses must be installed on the Meridian Enterprise license server:
-
FDA Module Server license (product code M--FDS): Required for vault configuration and activity auditing. One per Meridian Enterprise server.
-
FDA Module Client Extension license (product code M--FDE): Required for user authentication and electronic signatures. One per concurrent PowerUser user of those features.
If you register the Meridian Enterprise license, the FDA module will also accept that as a valid license.
The following licenses are required to create, show, and print electronic signatures (recommended):
-
Publisher for Meridian Enterprise license (product code M--PUS): For publishing to and from a Meridian Enterprise vault.
One Meridian Enterprise database connection license (Hypertrieve, SQL Server, or Oracle) is required for each Publisher computer.
-
Publisher eSignature rendering module license (product code M--PES): For applying watermarks, electronic signatures, and signature pages to renditions.
Other Publisher licenses may be required to render that documents to which electronic signatures are attached and to publish documents to system other than Meridian Enterprise.