Optional input parameters in inputparameters.xml
By default, the file inputparameters.xml contains only a set of mandatory properties. Optional parameters are either calculated by Content Manager, or they have a predefined default value. This section lists and describes the optional input parameters that you can set in the inputparameters.xml file. Only Content Manager experts should change these parameters.
Optional parameters
| Name | Description | Default value |
|---|---|---|
projectsuffix | Whenever more than one project is installed, the projectsuffix value indicates the project. Remember to make web application names and service ports unique as well. The value of this parameter is given as PROJECTSUFFIX in the rest of this table. | (none) |
webpath | The path of the folder in which the website folder is created. | APPPATH (calculated) |
datapath | The path of the folder in which the data folder is created. For example, when the datapath is c:\InfoShare the logs will be created in the folder c:\InfoShare\Data\Logs\. | APPPATH (calculated) |
workspacepath | This path is a temporary folder in which all the folders and files are copied and modified before the actual installation. | APPPATH\_Workspace (calculated) |
infosharecswebappname | The name of the web application that offers Organize Space, Draft Space and Review Space Services. | ISHCS + PROJECTSUFFIX |
infoshareauthorwebappname | The name of the Content Manager web application hosting ClientConfig and ASP.NET pages. | ISHCM + PROJECTSUFFIX |
infosharewswebappname | The name of the web application for Content Manager web services. | ISHWS + PROJECTSUFFIX |
infosharestswebappname | The name of the web application with the deprecated Content Manager Secure Token Service (STS). | ISHSTS + PROJECTSUFFIX |
websitename | The name of the website in which all web applications will be created. | Default Web Site |
infoshareidwebappname | The name of the web application for the Tridion Docs Identity Provider. | ISHID + PROJECTSUFFIX |
infoshareextwebappname | The name of the web application with the Web Extensions Service hosting customizations for Organize Space. | ISHEXT + PROJECTSUFFIX |
infoshareamwebappname | The name of the Access Management web application. | ISHAM + PROJECTSUFFIX |
infosharemetricswebappname | The name of the Metrics web application. | ISHMT + PROJECTSUFFIX |
localservicehostname | Indicates the local service hostname part of the base URL. This can be localhost or the machine name. It will be used by all service side components that access the WCF Services on the same box. | the NetBIOS name of this local computer (calculated) |
ps_fo_processor | The fully qualified file name of the XSL-FO processor, for example C:\Program Files\AntennaHouse\AHFormatterV6\AHFCmd.exe. | the highest installed version in %ProgramFiles% (calculated). |
ps_htmlhelp_processor | The fully qualified file name of the HTML Help processor. | C:\Program Files (x86)\HTML Help Workshop\hhc.exe
|
ps_javahelp_home | The full path to a JavaHelp JHHOME folder, used when you want to publish with the JavaHelp output type. | C:\javahelp\jh2.0
|
solrlucene_service_port | The port that the SolrLucene service uses. This port must be unique for each Content Manager instance installed on a server. | 8983 |
basehostname | The hostname part of the base URL. This value will be calculated using BASEURL as input, stripping the protocol http or https (e.g. ish.example.com) | BASEURL (calculated) |
servicecertificatethumbprint | The thumbprint of an already installed certificate (e.g. A43489159A520F0D93D032CCAF37E7FE20A8B419) for unique service identification. You can repurpose your SSL certificate. Note that all your linked web application servers in a farm should offer the same trusted certificate. | from HTTPS binding of websitename |
servicecertificatevalidationmode | The validation mode specified here decides how the application-to-application communication validates service certificates (specified in servicecertificatethumbprint). The allowed options are: ChainTrust, PeerTrust, PeerOrChainTrust or None. Setting the mode to None causes any certificate to be accepted. | ChainTrust |
servicecertificatesubjectname | Specify the subject name of an already installed certificate for unique service identification. You can repurpose your SSL certificate. Note that all your linked web application servers in a farm should offer the same trusted certificate. | from HTTPS binding of websitename |