uCosminexus Service Platform, Basic Development Guide

[Contents][Glossary][Index][Back][Next]

Appendix A.3 Migrating procedure when a repository is shared between development environment and operating environment in earlier version

In 07-60 and higher versions, you cannot share the same repository between a development environment and an operating environment. If the same repository is shared between a development environment and an operating environment, migrate the Cosminexus Service Platform from the earlier version to the version 09-60 according to steps (1) to (6) shown in the following figure:

Figure A-2 Procedure for migrating from an earlier version (When the repository is shared between the development environment and operating environment)

[Figure]

The details of steps (1) to (6) of Figure A-2 are described below.

Organization of this subsection
(1) Repository export (operating environment)
(2) Deleting the HCSCTE project (Development environment)
(3) Uninstalling the environment
(4) Installing each environment
(5) Creating an HCSCTE project (development environment)
(6) Importing the repository (Development environment)

(1) Repository export (operating environment)

Execute the cscrepctl command (the -export option) in the operating environment and export the repository prior to the version upgrade. If multiple repositories are being used, export all the required repositories and save them.

(2) Deleting the HCSCTE project (Development environment)

Delete the HCSCTE project once.

For details about the procedure, see 3.1.4 Deleting a Project.

(3) Uninstalling the environment

Uninstall the Cosminexus Service Platform of the earlier version in the development environment and the operating environment. Hitachi recommends that you save the directory information under Cosminexus, and then uninstall the Cosminexus Service Platform of the earlier version.

#
  • Uninstall components of the execution environment, such as the J2EE server, the Management Server, and PRF after stopping them.
  • If you are using an embedded database, stop the embedded database before uninstalling.
  • After unsetting up the HCSC server, delete all the entries under the repository root.

(4) Installing each environment

In the development environment and the operating environment, install the Cosminexus Service Platform of version 09-60 to upgrade the version.

(5) Creating an HCSCTE project (development environment)

Create a new HCSCTE project in the upgraded development environment. Specify the directory to be used as a repository. Do not specify the repository of the operating environment in the directory to be used as repository.

For details about the procedure, see 3.1.1 Creating a Project.

(6) Importing the repository (Development environment)

Import the repository information that was exported in Appendix A.3(1) Repository export (operating environment) to the development environment. When importing, in the Eclipse menu, turn OFF Project - Build automatically, and then import the repository. After you have imported the repository, turn it back to ON.

When you import the repository of an earlier version, packaging and deployment definition are executed automatically, and the repository information is inherited into the current version. Note that automatic execution of packaging and deployment definition is performed only for the HCSC components for which packaging and deployment definition were executed in the earlier version.

For details about how to import a repository, see 3.2.3 Importing a Repository.

#
Notes when migrating from a version earlier than 07-50
If the following file names are set up in the user-defined class of the service adapter (SessionBean), a warning message will appear.
  • csmsvcadpdef.jar
  • cscmsg_adpejb.jar
When the warning message appears, delete the above user-defined class in the Service Adapter Definition screen, change the file name, and then set up the name again.
Notes when migrating from versions prior to 08-10
If the following elements (compositor) with the occurrence count fixed at "once" are defined below the sequence or choice elements in the data transformation definition, the node display is changed; therefore, an error message is displayed indicating that the XML Schema used in the mapping definition file is changed:
  • sequence
  • choice
If the error message is displayed, start the mapping definition again to apply the changes.
Notes on migrating from a version earlier than 09-50
If a schema that meets the following conditions is defined in the data transformation definition, the namespace is changed. Therefore, an error message is displayed indicating that the XML Schema used in the mapping definition file has changed.
  1. A schema that has its target namespace (targetNamespace) defined at the import destination is specified for the transformation source node.
  2. The namespace in 1 above is not defined in any namespace declarations (xmlns[:prefix]) including import and include destinations.
If an error message is displayed, start the mapping definition again to apply the changes.
Notes regarding the memory
When importing an earlier-version repository, you need a large amount of memory. Therefore, use the procedure below to check whether the memory size is sufficient. If the memory is insufficient, increase the memory size before importing the repository.
  1. From the Eclipse menu, select Window and then Preferences.
  2. Select General in the tree view on the left side of the dialog box.
  3. Select the Show heap status check box on the right side of the dialog box.
  4. Select the recycle bin icon on the bottom right of the Eclipse window, and then run the garbage collector.
  5. Check the heap size shown to the left of the recycle bin icon.
  6. If the amount of unused heap memory is insufficient, edit the eclipse.ini file to increase the memory size specified in -Xmx. For details about how to edit eclipse.ini, see Appendixes B.1 Installation in the Application Server Application Development Guide.

To perform actual operations by using the repository information imported into the development environment, export this repository information from the development environment to the operating environment, and then deploy the HCSC components from the operating environment.