Establish client/server communications

Identify the process for starting and ending communication between IBM® i Access for Windows clients and host servers.

1. To initiate a server job that uses sockets communications support, the client system connects to a particular server's port number.
2. A server daemon must be started (with the STRHOSTSVR command) to listen for and accept the client's connection request. Upon accepting the connection request, the server daemon issues an internal request to attach the client's connection to a server job.
3. This server job may be a prestarted job or, if prestart jobs are not used, a batch job that is submitted when the client connection request is processed. The server job handles any further communications with the client. The initial data exchange includes a request that identifies authentication tokens that are associated with the client user. A user profile and password, or a Kerberos ticket, are examples of these tokens.
4. Once the authentication tokens are validated, the server job switches to use the IBM i user profile associated with those tokens, and changes the job by using many of the attributes defined for the user profile, such as accounting code and output queue.