uCosminexus Application Server Overview
The service platform is composed of the following three environments:
- Development environment
This is the environment for creating the HCSC components (a general name for the service adapters, business processes, and user-defined receptions created in the development environment) required to integrate the services, and for packaging them in EAR files.
- Execution environment
This is the environment for invoking service components and business processes corresponding to a request, and then executing the business.
- Operating environment
This is the environment for deploying the HCSC components created in the development environment in the execution environment, and thereafter executing the operating environment. Furthermore, in this environment you can collect information from the execution environment, and confirm the status of service components.
(2) Relationship between the development environment, execution environment, and operating environment
Set up the development environment, execution environment, and operating environment respectively on different computers.
Install Service Architect and Eclipse in the development environment. Install Service Platform in the execution environment, and install Eclipse if the OS is Windows.
To run the execution environment from the operating environment, you must use the data model called a repository.
The following figure shows the environments that compose the service platform.
Figure 10-5 Environments composing the service platform
These environments are mutually linked to implement an integrated environment of services. After you set up the environment and follow the steps mentioned below, each environment can actually execute operations:
- Create HCSC components in the development environment.
- In the operating environment, set up HCSC servers and define the system configuration.
- Export the repository from the operating environment, and import the system configuration definition, defined in the operating environment, to the development environment.
- Based on the system configuration definition defined in the operating environment, define the part of the system configuration in which components are deployed, and then update (deployment definition).
- Export the repository having the deployment definition defined in the development environment, to the operating environment.
- Based on the deployment definition defined in the development environment, deploy components in the execution environment from the operating environment.
To transfer the information between environments, use the repository that stores the information shared between environments. The repository is saved and read in a ZIP file format via a medium.
In the development environment, the information of the HCSC components created on multiple computers can be collected as one through a repository. Moreover, you can set up a test environment for executing testing and debugging of the created HCSC components on the same computer on which you have set up the development environment. The test environment is a simple environment that is required for testing and can be set up at the same time. The following figure shows the relationship between the development environment and test environment.
Figure 10-6 Relationship between the development environment and test environment
For executing operations in the development and test environments, use the following procedure:
- Create HCSC components in the development environment.
- Set up the test environment (you can use the HCSC Simple Setup functionality to set up an HCSC server, and define the system configuration). When setting up the test environment also, it is assumed that the execution environment is the actual environment.
- Export repository from the test environment, and import the system configuration definition defined in the test environment, to the development environment.
- Based on the system configuration definition defined in the test environment, define the part of the system configuration in which components are deployed, and then update (deployment definition).
- Export the repository having the deployment definition defined in the development environment, and then import to the test environment.
- Based on the deployment definition defined in the development environment, deploy components in the test environment.
Also the repository is used for transferring information between such environments. Since the development environment and test environment are set up on the same computer, information is transferred without the use of a medium.
With the Service Platform, you first build a test environment and then perform testing and debugging. You can use the HCSC Easy Setup functionality to build the test environment.
In actual system development, you need to configure the production environment in addition to the test environment. Therefore, you are required to move the repository used in the test environment to the production environment.
In the following test environments and production environments, if the settings for whether to use the database and Reliable Messaging are the same, you can move the repository used in the test environment to the production environment as it is:
- When both the database and Reliable Messaging are used in the test environment and production environment
- When both the database and Reliable Messaging are not used in the test environment and production environment
- When the database is used but Reliable Messaging is not used in the test environment and production environment
Note that in the test environment and in the production environment, you can move the repository even if the settings for whether to use the database and Reliable Messaging are not the same. For details, see the manual Service Platform System Setup and Operation Guide.
The following figure shows how to move a repository when the settings for whether to use the database and Reliable Messaging are the same in the test environment and the production environment:
Figure 10-7 Procedure for moving a repository when the settings for whether to use the database and Reliable Messaging are the same
- In the test environment, set up HCSC servers and define the system configuration.
You can use HCSC Easy Setup definitions to define the setup of HCSC server and the configuration of systems. However, when configuring a system using a database and not using Reliable Messaging, you cannot use the HCSC Easy Setup functionality.
- Export the repository from the operating environment, and import the system configuration definition that is defined in the test environment to the development environment.
- Create HCSC components in the development environment.
- Based on the system configuration definition defined in the test environment, define the part of the system configuration in which components are deployed, and then update (deployment definition).
- Export the repository having the deployment definition that is defined in the development definition, and import the repository to the operating environment.
- On the basis of the deployment definition that is defined in the development environment, deploy HCSC components on the test environment.
- In the production environment, set up HCSC servers and define the system configuration.
In the test environment and the production environment, specify the same settings for whether to use the database and Reliable Messaging.
- Export the repository included in the deployment definition that is defined in the development environment, and then import to the operating environment.
When you use standard import, you can move the repository of the test environment to the production environment, even if the HCSC server name or IP addresses are different.
- On the basis of the deployment definition that is defined in the development environment, deploy HCSC components on the production environment.
All Rights Reserved. Copyright (C) 2013, 2015, Hitachi, Ltd.