Orchestrator Components That Are Not Upgraded - Novell PLATESPIN ORCHESTRATE 2.0.2 - UPGARDE GUIDE 10-09-2009 Upgrade Manual

2 Use the following commands to run the modified script as the PostgreSQL database
administrator for the remote database:
su - postgres
psql -h <psql-server-addr> -d postgres -U postgres -f audit_db_upgrade.sql
3 Use the following command to log into PostgreSQL, using the database name and schema
owner substituted in Step 1 above:
su - postgres
psql -h <psql-server-addr> -d zos_db -U zos -f audit_db_upgrade.sql
4 Confirm that the database username and password match the values used when creating the
schema owner database user in
Database" in the
example, the username is
5 Confirm that the database username and password match the values you replaced in the
variables of the
6 Click Connect.
The Is Connected check box is selected: the Orchestrate Server is connected to the database so
that any queued data and subsequent job, user, and resource events are written there.
2.2 Orchestrator Components That Are Not
Upgraded
When you upgrade from the ZENworks Orchestrator Server to PlateSpin Orchestrate, the core
components are not upgraded or redeployed. Instead, the old core components are replaced with new
core PlateSpin Orchestrate components. If, however, you made any changes to the core components,
those changes are saved and you can manually re-enter the configuration you want after the upgrade.
For example, suppose you have deployed the Xen* provisioning adapter job and you made custom
changes to the
repackages the Xen provisioning adapter by creating a
Orchestrator_instance_directory/snapshot/deployment/core/xen.sar
archive contains the current state of the Xen provisioning adapter, including your custom changes.
32 PlateSpin Orchestrate 2.0 Upgrade Guide
"Creating a PlateSpin Orchestrate User for the PostgreSQL
PlateSpin Orchestrate 2.0 Installation and Configuration
and the password is
zos
script. In this example, the username is
.sql
policy file. When the Orchestrator Server prepares for an upgrade, it
xen30
.
zos
and the password is
zos
archive and then stores it in
.sar
Guide. In this
.
zos
/
. This
xen.sar