Page History

...

For more information on inbound HTTP processing in LANSA Composer, refer to:

HTTP Inbound (Server) Processing in LANSA Composer

To understand how your Processing Sequence containing the HTTP_SIMPLE_INBOUND activity is connected with an inbound HTTP request, refer to:

Connect Your Processing Sequence to an Inbound HTTP Request

This activity is nominally an iterator activity, although it is unusual insofar as it iterates only once.  It is defined as an iterator activity in order to allow any processing sequence directives nested beneath it to process the received content and prepare the response payload, if any.  You can nest transformation maps, other activities or whatever directives you need to perform this.  The activity's input parameters (RESPONSEFILEPATH and RESPONSECONTENTTYPE) that specify the response payload are not evaluated until the iteration completes - so your nested processing sequence directives can set their values.

...

For example, a Comma Separated file will have a value of  *TEXT *SV *CSV

Refer to the HTTP Configuration for a full list of types.

...