Abstract: The disclosure provides an approach for automatically scheduling resource-aware software-defined data center (SDDC) upgrades. Embodiments include receiving, via a user interface (UI), user input indicating one or more constraints related to automatically scheduling a plurality of upgrade phases for upgrading components of a plurality of computing devices across a plurality of SDDCs. Embodiments include receiving, via the UI, a user selection of a first UI control that, when selected, initiates an automatic assignment of the plurality of upgrade phases to particular time slots based on the one or more constraints. Embodiments include displaying, via the UI, a depiction of a schedule for the plurality of upgrade phases based on the automatic assignment. Embodiments include displaying, via the UI, a second UI control that, when selected, causes the automatic assignment to be finalized and a third UI control that, when selected, initiates a new automatic assignment.

Abstract: Disclosed are systems, apparatuses and techniques for replicating data between different cloud computing platforms. Examples include storage replicator components operable in different cloud computing platforms. The first storage replicator component may identify the second cloud computing platform as a location to copy a data file in response to an event related to the data file stored in a first cloud computing platform. The first storage replicator component may request a copy of the data file via an application programming interface of the first cloud computing platform. The attributes of the copy of the data file which involve modification to conform to data management conventions of the second cloud computing platform may be determined and modified to comply with conventions of the second cloud computing platform. The modified copy of the data file may be forwarded to the second cloud computing platform for storage.

Abstract: Disclosed are systems, apparatuses and techniques for replicating data between different cloud computing platforms. Examples include storage replicator components operable in different cloud computing platforms. The first storage replicator component may identify the second cloud computing platform as a location to copy a data file in response to an event related to the data file stored in a first cloud computing platform. The first storage replicator component may request a copy of the data file via an application programming interface of the first cloud computing platform. The attributes of the copy of the data file which involve modification to conform to data management conventions of the second cloud computing platform may be determined and modified to comply with conventions of the second cloud computing platform. The modified copy of the data file may be forwarded to the second cloud computing platform for storage.

Abstract: Disclosed are systems, apparatuses and techniques for replicating data between different cloud computing platforms. Examples include storage replicator components operable in different cloud computing platforms. The first storage replicator component may identify the second cloud computing platform as a location to copy a data file in response to an event related to the data file stored in a first cloud computing platform. The first storage replicator component may request a copy of the data file via an application programming interface of the first cloud computing platform. The attributes of the copy of the data file which involve modification to conform to data management conventions of the second cloud computing platform may be determined and modified to comply with conventions of the second cloud computing platform. The modified copy of the data file may be forwarded to the second cloud computing platform for storage.

Abstract: Disclosed are systems, apparatuses and techniques for replicating data between different cloud computing platforms. Examples include storage replicator components operable in different cloud computing platforms. The first storage replicator component may identify the second cloud computing platform as a location to copy a data file in response to an event related to the data file stored in a first cloud computing platform. The first storage replicator component may request a copy of the data file via an application programming interface of the first cloud computing platform. The attributes of the copy of the data file which involve modification to conform to data management conventions of the second cloud computing platform may be determined and modified to comply with conventions of the second cloud computing platform. The modified copy of the data file may be forwarded to the second cloud computing platform for storage.

Abstract: Disclosed are systems, apparatuses and techniques for replicating data between different cloud computing platforms. Examples include storage replicator components operable in different cloud computing platforms. The first storage replicator component may identify the second cloud computing platform as a location to copy a data file in response to an event related to the data file stored in a first cloud computing platform. The first storage replicator component may request a copy of the data file via an application programming interface of the first cloud computing platform. The attributes of the copy of the data file which involve modification to conform to data management conventions of the second cloud computing platform may be determined and modified to comply with conventions of the second cloud computing platform. The modified copy of the data file may be forwarded to the second cloud computing platform for storage.

Abstract: Disclosed are systems, apparatuses and techniques for replicating data between different cloud computing platforms. Examples include storage replicator components operable in different cloud computing platforms. The first storage replicator component may identify the second cloud computing platform as a location to copy a data file in response to an event related to the data file stored in a first cloud computing platform. The first storage replicator component may request a copy of the data file via an application programming interface of the first cloud computing platform. The attributes of the copy of the data file which involve modification to conform to data management conventions of the second cloud computing platform may be determined and modified to comply with conventions of the second cloud computing platform. The modified copy of the data file may be forwarded to the second cloud computing platform for storage.

Abstract: An apparatus, system, and method are disclosed for pattern-based archiving of business events on a middleware server. The method performs pattern-based archiving of business events on a middleware server by: interpreting a user-specified naming pattern for labeling event archive structures, each event archive structure corresponding to an event; detecting the occurrence of a middleware event triggered by a business process; generating an archive filename based on the user-specified naming pattern, the filename comprising data from the event; and providing the filename to an event storage module for saving an archive file with the filename. The archiving method allows users to review archived files such that the filename provides a context for the archive document, and users can more easily find specific documents.

Abstract: An apparatus, system, and method are disclosed for processing a technology specific message. In one embodiment, a computer program product receives a message having a conventional header and a user-defined header that both conform to a predefined header format, each header comprising a header name and a value; identifies each header in the message based on the predefined header format; generates a header structure to store the header name and the value from each header; stores the header structure in a set of header structures of an extendable message business object; and passes the extendable message business object to an integration broker.

Abstract: An apparatus, system, and method are disclosed for pattern-based archiving of business events on a middleware server. The method performs pattern-based archiving of business events on a middleware server by: interpreting a user-specified naming pattern for labeling event archive structures, each event archive structure corresponding to an event; detecting the occurrence of a middleware event triggered by a business process; generating an archive filename based on the user-specified naming pattern, the filename comprising data from the event; and providing the filename to an event storage module for saving an archive file with the filename. The archiving method allows users to review archived files such that the filename provides a context for the archive document, and users can more easily find specific documents.

Abstract: An apparatus, system, and method are disclosed for processing a technology specific message. In one embodiment, a computer program product receives a message having a conventional header and a user-defined header that both conform to a predefined header format, each header comprising a header name and a value; identifies each header in the message based on the predefined header format; generates a header structure to store the header name and the value from each header; stores the header structure in a set of header structures of an extendable message business object; and passes the extendable message business object to an integration broker.