Abstract:
A system and method for providing JAVA cloud services for use with a cloud computing environment. In accordance with an embodiment, a cloud environment, such as ORACLE Public Cloud (OPC), can include a JAVA cloud services (JCS) infrastructure, which allows a suite of software applications, middleware, and database offerings to be delivered to customers in a self-service, elastically scalable manner. In accordance with an embodiment, the JCS infrastructure can orchestrate, in combination with other cloud environment components, the creating and/or updating of a platform instance of a JAVA cloud service, including provisioning and deployment of the platform instance and/or deployment of software applications, and one or more personality injection or application deployment processing. Additional resources and/or services, such as a database service, can be wired to or otherwise associated with the JAVA cloud service, for use by customer applications that are deployed to the cloud.
Abstract:
A system and method for enabling a cloud computing environment. In accordance with an embodiment, the system can include a variety of hardware and/or software components and features, which can be used in delivering an infrastructure, platform, and/or applications to support public and private clouds.
Abstract:
Techniques are disclosed for enabling tenant hierarchy information to be migrated directly between different multi-tenant system (e.g., from a shared IDM system to a Nimbula system, or vice versa). A corresponding new tenant is created in a Nimbula system based on a combination of the tenant information and the service information from the shared IDM system. The Nimbula system extracts the tenant name and the service name from a request and asks the shared IDM system to verify that the user actually is a member of the tenant identified by the extracted tenant name. Upon successful authentication of the user, the Nimbula system requests the IDM system for roles that are associated with both the user and the extracted service name. The Nimbula system enable access to the service upon determining whether the requested operation can be performed relative to the specified service based on the roles.
Abstract:
Techniques are disclosed for enabling tenant hierarchy information to be migrated directly between different multi-tenant system (e.g., from a shared IDM system to a Nimbula system, or vice versa). A corresponding new tenant is created in a Nimbula system based on a combination of the tenant information and the service information from the shared IDM system. The Nimbula system extracts the tenant name and the service name from a request and asks the shared IDM system to verify that the user actually is a member of the tenant identified by the extracted tenant name. Upon successful authentication of the user, the Nimbula system requests the IDM system for roles that are associated with both the user and the extracted service name. The Nimbula system enable access to the service upon determining whether the requested operation can be performed relative to the specified service based on the roles.
Abstract:
A clustered database environment includes multiple database instances that appear as one server. An application server can use a data source and connection pools to connect with the clustered database. A notification service broadcasts notifications describing state changes in the database instances, which are then used by the data source and connection pools to control access to the database instances. A data source configuration allows for specification of a preferred affinity policy. A session affinity policy is used to provide database instance affinity for database access made under the context of a web session, whereby database operations are directed to a particular instance for a period of time when the application may be performing multiple, related updates to a specific data set. Directing such operations to a single database instance can be used to improve application performance due to increased local cache utilization.
Abstract:
A clustered database environment includes multiple database instances that appear as one server. An application server can use a data source and connection pools to connect with the clustered database. A notification service broadcasts notifications describing state changes in the database instances, which are then used by the data source and connection pools to control access to the database instances. A data source configuration allows for specification of a preferred affinity policy. A session affinity policy is used to provide database instance affinity for database access made under the context of a web session, whereby database operations are directed to a particular instance for a period of time when the application may be performing multiple, related updates to a specific data set. Directing such operations to a single database instance can be used to improve application performance due to increased local cache utilization.
Abstract:
A computer-implemented method and system can support a tiered cache, which includes a first cache and a second cache. The first cache operates to receive a request to at least one of update and query the tiered cache; and the second cache operates to perform at least one of an updating operation and a querying operation with respect to the request via at least one of a forward strategy and a listening scheme.
Abstract:
A system and method for providing whitelist functionality for use with a cloud computing environment. In accordance with an embodiment, software applications being deployed to the cloud are restricted from using certain classes or application program interfaces (APIs). During provisioning by, e.g., a Java cloud services (JCS) infrastructure, or another component of the cloud environment, an application's resources, such as its classes or API calls, can be matched against a whitelist of acceptable resources. If the application fails to be validated against the whitelist, it will not be deployed to the cloud, and the customer/user notified accordingly. In accordance with an embodiment, a whitelist functionality can be packaged within a software development kit (SDK), which customers/users can use during development of their applications, to verify that the applications will comply with, or successfully validate against the whitelist, prior to attempting to deploy the applications to the cloud.