Configuring SAS BI Web Services for Java

When a Web service operation is invoked, it in turn calls the appropriate SAS Stored Process running on the server tier. SAS execution always returns the SYSCC macro variable upon completion. By default, if this completion code is not 0, a SOAP fault is generated and returned to the invoking client. Alternatively, a comma-separated list of acceptable SAS completion codes can be specified to alter this behavior. Also, a hyphen separating two values can be used to conveniently specify a range of acceptable completion codes. In this case, the acceptable list of completion codes are treated as warnings rather than errors and do not cause a SOAP fault.

When invoking Web service operations for stored processes that have been configured with dynamic prompt data parameters, you can turn off validation to obtain better throughput if you are certain that these stored processes have been written in a robust manner to handle any possible data passed by clients. Dynamic prompt validation is enabled by default so that the middle-tier Web service validates client data against data providers to ensure that incoming data meets the specified criteria before calling the appropriate stored process on the server.

Set this property if you want to limit the amount of time that a stored process is allowed to run. If the stored process fails to execute in the specified time, it is canceled and a SOAP fault is returned to the invoking client. A value of zero indicates no time-out period.

Specify whether you want to enable or disable anonymous execution.

This property is the base namespace that is concatenated with the service name to create a target namespace to uniquely identify generated Web services. For example, if the base namespace is set to http://tempuri.org, and a client creates a new service named test without specifying an overriding namespace for this new service, then the target namespace for this Web service becomes http://tempuri.org/test.

Specifies the attachment conformance that should be enabled for generated Web services. There are two options: Message Transmission Optimization Mechanism (MTOM) and SOAP Messages with Attachments (SWA). The default is MTOM.

Setting this property to True causes the incoming request to be validated against the service’s schema. The default is false because this operation can be CPU intensive.

Setting this property to True causes the resulting output created by the service execution to be validated against the service’s schema. The default is false because this operation can be CPU intensive.

The default value is 2048 bytes. This attachment threshold is the number of bytes contained in the attachment that causes the data to be included as an out-of-band XOP/Include MTOM attachment. An attachment containing fewer bytes is transferred inline as base64 encoding for optimization.

See Acceptable SYSCC List. This property overrides its analogous common configuration property.

See Enable dynamic prompts validation. This property overrides its analogous common configuration property.

See SAS Stored Process timeout. This property overrides its analogous common configuration property.

Enabled by default. This property requires the SAS Anonymous Web user or Webanon account to have been created previously.

This property is the base namespace that is concatenated with the service name to create a target namespace to uniquely identify generated Web services. For example, if the base namespace is set to http://tempuri.org, and a client creates a new service named test without specifying an overriding namespace for this new service, then the target namespace for this Web service becomes http://tempuri.org/test.

This property specifies the attachment conformance that should be enabled for generated Web services. There are two options: Message Transmission Optimization Mechanism (MTOM) and SOAP Messages with Attachments (SWA). The default is MTOM.

Setting this property to true causes the incoming request to be validated against the service’s schema. The default is false, because this operation can be CPU intensive.

Setting this property to true causes the resulting output that is created by the service execution to be validated against the service’s schema. The default is false because this operation can be CPU intensive.

The default is 2048 bytes. This attachment threshold is the number of bytes contained in the attachment that causes the data to be included as an out-of-band XOP/Include MTOM attachment. An attachment containing fewer bytes is used as base 64 encoding for optimization.