Patent Application
20180081694
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Embodiments of the invention are generally related to application server, cloud, or other computing environments, and are particularly related to systems and methods for partition administrative targeting in such environments.
This application is related to U.S. patent application titled “SYSTEM AND METHOD FOR SUPPORTING PARTITIONS IN A MULTITENANT APPLICATION SERVER ENVIRONMENT”, application Ser. No. 14/748,094, filed Jun. 23, 2015; and U.S. patent application titled “SYSTEM AND METHOD FOR USE OF A GLOBAL RUNTIME IN A MULTITENANT APPLICATION SERVER ENVIRONMENT”, application Ser. No. 14/864,723, filed Sep. 24, 2015; each of which above applications are herein incorporated by reference.
In an application server, cloud, or other computing environment, that supports the use of partitions, for example, a multitenant application server environment, a software application deployed to the environment may include components or features that are directed to administrative functionality, in addition to the application's business or runtime logic.
When deployed within a cluster, those components or features of an application that are directed to administrative functionality may be installed to an administrative server within the cluster, while the application's business or runtime logic is installed to one or more managed server nodes, where they can operate within the lifecycles of those various nodes.
However, manual allocation of the administrative functionality, business or runtime logic, to various servers, creates a burden on the administrator. Additionally, in an application server environment that uses partitions, when an application is deployed within the context of a partition, the lifecycle of both its administrative functionality and business or runtime logic is generally controlled by the partition's lifecycle, which can lead to undesirable results, for example if the partition is shut down. These are some example of the types of environment in which embodiments of the invention can be used.
In accordance with an embodiment, described herein are a system and method for partition administrative (admin) targeting in an application server, cloud, or other computing environment. An application server can include one or more partitions, wherein each partition provides an administrative and runtime subdivision of a domain. An administrative virtual target associated with a partition enables an administrator to identify an administrative resource group, including one or more administrative applications or resources, for use with the partition. A partition administrative lifecycle state (e.g., SHUTDOWN) can be associated with various substates (e.g., BOOTED or HALTED). When a partition is associated with a first state or substate (e.g., SHUTDOWN.BOOTED), the administrative resource group in that partition continues to run at an associated target, while other resource groups are shut down. When a partition is associated with a second state or substate (e.g., SHUTDOWN.HALTED), all of the resource groups, including administrative resource groups, in that partition are shut down.
As described above, in an application server environment that uses partitions, when an application is deployed within the context of a partition, the lifecycle of both its administrative functionality and business or runtime logic, is generally controlled by the partition's lifecycle, which can lead to undesirable results, for example if the partition is shut down.
In accordance with an embodiment, described herein are a system and method for partition administrative (admin) targeting in an application server, cloud, or other computing environment. An application server can include one or more partitions, wherein each partition provides an administrative and runtime subdivision of a domain. An administrative virtual target associated with a partition enables an administrator to identify an administrative resource group, including one or more administrative applications or resources, for use with the partition.
As illustrated in
In accordance with an embodiment, the application server can include one or more partitions 104 that are defined for use at runtime. Each partition can be associated with a globally unique partition identifier (ID) and partition configuration, and can further include one or more resource groups 124, together with a reference to a resource group template 126 and/or partition-specific applications or resources 128. Domain-level resource groups, applications and/or resources 140 can also be defined at the domain level, optionally with a reference to a resource group template.
Each resource group template 160 can define one or more applications A 162, B 164, resources A 166, B 168, and/or other deployable applications or resources 170, and can be referenced by a resource group. For example, as illustrated in
Generally, a system administrator can define partitions, domain-level resource groups and resource group templates, and security realms; while a partition administrator can define aspects of their own partition, for example, by creating partition-level resource groups, deploying applications to the partition, or referencing specific realms for the partition.
As illustrated in
The resource group template illustrated in
In accordance with an embodiment, when a resource group within a partition (e.g., 202) references 220 a particular resource group template (e.g., 210), information associated with a particular partition can be used in combination with the referenced resource group template, to indicate a partition-specific information 230, for example a partition-specific PDB information. The partition-specific information can then be used by the application server to configure resources, for example a PDB resource, for use by the partition. For example, partition-specific PDB information associated with partition 202 can be used, by the application server, to configure 232 a container database (CDB) 236 with an appropriate PDB 238, for use by that partition.
Similarly, in accordance with an embodiment, a virtual target information associated with a particular partition can be used to define 239 a partition-specific virtual target 240, for use by the partition, e.g., baylandurgentcare.com, which can then be made accessible via a uniform resource locator (URL), e.g., http://baylandurgentcare.com.
In accordance with an embodiment, a system configuration such as a config.xml configuration file, is used to define a partition, including configuration elements for resource groups associated with that partition, and/or other partition properties. Values can be specified per-partition using property name/value pairs.
In accordance with an embodiment, a plurality of partitions can be executed within a managed server/cluster 242, or a similar environment which can provide access to a CDB 243, and which are accessible via a web tier 244. This allows, for example, a domain or partition to be associated with one or more of the PDBs (of the CDB).
In accordance with an embodiment, each of the plurality of partitions, in this example partition A 250 and partition B 260, can be configured to include a plurality of resources associated with that partition. For example, partition A can be configured to include a resource group 251 which contains an application A1 252, application A2 254, and JMS A 256, together with a datasource A 257 associated with PDB A 259, wherein the partition is accessible via a virtual target A 258. Similarly, partition B 260 can be configured to include a resource group 261 which contains an application B1 262, application B2 264, and JMS B 266, together with a datasource B 267 associated with PDB B 269, wherein the partition is accessible via a virtual target B 268.
While several of the above examples illustrate use of CDB and PDBs, in accordance with other embodiments, other types of multi-tenant or non-multi-tenant databases can be supported, wherein a particular configuration can be provided for each partition, for example through the use of schemas, or the use of different databases.
In accordance with an embodiment, a resource is a system resource, application, or other resource or object that can be deployed to a domain of the environment. For example, in accordance with an embodiment, a resource can be an application, JMS, JDBC, JavaMail, WLDF, data source, or other system resource or other type of object that can be deployed to a server, cluster, or other application server target.
In accordance with an embodiment, a partition is a runtime and administrative subdivision or slice of a domain that can be associated with a partition identifier (ID) and configuration, and can contain applications and/or refer to domain-wide resources through the use of resource groups and resource group templates.
Generally, a partition can contain its own applications, refer to domain wide applications via resource group templates, and have its own configuration. Partitionable entities can include resources, for example JMS, JDBC, JavaMail, WLDF resources, and other components, such as JNDI namespace, network traffic, work managers, and security policies and realms. In the context of a multi-tenant environment, the system can be configured to provide tenant access to the administrative and runtime aspects of partitions associated with a tenant.
In accordance with an embodiment, each resource group within a partition can optionally reference a resource group template. A partition can have multiple resource groups, and each of them can reference a resource group template. Each partition can define properties for configuration data that is not specified in the resource group templates to which the partition's resource groups refer. This enables the partition to act as a binding of deployable resources defined in a resource group template, to specific values for use with that partition. In some cases, a partition can override configuration information specified by a resource group template.
In accordance with an embodiment, a partition configuration, as defined for example by a config.xml configuration file, can include a plurality of configuration elements, for example: “partition”, which contains the attributes and child elements that define the partition; “resource-group”, which contains the applications and resources deployed to the partition; “resource-group-template”, which contains applications and resources defined by that template; “jdbc-system-resource-override”, which contains a database-specific service name, user name, and password; and “partition-properties”, which contains property key values that can be used for macro replacement in resource group templates. Upon startup, the system can use the information provided by the configuration file to generate partition-specific configuration elements for each resource, from the resource group template.
In accordance with an embodiment, a resource group is a named, fully-qualified collection of deployable resources that can be defined either at a domain or partition level, and can reference a resource group template. The resources in a resource group are considered fully-qualified in that the administrator has provided all of the information needed to start or connect to those resources, for example the credentials for connecting to a data source, or the targeting information for an application.
A system administrator can declare resource groups at the domain level, or at the partition level. At the domain level, a resource group provides a convenient way to group related resources. The system can manage resources declared in a domain-level resource group the same as ungrouped resources, so that the resources can be started during system start-up, and stopped during system shut-down. An administrator can also stop, start, or remove a resource in a group individually, and can act on all the resources in a group implicitly by operating on the group. For example, stopping a resource group stops all of the resources in the group that are not already stopped; starting the resource group starts any resources in the group that are not already started; and removing the resource group removes all of the resources contained in the group.
At the partition level, a system or partition administrator can configure zero or more resource groups in a partition, subject to any security restrictions. For example, in a SaaS use case, various partition-level resource groups can refer to domain-level resource group templates; while in a PaaS use case, partition-level resource groups can be created that do not refer to resource group templates, but instead represent applications and their related resources that are to be made available within that partition only.
In accordance with an embodiment, a resource group template is a collection of deployable resources that are defined at a domain level, that can be referenced from a resource group, and some of the information required to activate its resources may not be stored as part of the template itself, such that it supports the specification of partition level configuration. A domain can contain any number of resource group templates, each of which can include, for example, one or more related Java applications and the resources on which those applications depend. Some of the information about such resources may be the same across all partitions, while other information may vary from one partition to the next. Not all configuration need be specified at the domain level—partition level configuration can instead be specified in the resource group template through the use of macros, or property name/value pairs.
In accordance with an embodiment, a particular resource group template can be referenced by one or more resource groups. Generally, within any given partition, a resource group template can be referenced by one resource group at a time, i.e., not simultaneously by multiple resource groups within the same partition; however, it can be referenced at the same time by another resource group in a different partition. The object containing the resource group, e.g., the domain or partition, can use property name/value assignments to set the value of any tokens in the resource group template. When the system activates a resource group template using a referencing resource group, it can replace those tokens with values set in the resource group's containing object. In some cases, the system can also use statically-configured resource group templates and partitions to generate runtime configuration for each partition/template combination.
For example, in a SaaS use case, the system can activate the same applications and resources multiple times, including once for each partition that will use them. When an administrator defines a resource group template they can use tokens to represent the information that will be supplied elsewhere. For example, the username to use in connecting to a CRM-related data resource can be indicated in the resource group template as \${CRMDataUsername}.
In accordance with an embodiment, in a multi-tenant environment, such as a multi-tenant (MT) application server environment, a tenant is an entity that can be represented by, or otherwise associated with, one or more partitions and/or one or more tenant-aware applications. For example, tenants can represent distinct user organizations, such as different external companies, or different departments within a particular enterprise (e.g., HR and Finance departments), each of which can be associated with a different partition.
In accordance with an embodiment, the system enables users to deploy applications that are explicitly written to be tenant-aware, so that application developers can obtain the tenant ID of a current tenant. The tenant-aware application can then use the tenant ID to handle multiple tenants that are using a single instance of the application.
In accordance with an embodiment, the system includes support for partition administrative targeting (partition admin targeting) in an application server, cloud, or other computing environment.
In an application server environment that supports the use of partitions and virtual targets, targeting a resource group to, for example, an administrative server (admin server) can be accomplished by creating a virtual target for the admin server, and targeting the resource group to that virtual target.
However, when the partition is shut down, all of the applications and resources in the partition may be shut down, including components running on the admin server. This can pose difficulties for middleware (e.g., Fusion Middleware) applications and services, and internal applications (e.g., REST interfaces), which include administrative components that generally run on the admin server; since such applications and services may expect, in the event a partition is shut down, that their administrative components will continue to run.
In accordance with an embodiment, an administrative virtual target (admin virtual target) associated with a partition enables an administrator to identify an administrative resource group (admin resource group), including one or more administrative applications or resources, for use with the partition. A partition administrative lifecycle state (e.g., SHUTDOWN) can be associated with various substates (e.g., BOOTED or HALTED). When a partition is associated with a first state or substate (e.g., SHUTDOWN.BOOTED), the administrative resource group in that partition continues to run at an associated target, while other resource groups are shut down. When a partition is associated with a second state or substate (e.g., SHUTDOWN.HALTED), all of the resource groups, including administrative resource groups, in that partition are shut down.
In accordance with an embodiment, such partition administrative targeting enables support for auto-targeting of a partition's administrative applications or resources to, for example, an admin server; and also provides a partition lifecycle that handles administrative applications or resources appropriately, for example by allowing the administrative applications or resources to continue running even when the remainder of the partition's resource groups are shut down.
As illustrated in
In the example shown in
In accordance with an embodiment, each partition and its associated virtual targets can be registered with a web tier, so that, upon receiving a request (e.g, HTTP request) directed to a particular partition, the web tier can examine the request header or URI information, and dispatch the request to the appropriate partition or targeted server, including, as appropriate, to a partition's administrative virtual target or an associated admin server.
In accordance with an embodiment, each resource group can be associated with an administrative attribute that indicates if that resource group is to be considered an administrative resource group. Generally, an administrative resource group can be targeted in a manner similarly to other resource groups, for example, to an admin server, managed server, or other server. Applications and resources that are contained within an administrative resource group, whether defined directly in the resource group, or indirectly via a resource group template, can be considered administrative applications and resources.
In accordance with an embodiment, each partition can be provided with an automatically-created administrative virtual target, which can be created, for example when the partition is created.
In accordance with an embodiment, an administrative virtual target can be created with various attributes, for example: “Hostnames: empty (wildcard); uriPrefix: /partitions/<partition-name>; Targets: adminserver;” and/or other settings that can be inherited, for example, from an admin server's default HTTP server, and/or retrieved from a partition configuration bean, e.g., partition.getAdminTargetQ.
As illustrated in
In the example described herein, the string “SHUTDOWN.BOOTED” is used as a shorthand notation for, e.g., State=SHUTDOWN, Substate=BOOTED; while the string “SHUTDOWN.HALTED” is used as a shorthand notation for, e.g., State=SHUTDOWN, Substate=HALTED.
In accordance with an embodiment, shutting down a partition places it in a SHUTDOWN.BOOTED substate. When a partition is in a SHUTDOWN.BOOTED substate, its administrative resource groups are running, but all of its other resource groups are shut down. When applications in administrative resource groups are left running, they are actively RUNNING, i.e., they are not in a SUSPENDED state.
In accordance with an embodiment, in an admin server, the partition's internal applications remain running when the partition is in a SHUTDOWN.BOOTED substate. On managed server that are not targets of administrative resource groups the partition is fully shut down (halted) when the partition is shut down.
In accordance with an embodiment, when a partition is in a SHUTDOWN.BOOTED state, administrative internal applications remain running, but other applications are shut down.
In accordance with an embodiment, when a partition is in a SHUTDOWN.HALTED substate, all resource groups in the partition are shut down and the partition is fully shut down on all targets.
In accordance with an embodiment, examples of supported lifecycle operations on a partition can include halt( ): which takes a partition from a SHUTDOWN.BOOTED substate, or any running state, to a SHUTDOWN.HALTED substate; and boot( ): which takes a partition from a SHUTDOWN.HALTED substate to a SHUTDOWN.BOOTED substate.
In accordance with an embodiment, newly created partitions are created in a SHUTDOWN.HALTED substate. An administrator can start a partition from either a SHUTDOWN.BOOTED substate, or a SHUTDOWN.HALTED substate.
The above-described approach enables a partial shutdown of a partition while leaving administrative resource groups running, and/or a full shutdown of a partition leaving no resource groups running; and provides backward compatibility for, e.g., scripts which may be designed operate upon a shutdown state; while also enabling, e.g., internal applications, to be automatically targeted to an admin server, without the administrator having to manually configure such targeting.
As illustrated in
At step 344, an administrative virtual target is created for each partition, which enables an administrator to identify an administrative resource group, including one or more administrative applications or resources, for use with the partition.
At step 346, when a particular partition is associated with a first state or substate (e.g., SHUTDOWN.BOOTED), the administrative resource group in that partition is allowed to continue to run at an associated target, while other resource groups are shut down.
At step 348, when the particular partition is associated with a second state or substate (e.g., SHUTDOWN.HALTED), all of the resource groups are shut down, including administrative resource groups, in that partition.
The present invention may be conveniently implemented using one or more conventional general purpose or specialized computer, computing device, machine, or microprocessor, including one or more processors, memory and/or computer readable storage media programmed according to the teachings of the present disclosure. 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.
In some embodiments, the present invention includes a computer program product which is a non-transitory computer readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention. Examples of storage mediums can include, but are not limited to, floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or other types of storage media or devices suitable for non-transitory storage of instructions and/or data.
The foregoing description 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 the practitioner skilled in the art. For example, while several embodiments described above illustrate a multitenant application server environment, embodiments can also be used in other types of application server, cloud, or other computing environments. 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 following claims and their equivalents.
This application claims the benefit of priority to U.S. Provisional patent application titled “SYSTEM AND METHOD FOR PARTITION ADMIN TARGETING IN AN APPLICATION SERVER ENVIRONMENT”, Application No. 62/395,943, filed Sep. 16, 2016; which application is herein incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| 62395943 | Sep 2016 | US |
