Question
Not able to access the BIX cloud location through FTP in V7.3.1
Hi,
Did anyone tried to access BIX extracted files from the cloud location through Connect-FTP.
we are trying to FTP the Extracted zip file from cloud location to remote location.
Configurations from our end are good. but still getting the below errors:
| Step Number | 1 |
| Exception Trace | com.pega.pegarules.pub.PRRuntimeException: FTP Connection failed |
| Step Status | FAIL |
| Step Status Info | ** File does not exist or cannot be read: /local/pega-work/sync-data/bix/BIX_USAA_Enterprise_Complaints_Work_Cases_1.zip |
***Moderator Edit: Vidyaranjan | Updated Categories***
Thank you Nick.
Yes, this is Pega Cloud.
As of now, we are just running the extract rule. And we are trying to FTP that file to Remote location by using Connect-FTP.
FTP Server - shows Good and Success.
Extracted .zip files are in cloud location. We are providing the local path as "/local/pega-work/sync-data/bix/xxx.zip" in Connect-FTP method.
we are unable to trace the events. could you please suggest some debugs to enable to get the logs related to BIX , FTP, File Listener
Thank you!
Enabling debug on the following classes / packages will produce additional output related to the file listener:
com.pega.pegarules.integration.engine.internal.services.listener
com.pega.pegarules.storage
com.pega.pegarules.integration.engine.internal.services.file.FileListener
It sounds like the extract is completing successfully, so I don't know if that needs debug needs to be enabled for it, but this class is typically what you want to enable debug on for BIX:
com.pega.pegarules.data.internal.access.ExtractImpl
If you're running the extract manually, the extract will produce output on the Web node you are on (as opposed to the BIX or UTIL node where it should be running). It's possible that could be related to the issue, so keep that in mind when investigating. You may want to enter an SR for this as well, as troubleshooting these types of issues can be difficult. If you enter an SR, please update this post with the SR number for tracking purposes.
Thank you Nick. Thank you for your reply.
Raised SR and after our long analysis it seems there is a problem with File Listener which is not processing the files after extraction.
we Enabled all the Debuggers you suggested, but could not find any thing. we are not getting any logs logged.
Thank you
Is the extract running via an agent?
If so, is that agent configured to only run on the BIX node? (assuming this is the Pega Cloud)
If the agent is running on a non-bix node, the output will be generated on the wrong node.
If that doesn't appear to be the issue, we'd probably want to have a closer look at the logs and maybe enable some debug. An SR would be appropriate for investigating further. (If you open one, be sure to update this post with it)