CA2405673C - Provisioning web services - Google Patents
Provisioning web services Download PDFInfo
- Publication number
- CA2405673C CA2405673C CA002405673A CA2405673A CA2405673C CA 2405673 C CA2405673 C CA 2405673C CA 002405673 A CA002405673 A CA 002405673A CA 2405673 A CA2405673 A CA 2405673A CA 2405673 C CA2405673 C CA 2405673C
- Authority
- CA
- Canada
- Prior art keywords
- web service
- provisioning
- web
- web services
- processes data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
- 238000000034 method Methods 0.000 claims abstract description 69
- 230000002596 correlated effect Effects 0.000 claims abstract description 21
- 238000013500 data storage Methods 0.000 claims 2
- 238000004590 computer program Methods 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 6
- 239000000203 mixture Substances 0.000 description 5
- 238000004883 computer application Methods 0.000 description 2
- 230000000875 corresponding effect Effects 0.000 description 2
- 101100238304 Mus musculus Morc1 gene Proteins 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007935 neutral effect Effects 0.000 description 1
- 238000004801 process automation Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
Abstract
A web service provisioning system including a subscription system having a web service description data correlated to the at least one web service, and provisioning processes data correlated to the at least one web service. The provisioning system also includes an invocation system operatively coupled to the subscription system. A method of provisioning at least one web service, the method including the steps of providing user profile data; providing web service description data correlated to the at least one web service; providing provisioning processes data correlated to the at least one web service; selecting at least one web service; and invoking the provisioning processes data correlated to the selected at least one web service.
Description
PROVISIONING WEB SERVICES
FIELD OF THE INVENTION
This invention relates to the field of web services, and in particular to the provisioning of web services.
BACKGROUND
Web services are computer operations or functions that can be invoked remotely using an Internet based protocol over the web.
Communication between the client and server takes place over the Internet using standard Internet protocols. Simple Object Access Protocol (SOAP) over Hypertext Transfer Protocol (HTTP) is commonly used. A web service can be invoked from any machine that has Internet access, and the services themselves can be hosted in any data center that provides HTTP access.
As well, web services are currently defined using the Web Services Definition Language (WSDL). WSDL is a meta-description of web services. In addition to being readable by a human user, WSDL is easily read and processed by computer applications. This enables better web service client and server composition tools, as well as dynamic discovering, binding and use classes of applications.
Web services exchange data through the use of text based XML documents. These documents may be specified in a fashion that is computer language and computer platform neutral.
As a result, web services may be invoked from any client to any server without requiring the client and server to utilize the same language or operating system.
Web Services Flow Language (WSFL) is a standard that supports the composition of web services into business process models. It does this by capturing the orchestration and choreography of a given composition of services.
Many computer applications exist for the modeling ofbusiness processes. These applications enable the creation of the models to automate the business process. The modeled processes are called workflows. The component of an application, which performs the process automation, is called a workflow engine.
Certain web services, particularly those for which fees and financial accounts are involved typically require significant provisioning or preparation of associated resources.
Accordingly, the inventors have recognized the need to provide systems and methods for provisioning web services.
SUMMARY OF THE INVENTION
An aspect of the present invention is directed towards a web service provisioning system for provisioning at least one web service.
The provisioning system includes a subscription system having web service description data correlated to the at least one web service, and provisioning processes data correlated to the at least one web service. The provisioning system also includes an invocation system operatively coupled to the subscription system.
The provisioning system may also include a service catalog system configured to select at least one web service. The service catalog system may also be configured to determine user profile data. Preferably, the invocation system includes a workflow execution engine configured to receive user profile data and provisioning processes data, and configured to invoke provisioning processes data.
Another aspect of the present invention is directed towards a method of provisioning at least one web service, the method comprising the following steps:
a. providing user profile data;
b. providing web service description data correlated to the at least one web service;
c. providing web service provisioning processes data correlated to the at least one web service;
d. selecting at least one web service;
e. invoking the web service provisioning processes data correlated to the selected at least one web service.
BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments of the present invention will now be described, by way of example only, with reference to the following drawings, in which like reference numerals refer to like parts and in which:
FIGURE 1 is a schematic diagram of the components of a web services system which must be provisioned in order to give a consumer access to a web service;
FIGURE 2 is a schematic diagram of a web provisioning system, made in accordance with the present invention;
FIGURE 3 is a schematic diagram of the invocation system portion of the web provisioning system of Figure 2;
FIGURE 4 is a flow diagram of the method of provisioning a web service in accordance with the present invention; and FIGURE 5 is a schematic diagram of a provisioned web service.
DETAILED DESCRIPTION OF THE INVENTION
The procedure used to complete a task within a business is called a business process.
Consider the process followed when a request to purchase a stock is performed over the phone. The customer representative (CR) first verifies the identity of the caller who is requesting the purchase, and finds the customer account. Next the CR forwards the request to the trader to make the purchase. Once completed, a confirmation of the purchase must be provided back to the customer, and the customer's account debited for the cost of the transaction. There maybe an approval step involved, for example if the purchase was for a significant number of shares, or for an amount that exceeded the customer's current account balance.
A business process can be represented with a process description language. If the steps of the process can be automated, a program that can interpret the process description language may be used to manage the process from start to completion. A description that represents a business process is often referred to as a workflow.
Consider the process to purchase stocks on behalf of a customer described above. Each of the steps of that process could be implemented as a web service that can be invoked remotely via the Internet. Such a complex process could be described as a composition of web services. As will be understood by one skilled in the art, the Web Services Flow Language (WSFL) can be used to represent compositions of web services.
A simple web service could be developed to determine a stock quote:
getStockQuote( String symbol );
A service of this type is a remote procedure call (RPC) that would be invoked by a client application. As will be understood, the stock "symbol" is a parameter which is required to invoke the procedure call. A typical implementation of this web service would be the conversion of the request into a proprietary call over a local connection to retrieve the current stock price from an application which keeps track of stock prices. The result would be converted back to SOAP format and returned to the client application.
Such a web service can be invoked without requiring information about the identity of the caller. As noted, the only required parameter is the stock symbol. Many organizations offer this type of web service free of charge.
Consider now the implementation of a web service that is used to purchase a stock. This call might appear as:
purchaseStock( String symbol, String accountID, Int numberOfShares );
In this example, the required parameters include the referenced account ("accountID"). The account must be known to the system providing the web service beforehand, in order to verify the account information and to assign the ownership of the purchased stocks appropriately. Typically, a commission would be charged against the account (often based on the value of the stock purchased), in addition to a fixed charge for using the web service.
Accordingly, before a customer can use the purchaseStock web service, an account must be established for that customer, and other information such as the customer's name and address must be provided. The data center network infrastructure must be configured to route the web service requests and responses appropriately. These steps are a business process.
Configuring a system with account and other information sufficient to allow a particular consumer to access a particular web service is referred to as "provisioning".
Figure 1 illustrates a typical commercial web service system, shown generally as 10, and components 12 that may need to be provisioned in order to give a consumer 14 access to a web service 16 (such as the purchaseStock web service discussed above) over the Internet 18.
The components 12 of the web service system 10 may include a Security System 20 or module, which will need to be provided with a user identity and/or password in order to authenticate the consumer 14 when using the web service 16. The Security System 20 will also often require a list of the system 10 resources to which the consumer 14 will need access to use the web service 16.
A Billing System 22 or module may also be required in order to charge the consumer 14 for the use of the web service 16. Accordingly, the Billing System will need to be provisioned with a billing account for that consumer 14. A User Profile System 24 or module is also common. Typically, the User Profile System 24 will be provisioned with and record personal information or user profile data about the consumer, such as the consumer's name, address and phone number.
While not shown, other components will often require provisioning for elaborate commercial web services.
As will be understood, the steps in the provisioning process for the web service system 10 would typically include: configuring the Security System 20 with the consumer's 14 identity and/or password; creating an account for the consumer 14 in the Billing System 22;
storing the consumer's 14 user profile data in the User Profile System 24; and informing the component providing the web service 16 that the consumer 14 is ready to access the web service 16.
Figure 2 illustrates a WSFL-based web service provisioning system, shown generally as 100, made in accordance with the present invention. The provisioning system 100 includes a subscription system 110 and an invocation system 112.
The subscription system 110 includes a service catalog system or module 114, as well as a web service provisioning database 116. The provisioning database 116 contains web service description data 118 (ie. a WSDL description correlated to each web service 16), and WSFL
provisioning process (or workflow) data 120 corresponding to the web service steps required for provisioning each web service 16. The service catalog module 114 is configured to present to the user 14 each of the available web services (including web service 16), as well as the correlated WSDL description for each available web service. Through the service catalog module 114, the user 14 may then select one or more desired web services 16.
The service catalog module 114 is also configured to determine and store user profile data 122 (shown on FIG. 3) eorresponding to thc user 14, typically by requirinp, the uscr 14 to input the requirui data.
t)ncc the user has aelccted rt web servicc 16, the service catalog urodule 1 10 p;tsscs the WSh'l.
provisioning process da.ta 120 correlated to the web servicc 16, as well as the user prorile data 122. to the invocation system 112. 'I'ypically, the WSFI. provisioning process data 120 and thc user profile data 122 are stored and transferred as text based XMI, dtx.umcnls.
FIG. 3 illustratcs in greater detail the basic components of thc invocation system 112, and its rclAtiunship to the components to be provisionCd. 'l he invocation system 112 includes a WSFL
exccution engine 130, which is provided witlt the WSFI, provisioning liroccss data 120 A nd the user profile data 122.
As illustrated in H'IG. 3, cach of the stcps in the pmvisiorting process exists as a node 132 in the WSFI. provisionint; process data 120. Each node 132 contains wcb service invocation data for invoking a particidar provisioning wcb service crcatod to intplcincrrt one step of' the provisioning process.
By way of examplc ortly, the following illustrat.cs a simple provisiuning worktlow. 7'he first tlude 134 may be designed to invoke a web service which cstablishec $ user identity and/or password on the security system 20 corresponeling to the consumer 14. Similarly, the second node 136 rnay ittvoke a web service for storing the uscr proGle data 122 in the user prolile system 24. The third node 138 nisy invoke a web service for eruating a billing account correspondinp, to the user 14 on the hilling system 22. A fourth nodc 140 may also be required to invoke a web service tor iriforming the eomponent providing the wcb service 16 that the consumer 14 is ready to access the web service 16.
As noted prcviously, however, a cornprehensivc commercial web service systeni 10 may include other components which require pruvisioning, and whicl- will result in additional corresponding nodes 132 in the pmvisioning process data 120.
As will he underatond, one or morc of the nodes 132 in a provisioning process may be interruptible. Such interruptible workflow steps may require dccision-making or ntlicr human interaction by thc service provider_ Pnr cxample, an interruptiblc workflow step or node 132 may be provided which allows the scrvice provider to detcrrnine ifthc web service 16 for a partiwiar user 14 will be operate on a fast.wrver or a slower one, possibly based on the user's 14 anticipaled ('A9-2002-0062 6 requirements.
Referring now to Figure 4, illustrated therein is a logical flow diagram summarizing the steps carried out in provisioning at least one web service in accordance with the method 200 of the present invention, described in greater detail, above. These steps include providing user profile data (Block 210), and providing web service description data correlated to the at least one web service (Block 212). The method 200 also includes the step of providing provisioning processes data correlated to the at least one web service (Block 214). Typically the provisioning processes data is in WSFL
format. Finally, the method 200 includes the steps of selecting at least one web service (Block 216), and invoking the provisioning processes data correlated to the selected at least one web service (Block 218).
Figure 5 illustrates the process of invoking a web service once the various components have been provisioned by the web service provisioning system 100. When the user's 14 client application 150 requests invocation of the web service 16, the web services server 152 (and particularly the security system 20) will first verify the identity of the user 14. The user data provided by the client application 150 is compared to data stored by the security system 20 during the provisioning process.
If the identity of the user 14 is valid, the billing system 22 will be informed of the invocation of the web service 16, in order to appropriately invoice the user's 14 account (also created during the provisioning process) for charges established for using the web service 16.
Finally, the web service 16 itself will be invoked.
Thus, while what is shown and described herein constitutes preferred embodiments of the subject invention, it should be understood that various changes can be made without departing from the subject invention, the scope of which is defined in the appended claims.
FIELD OF THE INVENTION
This invention relates to the field of web services, and in particular to the provisioning of web services.
BACKGROUND
Web services are computer operations or functions that can be invoked remotely using an Internet based protocol over the web.
Communication between the client and server takes place over the Internet using standard Internet protocols. Simple Object Access Protocol (SOAP) over Hypertext Transfer Protocol (HTTP) is commonly used. A web service can be invoked from any machine that has Internet access, and the services themselves can be hosted in any data center that provides HTTP access.
As well, web services are currently defined using the Web Services Definition Language (WSDL). WSDL is a meta-description of web services. In addition to being readable by a human user, WSDL is easily read and processed by computer applications. This enables better web service client and server composition tools, as well as dynamic discovering, binding and use classes of applications.
Web services exchange data through the use of text based XML documents. These documents may be specified in a fashion that is computer language and computer platform neutral.
As a result, web services may be invoked from any client to any server without requiring the client and server to utilize the same language or operating system.
Web Services Flow Language (WSFL) is a standard that supports the composition of web services into business process models. It does this by capturing the orchestration and choreography of a given composition of services.
Many computer applications exist for the modeling ofbusiness processes. These applications enable the creation of the models to automate the business process. The modeled processes are called workflows. The component of an application, which performs the process automation, is called a workflow engine.
Certain web services, particularly those for which fees and financial accounts are involved typically require significant provisioning or preparation of associated resources.
Accordingly, the inventors have recognized the need to provide systems and methods for provisioning web services.
SUMMARY OF THE INVENTION
An aspect of the present invention is directed towards a web service provisioning system for provisioning at least one web service.
The provisioning system includes a subscription system having web service description data correlated to the at least one web service, and provisioning processes data correlated to the at least one web service. The provisioning system also includes an invocation system operatively coupled to the subscription system.
The provisioning system may also include a service catalog system configured to select at least one web service. The service catalog system may also be configured to determine user profile data. Preferably, the invocation system includes a workflow execution engine configured to receive user profile data and provisioning processes data, and configured to invoke provisioning processes data.
Another aspect of the present invention is directed towards a method of provisioning at least one web service, the method comprising the following steps:
a. providing user profile data;
b. providing web service description data correlated to the at least one web service;
c. providing web service provisioning processes data correlated to the at least one web service;
d. selecting at least one web service;
e. invoking the web service provisioning processes data correlated to the selected at least one web service.
BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments of the present invention will now be described, by way of example only, with reference to the following drawings, in which like reference numerals refer to like parts and in which:
FIGURE 1 is a schematic diagram of the components of a web services system which must be provisioned in order to give a consumer access to a web service;
FIGURE 2 is a schematic diagram of a web provisioning system, made in accordance with the present invention;
FIGURE 3 is a schematic diagram of the invocation system portion of the web provisioning system of Figure 2;
FIGURE 4 is a flow diagram of the method of provisioning a web service in accordance with the present invention; and FIGURE 5 is a schematic diagram of a provisioned web service.
DETAILED DESCRIPTION OF THE INVENTION
The procedure used to complete a task within a business is called a business process.
Consider the process followed when a request to purchase a stock is performed over the phone. The customer representative (CR) first verifies the identity of the caller who is requesting the purchase, and finds the customer account. Next the CR forwards the request to the trader to make the purchase. Once completed, a confirmation of the purchase must be provided back to the customer, and the customer's account debited for the cost of the transaction. There maybe an approval step involved, for example if the purchase was for a significant number of shares, or for an amount that exceeded the customer's current account balance.
A business process can be represented with a process description language. If the steps of the process can be automated, a program that can interpret the process description language may be used to manage the process from start to completion. A description that represents a business process is often referred to as a workflow.
Consider the process to purchase stocks on behalf of a customer described above. Each of the steps of that process could be implemented as a web service that can be invoked remotely via the Internet. Such a complex process could be described as a composition of web services. As will be understood by one skilled in the art, the Web Services Flow Language (WSFL) can be used to represent compositions of web services.
A simple web service could be developed to determine a stock quote:
getStockQuote( String symbol );
A service of this type is a remote procedure call (RPC) that would be invoked by a client application. As will be understood, the stock "symbol" is a parameter which is required to invoke the procedure call. A typical implementation of this web service would be the conversion of the request into a proprietary call over a local connection to retrieve the current stock price from an application which keeps track of stock prices. The result would be converted back to SOAP format and returned to the client application.
Such a web service can be invoked without requiring information about the identity of the caller. As noted, the only required parameter is the stock symbol. Many organizations offer this type of web service free of charge.
Consider now the implementation of a web service that is used to purchase a stock. This call might appear as:
purchaseStock( String symbol, String accountID, Int numberOfShares );
In this example, the required parameters include the referenced account ("accountID"). The account must be known to the system providing the web service beforehand, in order to verify the account information and to assign the ownership of the purchased stocks appropriately. Typically, a commission would be charged against the account (often based on the value of the stock purchased), in addition to a fixed charge for using the web service.
Accordingly, before a customer can use the purchaseStock web service, an account must be established for that customer, and other information such as the customer's name and address must be provided. The data center network infrastructure must be configured to route the web service requests and responses appropriately. These steps are a business process.
Configuring a system with account and other information sufficient to allow a particular consumer to access a particular web service is referred to as "provisioning".
Figure 1 illustrates a typical commercial web service system, shown generally as 10, and components 12 that may need to be provisioned in order to give a consumer 14 access to a web service 16 (such as the purchaseStock web service discussed above) over the Internet 18.
The components 12 of the web service system 10 may include a Security System 20 or module, which will need to be provided with a user identity and/or password in order to authenticate the consumer 14 when using the web service 16. The Security System 20 will also often require a list of the system 10 resources to which the consumer 14 will need access to use the web service 16.
A Billing System 22 or module may also be required in order to charge the consumer 14 for the use of the web service 16. Accordingly, the Billing System will need to be provisioned with a billing account for that consumer 14. A User Profile System 24 or module is also common. Typically, the User Profile System 24 will be provisioned with and record personal information or user profile data about the consumer, such as the consumer's name, address and phone number.
While not shown, other components will often require provisioning for elaborate commercial web services.
As will be understood, the steps in the provisioning process for the web service system 10 would typically include: configuring the Security System 20 with the consumer's 14 identity and/or password; creating an account for the consumer 14 in the Billing System 22;
storing the consumer's 14 user profile data in the User Profile System 24; and informing the component providing the web service 16 that the consumer 14 is ready to access the web service 16.
Figure 2 illustrates a WSFL-based web service provisioning system, shown generally as 100, made in accordance with the present invention. The provisioning system 100 includes a subscription system 110 and an invocation system 112.
The subscription system 110 includes a service catalog system or module 114, as well as a web service provisioning database 116. The provisioning database 116 contains web service description data 118 (ie. a WSDL description correlated to each web service 16), and WSFL
provisioning process (or workflow) data 120 corresponding to the web service steps required for provisioning each web service 16. The service catalog module 114 is configured to present to the user 14 each of the available web services (including web service 16), as well as the correlated WSDL description for each available web service. Through the service catalog module 114, the user 14 may then select one or more desired web services 16.
The service catalog module 114 is also configured to determine and store user profile data 122 (shown on FIG. 3) eorresponding to thc user 14, typically by requirinp, the uscr 14 to input the requirui data.
t)ncc the user has aelccted rt web servicc 16, the service catalog urodule 1 10 p;tsscs the WSh'l.
provisioning process da.ta 120 correlated to the web servicc 16, as well as the user prorile data 122. to the invocation system 112. 'I'ypically, the WSFI. provisioning process data 120 and thc user profile data 122 are stored and transferred as text based XMI, dtx.umcnls.
FIG. 3 illustratcs in greater detail the basic components of thc invocation system 112, and its rclAtiunship to the components to be provisionCd. 'l he invocation system 112 includes a WSFL
exccution engine 130, which is provided witlt the WSFI, provisioning liroccss data 120 A nd the user profile data 122.
As illustrated in H'IG. 3, cach of the stcps in the pmvisiorting process exists as a node 132 in the WSFI. provisionint; process data 120. Each node 132 contains wcb service invocation data for invoking a particidar provisioning wcb service crcatod to intplcincrrt one step of' the provisioning process.
By way of examplc ortly, the following illustrat.cs a simple provisiuning worktlow. 7'he first tlude 134 may be designed to invoke a web service which cstablishec $ user identity and/or password on the security system 20 corresponeling to the consumer 14. Similarly, the second node 136 rnay ittvoke a web service for storing the uscr proGle data 122 in the user prolile system 24. The third node 138 nisy invoke a web service for eruating a billing account correspondinp, to the user 14 on the hilling system 22. A fourth nodc 140 may also be required to invoke a web service tor iriforming the eomponent providing the wcb service 16 that the consumer 14 is ready to access the web service 16.
As noted prcviously, however, a cornprehensivc commercial web service systeni 10 may include other components which require pruvisioning, and whicl- will result in additional corresponding nodes 132 in the pmvisioning process data 120.
As will he underatond, one or morc of the nodes 132 in a provisioning process may be interruptible. Such interruptible workflow steps may require dccision-making or ntlicr human interaction by thc service provider_ Pnr cxample, an interruptiblc workflow step or node 132 may be provided which allows the scrvice provider to detcrrnine ifthc web service 16 for a partiwiar user 14 will be operate on a fast.wrver or a slower one, possibly based on the user's 14 anticipaled ('A9-2002-0062 6 requirements.
Referring now to Figure 4, illustrated therein is a logical flow diagram summarizing the steps carried out in provisioning at least one web service in accordance with the method 200 of the present invention, described in greater detail, above. These steps include providing user profile data (Block 210), and providing web service description data correlated to the at least one web service (Block 212). The method 200 also includes the step of providing provisioning processes data correlated to the at least one web service (Block 214). Typically the provisioning processes data is in WSFL
format. Finally, the method 200 includes the steps of selecting at least one web service (Block 216), and invoking the provisioning processes data correlated to the selected at least one web service (Block 218).
Figure 5 illustrates the process of invoking a web service once the various components have been provisioned by the web service provisioning system 100. When the user's 14 client application 150 requests invocation of the web service 16, the web services server 152 (and particularly the security system 20) will first verify the identity of the user 14. The user data provided by the client application 150 is compared to data stored by the security system 20 during the provisioning process.
If the identity of the user 14 is valid, the billing system 22 will be informed of the invocation of the web service 16, in order to appropriately invoice the user's 14 account (also created during the provisioning process) for charges established for using the web service 16.
Finally, the web service 16 itself will be invoked.
Thus, while what is shown and described herein constitutes preferred embodiments of the subject invention, it should be understood that various changes can be made without departing from the subject invention, the scope of which is defined in the appended claims.
Claims (3)
1. A web service provisioning system for provisioning a plurality of web service, the provisioning system comprising:
a- a subscription system including web service description data storage for storing web service description data correlated to each web service of the plurality of web services, wherein the web service description data defines the respective web services in Web Services Definition language, and provisioning processes data storage for storing respective provisioning processes data for each web service of the plurality of web services and for each of a plurality of provisioning web services that correlate to respective administrative systems supporting the plurality of web services, wherein the provisioning processes data is in Web Services Flow Language; and b. an invocation system operatively coupled to the subscription system and configured for:
receiving a selection of a first web service;
invoking the respective provisioning processes data for the first web service, and invoking the respective provisioning processes data for each provisioning web service that correlates to an administrative system supporting the first web service, wherein the provisioning processes data comprises a plurality of nodes, wherein each node of the plurality of nodes comprises web service invocation data for invoking the respective provisioning web service.
a- a subscription system including web service description data storage for storing web service description data correlated to each web service of the plurality of web services, wherein the web service description data defines the respective web services in Web Services Definition language, and provisioning processes data storage for storing respective provisioning processes data for each web service of the plurality of web services and for each of a plurality of provisioning web services that correlate to respective administrative systems supporting the plurality of web services, wherein the provisioning processes data is in Web Services Flow Language; and b. an invocation system operatively coupled to the subscription system and configured for:
receiving a selection of a first web service;
invoking the respective provisioning processes data for the first web service, and invoking the respective provisioning processes data for each provisioning web service that correlates to an administrative system supporting the first web service, wherein the provisioning processes data comprises a plurality of nodes, wherein each node of the plurality of nodes comprises web service invocation data for invoking the respective provisioning web service.
2. A method of provisioning a plurality of web services, the method comprising:
providing web service description data, correlated to each web service of the plurality of web services, wherein the web service description data is in Web Services Definition Language;
providing respective provisioning processes data for each web service of the plurality of web services and for each of a plurality of provisioning web services that correlate to respective administrative systems supporting the plurality of web services, wherein the provisioning processes data is in Web Services Flow Language;
receiving a selection of a first web service;
invoking the respective provisioning processes data for the first web service;
and invoking the respective provisioning processes data for each provisioning web service that correlates to an administrative system supporting the first web service, wherein the provisioning processes data comprises a plurality of nodes, wherein each node comprises web service invocation data correlated to invoking a respective provisioning web service.
providing web service description data, correlated to each web service of the plurality of web services, wherein the web service description data is in Web Services Definition Language;
providing respective provisioning processes data for each web service of the plurality of web services and for each of a plurality of provisioning web services that correlate to respective administrative systems supporting the plurality of web services, wherein the provisioning processes data is in Web Services Flow Language;
receiving a selection of a first web service;
invoking the respective provisioning processes data for the first web service;
and invoking the respective provisioning processes data for each provisioning web service that correlates to an administrative system supporting the first web service, wherein the provisioning processes data comprises a plurality of nodes, wherein each node comprises web service invocation data correlated to invoking a respective provisioning web service.
3. A computer program product comprising a computer readable medium having computer readable code means embodied thereon for carrying out the steps of provisioning a plurality of web services, the computer readable code means comprising:
a first code means for providing web service description data, correlated to each web service of the plurality of web services, wherein the web service description data is in Web Services Definition Language;
a second code means for providing respective provisioning processes data for each web service of the plurality of web services and for each of a plurality of provisioning web services that correlate to respective administrative systems supporting the plurality of web services, wherein the provisioning processes data is in Web Services Flow Language;
a third code means for receiving a selection of a first web service;
a fourth code means for invoking the respective provisioning processes data for the first web service; and a fifth code means for invoking the respective provisioning processes data for each provisioning web service that correlates to an administrative system supporting the first web service, wherein the provisioning processes data comprises a plurality of nodes, wherein each node comprises web service invocation data correlated to invoking a respective provisioning web service.
a first code means for providing web service description data, correlated to each web service of the plurality of web services, wherein the web service description data is in Web Services Definition Language;
a second code means for providing respective provisioning processes data for each web service of the plurality of web services and for each of a plurality of provisioning web services that correlate to respective administrative systems supporting the plurality of web services, wherein the provisioning processes data is in Web Services Flow Language;
a third code means for receiving a selection of a first web service;
a fourth code means for invoking the respective provisioning processes data for the first web service; and a fifth code means for invoking the respective provisioning processes data for each provisioning web service that correlates to an administrative system supporting the first web service, wherein the provisioning processes data comprises a plurality of nodes, wherein each node comprises web service invocation data correlated to invoking a respective provisioning web service.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002405673A CA2405673C (en) | 2002-09-30 | 2002-09-30 | Provisioning web services |
| US10/666,869 US7506021B2 (en) | 2002-09-30 | 2003-09-18 | Provisioning web services |
| US12/355,914 US20090182645A1 (en) | 2002-09-30 | 2009-01-19 | Provisioning Web Services |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002405673A CA2405673C (en) | 2002-09-30 | 2002-09-30 | Provisioning web services |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2405673A1 CA2405673A1 (en) | 2004-03-30 |
| CA2405673C true CA2405673C (en) | 2009-10-06 |
Family
ID=32034682
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002405673A Expired - Lifetime CA2405673C (en) | 2002-09-30 | 2002-09-30 | Provisioning web services |
Country Status (2)
| Country | Link |
|---|---|
| US (2) | US7506021B2 (en) |
| CA (1) | CA2405673C (en) |
Families Citing this family (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050125738A1 (en) * | 2003-12-04 | 2005-06-09 | Biplav Srivastava | Composite network-accesible services |
| US8321535B2 (en) * | 2004-11-19 | 2012-11-27 | Oracle International Corporation | Web services integration systems and methods |
| US20060165040A1 (en) * | 2004-11-30 | 2006-07-27 | Rathod Yogesh C | System, method, computer program products, standards, SOA infrastructure, search algorithm and a business method thereof for AI enabled information communication and computation (ICC) framework (NetAlter) operated by NetAlter Operating System (NOS) in terms of NetAlter Service Browser (NSB) to device alternative to internet and enterprise & social communication framework engrossing universally distributed grid supercomputing and peer to peer framework |
| US8433822B2 (en) * | 2005-03-09 | 2013-04-30 | Research In Motion Limited | System, method and apparatus for optimized wireless messaging |
| US7685303B2 (en) * | 2006-02-21 | 2010-03-23 | Microsoft Corporation | Object-oriented discovery framework |
| US9830145B2 (en) | 2006-08-14 | 2017-11-28 | Federal Home Loan Mortgage Corporation (Freddie Mac) | Systems and methods for infrastructure and middleware provisioning |
| US8055586B1 (en) | 2006-12-29 | 2011-11-08 | Amazon Technologies, Inc. | Providing configurable use by applications of sequences of invocable services |
| US7925554B1 (en) | 2006-12-29 | 2011-04-12 | Amazon Technologies, Inc. | Using configured application pricing to determine end user fees for use of invocable services |
| US10853780B1 (en) * | 2006-12-29 | 2020-12-01 | Amazon Technologies, Inc. | Providing configurable pricing for use of invocable services by applications |
| US20090089115A1 (en) * | 2007-10-01 | 2009-04-02 | Oracle International Corporation | Computer-implemented methods and systems for deriving process flow diagrams |
| US8713091B2 (en) * | 2008-10-03 | 2014-04-29 | Microsoft Corporation | Network based JIT on a priori knowledge of a set of disparate clients |
| US9705888B2 (en) | 2009-03-31 | 2017-07-11 | Amazon Technologies, Inc. | Managing security groups for data instances |
| US8713060B2 (en) | 2009-03-31 | 2014-04-29 | Amazon Technologies, Inc. | Control service for relational data management |
| US8060792B2 (en) | 2009-03-31 | 2011-11-15 | Amazon Technologies, Inc. | Monitoring and automated recovery of data instances |
| US8307003B1 (en) * | 2009-03-31 | 2012-11-06 | Amazon Technologies, Inc. | Self-service control environment |
| US9207984B2 (en) | 2009-03-31 | 2015-12-08 | Amazon Technologies, Inc. | Monitoring and automatic scaling of data volumes |
| US8332365B2 (en) | 2009-03-31 | 2012-12-11 | Amazon Technologies, Inc. | Cloning and recovery of data volumes |
| US8543590B2 (en) * | 2009-06-05 | 2013-09-24 | Tsx Inc. | Investor relations systems and methods |
| US9135283B2 (en) * | 2009-10-07 | 2015-09-15 | Amazon Technologies, Inc. | Self-service configuration for data environment |
| US8074107B2 (en) | 2009-10-26 | 2011-12-06 | Amazon Technologies, Inc. | Failover and recovery for replicated data instances |
| US8676753B2 (en) * | 2009-10-26 | 2014-03-18 | Amazon Technologies, Inc. | Monitoring of replicated data instances |
| US8335765B2 (en) * | 2009-10-26 | 2012-12-18 | Amazon Technologies, Inc. | Provisioning and managing replicated data instances |
| US8645459B2 (en) * | 2009-11-18 | 2014-02-04 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for a service provisioning platform for activating services in a communication network |
Family Cites Families (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH1063747A (en) * | 1996-08-20 | 1998-03-06 | Fuji Xerox Co Ltd | Work flow supporting system, and method therefor |
| US5930777A (en) * | 1997-04-15 | 1999-07-27 | Barber; Timothy P. | Method of charging for pay-per-access information over a network |
| US6023464A (en) | 1997-12-23 | 2000-02-08 | Mediaone Group, Inc. | Auto-provisioning of user equipment |
| US6349238B1 (en) * | 1998-09-16 | 2002-02-19 | Mci Worldcom, Inc. | System and method for managing the workflow for processing service orders among a variety of organizations within a telecommunications company |
| US6453162B1 (en) | 1998-12-10 | 2002-09-17 | Nortel Networks Limited | Method and system for subscriber provisioning of wireless services |
| US6647260B2 (en) | 1999-04-09 | 2003-11-11 | Openwave Systems Inc. | Method and system facilitating web based provisioning of two-way mobile communications devices |
| US6633907B1 (en) * | 1999-09-10 | 2003-10-14 | Microsoft Corporation | Methods and systems for provisioning online services |
| AU2001255306A1 (en) | 2000-04-14 | 2001-10-30 | Gensym Corporation | Intelligent transaction mining system |
| US7496637B2 (en) * | 2000-05-31 | 2009-02-24 | Oracle International Corp. | Web service syndication system |
| EP1402352A4 (en) * | 2001-02-22 | 2010-08-25 | Accenture Global Services Gmbh | Distributed development environment for building internet applications by developers at remote locations |
| US20030004746A1 (en) * | 2001-04-24 | 2003-01-02 | Ali Kheirolomoom | Scenario based creation and device agnostic deployment of discrete and networked business services using process-centric assembly and visual configuration of web service components |
| US20030036917A1 (en) * | 2001-04-25 | 2003-02-20 | Metallect Corporation | Service provision system and method |
| US20020194045A1 (en) * | 2001-05-01 | 2002-12-19 | Izhar Shay | System and method for automatically allocating and de-allocating resources and services |
| US7065740B2 (en) * | 2001-08-24 | 2006-06-20 | Microsoft Corporation | System and method to automate the management of computer services and programmable devices |
| US7343428B2 (en) * | 2001-09-19 | 2008-03-11 | International Business Machines Corporation | Dynamic, real-time integration of software resources through services of a content framework |
| US7035944B2 (en) * | 2001-09-19 | 2006-04-25 | International Business Machines Corporation | Programmatic management of software resources in a content framework environment |
| CA2404552C (en) * | 2001-09-21 | 2008-12-09 | Corel Corporation | System and method for secure communication |
| US7506059B2 (en) * | 2001-10-26 | 2009-03-17 | Nokia Corporation | Mobile client provisioning web service |
| US7254614B2 (en) * | 2001-11-20 | 2007-08-07 | Nokia Corporation | Web services push gateway |
| US8126722B2 (en) * | 2001-12-20 | 2012-02-28 | Verizon Business Global Llc | Application infrastructure platform (AIP) |
| US7603469B2 (en) * | 2002-01-15 | 2009-10-13 | International Business Machines Corporation | Provisioning aggregated services in a distributed computing environment |
| US20030163513A1 (en) * | 2002-02-22 | 2003-08-28 | International Business Machines Corporation | Providing role-based views from business web portals |
| US7787825B2 (en) * | 2002-05-08 | 2010-08-31 | Alcatel-Lucent Usa Inc. | Data based over the air provisioning for wireless services |
| US7729922B2 (en) * | 2002-08-15 | 2010-06-01 | Open Invention Network, Llc | Dynamic interface between BPSS conversation management and local business management |
-
2002
- 2002-09-30 CA CA002405673A patent/CA2405673C/en not_active Expired - Lifetime
-
2003
- 2003-09-18 US US10/666,869 patent/US7506021B2/en not_active Expired - Fee Related
-
2009
- 2009-01-19 US US12/355,914 patent/US20090182645A1/en not_active Abandoned
Also Published As
| Publication number | Publication date |
|---|---|
| US20040068565A1 (en) | 2004-04-08 |
| US20090182645A1 (en) | 2009-07-16 |
| CA2405673A1 (en) | 2004-03-30 |
| US7506021B2 (en) | 2009-03-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2405673C (en) | Provisioning web services | |
| US11157915B2 (en) | Automatic creation and configuration of license models and policies | |
| US8037193B2 (en) | Virtual token | |
| US7516103B1 (en) | Method and apparatus for facilitating electronic acquisition and maintenance of goods and services via the internet | |
| EP1388084B1 (en) | Counting and billing mechanism for web-services based on a soap-communication protocol | |
| US7912764B1 (en) | Generating new composite network services based on user selection of other constituent network services | |
| JP4069114B2 (en) | Dynamic late combining of third-party on-demand services on an on-demand basis | |
| US7236947B2 (en) | Providing highly automated procurement services | |
| US20070233577A1 (en) | Lead distribution method and system | |
| US20020035479A1 (en) | Access contract changing method for automatically changing an access contract between a prepaid contract and a postpaid contract | |
| US8577733B2 (en) | Method and system for dynamic order fulfillment | |
| WO1999052042A2 (en) | Telecommunication transmission system adapted to provide a platform for agent oriented electronic market place services | |
| KR100414200B1 (en) | Apparatus and control method for trade type engine in electronic trading system | |
| US8396782B2 (en) | Client-oriented, on-demand trading system | |
| JP2002312311A (en) | Service cooperation system | |
| JP7108246B1 (en) | Apparatus, method and program for setting business negotiations | |
| Marchione et al. | Price definition in the establishment of electronic contracts for web services | |
| EP1076864A2 (en) | Telecommunication transmission system adapted for an electronic market place | |
| US20080010164A1 (en) | Method and system for the network-based offering of goods, services and/or other items of value | |
| Succi et al. | Supporting electronic commerce of software products through pay-per-use rental of downloadable tools | |
| WO2019008160A1 (en) | Methods and systems for referrer-based payment system selection for internet-based merchants | |
| AU2329301A (en) | A virtual token | |
| KR20000049924A (en) | The method not required CGI for making shopping mall on internet and constructing electronic commerce system | |
| WO2009055471A1 (en) | Business to media transaction business process |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry |
Effective date: 20221003 |
|
| MKEX | Expiry |
Effective date: 20221003 |