Establish high availability for data access resources
Various enterprise information systems (EIS) use different methods for storing data. These backend data stores might be relational databases, procedural transaction programs, or object-oriented databases.
IBM WebSphere Application Server provides several options for accessing an information system's backend data store:
- Programming directly to the database through the JDBC 4.0 API, JDBC 3.0 API, or JDBC 2.0 optional package API.
- Programming to the procedural backend transaction through various J2EE Connector Architecture (JCA) 1.0 or 1.5 compliant connectors.
- Programming in the bean-managed persistence (BMP) bean or servlets indirectly accessing the backend store through either the JDBC API or JCA compliant connectors.
- Use container-managed persistence (CMP) beans.
- Use the IBM data access beans, which also use the JDBC API, but give you a rich set of features and function that hide much of the complexity associated with accessing relational databases.
Service Data Objects (SDO) simplify the programmer experience with a universal abstraction for messages and data, whether the programmer thinks of data in terms of XML documents or Java objects. For programmers, SDOs eliminate the complexity of the underlying data access technology (JDBC, RMI/IIOP, JAX-RPC, JMS, and so on) and message transport technology (java.io.Serializable, DOM Ojbects, SOAP, JMS, and so on).
Subtopics
- Changing the error detection model to use the Exception Checking Model
- Configure resource adapters
- Configure Oracle Real Application Cluster (RAC) with the application server
- Configure client reroute for applications that use DB2 databases
- Configure connection validation timeout
End-to-end paths for data access resources Migrate data access resources Administer data access resources Script for data access resources Data access resources Secure data access resources Developing data access resources Tune data access resources Troubleshoot data access resources