Regardless of your deployment model, the first step in deploying your application is to package the required ImageGear runtime components.
The following content of the /Accusoft/ImageGear<Version>/Bin/.. from your ImageGear Installation represents the ImageGear runtime components:
- ig_cmyk_profile.icm – ICC color profile (CMYK color space)
- ig_rgb_profile.icm – ICC color profile (RGB color space)
- libDL*.* – Third-party libraries used by ImageGear PDF components
- libicu*.* – Third-party libraries used by ImageGear PDF components
- libIGART<Version>.* – ImageGear ART components
- libIGCORE<Version>.* – ImageGear Core components
- libIGLZW<Version>.* – ImageGear LZW components
- libIGMED<Version>.* – ImageGear MD components (only available on Linux platform)
- libIGPDF<Version>.* – ImageGear PDF components
- picn5420.ssm – Accusoft's binarize implementation
- picn5520.ssm (picx520.ssm for 64-bit platforms) – Accusoft's implementation of DCRAW support.
- Resource/PDF – ImageGear PDF component resources
- Resource/PS – ImageGear PDF component resources
You can take these components and include them into the installation package for your application.
Please make sure your installation routine defines the SSMPATH environment variable that contains a path to the picn5520.ssm (picx520.ssm for 64-bit platforms) file. For example: SSMPATH=$HOME//YourApp/Bin
If you are using Automatically Reported Runtime (Node-Locked) Licensing model:
- If you are using the Server Licensing Utility (SLU) to register licenses on the end user's system, the "slu.jar" and "ldk.jar" located in /Accusoft/ImageGearXX/Licensing/Deployment/ have to be distributed.
- Also please make sure your installation routine defines the ACCUSOFT_LICENSE_DIR environment variable that contains a path to the "accusoft...imagegear" license file. For example: ACCUSOFT_LICENSE_DIR=$HOME//License
The end user will obtain the license file and place it to the $HOME//License directory.
