newbie on ESB and BRS here.
Below message was displayed in WSO2 download page for BRS:
IMPORTANT NOTICE
The WSO2 Business Rules Server (WSO2 BRS) was created as a mechanism to host standalone business rules services. We no longer believe it is well suited for others to use directly, and as such it will no longer be available for download.
We currently have the ability to execute business rules within WSO2 ESB, and we encourage you to continue to use the WSO2 ESB to create business rules services.
If you are currently using WSO2 BRS as a standalone product please contact us
We will of course support it as needed or help you migrate to the right higher level product.
How can I implement this example I saw on youtube https://www.youtube.com/watch?v=O-D2Hgdrzs8 using WSO2 ESB because BRS is no longer promoted.
I don't know also if I got it right, but my understanding is that the mediators like rule mediator is the best fit solution to implement business rules in ESB now. Am I right?
I hope you can help me how to translate the video tutorial from using BRS to ESB in WSO2, or at least if you know some good sites to read and use as reference, then I am happy to visit them as well.
Thank you in advance.
Related
I have already read many documentations of WSO2, there are some products of WSO2 such as: Enterprise Integration (EI), API Management (APIM), Identity Access Management (IS), Analytics Stream Processing (SP). I can understand the functions of IS and SP.
1. But I dont know what are differences between EI and APIM?
2. When can we use EI? When can we use APIM?
3. Can we merge WSO2 EI and APIM and IS and SP Products to execute all of them on one server?
Sorry for many questions, but I am really confuse in these matters, please give me advice.
WSO2 EI can be used to integrate different systems, orchestrate and then expose as new services/APIs.
WSO2 APIM can be used to manage those services/APIs. You can manage security, rate limiting, CORS, etc. and can see analytics of API usage etc. too. For APIM analytics, there is a customized version of SP which you can download separately.
You can't run all 4 as a single server. Those are 4 runtimes, so you have to start them separately.
we are evaluating to add an esb to our organization to solve several problems.
One of these problems is this: we need to add an user that must be created only on a custom hrm software to Domino Mail.
Before starting we would like to understand if this thing is possible using WSO2 ESB.
In addition to this is very important for us to understand there is a connector/adapter ready or we need to do custom Lotus script programming on Domino side.
Thanks in advance,
Mario
You can find all the available WSO2 ESB connectors and other connectors in WSO2 Store. It looks like there is no connector for Lotus Domino at the moment.
While evaluating various ESB's, I came across Apache Synapse & WSO2. In WSO2 it's mentioned that WSO2 completely uses Synapse and built on top of it.
However I am not still clear what additional features does WSO2 offer over Synapse? (Apart from commercial support).
One difference I could see is the web UI to manage proxy definitions, sequences creation etc. Are there any other features which WSO2 provides over Synapse? Also please share if there are any guidelines to choose between Synpase & WSO2
I just wanted to be sure why I am going to WSO2 over Synapse.
Thanks,
Harish
WSO2 ESB offer many great features on top of synapse. I am listing few here.
Graphical management console to create/manage/monitor proxies/APIs and services.
Support for many transports [1].
Statistics, logging and auditing support
Support for many content types
And industry accepted proven performance.
List can go on and on. Hence I am referring you to WSO2 documentation on features[2]. Hope you can get some idea from there.
[1] https://docs.wso2.com/display/ESB481/ESB+Transports
[2] https://docs.wso2.com/display/ESB481/Features
Can I have source code of any running application/Test case build using (DSS,ESB,IS,AS, etc).
I am able to understand the these servers separately but not able to deliver any project using these servers collectively.
Do not have clue to use all these servers collectively best way and din't get any video, article or samples using all there in one application.
I Have already posted this question in StackOverflow, but din't get any response.
Please help me to achieve the same so that the greatness of WSO2, I can show to some of my colleague and We can go long with WSO2.
You can try the Retail Bankning Sample with WSO2 Developer Studio and bunch of other WSO2 Servers such as WSO2 ESB, WSO2 BPS, WSO2 DSS, WSO2 AS etc [1]. This sample was demonstrated on this webinar as well [2]. Source code for the Webinar is in [3].
[1]. https://docs.wso2.com/display/DVS370/Retail+Banking+Sample
[2]. http://www.youtube.com/watch?v=4hdq1Qq-XSc
[3]. https://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/docs/src/main/resources/samples/banking-sample/Webinar/
Hope this helps!
I am working on WSO2 ESB 4.0.3 on MAC OS X Lion (10.7.4)
I would like to know what are the best practices for development for WSO2 ESB 4.0.3.
Currently I am using Data Services Feature in it and existing tomcat application, which we are trying to port to WSO2 ESB, does the SQL query in 2-3 seconds where as WSO2 ESB 4.0.3 with Data Services feature taking around 16-17 secodns.
I would be thankful if some body can let me know best practices for WSO2 and in perticular XSLT transformation.
Hoping for answer.
thanks
Hi Prabath
Here is how my environment is
I am using WSO2 ESB 4.0.3 with Data Services Feature 3.2.2. Proxy service front ends the DS service. Data sources are defined as carbon data sources in datasources.properties.
I tried to run the same service in the WSO2 Data Services Server 2.6.3 and the performance is comparable to what existing tomcat application does but the ESB 4.0.3 with Data Services Feature 3.2.2 takes 8 times more time than tomcat application. Looks like XSLT is not a issue as I thought earlier.
I have all the error handling & input validation in the proxy service which calls this DS.
Also I tried changing it to local for the transport but still same performance issue. Also I have to make sure the format of the forwarded XML is SOAP 12 in the end point definition otherwise proxy service does not forward with local transport.
Can you please suggest so that I can use WSO2 ESB with Data Services Feature 3.2.2 and get comparable performance?
Help really appreciated.
thanks
Abhijit
Hi Prabath
Thanks for reply.
Proxy service validation and transformation is not a problem. Looking at the logs it looks like Data Service deployed in ESB with Data Services feature is taking 8 times more time than the tomcat application. So it is Data Services Feature which is problem I believe and not the proxy service.
Even if we remove the proxy service where you will do the input validations and error handling?
Please let me know.
thanks
Abhijit
Abhijit,
I'm not quite clear of whether this problem is related to executing SQL using dbReport/dbLookup mediators against doing the same thing having data services features installed in ESB OR transforming responses using XSLT at the ESB layer against doing it at the DSS layer.
If it's the former, then you should be able to effectively use the db mediator pair (namely dbLookup and dbreport) to execute simple SQL queries such as SELECT, INSERT, UPDATE, DELETE, etc. However, it is not recommended to do use those mediators to do much complex queries such as stored procedures with "OUT and INOUT" parameters etc as WSO2 DSS is specifically designed to serve any sort of complex queries like that. However, this (using data services) comes at the cost of network latency. Because, you're invoking a data service endpoint through the network which obviously adds the network latency to the end-to-end time taken to get your task done. However, if you're using Data Services features installed in the WSO2 ESB, you always have the option of using "local" transport instead of "http/https" which does an in-JVM call and thus would not dispatch the request over the network.
If this is related to the later, meaning, if you refer to the XSLT transformations, I believe there's no such hard and fast rules in doing this and this would completely depend on your requirements and the usecase. For example, if you're only using WSO2 DSS and want to get some request transformed into a particular format that is expected by the client side, it would only be enough for you to get it done at the WSO2 DSS layer. Because, dispatching it into ESB ONLY for the sake of getting the XSLT transformation done, would add an additional unwanted overhead to the end-to-end completion time of your task. On the other hand, if you're doing this as a part of a configuration flow at the ESB side, then it's perfectly okay to use something like XSLT mediator inside the flow itself.
Hope this helps!
Regards.
Prabath
I hope Prabath already gave the answer to your question.
However, it is not recommended to do use those mediators to do much complex queries such as stored procedures with "OUT and INOUT" parameters etc as WSO2 DSS is specifically designed to serve any sort of complex queries like that. However, this (using data services) comes at the cost of network latency. Because, you're invoking a data service endpoint through the network which obviously adds the network latency to the end-to-end time taken to get your task done. However, if you're using Data Services features installed in the WSO2 ESB, you always have the option of using "local" transport instead of "http/https" which does an in-JVM call and thus would not dispatch the request over the network.