If you post parameters to the listener, each parameter is added to the AspireObject. There's also a head that holds the request parameters. If you browse to http://localhost:50505/process?param1=value1¶m2=value2 you'll get an AspireObject that looks like this:
<doc> <aspireHttpFeederServlet remotePort="52124" relativePath="/xml-search" serverName="localhost" source="HTTPFeederServlet" remoteHost="127.0.0.1" serverPort="50505" remoteAddr="127.0.0.1" fullPath="/cgi-bin/xml-search" servletPath="/cgi-bin"> <queryString>param1=value1¶m2=value2</queryString> </aspireHttpFeederServlet> <feederLabel>HttpFeeder</feederLabel> <param1 source="HTTPFeederServlet">value1</param1> <param2 source="HTTPFeederServlet">value2</param2> </doc>
When data is streamed to the listener via POST will be set as an input stream attached to the job. You can access the data using the Standards.Basic.getContentStream(Job j) method in the package com.accenture.aspire.framework from a custom rule in the workflow. This also means that you can follow the listener with any application that expect a stream (such as Extract Text) or a custom application that uses the content stream. The following components can be used to process the stream XML Sub Job Extractor, Tabular Files Extractor, XML File Loader, and Extract Text.
No available troubleshooting at this moment