An unbound connection can become bound in two ways:
A client application can call a remote persistent procedure (see ProgrammingABL Client Applications) or instantiate a ProcObject, in the case of an Open Client or Web service client. This call runs and instantiates a persistent procedure in the AppServer agent that handles the remote procedure request. The connection thus becomes bound, dedicating this AppServer agent to handle all future client requests over the bound connection.
An AppServer agent 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 AppServer agent that sets this attribute to handle all future client requests over the bound connection.
Note that 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 client application can call a remote persistent procedure (see ProgrammingABL Client Applications) or instantiate a ProcObject, in the case of an Open Client or Web service client. This call runs and instantiates a persistent procedure in the AppServer agent that handles the remote procedure request. The connection thus becomes bound, dedicating this AppServer agent to handle all future client requests over the bound connection.