What is an instance set?

Customizations for particular customers can be overlaid on the generic CollabNet TeamForge product in the form of an instance set.

Some SaaS clients require modifications to internal components beyond what they can accomplish with remote branding. For example, a client may need additional components that are not present in the base product.

Instance sets generally include Apache configuration files with rewrites and other logic, and sometimes include overrides for templates or Java classes.

Some components delivered in an instance set are entirely client-specific, while others, such as CVSup, are shared among several clients.

Limitations

The use of an instance set imposes these restrictions:

Instance scripts are usable only with an existing installation of CollabNet TeamForge patches before installation.
One and only one instance can be installed on a CollabNet TeamForge server at any one time.
No data migration will occur if any changes have been made to the CollabNet TeamForge database schema.

Instance set delivery

Instance sets are delivered in a tarball that contains all files and scripts necessary for installation.

The instance sets installed on a site are listed at <SITE_DIR>/dist/conf/instance.txt .

This is an example of the contents of an instance set tarball customized for a Redhat Linux operating system:

 instance-set-install.sh netbeansinst-manifest
				scripts/scast-instance-set.py packages/instance-set/
				packages/instance-set/1/ packages/instance-set/1/i386-redhat-7.2/
				packages/instance-set/1/i386-redhat-7.2/SCAST-netbeansinst-1.0-0-2.6.0.212.2.i386.rpm