Hitachi

uCosminexus Service Platform Setup and Operation Guide

G.4 Migration procedure for a rolling update

Rolling update is an update installation that is performed without fully stopping the system.

Rolling update can be performed only when the version to be updated is 07-50 or later. If the version to be updated is earlier than 07-50, install version 11-00 as a new installation. For notes on rolling update, see (15) Notes on rolling update.

Rolling update requires two or more HCSC servers that make up a load-balancing cluster.

Update Service Platform from the old version (07-50 or later) to the new version (11-00), following the steps in the below figure ((1) Export the repository (operating environment) to (13) Respecify the request transmission control (load balancer) settings).

Figure G‒3: Migration procedure for a rolling update

[Figure]

The steps in Figure G-3 ((1) Export the repository (operating environment) to (13) Respecify the request transmission control (load balancer) settings) are described below. Note that, for the HCSC servers other than the first, you must perform (14) Perform tasks on the HCSC servers other than the first HCSC server (execution environment).

For details about the commands used in these steps, see Chapter 5. Commands (Operating and Execution Environments) in the uCosminexus Service Platform Reference Guide. For details about the tasks performed in the development environment, see the Service Platform Basic Development Guide.

Important note

  • From version 07-60, the development environment and operating environment cannot share the same repository. If the repository is shared by the development and operating environments in the old version, prepare separate repositories in these environments before starting migration. For details about the migration procedure, see A.3 Migrating procedure when a repository is shared between development environment and operating environment in earlier version in the Service Platform Basic Development Guide.

  • You cannot perform the following operations in the old system until rolling update finishes:

    - Use the cscsvsetup command to set up a new HCSC server.

    - Use the csccompodeploy command to deploy a new HCSC component.

Organization of this subsection

(1) Export the repository (operating environment)

Before you update the version, in the operating environment, export the repository as a backup. If there are multiple repositories, export all necessary repositories as backups.

In the operating environment, execute the cscrepctl command (with the -export option) to export the repository (or repositories).

For details about how to export a repository, see 4.2 Exporting Repository Information.

To Page Top

(2) Install Service Platform in the development and operating environments

In the development and operating environments, install Service Platform 11-00 to update the version.

In the development environment, install Service Platform as a new installation or an update installation. In the operating environment, install Service Platform as an update installation.

To install Service Platform as a new installation:

Perform (2) Delete HCSC components (operating environment) to (6) Set up an HCSC server (operating environment) in G.2 Migration procedure for a new installation.

To install Service Platform as an update installation:

Perform (2) Perform update installation in each environment to (5) Uninstall products in G.3 Migration procedure for an update installation.

The prerequisites for installing Service Platform in the development and operating environments are as follows.

Prerequisites:

  • HCSC servers have been set up.

  • Service Platform and Reliable Messaging are not running.

  • The embedded database (if used) is not running.

  • The HCSC server, J2EE server, and HCSC components are not running.

Notes

Note the following points when you perform update installation:

  • If the J2EE server, Management Server, PRF, and other components that make up the Service Platform execution environment are running in the environment in which you install Service Platform, stop all of them, and then start update installation.

  • If an embedded database is used, stop it, and then start update installation.

To Page Top

(3) Change the class path of the J2EE server (development environment)

If the version to be updated is earlier than 09-00 and the option definition file for the J2EE server (usrconf.cfg) contains the entries listed below, delete all of them. When you change the definition, we recommend that you use Smart Composer functionality or management portal.

To Page Top

(4) Perform migration of old option adapter definition files (development environment)

Migration of the option adapters that were used in a version earlier than 09-00 requires the tasks described below.

(a) Migration of the TP1 adapter definition files

Copy the TP1 adapter execution-environment property files. The files to be copied and the copy destination directory are as follows:

Files to be copied: TP1-adapter-installation-directory\config\*.properties

Copy destination: Service-Platform-installation-directory\CSC\custom-adapter\TP1\config\

(b) Migration of the file adapter definition files

Copy the file adapter execution-environment property files. The files to be copied and the copy destination directory are as follows:

Files to be copied: file-adapter-installation-directory\config\*.properties

Copy destination: Service-Platform-installation-directory\CSC\custom-adapter\File\config\

(c) Migration of the Object Access adapter definition files

Copy the Object Access adapter execution-environment property files. The files to be copied and the copy destination directory are as follows:

Files to be copied: Object-Access-adapter-installation-directory\config\*.properties

Copy destination: Service-Platform-installation-directory\CSC\custom-adapter\OA\config\

(d) Migration of the Message Queue adapter definition files

Copy the Message Queue adapter execution-environment property files. The files to be copied and the copy destination directory are as follows:

Files to be copied: Message-Queue-adapter-installation-directory\config\*.properties

Copy destination: Service-Platform-installation-directory\CSC\custom-adapter\MQ\config\

(e) Migration of the FTP adapter definition files

Copy the FTP adapter command definition files and FTP adapter execution-environment property files. The files to be copied and the copy destination directory are as follows:

Files to be copied: FTP-adapter-installation-directory\config\*.properties

Copy destination: Service-Platform-installation-directory\CSC\custom-adapter\FTP\config\

To Page Top

(5) Uninstall products

The products listed below come with Service Platform 09-00 or later. If you update Service Platform from a version earlier than 09-00 and any of these products have already been installed, we recommend that you uninstall them.

To Page Top

(6) Import and export the repository (development and operating environments)

In (1) Export the repository (operating environment) above, you exported the repository. Here, import the exported repository in the development environment. The new version inherits the repository information from the old version. Then, similarly, import the exported repository in the new operating environment so that the repository information is also inherited in the new operating environment.

The tasks to be performed in import and export of the repository differ depending on how the development environment was installed in (2) Install Service Platform in the development and operating environments, as shown below.

If Service Platform is installed as a new installation:

Perform (7) Import the repository (development environment) to (9) Import the repository (operating environment) in G.2 Migration procedure for a new installation.

If Service Platform is installed as an update installation:

Perform (6) Import the repository (development environment) to (8) Import the repository (operating environment) in G.3 Migration procedure for an update installation.

To Page Top

(7) Specify the request transmission control (load balancer) settings

Specify the load balancer settings so that requests are not sent to the HCSC server being updated. Before doing this, make sure that no requests are being sent. How to specify the load balancer settings differs depending on the specifications of the load balancer you are using.

To Page Top

(8) Install Service Platform in the execution environment

In the execution environment, install Service Platform 11-00 to update the version.

In the execution environment, install Service Platform as a new installation or an update installation.

To install Service Platform as a new installation:

Perform (2) Delete HCSC components (operating environment) to (6) Set up an HCSC server (operating environment) in G.2 Migration procedure for a new installation.

To install Service Platform as an update installation:

Perform (2) Perform update installation in each environment to (5) Uninstall products in G.3 Migration procedure for an update installation.

To Page Top

(9) Update Service Platform and Reliable Messaging (execution environment)

Update Service Platform and Reliable Messaging by using the following procedure, which is also required when the version to be updated is earlier than 09-00:

To Page Top

(10) Update the execution environment (operating environment)

Update the version of the execution environment from the operating environment.

(a) Prerequisites

The execution environment can be updated when all of the following conditions are satisfied:

  • Management Server is running.

  • The embedded database (if used) is running.

  • The versions of the repository and installation are the same.

    If the repository version and installation version do not match, update the development environment, and then execute cscrepctl -import repository-ZIP-file to update the repository.

If the prerequisites listed above are not satisfied, satisfy them in the order in which they are listed.

(b) How to update the version

Execute the cscenvupdate command to update the version of the repository and HCSC server. 

cscenvupdate -csc name-of-the-HCSC-server-to-be-updated

To Page Top

(11) Start the HCSC server (operating environment)

Start the updated HCSC server.

To Page Top

(12) Start the HCSC components (operating environment)

Start the HCSC components that are deployed on the HCSC server whose version was updated in (10) Update the execution environment (operating environment).

To Page Top

(13) Respecify the request transmission control (load balancer) settings

Respecify the load balancer settings so that requests are sent to the updated HCSC server. How to specify the load balancer settings differs depending on the specifications of the load balancer you are using.

To Page Top

(14) Perform tasks on the HCSC servers other than the first HCSC server (execution environment)

On all HCSC servers that make up the load-balancing cluster, perform (7) Specify the request transmission control (load balancer) settings to (13) Respecify the request transmission control (load balancer) settings.

If you choose to convert the existing repository information before or after version update in the development environment, and to use the converted repository information with the new version, see Appendix A. Migrating from old version in the Service Platform Basic Development Guide.

To Page Top

(15) Notes on rolling update

(a) If the target of rolling update is version 08-70 or earlier

The cscenvupdate command might fail when all of the following conditions exist:

  • Service Platform has been set up in a configuration that uses HiRDB (as a database) and Reliable Messaging.

  • Business processes are used.

  • The update being performed is the first update performed in the cluster.

  • Rolling update is performed for Service Platform whose version is 08-70 or earlier.

The following describes the countermeasures for operating the system normally under the above conditions, and provides an operation example.

  • Countermeasures:

    Perform the following procedure (steps 1 to 4) on all running HCSC servers:

    1. Stop the execution log reference command and system operation GUI.

    2. Specify the request transmission control settings to prevent requests from being sent to the HCSC servers.

    3. Stop HCSC server receptions (standard and user-defined receptions).

    4. Discard the all resource adapter pools (by using the cjclearpool command).

    After performing the above procedure, execute the cscenvupdate command on one of the updated HCSC servers. You do not need to perform the above procedure on the rest of the updated HCSC servers. Note that after normal termination of the first cscenvupdate command is confirmed, the functions stopped in steps 1 to 3 can be restarted regardless of when an operation is performed on the second and following servers.

  • Operation example:

    This example assumes that the version is updated under the following conditions:

    • The cluster consists of HCSC servers A, B, and C.

    • While HCSC servers B and C are running, the cscenvupdate command is executed on HCSC server A.

    To run the system normally under the above conditions, perform the following procedure:

    1. Stop the execution log reference command and system operation GUI.

    2. Specify the request transmission control settings to prevent requests from being sent to HCSC servers B and C.

    3. Stop receptions of HCSC servers B and C (standard and user-defined receptions).

    4. Use the cjclearpool command to discard all resource adapter pools of HCSC servers B and C.

    5. Execute the cscenvupdate command on HCSC server A.

(b) If the target of rolling update is version 09-00 or later

The cscenvupdate command might fail when all of the following conditions exist:

  • Service Platform has been set up in a configuration that uses a database and Reliable Messaging.

  • Business processes are used.

  • The update being performed is the first update performed in the cluster.

In this case, stop online processing, and then perform rolling update, following the procedure in H.4 Repository migration procedure in the operating environment during rolling update.

To Page Top

Trademarks

All Rights Reserved. Copyright (C) 2022, Hitachi, Ltd.