|Publication number||US7461070 B2|
|Application number||US 11/295,284|
|Publication date||Dec 2, 2008|
|Filing date||Dec 6, 2005|
|Priority date||Oct 14, 2005|
|Also published as||US20070088721|
|Publication number||11295284, 295284, US 7461070 B2, US 7461070B2, US-B2-7461070, US7461070 B2, US7461070B2|
|Original Assignee||Bae Systems, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (4), Referenced by (6), Classifications (10), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims priority to U.S. Provisional Application No. 60/727,188 entitled “Modular Configuration and Deployment of JDBC Resources” by Rahul Srivastava, filed Oct. 14, 2005.
Application servers such as the WebLogic server available from BEA Systems of San Jose, Calif. allow users to do a number of functions. One of the functions that can be allowed by the application servers is to provide access to a database. In one embodiment, the application servers provide Java Database Connectivity (JDBC) for connection to a database. JDBC technology is an API defined in J2EE that provides DBMS connectivity to a wide range of databases and access to other tabular data sources, such as spreadsheets or flat files. With a JDBC technology-enabled driver, a user can connect to corporate data even in a heterogeneous environment. JDBC defines data sources such as the relational databases and flat files using basic implementations, connection pooling implementations and distributed transaction implementation.
In one embodiment, Java Database Connectivity (JDBC) data sources are configurable with XML configuration files. The XML configuration files can be used to obtain configuration information for the Java Database Connectivity (JDBC) data sources.
In one embodiment, a tool can convert the XML configuration files into configuration objects for the Java Database Connectivity (JDBC) data sources. The configuration objects can be MBeans or other Java Beans. Migration to a new environment can include producing an updated XML configuration file, such as a configuration file for the production environment. A tool can be used to update the XML file by inputting new binding variables.
A tool can provide a two phase deployment of data source configuration. In one embodiment, the two-phase deployment can be done such that if the deployment of the updated configuration fails, the configuration can roll back to the previous configuration.
The XML configuration files can be locally or globally scoped. In one embodiment of the present invention, a system including Java Database Connectivity (JDBC) data sources that are configurable with XML configuration files. The XML configuration files being used to obtain configuration information for the Java Database Connectivity (JDBC) data sources. A tool can be used to modify XML configuration files to produce updated XML configuration files and; a deployment tool can be used to deploy the updated configuration in a two-phase process that rolls back to the prior configuration upon a failure of the deployment of the updated configuration. In one embodiment, the original XML configuration files contain test configurations and the updated XML configuration files contain production configurations. The XML configuration files can be converted into configuration objects for the Java Database Connectivity (JDBC) data sources. The tool can be used to update the XML file by inputting new binding variables. The XML configuration files can be locally or globally scoped.
One embodiment of the present invention is a system including a tool to create at least one XML configuration file for a Java Database Connectivity (JDBC) data source; and a component to use the XML file to configure the Java Database Connectivity (JDBC) data source. The component can convert the XML configuration files into configuration objects for the Java Database Connectivity (JDBC) data source. Migration to a new environment can include producing an updated XML configuration file. The XML configuration files can be updated by inputting new binding variables
The following description gives one non-limiting implementation of one embodiment. The discussion below gives one embodiment, but those skilled in the art will understand that other implementations of the above-described concepts can be done. Any potentially limiting language given below is to be interpreted in the context of the specific non-limiting implementation and is not meant to limit the general concepts.
The external representation and configuration of JDBC objects—Connection Pools, Data Sources, Transactional Data Sources and Multi Pools—can be consolidated into a new type of Data Source object. These new uber-data sources can be defined via a new Java Bean type (weblogicj.2ee.descriptor.wl.JDBCDataSourceBean), which in turn can conform to the new JDBC schema (weblogicj2ee.descriptor.schemas.wls90.weblogic-jdbc.xsd). These data sources can be configurable as both global- and application-scoped JDBC resources. A new configuration MBean type JDBCSystemResourceMBean can act as a container for JDBCDataSourceBeans in the WLS configuration file (“config.xml”). A new WLS-specific extension type of J2EE Module called “JDBC Module” can be defined to contain data sources configured inside a J2EE application or as a standalone J2EE module. New runtime MBean types can be created to support the new data source type and related J2EE Management Objects (JSR77).
Users can monitor application's usage of configured JDBC objects. Additional statistics can be made available for JDBC objects such as multi pools, connection pools and prepared statement caches. Application can be able to register callbacks that will get invoked before and after invocations of methods in the JDBC driver. User can be able to obtain detailed usage profiles of JDBC resources such as connection pools and prepared statement caches. User can be able to debug the usage of JDBC objects such as connections and statements. User can be able to take a Diagnostic Image of the JDBC subsystem when requested for by BEA Support. User can be able to trace the flow of an individual (“dyed”) application request through the JDBC subsystem.
A JDBC schema can be defined for JDBC. Data Source definitions will be contained inside XML documents (“descriptors”) that will conform to this schema. These descriptors can have a suffix of “-jdbc.xml”. A new Java Bean type can be defined to represent the new data source object. This Java Bean can map to the new JDBC schema being defined. A new configuration MBean type “JDBCSystemResourceMBean” can be defined to contain global-scoped data sources. A new server software specific extension type of J2EE module called “JDBC Module” can be defined to configure data sources configured as J2EE modules. Data Sources can be deployed using a two-phase deployment mechanism. JSR88 provides a scheme to resolve J2EE applications' environment-specific dependencies (binding and tunable parameters) at deployment time. JDBC subsystem can make the necessary changes to support these requirements. New runtime MBean type JDBCDataSourceRuntimeMBean can deprecate the current runtime MBean type JDBCConnectionPoolRuntimeMBean. New runtime MBean type JDBCMultiDataSourceRuntimeMBean can be added to support MultiPools.
An example of an JDBC schema is given below.
One embodiment may be implemented using a conventional general purpose or a specialized digital computer or microprocessor(s) programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art. The invention may also be implemented by the preparation of integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be readily apparent to those skilled in the art.
One embodiment includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the features presented herein. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, micro drive, and magneto-optical disks, ROMs, Rams, EPROM's, EPROM's, Drams, Rams, flash memory devices, magnetic or optical cards, Nan systems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
Stored on any one of the computer readable medium (media), the present invention includes software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention. Such software may include, but is not limited to, device drivers, operating systems, execution environments/containers, and user applications.
The foregoing description of preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to one of ordinary skill in the relevant arts. For example, steps performed in the embodiments of the invention disclosed can be performed in alternate orders, certain steps can be omitted, and additional steps can be added. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims and their equivalents.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US7032014 *||Jan 18, 2002||Apr 18, 2006||Sun Microsystems, Inc.||Service management system for configuration information|
|US7178149 *||Apr 17, 2002||Feb 13, 2007||Axeda Corporation||XML scripting of soap commands|
|US7210143 *||Mar 4, 2003||Apr 24, 2007||International Business Machines Corporation||Deployment of applications in a multitier compute infrastructure|
|US7260819 *||Feb 20, 2003||Aug 21, 2007||Bea Systems, Inc.||System and method for software application scoping|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8458670||Sep 27, 2007||Jun 4, 2013||Symantec Corporation||Automatically adding bytecode to a software application to determine network communication information|
|US8578339||Sep 26, 2007||Nov 5, 2013||Symantec Corporation||Automatically adding bytecode to a software application to determine database access information|
|US8887141||Sep 28, 2007||Nov 11, 2014||Symantec Corporation||Automatically modifying a native code module accessed from virtual machine bytecode to determine execution information|
|US20090083271 *||Sep 26, 2007||Mar 26, 2009||Brian Day||Automatically Adding Bytecode to a Software Application to Determine Database Access Information|
|US20090089749 *||Sep 27, 2007||Apr 2, 2009||Brian Day||Automatically Adding Bytecode to a Software Application to Determine Network Communication Information|
|US20090089766 *||Sep 28, 2007||Apr 2, 2009||Brian Day||Automatically Modifying a Native Code Module Accessed from Virtual Machine Bytecode to Determine Execution Information|
|U.S. Classification||1/1, 707/E17.032, 707/E17.124, 707/999.01, 707/999.104|
|Cooperative Classification||Y10S707/99945, G06F9/44505|
|European Classification||G06F17/30N, G06F17/30X3|
|Dec 6, 2005||AS||Assignment|
Owner name: BEA SYSTEMS, IC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SRIVASTAVA, RAHUL;REEL/FRAME:017331/0360
Effective date: 20051128
|Apr 6, 2006||AS||Assignment|
Owner name: BEA SYSTEMS, INC., CALIFORNIA
Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY, PREVIOUSLY RECORDED AT REEL 017331, FRAME 0360;ASSIGNOR:SRIVASTAVA, RAHUL;REEL/FRAME:017486/0319
Effective date: 20051128
|Oct 15, 2010||AS||Assignment|
Owner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BEA SYSTEMS, INC.;REEL/FRAME:025192/0244
Effective date: 20101008
|May 2, 2012||FPAY||Fee payment|
Year of fee payment: 4
|May 19, 2016||FPAY||Fee payment|
Year of fee payment: 8