Abstract: A technique is disclosed for identifying impact of database changes on an application. Given a proposed database change, affected source code is identified that is affected by the proposed database change. References to the affected source code are created and organized into a hierarchy. A user can ascertain the extent of the impact by viewing the hierarchy and by using the hierarchy to access and view the affected source code in a visually distinct manner.

Abstract: A technique is disclosed for identifying impact of database changes on an application. Given a proposed database change, affected source code is identified that is affected by the proposed database change. References to the affected source code are created and organized into a hierarchy. A user can ascertain the extent of the impact by viewing the hierarchy and by using the hierarchy to access and view the affected source code in a visually distinct manner.

Abstract: A method of accessing layers in a multi-layer software architecture including a first layer, a second layer, and a third layer. The method includes: at the third layer, publishing an interface; and at the first layer, before execution of a first function, registering a callback routine with the third layer using the interface.

Abstract: A technique is disclosed for identifying impact of database changes on an application. Given a proposed database change, affected source code is identified that is affected by the proposed database change. References to the affected source code are created and organized into a hierarchy. A user can ascertain the extent of the impact by viewing the hierarchy and by using the hierarchy to access and view the affected source code in a visually distinct manner.

Abstract: Development tools are disclosed that connect various artifacts in a database aware fashion. For example, the development environment may integrate SQL query builders across multiple application development interfaces (e.g., a source code editor, XML editor, database scripting tools, etc.), significantly improving developer productivity, reducing development cost and time. Thus, the process of consuming heterogeneous artifacts in an application (or creating them for consumption) becomes a very productive experience, eliminating the need to manually cut/paste information in multiple project files in many cases.

Abstract: Embodiments of the invention introduce development tools that connect various artifacts in a database aware fashion. For example, embodiments of the invention integrate SQL query builders across multiple application development interfaces (e.g., a source code editor, XML editor, database scripting tools, etc.), significantly improving developer productivity, reducing development cost and time. Thus, the process of consuming heterogeneous artifacts in an application (or creating them for consumption) becomes a very productive experience, eliminating the need to manually cut/paste information in multiple project files in many cases.

Abstract: According to one embodiment of the present invention, a system enables control of database applications. The system comprises a computer system including a database application to provide access to a database system, and at least one processor. The computer system requests retrieval of application specific property information for the database application from a data repository, and applies the retrieved application specific property information to the database application to control operation of the database application. Embodiments of the present invention further include a method and computer program product for controlling database applications in substantially the same manner described above.

Abstract: A system and method for connection of an application program to its corresponding database in a relational database system environment. Rather than embedding connection configuration information or properties in an application program, connection configurations are stored in a connection configuration repository. The connection configuration repository is likewise stored in a database within the relational database system environment. The connection configuration information stored in the configuration repository may be updated, revised, deleted or assembled into groups/subgroups, without affecting the application programs.

Abstract: Provided are techniques for collecting client information for client applications running on a client computer, wherein the client information includes a client application identifier for each client application that issues queries to a database along with text of each of the queries that the client application issues; collecting database monitoring information that includes text of each query issued against the database and performance information for each query; combining the client information and the database monitoring information based on the text of the queries to obtain combined information that provides the client application identifier and the performance information for each of the queries; and identifying a problem query and at least one client application that has issued the problem query using the combined information.

Abstract: An apparatus, system, and method for creating and managing a data server-managed web services runtime. A generic web service runtime module and associated runtime controller are deployed on an application server. The runtime controller monitors a web services management metadata store for changes in the web service metadata defining the available data access based web services. If a change is detected, the generic web services runtime automatically updates the web service artifacts and web service endpoint interface associated with the affected web service such that the change in the web service metadata is reflected in the data access-based web service. A user manages the web services management metadata store and defines and manages data access-based web services from the database containing the web services management metadata store without interacting with the application server.

Abstract: Development tools are disclosed that connect various artifacts in a database aware fashion. For example, the development environment may integrate SQL query builders across multiple application development interfaces (e.g., a source code editor, XML editor, database scripting tools, etc.), significantly improving developer productivity, reducing development cost and time. Thus, the process of consuming heterogeneous artifacts in an application (or creating them for consumption) becomes a very productive experience, eliminating the need to manually cut/paste information in multiple project files in many cases.

Abstract: Embodiments of the invention introduce development tools that connect various artifacts in a database aware fashion. For example, embodiments of the invention integrate SQL query builders across multiple application development interfaces (e.g., a source code editor, XML editor, database scripting tools, etc.), significantly improving developer productivity, reducing development cost and time. Thus, the process of consuming heterogeneous artifacts in an application (or creating them for consumption) becomes a very productive experience, eliminating the need to manually cut/paste information in multiple project files in many cases.

Abstract: Systems, methods and articles of manufacture are disclosed for batching heterogeneous database commands. The heterogeneous database commands may include at least two database command types. Further, at least two of the heterogeneous database commands may include host variables. A request to execute the heterogeneous database commands may be received. The heterogeneous database commands may be sent to a database system for execution, responsive to the request.

Abstract: A technique is disclosed for identifying impact of database changes on an application. Given a proposed database change, affected source code is identified that is affected by the proposed database change. References to the affected source code are created and organized into a hierarchy. A user can ascertain the extent of the impact by viewing the hierarchy and by using the hierarchy to access and view the affected source code in a visually distinct manner.

Abstract: A method of accessing layers in a multi-layer software architecture including a first layer, a second layer, and a third layer. The method includes: at the third layer, publishing an interface; and at the first layer, before execution of a first function, registering a callback routine with the third layer using the interface.

Abstract: An apparatus, system, and method for creating and managing a data server-managed web services runtime. A generic web service runtime module and associated runtime controller are deployed on an application server. The runtime controller monitors a web services management metadata store for changes in the web service metadata defining the available data access based web services. If a change is detected, the generic web services runtime automatically updates the web service artifacts and web service endpoint interface associated with the affected web service such that the change in the web service metadata is reflected in the data access-based web service. A user manages the web services management metadata store and defines and manages data access-based web services from the database containing the web services management metadata store without interacting with the application server.

Abstract: An apparatus, system, and method are disclosed for providing access to a set of resources available directly to a particular class loader. The apparatus includes a request handler, a locator, an association module, and a navigation module. The request handler receives a resource identifier. The locator identifies a local resource set comprising resources available directly to a particular class loader. The resources correspond to the resource identifier. The association module associates the local resource set with the particular class loader. The navigation module locates a first resource accessible to a particular class loader based on a resource location policy. The resource location policy determines a search order of a class loader hierarchy to locate the first resource among local resource sets identified for each class loader in the class loader hierarchy. The apparatus provides access to, and navigation among, local resources of class loaders in a dynamic resource loading environment.

Abstract: Provided is an architecture for enabling business components to access middleware components in a runtime environment. A business container hosts business components and services to enable communication between the business components. A plurality of infrastructure components expose interfaces and methods to the business components, wherein the exposed interfaces and methods have names descriptive of a business domain for which the business applications are written. The infrastructure components implementation of the interfaces and methods exposed to the business components include calls to the middleware application programming interfaces (APIs) to invoke middleware APIs to cause middleware operations.

Abstract: Provided are a method, system, and program for matching client interfaces with service interfaces. A client component includes at least one client interface and a target component includes at least one service interface. A data structure for the client component associates at least one client interface in the client component with one target component. For each client interface indicated in the data structure, a determination is made as whether there is one service interface in the target component associated with the client interface that is compatible with the client interface.

Abstract: A method, apparatus, and article of manufacture for sending messages between objects in an object-oriented system. A reference attribute for a first object is defined, wherein the reference attribute refers to a second object. A message then may be sent from the first object to the second object using the reference attribute to route the message from the first object to the second object.