ApplicationType
The ApplicationType directive specifies the type of application that will be supported and how the interfaces to JADE function.
You must define this directive before the TcpConnection[n] directive within each Application directive.
The application type characteristics are listed in the following table.
| Characteristic | Value |
|---|---|
| Action | Specifies the JADE application type |
| Syntax | ApplicationType application-type |
| Context | Location |
| Handler | jadehttp-handler |
| Module | mod_ jadehttp |
| Example | ApplicationType RestServices |
The valid application type values are listed in the following table.
| Value | Description |
|---|---|
| RestServices | Representational State Transfer (REST) lightweight Web service that embraces HyperText Transfer Protocol (HTTP) through Extensible Markup Language (XML) or JavaScript Object Notation (JSON) messages instead of SOAP. |
| WebEnabledForms | Web-enabled forms. This application type results in all requests from a user being directed to the same JADE application copy during the user’s session. JadeHttp no longer inserts the tags into the HTML output; the JADE software now performs this function. |
|
The JADE side uses the multi-worker TCP facility to perform routing and queuing. For the WebEnabledForms application type, you must specify the MinInUse, MaxInUse, CloseDelay, and ConnectionGroup values for the TcpConnection[n] directive. |
|
| WebServices |
Web service operation, where user requests are sent to any available connection. The JADE side uses the multi-worker TCP facility to perform routing and queuing. |
| HtmlDocuments |
HTML documents operation where user requests are sent to any available connection. The JADE side uses the multi-worker TCP facility to perform routing and queuing. |
