JBI Composite Applications with JavaEE

Most of the JBI composite applications in OpenESB are written using BPEL Service Engine. This is because BPEL allows us to orchestrate various webservices. But what if one wanted to write a simple composite application without using BPEL. Let’s say someone wants to use an EJB WS as part of a larger composite application without invoking as an external webservice. By using Java EE Service Engine we will be bypassing the http layer. The JavaEE SE takes care of invoking EJB webservice from within a composite application. This blog is about creating a composite application only using Java EE SE. We will create an EJB WS and include it in a composite application. 1. Create an EJB Module 2. Name it as JavaEEEJBModule: 3. Right click on the newly created EJB Module and select “New Web Service”   4. When you click “Finish”, a new webservice with a default “hello” operation will be generated: 5. Right click on “Webservices” node and Click on “Generate and Copy WSDL”. 6. Select the conf folder under EJB. 7. Go to the newly generated WSDL, click on Design tab and add PartnerLink Type as shown below: 8. Select the Port type as JavaEEWS 9. Create a new Composite Application project:   10. Name it as JavaEEEJBCA. 11. Open the CASA editor by double clicking on “Service Assembly” under the composite application project 12. Drag the EJB Module into CASA Editor. It should look like this:   13. Right click on the composite application project and select “Clean and Build”. 14. After build succeeds, drag the soap icon from “WSDL Bindings” tab from Palette to...

Working with XSLT Service Engine: Part 2

Project summary: In This project, I am going to do xml to xml transformation using Service Bridge. Please Check working with XSLT Service Engine Part 1 for more details about XSLT Service engine and sample project for Request-Reply service of XSLT service Engine. In this sample project I am going to take customer information like Name , Address , Personal Data in separate node and then merge all above info in single node. Creating Sample Project Using   Service Bridge (xml to xml transformation) In Service Bridge we can apply multiple xml transformation on request xml and then send output back to source. We need to have same number of wsdl operation as number of transformation we want to do. In this project I am going to apply two xml transformations. So I need to create two wsdl as webservice operation to perform transformation. Let’s  say Request1 and response 1 – first operation Request2 and response 2 – second operation Client will send request via request 1 and response 1 will get back to client but over all process will something like this . (Client input xml)Request1–>apply xsl on input to generate request2–>  request 2àappy xsl on request 2 generate response 2–>  response 2 –> apply xsl on response2 to generate response1 –> response 1(client output xml). Create XSLT Module: Please refer to part 1 for details to create XSLT module. Create XSD for request and reply operation <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xml.netbeans.org/schema/CustomerDetails" xmlns:tns="http://xml.netbeans.org/schema/CustomerDetails" elementFormDefault="qualified"> <xsd:complexType name="CustomerName"> <xsd:sequence> <xsd:element name="firstName" type="xsd:string"/> <xsd:element name="lastName" type="xsd:string"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="CustomerAddress"> <xsd:sequence> <xsd:element name="HomeAddress"/> <xsd:element name="OfficeAddress"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="PersonalData"> <xsd:sequence> <xsd:element name="gender" type="xsd:string"/> <xsd:element...

Working With XSLT Service Engine: Part 1

About the XSLT Service Engine The XSLT Service Engine is a Java-based transformation engine that is used to convert XML documents from one data format to another. The XSLT Service Engine makes it easier for users to configure and expose XSL style sheets as web services. Using the XSLT Service Engine requires no special knowledge of XSL, but rather allows any XSL style sheet to be deployed as a JBI service unit. The XSLT Service Engine is not solely responsible for performing transformations. XSL style sheets implement a web service operation (as normally defined in a WSDL). When deployed as JBI service units, these service units correspond to a service endpoint. Each endpoint is activated when the XSLT service unit is deployed. In a sense, the XSLT Service Engine is a container of XSL style sheets, each of which represents a service endpoint in the JBI environment. The following steps highlight the life cycle of a typical message using the XSLT Service Engine: The XSLT service unit is configured with service endpoint information. The service unit is deplopyed, along with the XSL style sheet, to the JBI environment. The XSLT Service Engine compiles the style sheet. A message arrives and the XSLT Service Engine searches for the service endpoint responsible for handling the message. The message is transformed using the service endpoint’s XSL style sheet. A response is sent back via the Normalized Message Router (NMR). XSLT Service Engine Features The XSLT Service Engine supports the following use cases: Request-Reply Service Request-Reply is a standard request-reply scenario. An XML message request is transformed and the result is sent back...

Working with OpenESB WLMSE

Overview Here we will attempt to create simple Application that demonstrate use of WLM Application. Before we begin, quick introduction to WLM is appropriate. WLM stands for Worklist Manager. It allows you to create Web Service Application that require human action/decision (one of pre-defined options) based upon some input data. So, in nutshell, the WLM application can be fed messages (predefined type) and exposes some API’s (can be used to build Web Interface) that allows assigned user’s to see the requests as list of tasks for some actions/decisions. The resulting choice of the user will be sent back as output message (again pre-defined type) to calling service. The service interface is defined using WSDL and the communication is Synchronous. WLM application can be best thought of means to incorporate human step in an automated process. For example, if you need to incorporate human approval step in you BPEL Process, you can achieve this using WLM Application. It also provide features such as Task Escalation, Notification etc. This is what we are going to do in this Helloworld Application. A WLM Application has three components: Please refer to Downloads for required components download Design Time You can use Netbeans (download page) with SOA Modules and create WLM Project type. Using worklist editor, you create task definition wherein the aspects about the task definition is specified. More on this later. Runtime The built project is deployed on Glassfish with JBI Runtime Environment. Project Open-ESB provides a Service Engine called sun-wlm-engine which provide runtime implementation for WLM Projects. Web Application The Users of the Task can log on to Web Console and...

Maven archetype for creating OpenESB Components

This blog shows how to develop OpenESB component project in few steps using maven archetype. New generated projects can be built with OpenESB build process. The project generated using the following maven archetype will be similar to the existing component folder structure and can ONLY be built with OpenESB build process. Following two categories are possible for projects in OpenESB component development. – Plugin project – This project will build with netbeans-soa build process. – Component project – This project will build with ojc-core in openesb-component ====================================== Install Archetypes in Users local repository: ====================================== NOTE: Maven version should be 2.0.9 as same as OpenESB 1 – Checkout Archetype projects from OpenESB git repository: (openesb-componentsmaven-ojc-archeType-v2) maven-archetype-service-engine-v2 maven-archetype-binding-component-v2 maven-archetype-service-engine-plugin-v2 maven-archetype-binding-component-plugin-v2 Archetype of Service Engine ——————————— 1.1) Change directory to maven-archetype-service-engine-v2/ $ mvn clean install Archetype of Binding Component ——————————— 1.2) Change directory to maven-archetype-binding-component-v2/ $ mvn clean install Archetype of Service Engine’s Plugin/Module Project ——————————— 1) Change directory to maven-archetype-service-engine-plugin-v2/ $ mvn clean install Archetype of Binding Component’s Plugin/Module Plugin Project ——————————— 1) Change directory to maven-archetype-binding-component-plugin-v2/ $ mvn clean install ==================Installation complete for all archetype in User’s Local repository============== ================================================= Building Projects from archetypes ================================================= 1) Create new service engine: mvn archetype:generate -DarchetypeGroupId=open-jbi-components -DarchetypeArtifactId=service-engine-ojc-archetype -DarchetypeVersion=2.3.0 -DgroupId=newse -DartifactId=newse –OutPut for above command requires user input [INFO] Scanning for projects… [INFO] Searching repository for plugin with prefix: ‘archetype’. …… [GIVE THE Command line params options as per your wish and openESB configuration. [INFO] Using property: groupId = newse [INFO] Using property: artifactId = newse Define value for property ‘version’: 1.0-SNAPSHOT: [INFO] Using property: package = newse [INFO] Using property: componentName = newse...