Hi,

In a B2B MQ->SFTP setup where specific SFTP servers have a low limit of allowed connections - what are my options to handle this?

Currently the B2B service is using a common input queue and routes the messages/files to different SFTP servers as defined in the destination for respective receiver partner profile.

- Can I use SLM Policy/action to shape (queue) transactions bound for a specific partner profile (or destination)? If so how do I achieve this?
- Do I have to use dedicated input MQ queues and specific Datapower QMGR objects with matching "Total Connection Limit" for these SFTP backends?

Regards,
Rikard

------------------------------
Rikard Almroth
------------------------------

Hi I would recomend #2 - for #1 it is not a good idea to pull those mq messages into datapower and shape them, hey will just sit in memory and consume resources and potentialy could be lost if the internal shaping backlog got to big; better to let them sit on the mq q until they can be processed to the backend.

#2 would work. with a dedicated mq q and a connection limit from datapower to that qm then you can assure that the number of backend connections to the sftp would never exceed that limit set.
​​​

------------------------------
Matthias Siebler
MA
------------------------------

Original Message:
Sent: Mon August 22, 2022 03:38 AM
From: Rikard Almroth
Subject: B2B MQ -> SFTP. Limit number of connections for specific backends

Hi,

In a B2B MQ->SFTP setup where specific SFTP servers have a low limit of allowed connections - what are my options to handle this?

Currently the B2B service is using a common input queue and routes the messages/files to different SFTP servers as defined in the destination for respective receiver partner profile.

- Can I use SLM Policy/action to shape (queue) transactions bound for a specific partner profile (or destination)? If so how do I achieve this?
- Do I have to use dedicated input MQ queues and specific Datapower QMGR objects with matching "Total Connection Limit" for these SFTP backends?

Regards,
Rikard

------------------------------
Rikard Almroth
------------------------------

Hi,
Yes I will probably go for that solution.
Thanks for the reply.
/rikard

------------------------------
Rikard Almroth
------------------------------

Original Message:
Sent: Tue August 23, 2022 07:16 AM
From: Matthias Siebler
Subject: B2B MQ -> SFTP. Limit number of connections for specific backends

Hi I would recomend #2 - for #1 it is not a good idea to pull those mq messages into datapower and shape them, hey will just sit in memory and consume resources and potentialy could be lost if the internal shaping backlog got to big; better to let them sit on the mq q until they can be processed to the backend.

#2 would work. with a dedicated mq q and a connection limit from datapower to that qm then you can assure that the number of backend connections to the sftp would never exceed that limit set.
​​​

------------------------------
Matthias Siebler
MA

Original Message:
Sent: Mon August 22, 2022 03:38 AM
From: Rikard Almroth
Subject: B2B MQ -> SFTP. Limit number of connections for specific backends

Hi,

In a B2B MQ->SFTP setup where specific SFTP servers have a low limit of allowed connections - what are my options to handle this?

Currently the B2B service is using a common input queue and routes the messages/files to different SFTP servers as defined in the destination for respective receiver partner profile.

- Can I use SLM Policy/action to shape (queue) transactions bound for a specific partner profile (or destination)? If so how do I achieve this?
- Do I have to use dedicated input MQ queues and specific Datapower QMGR objects with matching "Total Connection Limit" for these SFTP backends?

Regards,
Rikard

------------------------------
Rikard Almroth
------------------------------