Overview - DCE Application Administration
As DCE evolves, commonly needed functions are being included in the DCE infrastructure. As an example, DCE Version 1.1 includes server control capabilities that can manage server operation and help servers exit in a controlled and efficient manner. Application developers can rely on these capabilities rather than implement special mechanisms to handle them independently in every server.
Moving commonly needed functions out of applications and into the DCE infrastructure provides important benefits. Applications can be smaller and easier to develop and maintain. Even more important, because applications are not encumbered with lots of special code, they are easier to reconfigure and reconnect with different kinds of clients. This adaptability is critical as organizations strive to keep up with changing business needs.
DCE applications have always had administrative aspects. Often, programs include the necessary functions to manage their own administrative needs, but this approach can be awkward and somewhat inflexible for administrators. Now, virtually all administrative functions are available to programmers and administrators alike through dcecp. This does not mean programmers no longer need to deal with these issues.
We expect some programmers to provide scripts written with dcecp that configure client and server programs to start and stop under specified conditions.
Although this approach offers a convenient and consistent way to administer applications, it also creates an area where programming and administrative concerns overlap. Our discussions in this topic will include this area of overlap, noting circumstances where administrative action might be needed.