WSO2 Business Process Server v3.1.0 Documentation

##### Overview

- Home
- Release Note
- WS-BPEL Compliance
- License

##### Downloads

- Releases

##### Installation Guide

- Installing WSO2 BPS

##### Quick Start Guide

- Modeling the process
- Deploying the process
- Testing the process

##### User Guide

- Deploying BPEL Processes
- Deploying Human Tasks
- Managing BPEL processes
- Managing BPEL process instances
- QoS for BPEL processes
- Securing BPEL processes
- Invoking secured partner services
- Versioning
- Management API

##### Human Task Guide

- Human Tasks Quick Start Guide
- Deploying HumanTasks
- Managing Tasks
- Developing a Human Task Artifact
- Human Task Management and Configuration
- Human Task Concepts

##### Administrator Guide

- External data sources Configuration
- Registry Configuration
- Events
- Unified Endpoints
- BPEL Extensions
- Transaction Factory Configuration
- Message Exchange Interceptors
- OpenJPA specific properties
- JMS Transport Configuration
- Process Instance Cleanup Tasks
- Process Hydration and Dehydration
- Enabling Peer-to-Peer(P2P) Communication
- Setting up a BPS Cluster

##### Best Practices

- Process Deployment Best Practices

##### Concepts

- Process Versioning
- Process instance events
- Partner links

##### WS-BPEL Extensions

- Activity Failure and Recovery
- Extension Activities and Extensible Assign Operations
- XPath Extensions
- Iterable ForEach
- Flexible Assigns
- BPEL4People Extension

##### Samples

- HelloWorld
- If-Else
- ForEach
- While
- Repeat Until
- Flow and Links
- Pick
- Synchronous and Asynchronous Service Invocations
- Fault Handling
- Split
- XslTransform
- Compensation Handler
- Event Handler

##### Resources

- FAQ
- External Articles
- Library
- Source Code

##### Community

- Forum
- Mailing Lists

##### Project Information

- Issue Tracking

# Quick-Start Guide - Deploying a Process

Once it's done with modeling the BPEL process, it can be deployed via Carbon Studio. Here the Carbon Application Project WS_NumberAdderCarbon which was created at "Modeling business processes".

- Creating WSO2 Business Process Server server
- Deploying the Carbon Application in WSO2 Business Process Server

1. Right-click on the Servers window. (If Server window not appearing in the Eclipse IDE, go to Window -> Show View -> Servers). Then select New -> Server.

2. It will show "New Server" Window. From the List expand the WSO2 folder and Select "WSO2 Carbon 3.2 based server" and (Figure 1). If you need, you can specify the Server name here. Here let's rename it as WSO2 BPS.

   Note: The reason for using Carbon 3.2 based server is BPS 2.1.0 is based on Carbon 3.2.0.

   Figure 1

3. Then have to set the CARBON_HOME. Click browse button and select the WSO2 Business process Server home folder. If you didn't have the WSO2 Business Process Server you can download it from http://wso2.com/products/business-process-server. After selecting the CARBON_HOME Click Finish.

   Note: If you want to configure more setting of the Server like Service port, web Console port etc. click Next and configure them.

   After completing this step 3 the WSO2 Business Process Server is added to Servers List. (See Figure 2)

   Figure 2

4. Let's deploy our carbon application in WSO2 Business Process Server. Click on WS_NumberAdderCarbon project in Project Explore and Drag and drop it on Server. As you see in Figure 3 our Carbon project is added to the WSO2 Business Process Server server.

   Figure 3

5. To run the server right-click on the server and select Start. In Console window, you can see the server Process's log.

6. It will automatically open the WSO2 Business Process Server login page in your default web browser. Login into the server using admin as username and again admin as password.

   Figure 4

7. After the login to the WSO2 Business Process Server, you will redirect to the WSO2 Business Process Server home page. Click on the "processes" under the "Business processes". It will show the currently deployed processes.

   Figure 5

Here you can see the AdderProcess is deployed in WSO2 Business Process Server. The Process ID generated as {"Process NameSpace"} ProcessName-VersionNo