Question
Starbucks
US
Last activity: 6 Aug 2024 9:32 EDT
Unable to publish BIX files generated in Pega cloud by different applications to different Remote folders
We have a requirement to send BIX files generated in Pega platfrom to Starbucks SFTP server. Currently we have 2 apps leveraging BIX & requirement is to send the BIX files generated from each app to a different folder in Starbucks SFTP server.
Currently the Service File Activity in 'BIXFTPListener' is final rule & it has option to only add one path in 'BIXFTPRelativeRemotePath' DSS. This cant workout for us as we have multiple apps in Pega cloud platform and we can't leverage one same path for all the applications.
Proposed solution:
Create a new Service File rule & add to OOTB BIX listener to customize considering activity in current service-file is Final. But not sure if this is better way to approach this (or) any other better way to customize this.
We are looking to understand if there is any alternative to solve this?
Pegasystems Inc.
GB
@Sarath Chand L Based on the provided context, one possible solution could be to create separate FTP Server data instances for each application. Each FTP Server data instance can have its own path defined. Then, you can create separate Service Package data instances for each application, each pointing to the respective FTP Server data instance.
Finally, you can create separate File Listener instances for each application, each pointing to the respective Service Package. This way, each application can have its own path for BIX file generation. However, this approach might require additional configuration and testing to ensure it works as expected.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Configuring an FTP listener to access BIX data extracts in Pega Cloud environments
Procedures for BIX extractions in Pega Cloud environments
Configuring the Pega Cloud SFTP service to access BIX extract files
@Sarath Chand L Based on the provided context, one possible solution could be to create separate FTP Server data instances for each application. Each FTP Server data instance can have its own path defined. Then, you can create separate Service Package data instances for each application, each pointing to the respective FTP Server data instance.
Finally, you can create separate File Listener instances for each application, each pointing to the respective Service Package. This way, each application can have its own path for BIX file generation. However, this approach might require additional configuration and testing to ensure it works as expected.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Configuring an FTP listener to access BIX data extracts in Pega Cloud environments
Procedures for BIX extractions in Pega Cloud environments
Configuring the Pega Cloud SFTP service to access BIX extract files
Overview of BIX extractions in Pega Cloud environments