There are some general requirements that every SOA web service client program must meet:
Reliable Session must be enabled
This is accomplished in the configuration file for the client application. Both the netTcpBinding and wsHttpBinding elements of the configuration file contain a reliableSession element:
<reliableSession ordered="true" inactivityTimeout="nn:nn:nn" enabled="true" />
Make sure the values for ordered and enabled are true. When you create a service reference, The Reliable Session value is propagated to the client program.
Impersonation or Delegation must be set for the network environment
If the DeltaV network is in a workgroup or the client is within the DeltaV domain, use Impersonation.
If the client is run in a domain outside of the DeltaV domain, use Delegation.
The Connect method must be called before calling any other method.
This method ensures that delegation or impersonation of users works properly in both domain and workgroup environments.
Client programs running in the external domain must point to the Secure SOA Server, not the SOA Gateway within the DeltaV system domain.
The web services property values are not automatically propagated from the Gateway Administration application to client programs. You must set the following properties in the configuration file for each client program to match the values in the Gateway Administration application:
CloseTimeout
InactivityTimeout
MaxArrayLength
MaxBytesPerRead
MaxReceivedMessageAndBufferSize
MaxStringContentLength
OpenTimeout
ReceiveTimeout
SendTimeout