The following table details the types of data that is migrated on the Master Server.
Table 9–1 Migration Overview
Data on the Master Server |
Is the Data Migrated? |
Mechanism for Migration |
---|---|---|
PostgresSQL data |
Yes |
SQL scripts |
CLI Client script for changes to existing commands |
No |
|
Migration of objects serialized through CLI Client |
No |
|
Migration of changes to the config.properties file on each node |
Yes |
Properties listed in the file are migrated using the details found in Migration Details for the Properties File. |
Resource migration |
Yes |
Copy the resources directory. |
The centerrun.properties file is migrated to the config.properties file. During the migration, the value of each property in the 4.0 file is compared to the value of the property in the 4.1 config.properties file. If the value is the same, the property is ignored. If the value is different, then the 4.0 value is copied to the 4.1 config.properties file. If a property exists in the 4.0 file and is absent in the 4.1 file, then the 4.0 value is added to the 4.1 file. Values for the following properties are not migrated to the 4.1 config.properties file:
webserver.TomcatHome
rsrc.localrepo
db.port
hostdb.ms.ipaddress
hostdb.ms.port
note.mailsubject
net.server.nconn
net.server.type.1
net.server.ip.1
net.server.port.1
net.server.parms.1
note.url
pe.defaultUserToRunAs
hostdb.ms.connectiontype
pe.maxSimulPlans
If you have changed the values for any of these properties in the 4.0 properties file, you will need to manually change the value in the 4.1 config.properties file.