G.2 Migration procedure for a new installation

(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.

(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 definition 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 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 6.5.6 HCSC server runtime definition file in the uCosminexus Service Platform Reference Guide.

  #2

  For details about how to specify these properties, see 2.3.9(5) Using XML parser pool functionality option.

(e) Note applying to migration from a version earlier than 09-70

If the following schema is included in the data transformation definition, the namespace will be changed. Therefore, an error message stating that the XML Schema used in the mapping definition file has been changed will be displayed.

• A namespace URI for which multiple different namespace prefixes are specified

If this error message is displayed, restart the mapping definition editor to apply the change.

(f) 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.

(g) 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 Service Platform Reception and Adapter Definition Guide.