Swift Fileact interface Payload and parfile issue with Holding status

[Former Member]

I have a requirement to pick files from BCM and send to SWIFT network and get the acknowledgement files back. BCM creates only a Payment file which has got the signature in it and the requirement is to send 2 files, a payment file and an par file to SWIFT. As per my understanding I have built the following:

We are on PI 7.4 dual stack.

Based on the above requirement we used FTP(Sender) to FTP(Target) .Scenario works with file adapter (FTP to FTP),We are able to pick files from sender and able to split into two files payload and par file,but we have request to use receiver as SFTP now,

1. SWIFT 622 package provided by SAP.

2. Multimapping for paylaod and par file

3. Created the communication channels

a. File sender (FTP) channel (to pick files from server

b. Two File receiver (SFTP) channels for Payload and par files (to send to SWIFT)

3. Added the adapter modules in the communication channels.
1.Sender CC Module parameters:
1 localejbs/swift/FileActConversionToSWIFTModule Local Enterprise Bean 1
2 CallSapAdapter Local Enterprise Bean 2
Module confoguration :
1 DetachParameters true
1 KeyId SWIFT
1 Service swift.corp.fa
1 UseLocalSecurity true
2.Receiver CC Module parameters

1 localejbs/swift/FileActConversionToSWIFTModule Local Enterprise Bean 1
2 localejbs/ModuleProcessorExitBean Local Enterprise Bean exit

Module Configuration
1 DetachParameters true
1 KeyId SWIFT
1 Service swift.corp.fa
1 UseLocalSecurity true
1 VerifyBackendSignature true
exit JNDIName deployedAdapters/com.sap.aii.adapter.sftp.ra/shareable/com.sap.aii.adapter.sftp.ra

Here the problem is same module beans is working for FTP receiver adapter with port 21 and the same for SFTP receiver adapter with port 22 is not working,messages are getting holding status in message monitoring.

Checked various blogs related to swift fileact interfaces and also the below link,but no solution.
https://blogs.sap.com/2014/04/14/sap-pi-integration-to-different-banks-using-swiftnet-and-bcm/
Can anyone please help me out who has knowledge on swift interfaces

Note: Holding messages are not related to normal PI Holding messages.

Regards,

Muni

[Former Member]

Thanks all,Issue has been resolved after re-installing the certificate and cleared EOIO messages.

Regards,

Muni

[mate_moricz]

Hi Muni,

Try to you set the VerifyBackendSignature to false and resend messages.

Best regards,
Mate

[Former Member]

HI Mate,

Tried the above option already,but no luck.

Validated the certificates from STRUST in ECC and PI keystore view as well and its looks good.

But no luck 😞

[mate_moricz]

Hi Muni,

Can you share with what error do the messages fail?

Best regards,
Mate

[manoj_khavatkopp]

Hi Muni,

SWIFT modules are not restricted to and adapter you can use the same in FTP/SFTP the module parameters remain same.

Usually you have an option "Maintain Order at Run Time" to deliver the Payment file first and then the parameter file so i would suggest you to check if there are any waiting/failure of messages in PI. http://host:port/MessagingSystem

Br,

Manoj

[Former Member]

HI Manoj,

Thanks for your reply.We already maintained the above option and no waiting/failure messages in PI.

[manoj_khavatkopp]

Just for testing purpose remove the "maintain order" and trigger and see if you the parameter file gets delivered . in your adapter engine filter the message based on sequence id i.e queue name then sort it accordingly on the ascending sequential number . this holding should be of pi failure/waiting only never has such issues in swift integration.

[Former Member]

Hi Manoj,

Tested based on your inputs. .but same holding status error...