Introduction
The MC2 ReST APIs can be accessed via API Gateway instead of via IIS (web server).
API Gateway is the standard access method in Eagle Access.
Read Timeout for API Gateway
The read timeout is the time-out applied from the moment you have established a connection
(So handshaking is done, and the connection can be used).
If no data comes from the server in this time-out time, the connection is terminated.
The API gateway uses a default read timeout value of 120000 in milliseconds.
This is equal to two minutes.
This should be reasonable amount of time for most REST apis, but if you have an api that is longer running,
the timeout value can be increased by a header passed into the api.
The header key is ioreadtimeout and the value should be in milliseconds, e.g. a value of 300000 would be 5 minutes.
Example:
curl
--location
--request GET 'https://clicktime.symantec.com/3NUzcQdPYLtkF2wuYyG4Jtd7Vc?u=https%3A%2F%2Fyour.api'
--header 'ioreadtimeout: 300000'
Please use reasonable timeout values when using this override as it does impact performance on the gateway.
The API Gateway can handle up to 36000000 (1 hour) as maximum override.
API Gateway – MC2 entitlements
The effective front end user name should be passed to MC2 with the http header x-eagle-user-id
MC2 ReST processing will include the user's Business Group in the request passed along to the extract,
unless the user is a super user. The Business Group will function as an entity filter during the execution
of the extract.
The one exception is the paceolap feedtype via the eql endpoint, which uses the front end user configured
in the EDS UI Vendor Configuration under the pace vendor id.
Manage space
Manage content
Integrations