2 options
WebSphere Application Server Enterprise V5 and programming model extensions / Peter Kovari ... [et al.].
- Format:
- Book
- Series:
- WebSphere handbook series.
- IBM redbooks.
- WebSphere handbook series
- IBM redbooks
- Language:
- English
- Subjects (All):
- Web servers--Computer programs.
- Web servers.
- WebSphere.
- Physical Description:
- xx, 706 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- [S.l.] : IBM, International Technical Support Organization, c2003.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Introduction
- Chapter 1. Introduction
- 1.1 WebSphere Application Server Enterprise
- 1.1.1 Simplify build-to-integrate tasks
- 1.1.2 Accelerate large-scale application development
- 1.2 How this book is organized
- 1.2.1 Organization of the PME chapters
- 1.2.2 End-to-end solution implementation
- Chapter 2. Planning
- 2.1 Planning for WebSphere Enterprise
- 2.2 Using WebSphere Enterprise
- 2.3 Service oriented architecture
- 2.3.1 Web services
- 2.3.2 J2C
- 2.3.3 Programming Model Extensions
- 2.3.4 Combining PMEs
- Chapter 3. Sample scenario
- 3.1 Business scenario
- 3.2 Business drivers
- 3.3 Use cases
- 3.4 Business processes
- 3.4.1 Catalog update business process
- 3.4.2 Purchase Order (PO) business process
- Part 2 Programming Model Extensions
- Chapter 4. Process Choreographer development scenarios
- 4.1 Planning
- 4.1.1 Business processes
- 4.1.2 Why use Process Choreographer?
- 4.1.3 Comparison with WebSphere MQ workflow
- 4.1.4 Business processes for J2EE programmers
- 4.1.5 Programming model
- 4.1.6 J2EE programming model
- 4.2 Design
- 4.2.1 Elements of a process model
- 4.2.2 Types of processes and transactions
- 4.2.3 Life cycle of a process
- 4.2.4 Undoing service activities: compensation
- 4.2.5 Process modeling languages and standards
- 4.2.6 External programming interfaces
- 4.3 Development
- 4.3.1 Choreographer Web client
- 4.3.2 Customizing the choreographer Web client
- 4.4 Testing and debugging
- 4.4.1 Unit test environment
- 4.5 Staff support
- 4.6 Sample scenario
- Chapter 5. Process Choreographer runtime environment
- 5.1 Process container architecture
- 5.2 Process container runtime topologies.
- 5.2.1 Stand-alone application server on a single machine (SA)
- 5.2.2 Application servers network deployed with no clustering (ND-noC)
- 5.2.3 Application server clusters in Network Deployment (ND-C)
- 5.2.4 Application server cluster with WebSphere MQ Clustering (MQ-C)
- 5.2.5 Application server cluster and high-availability configuration (DB-C&
- MQ-C)
- 5.3 Installing the process container
- 5.3.1 Resources required by a process container
- 5.3.2 Installing required software components
- 5.3.3 Process container on a stand-alone topology (SA)
- 5.3.4 Installing process container in a cell topology (ND-noC)
- 5.3.5 Installing process container in topology (ND-C, ND-VS, ND-HS)
- 5.4 Staff plug-in provider configuration
- 5.5 Security considerations
- 5.5.1 Securing the Process Choreographer resources
- 5.5.2 Process security context
- 5.5.3 Process Choreographer J2EE security roles
- 5.6 Managing business process applications
- 5.6.1 Artifacts of a business process application
- 5.6.2 Installing business process applications
- 5.6.3 Versioning process models
- 5.6.4 Starting and stopping process templates
- 5.6.5 Uninstalling a business process application
- 5.6.6 Editing a business process application
- 5.6.7 Managing process instances
- 5.7 Problem determination and troubleshooting
- 5.7.1 Error messages
- 5.7.2 Tracing process container
- 5.7.3 Process audit trail
- Chapter 6. Extended Messaging
- 6.1 Planning
- 6.1.1 Java Message Service
- 6.1.2 Extended Messaging
- 6.1.3 Why use Extended Messaging?
- 6.2 Design
- 6.2.1 Messaging patterns
- 6.2.2 Programming considerations
- 6.3 Development
- 6.3.1 Sample scenario
- 6.3.2 Creating the sample
- 6.4 Unit test environment
- 6.4.1 Configure Extended Messaging
- 6.4.2 Test the sample
- 6.5 Configuration.
- 6.5.1 Comparison of WebSphere MQ and Embedded Messaging
- 6.5.2 Configuration with JMS Embedded Messaging
- 6.5.3 Configuration with WebSphere MQ as the JMS provider
- 6.6 Deployment
- 6.7 Transactions and workload management
- 6.8 Handling late responses
- 6.8.1 Late response description
- 6.8.2 Configuration of late response
- 6.9 Problem determination and troubleshooting
- 6.10 Security considerations
- Chapter 7. Asynchronous Beans
- 7.1 Planning
- 7.1.1 What are Asynchronous Beans?
- 7.1.2 Asynchronous Beans programming interfaces
- 7.1.3 Asynchronous Beans: simple Java objects or EJBs?
- 7.1.4 Asynchronous Beans: programming model
- 7.1.5 When to use Asynchronous Beans
- 7.2 Design
- 7.2.1 Base application overview
- 7.2.2 Asynchronous patterns
- 7.3 Development - base application
- 7.3.1 Set up the base application
- 7.3.2 Understand the base application
- 7.3.3 Configure the base application
- 7.3.4 Run the base application
- 7.4 Development: "Asynchronize" the base application
- 7.4.1 Asynchronously initialize the cache using Work
- 7.4.2 Asynchronously keep cache updated using EventListener
- 7.4.3 Asynchronously update database using AlarmListener
- 7.4.4 Set up the extended application
- 7.5 Unit test environment
- 7.6 Assembly
- 7.7 Configure
- 7.8 Deployment
- 7.9 QoS (Quality of Service) considerations
- 7.9.1 Multiple WorkManagers
- 7.9.2 Dynamically tuning WorkManagers at runtime
- 7.10 Security considerations
- 7.11 An additional sample
- 7.11.1 Implementation details
- 7.11.2 Configuration and requirements
- Chapter 8. Application Profiling and Access Intent
- 8.1 Overview
- 8.2 Planning
- 8.3 Performance report
- 8.4 Assembly
- 8.4.1 Creating an Access Intent Policy
- 8.4.2 Creating an Access Intent
- 8.4.3 Creating an Application Profile.
- 8.4.4 Creating a Dynamic Query Access Intent
- 8.4.5 Application Profiling API
- 8.5 Problem determination and troubleshooting
- Chapter 9. Transactional Services
- 9.1 Transactions overview
- 9.2 Last Participant Support
- 9.2.1 Configuration
- 9.2.2 Troubleshooting
- 9.3 ActivitySession
- 9.3.1 Extended Local Transaction
- 9.3.2 Extended EJB life cycle
- 9.3.3 Usage scenarios
- 9.4 Runtime
- 9.4.1 Enable the ActivitySession service
- 9.4.2 Troubleshooting
- 9.5 JTA extensions
- 9.6 Samples
- Chapter 10. Business Rule Beans
- 10.1 Planning
- 10.2 Design
- 10.2.1 Business Rule Beans framework
- 10.2.2 Architecture
- 10.3 Development
- 10.3.1 Development environment setup
- 10.3.2 Creating the rule implementor
- 10.3.3 Creating and configuring the rule
- 10.3.4 Creating the rule client
- 10.3.5 Integrating the sample application with the business rule
- 10.4 Unit test environment
- 10.4.1 Rule unit testing
- 10.4.2 Testing the sample application with the rule beans enabled
- 10.5 Assembly
- 10.6 Deployment
- 10.6.1 Running the Rule Management Application
- 10.7 Problem determination and troubleshooting
- 10.8 Performance considerations
- 10.8.1 Client-side caching
- 10.8.2 Rule firing location
- 10.8.3 Creating database indexes
- 10.9 Security considerations
- Chapter 11. Dynamic Query
- 11.1 Planning
- 11.1.1 Dynamic Query
- 11.2 Design
- 11.3 Development
- 11.3.1 Dynamic Query Bean
- 11.3.2 Development environment setup
- 11.3.3 Development of Dynamic Query sample
- 11.3.4 Integration of Dynamic Query with sample application
- 11.4 Unit test environment
- 11.4.1 Configure application server
- 11.4.2 Running the sample application
- 11.5 Assembly
- 11.5.1 Projects export
- 11.5.2 Configuring EJB Access Intent for Dynamic Query
- 11.5.3 Incorporating bpeWebclient.war
- 11.6 Configuration.
- 11.6.1 Installing query.ear
- 11.6.2 Application class loader policy configuration
- 11.7 Deployment
- 11.8 Performance considerations
- 11.8.1 Transactions and Dynamic Query
- 11.9 Security considerations
- Chapter 12. Startup Bean
- 12.1 Introduction
- 12.1.1 Why use Startup Beans?
- 12.2 Design
- 12.3 Development
- 12.4 Unit test environment
- 12.5 Assembly
- 12.6 Development
- 12.6.1 Sample scenario
- 12.7 Configuration
- 12.8 Deployment
- 12.9 Runtime environment
- 12.9.1 Priorities when using multiple Startup Beans
- 12.9.2 Scalability
- 12.10 Problem determination and troubleshooting
- Chapter 13. Scheduler service
- 13.1 Introduction
- 13.2 Design
- 13.3 Development
- 13.3.1 Scheduler API
- 13.3.2 Steps for using the Scheduler service
- 13.4 Unit test environment
- 13.5 Assembly
- 13.6 Building and tools
- 13.7 Sample scenario
- 13.8 Configuration
- 13.9 Deployment
- 13.10 Scheduler service runtime
- 13.11 Problem determination and troubleshooting
- 13.12 Performance monitoring
- 13.13 Security considerations
- Chapter 14. Object pools
- 14.1 Planning
- 14.2 Design
- 14.3 Development
- 14.3.1 Object Pools API
- 14.3.2 Steps for using object pools
- 14.4 Unit test environment
- 14.5 Assembly
- 14.6 Sample application
- 14.7 Configuration
- 14.8 Runtime environment
- 14.9 Problem determination and troubleshooting
- 14.10 Performance monitoring
- Chapter 15. Shared Work Area service
- 15.1 Planning
- 15.2 Design
- 15.3 Development
- 15.3.1 Work Area API
- 15.3.2 Steps for using the Shared Work Area service
- 15.4 Unit test environment
- 15.5 Sample application
- 15.6 Configuration
- 15.6.1 Shared Work Area service configuration
- 15.6.2 Shared work area client properties
- 15.7 Problem determination and troubleshooting
- Chapter 16. Internationalization (i18n) service
- 16.1 Planning.
- 16.1.1 The traditional solutions and the limitations.
- Notes:
- "August 2003."
- Includes bibliographical references and index.
- OCLC:
- 932363919
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.