Configuration
The Configuration tab has the following fields.
Field |
Global Var? |
Description |
Name |
No |
The name to appear as the label for the activity in the process definition. |
Description |
No |
Short description of the activity. |
HTTP Connection |
No |
The HTTP Connection resource describes the characteristics of the connection used to receive incoming HTTP requests. For more information about specifying shared resources, see HTTP Connection. |
Output Style |
No |
Type of output. Can be either String or Binary. |
Parse Post Method Data |
No |
Specifies to parse the message body of the HTTP request into a schema for the activity’s output. When this check box is selected, the parameters specified in the Parameters field are used to validate the incoming request and parse it into the output schema. Note: In the case of an incoming GET request, there is no message body, so this field has no effect on incoming GET requests.
|
Parameters |
No |
The parameters of the incoming HTTP request. Specifying parameters in this table allows the incoming request to be parsed and represented as a schema in this activity’s output. For each parameter, you must provide a name, datatype, and whether the field is required, optional, or repeating. Use the + and x buttons to the right of the parameter table to add and remove parameters. Use the up and down arrows to move parameters to new positions in the table. Note: Specifying parameters in this field parses the query string of the request into the output schema, regardless of whether the Parse Post Method Data field is checked. Checking the Parse Post Method Data field and specifying parameters here is required to parse the message body along with the query string of the request.
|
HTTP Authentication |
No |
Specifies that the client sending the HTTP request must be authenticated. The user name and password specified in the incoming request must exist in the domain. Users are created and managed in the domain using TIBCO Administrator. |
Expose Security Context |
No |
Places the information from the user’s security context (either authentication or SSL certificate information) into the Context/SecurityContext output element. This is a fairly expensive operation and SSL certificates can consume memory resources, so check this option only if you require information from the user’s security context for later use in your process definition. |
Default Encoding |
Yes |
Specifies the encoding to use if no charset is specified in the Content-Type header of the message. This encoding is used for the message body and URL. However, when URIEncoding is specified in the HTTP Connection shared resource, the Default Encoding parameter specified here applies to the contentType alone and not to the URIEncoding property. |
Upgrade Configuration |
No |
This field is available only when projects created in ActiveMatrix BusinessWorks 5.2.x or earlier versions are migrated to a higher version. Selecting the check box upgrades the schema in the input/output tab for the activity. You can revert back to the old schema by clearing the check box. However, if you create new processes in the older projects, the activities always show the new schema in their input/output tabs. In this case, it is not possible to revert to the old schema. |