Working with Content Manager deployments
You can use ISHDeploy cmdlets to work with the available deployments on a Content Manager server.
Using a deployment
All cmdlets that target a specific deployment are driven from the -ISHDeployment parameter that expects a name of deployment or an instance as value. To acquire an instance use the Get-ISHDeployment.
The following two blocks are equal for the default deployment name InfoShare.
# Using the deployment instance
$deploymentName="InfoShare"
$deployment = Get-ISHDeployment -Name $deploymentName
Get-ISHDeploymentHistory -ISHDeployment $deployment
# Using the deployment name
$deploymentName="InfoShare"
Get-ISHDeploymentHistory -ISHDeployment $deploymentName
Using the deployment name paradigm is the preferred way for remote invocation purposes.
Cmdlet syntax for single deployments
All cmdlets, with the exception of Get-ISHDeployment, offer the -ISHDeployment parameter to help them target a deployment. When there is only one deployment available, it is possible to omit the -ISHDeployment and the module will automatically use the only deployment available.
For example, lets assume that Get-ISHDeployment outputs one deployment:
Get-ISHDeployment|Format-Table Name,SoftwareVersion,DatabaseType,AccessHostname
Name SoftwareVersion DatabaseType AccessHostName
---- --------------- ------------ --------------
InfoShare 15.0.3815.0 sqlserver ish.example.com
In this case, the following two invocation of Get-ISHDeploymentHistory are equal:
Get-ISHDeploymentHistory -ISHDeployment "InfoShare"Get-ISHDeploymentHistory
Although the system automatically figures out this one deployment named InfoShare, the history file will contain records with an explicit value for the -ISHDeployment parameter.