Few blogs which I read occasionally
Bobby Woolf: WebSphere SOA and J2EE in Practice
Bill Newport , WebSphere & Distributed Computing
Ali Arsanjani, Chief Architect SOA & Web Services, IBM
Grady Booch Software architecture, software engineering, and Renaissance Jazz
Sanjay Bose: SOA, ESB and beyond
Some more links
AIXPert:
WebSphere XD
SOAnderful
Also the following samples are most useful if you are working on WebSphere Process Server & WebSphere Integration Developer.
http://publib.boulder.ibm.com/bpcsamp/
http://www-128.ibm.com/developerworks/offers/lp/helloworld/
Thursday, March 15, 2007
Wednesday, March 14, 2007
Workflow in WebSphere Process Server
Last night i have participated in a technical discussions on WebSphere Process Server and work flow creating in WebSphere Integration Developer. The questions come up are like 1) How do we map the J2EE roles to Human task; 2) Dynamically added tasks based on a return value from HT.
I will search or do some work on this and post the answers here.
I will search or do some work on this and post the answers here.
Tuesday, March 13, 2007
Service Oriented Architecture, What is SOA?
SOA or Service Oriented Architecture is the buzz word in IT now. Why SOA so important these days?
Beginning of 90's, IT solutions learned the trick of Integration and importance of Integration. Messaging Middleware's ruled the solutions. Many solutions emphasized importance of Messaging Middlewares like MQSeries (now known as WebSphere MQ). There is a greater importance on interoperability and need for CORBA technologies.
The solutions carved using middleware technologies are well performed, highly scalable, but not addressing the business flexibility. Often a middleware solution expert would have to explain how the business process was realized. The business knowledge was neck deep into technical solution. This is taking substantially long time to modify the technical pieces to meet the business expectations.
The concepts of choreography and orchestration are emerging by end of 90's and birth of BPM (Business Process Management). In this business processes are realized by orchestrating coarse grained services in a BPEL (Business Process Execution Language) flow.
The tough job for an SOA architect is to identify the business logic and business process, and the technical pieces to tie them together in loosely coupled fashion.
What is SOA: SOA is an architectural approach that structures IT assets as a series of reusable services that perform a business functions.
Beginning of 90's, IT solutions learned the trick of Integration and importance of Integration. Messaging Middleware's ruled the solutions. Many solutions emphasized importance of Messaging Middlewares like MQSeries (now known as WebSphere MQ). There is a greater importance on interoperability and need for CORBA technologies.
The solutions carved using middleware technologies are well performed, highly scalable, but not addressing the business flexibility. Often a middleware solution expert would have to explain how the business process was realized. The business knowledge was neck deep into technical solution. This is taking substantially long time to modify the technical pieces to meet the business expectations.
The concepts of choreography and orchestration are emerging by end of 90's and birth of BPM (Business Process Management). In this business processes are realized by orchestrating coarse grained services in a BPEL (Business Process Execution Language) flow.
The tough job for an SOA architect is to identify the business logic and business process, and the technical pieces to tie them together in loosely coupled fashion.
What is SOA: SOA is an architectural approach that structures IT assets as a series of reusable services that perform a business functions.
Subscribe to:
Comments (Atom)