Does EI 7.0.1 contain Business-process server? Cause in MI, Ballerina, SI directories no business-process directory. Where is BPS? I want to configure workflows for API-M.
BPS is not included in EI 7 series and you might have to use EI 6x series if you need it.
Related
we are using WSO2 EI version 6.1.1 and fileconnector 2.0.10
We are trying to use the readSpecifiedLine operation from file connector but it always read the entire file. In this particular case we are trying to read a CSV skipping the header.
<fileconnector.readSpecifiedLines>
<source>{$ctx:sourceFile}</source>
<contentType>text/plain</contentType>
<start>2</start>
<end>3</end>
</fileconnector.readSpecifiedLines>
Did someone was able to use this operation successfully, can't find much on google either. thanks.
This issue is fixed with the version 2.0.12. Please download and redeploy the latest connector [1] from WSO2 store.
[1] https://store.wso2.com/store/assets/esbconnector/details/5d6de1a4-1fa7-434e-863f-95c8533d3df2
This is already a bug. Reported bug Jira Id.
https://wso2.org/jira/browse/ESBCONNECT-271
I have setup a wso2 cep cluster based on https://docs.wso2.com/display/SP400/Fully+Distributed+Deployment for 4.0.0
What extra do i need to do to upgrade to 4.2.0.
There's no huge difference between SP400 and SP420 (with respect to distributed setup). So, please refer to the following documentation[1] on upgrading WSO2 stream processor.
[1] https://docs.wso2.com/display/SP4xx/Upgrading+from+a+Previous+Release.
We are using WSO2 ESB 4.8.1. We have developed a proxy for reading a CSV file and inserting into a database table. File is configured to be MOVED to a history folder after processing. When the file is dropped in the FTP folder, a lock file would be created. It normally will be removed when the processing is over. But now it never gets deleted and the lock file stays as it is in the input folder. We couldn't find out the reason for the same. Please help to solve this issue.
You can also try to set transport.vfs.Locking parameter to disable creation of a .lock file when its processed.
Hope that helps
This is a known error in ESB 4.8.1. There is a patch available from WSO2 support, but that requires having a support contract. You can also use a newer version of the ESB since 4.8.1 is already quite dated, using 4.9 or 5.0 you should not run into these problems anymore.
We have two mule projects in different version 3.0 and 3.7. We want deploy these two projects in single VM (Windows). But I can able to run only one mule runtime not both in single VM(Windows).
Please advise!
Yes, you could run multiple esb instances on a single computer. we have experience doing that one 3.4 version and 3.7 version.
The documentation of the WSO2 Business Activity Monitor version 2.4.0 refers to an Activity Monitoring Toolbox which is not present in my installation (default configuration on 64bit Linux with 64bit JVM v1.6.0_39).
Can I download and install the Activity Monitoring Toolbox from an external location?
Thanks,
Kai
From BAM 2.4.0 release onwards, the previous BAM activity monitoring components have been deprecated. They were replaced by a new implementation of activity search and monitoring with many more added features.
The following artifacts will no longer be shipped:
With BAM distribution: the activity monitoring sample and the activity monitoring toolboxes.
With BAM data agents: activity monitoring data agent which has so far been available under 'Service Data Publishing'
The newer activity search component has its own Jaggery app which can use to query data directly from Cassandra using indices rather than use Hive scripts for summarising data. It will also be shipped with the BAM distribution by default, thereby negating the need for installation of a dedicated toolbox.
The message tracer will replace the activity data publisher for dumping SOAP payloads to BAM. It will also serve in correlating messages based on ID.
Additional information can be found at: http://docs.wso2.org/display/BAM240/Activity+Monitoring+Dashboard
Activity Monitoring toolbox is packed and installed by default in the BAM 2.4.0 where you do not have to install is again. If you want to install it into a BAM 2.3.0 or an older version it will not be easy as the new Activity Monitoring toolbox in BAM 2.4.0 is not only dependent on the deployable artifacts, Stream definition, Analytic script and the dashboard. But it need some other jar files as well which is in the plugins.