WSO2 ESB 4.8.1 support for FileConnector V2

WSO2 ESB File connector version2 introduces the atomic operation related to the file system and allows you to easily manipulate files based on your requirement. The file streaming functionality using Apache Commons I/O lets you copy large files and will reduce the file transfer time between the two file systems resulting in a significant improvement in performance that can be utilised in file operations.

Analytics Event Publisher for WSO2 CEP

WSO2 Complex Event Processor (CEP) is a lightweight, easy-to-use, open source Complex Event Processing server (CEP). It identifies the most meaningful events within the event cloud, analyzes their impact, and acts on them in real-time. Event publishers publish events to external systems via various transport protocols. and store data to databases for future analysis. Like the event receivers, this component also has different adapter implementations.

Stream Definitions for wso2 complex event processor

An event is a unit of data, and an event stream is a sequence of events of a particular type. The type of events can be defined as an event stream definition. so different stream definitions are required to be used to store several data streams into the same column family, different stream versions should be used with the same stream name corresponding to the column family.

Use siddhi Try it for Experimentation

This blog post explains how to use Siddhi Try It tool which comes with WSO2 CEP 4.2.0. The Siddhi Try It is a tool used for experimentation of event sequences through Siddhi Query Language (SiddhiQL) statements in real time basis. You can define an execution plan to store the event processing logic and input an event stream to test the Siddhi query processing functionality.

Federated Authenticator in WSO2 Identity Server 5.1.0

An authenticator allows you to authenticate the user using third party authentication systems such as LinkedIn, Clef and Foursquare. You can configure the authenticators for your identity provider to reach out to third party authentication systems to authenticate a user who logs in to your application. For example, if you configure LinkedIn authenticator as your authenticator in WSO2 Identity Server, you can authenticate a user of your application using LinkedIn authentication. You can also do the authentication with multiple third party authentication systems with a single authentication request called multifactor authentication .

Pass Dynamic Values through Class Mediator in ESB Connector methods

In this post, let's discuss how we can pass a dynamic number of arguments  to connector methods, Normally we work with pre-defined parameters in connector  but here let's see how we can pass dynamic parameters with dynamic value and name and how we can use inside the connector method.

There are two types of actions we can do to get dynamic parameters. First one is set some key values and get the values start with that key value another method is through some pre-defined keywords.

Git for Team Projects

In this post, I'm gonna explain how to use Git for our personal projects and contribute to others projects most importantly team works.  We assume that every reader knows about Git before this post. Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.  Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.

WSO2 Identity Server Dropbox Authenticator

Each authenticator provides you a way to authenticate the user using specific external authentication system. For example if you want to authenticate a user who logs into your application using Dropbox authenticator, you need to configure the Dropbox authenticator for your identity provider .The Dropbox authenticator allows you to authenticate user using Dropbox through WSO2 IS. 

Run Integration Test with WSO2 ESB EJB2 Connector and Jboss 5.1

As we discussed earlier EJB2 connector is a tool to make calls between remote EJB2.X objects and wso2 ESB. there are two type of calls we can call.Stateless and stateful where stateless is a one time call and stateful maintain a state between remote object and client. Integration Test for EJB2.X connector written based on Jboss 5.1 server so there are some pre configuration we need to  set before we run the integration test.

in this blog lets see how to configure ESB before run the test and what are the libraries we need to add to ESB and Test Client. Integration test is very important to check the stability of connector(to validate the methods).

WSO2 ESB EJB 2.x Connector

Enterprise JavaBeans is an architecture for transactional, component-based distributed computing. The specification for EJBs lays out not just the format of a bean itself, but also a set of services that must be provided by the container in which the bean runs. This makes EJBs a powerful development methodology for distributed application development. Neither the bean developer nor the client application programmer needs to be concerned with service details such as transaction support, security, remote object access, and many other complicated and error-prone issues. These are provided transparently for the developers by the EJB server and container.

Writing WSO2 ESB Connector Integration Test

We assume that readers have basic knowledge about TestNG and Connector. If not please get the knowledge about connector development from here before read this post. In this post we are analyzing how we can implement a connector integration test. Integration test is very important to evaluate the effectiveness of the connector functions. This post will focus on integration test based on Hello World Sample. 

Getting Started with Simple wso2 ESB EJB Mediator Sample

The EJB mediator calls an external Enterprise JavaBean(EJB) and stores the result in the message payload or in a message context property. Currently, this mediator supports EJB3 Stateless Session Beans and Stateful Session Beans.

WSO2 ESB EJB Mediator

The EJB mediator calls an external Enterprise JavaBean(EJB) and stores the result in the message payload or in a message context property. Currently, this mediator supports EJB3 Stateless Session Beans and Stateful Session Beans.

Getting Started with Simple Remote EJB 3.X Server Sample

This sample will give you a simple working experience with EJB client server . here I’m using netbeans as IDE and JBoss 5.1 as my EJB Container. and I created seperate client for Stateful an Stateless EJB sessions  in order to make easy the development .We'll create a ejb module project named EJBTestServer.

JAVA Remote Method Invocation (RMI)

Remote method invocation allows applications to call object methods located remotely, sharing resources and processing load across systems. Unlike other systems for remote execution which require that only simple data types or defined structures be passed to and from methods, RMI allows any Java object type to be used - even if the client or server has never encountered it before. RMI allows both client and server to dynamically load new object types as required.

WSO2 ESB Feed Connector

Atom is the name of an XML-based Web content and metadata syndication format, and an application-level protocol for publishing and editing Web resources belonging to periodically updated websites. All Atom feeds must be well-formed XML documents, and are identified with the application/atom+xml media type.

Getting Started with Simple Apache Abdera Server

Apache Abdera provides an implementation of the IETF Atom Syndication Format and Atom Publishing Protocol standards (RFC's 4287 and 5023). In this blog we're going to walk through how to build an Atom Publishing Protocol service server sample using Abdera's concepts of Providers and Collection Adapters. If you remember your AtomPub basics, you'll recall that AtomPub services are organized in a hierarchical way such that we have:

Getting Started with Simple WSO2 ESB Custom Inbound Endpoint

WSO2 ESB supports several inbound endpoints, but there can be scenarios that require functionality not provided by the existing inbound endpoints. For example, you might need an inbound endpoint to connect to a certain back-end server or vendor specific protocol.

Getting Started with Simple WSO2 ESB Connectors

A WSO2 connector allows you to interact with a third-party product's functionality and data from your ESB message flow, enabling you to connect to and interact with the APIs of services such as Twitter, Salesforce, and JIRA. This means that if you have enabled the Twitter and Google Spreadsheet connectors in your ESB instance,

Development challanges

Error-1

java.lang.ClassFormatError: Illegal local variable table start_pc 39 in method org.apache.synapse.transport.passthru.PassThroughHttpSender.sendUsingOutputStream(Lorg/apache/axis2/context/MessageContext;)V

java.lang.ClassFormatError: Illegal local variable table length 81 in method org.apache.synapse.transport.passthru.PassThroughHttpSender.maintenanceShutdown(J)V

Solution
adding the JVM arg -XX:-UseSplitVerifier(in wso2server.sh/bat)
Ex:-     $JAVACMD \
    -Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
    -Xms256m -Xmx1024m -XX:MaxPermSize=256m \
    -XX:-UseSplitVerifier \

###############################################

Error-1
When we run load test on ESB server by default it will only allow 20 concurrent threads to send out so if we increase the size of the thread in synapse properties(//repository/conf/synapse.properties) we may encounter the error.

[CodeBlob (0x00007f3fc1051e10)]
Framesize: 0
BufferBlob (0x00007f3fc1051e10) used for StubRoutines (2)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (sharedRuntime.cpp:834), pid=4948, tid=139907131430656
#  fatal error: exception happened outside interpreter, nmethods and vtable stubs at pc 0x00007f3fc105436f
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode linux-amd64 compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/rajjaz/Documents/ESB/wso2esb-5.0.0-RC/hs_err_pid4948.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Aborted (core dumped)


Solution

Increase the number based on the machine capacity