If you are upgrading to a later release of Stardust from an earlier release, there are a few things you have to take in account. The following sections document the changes required for specific issues.
For general upgrading, refer to the following topics:
Refer to the following section for specific upgrading issues:
For details on how to upgrade a Stardust version, refer to the Installation Guide. For known issues while upgrading, please refer to the Troubleshooting chapter.
To upgrade the audit trail from a previous Stardust version, use the following sysconsole command:
sysconsole upgraderuntime
with the following arguments:
-data, -a - Performs only data migration, preventing any SQL DDL execution. Combine with -step
to perform migrations involving temporary schema versions.-ddl, -l <arg> - Spools the SQL DDL defining the audittrail schema migration into the
specified file. No modifications to the audittrail will be performed.-describe, -d - Describes the migration steps involved, including any temporary schema versions.
No modifications to the audittrail will be performed.-ignorelock, -i - forces an upgrade run even if the audit trail DB is already locked for
upgrade.-recover, -r - to force a recovery run of the upgrade.-step, -s - Performs exactly one migration step. May require multiple invocations to fully
perform migrations involving temporary schema versions.For detailed information on the sysconsole command, refer to chapter The Sysconsole Command of the Operation Guide.
Refer to the release notes of the current Stardust version ( Release Notes 5.0.0 ) for details on runtime upgrades like schema changes that will be performed with this command on earlier versions.
You can perform a model upgrade via the Sysconsole command or from the Eclipse environment.
Please ask your administrator to perform the upgrade or use the sysconsole command option
upgrademodel
to upgrade to a newer Stardust version:
sysconsole upgrademodel -file <file> -source <source> -target <target>
Whereby:
file is the model file to upgrade inplace,source is the source file to upgrade andtarget is the target file for upgrade.For more information on using the sysconsole command please refer to the chapter The Sysconsole Command in the Operation Guide.
In case you import a model in Eclipse with an earlier Stardust version than you use, you will be prompted and asked if you want to upgrade to the currently installed version. Click Yes to upgrade the model.
Currently there is no automated facility for upgrading the libraries contained in existing Dynamic Web projects with Stardust facets to the most recent Stardust version. In that case you have to upgrade the Process Manager facets manually as described in detail in the section Upgrading Process Manager Facets of the chapter Creating a Dynamic Web Project in Eclipse .
Exception handling for embedded service factory services changed with version 2.1.0 to return unwrapped exceptions as with regular API calls. Additionally, raised exceptions now properly honor an existing transaction rollback policy. Note that this change might potentially break existing workarounds you have applied in an earlier version.
A runtime upgrade against audit trails created with earlier versions adds the new predefined process instance link type SPAWN to the audit trail. The SPAWN link type describes the case for just creating a new root process instance from an existing one with optionally copying data. This runtime upgrade job is optional if you are not using the spawn functionality.
Note that this upgrade job is a trivial one and can be applied without any risk!
A runtime upgrade for versions earlier than 1.1 adds the following columns to your schema:
In case you are using the JavaScript source file
IppProcessPortalClient.js
in your external Web application, you need to upgrade it with the new one provided in the
ipp-workflow-perspective.jar
file of the new Stardust installation.