US20200366751A1 - Managing dynamic configuration-based database connections using a proxy datasource - Google Patents
Managing dynamic configuration-based database connections using a proxy datasource Download PDFInfo
- Publication number
- US20200366751A1 US20200366751A1 US16/411,873 US201916411873A US2020366751A1 US 20200366751 A1 US20200366751 A1 US 20200366751A1 US 201916411873 A US201916411873 A US 201916411873A US 2020366751 A1 US2020366751 A1 US 2020366751A1
- Authority
- US
- United States
- Prior art keywords
- datasource
- proxy
- computing device
- database
- concrete
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H04L67/2804—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0866—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches for peripheral storage systems, e.g. disk cache
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0806—Multiuser, multiprocessor or multiprocessing cache systems
- G06F12/0808—Multiuser, multiprocessor or multiprocessing cache systems with cache invalidating means
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/545—Interprogram communication where tasks reside in different layers, e.g. user- and kernel-space
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1021—Server selection for load balancing based on client or server locations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H04L67/327—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/46—Caching storage objects of specific type in disk cache
- G06F2212/465—Structured object, e.g. database record
Abstract
Systems for managing dynamic configuration-based database connections using a proxy datasource are disclosed. In embodiments, a computer program product is provided including a computer readable storage medium having program instructions embodied therewith. The program instructions are executable by a computing device to cause the computing device to: send, by a software application of the computing device, a request for a connection to a first database to a proxy datasource of the computing device, wherein the request includes a database identifier and configuration data; pass, by a first concrete datasource of the computing device, a connection to the first database to the proxy datasource; return, by the proxy datasource of the computing device, the connection to the software application; and access, by the software application of the computing device, the first database via the connection.
Description
- The present invention relates generally to managing datasources and, more particularly, to managing dynamic configuration-based database connections using a proxy datasource.
- A datasource is a collection of information about a database such as the type of database, the location of the database, or credentials that might be associated with the database. A datasource is utilized to configure and access database connections between a server (or an application on the server) and a database. An application container is a controlling element for an application instance that runs within an application container environment. Within an application server/application container environment, datasources are typically configured statically via a deployment descriptor. Such datasources usually include connection information (e.g., database server hostname, port number, database name, etc.), as well as additional properties to control the behavior of database connections served up by the datasource (e.g. read timeout, write timeout, automatic client re-route properties, etc.).
- In an aspect of the invention, a computer-implemented method includes: receiving, by a proxy datasource of a computing device, a connection request for a connection to a database from a software application of the computing device, wherein the software application is in an application container environment; obtaining, by the proxy datasource of the computing device, configuration data associated with the connection request; creating, by the proxy datasource of the computing device, a concrete datasource according to the configuration data; and returning, by the proxy datasource of the computing device, the connection to the database to the software application.
- In another aspect of the invention, there is a computer program product including a computer readable storage medium having program instructions embodied therewith. The program instructions are executable by a computing device to cause the computing device to: send, by a software application of the computing device, a request for a connection to a first database to a proxy datasource of the computing device, wherein the request includes a database identifier and configuration data; pass, by a first datasource of the computing device, a connection to the first database to the proxy datasource; return, by the proxy datasource of the computing device, the connection to the software application; and access, by the software application of the computing device, the database via the connection.
- In another aspect of the invention, there is a system including a processor, a computer readable memory and a computer readable storage medium associated with a computing device. The system further includes: program instructions to send, by a software application of the computing device, a request to a proxy datasource of the computing device for a connection to a first database, wherein the request includes a database identifier and configuration data; program instructions to instantiate, by the proxy datasource of the computing device, a first concrete datasource for the first database according to the configuration data; program instructions to pass, by the proxy datasource of the computing device, a connection to the first database to the proxy datasource; program instructions to return, by the proxy datasource of the computing device, the connection to the software application; and program instructions to access, by the software application of the computing device, the database via the connection, wherein the program instructions are stored on the computer readable storage medium for execution by the processor via the computer readable memory.
- The present invention is described in the detailed description which follows, in reference to the noted plurality of drawings by way of non-limiting examples of exemplary embodiments of the present invention.
-
FIG. 1 depicts a computing infrastructure according to an embodiment of the present invention. -
FIG. 2 is an exemplary diagram of a static datasource configuration for managing connections between a software application and a database. -
FIG. 3 shows an exemplary environment in accordance with aspects of the invention. -
FIG. 4 shows a flowchart of steps of an exemplary method for dynamic configuration-based database connections with software applications utilizing a proxy datasource in accordance with embodiments of the invention. -
FIG. 5 is an exemplary block diagram illustrating the method ofFIG. 4 in accordance with aspects of the invention. -
FIGS. 6A and 6B show a flowchart of steps of an exemplary recovery method in accordance with aspects of the invention. - The present invention relates generally to managing datasources and, more particularly, to managing dynamic configuration-based database connections using a proxy datasource. In embodiments, a proxy datasource implementation is utilized to allow new database connections to be configured for use by an application without the need to restart the application. In implementations, the proxy datasource is defined to the application server/application container environment through the use of a single static datasource definition. This proxy datasource implementation then uses a configuration-based approach for managing any number of concrete datasources. In aspects, an application obtains database connections by using the proxy datasource in much the same way that it would use a static datasource, but also specifies a datasource identifier that acts as a key into the configuration of database connections (e.g., first and second databases).
- Since datasources are typically configured statically, the configuration of any new database connections that might be needed by the application would require a restart of the application. This restart requirement can be problematic in situations in which a server-based application needs to be “always on”.
- Advantageously, embodiments of the invention provide improvements to a computing device and to the technical field of implementing configuration-based database connections. More specifically, embodiments of the invention provide dynamic configuration-based management of concrete datasources and the proxy's dynamic management of database connections to these non-static datasources, which prevents the need to configure static datasources with the application container environment. Additionally, embodiments of the invention enable eXtended Architecture (XA) transaction recovery functionality, which allows the entire collection of concrete datasources to appear as a single XA datasource to the application container when it triggers XA transaction recovery operations.
- The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
- The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
- Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
- Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
- Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
- These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
- The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
- The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
- Referring now to
FIG. 1 , a schematic of an example of a computing infrastructure is shown.Computing infrastructure 10 is only one example of a suitable computing infrastructure and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention described herein. Regardless,computing infrastructure 10 is capable of being implemented and/or performing any of the functionality set forth hereinabove. - In
computing infrastructure 10 there is a computer system (or server) 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use withcomputer system 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like. -
Computer system 12 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types.Computer system 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices. - As shown in
FIG. 1 ,computer system 12 incomputing infrastructure 10 is shown in the form of a general-purpose computing device. The components ofcomputer system 12 may include, but are not limited to, one or more processors or processing units (e.g., CPU) 16, asystem memory 28, and abus 18 that couples various system components includingsystem memory 28 toprocessor 16. -
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus. -
Computer system 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible bycomputer system 12, and it includes both volatile and non-volatile media, removable and non-removable media. -
System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/orcache memory 32.Computer system 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only,storage system 34 can be provided for reading from and writing to a nonremovable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected tobus 18 by one or more data media interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention. - Program/
utility 40, having a set (at least one) ofprogram modules 42, may be stored inmemory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment.Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein. -
Computer system 12 may also communicate with one or moreexternal devices 14 such as a keyboard, a pointing device, adisplay 24, etc.; one or more devices that enable a user to interact withcomputer system 12; and/or any devices (e.g., network card, modem, etc.) that enablecomputer system 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet,computer system 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) vianetwork adapter 20. As depicted,network adapter 20 communicates with the other components ofcomputer system 12 viabus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction withcomputer system 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc. -
FIG. 2 is an exemplary diagram of a static datasource configuration for managing connections between a software application and a database. The configuration ofFIG. 2 may be implemented by the computer system 12 (e.g., server) ofFIG. 1 .FIG. 2 represents a scenario wherein an application (MyApp) 200 wishes to connect to one or more databases. - As illustrated in
FIG. 2 , when an application (MyApp) 200 desires a connection to a database 206 (MyDB1), theapplication 200 initially requests a handle (a reference based on the configuration data 201) to adatasource 202 from an application container represented at 204. Thedatasource 202 is a concrete datasource; meaning that it is a real instance of a datasource comprising a collection of information about a database, which may be utilized to configure and access database connections between a server (or an application on the server) and the database. The term application container as used herein refers to a controlling element for an application instance that runs within an application container environment. Theapplication container 204 instantiates (creates), as needed, thedatasource 202 for thedatabase 206. In the example ofFIG. 2 , thedatasource 202 includes connection information (e.g., database server hostname, port number, database name, etc.), as well as additional properties to control the behavior of the database connections served up by the datasource 202 (e.g., read timeout, write timeout, automatic client re-route properties, etc.). - In the example of
FIG. 2 , theapplication container 204 provides the handle for thedatabase 206 to theapplication 200, and theapplication 200 utilizes the handle to send a request to thedatasource 202 for a connection to thedatabase 206. Thedatasource 202 passes a connection to thedatabase 206, and returns it to theapplication 200. Theapplication 200 then interacts with the database 206 (e.g., accesses information in the database 206) via the connection created by thedatasource 202 and returned to theapplication 200 by thedatasource 202. - Since the
datasource 202 is configured statically, the configuration of any new database connections that might be needed by theapplication 200 would require a restart of theapplication 200. This restart requirement can be problematic in situations in which theapplication 200 needs to be “always on” or in which it is undesirable to restart theapplication 200. For example, if a user of theapplication 200 needed to introduce a new datasource to connect to an additional database MyDB2 (not depicted), then the static configuration would be updated to include theconfiguration data 208 for MyDB2. After the application container's static datasource configuration is updated to include theconfiguration data 208, theapplication 200 would need to be restarted in order to allow theapplication 200 to connect to the new database MyDB2. -
FIG. 3 shows an exemplary environment in accordance with aspects of the invention. The environment includesnetwork 50 connecting aserver 60 to one or more databases represented at 62 and 63. Theserver 60 may comprise thecomputer system 12 ofFIG. 1 , and may be connected to thenetwork 50 via thenetwork adapter 20 ofFIG. 1 . - The
network 20 may be any suitable communication network or combination of networks, such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet). The first andsecond databases server 60 or store information from theserver 60. - Still referring to
FIG. 3 , theserver 60 may include one or more program modules (e.g.,program module 42 ofFIG. 1 ) configured to perform one or more functions described herein. In embodiments, theserver 60 includes anapplication container environment 72 including one or more software applications represented byapplication 74. The term application container environment refers to a computing environment utilizing application containers (e.g., application container 73) to run desired software applications (e.g., application 74). The term application container as used herein refers to a controlling element for an application instance that runs within an application container environment. Application containers include runtime components, such as files, environment variables and libraries necessary to run the desired software. In implementations, theapplication container environment 72 further includes atransaction manager 75 configured to manage eXtended Architecture (XA) recovery functions. - In implementations, the
server 60 further comprises a proxy datasource module 76 (hereafter proxy datasource 76), configured to create concrete datasources (e.g., first and second datasources 77 and 78), and act as an intermediary between a software application (e.g., application 74) and the concrete datasources to facilitate the establishment of a connection between the software application and a database (e.g.,first database 80 or second database 81). The term proxy datasource as used herein refers to computer software that acts as a proxy to concrete (real) datasources so that the concrete datasources can be managed dynamically as configuration changes are made, without impacting the software application relying on the concrete datasource for a database connection. For example, in the case where a new database is added to theapplication container environment 72, the configuration information for an existing database (e.g., first database 80) may be changed or removed from stored configuration data. The first and second datasources 77 and 78 are concrete datasources utilized to configure and access database connections between a server or an application on the server (e.g., application 74) and a local or remote database (e.g., local first andsecond databases second database 62 and 63). - In embodiments, the
sever 60 may include additional or fewer components than those shown inFIG. 3 . In embodiments, separate components may be integrated into a single computing component or module. Additionally, or alternatively, a single component may be implemented as multiple computing components or modules. -
FIG. 4 shows a flowchart of an exemplary method in accordance with aspects of the invention. More specifically,FIG. 4 illustrates a method for dynamic configuration-based database connections with software applications utilizing a proxy datasource. Steps of the method ofFIG. 4 may be performed in the environment illustrated inFIG. 3 , and are described with reference to elements shown inFIG. 3 . - At
step 400, theapplication 74 sends a request to theapplication container 73 for a handle to theproxy datasource 76. The request is sent based on the desire to connect theapplication 74 to a first database (e.g., thefirst database 62 or the first database 80). For the purpose ofFIG. 4 , thefirst database 80 is referenced hereafter. In contrast to the dynamically configurable method ofFIG. 4 which requests a handle to aproxy datasource 76, the static datasource configuration ofFIG. 2 requests a handle to a concrete datasource (e.g.,datasource 202 ofFIG. 2 ). - At
step 401, theapplication container 73 provides theapplication 74 with the handle to theproxy datasource 76 in response to the request ofstep 400. In contrast to the method ofFIG. 4 , in static datasource configurations such as the one represented inFIG. 2 , a handle is returned to a concrete datasource (e.g.,datasource 202 ofFIG. 2 ) rather than a proxy datasource (e.g.,proxy datasource 76 ofFIG. 4 ). - At
step 402, theapplication 74 sends a request to theproxy datasource 76 for a connection to the first database 80 (i.e., a request for a datasource) based on the handle received atstep 401. In implementations, the request includes a datasource or database identifier (e.g., “db1”) identifying thefirst database 80, and configuration data. In aspects, the datasource or database identifier is specified through a specialized use of existing method parameters (e.g., DataSource.getConnection(String, String)), through a thread-local structure, or other method. The manner in which an application specifies the datasource or database identifier to theproxy datasource 76 when obtaining a connection to thefirst database 80 may vary depending on a particular implementation. In contrast to the method ofFIG. 4 , in static datasource configurations such as the one represented inFIG. 2 , a request for a connection to a database is sent directly to a concrete datasource (e.g.,datasource 202 ofFIG. 2 ). - At
step 403, theproxy datasource 76 instantiates a first datasource 77 (concrete datasource) for thefirst database 80 as needed (i.e., if thefirst datasource 77 has not yet been created/cached) in response to the request ofstep 402. In implementations, thefirst datasource 77 is created based on the configuration data of the request ofstep 402. - At
step 404, theproxy datasource 76 causes thefirst datasource 77 to pass the proxy datasource 76 a connection to thefirst database 80, and theproxy datasource 76 then returns the connection to theapplication 74. Step 404 may be implemented after creation of thefirst datasource 77 atstep 403, or when thefirst datasource 77 is already created, in response to the request for connection ofstep 402. In contrast to the method ofFIG. 4 , in static datasource configurations such as the one represented inFIG. 2 , a concrete datasource (e.g.,datasource 202 ofFIG. 2 ) itself returns a database connection to the application (e.g.,application 200 ofFIG. 2 ). - At
step 405, theapplication 74 interacts with thefirst database 80 via the connection created by thefirst datasource 77 and returned to theapplication 74 by theproxy datasource 76. Theapplication 74 may interact with thefirst database 80 to access or obtain data from thedatabase 80, or to store data in thefirst database 80. - In embodiments, the
application 74 connects to a plurality of databases utilizing theproxy datasource 76. In this way, new database configurations may be implemented within theapplication container environment 72 without the need for restarting theapplication 74 orserver 60 to instantiate a new datasource for the new database. - In one example at
step 406, theapplication 74 sends a request to theproxy datasource 76 for a connection to the second database 81 (i.e., a request for a datasource) based on the handle received atstep 401. In implementations, the request includes a datasource or database identifier (e.g., “db2”) identifying thesecond database 81, and configuration data. - At
step 407, theproxy datasource 76 instantiates (creates) thesecond datasource 78 for thesecond database 81 as needed (i.e., if thesecond datasource 78 has not yet been created/cached) in response to the request ofstep 406. In implementations, thesecond datasource 78 is created based on the configuration data of the request ofstep 406. - At
step 408, theproxy datasource 76 causes thesecond datasource 78 to pass the proxy datasource 76 a connection to thesecond database 81, and theproxy datasource 76 returns the connection to theapplication 74. In contrast to the method ofFIG. 4 , in static datasource configurations such as the one represented inFIG. 2 , a concrete datasource creates a connection to a database and directly returns the connection to an application. - At
step 409, theapplication 74 interacts with thesecond database 81 via the connection created by thesecond datasource 78 and returned to theapplication 74 by theproxy datasource 76. Theapplication 74 may interact with thesecond database 81 to obtain or access data in thesecond database 81, or to store data in thesecond database 81, for example. - In embodiments, once the
proxy datasource 76 mechanisms described above is in place, the proxy datasource' s configuration is updated dynamically to configure a new concrete datasource. Theapplication 74 then immediately starts to request connections from this new datasource without the need to restart theapplication 74 or the application server/container environment, since it is theproxy datasource 76 which deals with the underlying datasource configuration and manages the concrete datasource instances, as opposed to the application server/application container 73. Implementations of theproxy datasource 76 enable theserver 60 to reload configuration properties as needed on the fly in order to recognize and use any new configuration data. In implementations, a robust implementation of this dynamic configuration feature includes the ability of theproxy datasource 76 to detect changes to existing configuration information and react to those changes by marking any cached concrete datasource instances (affected by the configuration changes) for disposal so that any subsequent connection requests associated with any changed datasource configurations would result in instantiating a new instance of the concrete datasource using the new configuration information. - Accordingly in implementations, at
step 410, when the configuration data of the connection request (request ofsteps 402 or 406) comprises new configuration data, theproxy datasource 76 identifies the change in configuration data and marks cached datasource instances for disposal. Thereafter theproxy datasource 76 instantiates a new datasource based on the new configuration data. -
FIG. 5 is an exemplary block diagram illustrating the method ofFIG. 4 . The configuration ofFIG. 5 may be implemented by the computer system 12 (e.g., server) ofFIG. 1 .FIG. 5 represents a scenario wherein an application (MyApp) 74 wishes to connect to one or more databases. - With reference to
FIG. 5 , an application (MyApp) 74 initially requests a handle (a reference based on the configuration data 500) to aproxy datasource 76 from an application container represented at 73, in accordance withstep 400 ofFIG. 4 . In the example ofFIG. 5 ,configuration data 500 includes “<dataSource jndiName=“jdbc/ProxyDS” . . . />”. Theapplication container 73 provides the handle (e.g., “jdbc/ProxyDS”) to theapplication 74 in accordance withstep 401 ofFIG. 4 , and theapplication 74 sends a request to theproxy datasource 76 for a connection to a first database 80 (MyDB1) including a database identifier (e.g., “db1”) and configuration data in accordance withstep 402 ofFIG. 4 . In the example shown, theapplication 74 invokes getConnection (“db1”). - In the scenario of
FIG. 5 , a concrete datasource for thefirst database 80 has not yet been created. Theproxy datasource 76 creates thefirst datasource 77 for the first database 80 (MyDB1) based on the configuration data in the request, in accordance withstep 403 ofFIG. 4 . In one example,configuration data 502 for thefirst database 80 includes the following: . . . , “db1”:{“serverName”:“dbhost1”, “portNumber”:50000, “databaseName”:“MyDB1”}. Thefirst datasource 77 passes, to theproxy datasource 76, a connection to thefirst database 80 and theproxy datasource 76 returns the connection to theapplication 74, in accordance withstep 404 ofFIG. 4 . Theapplication 74 then interacts with thefirst database 80 to access data from thefirst database 80 and/or store data in thefirst database 80, in accordance withstep 405 ofFIG. 4 . - In the exemplary scenario of
FIG. 4 , theapplication 74 wishes to connect to asecond database 81 for which a concrete datasource has not yet been created. Accordingly, theapplication 74 sends a request to theproxy datasource 76 for a connection to the second database 81 (MyDB2) including a database identifier (e.g., “db2”) and configuration data in accordance withstep 406 ofFIG. 4 . In one example, theapplication 74 invokes getConnection(“db2”). Theproxy datasource 76 generates thesecond datasource 78 for the second database 81 (MyDB2) based on the configuration data in the request, in accordance withstep 407 ofFIG. 4 . In one example,configuration data 503 for thesecond database 81 includes the following: db2”:{“serverName”:“dbhost2”, “portNumber”:50000, “databaseName”:“MyDB2”}. Thesecond datasource 78 passes, to theproxy datasource 76, a connection to thesecond database 81 and theproxy datasource 76 returns the connection to theapplication 74, in accordance withstep 408 ofFIG. 4 . Theapplication 74 then interacts with thesecond database 81 to obtain data from thesecond database 81 and/or store data in thesecond database 81, in accordance withstep 409 ofFIG. 4 . - Based on the above, implementations of the invention utilize the
proxy datasource 76 as a proxy to concrete (real) datasources (e.g., first and second datasources 77 and 78) so that the concrete datasources can be managed dynamically as configuration changes are made, without impacting the application (e.g., application 74) wishing to utilize the datasource. A configuration change may occur, for example when a new database is added, and the configuration information for an existing database is changed or removed from the configuration. In implementations, part of the management of these concrete datasources involves an eXtended Architecture (XA) transaction management façade that is provided by theproxy datasource 76 implementation. The term XA refers to a two-phase commit protocol that is natively supported by many database and transaction monitors. In aspects, the XA transaction management façade appears as a single XA resource to theapplication container 73 which handles XA recovery steps triggered by atransaction manager 75. In implementations, the present invention provides a mechanism for XA recovery, wherein, during a recovery phase, theproxy datasource 76 provides thetransaction manager 75 with a single logical XA resource that supplies recoverable Xids (identifiers that identify each transaction branch in XA transactions) for a multiplicity of XA resources, enabling thetransaction manager 75 to agnostically recover transactional operations across multiple distinct datasources. An Xid is comprised of a global transaction identification (ID) that identifies a global transaction that a transaction will be a part of, a global transaction format ID, and a branch qualifier ID that uniquely identifies the transaction branch. - In situations where static datasources are utilized, such as the one depicted in
FIG. 2 , XA recovery transactions are handled by the application container (e.g.,application container 204 ofFIG. 2 ). However, in embodiments of the present invention utilizing proxy datasources, the application container (e.g., 73) is unaware of concrete datasources in use. Accordingly, XA recovery transactions utilize the proxy datasource to implement recovery transactions, based on the proxy datasources knowledge of existing concrete datasources. - In XA implementations, the
transaction manager 75 commits distributed branches of a global transaction using a two-phase commit protocol. In phase one, thetransaction manager 75 directs each resource manager (not shown) to prepare to commit, which is to verify and guarantee it can commit its respective branch of the global transaction. If a resource manager cannot commit its branch, thetransaction manager 75 rolls back the entire transaction in phase two. In phase two, thetransaction manager 75 either directs each resource manager to commit its branch or, if a resource manager reported it was unable to commit in phase one, rolls back the global transaction. In implementations, when a database is loaded from disk to recover after a failure or unexpected termination, any global transactions that were prepared but not committed are left pending, or in doubt. For recovery, thetransaction manager 75 calls recover method of each XA resource. -
FIGS. 6A and 6B show a flowchart of an exemplary method in accordance with aspects of the invention. More specifically,FIGS. 6A and 6B illustrate an exemplary method for XA recovery utilizing a proxy datasource of the invention. Steps of the method ofFIGS. 6A and 6B may be performed in the environment illustrated inFIG. 3 , and are described with reference to elements shown inFIG. 3 . - At
step 600, thetransaction manager 75 reads a transaction recovery log stored by theserver 60. Existing procedures for reading transaction recovery logs may be utilized in implementations ofstep 600. - At
step 601, thetransaction manager 75 finds an entry in the recovery log for an in-doubt transaction, wherein the proxy datasource is a participating resource in the in-doubt transaction. In contrast to the embodiment ofFIGS. 6A and 6B , in exemplary static datasource configurations such as the one depicted inFIG. 2 , the recovery log would list a concrete datasource as a participating resource. - At
step 602, thetransaction manager 75 requests an XA resource from theproxy datasource 76. In this configuration, the XA resource is a proxy XA resource, wherein theproxy datasource 76 provides thetransaction manager 75 with the proxy XA resource. - At
step 603, thetransaction manager 75 queries the proxy XA resource for recoverable Xids. - At
step 604, the proxy XA resource obtains a concrete XA resource from each available concrete datasource (e.g., thefirst datasource 77 and the second datasource 78). - At
step 605, the proxy XA resource requests recoverable Xids from each of the concrete XA resources. - At
step 606, the proxy XA resource builds a conglomerate list of recoverable Xids across all concrete XA resources and supplies this list to thetransaction manager 75. - At
step 607, thetransaction manager 75 identifies the Xids for the in-doubt transaction from its entry in the recovery log. - At
step 608, thetransaction manager 75 matches up each Xid needing recovery with the XA resource that reported the Xid as recoverable. - At
step 609, thetransaction manager 75 requests, for each Xid needing recovery, the corresponding proxy XA resource to prepare that Xid for commit. - At 610, the corresponding proxy XA resources of
step 609 each receive the respective request to prepare the Xid for commit, and use the Xid to identify a respective concrete XA resource. - At
step 611, each of the corresponding proxy XA resources ofstep 610 delegate the prepare operation to the concrete XA resources identified atstep 610. - At
step 612, thetransaction manager 75 requests, for each Xid needing recovery, the corresponding proxy XA resource to commit the transaction branch with the Xid. - At
step 613, each of the corresponding proxy XA resources ofstep 612 receives a respective request to commit the transaction branch with the Xid and uses the Xid to identify the respective concrete XA resource. - At
step 614, each of the corresponding XA resources ofstep 613 delegates the commit operation to the concrete XA resources identified atstep 613. - At
step 615, theserver 60 successfully recovers the transaction. The above method steps are implemented for the commit path in XA resource recovery, however, the above-identified steps may be utilized for the rollback path instead, wherein the rollback operation is substituted for the commit operation. - Thus, embodiments of the invention enable the
server 60 to perform eXtended Architecture (XA) recovery during a recovery phase, wherein the proxy datasource provides to a transaction manager of the computing device a single logical XA resource that supplies recoverable Xids for multiple XA resources, enabling the transaction manager to recover transactional operations across the first concrete datasource and a second concrete datasource, wherein the first and second concrete datasources are represented by the proxy datasource. In such embodiments, the concrete datasources are managed by the proxy datasource so that thetransaction manager 75 only really knows about theproxy datasource 76 while the concrete datasources (e.g.,first datasource 77 and second datasource 78) are largely hidden from thetransaction manager 75. In embodiments, in addition to the concrete datasources that are managed by the proxy datasource (and essentially hidden from the transaction manager's view), other transactional resources may be recovered by thetransaction manager 75. Thus, apart from the concrete datasources (e.g.,first datasource 77 and second datasource 78) being managed by theproxy datasource 76, it is possible that other resources (not related to the proxy datasource or the concrete datasources) can be participants in transactions being recovered. Accordingly, embodiments of the invention enable theserver 60 to recover transactional operations across: 1) the two or more concrete datasources which are represented (or managed) by theproxy datasource 76; and 2) any other transactional resources that happen to also be a participant in the transaction being recovered. - In embodiments, a service provider could offer to perform the processes described herein. In this case, the service provider can create, maintain, deploy, support, etc., the computer infrastructure that performs the process steps of the invention for one or more customers. These customers may be, for example, any business that uses technology. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
- In still another embodiment, the invention provides a computer-implemented method for implementing dynamic, configuration-based database connection in a server/application container environment. In this case, a computer infrastructure, such as computer system 12 (
FIG. 1 ), can be provided and one or more systems for performing the processes of the invention can be obtained (e.g., created, purchased, used, modified, etc.) and deployed to the computer infrastructure. To this extent, the deployment of a system can comprise one or more of: (1) installing program code on a computing device, such as computer system 12 (as shown inFIG. 1 ), from a computer-readable medium; (2) adding one or more computing devices to the computer infrastructure; and (3) incorporating and/or modifying one or more existing systems of the computer infrastructure to enable the computer infrastructure to perform the processes of the invention. - One exemplary computer-implemented method includes: receiving, by a proxy datasource, a request from an application for a connection to a specific datasource; reading, by the proxy datasource, configuration data associated with the requested connection; instantiating and configuring, by the proxy datasource, a concrete datasource implementation according to the configuration data; and returning, by the proxy datasource, the requested connection to the application. In implementations, the configuration data is updated dynamically to configure a new concrete datasource without restarting the application server/container environment. In aspects, the method further includes identifying, by the proxy datasource, a change to the configuration data; and marking cached concrete datasource instances affected by the change for disposal, such that new requests for datasources affected by the change result in instantiating a new instance of a concrete datasource.
- The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (21)
1-7. (canceled)
8. A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a computing device to cause the computing device to:
obtain, by a software application of the computing device, a handle to a proxy datasource from an application container in response to a request for the handle to the proxy datasource, wherein the proxy datasource acts as a proxy to one or more concrete data sources and stores configuration data associated with one or more databases;
send, by the software application of the computing device, a request for a connection to a first database to the proxy datasource of the computing device based on the handle, wherein the request includes a database identifier identifying the first database and configuration data associated with the first database;
pass, by a first concrete datasource of the computing device, a connection to the first database to the proxy datasource;
return, by the proxy datasource of the computing device, the connection to the software application, whereby the proxy datasource acts as an intermediary between the software application and the first concrete datasource to establish a connection between the software application and the first concrete datasource; and
access, by the software application of the computing device, the first database via the connection.
9. The computer program product of claim 8 , wherein the program instructions further cause the computing device to:
determine that the first concrete datasource has not been created; and
instantiate, by the proxy datasource of the computing device, the first concrete datasource for the first database according to the configuration data upon determining that the first concrete datasource has not been created.
10. The computer program product of claim 8 , wherein the program instructions further cause the computing device to dynamically update stored configuration data of the proxy datasource to configure a new datasource without restarting the software application or the computing device.
11. The computer program product of claim 8 , wherein the program instructions further cause the computing device to:
identify, by the proxy datasource of the computing device, a change to the configuration data; and
mark for disposal cached datasource instances affected by the change to the configuration data.
12. The computer program product of claim 11 , wherein the program instructions further cause the computing device to:
receive, by the proxy datasource of the computing device, a new request for a database connection to a second database, wherein the change to the configuration data affects the new request; and
instantiate, by the proxy datasource of the computing device, a new concrete datasource by the proxy datasource in response to the new request.
13. The computer program product of claim 8 , wherein the program instructions further cause the computing device to:
request, by the software application of the computing device, the handle to the proxy datasource from the application container of the computing device; and
provide, by the application container of the computing device, the handle to the software application.
14. The computer program product of claim 8 , wherein the program instructions further cause the computing device to: perform eXtended Architecture (XA) recovery during a recovery phase, wherein the proxy datasource provides to a transaction manager of the computing device a single logical XA resource that supplies recoverable Xids for multiple XA resources, enabling the transaction manager to recover transactional operations across the first concrete datasource and a second concrete datasource, wherein the first and second concrete datasources are represented by the proxy datasource.
15. A system comprising:
a processor, a computer readable memory and a computer readable storage medium associated with a computing device;
program instructions to obtain, by a software application of the computing device, a handle to a proxy datasource from an application container in response to a request for the handle to the proxy datasource, wherein the proxy datasource acts as a proxy to multiple concrete data sources and stores configuration data associated with multiple databases;
program instructions to send, by the software application of the computing device, a request to the proxy datasource of the computing device for a connection to a first database based on the handle, wherein the request includes a database identifier and configuration data associated with the first database;
program instructions to instantiate, by the proxy datasource of the computing device, a first concrete datasource for the first database according to the configuration data associated with the first database;
program instructions to pass, by the proxy datasource of the computing device, a connection to the first database to the proxy datasource;
program instructions to return, by the proxy datasource of the computing device, the connection to the software application, whereby the proxy datasource acts as an intermediary between the software application and the first concrete datasource to establish a connection between the software application and the first concrete datasource; and
program instructions to access, by the software application of the computing device, the database via the connection,
wherein the program instructions are stored on the computer readable storage medium for execution by the processor via the computer readable memory.
16. The system of claim 15 , further comprising program instructions to dynamically update stored configuration data of the proxy datasource to configure a new concrete datasource to connect the software application to a second database without restarting the software application or the computing device.
17. The system of claim 15 , further comprising:
program instructions to identify, by the proxy datasource of the computing device, a change to the configuration data; and
program instructions to mark for disposal cached datasource instances affected by the change to the configuration data.
18. The system of claim 17 , further comprising:
program instructions to receive, by the proxy datasource of the computing device, a new request for a database connection to a second database, wherein the change to the configuration data affects the new request; and
program instructions to instantiate, by the proxy datasource, a new concrete datasource by the proxy datasource in response to the new request.
19. The system of claim 15 , further comprising:
program instructions to request, by the software application of the computing device, the handle to the proxy datasource from the application container of the computing device; and
program instructions to provide, by the application container of the computing device, the handle to the software application.
20. The system of claim 15 , further comprising program instructions to perform eXtended Architecture (XA) recovery during a recovery phase, wherein the proxy datasource provides to a transaction manager of the computing device a single logical XA resource that supplies recoverable Xids for multiple XA resources, enabling the transaction manager to recover transactional operations across the first concrete datasource and a second concrete datasource, wherein the first and second concrete datasources are represented by the proxy datasource.
21. The computer program product of claim 8 , wherein the proxy datasource acts as a proxy to multiple concrete datasources and stores configuration data associated with multiple databases.
22. The computer program product of claim 8 , wherein the program instructions further cause the computing device to:
store, by the proxy datasource of the computing device, the configuration data associated with the first database as stored configuration data;
instantiate, by the proxy datasource of the computing device, a new concrete datasource by the proxy datasource in response to the new request; and
update dynamically, by the proxy datasource of the computing device, the stored configuration data based on the new concrete datasource.
23. The computer program product of claim 8 , wherein the program instructions further cause the computing device to:
identify, by the proxy datasource of the computing device, a change to the configuration data associated with the first database;
mark for disposal cached datasource instances affected by the change to the configuration data associated with the first database; and
provide, by the proxy datasource, a single logical eXtended Architecture (XA) resource the supplies recoverable Xids for multiple XA resources to a transaction manager of the application container, whereby the transaction manager is enabled to agnostically recover transactional operations across multiple concrete datasources.
24. The computer program product of claim 8 , wherein the handle is a reference based on the configuration data.
25. The system of claim 15 , further comprising:
program instructions to store, by the proxy datasource of the computing device, the configuration data associated with the first database as stored configuration data;
program instructions to instantiate, by the proxy datasource of the computing device, a new concrete datasource by the proxy datasource in response to the new request; and
program instructions to update dynamically, by the proxy datasource of the computing device, the stored configuration data based on the new concrete datasource.
26. The system of claim 15 , further comprising:
program instructions to identify, by the proxy datasource of the computing device, a change to the configuration data associated with the first database;
program instructions to mark for disposal cached datasource instances affected by the change to the configuration data associated with the first database; and
program instructions to provide, by the proxy datasource, a single logical eXtended Architecture (XA) resource that supplies recoverable Xids for multiple XA resources to a transaction manager of the application container, whereby the transaction manager is enabled to agnostically recover transactional operations across the multiple concrete datasources.
27. The system of claim 15 , wherein the handle is a reference based on the configuration data.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/411,873 US10938933B2 (en) | 2019-05-14 | 2019-05-14 | Managing dynamic configuration-based database connections using a proxy datasource |
US16/509,770 US10938934B2 (en) | 2019-05-14 | 2019-07-12 | Managing dynamic configuration-based database connections using a proxy datasource |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/411,873 US10938933B2 (en) | 2019-05-14 | 2019-05-14 | Managing dynamic configuration-based database connections using a proxy datasource |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/509,770 Continuation US10938934B2 (en) | 2019-05-14 | 2019-07-12 | Managing dynamic configuration-based database connections using a proxy datasource |
Publications (2)
Publication Number | Publication Date |
---|---|
US20200366751A1 true US20200366751A1 (en) | 2020-11-19 |
US10938933B2 US10938933B2 (en) | 2021-03-02 |
Family
ID=73230830
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/411,873 Active US10938933B2 (en) | 2019-05-14 | 2019-05-14 | Managing dynamic configuration-based database connections using a proxy datasource |
US16/509,770 Active US10938934B2 (en) | 2019-05-14 | 2019-07-12 | Managing dynamic configuration-based database connections using a proxy datasource |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/509,770 Active US10938934B2 (en) | 2019-05-14 | 2019-07-12 | Managing dynamic configuration-based database connections using a proxy datasource |
Country Status (1)
Country | Link |
---|---|
US (2) | US10938933B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113055498A (en) * | 2021-05-26 | 2021-06-29 | 天聚地合(苏州)数据股份有限公司 | Data source access method, device, storage medium and equipment |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8145759B2 (en) * | 2002-11-04 | 2012-03-27 | Oracle America, Inc. | Dynamically configurable resource pool |
US7134008B2 (en) * | 2003-09-04 | 2006-11-07 | Sun Microsystems, Inc. | Utility for configuring and verifying data sources |
US7519814B2 (en) * | 2003-09-15 | 2009-04-14 | Trigence Corp. | System for containerization of application sets |
US8429609B2 (en) * | 2004-05-21 | 2013-04-23 | Ca, Inc. | Method and system for web-based enterprise change and configuration management reports |
US7558799B2 (en) * | 2004-06-01 | 2009-07-07 | Microsoft Corporation | Method, system, and apparatus for discovering and connecting to data sources |
US7325003B2 (en) | 2004-07-02 | 2008-01-29 | Cognos Incorporated | Method and system for mapping datasources in a metadata model |
WO2006110983A1 (en) * | 2005-04-18 | 2006-10-26 | Research In Motion Limited | System and method for accessing multiple data sources by mobile applications |
US20080127055A1 (en) * | 2006-09-07 | 2008-05-29 | Microsoft Corporation | Application proxy |
US8234240B2 (en) | 2007-04-26 | 2012-07-31 | Microsoft Corporation | Framework for providing metrics from any datasource |
US9098548B1 (en) | 2010-06-14 | 2015-08-04 | Open Invention Network, Llc | Method and apparatus for accessing a data source from a client using a driver |
US8756329B2 (en) | 2010-09-15 | 2014-06-17 | Oracle International Corporation | System and method for parallel multiplexing between servers in a cluster |
US9003093B2 (en) | 2012-09-07 | 2015-04-07 | Mckesson Financial Holdings | Connector apparatus and associated method for bridging data between data sources and data targets |
US8984010B2 (en) | 2012-11-06 | 2015-03-17 | Business Objects Software Ltd. | Build pooled data source based on hana SAML login |
US9967324B2 (en) | 2014-01-21 | 2018-05-08 | Oracle International Corporation | System and method for providing data sources for use in a multitenant application server environment |
US9032425B1 (en) * | 2014-03-12 | 2015-05-12 | Vmware, Inc. | System and method to boost application performance by using a proxy for executing synchronous application programming interface calls |
US9930129B2 (en) * | 2014-09-24 | 2018-03-27 | Oracle International Corporation | System and method for java EE and java SE proxy data sources in a multitenant application server environment |
US10050903B2 (en) * | 2014-09-26 | 2018-08-14 | Oracle International Corporation | System and method for multi-tenancy enablement of enterprise JAVA (TM) applications using resource proxies and application tenancy context |
US9544275B2 (en) * | 2015-01-28 | 2017-01-10 | defend7, Inc. | Communication tunneling in application container environments |
US10033823B1 (en) * | 2015-06-24 | 2018-07-24 | Amazon Technologies, Inc. | Data proxy |
US20170195449A1 (en) | 2015-12-30 | 2017-07-06 | Business Objects Software, Ltd. | Smart proxy for datasources |
US10503623B2 (en) * | 2016-04-29 | 2019-12-10 | Ca, Inc. | Monitoring containerized applications |
US10929406B2 (en) | 2016-10-27 | 2021-02-23 | American Express Travel Related Services Company, Inc | Systems and methods for a self-services data file configuration with various data sources |
-
2019
- 2019-05-14 US US16/411,873 patent/US10938933B2/en active Active
- 2019-07-12 US US16/509,770 patent/US10938934B2/en active Active
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113055498A (en) * | 2021-05-26 | 2021-06-29 | 天聚地合(苏州)数据股份有限公司 | Data source access method, device, storage medium and equipment |
Also Published As
Publication number | Publication date |
---|---|
US10938934B2 (en) | 2021-03-02 |
US20200366753A1 (en) | 2020-11-19 |
US10938933B2 (en) | 2021-03-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10909064B2 (en) | Application architecture supporting multiple services and caching | |
US11200085B2 (en) | Sharing transaction contexts in an optimized colocation of java and non-java language applications | |
US20120278726A1 (en) | Unified secure virtual machine player and remote desktop client | |
US9898376B2 (en) | Recovery of a transaction after XA end | |
US9674293B2 (en) | Systems and methods for remote access to IMS databases | |
US20150277883A1 (en) | Extensions for deployment patterns | |
US10891569B1 (en) | Dynamic task discovery for workflow tasks | |
US11086827B1 (en) | Dataset schema and metadata management service | |
US20160048703A1 (en) | Securing integrity and consistency of a cloud storage service with efficient client operations | |
US9940113B2 (en) | Big data assistant | |
US20180329761A1 (en) | Integrating transaction processing system interfaces with event-driven polyglot runtime modules | |
US10938934B2 (en) | Managing dynamic configuration-based database connections using a proxy datasource | |
US20220292584A1 (en) | Combining data and notifications for multiple accounts of a common user | |
US11500893B2 (en) | System and method for dynamically finding database nodes and replication state | |
US11093477B1 (en) | Multiple source database system consolidation | |
US11163601B2 (en) | Dynamically determine the transaction coordinator in multitier hybrid transaction processing middleware systems | |
US11416476B2 (en) | Event ordering based on an identifier for a transaction | |
US11630838B1 (en) | Conflict-free replicated data types in a database | |
US8862544B2 (en) | Grid based replication | |
US11100106B1 (en) | Query engine virtualization | |
US20140059538A1 (en) | Virtual machine state tracking using object based storage | |
US11163613B2 (en) | Automated system integration | |
US11210129B2 (en) | Extended architecture as a service to integrate resource and transaction managers | |
US11176121B2 (en) | Global transaction serialization | |
US20220300988A1 (en) | Leveraging individual engagement history in account based personalization |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ADAMS, PHILLIP CARL;TIMM, JOHN THOMAS EDWARD;RAUH, NATHAN JON;SIGNING DATES FROM 20190510 TO 20190513;REEL/FRAME:049175/0571 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |