Abstract: Inbound processing of web service request messages at runtime is enhanced by providing validation of the message structure against corresponding schema, at an intermediary web service server rather than at the web service level (e.g., entirely by a web service application). Hence, there is minimal delay in responding to the client upon determining an invalid message structure, and unnecessary processing of invalid messages by the web service application is avoided.

Abstract: A web services system provides web services interfaces to applications having native interfaces with different types of synchrony. The web services interfaces can have the same or different type of synchrony than the underlying application. The web services layer translates a web services request from a client to corresponding function calls to applications. Upon receiving a response from an application, the web services layer translates the response back to a web services format and forwards it to the client. A naming convention is used to define the names of the data types and operations in the web services interface corresponding with data types and functions of the application. A function prefix can be used to specify a namespace in the web services interface unique to the application. A web services namespace is assigned to tokens so that requests for asynchronous web services are diverted to a general web services routine.

Abstract: A web services system provides web services interfaces to applications having native interfaces with different types of synchrony. The web services interfaces can have the same or different type of synchrony than the underlying application. The web services layer translates a web services request from a client to corresponding function calls to applications. Upon receiving a response from an application, the web services layer translates the response back to a web services format and forwards it to the client. A naming convention is used to define the names of the data types and operations in the web services interface corresponding with data types and functions of the application. A function prefix can be used to specify a namespace in the web services interface unique to the application. A web services namespace is assigned to tokens so that requests for asynchronous web services are diverted to a general web services routine.

Abstract: A web services system provides web services interfaces to applications having native interfaces with different types of synchrony. The web services interfaces can have the same or different type of synchrony than the underlying application. The web services layer translates a web services request from a client to corresponding function calls to applications. Upon receiving a response from an application, the web services layer translates the response back to a web services format and forwards it to the client. A naming convention is used to define the names of the data types and operations in the web services interface corresponding with data types and functions of the application. A function prefix can be used to specify a namespace in the web services interface unique to the application. A web services namespace is assigned to tokens so that requests for asynchronous web services are diverted to a general web services routine.

Abstract: A computer-implemented method of testing interoperability of a web service against a plurality of web services tools may include steps of providing a web services description language file (WSDL) that describes the web service to be tested; selecting at least one of the plurality of web services tools; generating and compiling sets of proxy files for each selected web service tool based upon the provided WSDL file and loading the generated and compiled proxy files into memory; generating an XML test case for each of the generated and compiled sets of proxy files, the XML test case including dummy variables for each operation of the provided WSDL file; populating the generated XML test case with values for at least some of the dummy variables, and invoking a targeted web service from a selected client platform using the populated XML test case and providing results for each invocation.

Abstract: A web service broker transforms, at runtime, output data from client applications to the input data form required by various web services. Such transformations are based on data and/or parameter mappings that are accessible to the broker. Further, the broker accesses and invokes particular web services in the manner required by the web services. Such invocations are based on information regarding the access style, such as RPC style of communication, and encoding, such as SOAP, associated with respective web services. The broker provides a generic framework in that it is capable of supporting transformation of different data and data forms from many different applications to respective data that many different respective web services can use.

Abstract: Systems, methodologies, media, and other embodiments associated with prioritizing network traffic are described. One exemplary method embodiment includes receiving a notice from a computer component to prioritize network traffic associated with a selected service. Network communications are inspected to identify priority network traffic associated with the selected service. Priority settings can then be dynamically reconfigured in the priority network traffic.

Abstract: Systems, methodologies, media, and other embodiments associated with identifying network communications of services are described. One example system embodiment includes a service identification logic configured to monitor execution of software of an application server and identify services being processed. The service identification logic can further include a logic configured to identify network communications associated with an identified service. The example system may also include a notification logic configured to notify one or more network devices to provide priority processing for the network communications associated with the identified service.

Abstract: A computer-implemented method of testing interoperability of a web service against a plurality of web services tools may include steps of providing a web services description language file (WSDL) that describes the web service to be tested; selecting at least one of the plurality of web services tools; generating and compiling sets of proxy files for each selected web service tool based upon the provided WSDL file and loading the generated and compiled proxy files into memory; generating an XML test case for each of the generated and compiled sets of proxy files, the XML test case including dummy variables for each operation of the provided WSDL file; populating the generated XML test case with values for at least some of the dummy variables, and invoking a targeted web service from a selected client platform using the populated XML test case and providing results for each invocation.

Abstract: A technique is described in which a web service provider is able to specify that messages related to business transactions with the web service includes trading partner information. For example, a provider may specify such requirements in a WSDL description of the relevant web service and may register the description with a UDDI registry. The trading partner information is regarding business transactions between the requesting party and the provider and is related to pre-established trading partner relationships and associated agreements and processes. Such trading partner information typically includes information that identifies, for example, the requesting party and the type of transaction. Consequently, the provider can determine whether the received request originates from an established trading partner and whether the requesting party is entitled to conduct the requested business transaction. Hence, application-level security is provided to electronic business transactions.

Abstract: A web services system provides web services interfaces to applications having native interfaces with different types of synchrony. The web services interfaces can have the same or different type of synchrony than the underlying application. The web services layer translates a web services request from a client to corresponding function calls to applications. Upon receiving a response from an application, the web services layer translates the response back to a web services format and forwards it to the client. A naming convention is used to define the names of the data types and operations in the web services interface corresponding with data types and functions of the application. A function prefix can be used to specify a namespace in the web services interface unique to the application. A web services namespace is assigned to tokens so that requests for asynchronous web services are diverted to a general web services routine.

Abstract: Inbound processing of web service request messages at runtime is enhanced by providing validation of the message structure against corresponding schema, at an intermediary web service server rather than at the web service application (e.g., web service application). Hence, there is minimal delay in responding to the client upon determining an invalid message structure, and unnecessary processing of invalid messages by the web service application is avoided.

Abstract: Systems, methodologies, media, and other embodiments associated with prioritizing network traffic are described. One exemplary method embodiment includes receiving a notice from a computer component to prioritize network traffic associated with a selected service. Network communications are inspected to identify priority network traffic associated with the selected service. Priority settings can then be dynamically reconfigured in the priority network traffic.

Abstract: Systems, methodologies, media, and other embodiments associated with identifying network communications of services are described. One example system embodiment includes a service identification logic configured to monitor execution of software of an application server and identify services being processed. The service identification logic can further include a logic configured to identify network communications associated with an identified service. The example system may also include a notification logic configured to notify one or more network devices to provide priority processing for the network communications associated with the identified service.

Abstract: A technique is described in which a web service provider is able to specify that messages related to business transactions with the web service includes trading partner information. For example, a provider may specify such requirements in a WSDL description of the relevant web service and may register the description with a UDDI registry. The trading partner information is regarding business transactions between the requesting party and the provider and is related to pre-established trading partner relationships and associated agreements and processes. Such trading partner information typically includes information that identifies, for example, the requesting party and the type of transaction. Consequently, the provider can determine whether the received request originates from an established trading partner and whether the requesting party is entitled to conduct the requested business transaction. Hence, application-level security is provided to electronic business transactions.

Abstract: A web service broker transforms, at runtime, output data from client applications to the input data form required by various web services. Such transformations are based on data and/or parameter mappings that are accessible to the broker. Further, the broker accesses and invokes particular web services in the manner required by the web services. Such invocations are based on information regarding the access style, such as RPC style of communication, and encoding, such as SOAP, associated with respective web services. The broker provides a generic framework in that it is capable of supporting transformation of different data and data forms from many different applications to respective data that many different respective web services can use.