Technical data

Modifying the obj.conf File
Administration Guide 13-7
The value of the ppath attribute can be any string that identifies requests
intended for Weblogic Server. When you use a
ppath, every request that
contains that path is redirected. For example, a
ppath of “*/weblogic/*”
redirects every request that begins “
http://enterprise.com/weblogic”
to the Netscape Enterprise Server Plug-In, which sends the request to the
specified Weblogic host or cluster.
c. Add the
Service directive within the <Object> and </Object> tags. In the
Service directive you can specify any valid parameters as name=value pairs.
Separate multiple name=value pairs with one and only one space. For example:
Service fn=wl_proxy WebLogicHost=myserver.com\
WebLogicPort=7001 PathTrim="/weblogic"
For a complete list of parameters, see “General Parameters for Web Server
Plug-Ins” on page -2. You must specify the following parameters:
For a non-clustered WebLogic Server:
The
WebLogicHost and WebLogicPort parameters.
For a cluster of WebLogic Server:
The
WebLogicCluster parameter.
The
Service directive should always begin with Service fn=wl_proxy,
followed by valid name=value pairs of parameters.
Here is an example of the object definitions for two separate
ppaths that
identify requests to be sent to different instances of WebLogic Server:
<Object name="weblogic" ppath="*/weblogic/*">
Service fn=wl_proxy WebLogicHost=myserver.com\
WebLogicPort=7001 PathTrim="/weblogic"
</Object>
<Object name="si" ppath="*/servletimages/*">
Service fn=wl_proxy WebLogicHost=otherserver.com\
WebLogicPort=7008
</Object>
Note: Parameters that are not required, such as PathTrim, can be used to
further configure the way the
ppath is passed through the Netscape
Enterprise Server Plug-In. For a complete list of plug-in parameters, see
“General Parameters for Web Server Plug-Ins” on page -2.