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.

In the operating environment, install Service Platform 09-51 to update the version. You can 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 (5) Install Service Platform in each environment in H.2 Repository migration procedure in the operating environment during a new installation.

To install Service Platform as an update installation:

Perform (1) Perform update installation in each environment in H.3 Repository migration procedure in the operating environment during update installation.

Note

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 update-install Service Platform, stop all of them, and then start update installation.

The prerequisites for installation 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.

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.

• Service Adapter for Flat Files
• Service Adapter Architect for Flat Files
• Service Adapter for FTP
• Service Adapter Architect for FTP
• Service Adapter for Message Queue
• Service Adapter Architect for Message Queue
• Service Adapter for Object Access
• Service Adapter Architect for Object Access
• Service Adapter for TP1
• Service Adapter Architect for TP1
• Code Conversion - Development Kit
• Code Conversion - Server Runtime
• Code Conversion - Runtime
• TP1/Client/J

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

In the execution environment, install Service Platform 09-51 to update the version.

You can install Service Platform as a new installation or an update installation in the execution environment.

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 H.2 Repository migration procedure in the operating environment during a new installation.

To install Service Platform as an update installation:

Perform (1) Perform update installation in each environment in H.3 Repository migration procedure in the operating environment during update installation.

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.

• add.class.path=TP1-adapter-installation-directory\lib\adptp1rt.jar
• add.class.path=file-adapter-installation-directory\lib\adpffrt.jar
• add.class.path=Object-Access-adapter-installation-directory\lib\adpoart.jar
• add.class.path=Object-Access-adapter-installation-directory\usrlib\adpoaow.jar
• add.class.path=Message-Queue-adapter-installation-directory\lib\adpmqrt.jar
• add.class.path=FTP-adapter-installation-directory\lib\adpftprt.jar
• add.class.path=FTP-adapter-installation-directory\lib\ftp_common.jar
• add.class.path=code-conversion-library-installation-directory\java\codeconv.jar
• add.class.path=TP1/Client/J-installation-directory\LIB\TP1Client.jar

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\

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.

• Service Adapter for Flat Files
• Service Adapter Architect for Flat Files
• Service Adapter for FTP
• Service Adapter Architect for FTP
• Service Adapter for Message Queue
• Service Adapter Architect for Message Queue
• Service Adapter for Object Access
• Service Adapter Architect for Object Access
• Service Adapter for TP1
• Service Adapter Architect for TP1
• Code Conversion - Development Kit
• Code Conversion - Server Runtime
• Code Conversion - Runtime
• TP1/Client/J

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:

• Execute the update command (mngenvupdate).
• Add properties to mserver.properties (Management Server environment configuration file).
  The properties to be added are shown below. If you start Management Server without adding these properties, commands whose names begin with csc might fail. For details about how to add properties, see 2.1.6(1) Setting mserver.properties (Management Server environment settings file).
  

  ejbserver.naming.port
  ejbserver.server.edition.settingforce

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 version of the repository is equal to or older than the version of the installation.
• The version of the repository is 08-00 or later (but older than that of the installation).

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
 

Start the updated HCSC server.

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

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.

On all HCSC servers that make up the load-balancing cluster, perform (4) 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 uCosminexus BPM/ESB Service Platform Basic Development Guide.

The notes that apply to rolling update are the same as the notes that apply to update of the development environment, operating environment, and execution environment. For notes on rolling update, see G.4(15) Notes on rolling update.