WL Cluster with NES Proxy

Question

We are evaluating the Cluster features of WebLogic and got a eval
          license for the Cluster Support.
          I am running a default cluster (mycluster) using the default Multicast
          address (237.0.0.1) and am seeing
          some strange behaviour/errors.
          Would appreciate some asistance in this matter.
          Our Environment
          I created directory in a shared file system to host the cluster.
          (h:\kkanth\weblogic)
          Created the mycluster directory and other directories as recommended in
          the Administrator's guide.
          I have two WL Servers (asera190 and asera162) with permanent IP
          addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
          I'm using a NES proxy on asera190 with the plugin for WL specified in
          obj.conf alongwith the other parameters.
          I'm able to have both the servers join to cluster mycluster and the WL
          Admin Console does display a tree that depicts the cluster as well as
          servers in it (server61 and server70). The individual server directories
          are being created in h:\kkanth\weblogic\mycluster directory with the
          appropriate access.log and weblogic.log files.
          When a browser attempts to access a URL such as
          http://asera190/weblogic/snoop it does return the proper response, but
          all requests are processed by asera162 which is listed first in the
          obj.conf. Opening multiple sessions does not cause the requests to be
          sent to asera190 which is the second server in the cluster. When
          asera162 is shutdown and removed from the cluster, I hoped that
          subsequent requests would go to asera190. However , depending on the
          origin of the request, different errors were thrown. If I try to access
          http://asera190/weblogic/snoop from a browser on asera190, I get an
          error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
          from asera162 cause "Failure at line 706 of file proxy.cpp".
          I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
          directory as well as the obj.conf file in the ....\config\ directory of
          asera190.
          We are running NES 3.5.1 and have setup proxy35.dll appropriately.
          weblogic.properties
          # THE WEBLOGIC PROPERTIES FILE
          # This file, which conforms to the java.util.Properties file
          # definition, configures your WebLogic products. You cannot run
          # WebLogic Server without setting required configuration properties in
          this
          # file. Required properties are marked and appear first in the file.
          # Details on each entry and important information about configuration
          # and security are documented on our website. Please go to:
          # http://www.weblogic.com/docs45/admindocs/properties.html
          # for full instructions on how to edit this file.
          # You do not need to include properties in this file unless you want to
          # change the default, embedded property. Some properties on the
          # T3AdminProps page are not listed here because the default property
          # is being used. You can change the default by adding the property and
          # its value to this file.
          # You cannot set weblogic.system.home in this file, since the WebLogic
          Server
          # must know where home is in order to retrieve this file. You can
          # change WebLogic home on the command line when you start the
          # WebLogic Server.
          # CLUSTER USERS: Note that the (shared) per-cluster properties file
          should
          # contain most all of the properties in this file. The only properties
          # that potentially belong in a per-server properties file for a server
          # running in a cluster are the registration (startup class) of pinned
          # RMI objects, and a few tuning properties that may be different for
          # servers in the cluster, depending upon hardware and memory. If you use
          # a per-server properties file, please REMOVE all properties except
          those
          # that are specifically required in the per-server properties file. You
          # can find specific notes on clusters by searching through this file for
          # "CLUSTER USERS".
          # The way this file is organized:
          # Core properties (includes REQUIRED and RECOMMENDED)
          # Core system properties
          # Core security-related properties
          # Core security-related properties for SSL
          # Core HTTPD administrative properties
          # Optional properties
          # Administrator properties
          # System properties
          # System startup files
          # System shutdown files
          # Security-related properties for Workspaces
          # Jolt for WebLogic properties
          # WebLogic Enterprise Connectivity properties
          # WebLogic File properties
          # WebLogic JMS demo properties
          # WebLogic RMI demo properties
          # WebLogic EJB demo properties
          # WebLogic ZAC demo properties
          # HTTPD administrative properties
          # WebLogic JDBC driver properties
          # WebLogic JDBC connection pool management
          # WebLogic demo connection pool
          # WebLogic HTTP Servlet properties
          # Proxy servlet registration
          # Classpath servlet registration
          # File servlet registration
          # ServerSideInclude servlet registration
          # PageCompileServlet (used by JHTML)
          # JSPServlet (used by JSP)
          # ServletServlet registration
          # Servlet reload properties
          # Servlet ACLs
          # WebLogic JHTML properties
          # User-written and demo servlet registrations
          # CORE PROPERTIES
          # You should set these before you start the WebLogic Server the first
          time.
          # If you need more instructions on individual properties in this
          # section, check the same section in the Optional Properties, where
          # we've left the long explanations. Or, better yet, go to our
          # website and read all about properties, at:
          # http://www.weblogic.com/docs45/admindocs/properties.html
          # CORE SYSTEM PROPERTIES
          # TCP/IP port number at which the WebLogic Server listens for
          connections
          weblogic.system.listenPort=7001
          # CORE SECURITY-RELATED PROPERTIES
          # Read important information about security at:
          # http://www.weblogic.com/docs45/admindocs/properties.html
          # REQUIRED: The system password MUST be set in order to start the
          # WebLogic Server. This password is case-sensitive, at least 8
          characters.
          # The username for the privileged user is ALWAYS "system".
          # This username and password also includes httpd access (see
          # HTTPD properties below).
          weblogic.password.system=kaykayka
          # RECOMMEND Set to 'everyone' if HTTPD is enabled
          weblogic.allow.execute.weblogic.servlet=everyone
          # Set individual ACLs to restrict access to HTTP-related resources,
          # such as the Administration servlets.
          # To make your own servlets generally available, follow this
          # pattern (provide a weblogic.allow.execute) for your packages and
          # set ACLs as appropriate.
          # CORE SECURITY-RELATED PROPERTIES FOR SSL
          # Read important information about SSL at:
          # http://www.weblogic.com/docs45/classdocs/API_secure.html
          # Enable SSL
          # (default if property not defined is false)
          weblogic.security.ssl.enable=true
          # SSL listen port
          weblogic.system.SSLListenPort=7002
          # Servlets for SSL
          # Authentication servlet for creating tokens for applets
          weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
          # Limits number of unclaimed stored tokens
          weblogic.security.certificateCacheSize=3
          # Capture CA root of client servlet
          weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
          # Certificates for SSL
          # Name of acceptable CA roots
          # For client authentication change value to a valid .pem file
          #weblogic.security.clientRootCA=SecureServerCA.pem
          # Server certificates for SSL
          weblogic.security.certificate.server=democert.pem
          weblogic.security.key.server=demokey.pem
          weblogic.security.certificate.authority=ca.pem
          # registration for certificate generator servlet
          weblogic.httpd.register.Certificate=utils.certificate
          weblogic.allow.execute.weblogic.servlet.Certificate=system
          # CORE HTTPD ADMINISTRATIVE PROPERTIES
          # True permits the HTTPD to run (default)
          # Uncomment this property to disable HTTPD
          #weblogic.httpd.enable=false
          # If authentication is required, add username/password for each user
          # who will be included in an ACL, as in this commented-out example:
          #weblogic.password.peter=#8gjsL4*
          # OPTIONAL PROPERTIES
          # These properties affect the behavior of the WebLogic Server.
          # You only need to set these properties if you want
          # to change the default setting, which is the property shown.
          # ADMINISTRATOR PROPERTIES
          # Administrator properties are optional information properties,
          # particularly useful for clusters.
          #weblogic.administrator.location=3355 California Drive, West Hampshire,
          CA 94104
          #weblogic.administrator.name=Joe Administrator
          #weblogic.administrator.phone=1 415 555 1234
          # SYSTEM PROPERTIES
          # System properties in this section are set to system defaults
          # Performance pack. The shared library must be accessible from your
          # PATH (NT) or from your shared library path (UNIX; the name of the
          # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
          weblogic.system.nativeIO.enable=true
          # Outputs logging information to the console as well as to the log file
          weblogic.system.enableConsole=true
          # Sets the directory or URL for the WebLogic Admin help pages
          # The help pages are shipped in the "docs/adminhelp" directory, in the
          # default document root in public_html
          weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
          # If you prefer to access the most recent help pages, you can do so
          online
          # by commenting out the previous property and uncommenting this one:
          #weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
          # Properties for tuning the server's performance
          # Number of WebLogic Server execute threads.
          weblogic.system.executeThreadCount=15
          # Other optional system properties
          # Limits size of weblogic.log (in K) and versions old log
          weblogic.system.maxLogFileSize=1024
          # Adjust minimum length of password
          weblogic.system.minPasswordLen=8
          # UNIX only: If running on port 80 on UNIX, enable the setUID program
          #weblogic.system.enableSetUID=false
          # UNIX only: Unprivileged user to setUID to after starting up
          # WebLogic Server on port 80
          #weblogic.system.nonPrivUser=nobody
          # CLUSTER-SPECIFIC PROPERTIES
          # Cluster-specific properties in this section are set to system
          defaults.
          # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
          # in the per-cluster properties file ONLY.
          # Time-to-live (number of hops) for the cluster's multicast messages
          # (default 1, range 1-255).
          #weblogic.cluster.multicastTTL=1
          # Sets the load-balancing algorithm to be used between
          # replicated services if none is specified. If not specified,
          # round-robin is used.
          #weblogic.cluster.defaultLoadAlgorithm=round-robin
          # SERVER-SPECIFIC CLUSTER PROPERTIES
          # Cluster-related properties in this section are set to system defaults.
          # CLUSTER USERS: Note that these server-specific cluster-related
          properties
          # should be set in the per-server properties file ONLY.
          # Sets the weight of the individual server for the weight-based
          load-balancing.
          # Range is 0 - 100.
          # Larger numbers increase the amount of traffic routed to this server.
          #weblogic.system.weight=100
          # SYSTEM STARTUP FILES - Examples
          # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
          # objects should be registered in the per-server properties file.
          # All other startup classes should be registered in the per-cluster
          # properties file.
          # For more info on writing and using startup file, see the
          # Developers Guide "Writing a WebLogic Client application," at
          # http://www.weblogic.com/docs45/classdocs/API_t3.html
          # Register a startup class by giving it a virtual name and
          # supplying its full pathname.
          #weblogic.system.startupClass.[virtual_name]=[full_pathname]
          # Add arguments for the startup class
          #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
          # This example shows the entry for examples/t3client/StartupQuery.java
          #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
          #weblogic.system.startupArgs.doquery=\
          # query=select * from emp,\
          # db=jdbc:weblogic:pool:demoPool
          # Other system startup files for use with VisiBroker
          # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
          # You must have installed Visigenic 2.5 for use with
          # the WebLogic Server before you uncomment these properties
          #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
          #weblogic.system.startupArgs.dovisi=\
          # clientName=T3Client Manager,\
          # connName=T3Connection Manager
          # SYSTEM SHUTDOWN FILES - Examples
          # For more info on writing and using shutdown file, see the
          # Developers Guide "Writing a WebLogic Client application," at
          # http://www.weblogic.com/docs45/classdocs/API_t3.html
          # Register a shutdown class by giving it a virtual name and
          # supplying its full pathname.
          #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
          # Add arguments for the shutdown class
          #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
          # This example shows the entry for examples/t3client/ShutdownTest.java
          #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
          #weblogic.system.shutdownArgs.ShutdownTest=\
          # outfile=c:/temp/shutdown.log
          # SECURITY-RELATED PROPERTIES FOR WORKSPACES
          # For backward compatibility, the following entries disable Access
          # Control on Workspaces
          weblogic.allow.read.weblogic.workspace=everyone
          weblogic.allow.write.weblogic.workspace=everyone
          # JOLT FOR WEBLOGIC PROPERTIES
          # These properties configure a BEA Jolt connection pool for use with
          # the simpapp and bankapp examples, and register a servlet for use with
          # with the simpapp example. The default server address provided here
          # points to a public TUXEDO server that is hosted by BEA for use with
          # this example.
          # Servlet registration for simpapp example:
          #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
          # Pool creation and cleanup
          # note this example is set up to work with the public
          # demo TUXEDO server available from BEA's website:
          #weblogic.system.startupClass.demojoltpoolStart=\
          # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
          #weblogic.system.startupArgs.demojoltpoolStart=\
          # poolname=demojoltpool,\
          # appaddrlist=//beademo1.beasys.com:8000,\
          # failoverlist=//beademo1.beasys.com:8000,\
          # minpoolsize=1,\
          # maxpoolsize=3
          #weblogic.system.shutdownClass.demojoltpoolStop=\
          # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
          #weblogic.system.shutdownArgs.demojoltpoolStop=\
          # poolname=demojoltpool
          # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
          # The registrations enable a BEA IIOP connection pool and
          # register servlets for use with the simpapp and university examples.
          # Configure for your environment and uncomment to use.
          # Uncommenting these properties requires WebLogic Enterprise
          Connectivity
          # and an operating WebLogic Enterprise Server.
          # Servlet registration for simpapp servlet example
          #weblogic.httpd.register.SimpappServlet=\
          # examples.wlec.servlets.simpapp.SimpappServlet
          #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
          # Servlet registration for simpapp EJB example
          # (You'll need to add the wlec_ejb_simpapp.jar to the
          # weblogic.ejb.deploy property in this file.)
          #weblogic.httpd.register.ejbSimpappServlet=\
          # examples.wlec.ejb.simpapp.ejbSimpappServlet
          #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
          # Pool creation and cleanup for the simpapp example
          #weblogic.CORBA.connectionPool.simplepool=\
          # appaddrlist=//wlehost:2468,\
          # failoverlist=//wlehost:2468,\
          # minpoolsize=2,\
          # maxpoolsize=3,\
          # username=wleuser,\
          # userrole=developer,\
          # domainname=simpapp
          # Servlet registration for university Servlet example:
          #weblogic.httpd.register.UniversityServlet=\
          # examples.wlec.servlets.university.UniversityServlet
          #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
          # Pool creation and cleanup for the University example:
          #weblogic.CORBA.connectionPool.Univpool=\
          # appaddrlist=//wlehost:2498,\
          # failoverlist=//wlehost:2498,\
          # minpoolsize=2,\
          # maxpoolsize=3,\
          # username=wleuser,\
          # userrole=developer,\
          # apppassword=wlepassword,\
          # domainname=university
          # WEBLOGIC FILE PROPERTIES
          # Maps a volume name to a path, for client file read/write
          #weblogic.io.fileSystem.[volumeName]=[fullPathName]
          # WEBLOGIC JMS DEMO PROPERTIES
          # CLUSTER USERS: Note that ALL JMS deployment should be done in the
          # per-cluster properties file ONLY.
          # You set up a JDBC connection pool if you want persistent messages
          # (including durable subscriptions). To use JMS and EJBs in the same
          # transaction, both must use the same JDBC connection pool. Uncomment
          # the following property to use the default JDBC connection pool
          # 'demo', which is defined in the Demo connection pool section of this
          file.
          #weblogic.jms.connectionPool=demoPool
          # The JMS Webshare example demonstrates how the ClientID for a
          # durable subscriber is configured in the connection factory:
          #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
          #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
          #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
          #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
          # The JMS trader example shows how to use JMS with an EJB. In addition
          # to uncommenting the following properties, you must also set up and
          # deploy the EJB example examples.ejb.basic.statefulSession.Trader to
          # try out this JMS example:
          #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
          #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
          #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
          #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
          # Registers the underlying servlet
          #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
          # These properties are used with the ServerReceive JMS example,
          # which demonstrates how to establish a JMS message consumer
          # in a startup class:
          #weblogic.system.startupClass.serverReceive=\
          # examples.jms.startup.ServerReceive
          #weblogic.system.startupArgs.serverReceive=\
          # connectionFactory=javax.jms.TopicConnectionFactory,\
          # topic=javax.jms.exampleTopic
          # These properties are used with the PoolReceive JMS example,
          # which demonstrates how to establish a pool of JMS message consumers
          # in a startup class:
          #weblogic.system.startupClass.poolReceive=\
          # examples.jms.startup.PoolReceive
          #weblogic.system.startupArgs.poolReceive=\
          # connectionFactory=javax.jms.TopicConnectionFactory,\
          # topic=javax.jms.exampleTopic
          # WEBLOGIC RMI DEMO PROPERTIES
          # CLUSTER USERS: Note that pinned RMI objects should be registered
          # in the per-server properties file ONLY. All other RMI startup
          # classes should be registered in the per-cluster properties file.
          # Remote classes registered at startup after the pattern:
          #weblogic.system.startupClass.[virtualName]=[fullPackageName]
          # These examples can be compiled to see RMI in action. Uncomment to use:
          #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
          #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
          # WEBLOGIC EJB DEMO PROPERTIES
          # CLUSTER USERS: Note that ALL EJB deployment should be done in the
          # per-cluster properties file ONLY.
          # See WebLogic Demo Connection Pool below for a connection pool
          # to use with these examples.
          # Deploys EJBeans. Uncomment the appropriate lines below and
          # modify DBMS-related info and paths to match your particular
          installation:
          #weblogic.ejb.deploy=\
          # d:/weblogic/myserver/cluster_ejb.jar, \
          # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
          # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
          # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
          # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
          # d:/weblogic/myserver/ejb_extensions_isModified.jar, \
          # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
          # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
          # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
          # d:/weblogic/myserver/ejb_subclass.jar, \
          # d:/weblogic/myserver/jolt_ejb_bankapp.jar
          # Servlets used by the EJB basic examples beanManaged and
          # containerManaged. Uncomment to use:
          #weblogic.httpd.register.beanManaged=\
          # examples.ejb.basic.beanManaged.Servlet
          #weblogic.httpd.register.containerManaged=\
          # examples.ejb.basic.containerManaged.Servlet
          # Add a list of users (set the password with
          weblogic.password.[username]=XXX)
          # to set an ACL for this servlet:
          #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
          #weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
          #weblogic.password.user1=user1Password
          #weblogic.password.user2=user2Password
          # WEBLOGIC ZAC DEMO PROPERTIES
          # These registrations enable the ZAC Publish Wizard.
          weblogic.zac.enable=true
          # Set the publish root for a WebLogic Server. Edit and
          # uncomment to use
          #weblogic.zac.publishRoot=d:/weblogic/zac
          # Set an ACL for each package you publish. The [name] is
          # the "Package name" you assign in the ZAC Publish Wizard.
          # Publish a package, edit this property, and uncomment to use.
          #weblogic.allow.read.weblogic.zac.[name]=[user list]
          #weblogic.allow.write.weblogic.zac.[name]=system
          # HTTPD ADMINISTRATIVE PROPERTIES
          # Enables logging of HTTPD info in common log format and
          # sets the log file name (default is "access.log" in "myserver")
          weblogic.httpd.enableLogFile=true
          weblogic.httpd.logFileName=access.log
          # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
          weblogic.httpd.enableEvents=false
          # Enables HTTP sessions
          weblogic.httpd.session.enable=true
          # Sets an optional cookie name. The default name is "WebLogicSession".
          # Prior to version 4.0, the default was "TengahSession". To make
          # this backward compatible with cookies generated from previous
          # installations, you should set this property to "TengahSession".
          # Uncomment this line and set this to any string of your choice,
          # or comment out this property to use the default.
          #weblogic.httpd.session.cookie.name=WebLogicSession
          # MIME types
          weblogic.httpd.mimeType.text/html=html,htm
          weblogic.httpd.mimeType.image/gif=gif
          weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
          weblogic.httpd.mimeType.application/pdf=pdf
          weblogic.httpd.mimeType.application/zip=zip
          weblogic.httpd.mimeType.application/x-java-vm=class
          weblogic.httpd.mimeType.application/x-java-archive=jar
          weblogic.httpd.mimeType.application/x-java-serialized-object=ser
          weblogic.httpd.mimeType.application/octet-stream=exe
          # In seconds, the keep-alive for HTTP and HTTPS requests
          weblogic.httpd.http.keepAliveSecs=60
          weblogic.httpd.https.keepAliveSecs=120
          # WEBLOGIC JDBC DRIVER PROPERTIES
          # Enables JDBC driver logging and sets the file name for the log
          # The weblogic.jdbc.logFile is placed in the per-server
          # directory (default is "myserver")
          weblogic.jdbc.enableLogFile=false
          weblogic.jdbc.logFileName=jdbc.log
          # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
          # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
          # in the per-cluster properties file ONLY.
          # For creating JDBC connection pools. This example shows a connection
          # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and
          "jill"
          # to use 4 JDBC connections (with a potential for up to 10 connections,
          # incremented by two at a time, with a delay of 1 second between each
          # attempt to connect to the database), to an Oracle database server
          called
          # "DEMO." If more than 4 connections are opened, after 15 minutes,
          unused
          # connections are dropped from the pool until only 4 connections remain
          open.
          # Every 10 minutes, any unused connections in the pool are tested and
          # refreshed if they are not viable.
          #weblogic.jdbc.connectionPool.oraclePool=\
          # url=jdbc:weblogic:oracle,\
          # driver=weblogic.jdbc.oci.Driver,\
          # loginDelaySecs=1,\
          # initialCapacity=4,\
          # maxCapacity=10,\
          # capacityIncrement=2,\
          # allowShrinking=true,\
          # shrinkPeriodMins=15,\
          # refreshMinutes=10,\
          # testTable=dual,\
          # props=user=SCOTT;password=tiger;server=DEMO
          # Get more details on each argument for this property in the
          # Administrators Guide on setting properties at:
          # http://www.weblogic.com/docs45/admindocs/properties.html
          # Set up ACLs for this connection pool with the following:
          #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
          # guest,joe,jill
          #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
          # joe,jill
          #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
          # joe,jill
          # This property is an ACL that specifies the users who can
          # create dynamic connection pools

Answer 1

Try the following obj.conf file. By the way why are using NES 35 version. If you are using NES 36 you should use proxy36.dll.
          Init fn="load-types" mime-types="mime.types"
          Init fn="load-modules" funcs="wl-proxy,wl-init" shlib="d:/weblogic/bin/proxy35.dll"
          Init fn="wl-init"
          Init access="C:/Netscape/SuiteSpot/https-octavia/logs/accessNewELF" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%
          \"%Req->headers.referer%\" \"%Req->headers.user-agent%\" %Req->reqpb.method% %Req->reqpb.uri% %Req->reqpb.query% \"%Req->reqpb.protocol%\"" fn="flex-init"
          <Object name="tg" ppath="*/weblogic/*">
          Service fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001" PathTrim="/weblogic"
          </Object>
          <Object name="default">
          NameTrans fn="pfx2dir" from="/ns-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
          NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
          NameTrans fn="pfx2dir" from="/help" dir="C:/Netscape/SuiteSpot/manual/https/ug"
          NameTrans fn="document-root" root="C:/Netscape/SuiteSpot/docs"
          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|POST|PUT)" type="text/jsp" fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001"
          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>
          <Object ppath="/usr/suitespot/docs/.perf">
          Service fn="service-dump"
          </Object>
          <Object name="cgi">
          ObjectType fn="force-type" type="magnus-internal/cgi"
          Service fn="send-cgi"
          </Object>
          Hope this helps
          Krishna Kanth wrote:
          > We are evaluating the Cluster features of WebLogic and got a eval
          > license for the Cluster Support.
          > I am running a default cluster (mycluster) using the default Multicast
          > address (237.0.0.1) and am seeing
          > some strange behaviour/errors.
          > Would appreciate some asistance in this matter.
          >
          > Our Environment
          > ----------------
          >
          > I created directory in a shared file system to host the cluster.
          > (h:\kkanth\weblogic)
          > Created the mycluster directory and other directories as recommended in
          > the Administrator's guide.
          >
          > I have two WL Servers (asera190 and asera162) with permanent IP
          > addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
          > I'm using a NES proxy on asera190 with the plugin for WL specified in
          > obj.conf alongwith the other parameters.
          >
          > I'm able to have both the servers join to cluster mycluster and the WL
          > Admin Console does display a tree that depicts the cluster as well as
          > servers in it (server61 and server70). The individual server directories
          > are being created in h:\kkanth\weblogic\mycluster directory with the
          > appropriate access.log and weblogic.log files.
          >
          > When a browser attempts to access a URL such as
          >
          > http://asera190/weblogic/snoop it does return the proper response, but
          > all requests are processed by asera162 which is listed first in the
          > obj.conf. Opening multiple sessions does not cause the requests to be
          > sent to asera190 which is the second server in the cluster. When
          > asera162 is shutdown and removed from the cluster, I hoped that
          > subsequent requests would go to asera190. However , depending on the
          > origin of the request, different errors were thrown. If I try to access
          > http://asera190/weblogic/snoop from a browser on asera190, I get an
          > error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
          > from asera162 cause "Failure at line 706 of file proxy.cpp".
          >
          > I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
          > directory as well as the obj.conf file in the ....\config\ directory of
          > asera190.
          >
          > We are running NES 3.5.1 and have setup proxy35.dll appropriately.
          >
          > weblogic.properties
          > *********
          > # THE WEBLOGIC PROPERTIES FILE
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # This file, which conforms to the java.util.Properties file
          > # definition, configures your WebLogic products. You cannot run
          > # WebLogic Server without setting required configuration properties in
          > this
          > # file. Required properties are marked and appear first in the file.
          > #
          > # Details on each entry and important information about configuration
          > # and security are documented on our website. Please go to:
          > #
          > # http://www.weblogic.com/docs45/admindocs/properties.html
          > #
          > # for full instructions on how to edit this file.
          > #
          > # You do not need to include properties in this file unless you want to
          > # change the default, embedded property. Some properties on the
          > # T3AdminProps page are not listed here because the default property
          > # is being used. You can change the default by adding the property and
          > # its value to this file.
          > #
          > # You cannot set weblogic.system.home in this file, since the WebLogic
          > Server
          > # must know where home is in order to retrieve this file. You can
          > # change WebLogic home on the command line when you start the
          > # WebLogic Server.
          > #
          > # CLUSTER USERS: Note that the (shared) per-cluster properties file
          > should
          > # contain most all of the properties in this file. The only properties
          > # that potentially belong in a per-server properties file for a server
          > # running in a cluster are the registration (startup class) of pinned
          > # RMI objects, and a few tuning properties that may be different for
          > # servers in the cluster, depending upon hardware and memory. If you use
          >
          > # a per-server properties file, please REMOVE all properties except
          > those
          > # that are specifically required in the per-server properties file. You
          > # can find specific notes on clusters by searching through this file for
          >
          > # "CLUSTER USERS".
          > #
          > # -------------------------------------------------
          > # The way this file is organized:
          > # Core properties (includes REQUIRED and RECOMMENDED)
          > # Core system properties
          > # Core security-related properties
          > # Core security-related properties for SSL
          > # Core HTTPD administrative properties
          > #
          > # Optional properties
          > # Administrator properties
          > # System properties
          > # System startup files
          > # System shutdown files
          > # Security-related properties for Workspaces
          > # Jolt for WebLogic properties
          > # WebLogic Enterprise Connectivity properties
          > # WebLogic File properties
          > # WebLogic JMS demo properties
          > # WebLogic RMI demo properties
          > # WebLogic EJB demo properties
          > # WebLogic ZAC demo properties
          > # HTTPD administrative properties
          > # WebLogic JDBC driver properties
          > # WebLogic JDBC connection pool management
          > # WebLogic demo connection pool
          > # WebLogic HTTP Servlet properties
          > # Proxy servlet registration
          > # Classpath servlet registration
          > # File servlet registration
          > # ServerSideInclude servlet registration
          > # PageCompileServlet (used by JHTML)
          > # JSPServlet (used by JSP)
          > # ServletServlet registration
          > # Servlet reload properties
          > # Servlet ACLs
          > # WebLogic JHTML properties
          > # User-written and demo servlet registrations
          > # -------------------------------------------------
          >
          > #################################################################
          > # CORE PROPERTIES
          > # -------------------------------------------------
          > # You should set these before you start the WebLogic Server the first
          > time.
          > # If you need more instructions on individual properties in this
          > # section, check the same section in the Optional Properties, where
          > # we've left the long explanations. Or, better yet, go to our
          > # website and read all about properties, at:
          > # http://www.weblogic.com/docs45/admindocs/properties.html
          > #################################################################
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # CORE SYSTEM PROPERTIES
          > # -------------------------------------------------
          > # TCP/IP port number at which the WebLogic Server listens for
          > connections
          > weblogic.system.listenPort=7001
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # CORE SECURITY-RELATED PROPERTIES
          > # -------------------------------------------------
          > # Read important information about security at:
          > #
          > # http://www.weblogic.com/docs45/admindocs/properties.html
          > #
          > # REQUIRED: The system password MUST be set in order to start the
          > # WebLogic Server. This password is case-sensitive, at least 8
          > characters.
          > # The username for the privileged user is ALWAYS "system".
          > # This username and password also includes httpd access (see
          > # HTTPD properties below).
          > weblogic.password.system=kaykayka
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # RECOMMEND Set to 'everyone' if HTTPD is enabled
          > weblogic.allow.execute.weblogic.servlet=everyone
          > # Set individual ACLs to restrict access to HTTP-related resources,
          > # such as the Administration servlets.
          > # To make your own servlets generally available, follow this
          > # pattern (provide a weblogic.allow.execute) for your packages and
          > # set ACLs as appropriate.
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # CORE SECURITY-RELATED PROPERTIES FOR SSL
          > # ------------------------------------------------
          > # Read important information about SSL at:
          > #
          > # http://www.weblogic.com/docs45/classdocs/API_secure.html
          > #
          > # Enable SSL
          > # (default if property not defined is false)
          > weblogic.security.ssl.enable=true
          > #
          > # SSL listen port
          > weblogic.system.SSLListenPort=7002
          >
          > # Servlets for SSL
          > # ------------------------------------------------
          > # Authentication servlet for creating tokens for applets
          > weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
          >
          > # Limits number of unclaimed stored tokens
          > weblogic.security.certificateCacheSize=3
          > # Capture CA root of client servlet
          > weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
          >
          > # Certificates for SSL
          > # ------------------------------------------------
          > # Name of acceptable CA roots
          > # For client authentication change value to a valid .pem file
          > #weblogic.security.clientRootCA=SecureServerCA.pem
          > #
          > # Server certificates for SSL
          > # ------------------------------------------------
          > weblogic.security.certificate.server=democert.pem
          > weblogic.security.key.server=demokey.pem
          > weblogic.security.certificate.authority=ca.pem
          >
          > # registration for certificate generator servlet
          > weblogic.httpd.register.Certificate=utils.certificate
          > weblogic.allow.execute.weblogic.servlet.Certificate=system
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # CORE HTTPD ADMINISTRATIVE PROPERTIES
          > # ------------------------------------------------
          > # True permits the HTTPD to run (default)
          > # Uncomment this property to disable HTTPD
          > #weblogic.httpd.enable=false
          > #
          > # If authentication is required, add username/password for each user
          > # who will be included in an ACL, as in this commented-out example:
          > #weblogic.password.peter=#8gjsL4*
          >
          > #################################################################
          > # OPTIONAL PROPERTIES
          > # ------------------------------------------------
          > # These properties affect the behavior of the WebLogic Server.
          > # You only need to set these properties if you want
          > # to change the default setting, which is the property shown.
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # ADMINISTRATOR PROPERTIES
          > # ------------------------------------------------
          > # Administrator properties are optional information properties,
          > # particularly useful for clusters.
          > #weblogic.administrator.location=3355 California Drive, West Hampshire,
          > CA 94104
          > #weblogic.administrator.name=Joe Administrator
          > #weblogic.administrator.phone=1 415 555 1234
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # SYSTEM PROPERTIES
          > # ------------------------------------------------
          > # System properties in this section are set to system defaults
          >
          > # Performance pack. The shared library must be accessible from your
          > # PATH (NT) or from your shared library path (UNIX; the name of the
          > # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
          > weblogic.system.nativeIO.enable=true
          >
          > # Outputs logging information to the console as well as to the log file
          > weblogic.system.enableConsole=true
          >
          > # Sets the directory or URL for the WebLogic Admin help pages
          > # The help pages are shipped in the "docs/adminhelp" directory, in the
          > # default document root in public_html
          > weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
          >
          > # If you prefer to access the most recent help pages, you can do so
          > online
          > # by commenting out the previous property and uncommenting this one:
          > #weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
          >
          > # Properties for tuning the server's performance
          > # ------------------------------------------------
          > # Number of WebLogic Server execute threads.
          > weblogic.system.executeThreadCount=15
          >
          > # Other optional system properties
          > # ------------------------------------------------
          > # Limits size of weblogic.log (in K) and versions old log
          > weblogic.system.maxLogFileSize=1024
          >
          > # Adjust minimum length of password
          > weblogic.system.minPasswordLen=8
          >
          > # UNIX only: If running on port 80 on UNIX, enable the setUID program
          > #weblogic.system.enableSetUID=false
          >
          > # UNIX only: Unprivileged user to setUID to after starting up
          > # WebLogic Server on port 80
          > #weblogic.system.nonPrivUser=nobody
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # CLUSTER-SPECIFIC PROPERTIES
          > # ------------------------------------------------
          > # Cluster-specific properties in this section are set to system
          > defaults.
          > # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
          >
          > # in the per-cluster properties file ONLY.
          > #
          > # Time-to-live (number of hops) for the cluster's multicast messages
          > # (default 1, range 1-255).
          > #weblogic.cluster.multicastTTL=1
          > #
          > # Sets the load-balancing algorithm to be used between
          > # replicated services if none is specified. If not specified,
          > # round-robin is used.
          > #weblogic.cluster.defaultLoadAlgorithm=round-robin
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # SERVER-SPECIFIC CLUSTER PROPERTIES
          > # ------------------------------------------------
          > # Cluster-related properties in this section are set to system defaults.
          >
          > # CLUSTER USERS: Note that these server-specific cluster-related
          > properties
          > # should be set in the per-server properties file ONLY.
          > #
          > # Sets the weight of the individual server for the weight-based
          > load-balancing.
          > # Range is 0 - 100.
          > # Larger numbers increase the amount of traffic routed to this server.
          > #weblogic.system.weight=100
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # SYSTEM STARTUP FILES - Examples
          > # ------------------------------------------------
          > # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
          > # objects should be registered in the per-server properties file.
          > # All other startup classes should be registered in the per-cluster
          > # properties file.
          > #
          > # For more info on writing and using startup file, see the
          > # Developers Guide "Writing a WebLogic Client application," at
          > # http://www.weblogic.com/docs45/classdocs/API_t3.html
          > #
          > # Register a startup class by giving it a virtual name and
          > # supplying its full pathname.
          > #weblogic.system.startupClass.[virtual_name]=[full_pathname]
          > #
          > # Add arguments for the startup class
          > #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
          > #
          > # This example shows the entry for examples/t3client/StartupQuery.java
          > #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
          > #weblogic.system.startupArgs.doquery=\
          > # query=select * from emp,\
          > # db=jdbc:weblogic:pool:demoPool
          > #
          > # Other system startup files for use with VisiBroker
          > # ------------------------------------------------
          > # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
          > # You must have installed Visigenic 2.5 for use with
          > # the WebLogic Server before you uncomment these properties
          > #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
          >
          > #weblogic.system.startupArgs.dovisi=\
          > # clientName=T3Client Manager,\
          > # connName=T3Connection Manager
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # SYSTEM SHUTDOWN FILES - Examples
          > # ------------------------------------------------
          > # For more info on writing and using shutdown file, see the
          > # Developers Guide "Writing a WebLogic Client application," at
          > # http://www.weblogic.com/docs45/classdocs/API_t3.html
          > #
          > # Register a shutdown class by giving it a virtual name and
          > # supplying its full pathname.
          > #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
          > #
          > # Add arguments for the shutdown class
          > #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
          > #
          > # This example shows the entry for examples/t3client/ShutdownTest.java
          > #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
          >
          > #weblogic.system.shutdownArgs.ShutdownTest=\
          > # outfile=c:/temp/shutdown.log
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # SECURITY-RELATED PROPERTIES FOR WORKSPACES
          > # ------------------------------------------------
          > # For backward compatibility, the following entries disable Access
          > # Control on Workspaces
          > weblogic.allow.read.weblogic.workspace=everyone
          > weblogic.allow.write.weblogic.workspace=everyone
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # JOLT FOR WEBLOGIC PROPERTIES
          > # ------------------------------------------------
          > # These properties configure a BEA Jolt connection pool for use with
          > # the simpapp and bankapp examples, and register a servlet for use with
          > # with the simpapp example. The default server address provided here
          > # points to a public TUXEDO server that is hosted by BEA for use with
          > # this example.
          > #
          > # Servlet registration for simpapp example:
          > # ------------------------------------------------
          > #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
          >
          > #
          > # Pool creation and cleanup
          > # note this example is set up to work with the public
          > # demo TUXEDO server available from BEA's website:
          > # ------------------------------------------------
          > #weblogic.system.startupClass.demojoltpoolStart=\
          > # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
          > #weblogic.system.startupArgs.demojoltpoolStart=\
          > # poolname=demojoltpool,\
          > # appaddrlist=//beademo1.beasys.com:8000,\
          > # failoverlist=//beademo1.beasys.com:8000,\
          > # minpoolsize=1,\
          > # maxpoolsize=3
          > #
          > #weblogic.system.shutdownClass.demojoltpoolStop=\
          > # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
          > #weblogic.system.shutdownArgs.demojoltpoolStop=\
          > # poolname=demojoltpool
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
          > # ------------------------------------------------
          > # The registrations enable a BEA IIOP connection pool and
          > # register servlets for use with the simpapp and university examples.
          > # Configure for your environment and uncomment to use.
          > # Uncommenting these properties requires WebLogic Enterprise
          > Connectivity
          > # and an operating WebLogic Enterprise Server.
          > #
          > # Servlet registration for simpapp servlet example
          > # ------------------------------------------------
          > #weblogic.httpd.register.SimpappServlet=\
          > # examples.wlec.servlets.simpapp.SimpappServlet
          > #
          > #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
          > #
          > # Servlet registration for simpapp EJB example
          > # (You'll need to add the wlec_ejb_simpapp.jar to the
          > # weblogic.ejb.deploy property in this file.)
          > # --------------------------------------------
          > #weblogic.httpd.register.ejbSimpappServlet=\
          > # examples.wlec.ejb.simpapp.ejbSimpappServlet
          > #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
          > #
          > # Pool creation and cleanup for the simpapp example
          > # -------------------------------------------------
          > #weblogic.CORBA.connectionPool.simplepool=\
          > # appaddrlist=//wlehost:2468,\
          > # failoverlist=//wlehost:2468,\
          > # minpoolsize=2,\
          > # maxpoolsize=3,\
          > # username=wleuser,\
          > # userrole=developer,\
          > # domainname=simpapp
          > #
          > # Servlet registration for university Servlet example:
          > # ---------------------------------------------------
          > #weblogic.httpd.register.UniversityServlet=\
          > # examples.wlec.servlets.university.UniversityServlet
          > #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
          > #
          > # Pool creation and cleanup for the University example:
          > # ----------------------------------------------------
          > #weblogic.CORBA.connectionPool.Univpool=\
          > # appaddrlist=//wlehost:2498,\
          > # failoverlist=//wlehost:2498,\
          > # minpoolsize=2,\
          > # maxpoolsize=3,\
          > # username=wleuser,\
          > # userrole=developer,\
          > # apppassword=wlepassword,\
          > # domainname=university
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # WEBLOGIC FILE PROPERTIES
          > # ------------------------------------------------
          > # Maps a volume name to a path, for client file read/write
          > #weblogic.io.fileSystem.[volumeName]=[fullPathName]
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # WEBLOGIC JMS DEMO PROPERTIES
          > # -------------------------------------------------
          > # CLUSTER USERS: Note that ALL JMS deployment should be done in the
          > # per-cluster properties file ONLY.
          > #
          > # You set up a JDBC connection pool if you want persistent messages
          > # (including durable subscriptions). To use JMS and EJBs in the same
          > # transaction, both must use the same JDBC connection pool. Uncomment
          > # the following property to use the default JDBC connection pool
          > # 'demo', which is defined in the Demo connection pool section of this
          > file.
          > #
          > #weblogic.jms.connectionPool=demoPool
          > #
          > # The JMS Webshare example demonstrates how the ClientID for a
          > # durable subscriber is configured in the connection factory:
          > #
          > #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
          > #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
          >
          > #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
          > #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
          > #
          > # The JMS trader example shows how to use JMS with an EJB. In addition
          > # to uncommenting the following properties, you must also set up and
          > # deploy the EJB example examples.ejb.basic.statefulSession.Trader to
          > # try out this JMS example:
          > #
          > #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
          > #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
          > #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
          > #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
          > #
          > # Registers the underlying servlet
          > #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
          > #
          > # These properties are used with the ServerReceive JMS example,
          > # which demonstrates how to establish a JMS message consumer
          > # in a startup class:
          > #
          > #weblogic.system.startupClass.serverReceive=\
          > # examples.jms.startup.ServerReceive
          > #weblogic.system.startupArgs.serverReceive=\
          > # connectionFactory=javax.jms.TopicConnectionFactory,\
          > # topic=javax.jms.exampleTopic
          > #
          > # These properties are used with the PoolReceive JMS example,
          > # which demonstrates how to establish a pool of JMS message consumers
          > # in a startup class:
          > #weblogic.system.startupClass.poolReceive=\
          > # examples.jms.startup.PoolReceive
          > #weblogic.system.startupArgs.poolReceive=\
          > # connectionFactory=javax.jms.TopicConnectionFactory,\
          > # topic=javax.jms.exampleTopic
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # WEBLOGIC RMI DEMO PROPERTIES
          > # ------------------------------------------------
          > # CLUSTER USERS: Note that pinned RMI objects should be registered
          > # in the per-server properties file ONLY. All other RMI startup
          > # classes should be registered in the per-cluster properties file.
          > #
          > # Remote classes registered at startup after the pattern:
          > #weblogic.system.startupClass.[virtualName]=[fullPackageName]
          > #
          > # These examples can be compiled to see RMI in action. Uncomment to use:
          >
          > #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
          >
          > #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # WEBLOGIC EJB DEMO PROPERTIES
          > # -------------------------------------------------
          > # CLUSTER USERS: Note that ALL EJB deployment should be done in the
          > # per-cluster properties file ONLY.
          > #
          > # See WebLogic Demo Connection Pool below for a connection pool
          > # to use with these examples.
          > #
          > # Deploys EJBeans. Uncomment the appropriate lines below and
          > # modify DBMS-related info and paths to match your particular
          > installation:
          > #weblogic.ejb.deploy=\
          > # d:/weblogic/myserver/cluster_ejb.jar, \
          > # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
          > # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
          > # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
          > # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
          > # d:/weblogic/myserver/ejb_extensions_isModified.jar, \
          > # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
          >
          > # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
          > # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
          > # d:/weblogic/myserver/ejb_subclass.jar, \
          > # d:/weblogic/myserver/jolt_ejb_bankapp.jar
          > #
          > # Servlets used by the EJB basic examples beanManaged and
          > # containerManaged. Uncomment to use:
          > #weblogic.httpd.register.beanManaged=\
          > # examples.ejb.basic.beanManaged.Servlet
          > #weblogic.httpd.register.containerManaged=\
          > # examples.ejb.basic.containerManaged.Servlet
          > #
          > # Add a list of users (set the password with
          > weblogic.password.[username]=XXX)
          > # to set an ACL for this servlet:
          > #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
          > #weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
          >
          > #weblogic.password.user1=user1Password
          > #weblogic.password.user2=user2Password
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # WEBLOGIC ZAC DEMO PROPERTIES
          > # -------------------------------------------------
          > # These registrations enable the ZAC Publish Wizard.
          > #
          > weblogic.zac.enable=true
          > #
          > # Set the publish root for a WebLogic Server. Edit and
          > # uncomment to use
          > #
          > #weblogic.zac.publishRoot=d:/weblogic/zac
          > #
          > # Set an ACL for each package you publish. The [name] is
          > # the "Package name" you assign in the ZAC Publish Wizard.
          > # Publish a package, edit this property, and uncomment to use.
          > #weblogic.allow.read.weblogic.zac.[name]=[user list]
          > #weblogic.allow.write.weblogic.zac.[name]=system
          >
          > # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
          > # HTTPD ADMINISTRATIVE PROPERTIES
          > # ------------------------------------------------
          > # Enables logging of HTTPD info in common log format and
          > # sets the log file name (default is "access.log" in "myserver")
          > weblogic.httpd.enableLogFile=true
          > weblogic.httpd.logFileName=access.log
          >
          > # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
          > weblogic.httpd.enableEvents=false
          >
          > # Enables HTTP sessions
          > weblogic.httpd.session.enable=true
          >
          > # Sets an optional cookie name. The default name is "WebLogicSession".
          > # Prior to version 4.0, the default was "TengahSession". To make
          > # this backward compatible with cookies generated from previous
          > # installations, you should set this property to "TengahSession".
          > # Uncomment t