This article provides answers to most commonly asked questions regarding WSO2 Business Process Server, its underlying Carbon framework, BPS deployment and configuration.
WSO2 Business Process Server (BPS) is an easy-to-use Open Source Business Process Server that executes business processes written following WS-BPEL standard. It serves as the business process management and hosting environment for your SOA.
.It is released under Apache Software License Version 2.0.
WSO2 Business Process Server is distributed completely free and all the distribution packs can be downloaded from the WSO2 Oxygen Tank. WSO2 Business Process Server can be downloaded as a binary distribution or a source distribution and if required one can even checkout the complete source code from the WSO2 SVN repository.
We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology. For more details and to take advantage of this unique opportunity please visit WSO2 Support.
Not only you are allowed, but it is encouraged. You can start by subscribing to carbon-dev@wso2.org and architecture@wso2.org mailing lists. Feel free to provide ideas, feed back and help us make our code better. You can also report bugs on our issue tracker and you can even submit patches. Visit WSO2 Oxygen Tank for more information about our mailig lists.
WSO2 carbon-studio is recommended.
Yes. You can debug a BPEL process using the Event Table in the Instance View of Management Console or using the Message Tracer.
Get the BPEL feature from the P2 repository and install it using the Carbon feature configuration functionality.
The deploy.xml file acts as the deployment descriptor for a BPEL package. It maps configuration information such as partner links, WSDL service, port, etc for processes in a BPEL archive.
The BPEL Process Configurations represents activities carried out within a business process written using WS-BPEL. The Basic Activities includes; Invoke, Receive, Reply, Assign, Compensate, CompensateScope, Exit, Throw, Empty, Rethrow, Wait. The Structured Activities includes; Flow, ForEach, If, Pick, RepeatUntil, Scope, Sequence, While.
Add log4j.logger.org.wso2.carbon.bpel.messagetrace=TRACE to log4j.properties file (located at WSO2 Business Process Server-3.1.0/repository/conf/log4j.properties) and set the Carbon log file threshold to trace. i.e. log4j.appender.CARBON_LOGFILE.threshold=TRACE Now re-start the BPS server and send a single request to the BPEL process and find the log file: BPS_HOME/repository/logs/wso2carbon.log
Apply either "Basic Security Scenarios" or "Advanced Security Scenarios" based on your preference.
Yes. WSO2 Business Process Server exposes business processes written in BPEL as web services. These services can be executed by a proxy service hosted in WSO2 Enterprise Service Bus (ESB) just like any other web service.
Yes. Create a proxy service which sends out emails using WSO2 ESB and call this proxy service within the BPEL process using "invoke" activity
Change the offSet value in the carbon.xml in each instance to different values.
Yes WSO2 Business Process Server supports clustering.
WS-BPEL 2.0 does not address human interactions directly. The BPEL4People is an extension to WS-BPEL 2.0 and is used to model human interactions within a BPEL process through the use of an extension activity.
WSO2 Business Process Server is built on top of WSO2 Carbon, an OSGi based components framework for SOA. It is powered by Apache ODE as the underlying BPEL engine. Java is the primary programming language used to develop WSO2 Business Process Server.
You can deploy any third party jar into the repository/components/lib directory. You also need to restart the server for the newly deployed jars to be picked up by the server runtime. WSO2 Business Process Server will convert any jar files copied into the above location into OSGi bundles. These OSGi bundles are placed in the repository/components/dropins directory.
Yes, you can extend the management console easily by writing a custom UI component.
Yes you can. You can connect WSO2 Business Process Server with any external user store implementation. The user store could be LDAP based, JDBC based or a custom developed user store. Please refer user core documentation for more details.
Yes you can. Login to the BPS management console and browse to the Feature Manager. Open the 'Installed Features' tab. From here you can uninstall any unwanted features.
Yes, WSO2 Business Process Server comes with a UI framework which supports i18n (internationalization) which lets you to use a language of your choice for the management console.
Hot deployment/hot update may take the system to inconsistent states if the updates are not properly coordinated. Therefore it is recommended to turn hot deployment and hot update off for production deployments.
WSO2 Business Process Server integrates with WSO2 Governance Registry out of the box. Refer the administrator guide for the necessary steps involved in remote registry configuration.
It is tested on JDK 1.6. Sun JDK and IBM JDK are supported.
When deploying you can remove, $BPS_HOME/samples and $BPS_HOME/repository/samples from the standard distribution.
You can uninstall all the UI components using the feature manager which will disable the management console.
It has been tested on the following app servers. JBoss, Weblogic, Websphere and Tomcat.
WSO2 Business Process Server ships with an embedded H2 database. However any database management system can be plugged into the BPS via JDBC. Database for BPEL engine persistence storage can be configured via datasources.properties file in repository/conf directory. Registry and user management related database configurations are available in repository/conf/registry.xml and repository/conf/user-mgt.xml files. WSO2 Business Process Server has been tested with MySQL, Oracle, MSSQL and PostgreSQL databases.
The memory allocation setting are in the wso2server.sh. The user can change the memory allocation settings by changing the following configuration.
-Xms256m -Xmx512m -XX:MaxPermSize=128m