A cloud computing environment provides the ability to deploy a web application that has been developed using one of a plurality of application frameworks and is configured to execute within one of a plurality of runtime environments. The cloud computing environment receives the web application in a package compatible with the runtime environment (e.g., a WAR file to be launched in an application server, for example) and dynamically binds available services by appropriately inserting service provisioning data (e.g., service network address, login credentials, etc.) into the package. The cloud computing environment then packages an instance of the runtime environment, a start script and the package into a web application deployment package, which is then transmitted to an application (e.g., container virtual machine, etc.). The application container unpacks the web application deployment package, installs the runtime environment, loads the web application package into the runtime environment and starts the start script, thereby deploying the web application in the application container.

Cloud platform architecture

A deployment system enables a developer to define a logical, multi-tier application blueprint that can be used to create and manage (e.g., redeploy, upgrade, backup, patch) multiple applications in a cloud infrastructure. In the application blueprint, the developer models an overall application architecture, or topology, that includes individual and clustered nodes (e.g., VMs), logical templates, cloud providers, deployment environments, software services, application-specific code, properties, and dependencies between top-tier and second-tier components. The application can be deployed according to the application blueprint, which means any needed VMs are provisioned from the cloud infrastructure, and application components and software services are installed.

Single, logical, multi-tier application blueprint used for deployment and management of multiple physical applications in a cloud infrastructure

A deployment system enables a developer to generate a deployment plan according to a logical, multi-tier application blueprint defined by application architects. The deployment plan includes tasks to be executed for deploying application components on virtual computing resource provided in a cloud infrastructure. The deployment plan includes time dependencies that determine an execution order of the tasks according to dependencies between application components specified in the application blueprint. The deployment plan enables system administrators to view the application blueprint as an ordered workflow view that facilitates collaboration between system administrators and application architects.

System to generate a deployment plan for a cloud infrastructure according to logical, multi-tier application blueprint

An identity management tool provides identity management across multiple domains, providing a single access point not only for information for runtime, network, and service layer information, but also for systems such as business support systems (BSS), operational support systems (OSS), and third party systems. The identity management tool creates a unified user profile that maps customer identities across the various domains, and presents the information in a virtual directory wherein the information appears to come from a single source, creating a central data hub for the various systems. This aggregation provides for the same experience and service across various access networks and using various channels. Such an architecture allows billing and service information to be shared with subscription and customer information, even though the data is substantially unrelated data from disparate data sources, without the need to combine schemas or aggregate the data into a single data store.

Shared view of customers across business support systems (BSS) and a service delivery platform (SDP)

Method and apparatus for supporting machine-to-machine (M2M) communications in a hierarchical network architecture including an M2M gateway are disclosed. An M2M entity, (such as M2M device, M2M gateway, or M2M network entity), may perform a service capability discovery procedure to discover an M2M service capability entity that may provide an M2M service capability, and register with the discovered M2M service capability entity. The address or identity of the service capability entity may be pre-configured or obtained from the dispatcher server. The M2M entity may indicate a support M2M service identifier and receive an identity or address of the M2M service capability entity mapping the service identifier. The gateway may advertise M2M service identifiers supported by the gateway so that the M2M device may access the gateway if there is a match. The address of M2M service capability entities may be obtained from the core network.

Method and apparatus for supporting machine-to-machine communications

A service proxy is used to automatically supply the message-format parameters required for incoming message communications to a web-service provider from client applications through a message-conversion system that the web-service provider previously sets up. For outgoing messages from the web service to client businesses, the service proxy automatically supplies the required message-format parameters according to service policies that client businesses set up previously through the web-service provider's web-site interface. The format of client application messages is predefined for a web service policy, and a configuration interface is established for context variables and message format variables. This service profile is recalled in order to apply the proper message format parameters for a web service request.

Method and apparatus for the use of dynamic XML message formats with web services

A packaging utility is created that can in turn create a deployment archive (DAR) file containing the data required to install a Web service application, comprising, for example, portlets for creating Web pages for the Web service's user interface, UDDI entries, executable programs, and application-wide properties. The application-wide properties may comprise elements to be used in connection with one or more Web services, for example, encryption levels, service levels, timeouts, and number of retries. For administration efficiency the application-wide properties may be applied according to hierarchies, for example from groupings of Web services to individual Web services and from organizations of users to individual users. An unpackaging tool is created to unpackage and install the DAR file on a target environment. A configuration set is employed by the unpackaging tool to determine where the elements of the Web service application are to be installed on the target environment.

System and method for a packaging and deployment mechanism for Web service applications

A method and apparatus to employ a service proxy to personalize service messages by automatically supplying the interface parameters used for communications between a Service provider and its client businesses. The service proxy does this according to context parameters that the client businesses specify during configuration of the messages used to communicate with one or more services. For simpler administration, the context variables may be organized in multiple kinds of hierarchies by which communications parameters specified at a higher level are automatically applied to categories at a lower level, although parameters specified directly for a lower-level category will override parameters from a higher category.

Non-intrusive personalization of web services

A method and apparatus to employ a service proxy to dynamically personalize Web service messages by automatically supplying the interface parameters used for communications between a Web service provider and its client businesses. The service proxy does this according to context parameters that the client businesses specifies during configuration set up at the Web service provider's Web site and in messages used to communicate with one or more Web services. For simpler administration, the context variables may be organized in multiple kinds of hierarchies by which communications parameters specified at a higher level are automatically applied to categories at a lower level, although parameters specified directly for a lower-level category will override parameters from a higher category.

Keith Yarbrough

Papers

Method and apparatus for the use of dynamic XML message formats with web services

System and method for a packaging and deployment mechanism for Web service applications

Non-intrusive personalization of web services

Method and apparatus for dynamic, non-intrusive personalization of web services

Dynamic, non-intrusive personalization of web services