home 
 
 
 
nlfr
 
Home
About ABIS
Services
Courses
Resources
Contact
MyABIS
 
All CoursesbalkjeGeneral » Introduction to HW & SW » TracksOperating systems » MVS - z/OS » UNIX - Linux - AIX » VMwareDatabases, transaction systems and middleware » DB2 for z/OS » DB2 UDB for Linux, UNIX and Windows » Oracle » SQL Server » MySQL » IMS » CICS » WebSphere MQ » WebSphere Application Server » Business intelligence and data warehouseApplication development » Methods and techniques » TOGAF » PRINCE2 » Programming languages » Internet development » Object Oriented systems » Java » IBM development tools » SAS » XML » SOA & web servicesSystems management » ITILbalkjePractical informationRegistration 

In focus - WebSphere backend integration

ABIS appreciates the important role played by the WebSphere Application Server when focusing on application integration and application reuse - more specifically, backend integration. A substantial part of our resources - investments in knowledge - are therefore WebSphere Server and integration-related. The acquired knowledge is used to expand and improve existing courses; or is offered in a seminar for customer specific requests. The figure below offer a number of alternative integration scenarios in which WebSphere Application Servers plays an important part. Each of the arrows emanating from the servlet running in the Java EE container - and all combinations integrating IMS, CICS and WebSphere MQ based applications - have been thoroughly tested by ABIS. And have been the subject of customer presentations.

../Pict/coursefocus/Nf_WEBSPH.gif

A focal point of our approach is the role of the Java EE container and the connector architecture it uses. This architecture allows for a certain degree of abstraction: application developers build there systems using standard based APIs; they call upon the features of the WebSphere Java EE container, and do not have to worry about a number of characteristics typically 'connection' or 'backend integration' related. Indeed, the WebSphere administrator will be responsible for the creation and configuration of a 'connector' object - a resource - including areas such as tuning, availability, and security. All concentrated in a centrally managed, trackable and tunable 'connector' object. As a result, problem analysis should become easier and more straightforward.

When discussing backend integration, a lot of alternative scenario's are available. Not all of them will be relevant for you; it all depend on the implementation scenarios to be implemented. We are glad to be able to work with you in developing a course or seminar showing your IT-staff how to get 'integrated' as well!