Setting up the Sending Application
The 'sending application' is the one sending requests to, and retrieving responses from, your payment adjustment application. To send requests to, and retrieve responses from, your payment adjustment application, you can wire in Send and Receive connectors for your chosen transport. The connectors can be wired in as described on this page.
The connectors should be configured above the default configuration by consulting the Connector documentation.
Kafka
To communicate via Kafka, you will need to bring the following dependency into your 'sending application'.
<dependency>
<groupId>com.iconsolutions.ipf.payments.adjustment</groupId>
<artifactId>payment-adjustment-client-connector-kafka</artifactId>
</dependency>This brings in a SendConnector and a ReceiveConnector with default configuration, as shown below. In addition to the below defaults, they’ll also have all the standard Kafka Connector default configurations. To customise the configuration, please consult the Connector documentation.
Property Grouping: ipf.payment-adjustment.request.kafka.producer
| Key | Description | Default Value |
|---|---|---|
ipf.payment-adjustment.request.kafka.producer.kafka-clients.client.id |
|
|
ipf.payment-adjustment.request.kafka.producer.restart-settings.max-backoff |
|
|
ipf.payment-adjustment.request.kafka.producer.restart-settings.max-restarts |
|
|
ipf.payment-adjustment.request.kafka.producer.restart-settings.max-restarts-within |
|
|
ipf.payment-adjustment.request.kafka.producer.restart-settings.min-backoff |
|
|
ipf.payment-adjustment.request.kafka.producer.restart-settings.random-factor |
|
|
ipf.payment-adjustment.request.kafka.producer.topic |
|
Property Grouping: ipf.payment-adjustment.response.kafka.consumer
| Key | Description | Default Value |
|---|---|---|
ipf.payment-adjustment.response.kafka.consumer.kafka-clients.auto.offset.reset |
|
|
ipf.payment-adjustment.response.kafka.consumer.kafka-clients.group.id |
|
|
ipf.payment-adjustment.response.kafka.consumer.restart-settings.max-backoff |
|
|
ipf.payment-adjustment.response.kafka.consumer.restart-settings.max-restarts |
|
|
ipf.payment-adjustment.response.kafka.consumer.restart-settings.max-restarts-within |
|
|
ipf.payment-adjustment.response.kafka.consumer.restart-settings.min-backoff |
|
|
ipf.payment-adjustment.response.kafka.consumer.restart-settings.random-factor |
|
|
ipf.payment-adjustment.response.kafka.consumer.topic |
|
JMS
To communicate via JMS, you will need to bring the following dependency into your 'sending application'.
<dependency>
<groupId>com.iconsolutions.ipf.payments.adjustment</groupId>
<artifactId>payment-adjustment-client-connector-jms</artifactId>
</dependency>This brings in a SendConnector and a ReceiveConnector with default configuration, as shown below. In addition to the below defaults, they’ll also have all the standard JMS Connector default configurations. To customise the configuration, please consult the Connector documentation.
Property Grouping: ipf.payment-adjustment.client-connector.jms
| Key | Description | Default Value |
|---|---|---|
ipf.payment-adjustment.client-connector.jms.broker.url |
|
|
ipf.payment-adjustment.client-connector.jms.consumer-window-size |
|
|
ipf.payment-adjustment.client-connector.jms.failover-timeout |
|
|
ipf.payment-adjustment.client-connector.jms.receive-timeout |
|
|
ipf.payment-adjustment.client-connector.jms.request.queue |
Queues |
|
ipf.payment-adjustment.client-connector.jms.response.queue |
|
|
ipf.payment-adjustment.client-connector.jms.session-cache-size |
|
HTTP
| If you’d prefer to use your own client implementation to connect via HTTP then please refer to the Payment Adjustment OpenAPI Specification page. |
To communicate via HTTP, you can bring the following dependency into your 'sending application'.
<dependency>
<groupId>com.iconsolutions.ipf.payments.adjustment</groupId>
<artifactId>payment-adjustment-client-connector-http</artifactId>
</dependency>This dependency brings in a HTTP RequestReplySendConnector with default configuration, as shown below. In addition to the below defaults, they’ll also have all the standard HTTP Connector default configurations. To customise the configuration, please consult the Connector documentation.