|
If a specific application server (CP-Server) should be preselected when the CP-Cockpit client is started for the first time, you can define this during the software distribution.
Please note:
|
You can only define a preset login if no login to the CP-Cockpit Client has yet taken place on that system. Depending on the login type, the value for the login is saved in the login.json file, which is in the path: "%PROGRAMDATA%\CP Corporate Planning GmbH" and "%APPDATA%\CP Corporate Planning AG".
|
Important:
|
The previously used silent properties SETUP_LOGINSETTING_PROTOCOL, SETUP_LOGINSETTING_SERVER and SETUP_LOGINSETTING_PORT are no longer available.
|
The following new configuration options apply:
Set the login credentials (largely automatically)
| • | "CPSERVER_HOSTNAME"
Specify the host name on which the CP-Server is installed. We recommend the FQDN of the server. This specification is required.
|
| • | "CPCONFIG_FULLFILENAME"
In this property, you can specify the absolute path to an existing cp.config file. The specified config is then read and the values are applied to the client. A local cp.config file, such as the one stored on the server system, will be detected and read automatically. |
Please note:
|
Problems may occur when cp.config is read via UNC path or in paths containing spaces via command line. We recommend copying cp.config to a short path on the local system first.
|
If no path to a cp.config is specified, the localhost default will be set. In most cases, the connection to the CP-Server should then be specified fully manually via command line.
Set the login credentials (fully manually)
| • | "CPSERVER_HOSTNAME"
Specify the host name on which the CP-Server is installed. We recommend the FQDN of the server. This specification is required.
|
| • | "CPCONFIG_CONNECTION_WEBMODULEHOST"
Complete URI as specified in CP-Config under "Connection settings\Client-Server communication". If necessary, replace the server name with the FQDN of the CP-Server computer. This specification is required for manual configuration.
|
The following configurations must correspond to the CP-Config settings in "Connection Settings\Identity":
| • | "CPCONFIG_CONNECTION_PIPEENABLED"
If the connection is to be established via net.pipe, set this value to "True".
|
| • | "CPCONFIG_CONNECTION_TCPENABLED"
If the connection is to be established via net.tcp, set this value to "True". The default port is 8083.
|
| • | "CPCONFIG_CONNECTION_TCPPORT"
If the connection is to be established via net.tcp, but the port is different from 8083, specify the desired port for the TCP connection here.
|
| • | "CPCONFIG_CONNECTION_HTTPENABLED"
If the connection is to be established via http, set this value to "True". The default port is 80.
|
| • | "CPCONFIG_CONNECTION_HTTPPORT"
If the connection is to be established via http, but the port is different from 80, specify the desired port for the HTTP connection here.
|
| • | "CPCONFIG_CONNECTION_HTTPSENABLED"
If the connection is to be established via https, set this value to "True". The default port is 443.
|
| • | "CPCONFIG_CONNECTION_HTTPSPORT"
If the connection is to be established via https, but the port is different from 443, specify the desired port for the HTTPS connection here. |
Via Setup.exe
If Setup.exe is used for the installation, all the missing system prerequisites (for example .NET) will be installed.
Example 1:
Setup.exe /L1031 /S /v/qn /V"ADDLOCAL=ALL CPSERVER_HOSTNAME=cpserver.domain CPCONFIG_CONNECTION_WEBMODULEHOST=https://cpserver.domain:8733/
| • | Full installation (ADDLOCAL=ALL) |
| • | with the host name of the CP-Server installation "cpserver.domain" |
| • | with the web module host connection as defined in the cp.config of the CP-Server CPCONFIG_CONNECTION_WEBMODULEHOST=https://cpserver.domain:8733/ |
| • | with the default protocol net.tcp and default port 8083 |
Example 2:
Setup.exe /L1031 /S /v/qn /V"ADDLOCAL=ALL CPCONFIG_CONNECTION_WEBMODULEHOST=https://cpserver.domain:8733/ CPSERVER_HOSTNAME=cpserver.domain CPCONFIG_CONNECTION_HTTPSENABLED=True CPCONFIG_CONNECTION_HTTPSPORT=995"
| • | Full installation (ADDLOCAL=ALL) |
| • | with the host name of the CP-Server installation "cpserver.domain" |
| • | with the web module host connection as defined in the cp.config of the CP-Server CPCONFIG_CONNECTION_WEBMODULEHOST=https://cpserver.domain:8733/ |
| • | with HTTPS protocol (CPCONFIG_CONNECTION_HTTPSENABLED) and the alternate port 995 (CPCONFIG_CONNECTION_HTTPSPORT) |
Via the CP-Cockpit.msi
If the MSI file is used for the installation, the missing system prerequisites (for example .NET) will not be installed. These must be distributed beforehand for a full installation.
Example:
C:\Windows\system32>msiexec.exe /i "PATH\CP-Cockpit.msi" ADDLOCAL=ALL CPCONFIG_CONNECTION_WEBMODULEHOST=https://cpserver.domain:8733/ CPSERVER_HOSTNAME=cpserver.domain CPCONFIG_CONNECTION_HTTPSENABLED=True CPCONFIG_CONNECTION_HTTPSPORT=995 /q
| • | Full installation (ADDLOCAL=ALL) |
| • | with the host name of the CP-Server installation "cpserver.domain" |
| • | with the web module host connection as defined in the cp.config of the CP-Server CPCONFIG_CONNECTION_WEBMODULEHOST=https://cpserver.domain:8733/ |
| • | with HTTPS protocol (CPCONFIG_CONNECTION_HTTPSENABLED) and the alternate port 995 (CPCONFIG_CONNECTION_HTTPSPORT) |
|
