Licensing
Licensing defines the limitations on the number of connections and the systems that can be connected through Integration Framework. The license is included in a license file called PimsoftIFServiceHost.Activator.key, which is installed on the server machine under the following system folders:
C:\Windows\System32 (for 32 bits platform)
C:\Windows\SystemWOW64 (for 64 bits platform)
When Integration Framework is accessed, the licensing functionality checks and validates your connection configuration. If it encounters any of the following issues, it exits immediately and depending on the issue encountered it produces one of following messages:
- License file not found
- Corrupted or invalid license file
- Expiration of DEMO time
Licensing Options
The following table describes the supported Integration Framework licensing options:
Integration Framework Licensing Options
| Item | License Check Description |
|---|---|
| Connector | Validate the type and the number of each type of connector. |
| PI and AF Systems | Name for each PI and PI-AF systems to be connected. |
| Other Systems | Machine name for each system to be connected. |
| Dataset | Number of Datasets available for each connector type. |
EXAMPLE: License Requirements Based on Needs
A customer needs to connect 2 Oracle systems (through OLEDB) in order to get or import in Sigmafine (SRVSF01) Measurement Data (from system Oracle1) and Movements (from system Oracle2). Moreover he needs to connect the planning data from a system (INVOR1) that exposes data through WebService. The license will be built as follow:
| Type | Quantity | System List |
|---|---|---|
| PI/AF | 1 | SVRSF01 |
| OLE | 1 | ORACLE1; ORACLE2 |
| SOA-Invoker | 1 | INVOR1 |
Note: The license file could be a temporary license or a permanent one. This license is a machine-specific file, so it is not transferable to any other machine(s). If you have a development system, be sure to use the right license file for the system.