Abstract: In accordance with an embodiment, described herein is a system and method for providing a representational state transfer (REST) service configuration wizard for creating REST reference or proxy services for execution in a service bus runtime. The configuration wizard can retrieve, based on a URI provided by a user, one or more resources of an external REST service, and can generate a plurality of properties for each resource. A plurality of interfaces can be provided to guide the user step by step in creating a REST reference service to access the external REST service. The user can make selections for each property and provide information if necessary. An API can be invoked to generate a REST reference service and a WADL file describing the REST reference service, based on the user's selections and the provided information.

Abstract: In accordance with an embodiment, described herein is a system and method for supporting REST services natively in a service bus runtime. The service bus runtime can include one or more native REST proxy services, one or more native REST pipelines, and one or more native REST reference services. A native REST proxy service can deliver a message payload of a REST native format into a native REST pipeline, which can process the payload without converting the payload to or from an XML-based Simple Object Access Protocol (SOAP) format. JavaScript code can be supported in the pipeline to manipulate the message payload. A REST branch node can be used in the service bus runtime to route a message based on an HTTP verb or a relative URL path in a header of the message.

Abstract: In accordance with an embodiment, described herein is a system and method for managing APIs exposed from proxy services executing in a service bus runtime. Each proxy service can be exposed as an API entry in an API catalog, where the API entry can be annotated with metadata, and published to an API portal. The published API entries can be subscribed to by an API consumer for an application. The application can pass an API key when invoking a proxy service corresponding to a subscribed API entry. A proxy interceptor associated with the corresponding proxy service can intercept the service invocation, and delegate the service invocation to an API managing component. The proxy interceptor can provide the API key and a proxy service reference to the API managing component, which can use the API key to collect usage metrics of the API subscription for display at the API portal.

Abstract: In accordance with an embodiment, described herein is a system and method for deploying a service bus artifact from a local development environment to a service bus instance in a cloud environment. A deployment API can be plugged into the local development environment to perform a plurality of steps required for deploying the service bus artifact, including enabling communication from the local development environment to pass through a corporate firewall. The plurality of steps can be wrapped in a single service call to the service bus instance; and can include creating a session, uploading the service bus artifact, importing the uploaded service bus artifact, executing customization, and activating the session. In the event of a failure of any step, the service call can abort. The deployment API is generic and can be plugged into a plurality of development products.

Abstract: In accordance with an embodiment, described herein is a system and method for supporting REST services natively in a service bus runtime. The service bus runtime can include one or more native REST proxy services, one or more native REST pipelines, and one or more native REST reference services. A native REST proxy service can deliver a message payload of a REST native format into a native REST pipeline, which can process the payload without converting the payload to or from an XML-based Simple Object Access Protocol (SOAP) format. JavaScript code can be supported in the pipeline to manipulate the message payload. A REST branch node can be used in the service bus runtime to route a message based on an HTTP verb or a relative URL path in a header of the message.

Abstract: In accordance with an embodiment, described herein is a system and method for supporting REST services natively in a service bus runtime. The service bus runtime can include one or more native REST proxy services, one or more native REST pipelines, and one or more native REST reference services. A native REST proxy service can deliver a message payload of a REST native format into a native REST pipeline, which can process the payload without converting the payload to or from an XML-based Simple Object Access Protocol (SOAP) format. JavaScript code can be supported in the pipeline to manipulate the message payload. A REST branch node can be used in the service bus runtime to route a message based on an HTTP verb or a relative URL path in a header of the message.

Abstract: A computer-controlled method can include creating a throttling group corresponding to a backend server configured to provide business services to multiple electronic devices over a service bus, defining a throttling group parameter for the throttling group, and routing messages based on the throttling group parameter.

Abstract: In accordance with an embodiment, described herein is a system and method for providing a representational state transfer (REST) service configuration wizard for creating REST reference or proxy services for execution in a service bus runtime. The configuration wizard can retrieve, based on a URI provided by a user, one or more resources of an external REST service, and can generate a plurality of properties for each resource. A plurality of interfaces can be provided to guide the user step by step in creating a REST reference service to access the external REST service. The user can make selections for each property and provide information if necessary. An API can be invoked to generate a REST reference service and a WADL file describing the REST reference service, based on the user's selections and the provided information.

Abstract: In accordance with an embodiment, described herein is a system and method for supporting REST services natively in a service bus runtime. The service bus runtime can include one or more native REST proxy services, one or more native REST pipelines, and one or more native REST reference services. A native REST proxy service can deliver a message payload of a REST native format into a native REST pipeline, which can process the payload without converting the payload to or from an XML-based Simple Object Access Protocol (SOAP) format. JavaScript code can be supported in the pipeline to manipulate the message payload. A REST branch node can be used in the service bus runtime to route a message based on an HTTP verb or a relative URL path in a header of the message.

Abstract: In accordance with an embodiment, described herein is a system and method for deploying a service bus artifact from a local development environment to a service bus instance in a cloud environment. A deployment API can be plugged into the local development environment to perform a plurality of steps required for deploying the service bus artifact, including enabling communication from the local development environment to pass through a corporate firewall. The plurality of steps can be wrapped in a single service call to the service bus instance; and can include creating a session, uploading the service bus artifact, importing the uploaded service bus artifact, executing customization, and activating the session. In the event of a failure of any step, the service call can abort. The deployment API is generic and can be plugged into a plurality of development products.

Abstract: In accordance with an embodiment, described herein is a system and method for managing APIs exposed from proxy services executing in a service bus runtime. Each proxy service can be exposed as an API entry in an API catalog, where the API entry can be annotated with metadata, and published to an API portal. The published API entries can be subscribed to by an API consumer for an application. The application can pass an API key when invoking a proxy service corresponding to a subscribed API entry. A proxy interceptor associated with the corresponding proxy service can intercept the service invocation, and delegate the service invocation to an API managing component. The proxy interceptor can provide the API key and a proxy service reference to the API managing component, which can use the API key to collect usage metrics of the API subscription for display at the API portal.

Abstract: A computer-controlled method can include creating a throttling group corresponding to a backend server configured to provide business services to multiple electronic devices over a service bus, defining a throttling group parameter for the throttling group, and routing messages based on the throttling group parameter.

Abstract: A rule-based personalization framework wherein an administrative tool is implemented as a web application, and the tool allows a non-technical user—such as a business or marketing manager—to define and manage rules and deploy them in a runtime environment. A rule is comprised of a set of condition types and action types. The manager utilizes a set of routines to create new rules or to search for existing rules. The source code of an application or application page will have tags embedded therein for association of the various actions. A rule is thereby deployed by associating certain actions with certain tags within the application. As the application is rendered, the tag will be encountered and the action executed. Actions might also be arbitrary in nature, having a predetermined interface that is implemented by the action in order for the action to be implemented properly into the associated framework.