6.4.3 HCSC server setup definition file

(a) Associated with setup configuration

db-use={ON|OFF} ~ <<ON>>

Specifies whether a database will be used with the HCSC server.

• ON

  A database will be used.

• OFF

  A database will not be used.

rm-use={ON|OFF} ~ <<ON>>

Specifies whether Reliable Messaging will be used with the HCSC server. An error occurs if OFF is specified for the db-use property, and you specify ON for this property.

• ON

  Reliable Messaging will be used.

• OFF

  Reliable Messaging will not be used.

hcscserver-data-filepath=output-destination-path-storing-System-Administrator-information-for-HCSC-server ~ <String of maximum 100 bytes> <<service-platform-installation-directory\CSC\spool\msg>>

Specifies an absolute path for the output destination to store the System Administrator information for the HCSC server. Use the characters / or \\ as directory delimiters. An error occurs if you specify a non-existent directory, and if the specified string exceeds 100 bytes. Therefore, explicitly specify this property when service-platform-installation-directory exceeds 84 bytes. Note that the byte length that can be specified is the length obtained after decoding the string with ISO-8859-1.

(b) Associated with standard receptions

request-ejb={ON|OFF}

Specifies whether a standard synchronous reception (SessionBean) will be used.

• ON

  A standard synchronous reception (SessionBean) will be used.

• OFF

  A standard synchronous reception (SessionBean) will not be used.

Specify ON in the following cases:

• To invoke service components from a service requester by using a SessionBean

• To re-execute process instances on the operating environment window

• To re-execute process instances by using the cscpireexec command

request-soap={ON|OFF}

Specifies whether a standard synchronous reception (Web Service) will be used.

• ON

  A standard synchronous reception (Web Service) will be used.

• OFF

  A standard synchronous reception (Web Service) will not be used.

Specify ON to invoke service components from a service requester by using Web Service.

request-jms={ON|OFF}

Specifies whether a standard asynchronous reception (MDB(WS-R)) will be used. An error occurs if OFF is specified for the rm-use property and you specify ON for this property.

• ON

  A standard asynchronous reception (MDB(WS-R)) will be used.

• OFF

  A standard asynchronous reception (MDB(WS-R)) will not be used.

Specify ON in the following cases:

• To invoke service components from a service requester by using MDB(WS-R)

• After executing reply activities with the deployed business processes, when a business process is defined for executing basic activities (receive , invoke service, invoke Java, data transformation, assign, empty, throw, and standby)

request-jms.maxmessage=maximum-number-of-messages-in-standard-asynchronous-reception-(MDB(WS-R))-queue ~ <Numeric character> ((1 to 65535)) <<1024>>

Specifies the maximum number of messages set when the reception queue is created for a standard asynchronous reception (MDB(WS-R)). This value depends on the value set in Reliable Messaging. This property is valid only when you specify ON in the request-jms property.

request-dbq={ON|OFF}

Specifies whether a standard asynchronous reception (MDB(DBQueue)) will be used. An error occurs if OFF is specified for the rm-use property, and you specify ON for this property.

• ON

  A standard asynchronous reception (MDB(DBQueue)) will be used.

  Note that you cannot specify ON in Oracle.

• OFF

  A standard asynchronous reception (MDB(DBQueue)) will not be used.

Specify ON to invoke service components from a service requester by using (MDB(DBQueue)).

request-dbq.maxmessage=maximum-number-of-messages-in-standard-asynchronous-reception-(MDB (DB queue))-queue ~ <Numeric character> ((1 to 65535)) <<1024>>

Specifies the maximum number of messages set when the reception queue is created for a standard asynchronous reception (MDB(DBQueue)). This value depends on the value set in Reliable Messaging. This property is valid only when you specify ON in the request-dbq property.

request-jms-rdarea=RD-area-name-of-standard-asynchronous-reception (MDB(WS-R)) ~ <Alphanumeric characters beginning with alphabetic characters, spaces, and underscores (_)> ((1 to 30 characters))

Specifies the RD area name of a standard asynchronous reception (MDB(WS-R)). This property is invalid when Oracle is used as the database. Because this value depends on the value specified for Reliable Messaging, you can specify this property only when using Reliable Messaging.

request-dbq-rdarea=RD-area-name-of-standard-asynchronous-reception (MDB(DBQueue)) ~ <Alphanumeric characters beginning with alphabetic characters, spaces, and underscores (_)> ((1 to 30 characters))

Specifies the RD area name of a standard asynchronous reception (MDB(DBQueue)). This property is invalid when Oracle is used as the database. Because this value depends on the value specified for Reliable Messaging, you can specify this property only when using Reliable Messaging.

request-dbq-maxlen=maximum-length-of-messages-in-standard-asynchronous-reception-(MDB(DBQueue)) ~ <Numeric character> ((1000 to 1048576)) <<33000>>

Specifies the maximum length of messages in a standard asynchronous reception (MDB(DBQueue)) in bytes. This value depends on the value set in Reliable Messaging.

(c) Associated with user-defined receptions

request-userdef-soap={ON|OFF} ~ <<OFF>>

Specifies whether a SOAP reception will be used.

• ON

  A SOAP reception will be used.

• OFF

  A SOAP reception will not be used.

  Important note

  You can deploy or execute user-defined receptions even if OFF is specified. However, note that when OFF is specified and user-defined receptions are defined in the development environment, the address of the request destination Web Service from the service requester is not displayed.

(d) Associated with J2EE

naming-service-hostname=host-name-of-Naming-Service ~ <Character string>

Specifies the host name for Naming Service. The host name depends on the name specified in the service platform. If you omit this property, the host name that has been set for Management Server is specified.

naming-service-port=port-number-of-Naming-Service ~ <Numeric character> ((1 to 65535))

Specifies the port number for the naming service. The port number depends on the value set in the service platform. If you omit this property, the port number for the in-process naming service of the logical J2EE server managed by Management Server is specified.

(e) Associated with Reliable Messaging

rm-systemname=system-name-of-Reliable-Messaging ~ <Uppercase alphabetic characters or numbers beginning with alphabetic characters> ((1 to 3 characters))

Specifies the RM system name of Reliable Messaging used by the HCSC server. You can specify this property only when using Reliable Messaging.

The system name depends on the name specified in the service platform. Make sure that you specify this property when ON is specified for the rm-use property. An error occurs if you specify this property when OFF is specified for the rm-use property.

rm-displayname=display-name-of-Reliable-Messaging ~ <Alphanumeric characters and underscores (_)>

Specifies the value obtained by sanitizing (changing characters other than one-byte alphanumeric characters to underscores (_)) the display name of Reliable Messaging (resource adapter) used by the HCSC server. You can specify this property only when using Reliable Messaging.

The display name depends on the name specified in the service platform. Make sure that you specify this property when ON is specified for the rm-use property. An error occurs if you specify this property when OFF is specified for the rm-use property.

(f) Associated with DB Connector

dbcon-xadisplayname=display-name-of-DB-Connector-for-XATransaction-or-LocalTransaction ~ <Alphanumeric characters and underscores (_)>

Specifies the value obtained by sanitizing (changing characters other than one-byte alphanumeric characters to underscores (_)) the display name of DB Connectors for XATransaction or LocalTransaction, which is used by the HCSC server. The display name depends on the name specified in the service platform. Make sure that you specify this property when ON is specified for the db-use property. An error occurs if you specify this property when OFF is specified for the db-use property.

dbcon-nodisplayname=display-name-of-DB-Connector-for-NoTransaction

Specifies the value obtained by sanitizing (changing characters other than one-byte alphanumeric characters to underscores (_)) the display name of DB Connector for NoTransaction, which is used by the HCSC server. The display name depends on the name specified in the service platform. Make sure that you specify this property when ON is specified for the db-use property. An error occurs if you specify this property when OFF is specified for the db-use property.

(g) Associated with databases

dbtype={HIRDB|ORACLE11G}

Specifies the type of the database to be used by the HCSC server. Make sure that you specify this property when ON is specified for the db-use property. An error occurs if you specify this property when OFF is specified for the db-use property.

• HIRDB

  HiRDB will be used as the database.

• ORACLE11G

  Oracle will be used as the database.

jdbc-type={DBPSV|HIRDB-TYPE4|ORACLE-THIN}

Specifies the type of the JDBC driver to be used when the HCSC server is offline. Make sure that you specify this property when ON is specified for the db-use property. An error occurs if you specify this property when OFF is specified for the db-use property.

• DBPSV

  JdbcDbpsvDriver of DABroker Library will be used. Make sure that you specify the properties jdbc-dbhostname and jdbc-dbconnectinfo when DBPSV is specified. You cannot access Oracle databases by using DABroker Library.

• HIRDB-TYPE4

  HiRDB Type4 JDBC Driver will be used. When HIRDB-TYPE4 is specified, make sure that you specify the properties jdbc-dbhostname and jdbc-dbconnectinfo.

• ORACLE-THIN

  Oracle JDBC Thin Driver will be used. Make sure that you specify this value in the dbtype property when ORACLE11G is specified as the database type to be used. Also, make sure that you specify the jdbc-url property when ORACLE-THIN is specified.

jdbc-url=database-URL-for-JDBC ~ <Character string>

Specifies the destination database URL specified for establishing a connection with the Driver.connect method, as the connection settings supporting each JDBC driver to be used when the HCSC server is offline. Make sure that you specify this property when ORACLE-THIN is specified as the JDBC driver type in the jdbc-type property.

• When DBPSV is specified in the jdbc-type property

  The specification of the jdbc-url property is disabled.

• When HIRDB-TYPE4 is specified in the jdbc-type property

  The specification of the jdbc-url property is disabled.

• When ORACLE-THIN is specified in the jdbc-type property

  Specifies the URL to be used for connecting Oracle JDBC Thin Driver to the database. Specifies the string after jdbc:oracle:thin:@. For details on the URL format, see the Oracle documentation. Do not specify a URL containing the user name and the password to be used for connecting to the database. Specify the user name and the password to be used for connecting to the database in the HCSC server configuration definition file.

jdbc-dbhostname=host-name-of-a- database ~ <Character string> ((maximum 2086 characters))

Specifies the host name or the IP address of HiRDB to be used by the HCSC server when the HCSC server is offline. Make sure that you specify this property when DBPSV and HIRDB-TYPE4 are specified as the JDBC driver types in the jdbc-type property. When ORACLE-THIN is specified in the jdbc-type property, the specification of the jdbc-dbhostname property is disabled.

jdbc-dbconnectinfo=database-connection-information ~ <Alphanumeric characters>

Specifies the connection information (the port number or the name of the environment variable group) to be used when the HCSC server is offline. Use the characters / or \\ as directory delimiters. This value depends on the value set in DABroker or HiRDB. Make sure that you specify this property when DBPSV and HIRDB-TYPE4 are specified as the JDBC driver types in the jdbc-type property.

• When DBPSV is specified in the jdbc-type property

  Specifies the port number of the HiRDB system, or the name of the environment variable group of the HiRDB client. When you specify the name of the environment variable group, make sure that you include @DABENVGRP at the beginning.

• When HIRDB-TYPE4 is specified in the jdbc-type property

  Specifies the port number of the HiRDB system, or the file name of the environment variable group of the HiRDB client. When you specify the file name of the environment variable group, make sure that you specify @HIRDBENVGRP= at the beginning followed by the file name of the environment variable group as an absolute path.

• When ORACLE-THIN is specified in the jdbc-type property

  The specification of the jdbc-dbconnectinfo property is disabled.

db-character-sets={ASCII|Shift_JIS|UTF-8|EUC-JP}

Specifies the type of the character encoding specified in the database to be used.

This property is used to convert the length (number of bytes of a string that can be entered in the database) of NCName of XML schema definition to the specified character encoding and perform a check during the input check for a command reception (MBean) and standard reception.

Make sure that you specify this property when ON is specified in the db-use property. You can omit this property if no database is to be used. If you do not specify this property when OFF is specified for the db-use property, check by converting the characters to UTF-8. If a type other than UTF-8 is specified, check with the specified character encoding.

• ASCII

  Specify ASCII when the character encoding type specified in the database to be used is ASCII.

• Shift_JIS

  Specify Shift_JIS when the character encoding type specified in the database to be used is Shift_JIS.

• UTF-8

  Specify UTF-8 when the character encoding type specified in the database to be used is UTF-8.

• EUC-JP

  Specify EUC-JP when the character encoding type specified in the database to be used is EUC-JP.

db-tbl-split-key={NONE|MONTH} ~ <<NONE>>

Specifies whether the range segmentation function of tables will be used based on the date data.

• NONE

  The range segmentation function will not be used.

• MONTH

  The range segmentation function will be used. The month (GMT) in which process instances started is used as the split key and registered to the table.

Define the segmentation method used for the range segmentation function of tables in the SQL script file specified in the sql-scriptfilename property. For details on the configuration of tables, see Appendix C. Database Table Information in the uCosminexus Service Platform Setup and Operation Guide.

db-tbl-split-corcheck-use={ON|OFF} ~ <<OFF>>

Specifies whether the check for duplicates in correlation sets, will be strengthened. Specify ON when using the segmentation functions of the execution log information table in HiRDB.

• ON

  The check for duplicates in correlation sets is strengthened.

• OFF

  The check for duplicates in correlation sets is not strengthened.

To use the table segmentation function, define the segmentation method in the SQL script file specified in sql-scriptfilename. For details on the configuration of tables, see Appendix C. Database Table Information in the Service Platform Setup and Operation Guide.

(h) Compatibility of business process statuses

bp-status-compatible={ON|OFF}

Specifies the following information. This property is valid when you use persistent business processes.

• Whether to set the process instance and the activity to the Error status when an exception (error) occurs while the invoke service activity of a business process is running

• Whether to end or to start a transaction for operations other than the execution of the invoke service activity with a synchronous communication model

The transaction and the status transition of the invoke service activity differ depending on the combination of the properties bp-status-compatible and bp-invoke-status-compatible. For details, see 3.4.4 Transactions of the invoke service activity in the manual Service Platform Overview

The default value for a new installation of 08-10 or later is OFF. Also, the default value is ON when migrated from the version 08-00 or earlier.

(i) Compatibility of invoke service activity statuses

bp-invoke-status-compatible={ON|OFF}

Specifies whether to end or to start a transaction when the execution of the invoke service activity of a business process is successfully completed.

This property is valid when you specify OFF in the bp-status-compatible property. Also, this property is valid when you use persistent business processes.

The transaction and the status transition of the invoke service activity differ depending on the combination of the properties bp-status-compatible and bp-invoke-status-compatible. For details, see 3.4.4 Transactions of the invoke service activity in the manual Service Platform Overview.

The default value for a new installation is OFF. Also, the default value is ON when migrated from the version 08-70 or earlier.

(j) RD area (table area) information for databases

cscserverinfo-tbl-area=table-area-for-basic-HCSC-information ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the table area that creates the basic HCSC information table. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

server-trans-tbl-area=table-area-for-HCSC-linkage ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the table area that creates the HCSC linkage directory. The value to be specified depends on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

location-tbl-area=table-area-for-locations ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the table area that creates the location directory. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

routing-tbl-area=table-area-for-routing ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the table area that creates the routing directory. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

cv-tbl-area=table-area-for-data-transformation ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the table area that creates the data transformation directory. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

exehistory-tbl-area=table-area-for-execution-log-information ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the table area that creates the execution log information table. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

exehistory-idx-area=area-for-storing-execution-log-information-table-index ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the execution log information table. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

process-tbl-area=area-for-storing-PROCESS-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the PROCESS table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

process-idx-area=area-for-storing-index-of-PROCESS-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the PROCESS table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

activity-tbl-area=area-for-storing-ACTIVITY-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the ACTIVITY table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

activity-idx-area=area-for-storing-index-of-ACTIVITY-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the ACTIVITY table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

link-tbl-area=area-for-storing-LINK-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the LINK table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

link-idx-area=area-for-storing-index-of-LINK-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the LINK table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

correlationset-tbl-area=area-for-storing-CORRELATIONSET-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the CORRELATIONSET table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

correlationset-idx-area=area-for-storing-index-of-CORRELATIONSET-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the CORRELATIONSET table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

string-variable-tbl-area=area-for-storing-STRING-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the STRING-VARIABLE table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

string-variable-idx-area=area-for-storing-index-of-STRING-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the STRING-VARIABLE table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

numeric-variable-tbl-area=area-for-storing-NUMERIC-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the NUMERIC-VARIABLE table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

numeric-variable-idx-area=area-for-storing-index-of-NUMERIC-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the NUMERIC-VARIABLE table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

boolean-variable-tbl-area=area-for-storing-BOOLEAN-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the BOOLEAN-VARIABLE table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

boolean-variable-idx-area=area-for-storing-index-of-BOOLEAN-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the BOOLEAN-VARIABLE table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

message-variable-tbl-area=area-for-storing-MESSAGE-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the MESSAGE-VARIABLE table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

message-variable-idx-area=area-for-storing-index-of-MESSAGE-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the MESSAGE-VARIABLE table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

message-variable-val-area=area-for-storing-VariableValue-string-of-MESSAGE-VARIABLE-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the VariableValue string of the MESSAGE-VARIABLE table for the business process infrastructure.

• In HiRDB

  No value needs to be specified. This property is disabled even if specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

message-relation-tbl-area=area-for-storing-MESSAGE-RELATION-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the MESSAGE-RELATION table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

message-relation-idx-area=area-for-storing-index-of-MESSAGE-RELATION-table-for-business-process-infrastructure ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the index of the MESSAGE-RELATION table for the business process infrastructure. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the index area is determined based on the database to be used.

clusterinfo-tbl-area=area-for-storing-cluster-information ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the table to store the cluster information that is set up in a cluster. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

haasyncadp-tbl-area=area-for-storing-service-IDs-of-asynchronous-adapters-deployed-within-a-cluster ~ <For a string and an RD area name: Alphanumeric characters beginning with alphabetic characters, and spaces> ((For an RD area name: 1 to 30 characters))

Specifies the area that creates the table to store the asynchronous-adapters service IDs deployed within a cluster. The value to be specified differs depending on the type of the database to be used.

• In HiRDB

  The RD area name will be specified.

• In Oracle

  The table area will be specified.

If you omit this property, the table area is determined based on the database to be used.

sql-scriptfilename=path-for-SQL-script-file ~ <Character string>

Specifies an absolute path for the SQL script file used to create the database. Use the characters / or \\ as directory delimiters.

This property is an optional function. When you specify a user SQL file in this property, make sure that the TABLE name, INDEX name, and VIEW name of the SQL file are correct. The operations might not function properly if you specify incorrect names. Also, when you remove the HCSC server setup, the tables used by the HCSC server are deleted irrespective of the SQL file contents. However, the tables that can be shared within the HA cluster are deleted only when the setup of the last HCSC server in the cluster is removed. For details on the set of tables used by the HCSC server, see 7.5.3 How to recover when executing HCSC server setup and unsetup in the uCosminexus Service Platform Setup and Operation Guide.

Also, for details on the SQL script file, see Appendix D. Setting up the SQL Script File in the uCosminexus Service Platform Setup and Operation Guide.

Note that the following properties will be disabled when you specify this property:

• cscserverinfo-tbl-area

• server-trans-tbl-area

• location-tbl-area

• routing-tbl-area

• cv-tbl-area

• exehistory-tbl-area

• exehistory-idx-area

• process-tbl-area

• process-idx-area

• activity-tbl-area

• activity-idx-area

• link-tbl-area

• link-idx-area

• correlationset-tbl-area

• correlationset-idx-area

• string-variable-tbl-area

• string-variable-idx-area

• numeric-variable-tbl-area

• numeric-variable-idx-area

• boolean-variable-tbl-area

• boolean-variable-idx-area

• message-variable-tbl-area

• message-variable-idx-area

• message-variable-val-area

• message-relation-tbl-area

• message-relation-idx-area

• clusterinfo-tbl-area

• haasyncadp-tbl-area

(k) Compatibility of the maximum number of activity instances

activitynumber-maximum-compatible={ON|OFF} ~ <<OFF>>

Specifies the upper limit for the activity instance ID numbers that can be generated with one process instance.

• ON

  A maximum of 32,768 activity instance ID numbers can be generated.

• OFF

  A maximum of 2,147,483,648 activity instance ID numbers can be generated.

The default values are as follows:

• For new installations of 08-50 or later

  The default value is OFF.

• For migration from the version 08-10 or earlier

  In an environment where no database is used, the default value is OFF, and in an environment where a database is used, the default value is ON.

(l) XML parsing

xmlanalyze-mode={standard|advanced} ~ <<standard>>

Selects the XML parsing mode from the following. Specify standard if you want to emphasize the compatibility with 09-00 or earlier in the process of XML parsing or to use the SOAP attachment function.

• standard

  The entire XML document will be parsed.

• advanced

  The memory usage and the processing performance will improve when you execute the following processing:

  • When you use SOAP receptions in the SOAP 1.1/ 1.2 combined mode

  • When you use SOAP adapters in the SOAP 1.1/ 1.2 combined mode

  • When you use DB adapters

  • When you execute data transformation

The notes on specifying advanced are as follows:

• As the entire XML document is not parsed, an error might not occur even if the XML data is invalid.

• The SOAP attachment function cannot be used.

• The following components use StAX to parse XML messages:

  • SOAP receptions (in the SOAP 1.1/ 1.2 combined mode)

  • SOAP adapters (in the SOAP 1.1/ 1.2 combined mode)

  • DB adapters

  • Business processes (header allocation processing)

  Therefore, create requesters and services keeping the following points in mind:

  • An exception occurs when you specify messages of XML version 1.1.

  • An exception occurs when you use the ISO-10646-UCS-4 encoding.

  • An exception does not occur when an XML document contains an element name beginning with a colon (:).

  • An exception does not occur when the character data in an XML document contains an independent CDATA section end delimiter ("]]>").

  • An empty element tag is output with the start and end tags as follows:

    (Example) <sample></sample>

For the notes on using StAX, see 6.4 Notes on StAX in the uCosminexus Application Server XML Processor User Guide.