System properties file

The system properties file contains information that is used by the components for all members and all nodes of AS4 Microservice.

The system properties file is the SystemConfigurationSYSLoader.properties file in the install_dir\Members\resources directory.

The system properties file contains values that the different system components need to start during installation. You can modify some of the properties after the system is installed, if necessary. Work with IBM® Customer Support when you modify these properties.

Important: You cannot configure this file with the Installation Manager like you can with the data grid, data source, and message fabric properties file. If you want to change the default values of the system properties file, you must manually update the default system properties file that is created after you run the Installation Manager.
Property Description
HighInboundWaterMark

The highest inbound connection buffer size for perimeter server services.

The default value is -1, which sets the property to the default value that is expected by the perimeter server client. For more information about perimeter server watermark settings, see Add a Perimeter Server to Sterling Integrator.

For example, the current version of the perimeter server client might be set for 100 KB to be optimal for watermarks. So, -1 sets the property to 100 KB. Later, the next version of the perimeter server client might be set for 200 KB to be optimal for watermarks. So, -1 sets the property to 200 KB.

If you do not use the default value of -1, the buffer size is in bytes.

You can set specific watermark parameters for each trading partner, by adding a perimeter server for each trading partner and configuring the perimeter server to match the trading volume and document size for each trading partner. Use this property to allocate more system memory to the trading partners with which you trade larger volumes and larger files. By allocating more or less memory to a trading partner, you can increase performance.
LowInboundWaterMark

The lowest inbound connection buffer size for perimeter server services.

The default value is -1, which sets the property to the default value that is expected by the perimeter server client. For more information about perimeter server watermark settings, see Add a Perimeter Server to Sterling Integrator.

For example, the current version of the perimeter server client might be set for 100 KB to be optimal for watermarks. So, -1 sets the property to 100 KB. Later, the next version of the perimeter server client might be set for 200 KB to be optimal for watermarks. So, -1 sets the property to 200 KB.

If you do not use the default value of -1, the buffer size is in bytes.

You can set specific watermark parameters for each trading partner, by adding a perimeter server for each trading partner and configuring the perimeter server to match the trading volume and document size for each trading partner. Use this property to allocate more system memory to the trading partners with which you trade larger volumes and larger files. By allocating more or less memory to a trading partner, you can increase performance.
HighOutboundWaterMark

The highest outbound connection buffer size for perimeter server services.

The default value is -1, which sets the property to the default value that is expected by the perimeter server client. For more information about perimeter server watermark settings, see Add a Perimeter Server to Sterling Integrator.

For example, the current version of the perimeter server client might be set for 100 KB to be optimal for watermarks. So, -1 sets the property to 100 KB. Later, the next version of the perimeter server client might be set for 200 KB to be optimal for watermarks. So, -1 sets the property to 200 KB.

If you do not use the default value of -1, the buffer size is in bytes.

You can set specific watermark parameters for each trading partner, by adding a perimeter server for each trading partner and configuring the perimeter server to match the trading volume and document size for each trading partner. Use this property to allocate more system memory to the trading partners with which you trade larger volumes and larger files. By allocating more or less memory to a trading partner, you can increase performance.
LowOutboundWaterMark

The lowest outbound connection buffer size for perimeter server services.

The default value is -1, which sets the property to the default value that is expected by the perimeter server client. For more information about perimeter server watermark settings, see Add a Perimeter Server to Sterling Integrator.

For example, the current version of the perimeter server client might be set for 100 KB to be optimal for watermarks. So, -1 sets the property to 100 KB. Later, the next version of the perimeter server client might be set for 200 KB to be optimal for watermarks. So, -1 sets the property to 200 KB.

If you do not use the default value of -1, the buffer size is in bytes.

You can set specific watermark parameters for each trading partner, by adding a perimeter server for each trading partner and configuring the perimeter server to match the trading volume and document size for each trading partner. Use this property to allocate more system memory to the trading partners with which you trade larger volumes and larger files. By allocating more or less memory to a trading partner, you can increase performance.
MaxThreads The maximum number of threads for the thread pool that the perimeter server creates while it is receiving or sending the data. The default value is 10.
MinThreads The minimum number of threads for the thread pool that the perimeter server creates while it is receiving or sending the data. The default value is 5.
SFS_target_service_lookup_number_of_retries The maximum number of retries that the store and forward service (SFS) attempts if the target service is not available. Range is 0 - 100. The default value is 3.
SFS_target_service_lookup_retry_interval The time interval, in seconds, between SFS retries if the target service is not available. Range is 1 - 600. The default value is 5.
SFS_Monitor_Heartbeat_interval The time interval, in seconds, at which the SFS monitor service accesses the cache to unlock documents. Range is 1 - 2147483647. The default value is 60.
SFS_store_and_forward Indicates whether to store and forward the document. Values are:
  • true (default) - Documents are stored and forwarded by the SFS.
  • false - Documents are not stored and forwarded by the SFS.
SFS_batch_size The number of documents in a batch to submit to a target service for each destination. The default value is 20.
SFS_threshold_limit The number of documents that remain in the executor service queue before the next batch of documents is fetched. The default value is 10.
SFS_upper_limit_on_maximum_number_of_threads
Restriction: AS4 Microservice does not currently use this property.

The maximum number of threads for a destination. Range is 1 - 2147483647. The default value is 100.
SFS_upper_limit_on_number_of_destination_retries
Restriction: AS4 Microservice does not currently use this property.

The maximum number of destination retries that can be set. Range is 1 - 50. The default value is 50.
SFS_upper_limit_on_number_of_transport_retries
Restriction: AS4 Microservice does not currently use this property.

The maximum number of transport retries that can be set. Range is 1 - 50. The default value is 50.
SFS_maximum_destination_retry_interval
Restriction: AS4 Microservice does not currently use this property.

The maximum destination retry interval, in seconds, that can be set. Range is 1 - 2147483647. The default value is 2147483647.
SFS_maximum_transport_retry_interval
Restriction: AS4 Microservice does not currently use this property.

The maximum transport retry interval time, in seconds, that can be set. Range is 1 - 2147483647. The default value is 2147483647.
SFS_maximum_polling_interval
Restriction: AS4 Microservice does not currently use this property.

The maximum polling interval time, in seconds. The default value is 2147483647.
SFS_MAX_ROUND_TIME The time, in seconds, that is required to send the document to the AS2 or AS4 destination and to process the response or the retry exception. This property is used by the SFS monitor service. The default value is 1200.
SFS_EXTRA_TIME_FOR_DOC_PROCESSING The extra time, in seconds, required to process the document by AS2 or AS4, based on the system load. This property is used by the SFS monitor service. The default value is 3600.
SFS_MONITOR_SERVICE_POLLING_TIME_INTERVAL The polling time interval, in milliseconds, for the SFS monitor service to poll the SFS document data map. This property is used by the SFS monitor service. The default value is 300000.
SFS_USE_WXS_PERSISTENCE Indicates whether SFS uses the database or the WebSphere® eXtreme Scale data grid for persisting business documents. Values are:
  • true (default) - SFS uses the data grid for persisting business documents.
  • false - SFS uses the database for persisting business documents.
DispatcherMessageFabricTimeout

The interval, in milliseconds, in which the communications dispatcher tries to put the Business Document message or waits for the Business Document response message. The default value is 120000.
FabricReceiverServiceLookUpRetryCount The number of times that the message fabric receiver tries to look up the target service before the connection fails. The default value is 3.
FabricReceiverServiceLookUpRetryInterval The interval, in milliseconds, after which the message fabric receiver tries again to look up the target service. The default value is 60000.
FIPS_MODE
Restriction: AS4 Microservice does not currently use this property.

Indicates whether algorithms that are prohibited by the Federal Information Processing Standards (FIPS) are restricted. Values are:

  • true - The system restricts FIPS prohibited algorithms.
  • false (default) - The system does not restrict FIPS prohibited algorithms.
EVENT_PERSISTENCE_LEVEL For AS2 and AS4, the level of event information to publish in the visibility queue. Values are:
  • full (default) - All events are published.
  • nil - No events are published.
BUFFER_SIZE_AS2 The buffer size, in bytes, used for processing AS2. The larger the buffer size, the more data is read and written to disk and the more data is processed in memory at any point in time. The default value is 32768.
MAIN_UNPACK_PIPE_SIZE_AS2 The pipe size, in bytes, for the main inbound AS2 unpackaging. A higher value means that the network thread can write to the pipe more frequently without getting blocked. The default value is 32768.
MAIN_INBOUND_UNPACK_FUTURE_TIMEOUT_AS2 The timeout, in milliseconds, for the unpackaging task that is submitted to the AS2 inbound threadpool. This value is the wait time after the last buffer is written to the inbound piped stream. Exceeding this time generates a timeout exception. The default value is 60000.
MDN_WRITETO_STORAGE Indicates whether to store the message disposition notification (MDN) in storage. Values are:
  • true (default) - When EVENT_PERSISTENCE_LEVEL=full, the MDN is written to storage.
  • false - When EVENT_PERSISTENCE_LEVEL=full, the MDN is base 64 and stored inline in a visibility event and published.
USE_SFS_FOR_BACKENDDOC_WRITE
Restriction: AS4 Microservice does not currently use this property.

Indicates whether to use SFS to write the backend document (BDO) to the queue. Values are:

  • true - Use SFS to write the BDO to the queue.
  • false (default) - Do not use SFS to write the BDO to the queue.
DELETE_PROCESS_STATE_LOG_POST_TRX Indicates whether the process state log record needs to be deleted after the transaction is complete. Deletions decrease the memory usage in the data grid. Values are:
  • true - Delete the process state log record after the transaction is complete.
  • false (default) - Do not delete the process state log record after the transaction is complete.
COMMS_VISIBILITY_EVENT_BATCH_SIZE The number of exchange visibility events that run time waits to get queued up before batch processing gets triggered off. The default value is 40.
COMMS_VISIBILITY_EVENT_BATCH_TIMEOUT The timeout, in milliseconds, that the run time waits to pass before batch processing of exchange visibility events gets triggered off. The default value is 10.
COMMS_VISIBILITY_BLOCK_WAIT_TIMEOUT The block timeout, in milliseconds, to be used to wait in a thread for all event parts of the thread to get published. The default value is 1200000.
PERSIST_SYNC_INBOUND_RAW_REQUEST_AS2 Indicates whether to store the raw request for an AS2 inbound transaction that is requesting a synchronous MDN. Values are:
  • true (default) - Store the raw request for an AS2 inbound transaction that is requesting a synchronous MDN.
  • false - Do not store the raw request for an AS2 inbound transaction that is requesting a synchronous MDN.
SoftStopTimeout
Important: The SoftStopTimeout property does not appear by default in an installation. To use this property, you must add it to the SystemConfigurationSYSLoader.properties file.

The time, in minutes, to use for the member softstop command default timeout. This value is used when the user does not specify a timeout value on the command line. If you do not specify a value for this property and the user does not specify a timeout value when you are using the command, the timeout defaults to one day.
SCHEDULER_USE_WXS

Indicates whether the scheduler writes information to the WebSphere eXtreme Scale data grid or directly to the database. Valid values are:

  • true (default) - The scheduler uses the WebSphere eXtreme Scale-based model.
  • false - The scheduler uses the direct database-based model.
IDENTITY_CRL_CHECK

Indicates whether to check the Certificate Revocation List (CRL) for each certificate that is retrieved. If this property is set to true, a request to get certificates does not return revoked or suspended certificates. Values are:

  • true (default) - Check the CRL for each certificate that is retrieved.
  • false - Do not check the CRL for each certificate that is retrieved.
IDENTITY_EXPIRY_CHECK

Indicates whether to allow an expired certificate when it is retrieved. If this property is set to true, a request to get certificates does not return expired certificates. Values are:

  • true - Do not allow an expired certificate when it is retrieved.
  • false (default) - Allow an expired certificate when it is retrieved.
IDENTITY_CERTPATH_VALIDATION

Indicates whether to validate the certificate path for each certificate that is retrieved. If this property is set to true, a request to get a certificate returns a certificate only if the certificate path validation is successful. Values are:

  • true (default) - Validate the certificate path for each certificate that is retrieved.
  • false - Do not validate the certificate path for each certificate that is retrieved.
NON_REPUDIATION_STORAGE_BUCKET
Important: The NON_REPUDIATION_STORAGE_BUCKET property does not have a default value. To use this property, you must add a value to it in the SystemConfigurationSYSLoader.properties file.

The storage bucket for storing nonrepudiation information, which is all of the raw data that is sent or received for all AS4 requests and responses. This data is saved by customers to an external directory. AS4 processing uses this property value to route non-repudiation information to this bucket.

You must set this property after you provision the storage bucket that is used for non-repudiation information.

If this property has no value, the nonrepudiation data is stored in the default bucket.
IDENTITY_MF_TIMEOUT The identity message fabric timeout in milliseconds. The default value is 150000.
DELETE_PULL_BLOBS

Indicates whether to delete the storage blobs while the pull message is being deleted after a successful pull transaction. Values are:

  • true (default) - Delete the storage blobs while the pull message is being deleted.
  • false - Do not delete the storage blobs while the pull message is being deleted.
USEREXIT_AUTHENTICATION_OUTBOUND_SERVICEID The user exit authentication and authorization service ID for outbound transactions. The default value is AuthenticationOutboundService.
USEREXIT_AUTHENTICATION_INBOUND_SERVICEID The user exit authentication and authorization service ID for inbound transactions. The default value is AuthenticationInboundService.
USERID_CERT_OIDS
Important: The USERID_CERT_OIDS property does not have a default value. To use this property, you must add a value to it in the SystemConfigurationSYSLoader.properties file.

The object identifier component of the user ID that is constructed from an X.509 certificate. The ID is constructed in the following order:

  1. Object identifier (OID) (USERID_CERT_OIDS)
  2. Subject attributes like CN or O (USERID_CERT_SUBJECT_ATTRIBUTES)

The user ID is sent to Sterling B2B Integrator in the business document (BDO). It also is used for the pull request authorization lookup.
USERID_CERT_SUBJECT_ATTRIBUTES
Important: The USERID_CERT_SUBJECT_ATTRIBUTES property does not have a default value. To use this property, you must add a value to it in the SystemConfigurationSYSLoader.properties file.

The subject attribute component of the user ID that is constructed from an X.509 certificate. The ID is constructed in the following order:

  1. Object identifier (OID) (USERID_CERT_OIDS)
  2. Subject attributes like CN or O (USERID_CERT_SUBJECT_ATTRIBUTES)

The user ID is sent to Sterling B2B Integrator in the business document (BDO). It also is used for the pull request authorization lookup.
RETRANSMISSION_INTERVAL The time, in milliseconds, between retransmitting messages for Web Services Reliable Messaging in AS4. The default value is 60000.
MAXIMUM_RETRANSMISSION_COUNT The maximum number of times to retry sending unacknowledged messages for Web Services Reliable Messaging in AS4. The default value is 1.
EXPONENTIAL_BACKOFF Indicates whether the time between message retransmission attempts for Web Services Reliable Messaging in AS4 grows exponentially. Valid values are:
  • true - The time between message retransmission attempts grows exponentially.
  • false (default) - The time between message retransmission attempts grows exponentially.
INACTIVITY_TIMEOUT The time that the message sequence for Web Services Reliable Messaging in AS4 remains inactive before it is cleaned up (in milliseconds). The default value is 300000.
AS4_OB_TWO_WAY_PUSH_PULL_DEFAULT_QUEUE_NAME The default queue to which the pull response business document object (BDO) is delivered for the outbound two-way push pull pattern in AS4, if a delivery destination is not available in the configuration. The default value is backendOutboundQueue.
COMMS_GENERIC_RETRY_COUNT The number of retries to write to the WebSphere eXtreme Scale data grid for most of the communications configurations. The default value is 20.
COMMS_GENERIC_RETRY_INTERVAL The interval in milliseconds for retries to write to the WebSphere eXtreme Scale data grid for most of the communications configurations. The default value is 3000.
COMMS_MEMORYEVENT_PRIVISIONER_RETRY_TIME The time, in milliseconds, that the memory event subscriber waits before each retry to the aggregator. The default value is 60000.
COMMS_MEMORYEVENT_DELAY_BEFORE_STOP The time, in milliseconds, to delay or wait before a STOP command is issued to give time for the resources to be quiesced. The default value is 300000.
IN_MEMORY_WSRM_INBOUND
Important: The IN_MEMORY_WSRM_INBOUND property does not appear by default in an installation. To use this property, you must add it to the SystemConfigurationSYSLoader.properties file.

Indicates whether the axis configuration for Web Services Reliable Messaging (WSRM) inbound messages uses the local in-memory storage manager. Valid values are:

  • true - The axis configuration for WSRM inbound messages uses the local in-memory storage manager.
  • false - The axis configuration for WSRM inbound messages does not use the local in-memory storage manager.
IN_MEMORY_WSRM_OUTBOUND
Important: The IN_MEMORY_WSRM_OUTBOUND property does not appear by default in an installation. To use this property, you must add it to the SystemConfigurationSYSLoader.properties file.

Indicates whether the axis configuration for Web Services Reliable Messaging (WSRM) outbound messages uses the local in-memory storage manager. Valid values are:

  • true - The axis configuration for WSRM outbound messages uses the local in-memory storage manager.
  • false - The axis configuration for WSRM outbound messages does not use the local in-memory storage manager.
DISPLAY_HEADERS_AS_VIZ_EVENT Indicates whether to include headers under the visibility event. By default, the value is true, which indicates that headers are included under the visibility event.
Important: If this property is set to true during the runtime flow of the AS4 protocol, the soap headers are passed to the visibility events.
AS2_NOTIFICATION_ENABLED Indicates whether the notification message is required for AS2. By default, the value is false, which indicates the AS2 notification is not enabled. To enable the notification, you must set the value to true.
AS2_NOTIFICATION_QUEUE Indicates the AS2 notification queue name. By default, the value is DefaultNotificationQueue. You can see the success or failure notification at the end of transaction in the configured queue. You can also configure the queue name of your choice by changing the default value.
EBMS_HEADER_VALIDATION_REQUEST Used to enable EBMS Header validation for an AS4 request. Set the property with value true. After you enable this property, you can see the corresponding visibility event in REQUEST tab under a transaction.
EBMS_HEADER_VALIDATION_RESPONSE Used to enable EBMS Header validation for an AS4 response. Set the property with value true.

After you enable this property, you can see the corresponding visibility event in RESPONSE tab under a transaction.

Example of system properties file

This code is an example of a system properties file:

# These configuration values are used by the system to configure various
# features of the system the same way for all members of the collective

#High/Low Watermarks for Perimeter Server Services
#You can set specific watermark parameters for each trading partner, by adding a perimeter server for each trading partner and configuring the perimeter 
#server to match the trading volume and document size for each trading partner. This enables you to allocate more system memory to your trading partners 
#with which you trade larger volumes and larger files. By allocating more or less memory to a trading partner, you can increase performance. 

#Inbound Connection 

#Highest inbound connection buffer size. This is the high watermark.
HighInboundWaterMark=-1

#Lowest inbound connection buffer size. This is the low watermark. 
LowInboundWaterMark=-1

#Outbound Connection

#Highest Outbound connection buffer size. This is the high watermark.
HighOutboundWaterMark=-1

#Lowest Outbound connection buffer size. This is the low watermark. 
LowOutboundWaterMark=-1

#Maximum and Minimum Threads for the Thread pool Perimeter Server creates while receiving or sending the data

MaxThreads=10
MinThreads=5

# SFS configuration properties
# Target service lookup number of retries 
SFS_target_service_lookup_number_of_retries=3

# Target service lookup retry interval 
SFS_target_service_lookup_retry_interval=5

# SFS_Monitor_Heartbeat_interval 
SFS_Monitor_Heartbeat_interval=60

# Store & forward 
SFS_store_and_forward=true

# Number of documents in a batch  to submit to target service [for each destination ]
SFS_batch_size=20

# Number of documents still remain in the executor service queue before fetching the next batch of documents 
SFS_threshold_limit=10

# Upper limit of maximum no. of threads
SFS_upper_limit_on_maximum_number_of_threads=100

# Upper limit on no. of destination retries
SFS_upper_limit_on_number_of_destination_retries=50

# Upper limit on no. of transport retries
SFS_upper_limit_on_number_of_transport_retries=50

# Maximum destination retry interval
SFS_maximum_destination_retry_interval=2147483647

# Maximum transport retry interval
SFS_maximum_transport_retry_interval=2147483647

# Maximum polling interval
SFS_maximum_polling_interval=2147483647

#time required to send the document to as2 destination and to process the response or RetryException (used in sfs monitor service)
#21937
SFS_MAX_ROUND_TIME=1200

#any extra time required to process the document by as2 as per system load in seconds (used in sfs monitor service)
SFS_EXTRA_TIME_FOR_DOC_PROCESSING=3600

#polling time interval for sfs monitor service to poll the sfs document data map in milliseconds (used in sfs monitor service)
SFS_MONITOR_SERVICE_POLLING_TIME_INTERVAL=300000

# The default value is true ,indicates SFS [Store and forward service ] component will use  WXS [WebSphere Extreme Scale] for persisting business documents
# If the value is false ,then SFS will use direct database for persisting business documents
# SFS_USE_WXS_PERSISTENCE=[true][false]
SFS_USE_WXS_PERSISTENCE=true

# Queue Dispatcher Configuration Parameters
#Timeout Interval in milliseconds till when message fabric tries to put the message or waits for the response message
DispatcherMessageFabricTimeout=120000

#Number of times Fabric Receiver looks up for the target service before failing 
FabricReceiverServiceLookUpRetryCount=3

#Retry time Interval in milliseconds after which a retry to look up the target service is done by Fabric Receiver
FabricReceiverServiceLookUpRetryInterval=60000

# FIPS Mode Enablement
# Enabling this makes sure that FIPS non-compliant algorithms will not be used in the system.
# FIPS_MODE=[true]|[false]
FIPS_MODE=false

# Event Persistence Level
# The level of event capturing to publish in visibility queue
# EVENT_PERSISTENCE_LEVEL=[full]|[nil]
EVENT_PERSISTENCE_LEVEL=full

# Buffer size for AS2 processing (as number of bytes)
# This will be the buffer size used in all AS2 processing right from channel read to 
# pipes and writing out to storage.
BUFFER_SIZE_AS2=32768

# The pipe size for the main inbound AS2 unpackaging (as number of bytes)
# This will be the pipe size used for the main inbound AS2 unpackaging pipe. 
# Higher value means that the network thread can write to the pipe more frequently without getting blocked.
MAIN_UNPACK_PIPE_SIZE_AS2=32768

# This is the timeout (in milliseconds) for the unpackaging task submitted to the inbound threadpool.
# This will be the wait time after the last buffer is written to the inbound piped stream exceeding which will result in a TimeoutException.
MAIN_INBOUND_UNPACK_FUTURE_TIMEOUT_AS2=60000

# MDN write to storage enablement
# Indicates whether to store the MDN in MEG Storage. If the EVENT_PERSISTENCE_LEVEL=nil and 
# MDN_WRITETO_STORAGE=false, then, the MDN would not be persisted at all.
# MDN_WRITETO_STORAGE=[true]|[false]
MDN_WRITETO_STORAGE=true

# Use SFS for Backend Document (BDO) write to queue
# Indicates whether the writing of BDO to backend destination needs to go through SFS.
# USE_SFS_FOR_BACKENDDOC_WRITE=[true]|[false]
USE_SFS_FOR_BACKENDDOC_WRITE=false

# Delete Process State Log post transaction completion
# Indicates whether the process state log record needs to be deleted after the transaction is complete. Deletion decreases the memory footprint in WXS.
# DELETE_PROCESS_STATE_LOG_POST_TRX=[true]|[false]
DELETE_PROCESS_STATE_LOG_POST_TRX=false

# COMMS visibility event Batch Size
# Indicates the batch size (number) to be used for publishing visibility events in COMMS
COMMS_VISIBILITY_EVENT_BATCH_SIZE=40

# COMMS visibility event Batch Timeout
# Indicates the batch timeout (in millisecond) to be used for publishing visibility events in COMMS
COMMS_VISIBILITY_EVENT_BATCH_TIMEOUT=10

# COMMS visibility Block wait Timeout
# Indicates the block timeout (in millisecond) to be used while waiting finally in a thread for all events to get published
COMMS_VISIBILITY_BLOCK_WAIT_TIMEOUT=1200000

# Inbound AS2 synchronous raw request persistence enablement
# Indicates whether we need to store the raw request for an AS2 inbound transaction in synchronous mode.
# PERSIST_SYNC_INBOUND_RAW_REQUEST_AS2=[true]|[false]
PERSIST_SYNC_INBOUND_RAW_REQUEST_AS2=true

#   Scheduler Component Starts # 
#IF Scheduler has to configure WXS BASED MODEL else, it will configure the Direct DB based model.
SCHEDULER_USE_WXS=true
#   Scheduler Component Ends #

#Identity
#Does a crl check for certificate to be used 
IDENTITY_CRL_CHECK=true

#Expiry certificates will be used.
IDENTITY_EXPIRY_CHECK=false

#Does a cert path validation
IDENTITY_CERTPATH_VALIDATION=true

# The storage bucket name for storing non repudiation information.
# Once the non repudiation storage bucket is provisioned, the non repudiation storage bucket name should be assigned to this key.
# If Empty, the non repudiation data will be stored into the default bucket.
NON_REPUDIATION_STORAGE_BUCKET=

#Identity MessageFabric timeout in milliseconds
IDENTITY_MF_TIMEOUT=150000

#Delete the storage blobs while deleting the pull message, after a successful pull transaction
DELETE_PULL_BLOBS=true

#User exit authentication and authorization service id
USEREXIT_AUTHENTICATION_OUTBOUND_SERVICEID=AuthenticationOutboundService
USEREXIT_AUTHENTICATION_INBOUND_SERVICEID=AuthenticationInboundService

#UserId constructed from x509Certificate will use the following OIDs and Subject Attributes like CN, O..
#UserId will be constructed in the order of OIDs first, followed by Subject Attributes
#This UserId will be sent to Backend(SI) in the BDO. It will also be used for Pull Request Authorization Lookup
USERID_CERT_OIDS=
USERID_CERT_SUBJECT_ATTRIBUTES=

#RELIABLE MESSAGING PROPERTIES - START
#time between retransmitting messages (in milliseconds).
RETRANSMISSION_INTERVAL=60000
#max count to retry sending unacknowledged messages.
MAXIMUM_RETRANSMISSION_COUNT=1
#if true the time between message retransmission attempts will grow exponentially.
EXPONENTIAL_BACKOFF=false
#time that the sequence is allowed to remain inactive before it is cleaned up (in milliseconds).
INACTIVITY_TIMEOUT=300000
#RELIABLE MESSAGING PROPERTIES - END

#Default queue to which the Pull response BDO will be delivered for outbound 2 way push pull pattern, if a delivery destination is not available in the configuration
AS4_OB_TWO_WAY_PUSH_PULL_DEFAULT_QUEUE_NAME=backendOutboundQueue

#Number of retries for most of COMMS configurations. This is applicable to retries to WXS.
COMMS_GENERIC_RETRY_COUNT=20
#Retry interval in milliseconds for most of the retry configurations in COMMS. This is applicable to retries to WXS.
COMMS_GENERIC_RETRY_INTERVAL=3000

#The memory event subscriber will wait before each retry to the aggregator. 
COMMS_MEMORYEVENT_PRIVISIONER_RETRY_TIME=60000

# Delay or wait defore a STOP is issued inorder to give time for the resources to be quiesced.
COMMS_MEMORYEVENT_DELAY_BEFORE_STOP=300000

# Include headers under the visibility event.
DISPLAY_HEADERS_AS_VIZ_EVENT = TRUE

# Indicate whether the notification message is required for AS2.
AS2_NOTIFICATION_ENABLED = TRUE

# Indicate the notification queue name.
AS2_NOTIFICATION_QUEUE = DefaultNotificationQueue

# Enable EBMS Header validation for an AS4 request.
EBMS_HEADER_VALIDATION_REQUEST = TRUE

# Enable EBMS Header validation for an AS4 response.
EBMS_HEADER_VALIDATION_RESPONSE = TRUE

Custom Cipher Configuration

To use custom ciphers in AS4 Microservice, you need to add the cipher values in the SystemConfigurationSYSLoader.properties file in the following format:

CIPHER.n=<cipher value>

Here, n is the number of ciphers. A maximum of 1000 ciphers can be added.

You need to execute the command execute config load sys_config from Member/bin.
Note: To execute the above command, the Catalog and Container members must be up and running. You can also execute the command even if all the four members (catalog, container, operational, informational) are up and running.

On execution of the above command, the values of the ciphers are populated in the HTTP SERVER and HTTP DESTINATION pages. When you select the Security Level as CUSTOM in above pages, then you see list of ciphers and save it.

When AS4 Microservice establishes or accepts an SSL connection, it uses the ciphers that are configured in HTTPS Destination for outbound connections and HTTPS Server for inbound connections.