# US 8,782,769 B2 · System and method for providing a rest-based management service in a traffic director environment > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,782,769 B2 - Document ID: US8782769B2 - Status: Granted - Kind: B2 - Application number: 13/627,646 - Filed: 2012-09-26 - Published: 2013-03-28 - Granted: 2014-07-15 - Earliest claimed: 2011-09-27 - Assignees: Oracle International Corporation - Applicants: Oracle International Corporation - Inventors: Amit Gupta; Praveen Chandrasekharan - Web page: https://patentgrep.com/patent/US8782769B2 ## CPC - G06F 9/505: {considering the load} - G06F 9/451: Execution arrangements for user interfaces - G06F 9/45512: {Command shells} - G06F 11/2041: {with more than one idle spare processing component} - G06F 40/274: Converting codes to words; Guess-ahead of partial word inputs - H04L 41/08: Configuration management of networks or network elements (address allocation H04L61/50) - H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)} - H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30) - G06F 11/3433: {for load management (allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029)} - G06F 2201/86: Event-based monitoring - H04L 67/1001: for accessing one among a plurality of replicated servers - H04L 67/10015: {Access to distributed or replicated servers, e.g. using brokers} - H04L 67/1034: Reaction to server failures by a load balancer - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Described herein are systems and methods for providing software administration tools, for use in administering server configurations, such as in a traffic director or other type of server environment. In accordance with an embodiment, the system comprises a traffic director having one or more traffic director instances, which is configured to receive and communicate requests, from clients, to origin servers having one or more pools of servers. An administration server can be used to manage the traffic director, including a REpresentational State Transfer (REST) infrastructure and management service which maps REST calls to mbeans or other management components registered on the administration server, for use in managing the traffic director. ## Claims ### Claim 1 A system for use in a computing environment which includes a traffic director component, comprising: one or more computer servers, operating as a traffic director environment, and having one or more server instances, wherein the server instances are managed using one or more mbeans or other management software components; an administration server, which is used to manage the traffic director environment, wherein the administration server includes a configuration store having a collection of configurable elements that determine a run-time behavior of the server instances; and a REpresentational State Transfer (REST) infrastructure and management service provided at the administration server, which maps REST calls received from administration consoles or other user interfaces to the mbeans or other management software components registered on the administration server, for use in managing the traffic director environment, including maintaining a mapping between a REST space and calls to the mbeans or other management software components, receiving a management request as a REST call, and verifying presence of a security token in the REST call, prior to passing the management request to the traffic director environment as a call to the mbeans or other management software components; wherein the REST infrastructure includes a security component which requires entities communicating a management request to first login or otherwise authenticate themselves with the security component, wherein in response to authenticating with the security component, the entity receives the security token, which must be included as part of the request header for subsequent management requests. ### Claim 2 (depends on 1) The system of claim 1, wherein the REST infrastructure and management service includes a web service which provides the mapping between a REST URI space and respective mbean calls. ### Claim 3 (depends on 1) The system of claim 1, wherein the administration server uses customized request headers and tokens to assert the authenticity of clients invoking management operations. ### Claim 4 (depends on 1) The system of claim 1, wherein the server instances are traffic director instances. ### Claim 5 A method for use in a computing environment which includes a traffic director component, comprising the steps of: operating, at one or more computer servers, a traffic director environment, having one or more server instances, wherein the server instances are managed using one or more mbeans or other management software components; providing an administration server, which is used to manage the traffic director environment, wherein the administration server includes a configuration store having a collection of configurable elements that determine a run-time behavior of the server instances; and providing a REpresentational State Transfer (REST) infrastructure and management service provided at the administration server, which maps REST calls received from administration consoles or other user interfaces to the mbeans or other management software components registered on the administration server, for use in managing the traffic director environment, including maintaining a mapping between a REST space and calls to the mbeans or other management software components, receiving a management request as a REST call, and verifying presence of a security token in the REST call, prior to passing the management request to the traffic director environment as a call to the mbeans or other management software components; wherein the REST infrastructure includes a security component which requires entities communicating a management request to first login or otherwise authenticate themselves with the security component, wherein in response to authenticating with the security component, the entity receives the security token, which must be included as part of the request header for subsequent management requests. ### Claim 6 (depends on 5) The method of claim 5, wherein the REST infrastructure and management service includes a web service which provides the mapping between a REST URI space and respective mbean calls. ### Claim 7 (depends on 5) The method of claim 5, wherein the administration server uses customized request headers and tokens to assert the authenticity of clients invoking management operations. ### Claim 8 (depends on 5) The method of claim 5, wherein the server instances are traffic director instances. ### Claim 9 A non-transitory computer readable medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising: operating, at one or more computer servers, a traffic director environment, having one or more server instances, wherein the server instances are managed using one or more mbeans or other management software components; providing an administration server, which is used to manage the traffic director environment, wherein the administration server includes a configuration store having a collection of configurable elements that determine a run-time behavior of the server instances; and providing a REpresentational State Transfer (REST) infrastructure and management service provided at the administration server, which maps REST calls received from administration consoles or other user interfaces to the mbeans or other management software components registered on the administration server, for use in managing the traffic director environment, including maintaining a mapping between a REST space and calls to the mbeans or other management software components, receiving a management request as a REST call, and verifying presence of a security token in the REST call, prior to passing the management request to the traffic director environment as a call to the mbeans or other management software components; wherein the REST infrastructure includes a security component which requires entities communicating a management request to first login or otherwise authenticate themselves with the security component, wherein in response to authenticating with the security component, the entity receives the security token, which must be included as part of the request header for subsequent management requests. ### Claim 10 (depends on 9) The non-transitory computer readable medium of claim 9, wherein the REST infrastructure and management service includes a web service which provides the mapping between a REST URI space and respective mbean calls. ### Claim 11 (depends on 9) The non-transitory computer readable medium of claim 9, wherein the administration server uses customized request headers and tokens to assert the authenticity of clients invoking management operations. ### Claim 12 (depends on 9) The non-transitory computer readable medium of claim 9, wherein the server instances are traffic director instances.