Oracle A54857-03 - Manual (Page 53)

Migrating to Oracle Web Listener 6-5
Migrating the obj.conf and mime.types Files
The obj.conf file defines how the server should handle the incoming requests for
documents and programs. An object contains a name or a pattern match which
defines the resources it applies to. For example:
<Object ppath=...>
Directives.
</Object>
Object also contains a series of directives. For example:
Directive fn=function [parameters]
The following directives can be converted:
• Init fn=load-types mime-types=xxx
The value for mime-types= is the file name that contains the MIME type
and ENCODING extension mapping, formatted as follows:
type=application/octet-stream exts=bin,exe
euc=x-gzip exts=gz,gzip,gzzipp
These MIME type and ENCODING extensions are translated into the
sv
server.cfg [MIMETypes] and [Encoding] sections as:
[MIMETypes]
application/octet-stream bin exe
[Encoding]
x-gzip gz gzip
Note: Oracle Web Application Server only allows extensions with less than five
characters. Any extensions with more than four characters are not migrated and
are reported after the migration is complete.
• NameTrans fn=”pfx2dir” from=/img dir=/Netscape/img
The value for from= is the virtual path; the value for dir= is the physical
path. This directive is mapped into the svserver.cfg [DirMaps] section as:
[DirMaps]
/Netscape/img/ NR /img/
• NameTrans fn=”pfx2dir” from=”/cgibin” dir=/Netscape \
/cgibin name=cgi
The value for from= is the virtual path and the value for dir= is the
physical path. The name=cgi means this is a cgi-bin directory. This
directive is mapped into the svserver.cfg [DirMaps] section as