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 WebSphere® Application Server provides several options for accessing an information system's backend data store:
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).
When you assemble enterprise bean code into files that can be deployed onto an application server, you configure properties that define how the application accesses an enterprise information system (EIS), such as a database.
Frequently, deploying a data access application includes more than installing your Web archive (WAR) or enterprise archive (EAR) file onto a server. Deployment can include tasks for configuring your application to use the data access resources of the server and overall run-time environment.
The application server uses the classes and other code that comprise a resource adapter archive (RAR) to support the resource adapters that you configure.
Use Structured Query Language in Java™ (SQLJ) to develop data access applications that connect to DB2® databases. SQLJ is a set of programming extensions that enable you to use the Java programming language to embed statements that provide SQL (Structured Query Language) database requests.