Technical data

Using SSL with the NSAPI Plug-In
Administration Guide 13-9
fn=wl_proxy WebLogicHost=localhost WebLogicPort=7001\
PathPrepend=/jspfiles
PathCheck fn=nt-uri-clean
PathCheck fn="check-acl" acl="default"
PathCheck fn=find-pathinfo
PathCheck fn=find-index index-names="index.html,home.html"
ObjectType fn=type-by-extension
ObjectType fn=force-type type=text/plain
Service method=(GET|HEAD) type=magnus-internal/imagemap\
fn=imagemap
Service method=(GET|HEAD) \
type=magnus-internal/directory fn=index-common
Service method=(GET|HEAD) \
type=*~magnus-internal/* fn=send-file
AddLog fn=flex-log name="access"
</Object>
b. Add a similar Service statement to the default object definition for all other
MIME types that you want to proxy to WebLogic Server.
5. If you want to enable HTTP-tunneling (optional):
Add the following object definition to the
obj.conf file, substituting the
WebLogic Server host name and the WebLogic Server port number, or the name
of a WebLogic Cluster that you wish to handle HTTP tunneling requests.
<Object name="tunnel" ppath="*/HTTPClnt*">
Service fn=wl_proxy WebLogicHost=192.192.1.4\
WebLogicPort=7001
</Object>
Using SSL with the NSAPI Plug-In
Use the Secure Sockets Layer (SSL) protocol to protect the connection between the
Netscape Enterprise Server Plug-In, and WebLogic Server. The SSL protocol provides
confidentiality and integrity to the data passed between the Netscape Enterprise Server
Plug-In and WebLogic Server. In addition, the SSL protocol allows the WebLogic
Server proxy plug-in to authenticate itself to the Netscape Enterprise Server to ensure
that information is passed to a trusted principal.