Patent application number | Description | Published |
20090049509 | SCOPE-CENTRIC ACCESS CONTROL MODEL - Apparatus, methods, and computer program products are disclosed that maintain an association graph made up of association tuples. Each of the association tuples belongs to an access-control-policy scope that imposes an access control policy. On receipt of a client reference and a supplier reference a scope-defining entity is identified from the client reference. The scope-defining entity has an explicit access control policy. An effective supplier reference is retrieved from a set of the association tuples matching the scope-defining entity and is presented. | 02-19-2009 |
20100122241 | Executable template - Systems, methods, and other embodiments associated with executable templates are described. One example method includes generating an executable template from a set of template data. When an executable template is executed, the executable template creates one or more instantiated entities. These instantiated entities may then be combined with entities created from portions of the original template that were not compilable into the executable format. | 05-13-2010 |
20100161645 | Change management - Systems, methods, and other embodiments associated with artifact type neutral change management are described. One example method includes maintaining an access table for each artifact in a collaborative software environment that records a most recent access of an artifact on a per user basis. An artifact type registration table is also maintained that maps each artifact type to the access table that records access information for artifacts of the given type and to a data store that stores artifacts of that type. For a given user, artifact pair, queries on the type registration table, access table, and data store are generated to return the last modification time for the artifact and the user's last access time for the artifact. This information is used to determine a change status of the artifact for the given user. This common framework can be used for artifacts of any type that are registered in the type registration table. | 06-24-2010 |
20100169306 | Type neutral container - Systems, methods, and other embodiments associated with an artifact type neutral container are described. This artifact type neutral container is achieved through an artifact type neutral architecture that is managed using a central type neutral registration mechanism. Queries are executed on type neutral registration tables to return data stores that store the artifacts found within a given artifact type neutral container. The data stores are queried to return the artifacts in the artifact type neutral container. The artifact type neutral container can be used in systems in which the artifact type neutral container and artifact data are stored in the same database as well as in systems in which the artifact type neutral container and artifact data are stored in different databases. | 07-01-2010 |
20110119314 | TEMPLATE BASED ENTITY TRANSFORMATION - Systems, methods, and other embodiments associated with template based entity transformation are described. One example method includes generating a difference set that describes differences between an existing data entity and a template. The example method may also include applying the template to the existing data entity based on the difference set and conflict resolution choices. | 05-19-2011 |
20140074540 | ROLE ASSIGNMENTS IN A CLOUD INFRASTRUCTURE - Provisioning, managing and tracking of services provided by a cloud infrastructure system are described. A subscription order request from a customer for services provided by the cloud infrastructure system is received. A separation of roles performed by different customer entities in a customer's organization when the customer subscribes to services in the cloud infrastructure system is determined. The roles relate to providing information about different portions of the subscription order by the customer entities. Upon completion of the assigned roles by the relevant customer entities, the subscription order is provisioned to the customer. | 03-13-2014 |
20140074659 | RAMPED ORDERING FOR CLOUD SERVICES - Provisioning, managing and tracking of services provided by a cloud infrastructure system are described. A subscription request from a customer for one or more services provided by the cloud infrastructure system is received. The request includes a specification of services with different service levels for different time periods. A phased deployment of a customer's subscription order based on the service levels and time periods specified by the customer in the subscription order is then determined. | 03-13-2014 |
20140074788 | DATA SYNCHRONIZATION IN A CLOUD INFRASTRUCTURE - A synchronization infrastructure that synchronizes data stored between components in a cloud infrastructure system is described. A first component in the cloud infrastructure system may store subscription information related to a subscription order which may in turn be utilized by a second component in the cloud infrastructure system to orchestrate the provisioning of services and resources for the order placed by the customer. The synchronization architecture utilizes transactionally consistent checkpoints that describe the state of the data stored in the components to synchronize the data between these components. | 03-13-2014 |
20140075016 | OVERAGE FRAMEWORK FOR CLOUD SERVICES - Provisioning, managing and tracking of services provided by a cloud infrastructure system are described. A subscription request from a customer for one or more services provided by the cloud infrastructure system is received. Resources for the requested services are then provisioned. Resource usage information for the resources is collected and an overuse of the resources provisioned to the services in the subscription request, by a customer is determined. The overage information is provided to the customer. | 03-13-2014 |
20140075027 | WORKFLOWS FOR PROCESSING CLOUD SERVICES - Provisioning, managing and tracking of services provided by a cloud infrastructure system are described. A subscription order request from a customer for services provided by the cloud infrastructure system is received. A workflow is defined that includes steps to process the subscription order. The workflow enables a customer to gain access to services requested in a subscription order upon placing the subscription order without the customer having to wait until all the steps involved in processing the subscription order are complete. | 03-13-2014 |
20140075499 | SECURITY INFRASTRUCTURE FOR CLOUD SERVICES - A framework for handling a secure interaction between components in a cloud infrastructure system that wish to transfer information between each other during processing of a customer's subscription order is described. The framework orders the security zones of components based on security levels and protects the transfer of information between components in security zones with different security levels. The assignment of a component to a security zone is based upon the sensitivity of the data handled by the components, the sensitivity of functions performed by the component, and the like. | 03-13-2014 |
20140143083 | SUBSCRIPTION ORDER GENERATION FOR CLOUD SERVICES - A framework for managing service components associated with a service subscribed to by a customer in a cloud infrastructure system is disclosed. The framework generates a subscription order for the customer based upon receiving a selection of service components from the customer. The framework identifies resource metrics associated with the service components selected by the customer and generates a subscription order for the customer based upon the service components and the resource metrics. | 05-22-2014 |