An unbound connection can become bound in two ways:
A client application can call a remote persistent procedure (see Programming ABL Client Applications) or instantiate an Open Client ProcObject, in the case of an Open Client or SOAP Web service client. This call runs and instantiates a persistent procedure in the PAS for OpenEdge session that handles the remote procedure request. The connection thus becomes bound, dedicating this session to handle all future client requests over the bound connection.
Note: It is the successful instantiation of a remote persistent procedure that forces the connection to transition from the unbound state to the bound state. If a client fails in its attempt to instantiate a remote persistent procedure on an unbound connection, the connection remains unbound.
A PAS for OpenEdge session handling a request from a client can run a procedure that sets the SERVER-CONNECTION-BOUND-REQUEST attribute on the SESSION handle to TRUE. The connection thus becomes bound, dedicating the session that sets this attribute to handle all future client requests over the bound connection.
A client application can call a remote persistent procedure (see Programming ABL Client Applications) or instantiate an Open Client ProcObject, in the case of an Open Client or SOAP Web service client. This call runs and instantiates a persistent procedure in the PAS for OpenEdge session that handles the remote procedure request. The connection thus becomes bound, dedicating this session to handle all future client requests over the bound connection.