About Me
Facebook
Facebook
Linked In
Linked In
Twitter
Twitter
YouTube
YouTube
Google +
Google +

Thursday, April 16, 2015

JBoss Maven Configuration

Introduction

What is Maven

Maven was originally started as an attempt to simplify the build processes in the Jakarta Turbine project. There were several projects each with their own Ant build files that were all slightly different and JARs were checked into CVS. We wanted a standard way to build the projects, a clear definition of what the project consisted of, an easy way to publish project information and a way to share JARs across several projects.

Configuration

JAVA_HOME System Variable

Right click on My Computer à Select Advanced system settings à select Environment variables under advanced tab.

Under system variables click on New àgive variable name as JAVA_HOME and variable value as C:\Program Files\Java\jdk1.7.0_55(JDK  path). 
C:\Program Files\Java\jdk1.7.0_55(JDK  path).
Similarly create a system variable ‘M2_HOME’ and value as D:\Fuse ESB\apache-maven-3.3.1(Maven folder).
Similarly create a system variable ‘Path’ and value as D:\Fuse ESB\apache-maven-3.3.1(Maven folder).

Download and update the Maven configuration.

  • Download maven from http://maven.apache.org/download.cgi
  • Install maven to D:\Fuse ESB\apache-maven-3.3.1 
  • Create maven repo folder e.g. D:\ Fuse ESB\Maven_Repo
  • Edit the global and personal settings.xml file to add the config you want e.g. change personal repo location (TODO: understand whats common config looks like) 
  • Add following repository tag to D:\Fuse ESB\apache-maven-3.3.1\conf\settings.xml:

<localRepository>D:\Fuse ESB\Maven_Repo</localRepository>This is for pointing Maven repository. All maven related jar’s will be downloaded into this folder.

Add profiles to Maven configuration.

Open JBoss Developer Studio, goto Window à Preferences à Expand Maven à select User Setting. Browse the user settings file as ‘D:\Fuse ESB\apache-maven-3.3.1\conf\settings.xml’
Then click on update settings, click on Apply and Ok.
Goto Window à Preferences à Expand JBoss Tools à select JBoss Maven Integration à Click on Configure Maven Repositories.

Click on Add Repository and enter the following details as shown below.
Profile ID: jboss-ga-repository
ID: jboss-ga-repository
Name: jboss-ga-repository
URL: http://maven.repository.redhat.com/techpreview/all/



Similarly add the following details too.Profile ID: jboss-earlyaccess-repository
ID: jboss-earlyaccess-repository
Name: jboss-earlyaccess-repository
URL: http://maven.repository.redhat.com/earlyaccess/all/
Now click on Ok and Click on Finish. There will be conformation pop up will be shown to update Settings.xml file and click on yes.
Create a Sample Fuse Project and and Right click on project select Run As à Maven Install.
Now Maven repository will be downloaded into repository folder and project will build successfully with Maven configuration, we can see the following logs in console.

continue reading

Tuesday, April 14, 2015

WebSphere Message Broker Interview Questions

1.What exactly do you understand by message broker?


A Message Broker is an intermediary program that helps communicating multiple system to each other by transforming, routing the messages in the way they need.

continue reading

Thursday, April 9, 2015

Appian BPM Software - BPM Suite Overview

Business Process Management (BPM) is defined as the discipline of managing processes to continually improve agility and business performance outcomes.
BPM Suite
As the value of process improvement in business became more understood, the BPM suite emerged with comprehensive, integrated capabilities to help organizations achieve their business goals and solve unique challenges more quickly at a lower total cost. A more cohesive approach to BPM than stand-alone technologies, the advanced BPM suite provides process management capabilities needed to achieve the optimal state of seamless, cross-functional process alignment.
There are ten critical components of a BPM suite:
Process – Simple web-based modeling using BPMN and SOA methodologies for rapid development and automation of business processes.
Rules – Automate, enforce and audit policies and practices of a dynamic rule driven process application.
Design – Rich and easy-to-use creation tools to quickly build simple interfaces.
Forms creation – Forms creator should allow designers to create interactive forms for users.
Analytics – Ability to track real-time process performance, create rich reporting dashboards, identify process bottlenecks, and optimize process efficiency flow.
Mobile – Ability to always be connected to important processes and tasks, regardless of time, place, or device.
Content – Integrated document and content management to store, secure, version, search and manage enterprise content for use in business processes.
Collaboration – Instant, continuous connections between people, processes, and information keeps the workforce aware, engaged, and working together toward objectives.
Data Integration and Access – Converge data from across all enterprise systems to provide complete information on any topic, available in a single location.
SOA and Integration – Use standard SOA development to build a repository of reusable services to accelerate BPM deployment to address many challenges.
At a minimum, BPM software must address the four core elements of process-based application development:
Design, Execute, Manage, and Optimize.
Design
• Simple Business Process Modeling Notation (BPMN) to create graphical Process Models
• Rules Engine to create required business rules
• Intuitive designer for forms and application interfaces
Execute
• Process automation with enterprise-level scalability
• Comprehensive Web Services orchestration
• Integration with other enterprise systems
Manage
              • Task and queue management
• Real-time reporting and status alerts
• In-flight process modification capabilities, enabling managers to handle exceptions

Optimize
Ø  Business Activity Monitoring (BAM) capabilities
Ø  Aggregate performance analysis.
Ø  Key Performance Indicators and SLA reporting
Design Processes
*      BPMN process solutions, rapidly built through drag-and-drop functionality
*      Native process repository captures and stores process models for rapid reuse
*      Business rules to define your critical policies and procedures
*      Forms interface design enables fast creation of task forms and dashboards
*      Complex event processing for tracking, analyzing, and responding to business events
Execute with Ease
*      Instant deployment of your newly built solutions on a scalable, flexible platform
*      Out-of-the-box Integration with diverse systems
*      Built-in enterprise mobility delivers responsive. Mobile user experiences with no extra work
*      Appian Records unify all data from across systems and processes in a single location
*      Flexible, portable implementation based on your specific needs: Cloud, on-premise, or both
Manage Tasks
*      Real-time management tools monitor in-flight processes, re-assign tasks, and view performance
*      Task management increases worker efficiency and reduces costs
*      Real-time visibility provides granular tracking of process and task progress
*      Skills-based routing ensures the right worker gets the right task
*      Social collaboration across people, processes, and systems drives awareness
Continually Optimize
*      Continuous process improvement constantly evolves business performance
*      Aggregated process history analysis identifies bottlenecks and inefficiencies
*      Predictive analytics leverage past performance and trends to create self-optimizing processes
*      Dynamic reporting provides real-time visibility into business operations
*      Appian Labs applies Appian BPM expertise to your process design and performance

continue reading

Wednesday, April 1, 2015

Developing Hello World Mule Flow in Mule ESB

Introduction

This application demonstrates a simple HTTP request-response activity. Mule responds to end user calls submitted via Web browser with a message that reads, "Hello World". This example was designed to demonstrate the ability of a Mule application to interact with an end user via an HTTP request. Its goal is to introduce users to Mule by illustrating very simple functionality.

Overview

The Hello World example consists of one simple Mule flow. This flow accepts an HTTP request, sets a static payload on the message, then returns a response to the end user. 

The request-response inbound HTTP endpoint receives requests the end user submits to the Web service. Because it has a request-response message exchange pattern, this HTTP endpoint is responsible for both receiving and returning messages. The descriptive notes included in the configuration of the endpoint helps other developers understand the actions the element performs in the context of the application.

Implementation

We need to complete the following procedure to create, then run this example in your own instance of Anypoint Studio. We can create template applications straight out of the box in Anypoint Studio and tweak the configurations of the use case-based templates to create your own customized applications in Mule.

Open Anypoint Studio, Right click and sect new à Mule Project.

Enter the project name as ‘EAI_HelloWorldMuleProject’ select the Runtime as ‘Mule Server 3.5.0 CE’ then click on next.
Change the project name as ‘EAI_HelloWorldMuleProjec’ as it shows small letters in this step then click on finish.
Open EAI_HelloWorldMuleProjec.xml file and it will show the empty flow. We need to implement our logic to display Hello World.
Drag and drop HTTP connector from connector pallet to Mule flow. Configure as shown below.
Select the HTTP connector à HTTP Properties à under General Tab enter the below configuration details as shown.
Field
Value
General Tab
Display Name
HTTP
Host
localhost
Port
8081
Notes Tab
Description
This endpoint receives an HTTP message.

Drag and drop Set Payload transformer from Transformations to sets a value in the message payload. In this example, the value utilizes a Mule expression to set a static string on the payload. Like the HTTP endpoint, the descriptive notes included in the configuration helps other developers understand the actions the element performs in the context of the application.

Select the Set Payload à Set Payload Properties àunder General Tab enter the below configuration details as shown.
Field
Value
General Tab
Display Name
Set Payload
Value
Hello Ameer
Notes Tab
Description
This processor sets the payload of the message to the string 'Hello Ameer'.

continue reading

Designed By AMEER BASHA G