Understanding the Changes in Server Management

Client/Server Binding with CCI required a non-dedicated server module, MFSERVER, to run on the server machine. For each new client conversation, this spawned a dedicated instance of itself to handle the server part of the application. The non-dedicated module was usually started manually, either by a user from the command line or by a system script. When a system administrator wanted to stop the server, the usual mechanism was to run the "mfcsmgr" utility with the "-t" option.

With Client/Server Binding using AAI (CSBIND/AAI), the spawning of the dedicated server module was controlled by AAI, and the system administrator would start and stop it by starting and stopping the AAI subsystem.

Client/Server Binding for Server Enterprise Edition is similar to AAI in this area, though it is more flexible. It provides a service package, CSBIND, which runs the server part of your application. The package can be associated with one or more services and one or more listeners (which receive client requests and pass them to the package module). Typically, you will configure a separate service for each of your Client/Server Binding applications, and you will have one listener (such as the "Web Services and J2EE" listener included with the sample configuration) which receives the requests. You can also give CSBIND requests their own listener, or multiple listeners.

If the CSBIND services are configured as "Available" and their listeners are configured to start when the enterprise server is started - the default configuration - then your Client/Server Binding servers will be available whenever that enterprise server is running.

If you change the status of a CSBIND service to "Disabled" while your enterprise server is running, your client programs will no longer be able to establish a connection with that service. If you change the status of the service's listener to "Blocked", then all services belonging to that listener will be hidden from all clients (except for clients which connect directly using the "machinename" configuration option - see below). If you change the status of the listener to "Stopped", then it will stop accepting new conversations until it is changed back to "Started" or the enterprise server is restarted.