uCosminexus Service Platform, Basic Development Guide
Usage existence of database and Reliable Messaging differ depending the functions of service platform to be used and operations to be performed. Following table shows the usage of database and Reliable Messaging for each function to be used.
Table 2-1 Usage of database and Reliable Messaging for each function to be used
Function to be used | Database | Reliable Messaging | |
---|---|---|---|
Following synchronous reception is to be used
|
N | N | |
Following asynchronous reception is to be used
|
N | N | |
Following synchronous service adapters are to be used
|
N | N | |
Following asynchronous service adapters are to be used
|
Y | Y | |
DB adapter is to be used | N# | N | |
Business process is to be used | Persistence business process is to be used | Y | N |
Non-persistence business process is to be used | N | N | |
Process instance execution history is to be managed | Y | N |
When you use non-persistence business process, take note that the processes that you can define in the development environment have a limitation. For details, see "5.2.1(3) Setting up status persistence".
From above mention table, one can understand that the configuration status depending on the usage existence of database and Reliable Messaging has following 3 patterns:
Settings contents of test environment differ depending on the pattern by which the concerned environment is set up. For the details on usage existence of database and Reliable Messaging to be set up in test environment and the concerned environment, see "1.3 Relationship between Test Environment and Production Environment" in "Service Platform System Setup and Operation Guide". Also, for setting contents in test environment, see "2.4 Easy Setup of the Test Environment".
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.