Installing a plugin

To manually install a plugin, you can use the PluginManager, which has several methods for installing and upgrading plugins. The PluginManager can be retrieved from the EnterpriseSession, which you gain when you log on to the APS.

Once a plugin has been installed, a PIN file is created for it. This file contains the following information:
PIN Statement Description

SI_PLUGIN_PROGID

ProgID of the plugin. Uniquely identifies the plugin.

SI_PLUGIN_CLSID

Class ID of the plugin.

SI_PLUGIN_PINFILE

Name of the plugin's .pin file.

SI_PLUGIN_SETUPPROGRAM

Name of the plugin's install program.

All current Crystal Enterprise plugins use the Windows Installer's installation package (.msi) as the setup program. As such, msiexec.exe must be in the client machine's path in order for PlugIn Manager to install the package.

SI_PLUGIN_SETUPCOMMAND

Command used to install the plugin.

SI_PLUGIN_UNINSTALLCOMMAND

Command used to uninstall the plugin.

SI_PLUGIN_NAME

The name of the plugin.

SI_PLUGIN_CAT

Category of the plugin. There are currently four categories: Desktop, Admin, Auth, and Dest.

SI_PLUGIN_VERSION

Plugin's version number.

SI_PLUGIN_OBJECTTYPENAME

The object type name is used to match the processing server. To allow the new object to be scheduled, you have to start the APS with a parameter like "-ObjectType <name>" where <name> is the object type name that you specified in this statement.



Crystal Decisions, Inc.
http://www.crystaldecisions.com
Support services:
http://support.crystaldecisions.com