Hey everybody,
My name is Yonni Mendes. I’m the Technological Lead for the Zend Server UI and WebAPI. I’ve been with Zend Server 6 since it was a spark in a product manager’s eye. I’m happy to have seen Zend Server 6 go through planning, design, development and deployment.
This is the first in a series of posts about the Zend Server WebAPI. In this series we will go over the WebAPI’s capabilities and what you can expect from process automation in Zend Server. Before we dig into the obscure corners of the Zend Server WebAPI, I should probably tell you a little about this system in general.
Welcome to the Zend Server WebAPI
The Zend Server WebAPI is reflected in everything our UI does. Practically anything you see in the UI can be done, at least to some degree, through the Zend Server WebAPI. Few are the cases where the UI resorts to bypassing the WebAPI and uses a privileged action to achieve some display goal.
The Zend Server WebAPI is accessible in a few ways but all of them rely on the same basic method – an HTTP request to a Zend Server WebAPI action. This central gateway goes through a uniform authentication process. The server then initiates the desired WebAPI action which will be executed like any other ZF2 controller/action request. This request then renders an output – in JSON or XML, which is sent to client to be consumed.
Words to actions
We can see this process with the following script.
Note that this is a sytnax synopsis for a ZF2 http client.
$client = new ZendHttpClient();
$client->setUri('http://:10081/ZendServer/Api/ ')
->setEncType(ZendHttpClient::ENC_FORMDATA)
->setMethod('Zend Server WebAPI spotlight: WebAPI 101
Posted in Uncategorized.
– December 16, 2013
0 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.