The Captiva Cloud Service acts as a local web capture server to process ImageGear ISIS API calls to perform tasks such as scanning and manipulating images. The service is part of the Captiva Cloud Runtime Components which must be installed on each client computer that will access your application. The Captiva Cloud Runtime Components can optionally be installed, which is necessary to use the ImageGear ISIS functionality.
By default, the Captiva Cloud Service is configured to start automatically when the computer starts. When the service starts, it scans for available TCP network ports that your application can use to communicate with the local web capture server. The server listens on port 49732, 49733, or 49734 for HTTP and on port 49735, 49736, or 49737 for HTTPS. If none of the ports are available, then an error is logged in the Windows System event log.
For an application to use the ImageGear ISIS features, the Captiva Cloud Runtime components must be installed on the application user’s system. The runtime components might be installed as a standalone package, or with another piece of software such as a scanning application. Users running your application must also have Microsoft .NET Framework 3.5 SP1 installed. You can download a redistributable package from the Microsoft website and include it in your distribution. The Captiva Cloud Runtime installer files are located in:
{Archive root}\Resources\Redistributables
The following redistribution options are available. You need to use only one of these.
A merge module lets you include toolkit components in an installer application. Use this option when you want to install the runtime alongside additional software. You can add a merge module file to your installation project following the instructions provided with Visual Studio.
The following merge modules are available:
This version of PixTWAIN can be used only by applications using the Captiva Cloud Runtime.
The installer is an executable file (plus supporting files) that can be used to distribute only the toolkit components. The installer can be run from a number of different contexts. A silent installation option is available, but by default the installer is interactive. You can distribute the installer if you want to allow users to decide where to install the files.
You can redistribute the runtime installer in many ways, such as on an intranet site, via an automatic deployment tool such as Microsoft Systems Management Server (SMS), or simply by making it available on a network share. Your distribution package must include all of the files in the Redistributable folder. The runtime can be installed by running setup.exe.
To perform a silent installation, run the installer using the following command:
setup.exe /S /v/qn
Additional command line arguments are available. Run the following command to display a list of arguments that you can specify:
setup.exe /?
The Windows Installer program itself (MsiExec.exe) accepts a number of additional arguments that can be passed with the /v argument. Run MsiExec.exe /help for more information about these arguments.
To help ensure continuous availability of toolkit functionality, you can configure the OpenText Captiva Cloud Service to restart automatically on failure when you install it. Windows services are configurable from a command line that you can call from your installer. Refer to the operating system documentation or the Microsoft web site for information about configuring the behavior for a service that fails. The service name is Emc.Captiva.WebCaptureService.