System and method for configuration and interchanging of business functionality implementations

Abstract

A system and method are presented for invoking integration actions in a unified collaboration system. A client communicates with a bridging web server through a ReST. The bridging web server comprises a cloud service which facilitates communication with integration servers, which may be located on-premises. In an embodiment, the integration server(s) host a number of plugins which are capable of implementing integration actions. The bridging web server decides which action implementation is the best one to service a request. The implementation may be based on prior configuration. Routing decisions on the bridging web server may be automatically selected based on prior configuration.

1 . A method for invoking integration actions in a unified collaboration system, wherein the system comprises at least a client operatively connected to a web server, wherein the web server is operatively connected to an integration server, the method comprising the steps of:
 a. establishing communication, by the client, with the web server, wherein the web server comprises a routing decision mechanism;   b. communicating, by the web server, with the integration server, wherein the integration server comprises a plurality of plugins capable of implementing the integration actions; and   c. deciding, by the web server, which integration action to perform wherein the deciding is based at least in part on prior configuration of the web server.   
     
     
         2 . The method of  claim 1 , wherein the communication of step (a) is established via ReST. 
     
     
         3 . The method of  claim 1 , wherein the web server comprises a cloud service which is capable of facilitating communication with the integration server. 
     
     
         4 . The method of  claim 1 , wherein the integration server is capable of integration of the client with one or more third party applications. 
     
     
         5 . The method of  claim 1 , wherein the client comprises one of: a unified collaboration service or a UI component, wherein the UI component requires a business function. 
     
     
         6 . The method of  claim 5 , wherein the client is capable of communication via HTTP and handling JSON bodies. 
     
     
         7 . The method of  claim 1 , wherein the integration server is located on-premises. 
     
     
         8 . The method of  claim 7 , wherein the integration server is capable of communicating via a WebSocket protocol. 
     
     
         9 . The method of  claim 1 , wherein the plugins define one or more integration action implementations. 
     
     
         10 . The method of  claim 1 , wherein the prior configuration comprises a manual configuration or an automatic configuration. 
     
     
         11 . The method of  claim 1 , wherein the integration action configuration is capable of alteration at any time in the process without disruption of the system. 
     
     
         12 . The method of  claim 1 , further comprising the step of:
 d. connecting, by the integration server, the unified collaboration system with a third party application.   
     
     
         13 . The method of  claim 12 , wherein the third party application comprises one or more of: a customer relationship management system, a database, and a workforce management system. 
     
     
         14 . The method of  claim 1 , wherein the integration actions have been manually configured to include one or more of: defined inputs to the integration action; defined outputs that the integration action provides; an identifier wherein the identifier is used by the client to specify which business function to perform; and a plugin grouping. 
     
     
         15 . The method of  claim 14 , wherein the defined inputs comprise property names and constraints on the property values and the defined outputs comprise property names and constraints on the property values. 
     
     
         16 . The method of  claim 14 , wherein the plugin grouping comprises a cluster of plugin instances that are available to fulfill a request of the integration action. 
     
     
         17 . A method for invoking integration actions in a unified collaboration system, wherein the system comprises at least a client operatively connected to a web server, wherein the web server is operatively connected to an integration server, the method comprising the steps of:
 a. establishing communication, by the client, with the web server, wherein the web server comprises a routing decision mechanism;   b. communicating, by the web server, with the integration server, wherein the integration server comprises a plurality of plugins capable of implementing the integration actions; and   c. deciding, by the web server, which integration action to perform wherein the deciding is based at least in part on a failsafe mechanism.   
     
     
         18 . The method of  claim 17 , wherein the communication of step (a) is established via ReST. 
     
     
         19 . The method of  claim 17 , wherein the web server comprises a cloud service which is capable of facilitating communication with the integration server. 
     
     
         20 . The method of  claim 17 , wherein the integration server is capable of integration of the client with one or more third party applications. 
     
     
         21 . The method of  claim 17 , wherein the client comprises one of: a unified collaboration service or a UI component, wherein the UI component a business function. 
     
     
         22 . The method of  claim 21 , wherein the client is capable of communication via HTTP and handling JSON bodies. 
     
     
         23 . The method of  claim 17 , wherein the integration server is located on-premises. 
     
     
         24 . The method of  claim 23 , wherein the integration server is capable of communicating via a WebSocket protocol. 
     
     
         25 . The method of  claim 17 , wherein the plugins define one or more integration action implementations. 
     
     
         26 . The method of  claim 17 , wherein the integration action configuration is capable of alteration at any time in the process without disruption of the system. 
     
     
         27 . The method of  claim 17 , further comprising the step of:
 d. connecting, by the integration server, the unified collaboration system with a third party application.   
     
     
         28 . The method of  claim 27 , wherein the third party application comprises one or more of: a customer relationship management system, a database, and a workforce management system. 
     
     
         29 . The method of  claim 17 , wherein the integration actions have been manually configured to include one or more of: defined inputs to the integration action; defined outputs that the integration action provides; an identifier wherein the identifier is used by the client to specify which business function to perform; and a plugin grouping. 
     
     
         30 . The method of  claim 29 , wherein the defined inputs comprise property names and constraints on the property values and the defined outputs comprise property names and constraints on the property values. 
     
     
         31 . The method of  claim 29 , wherein the plugin grouping comprises a cluster of plugin instances that are available to fulfill a request of the integration action. 
     
     
         32 . The method of  claim 17 , wherein the failsafe mechanism has been configured to utilize an alternative plugin if a desired plugin is unavailable.