Upgrading KCM from 5.4.0 and earlier
An upgrade from KCM 5.4.0 or earlier moves registration information from the Contract Manager to the KCM instances. If any KCM instances exist in the previous installation, the upgrade tool additionally requires the following parameters:
|
Parameter |
Required / Optional |
Description |
|---|---|---|
| Registration!ContractManagerLocation |
Required |
Specifies the Contract Manager location when registering the new KCM instances:
|
| ContractManager!RegistrationPort |
Optional |
The port for Contract Manager to use to register instances. The default value is 10443. |
| Registration!ContractManagerHost |
Optional |
The host of the Contract Manager on which the old KCM instances were registered. This is only needed when the Contract Manager is remote, but can also be used to explicitly set or override the host when the Contract Manager is local. If the old installation has a local Contract Manager, defaults to localhost. |
| Registration!ContractManagerConfigurationFile |
Optional |
The configuration export file of the Contract Manager, used for transferring registration information to the instances. This is only needed when the Contract Manager is remote. When a KCM instance cannot be located in the export file, the upgrade continues, but the instance will not have its registration configured and will not be started. |
| Registration#n!Partner | Optional |
The partner with which the KCM instance with number 'n' will be associated. This is only needed when the instance is not registered on a Contract Manager. |
| Registration#n!Customer | Optional |
The customer with which the KCM instance with number 'n' will be associated. This is only needed when the instance is not registered on a Contract Manager. |
| Registration#n!ExampleWebAppName | Optional |
The name of the example web application that will be created for the instance number 'n'. This information will not to be taken over from the old installation. If omitted, the example web application will not be created. |
An upgrade from KCM 5.4.0 or earlier skips contract types and interfaces that are not in use by an active contract. If you need to have them in the upgraded installation, you will need to define them manually again.