Also after our meeting with Stellent they have told us about another testing tool which gives more comprehensive results. It too is opensource from sourceforge (probably java..) http://www.opensta.org/, but have not yet had time to fully test it.
The value List Handler is a J2EE design pattern to limit the number of results to a page or 'pagination':
http://java.sun.com/blueprints/corej2eepatterns/Patterns/ValueListHandler.html
¶ 4:52 pm
LoadModule weblogic_module modules/mod_wl_20.so
WebLogicCluster localhost:7010,localhost:7011
MatchExpression *
This will load balance between the two given clustered services and redirect all page requests.
When you compare application servers, you are just comparing J2EE implementations and if all you need is a J2EE implementation then you can probably use an open source application server. But BEA's customers need much more than that. The J2EE implementation is just the "surface" of an application server.
Once you start a J2EE development project, the application server you use will determine how fast you can do your edit-compile-debug cycle. It will determine how easy it is to move you J2EE application from development to staging to production. Once you need to deploy, operate and maintain your J2EE application, your J2EE application server plays an even bigger role. It determines how easy it is to update the application, how easy it is to scale up and down (if possible at all), and it determines how much visibility you have into the operation of your application.
All of these things add up to much more than the cost of just writing the code. In fact, the costs of maintaining application lifecycle and of managing a runtime environment easily dwarves the costs of the software you are using.
Taken from http://indicthreads.com/content/view/228/0/1/3/
¶ 9:57 am
The server list basically says what servers as up and down in the cluster (updated on each request) – if you point this to more than one cluster you can see that you might get proxied to a server that you shouldn’t (unless u make the wls urls unique for each cluster).
<VirtualHost 192.168.5.42:80 >
ServerName 192.168.5.42
ErrorLog /opt/logs/apache/lsp/error_log
CustomLog /opt/logs/apache/lsp/access_log common
<Location /LSPPortalWeb>
SetHandler weblogic-handler
</Location>
<Location /cafe-webapp>
SetHandler weblogic-handler
</Location>
<Location /console>
SetHandler weblogic-handler
</Location>
<Location /NHSLspAdmin>
SetHandler weblogic-handler
</Location>
<IfModule mod_weblogic.c>
WebLogicHost 192.168.6.66
WebLogicPort 1201
</IfModule>
</VirtualHost>
<VirtualHost 192.168.30.77:80 >
ServerName 192.168.30.77
ErrorLog /opt/logs/apache/adent/error_log
CustomLog /opt/logs/apache/adent/access_log common
<Location /Ardentia>
SetHandler weblogic-handler
</Location>
<IfModule mod_weblogic.c>
WebLogicHost 192.168.6.155
WebLogicPort 1201
</IfModule>
</VirtualHost>
<VirtualHost *:3700 >
# try changing this to <VirtualHost 155.231.138.200:3700>
ServerName 192.168.5.42
ErrorLog /opt/logs/apache/lsp/NCRSerror_log
CustomLog /opt/logs/apache/lsp/NCRSaccess_log common
<Location /NCRSNotification-web>
SetHandler weblogic-handler
</Location>
<IfModule mod_weblogic.c>
WebLogicHost 192.168.6.66
WebLogicPort 1201
</IfModule>
</VirtualHost>
