666 results about "Service oriented" patented technology

Financial information data integration is provided through real time data integration services deployed in a services oriented architecture.

Services such as product services, real-time services, and common services are deployed in a services oriented architecture. These services may, for example, be deployed for use in a variety of enterprise data integration functions.

Health care information data integration is provided through real time data integration services deployed in a services oriented architecture.

A system and method for providing integration of service-oriented architecture (SOA) is provided. Generally, the method comprising the steps of: identifying SOA drivers, thereby determining matters that are driving the company to integrate the SOA and Web services into the company; developing a business initiative roadmap, thereby performing an analysis of current and planned business initiatives and projects of the company, and an analysis of current and potential services that will be required to implement or support the business initiatives during the providing integration of the SOA and Web services; developing an SOA technology roadmap, thereby determining necessary SOA enabling technical solutions that can be implemented to support the developed business initiative roadmap; and prioritizing and sequencing the business initiative roadmap and the SOA technology roadmap, thereby synchronizing the business initiatives and Web service initiatives with implementation of the supporting SOA technical solutions determined during the step of developing the SOA technology roadmap.

Real time data integration services are deployed in a services oriented architecture for supply chain management.

A Service-oriented architecture (SOA) and accompanying method. In one embodiment, the SOA includes one or more service requesters coupled to one or more service providers via a bus. The bus includes runtime-binding functionality to facilitate interaction between the one or more service requesters and the one or more service providers. A registry, which stores information pertaining to a service provided by the one or more service providers, communicates with one or more service providers and/or requesters and the bus. In a more specific embodiment, bus includes a Service-Integration Bus (SIB) that includes a Service-Factory (SF) module for facilitating implementing the runtime binding functionality and for selectively invoking the service. Functionality of the SOA is strategically organized into various tiers and layers, including a requester tier, a provider tier, a business-process services tier, an infrastructure-services tier, an SIB layer, a persistence layer, and so on, to optimize system reusability, adaptability, and other desirable properties. A service interface pattern is described whereby a change in service implementation does not require modification to the manner in which the service is invoked by a requester

An extraction function of an extract-transform-load data integration process is deployed as a service in a services oriented architecture.

A computer-implemented system and method for processing messages using a common interface platform supporting multiple pluggable data formats in a service-oriented pipeline architecture is disclosed. The method in an example embodiment includes deserializing or serializing a request/response message using a pluggable serializer/deserializer mechanism and a corresponding pluggable data format parser. An example embodiment uses a common model for serialization/deserialization regardless of the data format, resulting in a consistent and efficient mechanism.

The invention provides a system for providing services of an event-driven service-oriented internet of things and a working method of the system. The system is composed of a plurality of parts of an internet of things service system, an access agent, a unified message distribution network based on a publish-subscribe mechanism, a complex event processing engine, a resource descriptive model base and a sensor system. The system and the working method solve the problems that an existing system for providing the services of the internet of things can not process large-scale sensing information in a distributed mode, events in a physical world can not be processed, effective cross-business-domain and cross-organization coordination is difficult to achieve by different enterprise business processes. According to the system, sensing information is effectively distributed in the open and distributed computing environment, various pieces of sensing information can be conveniently and quickly distributed as required among different internet of things heterogeneous service systems, event-driven cross-business-domain and cross-organization service dynamic coordination is achieved, time, space and control flow uncoupled network services are provided, and quick response to change of the physical world can be flexibly and dynamically achieved in real time.

Techniques are disclosed for assembling statistics for diagnosing performance and scalability issues in SOA systems. Key statistics related to key points in a SOA system, for key activities during processing of transactions in the SOA system, are collected and aggregated. The statistics may include message flow rates and latency at key points in the system during a time interval, and execution times for key activities in the system during the time interval. The statistics for the time interval may be added to corresponding cumulative statistics, and persisted to storage. Reports may be generated based upon the statistics to present to a user. Automated processes may be implemented to use the statistics to identify the existence and likely cause of SOA application performance issues, and potentially to attempt to remediate the issues.

A software architecture for future open wireless architecture (OWA) mobile terminal providing an open and secured software platform supporting various wireless air interfaces with multi-dimensional mobility handovers and maximized spectrum efficiency for the truly service-oriented fixed, mobile and wireless communications convergence.

A system and method for implementing a server-based speech recognition system for multi-modal automated interaction in a vehicle includes receiving, by a vehicle driver, audio prompts by an on-board human-to-machine interface and a response with speech to complete tasks such as creating and sending text messages, web browsing, navigation, etc. This service-oriented architecture is utilized to call upon specialized speech recognizers in an adaptive fashion. The human-to-machine interface enables completion of a text input task while driving a vehicle in a way that minimizes the frequency of the driver's visual and mechanical interactions with the interface, thereby eliminating unsafe distractions during driving conditions. After the initial prompting, the typing task is followed by a computerized verbalization of the text. Subsequent interface steps can be visual in nature, or involve only sound.

Service Capability Interaction Manager (SCIM)-type functionality is provided at a horizontal service layer in an Service Oriented Architecture (SOA)-based approach. SCIM composition is provided at multiple levels, including the level of composition where servlets have full access to the context information of the service layer. SCIM composition also occurs at the level of an application dispatching messages to multiple applications/services for processing the messages. The functionality at the service layer also can be programmed using policies, such that routing decisions can be made dynamically as the result of processing conditions and actions. An incoming message can result in a Web service being triggered that in turn triggers a BPEL or SOA workflow, the workflow calling multiple operations to process the message as a result of a routing table or header, environmental and contextual information at the service level, and other information such as user preference or presence information.

A method of managing data with high granularity, comprises identifying data objects and an associated data management policy. The policy uses features and a common semantic to define a feature-based sequence of data management actions of a data management operation that varies for different objects depending on respective features. Features of the data objects are obtained and then used to associate a data management action with the object using the policy so that the object is managed individually according to its own features, thus achieving high granularity of data management precision and also high flexibility.

A method and system for managing service state data of a service in a service-oriented architecture by establishing a pluggable meta-data processor comprising: establishing a platform independent, extensible meta-data information model to define meta-data about service state data; establishing an extensible meta-data definition comprising an extensible set of service state data attributes; configuring one or more extensible semantic processors; configuring a controller meta-data processor; and defining contracts among the semantic processors.

A generalized architecture for a highly available transaction processing system that combines commercially available components and software components specifically developed to implement the architecture into an integrated, highly available transaction processing system that minimizes planned and unplanned downtime, minimizes data loss in the event of failures, provides proactive monitoring of both hardware and software components of the highly available transaction processing system, provides automated recovery actions that involve fast failover, either locally to an Inactive Node, or remotely to a Standby Site, and provides an easy-to-use graphical-user-interface-based management interface that provides service-oriented views of the state of the system, with context-directed commands and meta-commands to guide managers in execution of their tasks.

A method of recognizing and supporting multiple versions of a canonical message model in a service oriented architecture industry model repository comprising determining differences between at least one first version of a message model and at least one other version of the message model; mapping the differences between the different versions of the message models to the SOA IMR; and providing the mapping of the differences between the message models to a message access service, mapping of differences between the message models are applied and updated to the later of the message models to support the versions of the canonical message models seamlessly.