Cisco Technology, Inc.

Oracle International Corporation

Anna Igorevna Bokhan-Dilawari

Tuck Chang

Tim Diekmann

Geoffrey R Hendrey

Najeeb Andrabi

Sergey Sergeev

According to one or more embodiments of the disclosure, an example process herein may comprise: receiving a request into an extensibility platform from an entity, the extensibility platform configured in part by one or more solution packages; determining a type of the request and a particular corresponding solution package of the one or more solution packages; performing role-based access control on the request based on a corresponding role-based access control configuration for the type of the request as configured within the particular corresponding solution package; and forwarding, in response to appropriate access of the entity based on role-based access control, the request to a particular representational state transfer endpoint for the type of request as defined by the particular corresponding solution package, wherein the particular representational state transfer endpoint processes the request.

Custom rest endpoints and extensible role-based access control (RBAC) for an extensibility platform

According to one or more embodiments of the disclosure, an example method herein may comprise: managing a particular cell of a multi-celled architecture for an extensibility platform having one or more tenants served by datastores of the particular cell; connecting to a global cell manager for global cell management of all cells of the multi-celled architecture; identifying a consumption limit indicating a maximum amount of system resources that a particular tenant of the one or more tenants is allowed to consume of the particular cell; enforcing the consumption limit on the particular tenant; and ensuring that the particular tenant is provided system resources of the particular cell up to the consumption limit without limitation.

Cell-based architecture for an extensibility platform

Techniques for transforming plug-in application recipe (PIAR) variables are disclosed. A PIAR definition identifies a trigger and an action. Trigger variable values, exposed by a first plug-in application, are necessary to evaluate the trigger. Evaluating the trigger involves determining whether a condition is satisfied, based on values of trigger variables. A second plug-in application exposes an interface for carrying out an action. Evaluating the action involves carrying out the action based on input variable values. A user selects, via a graphical user interface of a PIAR management application, a variable for a trigger or action operation and a transformation operation to be applied to the variable. The PIAR management application generates a PIAR definition object defining the trigger, the action, and the transformation operation, and stores the PIAR definition object for evaluation on an ongoing basis.

Transforming plug-in application recipe variables

Techniques for managing a plug-in application recipe ('PIAR') are disclosed. A mapping between (a) a user-selected field, selected via a PIAR creation interface, and (b) a third-party application field, exposed by an application programming interface ('API') of a third-party application, is stored. The third-party application field is associated with a trigger or action of a PIAR. Managing the PIAR in an active state involves periodically receiving and checking data from the third-party application field against a PIAR condition. During or after managing the PIAR in the active state, information is stored to update the mapping to a different mapping. The different mapping maps the user-selected field to a different third-party application field. Without modifying the PIAR, managing the PIAR in the active state then involves periodically receiving and checking data from the different third-party application field against the PIAR condition.

Growing community of inventors

San Ramon, CA, United States of America

Anna Igorevna Bokhan-Dilawari