Page History

...

For more information on the use of HTTP activities and configurations in LANSA Composer to perform inbound (server) HTTP processing, please refer to:

HTTP Inbound (Server) Processing in LANSA Composer

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

Connect Your Processing Sequence to an Inbound HTTP Request

Related HTTP activities

When the HTTP inbound processing is complete, you should close the session using the HTTP_END activity.

...

The supplied example Processing Sequence EXAMPLE_HTTPUPLOAD demonstrates the use of HTTP_BEGIN_INBOUND and other advanced HTTP activities to process an inbound HTTP request and send a response.  Refer to the notes accompanying the example Processing Sequence for details.

Refer to Example Processing Sequences for information on installing and using the example Processing Sequences.

...

This value will contain the Application Name value from the HTTP inbound configuration that was matched to this HTTP inbound request.  For more information, refer to the description of Application Name in HTTP Configuration Details.

HTTP_QUERY_STRING 

This value will contain the query string from the URI.

...

The activity will resolve the content type received in the HTTP header to a single special value that best fits the conten type received.  For example, it will be set to *MULTIPART for a multipart message, or it may be set to values such as *TEXT, *XML etc.  Refer to the HTTP Configuration Details for a full list of types.

...