Before you apply console security, you must step through the two wizards that create and configure your webNetwork server and services and then implement directory services as a local XML document database (LocalTree.XML). If you have many users and demand high performance, you should leverage a supported directory service like Active Directory, OpenLDAP (2.1.x) or Novell's eDirectory. The wizards also populate webNetwork objects into a public context in the selected directory and create a relay service, the default entry point into webNetwork.
The relay acts as a proxy on behalf of users and passes requests to other Web services, which means you can run the relay services on a separate server in a DMZ outside your firewall. It will communicate with the webNetwork server and Web resources inside the firewall using the Java RMI (Remote Method Invocation) protocol.
Test Setup
Rather than use multiple servers for my tests, I put the relay, server and all services onto one box and changed the default entry point from Port 11001 to Port 80. In this configuration, the relay communicates with the server and other webNetwork services through Port 80 of the loopback address (127.0.0.1).
WebNetwork services are applications that translate to features--such as shared forums and calendars, as well as news, alert and information components--for end users. Your users can publish documents using WebDAV (Web-based Distributed Authoring and Versioning) and view them within browsers using document viewers that support popular file formats, such as .doc, .xml and .pdf. Users also can register for services and configure their own interfaces. WebNetwork supports profiling, so you can customize its appearance to the corporate brand or a departmental standard.