http://developer.netscape.com/docs/manuals/js/core/jsref/index.htmhttp://www.inprise.com/visibroker/products/config directory in the https-server_id directory in the installation directory. For example, if Enterprise Server is installed on a Windows NT machine in D:\Netscape\server4\, the configuration files for the server boots.mcom.com are in:
D:\Netscape\server4\https-boots.mcom.com\configThe main configuration files are
magnus.conf, obj.conf, and mime.types, but there are other configuration files as well. See Chapter 2, "Configuration Files," for an overview of these configuration files.
For more detailed information about the files magnus.conf, obj.conf, and mime.types, see the "NSAPI Programmer's Guide" at
http://developer.netscape.com/docs/manuals/enterprise/4.0/nsapi/index.htmThe "NSAPI Programmer's Guide
manuals/nsapi directory.
config, include and so on, in HTML files.
exec tag. The page also allows you to specify whether to parse all files or just those with a .shtml extension.
The directive in obj.conf that enables the parsing of server-side tags is:
Service fn="shtml_send" type="magnus-internal/parsed-html" method="(GET|HEAD)"To enable parsing of server-side tags for files with extensions other than
.shtml, add the extension to the appropriate line in the mime.types file. For example, the following line in mime.types indicates that files with either a .shtml or .jbhtml extension will be parsed for server-side tags.
type=magnus-internal/parsed-html exts=shtml,jbhtmlAfter making changes to
mime.types, restart the Enterprise Server to update its table of MIME type mappings, since the mime.types file is only loaded when the server is initialized.
http://developer.netscape.com/docs/manuals/enterprise/4.0/wrijsap/index.htm
obj.conf file has the following directives:
Init objects="d:/netscape/server4/https-boots.mcom.com/config/jsa.conf" fn="livewireInit"NameTrans fn="livewireNameTrans" name="ServerSideJS"<Object name="ServerSideJS">
Service fn="livewireService"
</Object>
If an administration server password is required to access the Server Side Javascript Application Manager, the ServerSideJS object will have more directives..web file. You will find several sample JavaScript applications, including the source files, the .web files, and the make files in the directory server-root/plugins/samples/js. One of the easiest ways to compile a new application is to copy a make file for an existing application and modify it to suit your needs.
For information about compiling server-side JavaScript Applications, see the section "Compiling an application" in "Chapter 3, Mechanics of Developing JavaScript Applications" in the book "Writing Server-Side JavaScript Applications" at:
http://developer.netscape.com/docs/manuals/enterprise/4.0/wrijsap/index.htm
http://server_name/appmgr/, for example http://poppy.mcom.com/appmgr/.
To access the JavaScript Application Manager from the Server Manager interface, go to the Server-side JavaScript page in the Programs tab. At the top of the page, you see a line saying something like:
The Server side Javascript Application Manager is at http://poppy.mcom.com/appmgr/Click on the location for the application manager. The application manager opens in another browser window. You can use the application manager to add JavaScript applications, run them, stop them, start them, and debug them. For information about using the JavaScript Application Manager, see:
manuals/ag directory.)http://developer.netscape.com/docs/manuals/enterprise/4.0/wrijsap/index.htm
http://developer.netscape.com/docs/manuals/js/core/jsref/index.htmhttp://developer.netscape.com/docs/manuals/communicator/jsref/index.htmhttp://developer.netscape.com/docs/manuals/enterprise/4.0/wrijsap/index.htmhttp://developer.netscape.com/docs/manuals/enterprise/4.0/wrijsap/index.htm
Also see "Chapter 10, LiveWire Database Service" of the JavaScript Reference at:
http://developer.netscape.com/docs/manuals/communicator/jsref/index.htmhttp://www.mozilla.org/js/
obj.conf contains a NameTrans directive that associates the name cgi with each request for a resource in that directory. These directives are automatically added to obj.conf when you specify CGI directories in the Server Manager interface, or you can manually add them to obj.conf if desired.
For example, the following instruction interprets all requests for resources in http://server-name/cgi-local as requests to invoke CGI programs in the directory D:/Netscape/Server4/docs/mycgi.
NameTrans fn="pfx2dir" from="/cgi-local"The
dir="D:/Netscape/Server4/docs/mycgi" name="cgi"
obj.conf file must contain the following named object:
<Object name="cgi">Do not remove this object from
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
obj.conf. If you do, the server will never recognize CGI directories, regardless of whether you specify them in the Server Manager interface or manually add more NameTrans directives to obj.conf.
cgi, .bat and.exe.
To change which extensions indicate CGI programs, modify the following line in mime.types to specify the desired extensions. Be sure to restart the server after editing mime.types.
type=magnus-internal/cgi exts=cgi,exe,batWhen the server is enabled to treat all files with an appropriate extensions as CGI programs, the
obj.conf file contains the following Service directive:
Service fn="send-cgi" type="magnus-internal/cgi"http://hoohoo.ncsa.uiuc.edu/cgi/overview.html
servlets.jar file is accessible to your Java compiler. The servlets.jar file is in the server installation directory at:
/bin/https/jarFor information on using the Servlet API see the "Java Servlet API" documentation from Sun Microsystems at:
http://www.javasoft.com/products/servlet/index.htmlA JavaServer Page (JSP) is a page much like an HTML page that can be viewed in a web browser. However, as well as containing HTML tags, it can include a set of JSP tags that extend the ability of the web page designer to incorporate dynamic content in a page. These tags provide functionality such as displaying property values and using simple conditionals.
http://www.javasoft.com/products/jdk/1.2/
Enterprise Server 4.0+ requires you to use an official version of JDK1.2 on Solaris and NT. On HP, AIX and IRIX use JDK 1.1.Regardless of whether you choose to install the JRE or specify a path to the JDK during installation, you can tell the Enterprise Server to switch to using either the JRE or JDK at any time, by using the "Configure JRE/JDK Paths" page in the Servlets tab of the Server Manager. Before the server can serve servlets and JSP, the servlet engine must be enabled. To enable servlets and JSP, use the Enable/Disable Servlets page in the Servlets tab of the Server Manager interface. If servlets are enabled, JSP can be enabled or disabled. If servlets are disabled, JSP is also disabled. When servlets are enabled, the
obj.conf file contains the following Init directives. The first one loads the servlets library and makes the servlet-related functions available to the Enterprise Server. The other two directives initialize the servlet engine.
Init shlib="d:/netscape/server4/bin/https/bin/NSServletPlugin.dll"
funcs="NSServletEarlyInit,NSServletLateInit,NSServletNameTrans,
NSServletService" shlib_flags="(global|now)" fn="load-modules"
Init EarlyInit="yes" fn="NSServletEarlyInit"
Init LateInit="yes" fn="NSServletLateInit"The file
obj.conf also has other directives that relate to servlets, and defines several additional objects for processing requests for servlets.
server_id/docs/servlet/.
For details of how to register servlet directories, see the book "Programmer's Guide to Servlets in ES 4.0.".jsp extension, and put it on the server in a directory at or below the document root. So long as JSP is enabled, the Enterprise Server treats all files with a .jsp extension as JavaServer Pages.
NOTE: Do not put JSP files in a registered servlets directory, since the Enterprise Server expects all files in a registered servlet directory to be servlets.)
http://www.javasoft.com/products/servlet/index.htmlFor information about creating JavaServer Pages, see Sun Microsystem's JavaServer Pages 0.92 spec in the build in the manuals/https/servlets/jsp092 subdirectory.
obj.conf contains instructions (known as directives) that tell the server how to process requests received from clients. Each instruction is enacted either during server initialization or during a particular stage of the request-handling process. Each instruction invokes a server application function (SAF).
For example, the following instruction is invoked when the request method is GET and the requested resource is of type text/html. This instruction calls the append-trailer function with a trailer argument of <H4><font color=green>Served by 4.0</font></H4>. (The append-trailer function simply returns the requested resource -- in this case an HTML file -- to the client, and appends the given trailer to it.)
Service method=GET type="text/html" fn=append-trailerEnterprise Server 4.0 comes with a set of pre-defined SAFs. It also comes with a library of NSAPI functions for developing your own SAFs to modify the way that the server handles requests.
trailer="<H4><font color=green>Served by 4.0</font></H4>"
obj.conf. The file obj.conf is essential for the operation of the server -- if it does not exist, the server cannot work, since it has nowhere to look for instructions on how to handle requests.
When defining new SAFs, include the header function nsapi.h (which is in server-root/plugins/include) to get access to all the NSAPI functions.
Init directive to obj.conf to load the shared library file that defines the new SAFs. This directive must call the load-modules function, which takes the following arguments:
For example, the following directive loads the shared library d:/netscape/server4/bin/https/bin/httpdlw.dll, (which enables server-side Javascript) and makes the functions livewireInit, livewireNameTrans, and livewireService available to the server.
Init fn="load-modules"
shlib="d:/netscape/server4/bin/https/bin/httpdlw.dll"
funcs="livewireInit,livewireNameTrans,livewireService"
obj.conf and how they determine how the server handles requestsobj.conf that calls load-moduleshttp://developer.netscape.com/docs/manuals/enterprise/4.0/nsapi/index.htmThe "NSAPI Programmer's Guide
manuals/nsapi directory.
http://developer.netscape.com/docs/manuals/enterprise/3.0/wai/index.htm
http://www.inprise.com/visibroker/products/After installing Visibroker, install the WAI component of Enterprise Server 4.0. After WAI is installed, you then need to enable WAI. Do this by using the WAI Management page in the Programs tab of the Server Manager. (If WAI is not installed, this button does not appear.)
obj.conf:
Init directive that invokes the load-modules function to load the shared library.Init directive that calls the initialization function.http://www.inprise.com/visibroker/products/For more information about writing WAI applications, see:
http://developer.netscape.com/docs/manuals/enterprise/3.0/wai/index.htm
private.
acl "*private*";To create access control lists, use the Restrict Access page in the Programs tab of the Server Manager interface. You can also edit the files that contain the ACLs used by the server. Access control lists reside in the directory
deny (all)
(user = "anyone");
server-installation-dir/httpacl. The server uses the default settings in the file server_root/httpacl/generated.https-serverid.acl. There is also a file called genwork.https-serverid.acl that is a working copy the server uses until you save and apply your changes when working with the user interface. When editing the ACL file, you might want to work in the genwork file and then use the Server Manager to load and apply the changes.
With the Access Control API, you can manipulate access control lists (ACLs), read and write ACL files, and evaluate and test access control to resources on the server. You can also define your own attributes for authentication. For example, you might want to authenticate users based on email address or on the URL that referred them to the resource. You can also authenticate the client based on your own authentication methods and databases.
obj.conf:
Init directive that invokes the load-modules function to load the shared library.Init directive that calls the initialization function.http://developer.netscape.com/docs/manuals/enterprise/3.0/accessapi/index.htmFor information about the syntax for editing ACL files, see Appendix A in the same book.
http://developer.netscape.com/docs/manuals/enterprise/3.0/webpub/index.htm
Table 1.1 APIs available in Netscape Enterprise Server 3.0
| API/Interface/Protocol | Language |
Documentation
|
|
|
|
|
|
|
|
|
|
|
|
| | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Last Updated: 08/12/99 12:35:13
Copyright ©1999 Netscape Communications Corp. All rights reserved.