29.01.2013 Views

WebSphere Application Server - IBM Redbooks

WebSphere Application Server - IBM Redbooks

WebSphere Application Server - IBM Redbooks

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.

A significant amount of data resides on the Enterprise Information System.<br />

Examples of EIS include:<br />

► Customer Information Control System (CICS®) server<br />

► Legacy applications developed on mainframes or legacy systems<br />

► Relational databases such as DB2<br />

Connectors provide the link between the new business logic in the middle tier to<br />

the vast accumulated assets in a company's existing applications and data<br />

systems.<br />

Note: <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> - Express provides JDBC connectivity to<br />

back-end relational databases. <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> - Express also<br />

supports the creation and use of Web services.<br />

2.1.2 <strong>IBM</strong> Patterns for e-business<br />

The job of an IT architect is to evaluate business problems and to design a<br />

solution. The architect begins by gathering input on the problem, the desired<br />

solution, and any special considerations or requirements that need to be factored<br />

in. The architect takes this input and designs a solution that includes one or more<br />

applications that provide the necessary functions.<br />

It is to our advantage to capture the experience of these IT architects in such a<br />

way that future engagements are made simpler. By taking this experience and<br />

crafting a repository we provide a way for architects to use this experience to<br />

build future solutions. Using proven scenarios saves time and money for both<br />

sides and helps ensure a solid solution that will stand the test of time.<br />

The <strong>IBM</strong> Patterns for e-business effort does just this. Its purpose is to capture<br />

e-business approaches that have been tested and proven. The information<br />

captured is thought to fit the majority of situations. By making these approaches<br />

available and classifying them into useful categories, we save the e-business<br />

planners, architects, and developers both time and money.<br />

These approaches are further refined into useful, tangible guidelines. The<br />

patterns and their associated guidelines allow the architect to start with a<br />

problem and a vision, find a conceptual pattern that fits this vision, define the<br />

necessary functional pieces that the application will need to succeed, and then<br />

actually build the application using coding techniques outlined in the guidelines.<br />

The <strong>IBM</strong> Patterns for e-business Web site (below) contains the information and<br />

references you need to design and build a solution from beginning to end.<br />

http://www.ibm.com/developerworks/patterns/<br />

Chapter 2. <strong>Application</strong> design 21

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

Saved successfully!

Ooh no, something went wrong!