Documentation Center

Typical Server Vanilla Installation using ISHDeploy

The Content Manager installation process is being simplified as we developed the notion of a vanilla deployment. In this type of deployment, most parameter values are calculated or set to a default, and authentication is set for a local use with ISHSTS. This makes the installation usable and testable out of the box with minimal effort.

Introducing ISHDeploy

With the help of an independent PowerShell module named ISHDeploy you can now install and configure Content Manager easily and have it run locally without mandatory post-installation tasks except the setting of a few input parameters.

The global integrated vanilla deployment including the ISHDeploy's code as configuration approach consists in the following steps:
  1. Set a subset of input parameters, the rest is calculated for you. We advise to stick to the suggested defaults as much as possible.
  2. Install.
  3. Setup connection with any commercial STS such as Microsoft ADFS or PingIdentity PingFederate using ISHDeploy cmdlets if you need to use those.
  4. Further code-configure using ISHDeploy cmdlets during the lifetime of Content Manager.
ISHDeploy

ISHDeploy is a separate PowerShell module that lets you literally code your configuration intentions. The name of this module is ISHDeploy xx.x.x, where xx.x.x is the version of Content Manager it is compatible with.

For example Knowledge Center 2016 SP1 matches ISHDeploy 12.0.1. . This module uses cmdlets with which you can express your intentions, the module performs the specific settings for you.

More derived and default inputparameters for InstallTool

In the default inputparameters.xml we only keep the following parameters: osuser, ospassword, connectstring, apppath, serviceusername, and servicepassword. The rest of the parameters should be either defaulted or calculated based on values of other parameters. For example apppath will initialize datapath and webpath which are remnants of physical hard drive optimizations.

Although deprecated, all original parameters can still be set explicitly if required. As a fall back mechanism if the system for example detects the wrong ps_java_home parameter value.

[TS-11359|TS-11332|TS-10217|TS-11052|TS-11357]