Connections

In a USoft application other than a client/server (Windows) application, all functionality is offered by a Rules Service that taps into that application.

In Service Definer, connect your services to a Rules Service by defining a connection associated to that Rules Service.

You can use a single connection and Rules Service for all your services. The same Rules Service can even be used by interactive web pages created in USoft Web Designer.

Depending on runtime workload and on administration needs in complex applications, you can alternatively create multiple connections, multiple Rules Services, multiple Rules Service instances, or all of these at the same time.

Each connection has a session name. Session names are useful in the context of web applications. To be able to create web applications using REST services, the USoft Services Framework returns cookies to the browser to recognize REST requests that come from the same user. If the user is inactive for a while (longer than the session timeout), then the Services Framework will throw an error.

By default, a Connection's Session Name attribute is set to the connection name. The session timeout is indicated by the Connection's "Session expiration seconds" attribute. By default, this attribute is set to 600 seconds.

If you use a SAML service provider configuration that must be able to connect to a Rules Service associated with your connection, Session Name must be the name of the entity name of the SAML service provider configuration.