To be able to POST basic requests to an ingest/storage service and return the response back to the caller, a new plugin is introduced. The plugin takes the request message from a specific configured field in a specific record from a specific configured database and will POST the raw contents to the URL configured for the plugin and relays the response back to the caller. In version 3.5.1.2226 of the WebAPI this proxy handler option has been added. The configuration in adlibweb.xml is like this:
<proxyServerConfiguration name="myproxy"> <ProxyPlugin type="Adlib.InternetService2.Proxy.GenericProxy"> <database>deliverables</database> <field>py</field> <url>https://the.storage.service/ingest/initiate</url> <token>some access token</token> <mimetype>application/json</mimetype> </ProxyPlugin> </proxyServerConfiguration>
and can be called with a string formatted like:
...wwwopac.ashx?proxy=<proxy server definition>&value=<record priref>
The required settings in the configuration are:
application/json
or text/xml
)The proxy doesn’t need a command parameter. The result of the URL call is returned to the caller of the API. The configured mime-type is used for both the POST to the external URL and the content type of the API response.