Perform the following tasks as needed before you upgrade the Appliance.
If you ever modified the Jetty configuration settings on the existing Appliance, your custom settings will be lost when you replace the Appliance during upgrade. Copy the settings to /vastorage, or make a note of the settings so you can re-configure them after the upgrade.
To copy the Jetting configuration settings:
Enable SSH on the PTM Appliance.
From your management computer, start an SSH session for ptm-ipaddr-or-dns-name on port 22, then log in as the root user to the Appliance.
You can use any SSH tool, such as Putty.
Save a copy of the /opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/ssl.ini file, or make a note of the Jetty keystore settings for the following parameters. The default values for PTM are shown here. Your settings might be different if you have ever made changes to the Jetty keystore using the appropriate keytool software. You will need to reset these keystore settings after the upgrade. Changeit is the actual password value in this example.
# Setup a keystore and truststore
jetty.keystore=certs/keystore
jetty.truststore=certs/keystore
# Set the passwords.
jetty.keystore.password=changeit
jetty.keymanager.password=changeit
jetty.truststore.password=changeitIf you customized the theme in PlateSpin Transformation Manager, you might need to save a copy of your files, depending on how you applied your theme.
Custom Theme in a separate folder: If you created a new custom theme (copied default themes to new directory and edited), the custom theme is saved in /vastorage and will be available after you upgrade the PTM Appliance.
After the upgrade, you must copy the new default theme files and re-create your custom theme by merging your settings into the latest format. See Section 11.3, Resetting Your Custom Theme after an Upgrade.
Customized default theme files: If you customized the default theme files in the default location (/vastorage/ptm/themes/ directory), your changes will be overwritten when you deploy a new Appliance.
Before you upgrade the PTM Appliance, go to the /vastorage/ptm/themes/ directory, then save your customized default theme files to a location where they will be available after the upgrade.
After the upgrade, you can reapply your custom settings to the new default theme files. See Section 11.1, Configurable Theme Components. Alternatively, create a custom theme. See Section 11.2, Setting Up Your Custom Theme.
When you shut down the PlateSpin Transformation Manager Appliance in the Appliance Shutdown step, PTM automatically archives essential configuration files in the vaconfig.zip file in the /vastorage/conf/ folder on Disk 2 (/vastorage).
Archive: vaconfig.zip extracting: etc/sysconfig/novell/NvlVAinit extracting: etc/Novell-VA-release extracting: usr/lib64/jvm/java/jre/lib/security/cacerts extracting: etc/opt/novell/ganglia/monitor/gmond.conf extracting: etc/opt/novell/ganglia/monitor/gmetad.conf extracting: etc/opt/novell/ganglia/monitor/net.d/recv.conf extracting: etc/opt/novell/ganglia/monitor/net.d/send.conf extracting: etc/sysconfig/SuSEfirewall2 extracting: etc/sysconfig/scripts/SuSEfirewall2-custom extracting: etc/ssh/sshd_config extracting: etc/opt/microfocus/ps_transform_mgr/config/system.properties extracting: etc/opt/microfocus/ps_transform_mgr/config/quartz-scheduler.cfg extracting: etc/opt/microfocus/ps_transform_mgr/config/pgusr.in extracting: etc/opt/microfocus/ps_transform_mgr/config/connector.properties extracting: etc/opt/microfocus/ps_transform_mgr/config/war-tm-config.xml extracting: etc/opt/microfocus/ps_transform_mgr/config/com.netiq.tm.backend.auth.cfg extracting: etc/opt/microfocus/ps_transform_mgr/config/transformationmanager-themes.cfg extracting: etc/opt/microfocus/ps_transform_mgr/config/com.netiq.tm.backend.connpool.cfg extracting: etc/opt/microfocus/ps_transform_mgr/config/security/tm_cert.der extracting: etc/opt/microfocus/ps_transform_mgr/config/security/tmKeystore.jks extracting: etc/sysconfig/postgresql extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/webapp.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/servlet.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/https.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/jaas.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/ssl.ini.bak extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/servlets.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/http.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/annotations.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/ssl.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/logging.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/gzip.ini extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/start.d/https.ini.bak extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/resources/logging.properties extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/resources/logback.xml extracting: opt/microfocus/ps_transform_mgr/tm-jetty-base/resources/jetty-logging.properties extracting: opt/microfocus/migrate_connector/config/settings.cfg extracting: opt/microfocus/migrate_connector/custom_callouts/__init__.py extracting: opt/microfocus/migrate_connector/custom_callouts/pre_cutover_testing_callout.py extracting: opt/microfocus/migrate_connector/custom_callouts/submit_validation_callout.py extracting: opt/microfocus/migrate_connector/custom_callouts/post_cutover_testing_callout.py extracting: opt/microfocus/migrate_connector/custom_callouts/custom_import_callout.py