3 options
DB2 for z/OS and WebSphere : the perfect couple / [Bart Steegmans ... et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Database management.
- IBM Database 2.
- z/OS.
- WebSphere.
- Physical Description:
- xxiv, 332 p. : ill.
- Edition:
- 1st ed.
- Other Title:
- Database 2 for z/OS and WebSphere
- Database Two for z/OS and WebSphere
- Place of Publication:
- San Jose : IBM, International Technical Support Organization, c2005.
- Language Note:
- English
- System Details:
- text file
- Summary:
- DB2 for z/OS is a high performance DBMS, with a very strong reputation in high volume transaction workloads based on relational technology. WebSphere Application Server is a transaction monitor based on object-oriented technology, very much in sync with the J2EE standard. Can we marry the object world and relational world to create a high-volume, high-performance end-to-end OLTP environment? The answers can be found in this IBM Redbooks publication. This book gives a broad understanding of the installation, configuration, and use of the IBM DB2 Universal Driver for SQLJ and JDBC in a DB2 for z/OS and OS/390 Version 7, and DB2 for z/OS Version 8 environment, with IBM WebSphere Application Server for z/OS for z/OS Version 5.02. It describes both type 2 and type 4 connectivity (including the XA transaction support) from a WebSphere Application Server on z/OS to a DB2 for z/OS and OS/390 database server. This publication also demonstrates the advantages of SQLJ in a DB2 environment, the SQLJ support in the IBM application development tool WebSphere Studio Application Developer, as well as the SQLJ support for Enterprise JavaBeans using container-managed persistence. Please note that the additional material referenced in the text is not available from IBM.
- Contents:
- Front cover
- Contents
- Figures
- Tables
- Examples
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Chapter 1. Introduction to DB2 for z/OS and OS/390
- 1.1 Relational database management systems
- 1.2 The DB2 Universal Database Family
- 1.2.1 DB2 UDB for Linux, UNIX®, and Windows®
- 1.2.2 DB2 UDB for iSeries™
- 1.2.3 DB2 Server for VSE and VM
- 1.2.4 More information on the DB2 UDB family, related tools, and products
- 1.3 Components of DB2 UDB for z/OS and OS/390
- 1.3.1 DB2 UDB for z/OS and OS/390 address spaces
- 1.3.2 DB2 attachment facilities
- 1.4 DB2 data structures
- 1.4.1 Databases
- 1.4.2 Storage groups
- 1.4.3 Data sets
- 1.4.4 Table spaces
- 1.4.5 Tables
- 1.4.6 Indexes
- 1.5 Structured query language (SQL)
- 1.5.1 Static SQL
- 1.5.2 Dynamic SQL
- 1.5.3 Industry standards
- 1.6 DB2 concepts
- 1.6.1 Referential constraints
- 1.6.2 DB2 packages, plans, collections, and package lists
- 1.6.3 Schemas
- 1.7 Accessing DB2 from a Java environment
- 1.7.1 JDBC fundamentals
- 1.7.2 JDBC driver types
- 1.7.3 IBM DB2 Legacy Driver
- 1.8 IBM DB2 Universal Driver for SQLJ and JDBC
- 1.8.1 IBM z/OS Application Connectivity to DB2 for z/OS and OS/390
- 1.9 Using the DB2 Universal Driver for SQLJ and JDBC
- 1.9.1 Required environment variable settings
- 1.9.2 DB2 Universal Driver stored procedures and metadata
- 1.9.3 Binding DB2 Universal JDBC Driver packages with the DB2Binder utility
- 1.9.4 DB2T4XAIndoubtUtil utility for DB2 UDB for OS/390 and z/OS Version 7
- 1.9.5 Differences between the DB2 Universal Driver and DB2 Legacy Driver
- 1.9.6 JDBC 3.0 APIs specific to the DB2 Universal Driver
- Chapter 2. Introduction to WebSphere for z/OS
- 2.1 Java 2 Enterprise Edition (J2EE) overview.
- 2.2 WebSphere Application Server architecture
- 2.3 WebSphere Application Server administration
- 2.3.1 Administration console
- 2.3.2 Other tools
- 2.4 The WebSphere family
- 2.5 WAS 5.0.2 features and J2EE support
- Chapter 3. WebSphere - DB2 environment
- 3.1 Introduction to the sample scenario setup
- 3.2 Introduction to DB2 drivers for Java
- 3.3 Data source definitions in WAS V5
- 3.4 The IBM DB2 Universal Driver for SQLJ and JDBC
- 3.4.1 Summary of WAS z/OS external changes for the Universal Driver
- 3.5 Configuring Universal JDBC Driver type 2 connectivity
- 3.5.1 Specifying the Universal JDBC Driver provider
- 3.5.2 Defining Data Sources under this provider
- 3.5.3 Setting/verifying the symbolic environment variables
- 3.5.4 Defining DB2 Universal Driver - General properties
- 3.5.5 Searching for the package to execute
- 3.5.6 Linking to the DB2 libraries
- 3.5.7 Creating a new Application Server
- 3.6 Configuring Universal JDBC Driver type 4 connectivity
- 3.6.1 Using the Universal Driver for type 4 (non-XA)
- 3.6.2 Using the Universal Driver for type 4 (XA) connectivity
- 3.7 Summary
- Chapter 4. DB2 and Java architecture guide
- 4.1 Introduction to J2EE data access architecture
- 4.2 Servlets and JavaServer Pages
- 4.2.1 Benefits of data access from servlets and JSPs
- 4.2.2 Considerations for data access from a servlet
- 4.3 Enterprise JavaBeans
- 4.4 Session Beans
- 4.5 Stateless session Beans
- 4.5.1 Benefits of data access from a stateless session Bean
- 4.5.2 Considerations
- 4.6 Stateful session Beans
- 4.6.1 Benefits of stateful session Beans
- 4.6.2 Considerations
- 4.7 Entity Beans
- 4.8 Bean-Managed Persistence entity Beans
- 4.8.1 Benefits
- 4.8.2 Considerations
- 4.9 Container-Managed Persistence entity Beans
- 4.9.1 Benefits
- 4.9.2 Considerations
- 4.10 Message-driven Beans.
- 4.11 Session facade pattern
- 4.12 Stored procedures
- 4.12.1 Benefits of accessing data from stored procedures
- 4.12.2 Considerations
- 4.13 Web services
- 4.14 SQLJ support
- 4.15 Java Data Objects
- 4.16 EJB Beans summary
- Chapter 5. DB2 application development in a WebSphere environment
- 5.1 JDBC and SQLJ application programming comparison
- 5.1.1 JDBC and SQLJ compared
- 5.1.2 Best practices
- 5.2 JDBC application programming concepts
- 5.2.1 Java packages for JDBC applications
- 5.2.2 Using the DB2 Universal JDBC Driver and the DataSource interface
- 5.2.3 Java identifiers and JDBC parameter markers
- 5.2.4 Statement and ResultSet interfaces
- 5.3 SQLJ application programming concepts
- 5.4 Preparing JDBC and SQLJ applications for execution
- 5.4.1 JDBC program preparation process
- 5.4.2 SQLJ program preparation process
- 5.5 Impact of different DB2 bind options on Java applications
- 5.5.1 OWNER bind option
- 5.5.2 QUALIFIER bind option
- 5.5.3 DYNAMICRULES bind option
- 5.5.4 ISOLATION bind option
- 5.6 Special registers
- 5.6.1 CURRENT SQLID
- 5.6.2 CURRENT SCHEMA
- 5.6.3 CURRENT PACKAGESET
- 5.6.4 CURRENT PACKAGE PATH
- 5.6.5 Using properties to specify special registers
- Chapter 6. WebSphere - DB2 security
- 6.1 Introduction to authentication, authorization, and auditing
- 6.1.1 Authentication
- 6.1.2 Authorization
- 6.1.3 Auditing
- 6.1.4 Application or infrastructure
- 6.1.5 DB2-supported authentication, authorization, and auditing
- 6.1.6 Choosing what identity to send DB2
- 6.1.7 Configuring WebSphere for authentication
- 6.1.8 Programmatic authentication
- 6.1.9 Default user ID and password authentication
- 6.1.10 Thread identity support
- 6.2 DB2 auditing
- Chapter 7. SQLJ
- 7.1 Writing SQLJ versus JDBC applications
- 7.1.1 Connections
- 7.1.2 Using SQLJ
- 7.1.3 Using JDBC.
- 7.2 Profile customization
- 7.2.1 Profile customization when using unqualified SQL
- 7.2.2 Reducing the number of SQLJ-generated packages
- 7.2.3 Using manual package versioning
- 7.3 Application design
- 7.3.1 Best practice
- 7.3.2 The detailed application flow
- 7.3.3 Exceptions and transactions
- 7.3.4 SQL exceptions and SQL warnings
- 7.4 SQLJ in WebSphere Studio Application Developer
- 7.4.1 Setting up the environment
- 7.4.2 Create the server and the datasource
- 7.4.3 Using an SQLJ Java project
- 7.4.4 User-managed persistence
- 7.4.5 Container-managed persistence
- 7.4.6 Customization
- 7.4.7 WAS 5.1.0.1 FixPak
- 7.5 Deployment to WebSphere Application Server
- 7.6 Summary
- Chapter 8. Transaction management in a WebSphere environment
- 8.1 What transactions are
- 8.1.1 Local transactions
- 8.1.2 Global transactions
- 8.2 WebSphere transaction management
- 8.2.1 Transaction demarcation
- 8.2.2 Bean-managed transactions and the UserTransaction interface
- 8.2.3 Transaction types (for container-managed transactions)
- 8.3 WebSphere resources and transaction support
- 8.3.1 Resource interfaces
- 8.3.2 Resource transaction isolation
- 8.3.3 Configuring JDBC resources
- 8.4 DB2 as a transaction manager
- 8.4.1 Configuring and exploiting DB2 as a transaction manager
- 8.4.2 DB2 configuration requirements
- 8.4.3 DB2 or WAS as a transaction manager
- 8.5 DB2 as a resource manager
- 8.5.1 DB2's support for XA
- 8.5.2 Global transaction support
- 8.6 Considerations for two-phase commit processing
- 8.6.1 Lock duration
- 8.6.2 Failure impact
- 8.6.3 Lock impact from failure
- 8.6.4 How to recover from failures
- Chapter 9. DB2 locking in a WebSphere environment
- 9.1 DB2 locking
- 9.2 Transaction isolation
- 9.2.1 Isolation levels
- 9.2.2 Overriding lock mode.
- 9.2.3 DB2 isolation determination in Java applications
- 9.2.4 Maintaining integrity with isolation Cursor Stability
- 9.2.5 Data sharing considerations
- 9.3 WebSphere transaction-related deployment descriptors
- 9.3.1 Setting the WebSphere transaction isolation level
- 9.3.2 Entity Bean isolation level (access intent)
- 9.4 Container-managed persistence generated SQL
- 9.4.1 Who generates the persistence SQL
- 9.4.2 Access intents
- Chapter 10. DB2 - WebSphere performance aspects
- 10.1 Recommended hardware and software configuration
- 10.2 WebSphere Application Server connection pooling
- 10.2.1 What is new in Version 5 - What is in WebSphere Version 4
- 10.2.2 How connection pooling works - How connection objects are structured
- 10.2.3 WebSphere data sources
- 10.2.4 Connection pooling - Best practices
- 10.3 DB2 and JDBC
- 10.3.1 Adjusting the number of DB2 threads and connections
- 10.3.2 Enabling DB2 dynamic statement cache
- 10.3.3 Choosing static SQL over dynamic SQL
- 10.3.4 Usage guidelines for JCC type 2 and type 4 connectivity
- 10.3.5 Enterprise JavaBeans (EJBs) and DB2 access
- 10.4 WLM classification of WAS and its impact on DB2
- 10.4.1 How DB2 and WebSphere Servers are structured on z/OS
- 10.4.2 Enabling WLM dynamic application environments with WAS V5
- 10.4.3 WebSphere classification and its impact on DB2
- 10.5 Tuning the storage for z/OS and the Java Virtual Machine
- 10.6 Universal Driver tracing
- 10.6.1 Universal Driver tracing
- 10.6.2 DB2SystemMonitor class
- Chapter 11. Sample application
- 11.1 Introduction
- 11.1.1 Sample table description
- 11.1.2 Importing the tables into WSAD
- 11.2 MVC model with entity Beans and a session Bean
- 11.2.1 Creating entity CMP Beans using JDBC from the imported tables
- 11.2.2 Container-managed persistence entity Beans with SQLJ.
- 11.2.3 Bean and container-managed persistence entity Bean with SQLJ.
- Notes:
- "January 2005."
- "SG24-6319-00."
- Includes bibliographical references and index.
- OCLC:
- 80247113
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.