URI

<services_uri>/rooturls/harvest[.<format>]

Supported Methods

GET, HEAD

Parent Resource

services

Introduction

Harvest batch registered services.

Supported Methods:

• GET: Trigger harvesting batch registered services.
• HEAD: Check whether the harvestBatchRegisterServices resource exists, or whether the permission can access the harvestBatchRegisterServices resource.

Supported output formats: RJSON, JSON, HTML, XML.

Resource hierarchy

HTTP Request Method

Perform an HTTP request on the following URI. The rjson output format is used as an example, where supermapiportal is the server name.

http://supermapiportal:8190/iportal/web/services/rooturls/harvest.rjson

GET Request

Trigger harvesting batch registered services.

Response Structure

Perform a GET request on the harvestBatchRegisterServices resource. The returned resource representation structure is as follows:

Response Example

Perform a GET request on the harvestBatchRegisterServices resource: http://localhost:8190/iportal/web/services/rooturls/harvest.rjson to trigger harvesting batch registered services. The returned rjson representation is as follows:

{"succeed": true}

HEAD Request

Returns the same HTTP response headers as a GET request, but without a response entity. You can obtain the metadata information contained in the response message headers without transferring the entire response content. The metadata information includes media type, character encoding, compression encoding, entity content length, etc.

A HEAD request can be used to determine whether the harvestBatchRegisterServices resource exists, or whether the client has permission to access the harvestBatchRegisterServices resource. By performing a HEAD request on a URI with .<format> appended, you can also quickly determine whether the harvestBatchRegisterServices resource supports the <format> representation.

See

• services
• Constructing REST Requests
• Status Codes
• Output Formats
• Resource hierarchy