A directive is a way to access or invoke resources. Integration Server supports these directives:

Users specify directives as follows:

For example:

By default, all Integration Server ports except the proxy port allow all the directives listed above. The proxy port allows all directives except the web directive. However, for security reasons, an organization typically allows only those directives that are necessary to fulfill its business requirements. You might allow all directives on ports that are accessible only to users within your firewall, but you might want to restrict directives on ports that are exposed to users outside the firewall. For example, if you want to receive only SOAP requests on a particular port, from both internal and external users, you could allow the soap directive but no other directives on that port. To restrict the use of directives to certain ports only, you set the watt.server.allowDirective parameter (see watt.server.).

You can specify alternative names for the invoke, soap, and rest directives. For example, by default, the invoke directive is specified on URLs as "invoke" (that is, http://host:port/invoke/folder/service_name). You can identify an alternative word for users to specify as the invoke directive. For example, you might want to allow users to specify the invoke directive as "submit" (that is, http://host:port/submit/folder/service_name).

To specify an alternative word for the invoke directive, set the watt.server.invokeDirective parameter (see Server Configuration Parameters).

To specify an alternative word for the soap directive, set the watt.server.SOAP.directive parameter (see Server Configuration Parameters).

To specify an alternative word for the rest directive, set the watt.server.RESTDirective parameter (see Server Configuration Parameters).