uCosminexus Service Platform, Basic Development Guide

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

2.3 Development Work Flow

The following figure shows the workflow for using a Cosminexus Service Platform to develop a system.

Figure 2-1 System development work flow

[Figure]

Note #1
For HCSC easy setup, see "1.3 Relationship between Test Environment and Production Environment" in "Service Platform System Setup and Operation Guide". For exporting the repository, see "4.2 Exporting Repository Information" in "Service Platform System Setup and Operation Guide".

Note #2
Create the test environment, using HCSC easy setup. For HCSC easy setup, see " 2.4 Easy Setup of the Test Environment". If you do not use the HCSC easy setup function, see the "Service Platform System Setup and Operation Guide" to operate and create the execution environment.

Note #3
For the definition of service adapter and user-defined reception, see "2. Defining user-defined reception" and "3. Defining Adapters" in "Service Platform Reception and Adapter Definition Guide".

Note#4
You can execute above-mentioned work in a batch. However, batch execution is possible at the time of system development or in the period from unit test through combined test. Deployment and start of HCSC components implemented in operating environment is executed along with the above-mentioned batch execution. For details, see "7.5 Batch execution of processes for deploying HCSC components on the HCSC Server and then starting".

Work to be performed in each process is as follows:

Organization of this section
(1) Importing the repository (acquiring system configuration definition)
(2) Creating message format
(3) Defining a service adapter
(4) Defining a business process
(5) Creating data transformation definition
(6) Defining the user-defined reception
(7) Exporting a repository (integrating to master development environment)
(8) Importing a repository (integrating to master development environment)
(9) Assembling (packaging) HCSC components
(10) Deployment definition
(11) Exporting repository (data migration to operating environment)
(12) Creating a service requester
(13) Debugging business processes

(1) Importing the repository (acquiring system configuration definition)

Import only the system configuration definition, to integrate the information of HCSC server created in operating environment, with the master development environment. For details on importing the repository, see "3.2.3 Importing a Repository".

(2) Creating message format

Define a format of messages (message format) exchanged between the service adapter and service components. Created message format differs depending on whether XML format data or binary format (other than XML format) data is to be handled in message used for executing service component. For details on creating message format, see "4. Creating Message Formats".

(3) Defining a service adapter

When you develop a system using a service adapter, add the service adapter by using a wizard for adding a service adapter as well as already defined service adapter. Define the added service adapter, by using the Define service adapter screen. For details on defining a service adapter, see "3. Defining Adapters" in "Service Platform Reception and Adapter Definition Guide".

(4) Defining a business process

When you develop a system by using a business process, add the business process by using the wizard for adding a business process or already defined business process. Define the added business process, by using the Define business process screen. For details on defining a business process, see "5.Defining Business Processes".

Also, when you receive a business process execution request, with non-standard reception, you must define the user-defined reception. For details on defining a user-defined reception, see "2. Defining User-Defined Reception" in "Service Platform Reception and Adapter Definition Guide".

(5) Creating data transformation definition

Define the data transformation, when data transformation is required in message exchange with service component. For details on the data transformation definition, see "6. Defining Data Transformation".

(6) Defining the user-defined reception

Define the user-defined reception, to receive service component execution requests and define any format as the interface that returns the response. For details on defining the user-defined reception, see "2. Defining User-Defined Reception" in "Service Platform Reception and Adapter Definition Guide".

(7) Exporting a repository (integrating to master development environment)

When you develop HCSC components in multiple development environments (distributed development), export the repository in which HCSC components developed in environment other than master development environment are included.

For exporting the repository, see " 3.2.2 Exporting a Repository".

(8) Importing a repository (integrating to master development environment)

To integrate the information of HCSC component for which distributed development in performed on machines other than master development environment, to the master development environment, import a part of repository exported in " (7) Exporting a repository (integrating to master development environment)" to the master development environment. For importing a repository, see " 3.2.3 Importing a Repository".

(9) Assembling (packaging) HCSC components

Consolidate the definition files related to definition of HCSC components defined from "(3) Defining a service adapter"(6) Defining the user-defined reception" as well as the files provided by execution environment, and perform packaging in EAR file. For details on packaging, see "7. Packaging HCSC Components and Defining Deployment".

(10) Deployment definition

Define the information of cluster (or unit HCSC server) that deploys HCSC components. For details on deployment definition, see "7. Packaging HCSC Components and Defining Deployment".

Reference note
Before deploying the procedure to check Usage existence of database and Reliable Messaging, set in the cluster (or unit HCSC server) to be deployed, is as follows:
  1. From menu of Eclipse, select [HCSC-Definer]-[System configuration definitions list].
    List of clusters to be deployed (or unit HCSC servers) is displayed in the system configuration definitions list of the Tree view.
  2. From the list of clusters (or unit HCSC servers) to be deployed, select the cluster (or unit HCSC server) to be checked and double click the same.
    Information about usage existence of database and Reliable Messaging set in the cluster (or unit HCSC server) to be deployed is displayed.

(11) Exporting repository (data migration to operating environment)

Export the repository that stores the definition file required for deploying HCSC components, in master development environment. Information exported from the master development environment is imported to operating environment. For exporting repository, see "3.2.2 Exporting a Repository".

(12) Creating a service requester

Create a service requester for sending the message that requests HCSC components to execute service components. You can create a service requester and define a service adapter or a business process at the same time. When you want to create concurrently, check the interface information to be set in the definition of service adapter or business process beforehand and set up the same information in service requester as well. For details on how to create HCSC components, see "8. Creating Service Requesters".

(13) Debugging business processes

Test and debug the defined business processes in development environment, before using them in operating environment. For details on debugging business processes, see "9. Debugging Business Processes".