Licensing Instructions

Limited Distribution Licensing

In Windows, run the setup .exe file to install a license. No other actions are required.

In Linux and macOS visit the URL below to generate a Runtime License value.

https://www.4dpayments.com/full/DOTHA

After obtaining the RuntimeLicense value assign this to the RuntimeLicense property to license the application for deployment. For instance:

component.runtime_license = "<value from above>"

This provides a license to the component and your application will run without a license prompt on any machine to which it is distributed.

Note that each component instance in your code must be assigned a RuntimeLicense value.

Trial Licensing

In Windows, run the setup .exe file to install a license. No other actions are required.

In Linux and macOS visit the URL below to generate a 30-day Trial Runtime License value.

https://www.4dpayments.com/trial/DOTHA

After obtaining the RuntimeLicense value assign this to the RuntimeLicense property to license the application for deployment. For instance:

component.runtime_license = "<value from above>"

This provides a 30-day trial license to the component and your application will run without a license prompt on any machine to which it is distributed during that time.

Note that each component instance in your code must be assigned a RuntimeLicense value.

Single Machine Licensing

In Windows, run the setup .exe file to install a license. No other actions are required.

In Linux and macOS the install-license utility is used to activate a license. Download the install-license utility from http://www.4dpayments.com/lic/install-license.tar.gz and extract the archive. After extracting, run the install-license utility. For instance:

./install-license YOUR_PRODUCT_KEY -p DOTHA

The single machine license will be downloaded and stored in the ".DPayments" folder of the user's home directory (i.e. "~/.DPayments").

At runtime a valid license must be present in either the current directory or the ".DPayments" folder of the user's home directory.

Deployment

After licensing your application using one of the above methods, no further steps are required to embed the license for distribution.

To deploy your application, simply ensure the module is installed on the deployment machine using pip:

  cd C:\path\to\install_dir
  python -m pip install inebank-22.0.xxxx.tar.gz

Once the product's Python package has been installed, the module can be imported and used: from inebank import *. Nothing else is required to deploy the application.

As an alternative to installing the module using pip, you can manually deploy the application and module together. The module comes in two pieces, both of which must be deployed with the application.

• The Python module named inebank.py
• The native library (unmanaged) named as follows:
• Windows: pyinebank22.dll (available for x64 and x86 processor architectures)
• Linux: libpyinebank.so.22.0 (available for x64 and x86 processor architectures)
• macOS: libpyinebank22.0.dylib (available for x64 and ARM64 processor architectures)

Both pieces are included in the product's Python package, <install_dir>\inebank-22.0.xxxx.tar.gz.

To package the module and native library alongside the application, first extract the archive then use the setuptools module to run the setup script setup.py. For instance:

  cd C:\path\to\install_dir\inebank-22.0.xxxx\
  python setup.py build --build-lib=<app_dir>

The above setup command packages the module and native library for deployment. A folder is created in the app_dir directory with the module and the native library packaged inside.

License Transfer

If you would like to transfer your license to another system, please complete our license transfer form. This will ensure your installations are not mistaken for license violations.

For additional information about our product activation process, please refer to our product activation FAQ.