Network Deployment (Distributed operating systems), v8.0 > Tune performance
Tune Data access resources
This page provides a starting point for finding information about data access. 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.
The flexible IBM WAS provides several options for accessing an information system backend data store:
- Program directly to the database through the JDBC 4.0 API, JDBC 3.0 API, or JDBC 2.0 optional package API.
- Program to the procedural backend transaction through various J2EE Connector Architecture (JCA) 1.0 or 1.5 compliant connectors.
- Program 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, such as, JDBC, RMI/IIOP, JAX-RPC and JMS, and message transport technology, such as, (java.io.Serializable, DOM Objects, SOAP and JMS).
End-to-end paths for Data access resources
Migrate Data access resources
Administer Data access resources
Scripting for data access resources
Establishing high availability for Data access resources
Secure Data access resources
Develop Data access resources
Data access resources
Troubleshoot Data access resources