Jump to content


Photo

API Call of Server returns Object not found

Empty Rsponse Not found API

Best Answer Aravindan Anandan, 10 March 2020 - 11:50 PM

The configuration hierarchy for the services is as follows:

<Service>
   <Server1>
      attributes
   </Server1>
   <Server2>
      attributes
   </Server2>
   <RuleGroup1>
      attributes
      <Rule Group Server>
         attributes
      </Rule Group Server>
   </Rule Group1>
</Service>
 

From the error message that you mentioned, it looks like the server you are querying is under a rule group. So you may need to change your request URL to include the rule group name.

Use the following url space format to query the server.

 

URL space: /services/{Service Name}/content-rules/{Rule Group Name}/content-rule-servers/{Server Name}

Go to the full post


This topic has been archived. This means that you cannot reply to this topic.
2 replies to this topic

#1 Philipp Kropik

Philipp Kropik
  • Members
  • 7 posts

Posted 10 March 2020 - 06:54 AM

Hi, 
 
I'm trying to get started using the API calls, and no I've run into the following Problem when Calling the Server directly to get the properties of the server, I'm hit with the response: 
"Object 'Dummyname' does not exist on this system.", in addition to the Auth Token used. 
I'm sending a Get-Request to https://Waf-Path/restapi/v3.1/services/WebApp/servers/Dummyname
 
When Checking the call just for the Webapp the Server I am trying to query shows up under "Rule Group Server: data:".
 
Am I missing something or, does the fact that the server is used for more than one Rules Group with different SNI Settings confuse the API? 
 
The target of the exploration is to add the API calls to our Jenkins scripts so we can, disable a Server, update the app and reenable it without having to do these jobs manually. 
 
Any help would be appreciated. 
 
Philipp 
 


#2 Aravindan Anandan

Aravindan Anandan
  • Barracuda Team Members
  • 87 posts

Posted 10 March 2020 - 11:50 PM   Best Answer

The configuration hierarchy for the services is as follows:

<Service>
   <Server1>
      attributes
   </Server1>
   <Server2>
      attributes
   </Server2>
   <RuleGroup1>
      attributes
      <Rule Group Server>
         attributes
      </Rule Group Server>
   </Rule Group1>
</Service>
 

From the error message that you mentioned, it looks like the server you are querying is under a rule group. So you may need to change your request URL to include the rule group name.

Use the following url space format to query the server.

 

URL space: /services/{Service Name}/content-rules/{Rule Group Name}/content-rule-servers/{Server Name}



#3 Philipp Kropik

Philipp Kropik
  • Members
  • 7 posts

Posted 07 April 2020 - 05:30 AM

Thank you!

That solved the Problem.