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.

Before you update the version, in the execution environment, delete all HCSC components deployed on the HCSC server. If there are multiple HCSC servers, delete all HCSC components from all of the HCSC servers.

In the operating environment, execute the csccompoundeploy command as shown below. This command deletes all HCSC components deployed on the specified HCSC server.

 
csccompoundeploy -csc HCSC-server-name -type {adapter|bp} -name service-adapter's-service-ID
 

Before you update the version, in the execution environment, perform unsetup of all HCSC servers.

In the operating environment, execute the cscsvunsetup command to perform unsetup of all HCSC servers. For a test environment in which Service Platform was set up by using HCSC Easy Setup, use HCSC Easy Setup to perform unsetup.

For details about how to perform unsetup of HCSC servers, see 3.3.5 Unsetting up an HCSC server.

If you have updated a version earlier than 07-50 to 09-50 without performing unsetup, you must delete the HCSC servers manually. You do not need to manually delete the HCSC servers if the update is from 07-50 or later to 09-50.

Uninstall the old version of Service Platform in the development, operating, and execution environments. We recommend that you back up the Service Platform installation directory before uninstalling Service Platform.

(a) Notes on uninstallation

• Before you start uninstallation, terminate all components, such as the J2EE server, Management Server, and PRF, in the execution environment.
• If an embedded database is used, terminate it before you start uninstallation.

(b) Notes applying to an update from a version earlier than 07-50

• Finish unsetup of all HCSC servers before updating the version.
• Before you update the version of the execution environment, use the cscrepls command to confirm that no HCSC server information remains. If HCSC server information remains, perform unsetup of those HCSC servers, and then update the version. If you attempt to update the version when HCSC server information remains, the update will not be performed correctly.
• After performing unsetup of HCSC servers, delete the repository root, including the contents.

(c) Notes applying to an update from a version earlier than 09-00

The products listed below come with Service Platform 09-00 or later. If any of the products listed below 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

(d) Note on updating the development environment

In the development environment, delete the HCSCTE project before updating the version, and then re-create the project after updating the version.

Install Service Platform 09-51 to update the version in the development, operating, and execution environments.

Set up and define the same environment as the previously created HCSC server, based on the following files that were created previously:

• HCSC server configuration definition file
• HCSC server setup definition file
• HCSC server runtime definition file
• User-defined reception runtime definition file

In a test environment, use HCSC Easy Setup to set up an HCSC server.

In (1) Export the repository (operating environment) above, you exported the repository. Here, import the exported repository in the development environment. Before you import the repository, make sure that Build Automatically (in the Project menu) is disabled in Eclipse. After the repository has been imported, enable Build Automatically again.

When you import the repository that was used in the old version, packaging and deployment definition are automatically performed, and the new version inherits the repository information. Note that packaging and deployment definition are automatically performed for only the service adapters, business processes, and user-defined receptions for which packaging and deployment definition were performed in the old version.

(a) Note applying to update from a version earlier than 07-50

If the following file names are set in a user-defined class of the SessionBean adapter, a warning message appears:

• csmsvcadpdef.jar
• cscmsg_adpejb.jar

If a warning message appears, in the Service Adapter Settings window, delete that user-defined class, change the file names, and then set the new file names again.

(b) Note applying to update from version 07-60 or later

If the version that you want to update is 07-60 or later, the service adapters and user-defined receptions to be deployed in the execution environment must be imported to the development environment and packaged again. If you do not repackage service adapters, the KDEC03007-E message might not be output. If you do not repackage user-defined receptions, incorrect characters might be output to the KDEC00001-E message. For details about how to perform packaging, see 7.2 Packaging in the uCosminexus BPM/ESB Service Platform Basic Development Guide.

(c) Note applying to update from a version earlier than 08-10

If the elements (compositors) listed below are defined under the sequence or choice element in the data transformation definition and the number of occurrences is fixed to 1 for those elements, the node display is changed. As a result, an error message appears, indicating that the XML schema used in the mapping definition file has been changed.

• sequence
• choice

If this error message appears, restart mapping definition, and then apply the change.

(d) Notes applying to update from a version earlier than 09-50

• If the data transformation definition includes the schema definitions shown below, the namespace is changed. As a result, an error message appears, indicating that the XML schema used in the mapping definition file has been changed.
  
  1. The schema that defines the target namespace (targetNamespace) at the import destination is specified on the transformation source node.
  2. The namespace in 1 is not defined in all namespace declarations (xmlns[:prefix]) including the import or include destination.
  If this error message appears, restart mapping definition, and then apply the change.
  
• Because the default values are used for the minimum and maximum numbers of pooled instances, if the xml-pooled-instance-minimum or xml-pooled-instance-maximum property is specified in the HCSC server runtime definition file, the specification of these properties might affect performance. To prevent performance from being affected, make sure that the same values are specified for these properties and the corresponding properties in the usrconf.properties file (user property file for the J2EE server), as shown below.
  

  Item	Properties in the HCSC server runtime definition file#1	Properties in the usrconf.properties file (user property file for the J2EE server)#2
  Min.	xml-pooled-instance-minimum	csc.dt.pool.DocumentBuilder.initialSize
  Max.	xml-pooled-instance-maximum	csc.dt.pool.DocumentBuilder.maxSize

  #1

  For details about the HCSC server runtime definition file, see HCSC server runtime definition file in the uCosminexus Service Platform Reference Guide.

  #2

  For details about how to specify these properties, see 2.3.10 Using XML parser pool functionality option.

  
  

(e) Note on memory

Import of the repository used in the old version requires a lot of memory. Therefore, use the procedure below to check whether the amount of installed memory is sufficient. If the amount of installed memory is insufficient, increase memory, and then import the repository.

1. From the Eclipse menu, select Window, and then Preferences.
2. In the tree view at the left of the dialog box that opens, select General.
3. Select the Show heap status check box at the right of the dialog box.
4. Select the trash can icon in the bottom right of the Eclipse window to run the garbage collector.
5. Check the heap size displayed to the left of the trash can icon.
6. If unused heap space is insufficient, edit the eclipse.ini file to increase the memory size (the value of -Xmx). For details about how to edit the eclipse.ini file, see 2.4.3 Setting up the Eclipse environment in the uCosminexus Application Server Application Development Guide.

(f) Notes on the client definition file

If the SOAP adapter is defined in the development environment, the value of the c4web.logger.log_file_prefix property in the client definition file (c4webcl.properties) is automatically changed to the service ID. Delete the old client definition file if it is unnecessary. For details, see 3.3.1 Defining SOAP adapters in the uCosminexus BPM/ESB Service Platform Reception and Adapter Definition Guide.

Export the repository that was imported in (7) Import the repository (development environment).

Import the repository that was exported in (8) Export the repository (development environment). Note that you cannot import the repository that was used in the old version.

Execute the cscrepctl command (with the -import option) in the operating environment.

For details about how to import the repository, see 4.3 Importing a repository.

After you have imported the repository information in (9) Import the repository (operating environment), deploy the HCSC components included in the repository information on the HCSC server. Make sure that the resulting environment is the same as the environment existing when the repository was exported in (1) Export the repository (operating environment).

Execute the csccompodeploy command (with the -all option) in the operating environment.

For details about how to deploy HCSC components, see 3.1.8 Deploying a service adapter and 3.1.13 Deploying a business process.

After you have deployed the HCSC components, you can perform operations on them as you could before the version was updated.

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 A.3 Migrating procedure when a repository is shared between development environment and operating environment in earlier version< in the uCosminexus BPM/ESB Service Platform Basic Development Guide.