Application Configuration
General Configuration
Key |
Type |
Description |
Default Value |
|
|
|
|
|
|
Whether to map bics from config, or direct from the incoming |
|
|
|
Whether to map bics from config, or direct from the incoming |
|
|
|
The instructing agent BIC to be used by the CSM (grpHdr.instgAgt.finInstnId.BICFI) |
|
|
|
The instructed agent BIC to be used by the CSM (grpHdr.instdAgt.finInstnId.BICFI). |
|
|
|
The instructing agent BIC to be used by the CSM (grpHdr.instgAgt.finInstnId.BICFI) |
|
|
|
The instructed agent BIC to be used by the CSM (grpHdr.instdAgt.finInstnId.BICFI). |
|
|
|
Whether the service should check if the inbound payments are received within the specified |
|
|
|
The max allowed amount per transaction. |
|
|
|
The max allowed age of received inbound payments. |
|
|
|
A list of creditor agent BICs allowed for inbound payments. |
|
|
|
List of debtor agent BICs allowed for outbound payments. |
|
|
|
The instructing agent BIC to be used by the CSM. |
|
|
|
The max allowed age of received AM05 rejects. |
|
|
|
Minimum back off time before a retry |
|
|
|
Time it will take to apply restart max restrictions - whichever comes first max-restarts or the time limit will end retries |
|
|
|
Maximum number of retries before failure |
|
|
|
Maximum back off time before a retry |
|
|
|
Multiplier for the retry back off times - every retry will progressively longer depends on this factor - by default here it adds 25 percent on each retry |
|
|
|
Should TIPS CSM service listen to the If true - it listens and this will be translated to technical response which will be sent to the clients of TIPS CSM Service If false - it doesn’t listen for send outcomes. However, TIPS CSM Service will generate appropriate technical response as soon as the message is sent out |
|
|
|
Should we ignore AM05 reject messages |
|
|
|
The max allowed age of received AM05 rejects. |
|
|
|
Generate IPF processing data events |
|
|
|
Where to output message log messages. e.g. mongo,kafka,ipf-processing-data-egress |
|
Validation Configurations
Property Grouping: ipf.csm.tips.validation.pacs008
| Key | Description | Default Value |
|---|---|---|
ipf.csm.tips.validation.pacs008.creditor-address-structural-validation-inbound.enabled |
Enables structural creditor address validations for inbound pacs.008 messages. |
|
ipf.csm.tips.validation.pacs008.creditor-address-structural-validation-outbound.enabled |
Enables structural creditor address validations for outbound pacs.008 messages. |
|
ipf.csm.tips.validation.pacs008.debtor-address-structural-validation-inbound.enabled |
Enables structural debtor address validations for inbound pacs.008 messages. |
|
ipf.csm.tips.validation.pacs008.debtor-address-structural-validation-outbound.enabled |
Enables structural debtor address validations for outbound pacs.008 messages. |
|
ipf.csm.tips.validation.pacs008.non-eea-debtor-address-validation-inbound.enabled |
Enables non EEA debtor address validations for inbound pacs.008 messages. |
|
ipf.csm.tips.validation.pacs008.non-eea-debtor-address-validation-outbound.enabled |
Enables non EEA debtor address validations for outbound pacs.008 messages. |
|
Character Replacements Configurations
Config |
Type |
Description |
|
|
Character to be replaced |
|
|
Character replacement |
|
|
Flag indicating whether the replacement should happen only in the text nodes of the DOM |
|
|
List of characters to be replaced |
|
|
Character replacement for list |
|
|
Flag indicating whether the replacement should happen only in the text nodes of the DOM |
|
|
Regular expression for replaced characters |
|
|
Character replacement for regex |
|
|
Flag indicating whether the replacement should happen only in the text nodes of the DOM |
Processing Entity Configuration
Extra notes - Cache purging configuration for Pacs.008 inbound and outbound messages duplicate check
The below table contains only the root path of the configuration. For all options of the cache purging configuration please refer to the transaction cache documentation.
The purging period (retain-from-offset) value should always be longer than the value of
pacs008-duplicate-message-check-period.
Config |
Type |
Comment |
Default |
|
Period |
Sets the duplicate validation period for Pacs.008 messages. The value is rounded to full days (e.g. 25 and 47 hours is still 1 day). The check considers all previous message within the configured period and a duplicate is only flagged when it has been created in the given period, it is otherwise ignored. If set to 0 the check falls down to the default behaviour. |
|
|
Boolean |
Controls if purging is enabled for the Pacs.008 inbound and outbound duplicate checks cache entries. |
|
|
Complex Type |
Configures the inbound Pacs.008 duplicate check cache entries purge. When enabled, it will default to 17:00 after 10 days. |
|
|
Complex Type |
Configures the outbound Pacs.008 duplicate check cache entries purge. When enabled, it will default to 17:00 after 10 days. |
Gateway Header Configuration
Key |
Type |
Description |
Default Value |
Inserted As Message Header |
|
|
Should gateway headers be included in messages sent to the scheme |
|
N/A |
|
|
ID of the sender |
|
|
|
|
ID of the receiver e.g. CSM |
|
|
|
|
Key, value pair of class and applicable message type |
|
|
|
|
Indicates the routing strategy, which decide if message should be routed. Used when routing to TIPS from RT1 |
|
|
|
|
Indicates if the message to be sent is potentially a duplicate (Y/N) |
|
|
JMS Configuration
General JMS Configuration
Key |
Type |
Description |
Default Value |
|
|
Outbound queue to CSM |
|
|
|
|
|
|
|
Use IBM MQ or Artemis MQ as broker |
|
|
|
Inbound queue from CSM |
|
|
|
|
Artemis
Key |
Type |
Description |
Default Value |
|
|
Broker URL of an ActiveMQ Artemis deployment |
|
IBM MQ
Key |
Type |
Description |
Default Value |
|
|
The host name or IP address of the system on which the IBM MQ broker runs. The property is used with the |
localhost |
|
|
The number of the port on which the IBM MQ queue manager listens for incoming requests. |
|
|
|
Name of the queue manager we’re connecting to. |
|
|
|
The name of the channel to be used for the connection to the IBM MQ broker |
|
|
|
The name of the CipherSuite to be used on an SSL or TLS connection to a queue manager. The protocol used in negotiating the secure connection depends on the specified CipherSuite. |
|
|
|
The location of the SSL keystore to be used when connecting to IBM MQ. |
Not set |
|
|
The password of the SSL keystore to be used when connecting to IBM MQ. |
Not set |
|
|
The type of the SSL keystore to be used when connecting to IBM MQ. |
Not set |
Kafka Configuration
Key |
Type |
Description |
Default Value |
|
|
Name of the topic that the TIPS CSM service adapter will receive messages from |
|
|
|
Multiplier for the retry back off times - every retry will progressively longer depends on this factor - by default here it adds 25 percent on each retry |
|
|
|
Maximum back off time before a retry |
|
|
|
Name of the topic that the TIPS CSM service adapter will send messages to |
|
|
|
Minimum back off time before a retry |
|
|
|
Maximum number of retries before failure |
|
|
|
Kafka consumer GroupID |
|
|
|
Minimum back off time before a retry |
|
|
|
Maximum back off time before a retry |
|
|
|
Time it will take to apply restart max restrictions - whichever comes first max-restarts or the time limit will end retries |
|
|
|
Time it will take to apply restart max restrictions - whichever comes first max-restarts or the time limit will end retries |
|
|
|
Name of the topic that the TIPS CSM Service adapter will receive messages from |
|
|
|
Maximum number of retries before failure |
|