Abstract: A client system requests to upload an input data stream to a server system. The input data stream is split to a sequence of chunks. The chunks are transferred in parallel by a number of connections from the client system to the server system. At the server system, the transferred chunks are merged into an output stream according to the sequence. The output stream represents the rebuilt input stream.

Abstract: Various embodiments of systems and methods to process customized deployment scenarios in a shared computing environment are described. In one aspect, a deployment request is received at the shared computing environment by a client associated with a customized deployment scenario. In a response, a deploy service of the shared computing environment is instantiated. In another aspect, one or more custom deploy processors are identified by the deploy service, where the one or more custom deploy processors correspond to one or more customized deployment scenarios. In yet another aspect, a part of a deployable content passed to the one or more custom deploy processors by the deploy service, is deployed to the shared computing environment by at least one corresponding custom deploy processor.

Abstract: In one aspect, a transformation of web application archives (WARs) to Open Services Gateway initiative (OSGi™) web bundles is performed. WARs are specialized Java® archives for packaging web applications and the transformation to OSGi™ web bundles is realized by applying proper entries to the manifest of the WARs thus making them OSGi™ compliant. In another aspect, the transformed WARs to OSGi™ web bundles are marked as auto started so that the web application is available for requests after product installation.

Abstract: In one aspect, a metadata of an application is received. The metadata describes a number of artifacts of the computer application. Based on a reference in the application metadata, at least one service that the application is configured to access is determined. In another aspect, additional metadata describing artifacts associated with the at least one service are identified. The artifacts associated with the at least one service and the artifacts of the computer application are selected for installation of the computer application.

Abstract: A client system requests to upload an input data stream to a server system. The input data stream is split to a sequence of chunks. The chunks are transferred in parallel by a number of connections from the client system to the server system. At the server system, the transferred chunks are merged into an output stream according to the sequence. The output stream represents the rebuilt input stream.

Abstract: In one aspect, a software application with application artifacts is deployed on a cloud computing platform. The cloud computing platform includes a platform product that can provide functionality that is required by the application. Application metadata is created based on analyzing the application artifacts and describes the application artifacts requirement. An application repository stores the application artifacts and the application metadata. A product description defines an application product for the software application and a product reference to the platform product is defined. The product description and the product reference are published in the application repository to update the application metadata. A composite repository refers to the application product and the platform product. The composite repository is transferred to a platform repository provided by the cloud computing platform.

Abstract: Various embodiments of systems and methods to process customized deployment scenarios in a shared computing environment are described. In one aspect, a deployment request is received at the shared computing environment by a client associated with a customized deployment scenario. In a response, a deploy service of the shared computing environment is instantiated. In another aspect, one or more custom deploy processors are identified by the deploy service, where the one or more custom deploy processors correspond to one or more customized deployment scenarios. In yet another aspect, a part of a deployable content passed to the one or more custom deploy processors by the deploy service, is deployed to the shared computing environment by at least one corresponding custom deploy processor.

Abstract: A computerized method and a system for direct deploy of static content. Static content is received at a deployment framework of an application server. The content is forwarded to a content deployment extension (CDE) for implementing the deployment of the content on the applications server. The application server operates in online mode during the deployment. The CDE selects an appropriate content handler to handle the deployment of the content. The content is deployed by the content handler on the application server in online mode. The CDE receive a feedback from the deployment of the static content.

Abstract: In one aspect, a business application is provided by a customer for execution in a cloud environment. A runtime platform for the business application is identified based on the functionality of the business application. In another aspect, an installable package for a product composing the business application and a first version of the runtime platform is generated. In yet another aspect, the business application and a second version of the runtime platform are synchronously installed in a cloud environment based on the installable package of the product, where the metadata of the business application and the metadata of the business application are dynamically validated prior the installation to guarantee compatibility.

Abstract: In one aspect, a software application with application artifacts is deployed on a cloud computing platform. The cloud computing platform includes a platform product that can provide functionality that is required by the application. Application metadata is created based on analyzing the application artifacts and describes the application artifacts requirement. An application repository stores the application artifacts and the application metadata. A product description defines an application product for the software application and a product reference to the platform product is defined. The product description and the product reference are published in the application repository to update the application metadata. A composite repository refers to the application product and the platform product. The composite repository is transferred to a platform repository provided by the cloud computing platform.

Abstract: In one aspect, an application is received to be to be executed in a local development environment. The application is configured to access at least one service from a number of services of a remote runtime platform. A software development kit (SDK) is selected as an execution environment of the application. The SDK includes a number of application programming interfaces (APIs) of the services and a number of local implementations of the services. In another aspect, the application is executed over the SDK and remote functioning of the application is emulated in the local development environment.

Abstract: In one aspect, a metadata of an application is received. The metadata describes a number of artifacts of the computer application. Based on a reference in the application metadata, at least one service that the application is configured to access is determined. In another aspect, additional metadata describing artifacts associated with the at least one service are identified. The artifacts associated with the at least one service and the artifacts of the computer application are selected for installation of the computer application.

Abstract: In one aspect, a transformation of web application archives (WARs) to Open Services Gateway initiative (OSGi™) web bundles is performed. WARs are specialized Java® archives for packaging web applications and the transformation to OSGi™ web bundles is realized by applying proper entries to the manifest of the WARs thus making them OSGi™ compliant. In another aspect, the transformed WARs to OSGi™ web bundles are marked as auto started so that the web application is available for requests after product installation.

Abstract: In one aspect, a new software application building upon a base software product is created. A definition of a new software product is generated including the new software application. A reference to the base software product is included in the definition of the new software product. In another aspect, an installable package for the new software product is generated based on the definition and stored in a public repository. In yet another aspect, the installable package of the new software product includes a reference to an installable package of the base software product to enable customers installing the new software product with nesting an installation of the base software product.

Abstract: In one aspect, a business application is provided by a customer for execution in a cloud environment. A runtime platform for the business application is identified based on the functionality of the business application. In another aspect, an installable package for a product composing the business application and a first version of the runtime platform is generated. In yet another aspect, the business application and a second version of the runtime platform are synchronously installed in a cloud environment based on the installable package of the product, where the metadata of the business application and the metadata of the business application are dynamically validated prior the installation to guarantee compatibility.

Abstract: A computerized method and a system for direct deploy of static content. Static content is received at a deployment framework of an application server. The content is forwarded to a content deployment extension (CDE) for implementing the deployment of the content on the applications server. The application server operates in online mode during the deployment. The CDE selects an appropriate content handler to handle the deployment of the content. The content is deployed by the content handler on the application server in online mode. The CDE receive a feedback from the deployment of the static content.