./importdb
userdb_name
Converting 2.0 ACL files
Currently, there are no forms that allow you to edit a 3.0 ACL file; you must edit the file by using a text editor after the conversion.
To convert 2.0 ACL files:
<Object ppath="/usr/ns-homeC:/Netscape/Server/docs/test/*">In the previous example, the first line is the object that states which server resource you want to restrict access to. The second line is the PathCheck directive that uses the check-acl function, which binds the ACL file to the object in which the directive appears; the name of the ACL file is testacl.
PathCheck fn="check-acl" acl="testacl"
</Object>
version 3.0;
acl sampleacl;
authenticate (user, group){
method = ssl;
};
allow (read) user=all;
allow (write) group="*";
version 3.0;ACLs must be named. The ACL must include the following line:
acl
acl_name;
authenticate (user) {The following example uses SSL as the authentication method for users and groups:
method = basic;
};
authenticate (user, group) {
method = ssl;
};
allow|deny [absolute] (right[,right...]) attribute qualifier expression;allow|deny--Use allow to allow users and groups access; use deny to deny users and groups access. absolute--The result of this statement cannot be overridden by any succeeding statment. ACL evaluation ends, and the allow or deny is applied. You can restrict access to your server by time of day (based on the local time on the server) by using the timeofday attribute qualifier. For example, you can use the timeofday attribute qualifier to restrict access to certain users during specific hours. Use military-style, 24-hour time to specify times (for example, use 0400 to specify 4 a.m. or 2230 for 10:15 p.m.). The following example restricts access to a group of users called guests between 8 a.m. and 4:59 pm.
allow (read)You can also restrict access by day of the week. Use the following three-letter abbreviations to specify days of the week: Sun, Mon, Tue, Wed Thu, Fri, and Sat. The following example controls access for premium customers (any day, any time) and Discount customers (all day weekends and weekdays anytime except 8am-4:59pm):
(group=guests) and
(timeofday<800 or timeofday>=1700);
allow (read) (group=discount and dayofweek=SatSun) or
(group=discount and (dayofweek="mon,tue,wed,thu,fri" and
(timeofday<0800 or timeofday>=1700)))
or
(group=premium);
NoteIf you delete or modify agent files, the agents will no longer work.
Configuring web publishing
Netscape Web Publishing System includes document management controls to allow you as a server administrator and end users who have proper permissions to:
http://[server_name]/WebPub/WPIntro.html/For example, if your web server's name is www.acmecorp.com, you'd type
http://www.acmecorp.com/WebPub/WPIntro.html/
to access the web publishing home page.
More information on how to use web publishing is in the"User's Guide", which is located in your server root directory, in the /bin/https/admin/html/manual/beta directory.
Setting up version control
Use the version control feature in Netscape Enterprise Server to provide check-in, and check-out capabilities to groups of people working on the same set documents. As a default, version control is enabled for your server. To disable version control, delete or comment out references to ContentMgr in obj.conf, which is in [server_root]/https-[server_name]/config.
Only users and groups that have been created using the Users&Groups forms in the administration server will have access to files placed under version control. For more information about creating users and groups, see "Configuring the administration server", which is located in your server root directory, in the /bin/https/admin/html/manual/beta directory.
To change the version control archive directory:
Adding metadata properties
As server administrator, you can add properties for metadata.
To add properties:
Caution!If you have sensitive documents in the collection directory that are protected by access control, you should store them in another directory. Although protected documents can be searched, and any matches in them to user-specified criteria will be listed in the search results, users cannot access any protected documents unless they enter a valid user name and password.
NameTrans from="/ns-search" fn="search-find"
NameTrans from="/search" fn="pfx2dir" dir="[ServerRoot]/plugins/search/vsearch" name="cgi"
NameTrans from="/ui" fn="pfx2dir" dir="[ServerRoot]/plugins/search/ui"
Service fn="search-service"cgi-path="[ServerRoot]/plugins/search/vsearch/iareco rd.exe" type="magnus-internal/search"
Note
When adding the previous lines to your obj.conf file, substitute [ServerRoot] with your server root directory. Place the NameTrans directives with the existing NameTrans directives; place the Service directive with the existing Service directives.