Cisco Cisco UCS B440 M1 High-Performance Blade Server Weißbuch
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 78 of 83
c) In broweser-starter.war edit the context root to /browser-starter
d) On Medrec Overview tab , edit the Deployment Order to “1”
e) Ensure all targets point to previously created cluster
4) Start the application . Presently we can access the application to each of the configrd
Weblogic Cluster. In next section we would use Apache HTTP Server with Weblogic HTTP plugin and
define the cluster configuration
When the Oracle WebLogic Cluster is configured, interface it with Apache 2.2 HTTP Server by using Apache HTTP
Server Plug-in for WebLogic 10.3.5.
4.5.5 Apache HTTP Server Plug-in
Apache HTTP Server Plug-In allows requests to be routed from an Apache HTTP Server to WebLogic Cluster.The
plug-in is intended for use in an environment where an Apache Server serves static pages, and dynamic part of
web-page (HTTP Servlets or JSP's) is delegated to WebLogic Server, which may be operating in a different
process, possibly on a different host.
Tasks #
Task Description
1.
Copy the Apache2.2-WebLogic (mod_wl_22.so) plug-in from
$WL_HOME/server/plugin/linux/x86_64 to $Apache_Home/modules
$WL_HOME/server/plugin/linux/x86_64 to $Apache_Home/modules
2.
Edit $Apache_Home/conf/httpd.conf with following parameters:
#Load WebLogic plug-in module
LoadModule WebLogic_module modules/mod_wl_22.so
# SetHandler specifies the handler for the Apache HTTP Server Plug-In module
.Presently we have are proxing all request to WebLogic.
<Location /medrec>
We have clustered WebLogic MedRec application and defined the
loation
SetHandler WebLogic-handler
</Location>
# Add an IfModule block that defines WebLogic Cluster
<IfModule mod_WebLogic.c>
WebLogicCluster MServer_1:7003,MServer_2:7004,MServer_01:7001,MServer_02:7004
</IfModule>
3.
Restart apache, and we have a Apache 2.2 proxying requests to Oracle WebLogic
Cluster. Access
Cluster. Access
http://<Apache-Server>/medrec/
to ensure that you can access the
clustered application.
4.6 Cisco UCS Statelessness
As elaborated in the previous sections, Cisco Unified Computing System enables data center servers to be
stateless, for example a server’s identity (using MAC or WWN addressing or UIDs) as well as build and operational
policy information such as firmware and BIOS revisions and network and storage connectivity profiles can be
dynamically provisioned or migrated to any physical server in the system.
Cisco UCS Service profiles, in combination with the stateless nature of Cisco Unified Computing System servers,
provide the underlying mechanism that allows the use of a common pool of spare servers that can be quickly
repurposed for nearly any requirement. For most organization and applications, this feature can result in an
immediate reduction in capital expenditures (CapEx) because required spare and overflow capacity can be shared