With the KDCUPD tool (KDCFILE UPDate) you can migrate important user data and administration information after regenerating your UTM application:
In standalone UTM applications, KDCUPD transfers the data from the old to the new KDCFILE.
In UTM cluster applications, there is a distinction between node updates (updating the KDCFILE of a single node application) and cluster updates (updating of UTM cluster files).
Furthermore, you can switch with the help of KDCUPD from an older openUTM version to the current openUTM version without the data in the KDCFILE of the previous production application.
KDCUPD in standalone applications
In a standalone UTM application, KDCUPD can be used for both UTM-S and UTM-F.
In the case of UTM-S, KDCUPD enables the user data to be transferred from the previous KDCFILE to the new KDCFILE on completion of the application run. KDCUPD can transfer all user data or only specific user data, as required.
Once all the user data has been transferred by KDCUPD and the application has been restarted, the users can resume their work:
Interrupted services are continued.
Processing of UTM-controlled message queues continues:
all asynchronous messages are output
all background jobs are executed
all time-driven jobs are processed by openUTM at the specified time
All messages in service-controlled queues are available for further processing.
KDCUPD in UTM cluster applications on Linux, Unix and Windows systems
In UTM cluster applications, KDCUPD can be used with both UTM-S and UTM-F. KDCUPD enables you to perform both node updates and cluster updates.
Node updates
In the case of a node update, KDCUPD transfers administration and user data from a node application’s old KDCFILE to a node application's new KDCFILE. Data that applies locally at node level such as TLS, asynchronous messages or background jobs is transferred.
If there are a large number of changes to the generation (for example, new connections to partner applications), it is possible to perform a node update while the UTM cluster application is running (online update). In this case, the node update is performed for each individual node in sequence, i.e. the node application is terminated, the data is transferred using KDCUPD and the node application is then started again. The remaining node applications continue to run during this process.
For some changes, it is necessary to terminate the UTM cluster application.
Cluster updates
In the case of cluster updates, KDCUPD transfers administration and user data from the old UTM cluster files to the new UTM cluster files. To do this, it is necessary to terminate the UTM cluster application.
It is only necessary to perform a cluster update if fundamental changes are made to the cluster configuration, e.g. if the number of generated node applications or the number of cluster page pool files is increased.
During a cluster update, data that is valid globally in the cluster (ULS, GSSB, service data, passwords, locales) is transferred
After a cluster update, it is generally necessary to perform a node update for each node application.
| For further information on using KDCUPD in a UTM cluster application, see "Update generation in a cluster" in the platform specific openUTM manual “Using UTM Applications”. |
Checking the KDCFILE for consistency
KDCUPD also provides the CHECK option, with which you can check the files of a KDCFILE for consistency without transferring user data to a new KDCFILE.
Migrating with KDCUPD
The UTM tool KDCUPD can also be used to migrate to another version of openUTM. You can transfer user data from the KDCFILE of the preceding versions into the newly created KDCFILE of the current openUTM version. You start the application under the current openUTM version using this KDCFILE, and afterwards the users can continue with their current work. For instance, after upgrading to a follow-up version, a time-driven print job initiated with the preceding version can be automatically activated by the current version - exactly at the desired time.
Migrating to a 64-bit environment with KDCUPD on Linux, Unix and Windows systems
KDCUPD can be used to transfer information from a 32-bit application environment to a 64-bit application environment. This means that you are able to switch over to a 64-bit environment quickly and without loss of data.
| You will find more information on KDCUPD in the openUTM Manual “Generating Applications”. |