Slides from the presentation I first gave in Dublin on 21/3/12 at the OUG Ireland conference

1. WebLogic for DBAs
Simon Haslam
Veriton Limited
1 (1.0)

2. Simon Haslam / Veriton
Consultant & Oracle Partner,
established for 15 years
I mainly work on demanding web &
contact-centre applications
Architecture planning to installation Middle
Admin ware
to troubleshooting (and most things istrati
on
in between!)
2 (1.0)

3. Agenda
1. WebLogic Architecture and Components
2. Installing WLS & Configuring a Domain
3. Oracle Enterprise Manager – 11g & 12c
4. Managing WebLogic

4. Recap.
HTTP(S)
HTTP(S)
used
Web Server to return
HTML
HTTP(S), AJP etc
Application Server
e.g. SQL*Net
Database etc
4 (1.0)

5. Key WebLogic Terms
• Domain
– Grouping of config/resources for an environment
– Has one set of administrators/security privileges
– Can be in Production or Development mode
• Admin Server
– Only one per domain
– Runs the Admin Console
– Can be relocated for HA
• Managed Server
– The server(s)/JVM that run your app(s)
– Cluster(s) distribute your app over several MS
• Node Manager
– Small java program that (re)starts your servers (MS & AS)
5 (1.0)

6. Example Architecture
machine node
manager
app managed
requests webserver server
plug-in managed
server admin
console
machine
admin
server
managed
server
domain node
manager
END
6 (1.0)

7. Component Notes
• A domain only ever has one admin server
– it looks after the master config.xml
• The admin server doesn’t actually need to
be running all the time
– Managed Server Independence – the MS can
start up/run on its own
– AS primarily used for changing configuration
or deploying apps
• You want Node Manager running all the
time to stop/start WebLogic servers
7 (1.0)

8. Quick Demo
• WebLogic Console
– machines
– servers
– data sources
– deployed applications
8 (1.0)

9. Typical Enterprise Application
Load Balancers
Web Server Web Server
WebLogic WebLogic
App App
Managed Server Managed Server
Cluster
Oracle Database Web
Web
(RAC and/or DG) Services
Services
Services Layer
9 (1.0)

10. Enterprise Manager GC/CC
• Actually a fairly straightforward java
application
• Runs an Oracle Management Service (OMS)
which OEM Agents (server processes
running on remote machines you want to
manage) connect to over HTTPS
• Has a web application that provides the
main EM console
10 (1.0)

11. EM Grid/Cloud Control (HA)
Load Balancer
Web Server Web Server
OMS OMS
1 2
WebLogic WebLogic
EMGC_OMS1 EMGC_OMS2
Managed Server Managed Server
Repository Database My
My
(DG and/or RAC) Oracle
Oracle
Support
Support
Services Layer
11 (1.0)

12. Agenda
1. WebLogic Architecture and Components
2. Installing WLS & Configuring a Domain
3. Oracle Enterprise Manager – 11g & 12c
4. Managing WebLogic

13. Install
• Middleware Home
– ‘binaries’ which may include various Oracle
layered products (such as SOA Suite or Forms)
– read-only*
• Domain Home
– configuration and logs
– can live happily outside the middleware home:
nice!
– one middleware home / WebLogic installation
can be used to run several separate domains
* a few parts of Oracle ignore this
13 (1.0)

14. WebLogic Installation Steps
1. Install JVM (typically JRockit)
2. Install a Middleware Home and WebLogic
3. Configure a Domain
• Note: I usually install the JVM and use the
generic .jar installer (i.e. same for all
platforms) rather than using installer
bundled with a JVM
14 (1.0)

15. 1) Install JVM
• Sun HotSpot or JRockit (will converge), or
JVM for your platform (e.g. IBM)
• JRockit specific:
– don’t install demos & samples/source code
– Windows latest – you probably don’t want
JRockit as the public JRE
15 (1.0)

16. 2) Install WebLogic
• e.g. java -jar wls1036_generic.jar
• Only most relevant screens follow…
16 (1.0)

17. 17 (1.0)

18. 18 (1.0)

19. 3) Configure a Domain
• You use the config wizard to create domains
– $WL_HOME/common/bin/config.sh (.cmd)
– there are several other methods too
• There’s a good chance your app will
configure a domain for you (though you
may wish to standardise)
• Only most relevant screens follow…
19 (1.0)

20. 20 (1.0)

21. 21 (1.0)

22. 22 (1.0)

23. Agenda
1. WebLogic Architecture and Components
2. Installing WLS & Configuring a Domain
3. Oracle Enterprise Manager – 11g & 12c
4. Managing WebLogic

24. OEM Grid Control 11g
• 11g GC was first OEM release to use
WebLogic instead of OC4J
• You had to install WebLogic yourself first,
then use SmartUpdate (BSU) to apply
WDJ7 set of patches
– online or offline
– see http://www.veriton.co.uk/roller/fmw/entry/
offline_patching_of_weblogic_server
• If you’re installing now you’ll probably go
straight to EM 12c ☺
24 (1.0)

25. 25 (1.0)

26. EM 12c – most relevant screens
26 (1.0)

27. 27 (1.0)

28. Note: this is the current list of plug-ins for
12.1 BP1 but will probably increase over time
28 (1.0)

29. Configure
29 (1.0)

30. 30 (1.0)

31. 32 bit Gotcha!
• If you’re installing on Oracle Linux 5.7 see:
https://forums.oracle.com/forums/thread.jspa?
messageID=10220015
• Need to lower memory usage in
<ORACLE_HOME>/oms/sysman/omsca/scripts/
wls/create_domain.py
• You wouldn’t use 32 bit in production now
but may do for laptop or lab VM
31 (1.0)

32. Agenda
1. WebLogic Architecture and Components
2. Installing WLS & Configuring a Domain
3. Oracle Enterprise Manager – 11g & 12c
4. Managing WebLogic

33. 33 (1.0)

34. Managing WebLogic
• Admin console is usually starting point
• Processes to check
– java for admin server & managed server
– java for nm
• Node manager (only use java version)
• Log files…
34 (1.0)

35. Log Files
• Managed server logs are under:
– DOMAIN_HOME/servers/<name>/logs
– Accessible through console too
• Diagnostics
• Console monitor
35 (1.0)

36. Quick Demo
• Processes
• Log files
36 (1.0)

37. WLST Example
def create_ds(DS_NAME, DS_PARAMS, TARGETS, JNDI, DB_USER, DB_PASS,
DB_SERVICE, DB_HOSTS, ONS_HOSTS):
cd('/')
cmo.createJDBCSystemResource(DS_NAME)
cd('/JDBCSystemResources/'+DS_NAME+'/JDBCResource/'+DS_NAME)
cmo.setName(DS_NAME)
cd('JDBCDataSourceParams/'+DS_NAME)
set('JNDINames',jarray.array([String(JNDI)], String))
...etc...
37 (1.0)

38. 38 (1.0)

39. • WebLogic is a java application server
– typically delivers HTML over HTTP(S)
• All WLS processes run on a JVM
• Middleware home is static, domain home contains
config and logs
• WLS Console is usually first point of contact
(though don’t forget about WLST for automation)
• OEM 12c runs on WebLogic but the installer now
does the WLS set up work for you
39 (1.0)

40. Thanks for listening!
Twitter: @simon_haslam
Oracle Fusion Middleware Admin blog:
http://simonhaslam.co.uk
40 (1.0)