Webtier as a service
A method for automated web resource deployment is provided. The method comprises creating web resource publication requests, wherein each web resource publication request comprises a number of configuration changes necessary to publish a web resource, on a network, at a particular uniform resource location. A standard format, validation workflow, and an approval workflow are provided for automation of the web resource publication requests. Once validated and approved, web resource publication requests are automatically converted to API calls which are executed on backend servers to implement the configuration changes required in the environment without further human intervention.
1. A computer-implemented method, comprising:
receiving, by one or more processors, a web resource publication request from a client, the web resource publication request having a format;
validating, by the one or more processors, the format of the web resource publication request;
approving, by the one or more processors, implementation of the web resource publication request;
converting, by the one or more processors, the web resource publication request to a number of application programming interface (API) calls;
receiving, by the one or more processors responsive to transmission of the number of API calls, a number of API call responses, the number of API call responses including a status of implementing a number of configuration changes;
determining, by the one or more processors using the number of API call responses, a request status of the web resource publication request; and
sending, by the one or more processors, the request status of the web resource publication request to the client.
2. The method of claim 1 , wherein the number of API call responses include one of a first format responsive to a backend server successfully implementing the number of configuration changes and a second format responsive to the backend server unsuccessfully implementing the number of configuration changes.
3. The method of claim 1 , further comprising:
generating, responsive to determining implementation of the number of configuration changes, information pertaining to the number of configuration changes;
storing, in a database, the information pertaining to the number of configuration changes; and
updating, responsive to receiving a second number of API call responses, the information pertaining to the number of configuration changes to reflect a second number of configuration changes.
4. The method of claim 1 , wherein a web resource acted on by the web resource publication request comprises one of:
a uniform resource locator (URL);
a uniform resource identifier (URI);
a service; and
a subscription.
5. The method of claim 1 , wherein an action requested by the web resource publication request comprises one of:
creating;
modifying;
viewing;
workflow approval; and
deleting.
6. The method of claim 1 , wherein the number of API calls comprise one of:
web service API;
Firewall API;
certificate API;
VIP API; and
DNS API.
7. The method of claim 1 , wherein the client comprises one of:
a user logged into a user interface; and
a programmatic API call.
8. The method of claim 1 , wherein the format of the web resource publication request comprises one of:
a URL name;
a service name;
a LDAP name;
a server identifier;
a VIP identifier; and
a port number.
9. The method of claim 1 , wherein the number of configuration changes are executed on a Virtual IP Address (VIP) server via a VIP API call to the VIP server.
10. The method of claim 1 , wherein the number of configuration changes are executed on a certificate store via a certificate API call to the certificate store.
11. A system comprising one or more memory devices storing instructions that, when executed by one or more processors, cause the one or more processors to:
receive a web resource publication request from a client, the web resource publication request having a format;
validate the format of the web resource publication request;
approve implementation of the web resource publication request;
convert the web resource publication request to a number of application programming interface (API) calls;
receive, responsive to transmission of the number of API calls, a number of API call responses, the number of API call responses including a status of implementing a number of configuration changes;
determine, using the number of API call responses, a request status of the web resource publication request; and
send the request status of the web resource publication request to the client.
12. The system of claim 11 , wherein the number of API call responses include one of a first format responsive to a backend server successfully implementing the number of configuration changes and a second format responsive to the backend server unsuccessfully implementing the number of configuration changes.
13. The system of claim 11 , wherein the instructions cause the one or more processors to:
generate, responsive to determining implementation of the number of configuration changes, information pertaining to the number of configuration changes;
store, in a database, the information pertaining to the number of configuration changes; and
update, responsive to receiving a second number of API call responses, the information pertaining to the number of configuration changes to reflect a second number of configuration changes.
14. The system of claim 11 , wherein a web resource acted on by the web resource publication request comprises one of:
a uniform resource locator (URL);
a uniform resource identifier (URI);
a service; and
a subscription.
15. The system of claim 11 , wherein an action requested by the web resource publication request comprises one of:
creating;
modifying;
viewing;
workflow approval; and
deleting.
16. The system of claim 11 , wherein the number of API calls comprise one of:
web service API;
Firewall API;
certificate API;
VIP API; and
DNS API.
17. A non-transitory computer readable storage media having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to implement operations comprising:
receiving a web resource publication request from a client, the web resource publication request having a format;
validating the format of the web resource publication request;
approving implementation of the web resource publication request;
converting the web resource publication request to a number of application programming interface (API) calls;
receiving, responsive to transmission of the number of API calls, a number of API call responses, the number of API call responses including a status of implementing a number of configuration changes;
determining, using the number of API call responses, a request status of the web resource publication request; and
sending the request status of the web resource publication request to the client.
18. The non-transitory computer readable storage media of claim 17 , wherein the number of API call responses include one of a first format responsive to a backend server successfully implementing the number of configuration changes and a second format responsive to the backend server unsuccessfully implementing the number of configuration changes.
19. The non-transitory computer readable storage media of claim 17 , the operations further comprising:
generating, responsive to determining implementation of the number of configuration changes, information pertaining to the number of configuration changes;
storing, in a database, the information pertaining to the number of configuration changes; and
updating, responsive to receiving a second number of API call responses, the information pertaining to the number of configuration changes to reflect a second number of configuration changes.
20. The non-transitory computer readable storage media of claim 17 , wherein a web resource acted on by the web resource publication request comprises one of:
a uniform resource locator (URL);
a uniform resource identifier (URI);
a service; and
a subscription.