Parameters
This section lists and describes the parameters contained in the inputparameters.xml file. You must define these parameters for the installation to work correctly.
-
osuser - The user name for the designated operating system account.
-
ospassword - The password for the designated operating system account. Set the password so that it never expires.
-
projectsuffix - A suffix that specifies the particular instance of Content Manager, if you are installing multiple Content Manager instances on a server.
-
connectstring - The connection string for the instance of the database application.
-
databasetype -
The type of database application that is used. The following are valid values:
oraclesqlserver
-
apppath -
The root directory for the Content Manager installation.
By default, this is set to C:\InfoShare.
-
webpath -
The root directory for the Web site.
By default, this is set to C:\InfoShare.
-
datapath -
The directory containing the data directory. This directory stores all data exported from Content Manager.
By default, this parameter is set to C:\InfoShare.
-
workspacepath -
The temporary directory where installation files are stored.
By default, this parameter is set to C:\InfoShare\_Workspace.
-
infoshareauthorwebappname -
The name of the web client application.
By default, this parameter is set to ISHCM.
-
infosharewswebappname -
The name of the web services application.
By default, this parameter is set to ISHWS.
-
infosharestswebappname -
Specify the name of the website with the Content Manager Secure Token Service (STS).
Follow the same patterns as infoshareauthorwebappname and infosharewswebappname
-
websitename -
The name of the web site where all virtual directories are created.
By default, it is set to Default Web Site.
-
baseurl -
Specify the base URL that is used to access the Content Manager web client.
This URL must specify the https:// secure protocol.
As a best practice, the HTTPS binding on IIS should have a certificate matching its Common Name with this host name.
-
localservicehostname -
The host name for the local address.
This specifies the host name with which communication within the Content Manager box takes place.
It can be local host or the node's machine name.
-
ps_fo_processor - The fully qualified file name of the XSL-FO processor, for example C:\Program Files\AntennaHouse\AHFormatterV6\AHFCmd.exe.
-
ps_htmlhelp_processor -
The fully qualified file name of the HTML Help processor, for example C:\Program Files (x86)\HTML Help Workshop\hhc.exe
-
ps_java_home -
The path to the JAVA HOME directory.
-
ps_javahelp_home -
The full path to a JavaHelp JHHOME folder. This allows you to set the JavaHelp Home folder when you want to publish with the JavaHelp output type.
-
ps_webworks_automap_application -
The fully qualified path and filename of WebWorks.
-
solrlucene_service_port - The port the SolrLucene service uses. This port must be unique for each Content Manager instance installed on a server.
-
solrlucene_stop_port - The port that is used to stop the SolrLucene service. This port must be unique for each Content Manager instance installed on a server.
-
servicecertificatethumbprint -
Specify the thumbprint of the service certificate.
In a typical Content Manager setup, the service certificate is the SSL certificate of the IIS web site where a standard Content Manager setup is going to be installed.
- Open
- Right-click the certificate of the IIS web site that is going to be used for Content Manager, then click View.
- Select the details tab, then click the Thumbprint field.
The bottom pane displays the details of the Thumbprint field.
- Select the entire value, then press CTRL + C to copy it to the clipboard.
- Paste it in the
servicecertificatethumbprint/currentvalueparameter of the inputparameters.xml file. - Delete any spaces and any control characters.
For example, the preceding Thumbprint would be represented as
A43489159A520F0D93D032CCAF37E7FE20A8B419in theservicecertificatethumbprintparameter. -
servicecertificatevalidationmode -
Specify the validation mode of the service certificate.
Specify the level of validation used to verify the service certificate (
servicecertificatethumbprint):ChainTrustValidates the certificate using a trust chain (it validates the certificate, the CA(s), and it checks if the certificate is not revoked using CRL or OCSP).
PeerTrustVerifies if the certificate is in the TrustedPeople certificate store of the computer.
PeerOrChainTrustVerifies if the certificate is valid, based on either a
ChainTrustor aPeerTrustvalidation.NoneThe certificate is not validated, it is always valid.
-
issuercertificatethumbprint -
Specify the thumbprint of the signing certificate on the configured STS (
issuerwstrustendpointurlandissuerwsfederationendpointurl).You can configure Content Manager to use either the ISHSTS or another STS, such as Microsoft ADFS.
Depending on whether you use ISHSTS or ADFS, do one of the following:
Content Manager STS Content Manager STS uses the same certificate as the one that is used on the IIS web site where Content Manager is going to be installed. Therefore, the thumbprint of the signing certificate is the thumbprint of the IIS web site certificate.
- Open
- Right-click the certificate of the IIS web site that is going to be used for Content Manager, then click View.
- Select the details tab, then click the Thumbprint field.
The bottom pane displays the details of the Thumbprint field.
- Select the entire value, then press CTRL + C to copy it to the clipboard.
- Paste it in the
issuercertificatethumbprint/currentvalueparameter of the inputparameters.xml file. - Delete any spaces and any control characters.
ADFS - Open , right-click the primary token signing certificate, then choose View certificate.
- Select the details tab, then click the Thumbprint field.
- Select the entire value, then press CTRL + C to copy it to the clipboard.
- Paste it in the
issuercertificatethumbprint/currentvalueparameter of the inputparameters.xml file. - Delete any spaces and any control characters.
-
issuercertificatevalidationmode -
Specify the validation mode of the issuer certificate.
Specify the level of validation used to verify the issuer certificate (
issuercertificatethumbprint):ChainTrustValidates the certificate using a trust chain (it validates the certificate, the CA(s), and it checks if the certificate is not revoked using CRL or OCSP).
PeerTrustVerifies if the certificate is in the TrustedPeople certificate store of the computer.
PeerOrChainTrustVerifies if the certificate is valid, based on either a
ChainTrustor aPeerTrustvalidation.NoneThe certificate is not validated, it is always valid.
-
issuerwstrustbindingtype -
Specify the binding type for the
issuerwsfederationendpointurlparameter.Depending on the authentication mode supported by the server defined in theissuerwstrustendpointurlparameter, specify one of the following values:- UserNameMixed when the
issuerwstrustendpointurlexpects username/password credentials. - WindowsMixed when the
issuerwstrustendpointurlexpects windows credentials.
- UserNameMixed when the
-
issueractorusername -
When delegating, specify the user name of the actor.
- When
issuerwstrustbindingtypeis UserNameMixed, specify the user name of a user defined in the Content Manager user repository. - When
issuerwstrustbindingtypeis WindowsMixed, use the value ofosuser.
- When
-
issueractorpassword -
When delegating, specify the password of the actor.
- When
issuerwstrustbindingtypeis UserNameMixed, specify the password matching the user defined withissueractorusername. - When
issuerwstrustbindingtypeis WindowsMixed, leave this field empty.
- When
-
issuerwstrustendpointurl -
Specify the endpoint of the STS for the active profile.
- When authenticating with ISHSTS, the base URL for authentication endpoints is
baseurl/infosharestswebappname/issue/wstrust/, wherebaseurlandinfosharestswebappnameare the designated values for thebaseurland theinfosharestswebappnameparameters, respectively.The authentication endpoints are:
mixed/usernamefor user name/password authentication. In this case,issuerwstrustbindingtypebecomes UserNameMixed;mixed/windowsfor Windows authentication. In this case,issuerwstrustbindingtypebecomes WindowsMixed.
- When authenticating with ADFS STS, specify https://adfs.example.com/adfs/services/trust/13/windowsmixed (where
adfsrefers to an example server related to ADFS), and verify that this ADFS endpoint is enabled. To check if the ADFS endpoint is enabled, perform the following actions:- Open .
- Check that /adfs/serices/trust/13/windowsmixed is enabled.
In this case,
issuerwstrustbindingtypebecomes UserNameMixed. - If you configure authentication with a different STS solution, specify the appropriate value based on the requirements for the selected STS and Identity Provider (IdP).
- When authenticating with ISHSTS, the base URL for authentication endpoints is
-
issuerwsfederationendpointurl -
Specify the endpoint of the STS for the passive profile.
- When authenticating with ISHSTS, specify:
baseurl/infosharestswebappname/issue/wsfed, wherebaseurlandinfosharestswebappnameare the values specified for thebaseurland theinfosharestswebappnameparameters, respectively. - When authenticating with ADFS STS, specify https://adfs.example.com/adfs/ls/.
- If you configure authentication with a different STS solution, specify the appropriate value based on the requirements for the selected STS and Identity Provider (IdP).
- When authenticating with ISHSTS, specify:
-
issuerwstrustmexurl -
This is the metadata address (Mex) of the STS for the active profile. It is used when generating proxy classes. For example:
ISHSTS: https://ish.example.com/ISHSTS/issue/wstrust/mex (where
ishrefers to an example server dedicated to Content Manager)ADFS: https://adfs.example.com/adfs/services/trust/mex
Other STS: Value based on that specific STS.
-
serviceusername -
Specify the user name for the Content Manager translation organizer service.
- When
issuerwstrustbindingtypeis UserNameMixed, specify the user name of the service user defined in the Content Manager user repository. - When
issuerwstrustbindingtypeis WindowsMixed, leave this field empty.
- When
-
servicepassword -
Specify the password matching serviceusername.
- When
issuerwstrustbindingtypeis UserNameMixed, specify the password matching the user defined withserviceusername. - When
issuerwstrustbindingtypeis WindowsMixed, leave this field empty. For this to work also change <validate>askpasswordtwiceifempty</validate> to <validate/>.
- When