Rule Service plug-in for WSO2 Business Rules Server (BRS) generates the rule configuration file in an Eclipse environment and generates aar/car file to be deployed in the Business Rules Server. This tutorial describes the steps to be taken when creating a rule service project and deploying its deployable artifacts to the WSO2 BRS using the new WSO2 Developer Studio plug-in.
SOA and business rules are key technologies used in most of the software systems to achieve flexibility and adaptability. Therefore ability to use business rules within an SOA environment brings certain advantages to users. This article describes how to use business rules within an SOA environment using WSO2 BRS and WSO2 ESB. Further it elaborates the underline concepts behind business rules integration so that the SOA architects able to determine where to use and how to use business rules within their solutions.
By default all WSO2 products shipped with a self signed certificate. In-order to make products more secure, many users prefer to install a CA signed certificate into the product. This KB describes steps to install a CA signed certificate into WSO2 products.
Complex Event Processing (CEP) systems and Business rule management systems (BRMS) are identified as playing major role in sophisticated systems today and in the future. It will be very useful, if we can use them together when making business decisions. The utmost pattern to integrate these heterogeneous systems is to use Service Oriented Architecture (SOA). This article is describing how it can integrate business rules, complex event processing services and data services together and how to use them effectively with SOA to develop a transaction validation system. You can use this as the sample for your transaction validation system and make it to production level easily.
Service Oriented Architecture (SOA) is a pattern most often used to integrate heterogeneous systems. If business decisions written as rules can be exposed as services, then business rules can also be integrated into SOA systems. The WSO2 Business Rules Server (BRS) can be used to expose business rules as web services, while the WSO2 Business Process Server (BPS) is used to integrate different services and provide composite functionality in a standard manner using Business Process Execution Language (BPEL). This article describes an example of how to integrate business rules with a such SOA system.
Security is one of the key aspects of any software system. Authentication and Authorization are basic security requirement of any software system. In an SOA environment which most of the time is realized using web services, Username Token and HTTP basic authentication can be used to authenticate the users. Then XCMAL policy based authorization provides centralized authorization. Therefore this article describes such a SOA system written using WSO2 Enterprise Service Bus (ESB), further protecting the back end services using mutual authentication.
Service oriented architecture (SOA) is the pattern most often used to integrate heterogeneous systems so, if business decisions written as rules can be exposed as services, then business rules can also be integrated into SOA systems. The WSO2 Business Rules Server (BRS) can be used to expose business rules as web services, while the WSO2 Enterprise Service Bus (ESB) is frequently used to integrate different services and provide composite functionality. This article describes an example of how to integrate business rules with a SOA system.