Microsoft Technology Licensing, LLC

Vinod Kumar

Ashok Srinivasan

Jeff Comstock

Michael Merz

Jaskaran Singh

Shane Brady

Ruiyi Wang

Alexander N Samoylenko

Alexander MacLeod

Rohit Kapoor

Ann Williams

Caesar M Samsi

A system is provided for employing an orchestrator to deploy and implement changes to a system. A change request may be a system build, upgrade, and patches for updating a subset of files within the system. The orchestrator may initially perform a security check and a validation check on a received change request. Upon receiving validation and approval, the change request may be deployed and propagated through a series of deployment scopes. The deployment scopes may become increasingly larger to extensively test the applied change before fully implementing the change on the target system. The orchestrator may submit the applied change to a validation component for getting validation of the change within the deployment scope after each applied change within a deployment scope. After the change request has been deployed through the deployment scopes and validated, the change request may be deployed to the target system and fully implemented.

Automatic system upgrade orchestrator

A system and method for processing messages in an enterprise resource planning (ERP) system is provided. A processing service generates a snapshot of a message queue, which contains a plurality of messages to be processed by the ERP system. Each message has an associated conversation, identified by a unique combination of an endpoint, channel, and subconversation identifier. For each conversation, the processing service determines whether messages of the conversation are to be processed in serial or in parallel, based on the subconversation identifier of the conversation. When the messages of the conversation are to be processed in serial, a task is created to process the messages serially. Alternatively, when the messages of the conversation are to be processed in parallel, a task is created for each of the messages. The messages of each task are processed serially by the task, while each task is executed in parallel with other tasks.

Conversational parallelism for message processing

A system and method for generating application code and an external interface for a service class, in an enterprise resource planning (ERP) system is provided. The system receives a definition of a service class from a user via a user interface tool. The definition of the service class specifies a query for the service class and operations that are to be enabled for the service class. The system automatically generates application code for the service class, which enables the service class to be used by an internal endpoint of the ERP system. The application code is customizable by the user; the user may add additional operations to the service class. In addition, the system automatically generates an external interface for the service class, which enables the service class to be used by an external endpoint of the ERP system without needing knowledge of the application code.

Unified, configurable services stack for integration of enterprise applications

For each of a set of business application classes on an application server, a web service class consisting of a separate web service method for each of a set of actions is generated. Each web service method contains a call to an interface web service method stored on a web server. The interface web service method is capable of calling a method on the application server. Once generated, the web service classes are compiled into an assembly and are stored on the web server.

Generating and binding web services to application components

A security model is provided that controls access to a secured application. Under the security model, a submitting user is authenticated when the user submits a message to have the application perform an action. The application is then used to determine if the submitting user is authorized to submit messages on behalf of a source endpoint stored in the message. A method in the application is then invoked to perform the action while impersonating a source endpoint user stored in the message.

Security model for application and trading partner integration

Aspects of the subject matter described herein relate to processing payment requests. In aspects, a user of an online system is allowed to pay for goods or services using a combination or one or more payment types including credit card, cash card, gift certificate, purchase order, money order, other payment types, and the like. A payment router determines which payment processor(s) needs to be involved to satisfy each payment request and routes payment requests to each payment processor as needed. Adding new payment methods and changing existing payment methods may be accomplished by changing a table or the like that associates payment methods with payment processors.

Growing community of inventors

Redmond, WA, United States of America

Vinod Kumar