The Workplace Shell, when started, will default to the wpdServer class and load WPDSERV.DLL. If you create a new server class, you can tell the Workplace Shell to use your server by setting WPDSERVERALIAS to YourServer in the CONFIG.SYS file and use regimpl to change the server name from wpdServer to YourServer.
There are a number of ways to start the DSOM daemon and Workplace Shell DSOM server. To start both SOMDD and WPDS at the time the OS/2 operating system is started, set WPDSERVERSTART to ON in the CONFIG.SYS file and reboot. Both the daemon and the server are hidden to the user when started.
If during development you require to see the output of SOMDD, then set the environment variable SOMDD.DISPLAY to ON in the CONFIG.SYS file and reboot. When using the Workplace Shell DSOM server you should always allow the Workplace Shell to start the DSOM daemon and never start the daemon from a command line. In this way, the Workplace Shell is aware of its existence.
In the case, when a client DSOM application is run and only the DSOM daemon is active, then the implementation repository, using the implementation ID passed to it to locate the server definition, starts an executable, WPDSACTV.EXE, which in-turn starts the Workplace Shell DSOM server. Once the server is active, then the client program will continue to process as normal.
The OS/2 operating system supplies a utility called WPDSINIT.EXE which provides the functions to start, stop and query the current status of the DSOM daemon and the Workplace Shell DSOM server from the command line:
Function Name
The DSOM daemon or the Workplace Shell DSOM server can be manipulated independently by specifying either somdd or server as the second parameter to WPDSINIT.
The last method available for manipulating both the daemon and the server is programmatically through four new functions: