Creating self-signed SSL certificate

• Generate a private key

$ openssl genrsa -des3 -out server.key 1024

You have to provide pass phrase which incorporated the private key

• Generate Certificate Signing Request (CSR)

$ openssl req -new -key server.key -out server.csr

Enter pass phrase for server.key:

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [AU]:SL

State or Province Name (full name) [Some-State]:Western

Locality Name (eg, city) []:CMB

Organization Name (eg, company) [Internet Widgits Pty Ltd]:WSO2

Organizational Unit Name (eg, section) []:BRS

Common Name (e.g. server FQDN or YOUR name) []:wso2.brs.com

Email Address []:milindap@wso2.com

Please enter the following 'extra' attributes

to be sent with your certificate request

A challenge password []:

An optional company name []:

For the Common Name (CN), you have to provide fully qualified domain name of the server. In above example the expected server url in https://wso2.brs.com/, hence proved the wso2.brs.com as the CN.

• Create self-signed certificate

$ openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

Signature ok

subject=/C=SL/ST=Western/L=CMB/O=WSO2/OU=BRS/CN=wso2.brs.com/emailAddress=milindap@wso2.com

Getting Private key

Enter pass phrase for server.key:

This will create server.crt certificate. 

Humantask Rendering in WSO2 Business Process Server [WSO2 BPS]

Little introduction about WS-Humantask

WS-Humantask is defined to integrate humans into enterprise integration. When task request received by humantask engine, it create instance of the task with received request information. Then assignee or potential owner can claim the task and work on it and complete it. On completion response message is sent to the callback service. That's the most basic usage of WS-Humantask.  

WSO2 Business Process Server (WSO2 BPS) includes humantask engine which compliance with WS-HumanTask Specification Version 1.1 [1].

Humantask Rendering

When humantask instance created it can be presented to its (potential) owners to claim task and perform work using Task Client application. An easily customizable client application (humantask-explorer) with main basic functionalities is packed with WSO2 Business Process Server.  

When user selects interested task, client application should render task allowing user to view information related to task instance. 

WS-Humantask provide container to provide rendering information to Task Client application. And task clients (eg: humantask-explorer) use these information and construct the user interface. The container mentioned above for rendering a task’s information is tasks rendering element.

 

Task rendering details are out of the scope of WS-Humantask. So WSO2 input and output renderings have introduced WSO2 Business Process Server 3.5.0 onwards.

Why we introduced humantask rendering support:

In previous versions of WSO2 BPS did not support task rendering, instead you had two options with the help of HumanTaskClientAPIAdmin adminservice:

1. Build your own client application including task information rendering for each task definition
2. Using humantask client built into management console. In this case you have to package separate .jsp pages to display input, output and response  which display input data, user workspace and create response message.

Above both methods introduce high workload per task definition (in method 2) and unable to implement client applications which support almost any humantasks (client applications are tightly coupled with each humantask definition), which makes adding new task much complicated work. That's why, with new release WSO2 BPS 3.5.0 onwards we introduce task rendering support. 

Syntax:

Description

<renderings>		Within “renderings” element rendering types are listed.
<rendering>	xmlns, type	WSO2 Business Process Server supports two main rendering types: wso2:input and wso2:output The namespace is specified as: xmlns:wso2=”http://wso2.org/ht/schema/renderings/” The type of the rendering is specified by the “type” attribute as follows: If the rendering elements listed under <rendering> are input renderings : type="wso2:input" If the rendering elements listed under <rendering> are output renderings : type="wso2:output"
<wso2:input>		wso2:input rendering type is used to render input information to the task instance in the user interface. Each information is represented by <wso2:element> which list input information that need to display as label / value pairs. Format of rendering input element (<wso2:element>) as follows: <wso2:element id=”[Unique id for the display element]”>    <wso2:label>[Label to display for the input element]</wso2:label>    <wso2:value>[xpath to get the value from the input message / presentationParameter]</wso2:value> </wso2:element> Attributes id - Unique ID for each element Child elements <wso2:label> - Label (or text) to display with the value <wso2:value> - The value to display with the label. This value can be extracted from the input message (by providing xpath) or by presentation parameters. Example 01 : retrieving value by xpath <wso2:element id="custId">   <wso2:label>Customer Identifier</wso2:label>   <wso2:value>/test10:ClaimApprovalData/test10:cust/test10:id</wso2:value> </wso2:element> Example 02 : Set value by presentation parameter defined in the presentationParameters in humantask definition <wso2:element id="fname">   <wso2:label>First Name</wso2:label>   <wso2:value>$firstname$</wso2:value> </wso2:element>
<wso2:output>		wso2:output rendering is used to render user workspace (to generate html form that need to filled by the task assignee) and to populate response message to the callback service when task instance get completed. Each form element is represented by <wso2:element>. Format of the output rendering element () as follows: <wso2:element id="[unique id for each element]">    <wso2:label>[Label to display for the form field]</wso2:label>    <wso2:xpath>[xpath of the element in the output message to be filled with this form field]</wso2:xpath>   <wso2:value type="[string | boolean | Int | double | list]">[comma separated values for list type and boolean type]</wso2:value>   <wso2:default>[default value for above mentioned value element]</wso2:default>* </wso2:element> Attributes id - Unique ID for each form element Child elements <wso2:label> - Label to display for the form field <wso2:xpath> - Xpath of the element in the output response message to be filled with this form field input content <wso2:value type=””> - The “type” attribute is used to define the type of the form field. string : provide textarea int / double : provide number input boolean : provide radio buttons. Texts to display with two radio buttons should provide as comma separated values within value element, with respective to “true” and “false”. list : provide dropdown selection. Texts to display in the dropdown list should provide as comma separated values. <wso2:default> - Can provide default value to display in the form Example 01: <htd:rendering type="wso2:output">   <wso2:outputs>       <wso2:element id="approve">          <wso2:label>Loan Status</wso2:label>              <wso2:xpath>/test10:ClaimApprovalResponse/test10:approved</wso2:xpath>           <wso2:value type="boolean">Approved, Not approved</wso2:value>           <wso2:default>Disapproved</wso2:default>      </wso2:element>      <wso2:element id="loanTypeSelectList">           <wso2:label>Loan Type</wso2:label>           <wso2:xpath>/test10:ClaimApprovalResponse/test10:loanType</wso2:xpath>           <wso2:value type="list">car loan, house loan, development loan, education loan</wso2:value>           <wso2:default>house loan</wso2:default>      </wso2:element>      <wso2:element id="loadDescription">           <wso2:label>Loan Description</wso2:label>           <wso2:xpath>/test10:ClaimApprovalResponse/test10:description</wso2:xpath>           <wso2:value type="string"></wso2:value>           <wso2:default>car loan</wso2:default>      </wso2:element>      <wso2:element id="loanInterestAlteration">           <wso2:label>Loan Interest Alteration</wso2:label>           <wso2:xpath>/test10:ClaimApprovalResponse/test10:interest</wso2:xpath>           <wso2:value type="int"></wso2:value>           <wso2:default>1000</wso2:default>      </wso2:element>   </wso2:outputs> </htd:rendering> Generated form in humantask-explorer will be shown as follows

[1] http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cs-01.html 

Changing port in Tomcat Server

Sometimes we need to run several servers (or several tomcat servers) in same machine specially when developing and testing. In such situations we have to change the default port 8080 of the server. For that follow below simple steps.

1. Open server.xml located in the <TOMCAT_HOME>/conf/ directory using your favorite text editor.

2. Then find Connector element similar to the snipt shown below:

3. The attribute "port" is the port number which server get binded. So you have to change that desired port number.

4. Then save the file and restart the server.

That's all :)

Invoking Fault Sequence for SOAPFaults in WSO2 ESB

In WSO2 Enterprise Service Bus Synapse configuration provides ability to execute set of instruction when some fault occurred within mediation flow by with the help of faultSequence. It's similar catch block to try-catch in JAVA. We can bind faultSequence with ESB proxies, API's etc.

Generally faultSequence get executed for errors, exception in mediation flow, such as trying to process malformed xml, endpoint timeout, any mediation errors, etc. It is not designed to execute  when error response get received. But you can set property to execute faultSequence when a standards soap fault (SOAPFault) response received from an endpoint. It becomes handy in service chaining because we do not need to check and verify for fault response before calling the next endpoint.

You can force to execute faultSequence by setting "FORCE_ERROR_ON_SOAP_FAULT" property to "true"

<property name="FORCE_ERROR_ON_SOAP_FAULT" value="true" scope="default" type="STRING"/>

Sample synapse configuration to depict usage of  FORCE_ERROR_ON_SOAP_FAULT



In above sample simply front echo service which comes by default with WSO2 ESB. If you call "echoProxy" which echo service returns SOAPFault such as sending alphabetical character for echoInt operation, you can see the fault sequence "echoFaultSeq" get executed.

WSO2 DSS for absolute beginners

WSO2 Data Services Server is 100% open source product that can be used to create and deploy data services.

What is a Dataservice?

Most businesses require secure and managed data access across these federated data stores, data service transactions, data transformation and validation.

An organization's data exposed as a service, decoupled from the infrastructure where it is stored, is called data services in service oriented architecture (SOA).

If I explain in most simple way: Data service exposes database or database content or any other data source as a web service. In most simplest explanation is it just wraps database (or table, multiple tables) or any other data source and expose the data as web service in more controlled, meaningful manner. 

Data Services provide a convenient mechanism to configure a Web service interface for data in various data sources such as relational databases, CSV files, Microsoft Excel sheets, Google spreadsheets etc

As an example, let’s say you want expose employee information in the database which employee personal information are in emplyeeInfo table and work related information is in another table called employeeWork table. And think you want to expose those information as a web service when requester sends the employee id and the service returns employee personal information with his work performance information. Simply you can create web service using WSO2 DSS by wrapping the SQL query to retrieve that information and present in the response. 

The beauty with DSS is, it handle all dirty work such as creating database connection, database connection pool handling, executing SQL queries, mapping resultant data to the response, etc. which is an unusual overhead to for development. With WSO2 DSS it just simply a web service call, so developers can more concentrate on the business logic / use case.

You can get more feeling about DSS by following  

Generating simple data service using WSO2 DSS Generate wizard

Now we will try out generate data service for given database table. In generate it will create data service with CRUD operations for the table.

Refer https://docs.wso2.com/display/DSS322/Installing+the+Product for installation instructions and refer https://docs.wso2.com/display/DSS322/Running+the+Product for running product instructions.

1. After starting the product and then login to the management console (default username: admin password: admin)
2. First we have to first define data source

NOTE : before creating datasource you have to copy database jdbc driver relevant to your database to <PRODUCT_HOME>/repository/components/lib.

1. Go to Configure tab → Data Sources
2. Will get list of data sources currently configured as follows

3. Click “Add Data Source” and provide information related to the database as follows:

Click Test Connection to verify provided information

Can provide data source connection pool parameters by expanding “Data Source Configuration Parameters” (refer: https://docs.wso2.com/display/DSS322/Configuring+the+Datasource+Connection+Pool+Parameters )

Click save when finished.

3. Now we can generate dataservice
1. Go to Main → Click “Generate” under Data Service
2. Select previously created Data Source from the drop down and give the database name

NOTE : For the “Database name”, you have to give the actual database (schema) name. Most of the time people get confused with this. In this case “DSS_DB” which created with the command “create database DSS_DB;”

Then click “Next”

3. You will get list of all available tables in the database as shown below. You can to select tables which need to expose as data service and click “Next”

4. In “Service Generation” section you have to provide Data Service Namespace and the Data Service Name. And select whether you need single service with CRUD operation for all the tables or multiple services per table (service per table)

4. After click Next you will get notice that service deployed successfully.

4. Now you have finished creating data service. If you navigate to “List” under Services in Main tab you will find created data service. You can tryout it by clicking Try this service.