Dynamic registration of an application with an enterprise system
US-9723058-B2 · Aug 1, 2017 · US
US2018295211A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2018295211-A1 |
| Application number | US-201715481396-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 6, 2017 |
| Priority date | Apr 6, 2017 |
| Publication date | Oct 11, 2018 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system and method for self-deploying applications for a contact center. An executable unit is built for deploying an application for the contact center, and the application and logic for provisioning the application are aggregated into the executable unit. The executable unit is then provided for deployment. When the executable unit is run, logic within the executable unit is configured to automatically register the application on the computing environment, discover and resolve services used by the application, and start the application on the computing environment.
Opening claim text (preview).
1 . A system for self-deploying applications for a contact center, the system comprising: a processor; and a memory, wherein the memory stores instructions that, when executed by the processor, cause the processor to: receive instructions to build an executable unit for deploying an application for the contact center; in response to the instructions, aggregate into the executable unit, the application and logic for provisioning the application; and provide the executable unit for self-deploying the application on a computing environment associated with the contact center, wherein the logic is configured to perform actions for self-deploying the application in response to the executable unit being run. 2 . The system of claim 1 , wherein the actions include automatically registering the application on the computing environment. 3 . The system of claim 2 , wherein the automatically registering the application includes assigning a network name and a network address to the application without access to an external directory service. 4 . The system of claim 3 , wherein, the automatically registering the application includes resolving naming and address conflicts without access to the external directory service. 5 . The system of claim 1 , wherein the actions include monitoring a state of the application and publishing the state to other applications on the computing environment. 6 . The system of claim 1 , wherein the executable unit includes data on external services depended upon by the application, and the actions include resolving the external services. 7 . The system of claim 6 , wherein the resolving of the external services includes locating the external services on the computing environment. 8 . The system of claim 6 , wherein the resolving of the external services includes comparing data of a responding external service against service conditions, and determining a match of the data against the service conditions. 9 . The system of claim 7 , wherein the resolving of external services includes blocking provisioning of the application in response to the external services not being resolved. 10 . The system of claim 1 , wherein the instructions that cause the processor to aggregate the application and the logic include instructions that cause the processor to generate a container for the application and the logic via container technology. 11 . A method for self-deploying applications for a contact center, the method comprising: receiving, by a processor, instructions to build an executable unit for deploying an application for the contact center; in response to the instructions, aggregating, by the processor, into the executable unit, the application and logic for provisioning the application; and providing, by the processor, the executable unit for self-deploying the application on a computing environment associated with the contact center, wherein the logic is configured to perform actions for self-deploying the application in response to the executable unit being run. 12 . The method of claim 11 , wherein the actions include registering the application on the computing environment. 13 . The method of claim 12 , wherein the automatically registering the application includes assigning a network name and a network address to the application without access to an external directory service. 14 . The method of claim 12 , wherein the automatically registering includes resolving naming and address conflicts without access to the external directory service. 15 . The method of claim 11 , wherein the actions include monitoring a state of the application and publishing the state to other, applications on the computing environment. 16 . The method of claim 11 , wherein the executable unit includes data on external services depended upon by the application, and the actions include resolving the external services. 17 . The method of claim 16 , wherein the resolving of the external services includes locating the external services on the computing environment. 18 . The method of claim 15 , wherein the resolving of the external services includes comparing data of a responding external service against service conditions, and determining a match of the data against the service conditions. 19 . The method of claim 17 , wherein the resolving of external services includes blocking provisioning of the application in response to the external services not being resolved. 20 . The method of claim 11 , wherein the aggregating of the application and the logic include generating a container for the application and the logic via container technology.
Mechanisms for avoiding name conflicts · CPC title
involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function · CPC title
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
Electricity · mapped topic
Electricity · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.