Dynamic web service deployment and integration

BACKGROUND

Computers have become highly integrated in the workforce, in the home, in mobile devices, and many other places. Computers can process massive amounts of information quickly and efficiently. Software applications designed to run on computer systems allow users to perform a wide variety of functions including business applications, schoolwork, entertainment and more. Software applications are often designed to perform specific tasks, such as word processor applications for drafting documents, or email programs for sending, receiving and organizing email.

In many cases, software applications are designed to interact with other software applications or other computer systems. For example, a client computer system might connect to a server in a datacenter to access a service. The service could provide simple or complex functionality, and may be able to communicate with other services in the process while providing the desired functionality. Such services are often referred to as software as a service (SAAS).

Datacenters configured to provide such services often provide a variety of generalized system services, as well as more specific business-specific services. Providing both the generalized services the business-specific services often leads to inefficiencies system-wide.

BRIEF SUMMARY

Embodiments described herein are directed to providing dynamically updatable web service components. In one embodiment, a computer system receives, at a dynamic web service configuration store, registration information from a service provider registering web services with the dynamic web service configuration store, the registration information indicating a mapping of which web service components are to be used with corresponding user requests. The computer system receives a request from a user requesting a portion of web service functionality and provides the web service functionality using the web service component indicated in the mapping. The computer system receives an indication from the service provider that various web service components are to be updated, the indication including updated web service component portions. The computer system also dynamically updates the web service component, so that subsequent user requests for the same portion of web service functionality are processed using the updated web service component.

In an alternative embodiment, a computer system receives at a dynamic web service configuration store a request from a user for a portion of web service functionality, where the dynamic web service configuration store is configurable to allow dynamic changes to both web service component mappings indicating which web service components are to be used with a corresponding user request, and data structure mappings indicating which data structures are to be used with a corresponding user request. The computer system determines an appropriate web service component and data structure mapping based on the received user request. The computer system provides the web service functionality using the web service component and data structure indicated in the mapping and determines that a web service component has been dynamically updated based on information provided to the dynamic web service configuration store by the web service provider. The computer system also dynamically implements the updated component to process subsequent user requests.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

To further clarify the above and other advantages and features of embodiments of the present invention, a more particular description of embodiments of the present invention will be rendered by reference to the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates a computer architecture in which embodiments of the present invention may operate including providing dynamically updatable web service components.

<figref idrefs="DRAWINGS">FIG. 2</figref> illustrates a flowchart of an example method for providing dynamically updatable web service components.

<figref idrefs="DRAWINGS">FIG. 3</figref> illustrates a flowchart of an alternative example method for providing dynamically updatable web service components.

<figref idrefs="DRAWINGS">FIG. 4</figref> illustrates a computer architecture which includes elements embodiment of the present invention in which.

DETAILED DESCRIPTION

Embodiments described herein are directed to providing dynamically updatable web service components. In one embodiment, a computer system receives, at a dynamic web service configuration store, registration information from a service provider registering web services with the dynamic web service configuration store, the registration information indicating a mapping of which web service components are to be used with corresponding user requests. The computer system receives a request from a user requesting a portion of web service functionality and provides the web service functionality using the web service component indicated in the mapping. The computer system receives an indication from the service provider that various web service components are to be updated, the indication including updated web service component portions. The computer system also dynamically updates the web service component, so that subsequent user requests for the same portion of web service functionality are processed using the updated web service component.

In an alternative embodiment, a computer system receives at a dynamic web service configuration store a request from a user for a portion of web service functionality, where the dynamic web service configuration store is configurable to allow dynamic changes to both web service component mappings indicating which web service components are to be used with a corresponding user request, and data structure mappings indicating which data structures are to be used with a corresponding user request. The computer system determines an appropriate web service component and data structure mapping based on the received user request. The computer system provides the web service functionality using the web service component and data structure indicated in the mapping and determines that a web service component has been dynamically updated based on information provided to the dynamic web service configuration store by the web service provider. The computer system also dynamically implements the updated component to process subsequent user requests.

Embodiments of the present invention may comprise or utilize a special purpose or general-purpose computer including computer hardware, as discussed in greater detail below. Embodiments within the scope of the present invention also include physical and other computer-readable storage media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are physical storage media including recordable-type storage media. Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: physical storage media and transmission media.

Physical storage media includes RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.

A “network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmission media can include a network and/or data links which can be used to carry or transport desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.

However, it should be understood, that upon reaching various computer system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to physical storage media. For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface card, and then eventually transferred to computer system RAM and/or to less volatile physical storage media at a computer system. Thus, it should be understood that physical storage media can be included in computer system components that also (or even primarily) utilize transmission media.

Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

Those skilled in the art will appreciate that the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, pagers, routers, switches, and the like. The invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates a computer architecture <b>100</b> in which the principles of the present invention may be employed. Computer architecture <b>100</b> includes intermediary computer system <b>110</b> (“intermediary <b>110</b>” or “system <b>110</b>” herein). Intermediary <b>110</b> may be any type of computing system including a server computing system, client computing system (including portable computing systems such as laptops) or any other type of computing system. Intermediary <b>110</b> includes dynamic web service configuration store <b>115</b> (“configuration store <b>115</b>” herein) which is configured to interact with other elements and modules of architecture <b>100</b>.

For example, configuration store <b>115</b> may receive registration information <b>107</b> from service provider <b>105</b>. Service provider <b>105</b> may be any type of computer user or entity including developers, companies, end-users or other persons capable of providing a service. Typically, such services are web services accessible through a browser. However, the services provided by service provider <b>105</b> may be any type of services including stand-alone applications, server applets or other portions of software code or portions of software applications. Registration information <b>107</b> may include information about the various services provided by service provider <b>105</b>. In addition to identifying those services that are provided, registration information <b>107</b> may also identify how to interact with or initiate those services. For instance, various web service components may be initialized using component mappings <b>108</b>. As web service components are changed by the developer (or other users), the updates <b>106</b> may be sent to intermediary computer system <b>110</b>, which may be then incorporated into the existing (registered) web services <b>116</b> by web service updating module <b>117</b>.

Thus, service provider <b>105</b> may be able to register a web service which is stored in configuration store <b>115</b> as a registered service <b>116</b>. Component mappings <b>108</b> may be used to identify various components within the registered web service, each of which may be individually updatable. The updates, sent as updated component information <b>106</b>, may be applied dynamically while the web service is running and may be applied automatically on a set schedule or at a user-appointed time. As web service updating module <b>117</b> applies the component updates, end-user <b>125</b> may, in response to web service request <b>121</b>, receive web service <b>121</b> with updated components. Thus, in some embodiments, a user may request a web service and begin using that service while, in the background, the service provider is updating one or more components of that web service. Upon detecting that at least some of the web service's components have been updated, intermediary computer system <b>110</b> can immediately begin providing the web service <b>121</b> with the updated components. In some cases, the transition to a new web service component may occur transparently to the user. In other cases, where the changes to the web service component(s) are more drastic, user <b>125</b> may be aware that parts of the web service have changed. This process will be described in greater detail below with regard to method <b>200</b> of <figref idrefs="DRAWINGS">FIG. 2</figref>.

<figref idrefs="DRAWINGS">FIG. 2</figref> illustrates a flowchart of a method <b>200</b> for providing dynamically updatable web service components. The method <b>200</b> will now be described with frequent reference to the components and data of environments <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1 and 400</figref> of <figref idrefs="DRAWINGS">FIG. 4</figref>.

Method <b>200</b> includes an act of receiving at a dynamic web service configuration store registration information from a service provider registering one or more web services with the dynamic web service configuration store, the registration information indicating a mapping of which web service components are to be used with corresponding user requests (act <b>210</b>). For example, dynamic web service configuration store <b>115</b> may be configured to receive registration information <b>107</b> from service provider <b>105</b> registering various web services with the configuration store. Registration information <b>107</b> may indicate a mapping (<b>108</b>) of which web service components are to be used in conjunction with a received web service request <b>120</b> received from user <b>125</b>. Thus, in one embodiment, a user may send a web service request through the user's interaction with a web browser. The request <b>120</b> is received by intermediary system <b>110</b>, upon which the system determines which service(s) or service components are to be used to handle the user's service request. In some cases, component mappings <b>108</b> may be stored in configuration store <b>115</b> as stored component mappings <b>108</b>S in a look-up table or other data structure. As a result, a web service request may simply query configuration store <b>115</b> to determine which service components are to be used to satisfy a client's web service request.

In some cases, configuration store <b>115</b> may be configurable to allow dynamic changes to both web service component mappings <b>108</b> indicating which components are to be used with a corresponding user request, as well as data structure mappings (which may be part of component mappings <b>108</b>) indicating which data structures are to be used with a corresponding user request. Accordingly, when service provider <b>105</b> desires to make a change to a web service or web service component, the service provider is able to dynamically change (via updates <b>106</b>) which web service components are to be used to handle certain user web service requests. Moreover, the service provider is also to dynamically change which data structures are to be used to process the user's service request. For example, in a business-oriented web service such as an order processing service, the service provider may be able to choose between different formats for storing the user's contact information, order information, and shipment information. This is just one example of how a service provider can change the component mapping information, and should not be read as being limited to the above example.

Dynamic web service configuration store <b>115</b> may be configured to receive and store updates received from a variety of different service providers. Intermediary computer system <b>110</b> may be configured to process a substantially limitless number of web service registrations and may also receive updates regarding different web services, components and/or mappings. Thus, a service provider may have up-to-the minute control over which web services or web service components are being used to handle a client's web service request.

Method <b>200</b> includes an act of receiving a request from a user requesting a portion of web service functionality (act <b>220</b>). For example, intermediary system <b>110</b> may receive web service request <b>120</b> from user <b>125</b> requesting a portion of web service functionality. In some cases, the requested portion of web service functionality provided by the web service component may comprise a business action such as the signing-up of a new customer. The service provider may be able to specify which web service (component) is used to process the signing-up. As explained above, the service provider may, after an initial web service has been chosen, update the entire service or a component thereof, and while updating the component, update the component's corresponding mapping to ensure that the new component is used to process the user's request. When updating the mapping, the service provider may update the manner in which the web service (business action) maps to one or more web service data structures. The data structures may also be updated separately from, or in addition to, the web service component mappings.

Method <b>200</b> includes an act of providing the web service functionality using the web service component indicated in the mapping (act <b>230</b>). For example, intermediary computer system <b>110</b> may provide the web service functionality (<b>121</b>) to user <b>125</b> using the web service component indicated in the mapping. Thus, if user <b>125</b> requests functionality A in web service request <b>120</b>, intermediary server <b>110</b> (or configuration store <b>115</b>) will check the mappings stored with registered services <b>116</b> to determine which web service or web service component is to be used to provide functionality A. This service is selected, and the user's request is processed using the selected web service.

Method <b>200</b> includes an act of receiving an indication from the service provider that one or more web service components are to be updated, the indication including one or more updated web service component portions (act <b>240</b>). For example, intermediary computing system <b>110</b> may receive updated component information <b>106</b> indicating that one or more web service components are to be updated. The updated component information may also include updated web service component portions or entire web service components.

Method <b>200</b> includes an act of dynamically updating the web service component, such that subsequent user requests for the same portion of web service functionality are processed using the updated web service component (act <b>250</b>). For example, web service updating module <b>117</b> of intermediary computer system <b>110</b> may dynamically update any of the web service components stored in configuration store <b>115</b>. In this manner, any web service requests received requesting the functionality provided by the updated web service. In some cases, the mapping indicating which user requests are to be handled by a given web service (or group of services) is automatically updated based on a determination that the web service component has been updated. Thus, intermediary computer system may detect when a component has been updated and, as a result, automatically update the mapping to map to the current, updated version of the component.

Updating the web service components may include adding extended functionality to an existing web service component, so that the updated existing web service component is configured to provide both its existing functionality and the newly extended functionality. In some cases, intermediary computer system <b>110</b> may determine that changes have been made to one or more data files in a database communicatively connected to the dynamic web service configuration store <b>115</b>. In response, system <b>110</b> may automatically and dynamically update those web service components configured to use the updated data files. Accordingly, as illustrated in environment <b>400</b> of <figref idrefs="DRAWINGS">FIG. 4</figref>, intermediary computer system <b>410</b> may be configured to communicate with web service database to access both the web services and information that is used by the web service. This process may be performed as a result of a web service request received from a user at a browser <b>430</b> (or from web service <b>421</b> which may be running as part of browser <b>430</b>). The intermediary computer system <b>410</b> may thus provide web service <b>421</b> to the user via the browser, the web service including (or having access to) the information stored in web service database <b>401</b>.

<figref idrefs="DRAWINGS">FIG. 3</figref> illustrates a flowchart of a method <b>300</b> for providing dynamically updatable web service components. The method <b>300</b> will now be described with frequent reference to the components and data of environments <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1 and 400</figref> of <figref idrefs="DRAWINGS">FIG. 4</figref>.

Method <b>300</b> includes an act of receiving at a dynamic web service configuration store a request from a user for a portion of web service functionality, the dynamic web service configuration store being configurable to allow dynamic changes to both web service component mappings indicating which web service components are to be used with a corresponding user request, and data structure mappings indicating which data structures are to be used with a corresponding user request (act <b>310</b>). For example, configuration store <b>115</b> may receive web service request <b>120</b> from user <b>125</b> requesting a portion of web service functionality. Configuration store <b>115</b> may be configurable to allow dynamic changes to both web service component mappings <b>108</b> indicating which web service components are to be used with a corresponding user request (e.g. <b>120</b>), as well as data structure mappings indicating which data structures are to be used with a corresponding user request. In some cases, a request for web service functionality is received from a web application (such as from web service <b>421</b> which may be operating with browser <b>430</b>). As explained above, dynamic web service configuration store <b>115</b> may be configured to receive and store requests received from multiple different end users <b>125</b>.

Method <b>300</b> includes an act of determining an appropriate web service component and data structure mapping based on the received user request (act <b>320</b>). For example, intermediary computer system <b>110</b> may determine, using mappings <b>108</b>, which web service component and data structure mapping are appropriate to use to process each user's request, based on the functionality requested by each respective user.

Method <b>300</b> includes an act of providing the web service functionality using the web service component and data structure indicated in the mapping (act <b>330</b>). For example, intermediary computer system <b>110</b> may provide web service functionality <b>121</b> to user <b>125</b> using the web service component(s) and/or data structure(s) indicated in mappings <b>108</b>. In some cases, providing the web service functionality may include sending a web services description language (WSDL) data portion to the user indicating which web service component is to be used. User <b>125</b>'s browser may be configured to receive and interpret the WSDL data portion and use the information stored in the data to identify which web service component is to be used to handle the user's request.

Method <b>300</b> includes an act of determining that a web service component has been dynamically updated based on information provided to the dynamic web service configuration store by the web service provider (act <b>340</b>). For example, intermediary computer system <b>110</b> may determine that at least one of the components of a web service have been dynamically updated based on information provided to configuration store <b>115</b> by service provider <b>105</b>. Thus, intermediary system <b>110</b> may be informed any time a web service component is updated; thus, when a web service request is received, system <b>110</b> will know to use the updated web service to process the user's request. Additionally or alternatively, intermediary system <b>110</b> may determine that data used by a web service component itself in providing the web service functionality has been updated and, based on that determination, automatically update the corresponding web service's mappings. In such cases, changes made to data used by the web service component to provide the web service functionality may automatically cause the dynamic web service configuration store <b>115</b> to update one or more business actions made available by the web service component, based on the changes to the data.

Method <b>300</b> also includes an act of dynamically implementing the updated component to process subsequent user requests (act <b>350</b>). For example, intermediary computing system may dynamically implement the updated component to process subsequent user requests for the updated web service. In some cases, intermediary system <b>110</b> may determine that changes have been made to one or more data files in a database communicatively connected to the dynamic web service configuration store and, based on that determination, automatically and dynamically update those web service components configured to use the updated data files. In this manner, a service provider can easily and dynamically update web service components without having to update the entire web service. Moreover, intermediary system <b>110</b> can automatically update the mappings when a new web service or web service component is uploaded. This helps to ensure that the user is always using the most up-to-date version of the web service component.

The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.