Abstract: Techniques are described for binding secondary services with a cloud service instance. In one or more embodiments, a service definition defines a set of secondary services that are compatible with a primary service. In response to receiving a request to perform a provisioning operation for the instance of the primary service, a provisioning engine identifies, from the set of secondary services that are compatible with the primary service, a subset of one or more secondary services that are available. The provisioning engine binds the subset of one or more secondary services to the primary service to generate a deployment configuration for the instance of the primary service. Based on the deployment configuration, the provisioning engine provisions a set of components for the instance of the primary service.

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: Techniques are described for binding secondary services with a cloud service instance. In one or more embodiments, a service definition defines a set of secondary services that are compatible with a primary service. In response to receiving a request to perform a provisioning operation for the instance of the primary service, a provisioning engine identifies, from the set of secondary services that are compatible with the primary service, a subset of one or more secondary services that are available. The provisioning engine binds the subset of one or more secondary services to the primary service to generate a deployment configuration for the instance of the primary service. Based on the deployment configuration, the provisioning engine provisions a set of components for the instance of the primary service.

Abstract: Techniques are described for binding secondary services with a cloud service instance. In one or more embodiments, a service definition defines a set of secondary services that are compatible with a primary service. In response to receiving a request to perform a provisioning operation for the instance of the primary service, a provisioning engine identifies, from the set of secondary services that are compatible with the primary service, a subset of one or more secondary services that are available. The provisioning engine binds the subset of one or more secondary services to the primary service to generate a deployment configuration for the instance of the primary service. Based on the deployment configuration, the provisioning engine provisions a set of components for the instance of the primary service.

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 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: Techniques are described for automated provisioning of cloud service instances. In one or more embodiments, a service definition defines a set of resource dependencies for a plurality of versions of a cloud service including a first set of resource dependencies for a first version of the cloud service and a second set of one or more resource dependencies for a second version of the cloud service, wherein the second set of one or more resource dependencies modifies the first set of resource dependencies. In response to the request to perform a service operation for an instance of the second version of the cloud service, a provisioning engine generates and executes a set of instructions for provisioning a set of resources for the instance of the second version of the cloud service based on the target set of resource dependencies determined based on the first and second set of resource dependencies.

Abstract: Techniques are described for binding secondary services with a cloud service instance. In one or more embodiments, a service definition defines a set of secondary services that are compatible with a primary service. In response to receiving a request to perform a provisioning operation for the instance of the primary service, a provisioning engine identifies, from the set of secondary services that are compatible with the primary service, a subset of one or more secondary services that are available. The provisioning engine binds the subset of one or more secondary services to the primary service to generate a deployment configuration for the instance of the primary service. Based on the deployment configuration, the provisioning engine provisions a set of components for the instance of the primary service.

Abstract: Techniques are described for automated provisioning of cloud service instances. In one or more embodiments, a service definition defines a set of resource dependencies for a plurality of versions of a cloud service including a first set of resource dependencies for a first version of the cloud service and a second set of one or more resource dependencies for a second version of the cloud service, wherein the second set of one or more resource dependencies modifies the first set of resource dependencies. In response to the request to perform a service operation for an instance of the second version of the cloud service, a provisioning engine generates and executes a set of instructions for provisioning a set of resources for the instance of the second version of the cloud service based on the target set of resource dependencies determined based on the first and second set of resource dependencies.

Abstract: A system and method for patching cloud services for use with a cloud computing environment. In accordance with an embodiment, a cloud environment includes a cloud services infrastructure, which allows a suite of software applications, middleware, and database offerings to be delivered to customers in a self-service, elastically scalable manner. Over time, it may become necessary to update one or more of the deployed services. In accordance with an embodiment, services can be patched using a two phase approach. During an offline phase, patches are used to update shared components, such as middleware volumes, without disrupting any currently running services. Subsequently, during an online phase, patched components are enabled on all service hosts, and any necessary domain update/upgrade operations are invoked.

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.

Abstract: A system and method for patching Java cloud services for use with a cloud computing environment. In accordance with an embodiment, a cloud environment, such as Oracle Public Cloud (OPC), includes 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. Over time, it may become necessary to update one or more of the deployed services. In accordance with an embodiment, services can be patched using a two phase approach. During an offline phase, patches are used to update shared components, such as middleware volumes, without disrupting any currently running Java services. Subsequently, during an online phase, patched components are enabled on all Java service hosts, and any necessary domain update/upgrade operations are invoked.

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 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.

Abstract: The challenge of communicating document caching policies from document servers to client processes in the most generally applicable manner is solved by enabling the application of caching policies to classes of documents, rather than single instances of documents. Caching policies are applied to a given class of documents by specifying caching policies in metadata that describes the structure of the class of documents that conform to the metadata. In the context of XML data documents and document fragments, an XML schema can be annotated to include a representation of a caching policy, thereby specifying the caching policy for XML data documents and fragments that conform to the corresponding XML schema.

Abstract: The challenge of communicating document caching policies from document servers to client processes in the most generally applicable manner is solved by enabling the application of caching policies to classes of documents, rather than single instances of documents. Caching policies are applied to a given class of documents by specifying caching policies in metadata that describes the structure of the class of documents that conform to the metadata. In the context of XML data documents and document fragments, an XML schema can be annotated to include a representation of a caching policy, thereby specifying the caching policy for XML data documents and fragments that conform to the corresponding XML schema.

Abstract: The challenge of communicating document caching policies from document servers to client processes in the most generally applicable manner is solved by enabling the application of caching policies to classes of documents, rather than single instances of documents. Caching policies are applied to a given class of documents by specifying caching policies in metadata that describes the structure of the class of documents that conform to the metadata. In the context of XML data documents and document fragments, an XML schema can be annotated to include a representation of a caching policy, thereby specifying the caching policy for XML data documents and fragments that conform to the corresponding XML schema.

Abstract: The challenge of communicating document caching policies from document servers to client processes in the most generally applicable manner is solved by enabling the application of caching policies to classes of documents, rather than single instances of documents. Caching policies are applied to a given class of documents by specifying caching policies in metadata that describes the structure of the class of documents that conform to the metadata. In the context of XML data documents and document fragments, an XML schema can be annotated to include a representation of a caching policy, thereby specifying the caching policy for XML data documents and fragments that conform to the corresponding XML schema.