09.02.2015 Views

Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Value of BPM for the <strong>Cloud</strong>s 141<br />

earlier <strong>in</strong> this chapter, no st<strong>and</strong>ard def<strong>in</strong>itions exist for these concepts, so perhaps<br />

it is time we created them.<br />

Bus<strong>in</strong>ess process automation (BPA) tools <strong>and</strong> approaches provide<br />

mechanisms for the automation of bus<strong>in</strong>ess processes without end-user<br />

<strong>in</strong>teraction at execution time. Most application <strong>in</strong>tegration tools<br />

provide this type of subsystem.<br />

Workflow tools allow for the automation of bus<strong>in</strong>ess processes with<br />

end-user <strong>in</strong>teraction (typically) at execution time. These categories of<br />

technology <strong>and</strong> approaches are typically document oriented, mov<strong>in</strong>g<br />

document <strong>in</strong>formation among human decision makers.<br />

BPM is an aggregation of bus<strong>in</strong>ess process model<strong>in</strong>g, bus<strong>in</strong>ess process<br />

automation, <strong>and</strong> workflow. This approach implements <strong>and</strong> manages<br />

transactions <strong>and</strong> real-time bus<strong>in</strong>ess processes that span multiple<br />

applications, provid<strong>in</strong>g a layer to create common processes that span<br />

many processes <strong>in</strong> <strong>in</strong>tegrated systems.<br />

The good news is that most bus<strong>in</strong>ess processes are already automated.<br />

The bad news is that they tend to exist with<strong>in</strong> different systems. For example,<br />

add<strong>in</strong>g a customer to a packaged account<strong>in</strong>g application may establish the<br />

customer <strong>in</strong> that system, but it may still be necessary to use another system (a<br />

different system that may exist with<strong>in</strong> a trad<strong>in</strong>g partner) to perform a credit<br />

check on that customer <strong>and</strong> still another system to process an <strong>in</strong>voice. You<br />

need not possess exceptional <strong>in</strong>sight to recognize the potential for disaster<br />

that exists <strong>in</strong> this scenario. Not only do these disparate systems need to share<br />

<strong>in</strong>formation <strong>and</strong> services, but they also need to share that <strong>in</strong>formation <strong>in</strong> an<br />

orderly <strong>and</strong> efficient manner.<br />

The goal of BPM, <strong>and</strong> the use of BPM with<strong>in</strong> cloud comput<strong>in</strong>g, is to automate<br />

services <strong>in</strong>vocation <strong>and</strong> process flow so that another layer of processes<br />

will exist over <strong>and</strong> above the processes encapsulated <strong>in</strong> exist<strong>in</strong>g systems. In<br />

other words, BPM completes application b<strong>in</strong>d<strong>in</strong>g, allow<strong>in</strong>g the <strong>in</strong>tegration of<br />

systems by readily shar<strong>in</strong>g <strong>in</strong>formation <strong>and</strong> services <strong>and</strong> by manag<strong>in</strong>g the<br />

shar<strong>in</strong>g of that <strong>in</strong>formation <strong>and</strong> services with easy-to-use tools. This enables<br />

the process architect to create <strong>and</strong> re-create processes to solve bus<strong>in</strong>ess problems<br />

<strong>and</strong> adjust processes as needed, as the bus<strong>in</strong>ess changes.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!