i lllffi{Hilllillllllllllllilll OS --
https://www.bubangalore.com/papers/ba-5-sem-computer-science-5-internet-technology-2012.pdf
INVESTIGATING THE J2EE SOFTWARE ARCHITECTURE FOR
J2EE was developed by Sun Microsystems and its associates as a Java- EJB clients are applications that access EJB components in EJB containers.
MIT ;sequence=
14IT704 Enterprise programming-II
Session beans and Message driven Beans are EJB components 2 a) Describe in detail about Architecture and goals of Java EE with neat diagram.
BCE
CEGP013091 CEGP013091 CEGP013091
2) Neat diagrams must be drawn wherever necessary. b) Explain how to create and read array elements in java script. ... EJB architecture.
may jun analysis
Component-based Software Development
22 juin 2008 The EJB architecture maps out the programming and deployment en- vironment for distributed software components. It de nes the entire pro-.
FULLTEXT
Mastering Enterprise JavaBeans™
Component Architectures. 12. Introducing Enterprise JavaBeans. 13. Why Java? 14. EJB as a Business Solution. 14. The EJB Ecosystem. 16. The Bean Provider.
MasteringEJB
Generic Model-based Approaches for Software Reverse
23 avr. 2019 ses/activités d'UML (i.e. fUML) et des éléments noyaux du langage de pro- ... architectures and related technical solutions ...
Software Architecture and Design Patterns Unit-I IV B. Tech I
All of the elements apparently have some sort of relationship with each other since the diagram is fully connected. The models are described in figure 3.
SADP
Build a business process solution using Rational and WebSphere
claim system. Figure 2-11 Merged claim process architecture overview diagram The EJB components have been modified to issue JMS ... Tidy up the diagram.
sg
WebSphere Application Server V7.0: Concepts Planning
https://www.redbooks.ibm.com/redbooks/pdfs/sg247708.pdf
ibm.com/redbooksBuild a Business ProcessSolution Using Rational and WebSphere ToolsPeter Swithinbank Hossam Badawi
Jenny He
Arisa Izuno
Parul Lewicke
Holger Schwarzer
Larry Yusuf
Explore IBM On Demand Business and
business-driven developmentLearn to use modeling, UML, and
BPELStudy implementation
and integrationFront cover
Build a Business Process Solution Using Rational
and WebSphere Tools February 2006International Technical Support OrganizationSG24-6636-00
© Copyright International Business Machines Corporation 2006. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
First Edition (February 2006)
This edition applies to Version 5 of the WebSphere platform. Note: Before using this information and the product it supports, read the information in "Notices" on page xi. © Copyright IBM Corp. 2006. All rights reserved.iiiContents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
The companies in this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Part 1. Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Chapter 1. Business context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Setting the scene. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.1 Company history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.2 Scope of the scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1.3 Claim system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Business goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2.1 Reduce cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.2 Increase customer satisfaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.3 Incorporate existing resources into the new solution . . . . . . . . . . . . . 8
1.2.4 Provide a complete view of the external assessment process . . . . . . 9
1.3 IT goals and constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 2. Current architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Before the merger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2 The merged solution context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Integration solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.1 Quote and policy administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.2 Claims Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4 IT infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.1 User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.2 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.4.3 Message Brokers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4.4 Process managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.5 Backend transaction servers and data centers. . . . . . . . . . . . . . . . . 31
2.5 Extending the architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.6 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
iv Build a Business Process Solution Using Rational and WebSphere ToolsPart 2. Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 3. Our method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.1 Building the On Demand Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.1.1 The on demand operating environment . . . . . . . . . . . . . . . . . . . . . . 40
3.1.2 Service-oriented modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1.3 The IBM Software Development Platform. . . . . . . . . . . . . . . . . . . . . 43
3.2 Building the External Claim Assessor solution . . . . . . . . . . . . . . . . . . . . . 45
3.2.1 Roles and responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.2 Responsibilities and contract-based development . . . . . . . . . . . . . . 52
3.2.3 Gather business requirements though modeling workshops . . . . . . 55
3.2.4 Establish a Reference Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.2.5 The Patterns for e-business layered asset model. . . . . . . . . . . . . . . 58
3.2.6 A process for using the Patterns for e-business asset model. . . . . . 59
3.2.7 Use a Model Driven Development approach . . . . . . . . . . . . . . . . . . 67
3.2.8 Tool chains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.3 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Chapter 4. Business Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.1 Introduction to business process management. . . . . . . . . . . . . . . . . . . . . 76
4.1.1 Business Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.1.2 IBM suite of BPM tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.1.3 Why business process modelling . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.1.4 WebSphere Business Integration Modeler . . . . . . . . . . . . . . . . . . . . 81
4.1.5 Editions of WebSphere Business Integration Modeler . . . . . . . . . . . 81
4.2 Using WebSphere Business Integration Modeler . . . . . . . . . . . . . . . . . . . 82
4.2.1 Who uses WebSphere Business Integration Modeler?. . . . . . . . . . . 83
4.3 Modeling the claim investigation process . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.3.1 Start WebSphere Business Integration Modeler. . . . . . . . . . . . . . . . 84
4.3.2 Import AS-IS process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.3.3 Analyzing the as-is process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.3.4 Create the to-be process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.3.5 Build a new process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.3.6 Features attractive to business analyst. . . . . . . . . . . . . . . . . . . . . . 117
4.4 Simulate the process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4.4.1 Create a simulation snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4.4.2 Define values for simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4.4.3 Run a simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
4.4.4 Simulate the whole claim investigation process . . . . . . . . . . . . . . . 129
4.4.5 Analyze the results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.5 Developing the process implementation . . . . . . . . . . . . . . . . . . . . . . . . . 134
4.5.1 Export processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4.5.2 Export as FDL process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Contents v4.5.3 Export RequestExternalReports as a BPEL4WS process . . . . . . . 1434.6 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Chapter 5. System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535.1 Selecting the architectural patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
5.2 Step 0: Collating requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.2.1 Business goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.2.2 Business use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.2.3 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.2.4 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5.2.5 Organization and architectural constraints . . . . . . . . . . . . . . . . . . . 168
5.2.6 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.3 Step 1: Select a Business Integration Pattern. . . . . . . . . . . . . . . . . . . . . 169
5.4 Step 2: Select the application pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.4.1 Collaborations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.4.2 Application Patterns for the Extended Enterprise . . . . . . . . . . . . . . 173
5.4.3 Application patterns for Application Integration. . . . . . . . . . . . . . . . 175
5.5 Step 3: Select and merge the runtime patterns. . . . . . . . . . . . . . . . . . . . 176
5.5.1 Proposal 1: Broker focussed integration pattern. . . . . . . . . . . . . . . 177
5.5.2 Proposal 2: Process focused integration pattern . . . . . . . . . . . . . . 179
5.6 Step 4: Apply product mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5.6.1 Existing systems and platform investments . . . . . . . . . . . . . . . . . . 181
5.6.2 Available customer and developer skills . . . . . . . . . . . . . . . . . . . . . 181
5.6.3 Customer choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
5.6.4 Product Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
5.7 Reference architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5.7.1 Omissions from the reference architecture . . . . . . . . . . . . . . . . . . . 185
5.8 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Chapter 6. Solution Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1876.1 Interaction Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
6.1.1 Interaction descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
6.1.2 Sequence diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6.2 Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.2.1 Choice of interface description language . . . . . . . . . . . . . . . . . . . . 195
6.2.2 Creating WSDL interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6.2.3 Sources of Interface Information for the scenario . . . . . . . . . . . . . . 198
6.2.4 Creating the interface definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6.2.5 Incorporating the interfaces into the UML model . . . . . . . . . . . . . . 209
ibm.com/redbooksBuild a Business ProcessSolution Using Rational and WebSphere ToolsPeter SwithinbankHossam Badawi
Jenny He
Arisa Izuno
Parul Lewicke
Holger Schwarzer
Larry Yusuf
Explore IBM On Demand Business and
business-driven developmentLearn to use modeling, UML, and
BPELStudy implementation
and integrationFront cover
Build a Business Process Solution Using Rational
and WebSphere Tools February 2006International Technical Support OrganizationSG24-6636-00
© Copyright International Business Machines Corporation 2006. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
First Edition (February 2006)
This edition applies to Version 5 of the WebSphere platform. Note: Before using this information and the product it supports, read the information in "Notices" on page xi. © Copyright IBM Corp. 2006. All rights reserved.iiiContents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
The companies in this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv
The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Part 1. Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Chapter 1. Business context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Setting the scene. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.1 Company history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.2 Scope of the scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1.3 Claim system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Business goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2.1 Reduce cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.2 Increase customer satisfaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.3 Incorporate existing resources into the new solution . . . . . . . . . . . . . 8
1.2.4 Provide a complete view of the external assessment process . . . . . . 9
1.3 IT goals and constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 2. Current architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Before the merger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2 The merged solution context. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Integration solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.1 Quote and policy administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.2 Claims Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4 IT infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4.1 User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.2 Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.4.3 Message Brokers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4.4 Process managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4.5 Backend transaction servers and data centers. . . . . . . . . . . . . . . . . 31
2.5 Extending the architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.6 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
iv Build a Business Process Solution Using Rational and WebSphere ToolsPart 2. Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 3. Our method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.1 Building the On Demand Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.1.1 The on demand operating environment . . . . . . . . . . . . . . . . . . . . . . 40
3.1.2 Service-oriented modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1.3 The IBM Software Development Platform. . . . . . . . . . . . . . . . . . . . . 43
3.2 Building the External Claim Assessor solution . . . . . . . . . . . . . . . . . . . . . 45
3.2.1 Roles and responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.2 Responsibilities and contract-based development . . . . . . . . . . . . . . 52
3.2.3 Gather business requirements though modeling workshops . . . . . . 55
3.2.4 Establish a Reference Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.2.5 The Patterns for e-business layered asset model. . . . . . . . . . . . . . . 58
3.2.6 A process for using the Patterns for e-business asset model. . . . . . 59
3.2.7 Use a Model Driven Development approach . . . . . . . . . . . . . . . . . . 67
3.2.8 Tool chains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.3 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Chapter 4. Business Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75