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).
Optimized local adapters and the supporting native API callable services provide an alternative path for enterprise architecture and application development on the z/OS® platform.
Use this high-level task when you are planning to implement the optimized local adapters for z/OS® in your environment.
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.
Use this task when you are implementing the optimized local adapters support for calling inbound to WebSphere Application Server for z/OS Enterprise JavaBeans (EJB) applications.
Use this task when you are implementing the optimized local adapters support for calling programs in external address spaces from WebSphere Application Server for z/OS applications.
Configuring data access for the Application Client involves specifying the resource reference and associated database information required for data access. This specification is done as part of the assembly and deployment steps for the Application Client.
If you have a DB2 database configured in the Application Server, enable DB2 Performance Expert Extended Insight (PEEI) to employ an end-to-end monitoring system for your environment. PEEI features allow you to monitor transactions throughout your system stack and tune your resources according to the comprehensive data reports.
You can disable support for all custom finders defined on a specific bean by modifying your application's EAR file.
You can add an environment variable to establish support for custom finders you want to use in data access applications.
Extend data source definitions, which consist of non-core or custom properties, for DB2® data sources to add a greater level of application flexibility when you are using the DB2 Universal JDBC driver or DB2 Using IBM® JCC driver. This capability is sometimes referred to as heterogeneous pooling. Use this feature to configure a DB2 data source in the application server with a core set of data source properties, and defer to individual applications to define any custom or non-core properties, like currentSchema or clientApplicationInformation, that you want to be application specific. You can also use these extended definitions to override any non-core or custom properties that are already defined for the data source. In addition, this feature can reduce the number of physical connections that the application server uses by employing one connection pool between resources that connect to the same data source.
Using a WebSphere Application Server API or trace function, you can pass unique client information about every connection that originates from the same data source.
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. This topic describes the conventions in use for WebSphere Application Server.