uCosminexus Service Platform, Setup and Operation Guide
Existence of usage of the database and Reliable Messaging differs according to the functionality of Service Platform to be used and the kind of operation required. The following table describes the existence of usage of Reliable Messaging and database as per each functionality:
Table 2-2 TableDatabase of each functionality to be used and existence of usage of Reliable Messaging
| Functionality to be used | Database | Reliable Messaging | |
|---|---|---|---|
| Synchronous reception is to be used | N | N | |
| Asynchronous reception (standard reception (MDB(WS-R)), standard reception (MDB(DB queue))) are to be used | N | N | |
| Synchronous service adapter is to be used | N | N | |
| Asynchronous service adapter (MDB(WS-R) adapter, MDB(DB queue) adapter) are to be used | Y | Y | |
| Business process is to be used | Persistent business process is to be used | Y | N |
| Non-persistent business process is to be used#1 | N | N | |
| Process instance execution history is to be managed | Y | N | |
| DB adapter is to be used | N#2 | N | |
From the above table it is understood that the configuration format according to existence of usage of the database and Reliable Messaging contains the following 3 patterns:
Contents of settings related to the execution environment are different during system setup according to each pattern. For details on execution environment setting contents in each pattern, see "2.3 Settings related to execution environment".
Setting of existence of usage of the database and Reliable Messaging is defined in HCSC server setup definition file. Database settings are not required if the database is not used and Reliable Messaging setting is not required if Reliable Messaging is not used.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.