I have a scenario to download a file from ADLS Gen2 and then process the data using wso2
I see there is a connector in wso2 but it has only listing, uploading, creating, and deleting options.
Nothing to download files.
Can someone help.
If the Download operation is not available you can consider writing your own Class Mediator to implement the functionality.
Related
Does WSO2 have an Excel connector? It is not visible in WSO2 Connector place. In case it is not available from WSO2, is there any third party connector available?
I understand you can expose an Excel file as a Data Service but that is different from a Connector.
Unfortunately WSO2 does not have an Excel connector. I am also not aware of any third party connectors without having too much context about what you are trying to achieve by means of an Excel connector.
Food for thought, try to think of the Excel file as being a kind of database that stores the information. You then in turn setup a datasource connection to the file using the following link as guidance: https://docs.wso2.com/display/EI611/Exposing+Excel+Data+as+a+Data+Service
After which you can easily define a query for the data in question.
I have another question on WSO2 APIM 2.6.0
I am working in one scenario where I have to store one file which is in json in gov registry. I can do that manually from the dashboard but I am looking for a way to perform that using API or in automated way.
Research done till now
1) Checking on the link which ideally enable WSO2 ESB to maintain a remote registry. But I am unable to get how the registry DB will be shared between the applications (APIM and ESB).
Like, ESB has property where we can store the data in registry directly from proxy or an API and also enables us to retrieve them accordingly.
But how do we do in APIM to store the file with json content.
Any suggestions here.
Thanks
We're evaluating a few WSO2 products for a solution. As part of the requirement we need to deploy the WSO2 analytics car file in DAS(preferably version 3.1.0). When we deploy the car it fails due to an incompatibility in the EsbAnalytics-ExecutionPlan-statistic execution plan file. A closer look inside the file shows that it refers to a custom stream function extension called esbAnalytics, this file is not available inside the car file or in the usual locations such as lib and dropins.
Can some one please share the steps to make the analytics car work in DAS?
If you are going to use ESB analytics features in DAS, you need to install its features first. The ESB analytics extension comes with those features.
Refer to the documentation[1] for the instructions on installing ESB analytics features on DAS 3.1.0.
[1] https://docs.wso2.com/display/DAS310/Working+with+Product+Specific+Analytics+Profiles#618096e7e77848b3abcc5785000d53cc
Now I want to use data mapper mediator in WSO2 ei console, and it requires me to select some Configuration Registry files:
but I don't know how to register these configuration, in the WSO2 EI documentation I could hardly find how to register, while I only found that I can create a ESB solution project and package that to a .car file, then deploy it.
But I don't want to do this, so I need help.
I believe what you're looking for is in this link.
Mapping Configuration: The file, which contains the script file that is used to execute the mapping. You need to create a mapping
configuration file using the Dev Studio-based Tooling plugin, and
store it either in the Configuration Registry or Governance Registry,
to select and upload it from here.
Let me know if it worked or need more help.
I want to compress and decompress files in WSO2 ESB. Is it is possible, if yes please help me to do it.
Thanks.
You can transfer very large ad hoc files with VFS by enabling binary relay in WSO2 ESB. Check this doc on how to enable binary relay builder and expanding formatter. VFS transport documentation and this article will be helpful for your use case.
You can always write a class mediator to decompress the file and read the content.
https://docs.wso2.com/display/ESB481/Writing+a+WSO2+ESB+Mediator