International Business Machines Corporation

Joshua L Purcell

Romelia H Flores

Mathews Thomas

James P Appleyard

Edwin J Bruce

Tassanee Kraipon Supakkul

Julio Wong

David Hertenstein

Nelson M Sanchez

A workflow server can receive requests, each for a business process workflow conforming to a business process model. Each business process workflow can include a set of interdependent tasks. The workflow server can satisfy received requests by assigning tasks to different service providers that provide software services. Each of the tasks can be assigned to corresponding ones of the software services. For each task, the workflow server can also defines an allocated cost per software service, and a time allocation per software service for completing the corresponding one of the tasks. Different service providers, including those assigned to tasks, can receive information for ones of the tasks not directly assigned to them by the workflow server. The different service providers can then bid on these tasks. Wherein when bids are won, tasks for a business process flow can be reassigned based on winning bids.

Dynamically optimized distributed cloud computing-based business process management (BPM) system

A mashup widget can include a widget component and a widget container. The widget container can be graphically rendered within widget defined boundaries of a mashup application. The widget component can detect an externally defined video file. The video file can have a native frame size, which is a frame size at which the video file is encoded. The video file can be loaded from a remote data source over an IP network. The native frame size of the video file can be determined. The defined boundaries of an embedded multimedia application can be dynamically adjusted to the native size. The defined boundaries of the widget container can be resized to accommodate the adjusted embedded multimedia application. The video can be rendered and presented within in the adjusted widget container.

Interactive video player component for mashup interfaces

Users can be logged into an organization portal and an organization role can be determined for each user. For each user, indicators of values obtained from metrics tailored for the organization role can be presented within a plurality of metrics driven portlets of an organization portal. The plurality of metrics driven portlets can include at least one score card and at least one dashboard. Responsive to detecting that the at least one of the plurality of metrics exceeds a boundary condition, an out-of-bounds event can be triggered, a set of the users who are to be apprised of an occurrence of the out-of-bounds event can be programmatically determined, a Web data repository can be searched for items specific to the out of bounds event and, for each user in the set, contents of at least one of the portlets can be altered to include items from the Web data repository.

Role tailored dashboards and scorecards in a portal solution that integrates retrieved metrics across an enterprise

Interface requirements for a set of services to be implemented between service oriented architecture (SOA) front end components and SOA back end components can be identified. A service emulator can be created that satisfies service call and data needs of the SOA front end components. The SOA front end components are operable to be combined with the service emulator to form an interactive prototype. The SOA front end components are operable to be combined with the SOA back end components to form an operable SOA solution.

Service emulator substituting for backend components to satisfy needs of front end components

The disclosed invention presents a multi-phased approach for developing a service oriented architecture (SOA) solution using front end SOA components that endure throughout the SOA development lifecycle. The approach can determine interface requirements between a set of services to be implemented in a SOA solution and SOA front end. The SOA front end can conform to the determined interface requirements. The SOA front end can also be interactively utilized early within and can be applicable to all phases of a SOA lifecycle, which includes design, development, and implementation phases. The SOA front end can be combined with a service emulator to form an interactive prototype of the SOA solution. The SOA front end can also be combined with a set of SOA back end components to form the SOA solution.

SOA software components that endure from prototyping to production

Enabling workflow awareness within a business process management (BPM) system can utilize a workflow awareness controller that can receive an instantiation request for a workflow. The workflow can be comprised of multiple workflow steps to be performed by the BPM system. From workflow metadata, workflow redundancies, at the instance or step level, can be determined with other workflow instances initiated prior to the receipt of the instantiation request. The workflow metadata can include records that uniquely represent the operating parameter values of the prior workflow instances. When a workflow redundancy exists, persistent workflow data corresponding to the workflow redundancy can be utilized during the performance of a workflow instance of the requested workflow within the BPM system. The persistent workflow data can replace the performance of one or more workflow steps of the workflow instance, which can reduce the redundant performance of the workflow steps for the requested workflow.

Growing community of inventors

Dallas, TX, United States of America

Joshua L Purcell