Friday, April 29

JDBC (Java DataBase Connectivity ) in Oracle WebLogic - Overview

How to connect to Database from Oracle WebLogic Server :
You first create JDBC Datasource (or multi data sources) and then deploy this JDBC datasource (or multi datasource) to WebLogic Server (or cluster) in Domain.
Datasource: contains pool of database connections that are created when datasource instance is created i.e.
a) When it is deployed or targeted
or
b) Server start-up
Multi Datasource : Abstraction around data source to provide load balancing or failover for datasource which are part of Multi Datasource.
.
Who can create JDBC Resource - Administrator or Programmer
How a JDBC resource is created - Using
i) Administration Console (by Administrator)
ii) WLST (WebLogic Scripting Tool)  (by Administrator)
iii) by Programmatically using JMX API (by Developer)
System v/s Application JDBC Module - JDBC Modules created by Administrator using Console or WLST are called as System JDBC module where as JDBC module created by developer using WebLogic Workshop, other IDE (Integrated Development Environment) or XML editor are called as Application JDBC Module.
How JDBC Datasource is stored on server - as XML File under $DOMAIN/config/jdbc directory. i.e. $WEBLOGIC_HOME/ user_projects/ domains/ [domain_name]/ config/ jdbc/
config.xml file in “$WEBLOGIC_HOME/user_projects/domains/[domain_name]/config” points to JDBC datasource configuration file via parameter jdbc-system-resource
sample entry in config.xml
 
    JDBC1
    AdminServer
    jdbc/JDBC1-1894-jdbc.xml
 
which means JDBC configuration file is at “$WEBLOGIC_HOME/ user_projects/ domains/ [domain_name]/ config/ jdbc/ JDBC1-1894-jdbc.xml



WebLogic Server JDBC for Database connection : Step by Step

This is in continuation of my last post on Database Connectivity (JDBC) in WebLogic Server here , In today’s post I am going to cover step by step JDBC configuration using Administration Console.
1. Login to WebLogic Server Administration console (default port 7001)
http://hostname:port/console
2. Select Data Sources under JDBC in Services section
.
.
3. Click on New button on right side as shown above
4. Enter JDBC Name, JNDI Name, Database & Driver type as shown below
.
. 
5. In next screen, enter database connection pool details i.e.
Database Name
Host Name (on which database is running)
– PortNumber (on which database listener is listening)
Database User Name
&
Password (for database user)
. 
6. In next screen you test connection by clicking on “Test Configuration” as shown below
.
. 
7.Finally you select target servers (Administration and Managed Server in that domain) for that Datasource.
. 
8. On clicking Finish button, you should see datasource as listed below
To create Multi Datasource
Steps mentioned above are to create single Datasource. To create Multi Datasource first create two or more Datasource as mentioned above (I created JDBC1 & JDBC2)  then select Multi Datasources from console as shown below
.
2. Click on New button above, In next screen select Name of Multi Datasource and JNDI
.
.
3. Select Algorithm Typefor Multi Datasource i.e. Failover or Load Balancing
4. Select Datasource which you want to make part of Multi Datasource as shown below 
.
5. Finally click on Finish to see Multi Data Sources

 

 


Console deployment

Click here to view console deployment. 

Console deployment Video

Deploy Application on Oracle WebLogic Server

Things good to know before deploying application on Oracle WLS 
i) User with Admin or Deployer role can deploy application
ii) Weblogic supports following type of deployment unit
a) EAR file (Enterprise Archive)
b) WAR file (Web Archive)
c) JAR files, EJB (Enterprise Java Beans)
d) RAR (Resource Adapter/Connector )
e) Web Services (WAR/JAR)
f) J2EE Library
g) CAR (Client Application Archive)
–  Web Archive configuration file is usually …../WEB-INF/web.xml
–  Enterprise Application (EAR) configuration file is usually …/META-INF/application.xml
iii) Application name can contain only following character (a-z, A-Z, 0-9, underscore, hyphen, . period/dot)
iv) Application name with only period/dot (like . or .. or …) is not valid name, it should contain at least one other character.
v) Application Name should be 215 character or less
.
Tools used to deploy/configure applications
1) weblogic.Deployer - command line interface
2) Administration Console - Web based interface
3) WLST(WebLogic Scripting Tool) - command line tool to automate deployment configuration and operation
4) Tool for developers (wldeploy, weblogic.PlanGenerator, API, autodeploy)
.
Steps to Deploy Application using Administration Console
In this post I’ll cover steps to deploy application using Administration Console
Download Sample Application from here  use this file to deploy on WebLogic Server.
1. Start Administration Console if its not Up already (In my case Administration Server is listening on port 7001)
deployment 2
2) Access Administration console using URL http(s):// :/console 
3) Login using User (with admin or deployer role)  weblogic in my case
4) First step is to acquire Lock as shown in screen

5) Click on deployment

6) Click on Install button

7) Select Application (war, jar, ear) File . You should get this application (war, ear, jar) file from development team.

8) Select Install this deployment as Application and click Next


9) Activate Canges by clicking on button on left as shown in screen

10) Start Application by clicking on Start Button


.

Oracle WebLogic Server - Startup/Shutdown

There are multiple ways to start WebLogic Server(listed below). This post covers WebLogic Startup/Shutdown  using scripts.  Start WebLogic using Node Manager, WLST (WebLogic Scripting Tool) or other tools coming soon …
                        There are two type of WebLogic Server instance in a domain, Administration Server and Managed Server.
You can start Managed Server without Administration Server with exception for first time. If you are starting Managed Server for first time]then Administration Server should be Up. Managed Server can cache config files locally(in its local config directory) and later Managed Server can start on its own.
To start Managed Server using script, supply Admin Server protocol, Server Name and Listen Port(check startup command for more information).
If startup mode of domain is “production” then startup will prompt you for username & password to start services (You can create define username/password in boot.properties file. Coming soon !!!).
If you create domain and startup mode is “development” then startup will not prompt for username/password as username password are stored in boot identity file in security directory of Domain at BEA_HOME / user_projects / domains / / servers/ / security / boot.properties
 
.
Ways to start Administration Serverin Oracle WebLogic
1.Using startup script
2. From Windows Start Menu (windows only)
3. Using “java weblogic.Server” command
4. Using WLST (WebLogic Scripting Tool) and Node Manager
5. Using WLST without Node Manager
.
Ways to start Managed Serverin Oracle WebLogic 
1.Using startup script
2. Using Administration Console
3. Using WLST and Node Manager
4. Using “java weblogic.Server” command
 .
1. Starting Administration Server (startWebLogic.cmd or .sh)
2. Starting Managed Server (startManagedWebLogic.sh or .cmd)
.
A. To Start WebLogic Administration Server Instance
Go to domain for which you wish to start Administration Server
cd $BEA_HOME/user_projects/domains//bin
startWebLogic.cmd (for Windows)
startWebLogic.sh (for Unix)
confirm that WebLogic Adminstration Server started properly by looking at message “Service started RUNNING mode“. Log file in below picture shows that AdminSever is listening on Port 7001 and all IP addresses on specific machine.
start WebLogic
Startup/Shutdown Log file can be found at $BEA_HOME/ user_projects/ domains/ /servers/ /logs / .log
.
B. Start Managed Server Instance
If you created Managed Server while creating domain then you can start Managed Server using startManagedWebLogic command
$BEA_HOME/user_projects/domains//bin
startManagedWebLogic.cmd (for Windows)
startManagedWebLogic.sh  (for Unix)
I created Managed Server MS1 with Admin Port as 7003
startManagedWebLogic.cmd ms1 http://localhost:7003 (Windows)
.
References

Create Domain in Oracle WebLogic

After WebLogic installation Here, next step is to create Domain. This post cover steps to create Domain in WebLogic (Simple - Administration Server or Advanced - one Administration Server and two Managed Server in a Cluster). If you are not familiar with Domain, Administration/Managed Server or Cluster then read my post here my post here   or Oracle Documentation here
  There are multiple ways to create domain, steps mentioned here are using Configuration Manager Wizard (config.sh or config.cmd).
–For Unix/Windows start configuration wizard using $BEA_HOME/ wlserver_10.0/ commom/ bin/ config.cmd (windows) or config.sh(UNix)
–To Start configuration wizard in console mode use - config.[cmd|sh] -mode=console
Screenshot below for creating Domain in WebLogic using Configurtaion Manager in GUI mode. Start Configuration Manager using command given above (config.sh / config.cmd)
1) Create or Extend Domain - In First screen you select if you wish to Create new WebLogic Domain or Extend an Existing WebLogic Domain.
   Extending WebLogic Domainmeans you already have WebLogic Domain and want to add more Managed Server or configure cluster or configure additional applications.
weblogic 4
2) Select Domain Source
weblogic 5
3) Configure Administrator - In below screen you define UserName and Password for WebLogic Domain and add/grant Administrator Role to that User (This user name /password will be used to start/stop domain if Mode of domain is Production and to login to domain Admin WebConsole)
weblogic 6
4) Select JDK & Start Mode -  In below screen, you define Mode in which you wish to start your domain and JDK (Sun, JRockit or any other JDK)
Production Mode- Domain is more secure, You need username password to start domain or deploy application.
Development Mode- Not very secure, You can Autodeploy application and no need to provide username/password to start Domain.
weblogic 7
5) Customize your domain -  Using below screen you can customize your domain (Create Managed Server, Cluster, JDBC Source, JMS File Store). Select initially No to create simple domain with Just one Administration Server (You can deploy your application in Administration Server but this is not recommended in Production Instance).
  To create Advanced Domain (one Administration Server and two Managed Server and Cluster) go to Step  8 )
weblogic 8
6) In next screen you provide Domain Name, Location of Domain.
weblogic 9
7) Finally, If you are installing on Windows, you can select to “Start Admin Server
weblogic 10
Click Done to finish Domain Installation. 
Next Step, go to Start WebLogic and access Domain Console from browser at end of this post.
.
Create Domain with one Administration Server and two Managed Server Instance in Cluster 
Steps here are to create new Domain with one Administration Server (AdminServer), two Managed Server (MS1 & MS2) in cluster (cluster_1)
- Administration Server and both Managed Server are installed on single machine (you can configure them on multiple servers as well).
.
Administration Server
Name - AdminServer
Listen Address - All IP address on machine
Listen port - 7003
SSL Listen Port - 7004
.
Managed Server 1
Name - ms1
Listen Address - All IP address on machine
Listen port - 7103
SSL Listen Port - 7104
.Managed Server 2
Name - ms2
Listen Address - All IP address on machine
Listen port - 7203
SSL Listen Port - 7204
.
Cluster Details 
Cluster Name - cluster_1
Multicast Address - 239.192.0.0
Multicast Port - 8050
Cluster Address - 127.0.0.1
Cluster Member - ms1 & ms2
8 ) Start with step 1) to 4) as shown above on screen 5) “Customize Environment” select  Yes as shown below 
weblogic 8b.
9) Configure Administration Server - configure Administration Server using this screen like Name, Listen & SSL Listen Port
weblogic 8c
10) Configure Managed Server - click on Add to add managed server. 
weblogic 8d
11) Configure Managed Server - Add two managed server (ms1:7103:7104 & ms2:7203:7204)
weblogic 8e
12) Configure Cluster - click on Add to create cluster and add Managed Server in Cluster. If you have NOT defined any managed server in previous screen, you will NOT get this screen.  
weblogic 8f
13) Configure Cluster- Define cluster with Cluster Name, Multicast Address,  Port and address.
weblogic 8g
14) Assign Server to Cluster - Use this screen to add Managed Server on Left hand side to Cluster on right hand side.
weblogic 8h
15) Assign Server to Cluster - as shown in below screen shot, We added MS1 & MS2 to cluster_1
weblogic 8i
16) Configure Machine - Use this screen if you have more than one machine in your system. In our configuration Administration Server and  all Managed Server are on single machine.
weblogic 8j
17) Review WebLogic Domain -
weblogic 8k
18) Create WebLogic Domain  - define Domain Name and Domain Location on this screen. This screen is similar to step 6) above
weblogic 8l
.
.
Start WebLogic Domain
Once you have successfully created domain, next step is to  start weblogic domain and access Administration Console. (Steps here are to start basic domain - only one Administration Server,  “Start/Stop WebLogic Server - Administration and Managed Server“ coming soon… )
Startup Script
$BEA_HOME/user_projects/domain//bin/startWebLogic.sh (Unix)
$BEA_HOME\user_projects\domain\\bin\startWebLogic.cmd (Windows)
I installed domain with name base_domain and my BEA_HOME is c:\bea hence to start my domain -
c:\bea\user_projects\ domains\ base_domain\ bin\ startWebLogic.cmd
Access Administration Console
Default Administration Port is 7001 so use port as 7001 (else use port you entered while creating WebLogic Domain)
http://.domain:7001/console
or
http://localhost:7001/console (If you are accessing from server directly)
Login to WebLogic Admin Console using UserName/Password created during WebLogic Domain Creation.
weblogic 11
After successful login you should get screen like below.
weblogic
.

Domain , Administration & Managed Server, Cluster in Oracle WebLogic

This is next post in series “Learn Oracle WebLogic with Us“. Next Step after Oracle WebLogic Installation  is to create Domain.
        Before creating domains let us understand Domain, Administration Server, Managed Server and Cluster in Oracle WebLogic.
In next post We’ll learn how to create basic Domain (Administration Server only) and Domain with Managed Server Cluster (one Administration Server and two Managed Server in cluster) using Configuration Manager.
 
What is domain in WebLogic ?
WebLogic Domain
Domain is logical grouping of resources and services and consist of Administration Server, Managed Server and cluster.  There can only be one administration Server in domain and zero to N Managed Server.
.
.
What is Administration Server ?
Administration Server is WebLogic Server instance that maintains configuration data for a domain. You can deploy your application on administration Server but it is recommended to create managed Server and deploy your application in managed server and leave Administration domain for configuration and maintenance.

—There will always be atleast one Administration Server in a domain.
.
.
What is Managed Server ?
Any WebLogic Server instance apart from Administration Server is called as Managed Servers. This is weblogic server where you deploy your application (Though you can deploy your application in Administration server as well but it is not recommended in production/UAT instance)
.
.
What is Cluster in WebLogic ?
Group of WebLogic Managed Server Instances that work together to provide high availability and scalability for applications is called cluster. WebLogic Servers with in cluster can run on same machine or different machines. These are also called as managed Server cluster.
.
.
Things you should know before creating domain in WebLogic Server ?
You use configuration wizard to create or extend domain but this can be used only in offline mode (when weblogic server is not running)
You can also use WLST (WebLogic Scripting Tool), command line tool to create and extend domains in WebLogic Server.
You can also use unpack command to create new domain. This command can’t be used to extend domain.
Extending a domain means, you already created domain and now wish to extend it (use more application, add managed server, create cluster…)
Configuration wizard can be run in Graphical Mode (interactive GUI) or Console Mode (interactive text based)
For silent mode use WLST (WebLogic Scripting Tool)
While creating domain you specify Startup Mode (Development or Production). In development mode, you get autodeploy option and security is low. In production mode you need username/password to deploy applications.
When you create domain, it creates following directories
i) autodeploy ii) bin iii) config (config.xml for domain sits here)  iv) console-ext v) lib vi) security vii) servers
–You use config.cmd (windows) or config.sh (unix) from $BEA_HOME/ wlserver_/ common/ bin to start configuration manager to create domain
Below Flowchart (image from Oracle Documentation) displays steps to create domain.
Create WebLogic Domain
Step by Step Weblogic Domain creation (with Managed Server Cluster) coming soon …

Oracle WebLogic Installation Steps

Oracle WebLogic Server is J2EE Server (earlier known as BAEWebLogic Server) similar to Oracle Application Server.  
  This post covers installation of Oracle WebLogic Server with available installation Mode and Components.
You can download Oracle WebLogic Software from here  (Currently it is available on Windows, Linux and Solaris and can be installed on Windows Vista also)

A. Installation Mode
BEA products can be installed in following mode
i) Graphical Mode - Interactive GUI based
ii) Console Mode - Interactive Text Based (-mode=console)
iii) Silent Mode- Non Interactive method using XML properties file  (-mode=silent -silent_xml=properties_xml_file)
.
B. Installation Type
i) Complete or
ii) Custom
.
C. Installation Component
Depending on type of installer you choose, you get following kind of component
1) WebLogic Server
—Server
—Server Examples
—Server Add-ons
2) Workshop
—Workshop for WebLogic
—Workshop Runtime Framework
3) WebLogic Integration
—Integration Server
—Workshop Integration Extension
—Integration Examples
4) WebLogic Portal
—Portal Server
—Workshop Portal Extension
—Portal Examples
D. Installation Requirement

i) Hard Disk- Approx 3.5 GB for complete installation.
ii) Memory - Minimum 1GB as per documentation (will work on 500MB as well)
iii) JDK - JDK (Java Development Kit - Not required on windows on Unix install JDK 4,5 or 6)
iv) BEA HOme Directory - This directory is repository for common files used by multiple BEA products.
v) Product Installation Directory- Specific to particular BEA product like WebLogic Server, Workshop for WebLogic, WEbLogic Integration …
vi) Temp Directory - approx 2.5 times of total installation (this will be cleaned up after installation)
.
E. Things to consider
1. Try NOT to give space in directory for BEA_HOME (like Program Files)
2. Try Not to exceed 12 characters when naming BEA_HOME
3. You can specifiy installation log file during installation like -log=/myinstalllog.log
4. To start installation in console mode use  -mode=console
5. To start in silent mode, create silent.xml file containing all values and use -mode=silent -silent_xml=
.
F. Installation Steps
1. Welcome
2. Choose BEA Home
3. Choose Install Type (Complete , Custom). If you selected Custom, Go to 4 else go to 5
4. Choose Product and Component (mentioned in step C above)
5. Choose Product Installation Directories
6.Install Windows SErvice (only if installation is on windows AND You have administrative privileges AND this is first installation AND this is CUSTOM installation)
7. Installation complete
.
Start Installation on Windows/Linux
Go to location where you have download software and start installation as
server1001_win32.exe -mode=console -log=c:\weblogic.log 
Replace server1001_win32.exewith executable name on Linux/Solaris and change location to directory as per Unix like /home/bea/weblogic.log (This will install BEA in interactive console mode)

Sunday, April 17

Weblogic 10 - what to know

WA1641 BEA WebLogic Server 10.0 Administration

The basics of the administration and deployment of Web applications in BEA WebLogic Server 10.
Objectives
At the completion of this, the student will be able to:
  • Understand WebLogic architecture
  • Understand deployments of EJB and Web applications
  • Understand how to run WebLogic as a Web server
  • Set up WebLogic Server test environments for developers
  • Start/stop servers, problem detection and trouble shooting
  • Use the WLST for command-line administration
  • Use clustering for fault tolerance and load balancing
  • Configure and monitor resources in a production environment
  • Conduct security planning and implementation
  • Handle large throughput and concurrency
  • Understand performance tuning
  • Use the JRockit Management Console for performance monitoring
Topics
  • J2EE and WebLogic Server architecture
  • WLST
  • WebLogic Clustering
  • WebLogic Application Deployment
  • WebLogic Resources and Services Configuration and Monitoring
  • Security and Transaction Management
  • WebLogic Performance Tuning
Audience
Web server administrators, project managers, developers and consultants who want to gain the knowledge of WebLogic Server administration.
Prerequisites
  • Knowledge and experience of network management and protocols
  • Knowledge and experience of RDBMS

WA1641 BEA WebLogic Server 10.0 Administration

1. Introduction To J2EE

  • Objectives
  • What Is JEE?
  • History Of JEE
  • Browsers And Web Servers
  • Limitations Of Browsers And Web Servers
  • Client vs. Server Processing
  • Server Side Processing
  • Problems with CGI
  • JEE Offers Server Side Processing
  • JEE Server Side Processing
  • J2EE Components
  • JEE: Servlets
  • JEE: JSPs
  • JEE: EJBs
  • JEE Containers
  • Sun JEE Blueprint
  • JEE Application Server Vendors
  • Development Environments
  • JEE And JDK
  • J2EE Versions
  • J2EE Historical Timeline
  • Database Vendors
  • 3-Tier Architecture
  • Summary  

2. BEA WebLogic Server v10

  • The BEA WebLogic Family Of Products
  • BEA WebLogic Portal
  • BEA WebLogic Integration
  • BEA WebLogic Workshop
  • BEA WebLogic Server v10
  • New Administrative Features  

3. Introduction To WebLogic Server 10

  • Objectives
  • WebLogic Server Instances
  • The Java Virtual Machine
  • JVM Providers
  • Threads vs. Processes
  • WebLogic Server Domains
  • Servers And Domains
  • Domain Configuration
  • WebLogic Administration Domain
  • Directory Structures
  • Getting Started Roadmap
  • Install WebLogic Server
  • The Configuration Wizard
  • The Configuration Wizard: Creating A New Domain
  • Starting The Administrative Server
  • The Administration Console
  • Administrative Tasks
  • Lock & Activate In The Admin Console
  • Other Administrative Tools
  • Setting the Domain Environment
  • Automatically Starting Admin Servers
  • Managed Servers
  • Creating A Managed Server
  • Server Details
  • Starting A Managed Server
  • Password boot.properties
  • Examining Server Status
  • Shutting Down Servers
  • Admin Server Shutdown
  • Admin Server Backup
  • Start Scripts
  • config.xml
  • Summary  

4. WLST: The WebLogic Scripting Tool

  • Objectives
  • The WLST
  • WLST Details
  • MBeans And JMX Administration
  • Layered JMX Architecture
  • MBeans And WLST
  • Starting WLST
  • Simple WLST Commands
  • WLST Is Hierarchical
  • Navigating WLST
  • MBean Operations
  • MBean Operations: Query
  • MBean Operations: Configurational
  • MBean Operations: Instantiation
  • Other WLST Commands
  • Scripting With WLST
  • Recording WLST Scripts
  • Configure Recording
  • Start Recording
  • Sample Recorded Script
  • References
  • Summary  

5. Logging and Monitoring

  • Objectives
  • Introduction
  • WebLogic Logging Services
  • Java Logging API
  • Java Logging API
  • Log4j
  • Specifying the Logging Implementation
  • Message Severity
  • WebLogic Server Logs
  • Server Log
  • Viewing Server Log
  • Configuring Server Log
  • HTTP Access Log
  • Configuring HTTP Access Log
  • JMS Log
  • Configuring JMS Log
  • Domain Log
  • Viewing Logs
  • Summary  

6. Using WebLogic As A WebServer

  • Objectives
  • Web Server Overview
  • Using WebLogic Web Server
  • Configuring The WebLogic Web Server
  • Virtual Hosts
  • Creating Virtual Hosts
  • Specifying Virtual Host Names
  • Targeting Virtual Hosts to Server
  • Access Log
  • External Web Servers
  • Apache HTTP Server Plug-In
  • Installing Apache HTTP Server Plug-In
  • Configuring Apache HTTP Server Plug-In
  • Keep-Alive Connections
  • Summary  

7. Assembling Applications

  • Objectives
  • Java Web Application Architecture
  • JEE Architecture
  • Web Application Programming Model MVC
  • An MVC Example
  • The Infrastructure for Enterprise Web Applications
  • What is Application Assembly?
  • JEE Modules
  • JEE Application Assembly
  • Web Module
  • Web Module - Deployment Descriptor
  • web.xml
  • weblogic.xml
  • WEB-INF Directory
  • Web Application Directory
  • EJB Modules
  • EJB Deployment Descriptors
  • ejb-jar.xml
  • Enterprise Application Modules
  • Enterprise Application Deployment Descriptor
  • Accessing Web Applications
  • Summary  

8. Deploying Applications

  • Objectives
  • The Process
  • Deployment Overview
  • Archive Vs Expanded Directory
  • Default Deployment Names
  • Deployment Methods
  • Auto-Deployment
  • Console Deployment
  • Starting an Application
  • Stopping an Application
  • Updating Applications
  • Deleting Applications
  • Testing a Deployed Application
  • Monitoring Deployed Applications
  • Editing Deployment Descriptors
  • Using Command Line Deployment
  • weblogic.Deployer
  • weblogic.Deployer Commands Syntax
  • T3 Protocol Overview
  • weblogic.Deployer Usage
  • wldeploy Ant Task
  • wldeploy Ant Task Examples
  • WebLogic Scripting Tool (WLST)
  • WebLogic Scripting Tool (WLST) Scripts
  • Deployment Plans
  • What Is A Deployment Plan?
  • Deployment Plan Overriding
  • Creating A Plan
  • Using A Plan
  • Best Practices
  • Summary  

9. Database Access and WebLogic

  • Objectives
  • Overview
  • Types of JDBC Drivers
  • Working with a Database via JDBC (Client side)
  • The Need for Connection Pooling
  • Connection Pooling and Data Sources
  • Connecting with Data Source
  • Steps in using Connection Pooling
  • Admin Tasks for Connection Pools and Data Sources
  • JDBC Driver Support in WebLogic Server
  • Database Access Using WebLogic
  • Working with Data Sources
  • Creating a Data Source
  • Editing Data Source Properties
  • Monitoring Data Source and Connection Pools
  • Summary  

10. WebLogic and JMS

  • Objectives
  • The Trouble with RMI/IIOP
  • Messaging to the Rescue
  • Message-Oriented Middleware
  • Messaging Features
  • Publish/Subscribe
  • Point-to-Point
  • Java Messaging Service
  • Terminology
  • The JMS Interfaces
  • Integrating JMS and EJB
  • Durable Subscription
  • Deployment Descriptor Entry
  • Binding the Queue or Topic
  • Transactions & Guaranteed Delivery
  • WebLogic JMS Server
  • Creating a JMS Server
  • Creating a Connection Factory
  • Creating a Topic
  • Threshold and Quota
  • Configuring Threshold and Quota
  • Distributed Destination
  • Creating a Distributed Topic/Queue
  • Creating a Distributed Topic
  • Monitoring JMS in WebLogic
  • Messaging Bridge
  • Summary  

11. Remote Administration

  • Objectives
  • Node Manager Overview
  • Node Manager Functionality & Configuration
  • Starting an Administration Server from Node Manager
  • Starting a Managed Server from Node Manager
  • Restarting a Administration Server from Node Manager
  • Restarting a Managed Server from Node Manager
  • Shutting Down a Server Instance From a Node Manager
  • Working with Security
  • Working with Machines
  • Creating a Machine
  • Adding Server Instances To a Machine
  • Starting The Node Manager
  • Monitoring Managed Servers
  • Node Manager Logs and Configuration Files
  • Summary  

12. Chapter 11: Security

  • Objectives
  • WebLogic Server Security
  • Authentication / Authorization
  • Resources That Can Be Secured
  • Authentication Mechanisms
  • WebLogic Security Diagram
  • Overview: Security Tasks For Securing Resources
  • WebLogic Security Realms
  • Configuring A User Registry
  • The Embedded LDAP Server
  • Managing Users/Groups
  • User Lockout
  • Managing Roles
  • Securing A Resource
  • WebLogic Server Policies
  • Specifying A Policy Condition
  • Policies And Roles
  • Creating A Scoped Role
  • Declarative Security
  • Example: Securing A Web Resource
  • Example: Securing A Web Resource Specifying Roles
  • Example: Securing A Web Resource Specifying Constraints
  • Example: Securing A Web Resource Specifying Constraints
  • Example: Securing A Web Resource Auth Method
  • Example: Securing A Web Resource Auth Method
  • Example: Securing A Web Resource Map Roles
  • Encryption
  • SSL
  • Public Key / Private Key Encryption
  • Secure Communication Over The Web - SSL
  • SSL And WebLogic Server
  • Creating A Digital Certificate
  • Dealing With A CA
  • Configuring WebLogic Server SSL: Keystores
  • Configure WebLogic SSL Settings
  • Configuring WebLogic Server SSL: Setting A Listen Port
  • Summary

13. Clustering

  • Objectives
  • What Is Clustering?
  • What Components Can Be Clustered?
  • Basic Cluster Diagrams
  • The Load Balancer
  • Web Container Load Balancing
  • Horizontal Vs. Vertical Clustering
  • Horizontal Clustering
  • Horizontal vs. Vertical Clustering
  • Clustering WebLogic Server
  • WebLogic Cluster Requirements
  • Configure Domain For Clustering
  • Create A Cluster
  • Multicasting vs. Unicasting
  • Create A Cluster
  • Configure Application Resources
  • Deploy Applications To The Cluster
  • Configure A Load Balancer
  • Load Balancer Options
  • Hardware Load Balancers
  • Proxy Plug In Load Balancers
  • HttpClusterServlet Load Balancer
  • Session State
  • Clustered Session State
  • Session State Strategies
  • In-Memory Replication
  • Configuring Session State Replication
  • JDBC Session Persistence
  • JDBC Multi Data Sources
  • Creating A Multi Data Source
  • EJB Clustering
  • EJB Load Balance Algorithm
  • Summary  

14. Performance Tuning

  • Objectives
  • Performance Tuning
  • Response Time
  • Throughput
  • Throughput Curve
  • The significance of throughput
  • Response Time Curve
  • Think time
  • Saturation
  • Response time at system saturation
  • Response time past the buckle point
  • Interpreting response time trends
  • Interpreting response time trends
  • Interpreting response time trends
  • Basic Tuning Methodology
  • Areas To Tune
  • Tuning Hardware
  • Tune The Operating System
  • Tune The JVM
  • JVM Choices
  • Memory Performance Concerns
  • Client or Server VM
  • The Heap
  • The Heap (cont.)
  • Heap Limit
  • Heap Top
  • Default Heap Sizes
  • Configure The Heap Size
  • Allocation Failure
  • Garbage Collection
  • Heap Regions Sun JDK
  • Analyzing Verbose GC - Sun
  • Verbose GC - JRockit
  • Thread Local Heap (TLH)
  • Types of Collector In Sun JVM 1.5
  • Memory Tuning Goals
  • Effect of Initial Heap Size on GC
  • Controlling the GC Timings
  • Optimizing GC
  • Self Optimizing Throughput Collector
  • JRockit Management Console
  • Launching the Client
  • The JMC
  • JMC Memory Usage
  • JMC CPU Usage
  • System Information
  • Method Profiler
  • Exception Count
  • Notification
  • JRA Recording
  • Tuning WebLogic Server
  • Thread Settings
  • Socket Readers
  • Socket Implementation
  • Monitoring Threads
  • Connection BackLog
  • Tuning The Back End
  • Summary