Skip to end of metadata
Go to start of metadata

Business Rule

Business rules are used to define a business structure or control/influence a particular aspect of a business.


Components in the Carbon platform add functionality to all WSO2 Carbon-based products. For example, the statistics component enables users to monitor system and service level statistics. A component in the Carbon platform is made up of one or more OSGi bundles, which is the modularization unit in OSGi similar to a JAR file in Java. For example, the statistics component contains two bundles: one is the back-end bundle that collects, summarizes, and stores statistics, and the other is the front-end bundle, which presents the data to the user through a user-friendly interface. This component-based architecture of the WSO2 Carbon platform gives developers flexibility to build efficient and lean products that best suit their unique business needs simply by adding and removing components.

Key Store

The Key Store used to encrypt administrator passwords and other confidential information in Carbon is configured in <PRODUCT_HOME>/repository/conf/carbon.xml file. This keystore configuration can be found under the <security> element of the carbon.xml file.

 Port Offset

The port offset feature allows you to run multiple WSO2 products, multiple instances of a WSO2 product, or multiple WSO2 product clusters on the same server or virtual machine (VM). The port offset defines the number by which all ports defined in the runtime such as the HTTP/S ports will be offset. For example, if the HTTP port is defined as 9763 and the portOffset is 1, the effective HTTP port will be 9764. Therefore, for each additional WSO2 product, instance, or cluster you add to a server, set the port offset to a unique value (the default is 0).

Port offset can be passed to the server during startup as follows:
./wso2server.sh -DportOffset=3

Alternatively, you can set it in the Ports section of <PRODUCT_HOME>/repository/conf/carbon.xml as follows:

Service Group

A service group is a convenient way of deploying multiple services in one service archive file. For more information, see Accessing Service Groups. 


An XML-based, extensible message envelope format, with "bindings" to underlying protocols. The primary protocols are HTTP and HTTPS, although bindings for others, including SMTP and XMPP, have been written.


An XML format allows service interfaces to be described along with the details of their bindings to specific protocols. It is typically used to generate server and client code and for configuration.

WSDL Endpoint

WSDL Endpoint is an endpoint definition based on a specified WSDL document. The WSDL document can be specified either as a URI or as an inlined definition within the configuration.

WSO2 BRS Management Console

WSO2 BRS Management Console is a Web based control panel powered by JSP and AJAX which enables system administrators to interact with a running BRS instance without touching any underlying configuration files. The Management Console allows the users to command and control rule services and much more.

WSO2 Carbon

WSO2 Carbon is the component-based, service oriented platform on top of which the WSO2 products are built. Carbon consists of a collection of OSGi bundles as Carbon components for security, clustering, logging, statistics, management and more. You can build products simply by plugging various Carbon components together using the WSO2 Carbon component manager.

  • No labels