WebLogic Server System Adminstration

OutOfMemoryError in Compile time Issue

2010-10-04T22:49:00.000-07:00

WebLogic server startup causing the OutOfMemoryError when it is compling new jar file

I have deployed the ear file(it contains jars,wars) and I was trying to restart the application on one managed server,The managed server started successfully with running mode but startWeblogic.OUT file having the "OutofMmoryError" error. so i need to fix as i am on prod deploy call.

I have tried to resolve by checking the disk space utiliazation,Jdk's min&max memorey arguments,heapdump etc ...everywhere it looks good, eventhought I have restarted the server after cleared cache ,space ...still the error is coming up ...

found that the java is trying to compile the new jar file, and it was failing to compile while deploying it in server startup.

I have tried many ways to resolve it ...but it didn't success it.

After i had compared the admin console with the another prod backup environment's admin console which is working fine.

Found that there is a Java Compiler path different in admin console when we compared with other environment's admin console for that perticular server instance.
so the compiler is not supporting while compiling perticular jar file
actually *ejb.jar file was trying to deploy and compliling after we restarted the server so that the perticular code is not supporting.

I have updated the path from /usr/j2se142_08/bin/javac to /java/j2se142_11/bin/javac

then the server came up successfully after bounced the server without any error.

for this, i have created a problem ticket and resolved it finally, it is a small issue but taken much time to trouble shoot the problem ...

JRokit GC Option Enable issue

2010-10-04T20:09:00.000-07:00

One of the WebLogic Server instance is not starting due to passing the java options, which are not supported to jrockit.

My environemnt requirement is that, I need to enable the verbose:gc for my production servers and I have tried to enable by giving the below java options in a customized script which inturn calls start script. After my try in development test server that was failed to start.

#JAVA_OPTIONS="$JAVA_OPTIONS -DDebugSecurityAtn=true -DDebugSSL=true"
JAVA_OPTIONS="${JAVA_OPTIONS} -XX:+HeapDumpOnOutOfMemoryError -verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -Xloggc:${LOGDIR}/gc.log"

On the server logs it kicked the rejected message "illegal java option" error in weblogic.log file and on the other hand gc.log file is not created, I have found in googling that we are using jrockit so these "-verbose:gc, Xloggc:gc.log,etc options are NOTsupporting which are supported by Sun JDK hotspot JVM. and server is not coming up. What made missing?? You think think!! I got an idea, of-course it is a doubt wheather this JDK options are same or different for JRockit JVM??

After struggling on google for few minutes…

Finally I have fixed this issue by giving the proper jrockit's supported GC options (verbose: memory, Xverboselog:gc.log etc)

It Works out the below options and its created gc.log under logdir path:

#JAVA_OPTIONS="$JAVA_OPTIONS -DDebugSecurityAtn=true -DDebugSSL=true"
JAVA_OPTIONS="$JAVA_OPTIONS -DDebugSecurityAtn=true -DDebugSSL=true -Xverbose:memory -Xgcprio:pausetime
-Xverboselog:${LOGDIR}/gc.log"

Now the desired sample gc.log generated as it is shown below:

[INFO ][memory ] [YC#84] 69.846-69.862: YC 589972KB->562334KB (1048576KB), 0.016 s, sum of pauses 15.527 ms, longest pause 15.527 ms.
[INFO ][memory ] [YC#85] 70.223-70.234: YC 596537KB->566915KB (1048576KB), 0.011 s, sum of pauses 10.404 ms, longest pause 10.404 ms.
[INFO ][memory ] [YC#86] 70.525-70.535: YC 602423KB->572377KB (1048576KB), 0.010 s, sum of pauses 10.230 ms, longest pause 10.230 ms.
[INFO ][memory ] [YC#87] 70.828-70.839: YC 605159KB->575545KB (1048576KB), 0.011 s, sum of pauses 10.772 ms, longest pause 10.772 ms.

conclusion: all jdk's GC options does not supported/compatible with jrockit's gc options

Ref Site for Jrockit:
http://weblogic-wonders.com/weblogic/2010/09/03/why-and-how-oracle-jrockit/
Ref Site for JDK and JRockit's options:
http://www.tagtraum.com/gcviewer-vmflags.html#sun.loggc

Semaphore issue in WebServer

2010-10-03T11:12:00.000-07:00

In most of the Web Server's environments are in the De-Militarized Zone(DMZ)architecture as front end for weblogic. So the front tier is having the setup for the proxy plug-in with one of the WebServers (HTTP). This post is about Sunone WebServer proxying for WebLogic web-tier.

The issue encountered when one of the physical site's single sign on page is failed to display. There are many users on that site, they need immediate resolution for the issue. Because in the e-commerce world every minute is precious each hit is valuable every delay of operation that causes losses in dollars. Keeping in this in mind acted instantly the producing support team. The team focused in the each log that related to that site and its SSO web instance. finally the team found that whole causing flaw is in a webserver agent log, it is an issue related to processes the Max semaphore setting on one server, while bringing up the web instances."Failed to initialize the siteminder agent error came while starting sun web server".

After a while the smart WLA, wearing the thinking cap, found the Resolution as "Increased the max semaphore limit" on the Unix machine has the current setting as (200) changed to 512 using the below given command sequel.

Here we go ... Now let see how the 'prctl' Unix commands helps us to create or add the fragmentation size limit to 512:

$ prctl -t priv -n project.max-sem-ids -v 512 -e deny $$

Below command to delete the fragmentation size limit to 200: (delete the old setting ,after/before adding the new size)

$ prctl -t priv -n project.max-sem-ids -v 200 -x $$

Below command is to list all the semaphore settings:

$ prctl -n project.max-sem-ids $$

process: 25277: bash
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-sem-ids
privileged 512 - deny -
system 16.8M max deny -

The similar issue is identified in Apache WebServer associated with CA SiteMinder Agent service too.
Hope this will give basic idea about the semaphore issue and its resolution.

Keep reading the blog!! enjoy!! write back to us with your issues on WebLogic Administration issues!!!

Source from : Smart WLA Sarangapani. M
Reference:

http://www.bigadmins.com/solaris/how-to-tune-kernel-parameters-in-solaris-10/

WebLogic Administration issues Part 1

2010-09-28T18:18:00.000-07:00

WLA production support Issues

Day to day there are many issues comes to WebLogic Administrator, When issues comes I feel more happy because variety tricks need to be developed, this is the situation where we can explore things into the deeper level, understand and get the effective resolution after a little bit brainstorming research. This might be good habit of any WLA, What do you say guys?? Here I going to share with you guys, my recent issues (this week) faced and fixed them on time

There is issue going in a Data center, all the people in the data center are feeling panic. There lift their hands unable to find from where this issue originated. While starting the WebLogic instance unable to start.

A smart WLA, How is not only think in WebLogic, he is having fantastic knowledge about UNIX too. Just within few minutes after he found the root cause of the issue is one of the mounted Disk space is overloaded 100% disk utilization FULL!!

How he found the space issue you can see here. It the problem is that there is not enough space to start the sever instance. In the server instance log it is going to show space issue. A small JVM kid unable to have sufficient memory.

/logs> du - sk *|sort –rn |head
12050 lof_09-14-2010.log
2950 LOF_PERF_09-14-2010.log
2951 346 startWebLogic.OUT
488 PERF_09-14-2010.log
489 452 LOG_09-14-2010.log
---
Above command shows that we can see the file or directories, which occupied how much disk sizes on a particular filesystem, mount point. Accordingly we can resolve the issue by rotate the logs to clear off the space for particular instance is being occupied more disk space. So be brave to face the issue!!

Sourced by : Sarangapani Matoori WLA

Creating a Domains using weblogic.Server

2010-09-05T11:44:00.000-07:00

It was chilling January days, when I was doing my experiments for WebLogic System Administration certificate. You might think that how come this is possible a domain using weblogic.Server?? But it is true, you can do this, you can configure a domain using java weblogic.Server. This blog enables you to help you to make that domain with weblogic.Server class and the same command will Start the Admin Server of-course you can name your Admin Server here I did as Server2. The command can be given as follows:

java -XX:MaxPermSize=512m -Dweblogic.RootDirectory=.
-Dweblogic.Domain=domain2 -Dweblogic.Name=Server2 -Dweblogic.management.username=weblogic
-Dweblogic.management.password=weblogic -Dweblogic.ListenAddress=WLHost.com
-Dweblogic.ListenPort=9015 weblogic.Server

Let us see new scenario
If we have config.xml file copied from an existing domain then we can run the server with the override the exiting values present in the urconfig.xml file with ListenAddress, ListenPort new values given in command line.

No config.xml was found.
Would you like the server to create a default configuration and boot? (y/n): y

The response 'y' indicates to the weblogic.Server to create a domain directyory with all required files and directories for it.
If you don't specify the ListenAddress then weblogic will search for all possible network channels to connect with the given port.

java -XX:MaxPermSize=512m -Dweblogic.RootDirectory=. -Dweblogic.ConfigFile=urconfig.xml
-Dweblogic.Domain=domain2 -Dweblogic.Name=Server2 -Dweblogic.management.username=weblogic
-Dweblogic.management.password=weblogic -Dweblogic.ListenAddress=WLHost.com
-Dweblogic.ListenPort=9015 weblogic.Server

Above highlighted text in single line in a command prompt or keep this into a shell script or batch script for respective operating environments. Here the domain can be created for only single server (Admin Server) instance, and we cannot add managed server and cluster etc. if we have already a config.xml file available then we can specify using -Dweblogic.ConfigFile=urconfig.xml.

Creating the Domains using ANT

2010-09-05T11:42:00.000-07:00

This is my one more attempt to creating the WebLogic domain with ANT Script that is build.xml.

In the Oracle WebLogic we have wonderful options to define the parameters to create a domain with ant script (build.xml). Here it comes the most powerful ANT task given by WebLogic with a specialized parameters i.e., wlserver.

My experiment is going to create a simple single server domain and starts the Admin server also with this script.

You can use any editor to edit this build.xml and enter the following lines then run ant in your command prompt

My Successful build.xml made for Solaris operating environment where all PATH, CLASSPATH variables already defined as told in earlier post which already assigned in previous domain creation.

Note: Each line keep it in the lessthan Open tag(<) and greaterthan close tag(/>) and remove if open or close braces () are there in there before using it

Execution Results as follows:
bash-3.00$ ant
Buildfile: build.xml
newserver:
[delete] Deleting directory /export/home/wluser/testant/tmp
[mkdir] Created dir: /export/home/wluser/testant/tmp
BUILD SUCCESSFUL
Total time: 1 minute 26 seconds
[WLServer wsant] Server will not be killed due to noExit flagwsant

Noticed following changes to work it properly:

1. The folder name tmp is used for creating domain that can be domain directory path, we change it once the ant script run successful.
2. When I used the e-docs given ant script it is running the server after configuring domain with given parameters and automatically
Killing the ant generated process. To stop this added attribute noExit with true as value.
3. The default jvmags to start WebLogic Server not sufficient. it is throughing following Error:
java.lang.OutOfMemoryError: PermGen space
To resolve this wlserver standalone tag changed to paired tag, and a child tag added as jvmarg.

Ref: "Starting Servers and Creating Domains Using the wlserver Ant Task" on Oracle Documents

Creating Domain using pack and unpack

2010-09-05T11:39:00.000-07:00

Though there are many ways to configuring a WebLogic domain, Here I am going to experiment with pack and unpack commands for my Certification. Later I found it is very handy for migrating old domains to new and it is best suites for extending the domains also.

You have one more chance of creating domain template with Domain Template Builder

http://download.oracle.com/docs/cd/E13179_01/common/docs102/tempbuild/index.html

Create new domains using custom Domain/Configuration Templates

Creating Domain by using pack and unpack command of new feature in Weblogic Server 9.x and above 10g or 11g:

The WebLogic provides two compressing and uncompressing the domain for reusing to another remote machine or it can be used as backup for the existing domain.

Which requires the PATH need to set to /common/bin

export PATH=/export/home/wlsuser/bea/weblogic92/common/bin:$PATH

PACK Process

Now let us see PACK Process how it works

Syntax:

pack -domain=domain -template=template -template_name=“template_name”
[-template_author=“author”][-template_desc=“description”]
[-managed={true|false}][-log=log_file] [-log_priority=log_priority]

if it is in the pack command in the path you can give pack.sh from any directory otherwise you need to goto that path.
Example

bash-3.00$ pack.sh -domain="/export/home/wlsuser/domains/wlscldom"
-template="/export/home/wlsuser/templates/wlscltemp.jar" -template_name="WLS
CLUSTER DOMAIN" -log=/export/home/wlsuser/logs/wlscldompack.log -log_priority=INFO

<< read domain from "/export/home/wlsuser/domains/wlscldom" >> succeed: read domain from "/export/home/wlsuser/domains/wlscldom"
<< write template to "/export/home/wlsuser/templates/wlscltemp.jar" ................................................................................. ................... >> succeed: write template to "/export/home/wlsuser/templates/wlscltemp.jar"
<< close template >> succeed: close template

To confirm that domain created in the current directory check with ls command.
bash-3.00$ ls -l
total 30
drwxr-xr-x 8 wlsuser wlproj512 Dec 19 07:58 bea
drwxr-xr-x 3 wlsuser wlproj512 Dec 24 10:48 domains
bash-3.00$ cd logs
bash-3.00$ ls -l
total 130
-rw-r--r-- 1 wlsuser wlproj948 Dec 24 12:06 wlscldompack.log

To View the logged info related to pack process.
bash-3.00$ tail -100 wlscldompack.log
2008-12-24 12:06:43,569 INFO [runScript]
com.bea.plateng.domain.script.ScriptExecutor - read domain from
"/export/home/wlsuser/domains/wlscldom"
2008-12-24 12:06:52,643 INFO [runScript]
com.bea.plateng.domain.script.ScriptExecutor - succeed: read domain from
"/export/home/wlsuser/domains/wlscldom"
2008-12-24 12:06:52,648 INFO [runScript]
com.bea.plateng.domain.script.ScriptExecutor - write template to
"/export/home/wlsuser/templates/wlscltemp.jar"
2008-12-24 12:06:56,785 INFO [Thread-1] com.bea.plateng.domain.TemplateGenerator
- Template Generation Successfull!
2008-12-24 12:06:56,847 INFO [runScript]
com.bea.plateng.domain.script.ScriptExecutor - succeed: write template to
"/export/home/wlsuser/templates/wlscltemp.jar"
2008-12-24 12:06:56,852 INFO [runScript]
com.bea.plateng.domain.script.ScriptExecutor - close template
2008-12-24 12:06:56,856 INFO [runScript]
com.bea.plateng.domain.script.ScriptExecutor - succeed: close template

bash-3.00$ cd templates
bash-3.00$ ls -l
total 46
-rw-r--r-- 1 wlsuser wlproj 23188 Dec 24 12:06 wlscltemp.jar

To pack the managed servers only then we need to use the option '-managed=true'. by default it is set to false.
bash-3.00$ pack.sh -managed=true -domain="/export/home/wlsuser/domains/wlscldom"
-template="/export/home/wlsuser/templates/wlscltemp.jar" -template_name="WLS
CLUSTER DOMAIN" -log=/export/home/wlsuser/logs/wlscldompack.log -log_priority=INFO

UNPACK Process

To run this we must already run the pack command on a domain which is already existing. The domain template jar must be copied to the destination machine.

Syntax:
unpack -template=template -domain=domain [-user_name=username]
[-password=password] [-app_dir=application_directory]
[-java_home=java_home_directory] [-server_start_mode={dev|prod}]
[-log=log_file] [-log_priority=log_priority]

Example

bash-3.00$ unpack.sh -template=wlscltemp.jar -domain=domains/wlscldom
-log=wlscldomunpack.log -log_priority=INFO

<< read template from "/home/wlsuser/wlscltemp.jar" >> succeed: read template from "/home/wlsuser/wlscltemp.jar"
<< write Domain to "/home/wlsuser/domains/wlscldom" ................................................................................. .............. >> succeed: write Domain to "/home/wlsuser/domains/wlscldom"
<< close template >> succeed: close template
bash-3.00$ ls -l
total 1188090
drwxr-xr-x 7 wlsuser wlproj 1024 Dec 24 09:13 bea
drwxr-xr-x 3 wlsuser wlproj 96 Dec 24 12:20 domains

To unpack managed server also it will work in the similar manner. But need to put the “-managed=true”

Example:

pack.sh -managed=true -domain="/home/wluser/domains/WLclsnm/" -template="/home/wluser/templates/WLclsnm.jar" -template_name="WLS CLUSTER DOMAIN" -log=/home/wluser/logs/wlscldompack.log -log_priority=INFO


unpack.sh -template=WLclsnm.jar -domain=domains/WLclsnm -log=WLclsnmpack.log -log_priority=INFO

Managing the Weblogic Server Life Cycle

2010-09-05T11:31:00.000-07:00

In this post I am going to discuss about WebLogic Server Life Cycle. Before you dive into the deeper you must know each Java option that you can use, and also argument you can pass to the weblogic.Server class, which is a member of weblogic package given by Oracle WebLogic installation.
Usage: java [options] weblogic.Server [args...]
Where WebLogic options include:
-Djava.security.policy= the location of the security policyfile
-Dweblogic.Domain= WebLogic domain name
-Dweblogic.Name= WebLogic server name
-Dweblogic.ext.dirs=':' separated list of directories to pick up jars fromand add to the end of the server classpath.The list can also contain individual jars.
-Dweblogic.management.server=WebLogic Admin Server URL for starting a Managed Server, the value can be: host:port or http://host:port or https://host:port
-Dweblogic.home= The location of the WebLogic Server product install. By default, this will be derived from the classpath.
-Dweblogic.RootDirectory=The root directory of your domain, where your configuration is housed.
default is the current working directory
-Dweblogic.management.username= user name
-Dweblogic.management.password= user password
-Dweblogic.management.pkpassword= private key password
-Dweblogic.security.unixrealm.authProgram= the name of the program used to authenticate users in the unix
security realm
-Dweblogic.= specify a server attribute, it will override the attribute value set in config.xml for this server
-Dweblogic.admin.host= same as weblogic.management.server, an old property
-javaagent:$WL_HOME/server/lib/diagnostics-agent.jar enable diagnostics hot code-swap for application classes And WebLogic args include:
-? -help print this help message

1. Starting the AdminServer by 'weblogic.Server'

Here is the basic command how the WebLogic Server will be started in the script. Actually, inside story you can understand how it goes by executing this command at your command line. To Start a admin Server we need to go to domains directory and use the following command:

java weblogic.Server

The JVM parameters will be considered default as 256 MB minimum and 512MB maximum heap size. If you wish to change you can specify as follows:

java -Xms512m -Xmx1024m -XX:MaxPermSize=512m weblogic.Server

while starting the admin server by using the weblogic.Server command Line references, uses minmum capability to start the Server instances. When we open the WebLogic Console in a browser it requires the load the console portal which cannot run on the default heap size like -Xms512m -Xmx1024m , need to increase the heap size and Permanent Size for the JVM also need to increase with -XX:MaxPermSize=512m. following command also works for running Admin server.

java -XX:MaxPermSize=512m weblogic.Server

If we don't use the JVM parameter of XX:MaxPermSize=512m , we will face the issue of "Out of Memor Error(perm gen error)" when accessing the console of admin

2) Starting the Managed Server by weblogic.Server command

Syntax :

java -Dweblogic.Name=managed-server-name -Dweblogic.management.server=adminURL weblogic.Server

java -Dweblogic.Name=app02 -Dweblogic.management.server=http://WLHOST:7913 -Dweblogic.management.username='weblogic' -Dweblogic.management.password='weblogic' weblogic.Server

2.1 Starting a Managed Server in ADMIN Mode

You might feel very thril here, To run the command line for the managed server for our regular example:
(Here WLHost replace with your own)

Starting a WebLogic instance in ADMIN mode

 nohup java -Dweblogic.Name=app02 \
-Dweblogic.management.server=http://WLHOST:7913 \
-Dweblogic.management.username='weblogic' \
-Dweblogic.management.password='weblogic' \
-Dweblogic.management.startupMode=ADMIN weblogic.Server >app02.out 2>&1 &

To check the status of the Server into the logs are as follows:

$tail -100f app02.out

2.2 Starting a Managed Server STANDBY Mode

Here one more wonder you can see here, To run the command line for the managed server for our regular example: (Here WLHost replace with your own)

Starting a WebLogic instance in STANDBY mode

nohup java -Dweblogic.Name=app02 \
-Dweblogic.management.server=http://WLHOST:7913 \
-Dweblogic.management.username='weblogic' \
-Dweblogic.management.password='weblogic' \
-Dweblogic.management.startupMode=STANDBY weblogic.Server >app02.out 2>&1 &

To check the status of the Server you need to look into the logs are as follows:

tail -100f app02.out

Normally we can start the managed server which is in remotely in command line by using the below :(starting managed server in remotely)

startManagedWebLogic.sh "app02" "http://wladminhost:7913"
app02 #remote managed server
http://wladminhost:7913 #admin url

Basic Steps for configuring WebLogic Domain

2010-09-05T10:34:00.000-07:00

Domain with AdminServer Creation:
Note: This is for Intial lerner or Basics who want to do manually not by using the wlst
Domain:
A domain is the basic administration unit for WebLogic Server. It consists of one or more WebLogic Server instances, and logically related resources and services that are managed, collectively, as one unit.
 The basic domain infrastructure consists of one Administration Server and optional Managed Servers and clusters

Administration Server :
A domain always includes one WebLogic Server instance that is configured as an Administration Server. The Administration Server provides a central point for managing the domain and providing access to the WebLogic Server administration tools
Managed Servers:
All other WebLogic Server instances in a domain are called Managed Servers. Managed Servers host application components and resources, which are also deployed and managed as part of the domain.
Clusters:
A domain may also include WebLogic Server clusters, which are groups of server instances that work together to provide scalability and high availability for applications. A cluster appears as a single WebLogic Server instance.

Creation of Domain in Weblogic 9.2:

1) Logon to SSH.
2) Go to Weblogic home
Command : cd $WEBLOGICHOME.
3) Go to the folder common/bin
Command : cd common/bin
4) Execute config.sh file. This file mainly takes care below the tasks,
Command : sh config.sh -mode=console
a) set ups the weblogic home, the root directory for Weblogic installation.
b) set ups the common environment like java home, java vendor and DataBase.
5) After executing the above command BEA WebLogic Configuration Wizard opens
6) Under this wizard we have below two options,
1.To create a new weblogic domain.
2.Extend the existing domain.
7) To create a new domain enter the index number 1.
Command : 1 and press ENTER
8) After executing the above command, Options for selecting domain source will be available.
9) Select option 2, to choose custom template.
Command : 2 and press ENTER
10) After executing the above command, below options will be available.
1 - Modify "User name"
2 - Modify "User password"
3 - Modify "Confirm user password"
4 - Modify "Description"
5 - Discard Changes
11) Select option 1, to modify User Name.
Command : 1 and press ENTER

12) Enter the user name and press ENTER.
Command : system and press ENTER
13) Select option 2, to modify the Password.
Command : weblogic and press ENTER
14) Select option 3, to confirm the Password.
Command : weblogic and press ENTER
15) After configuring the User Name and Password, type ‘next’ to proceed further with Domain configuration mode.
Command : next
16) After executing the above command, options to enable the domain in Production mode and Development mode will be available. Type 1 to enable Development mode.
Command : 1 and press ENTER
17) After executing the above command, options to select the JDK will be available. As we are using JDK 1.5 we need to select option 1.
Command : 1 and press ENTER
18) After executing the above command, options to modify the pre-configured settings we available. Select 1 to modify the settings
Command : 1 and press ENTER
19) After executing the above command, options to modify the below administration server configuration will be available.
1 - Modify "Name"
2 - Modify "Listen address"
3 - Modify "Listen port"
4 - Modify "SSL enabled"
20) Select option 2 to modify the Listen address.
Command : 2 and press ENTER
21) Enter the value for Listen address.
Command : x.xxx.xx.xx and press ENTER
22) Now, select option 3 to modify Listen port.
Command : 3 and press ENTER
23) Enter the value for Listen port.
Command : 6501 and Press ENTER
24) Option for target domain will be available for this domain.
Command : /pani/project/username
25) Option Edit the domain name will be available. Choose option 1 to edit the name else type Next for the creation of the domain.
Command : Next
26) Domain will be created successfully.

Updating Weblogic License

2010-01-26T11:09:00.000-08:00

Updating License file when it expires or moved from one version to another version of weblogic server and Installation of Patches Plugins :
[1] Install and configure WebLogic Server service packs (old versions) and patches

http://download.oracle.com/docs/cd/E14759_01/index.htm

[2] Install Web Server plug-ins if required on supported platforms

http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs81/81_over/add-ons.html

[3] Updating WebLogic License file

#This below info is written by pavan
WebLogic License Updating
Here we go to update the BEA License file ...

What happens if it is not updated?

1. We cannot have more instances on the same domain it is limiting to 5 instances only.

2. If you had the 5th instance including your Admin in RUNNING state but, you cannot access the console.

What is the resolution for this situation?

Update your BEA/Oracle Licence as per the given steps.

Stop all server instances which are already running.

Update this on every machine.

Remove "servers" folder

1. Click the license link:http://licensecodes.oracle.com/bea.html

choose here "BEA WebLogic Server Products" As per your operating environment you can choose the update.zip file.

2. Download you application suitable license zip file I have choosen version as "9.2 - 9.2mp3" -- LIC-WLSP92

3. Take a backup of the old license file

cp license.bea license.bea_bkp

4. Place the downloaded new license file (license.bea_new) in the BEA_HOME

4. Run the following command.

$ ./UpdateLicense.sh license.bea_new

Here it will apply the new lincense modifications on to the license.bea file directly.

If this command failed revert back to the old backup.

Now your license is ready to use more than 5 users (Clustered environment).

Start the servers and check for availability of new license.

Weblogic UnInstallation in Solaris

2010-01-26T10:40:00.000-08:00

Continuation of Weblogic Server Installation under Solaris 5.10 box
Weblogic Server Uninstallation in 3 Modes:
1.GUI
2.Console
3.Silent

2.Console Mode uninstallation of Weblogic Server in Solaris Box

1. Go to the following directory:
WL_HOME/uninstall
Here WL_HOME represents the directory in which you installed
WebLogic Server.
2. At the prompt, enter the following command:

 
bash-3.00$ cd bea
bash-3.00$ ls -l
total 40
-rwxr-xr-x   1 wluser   beaproject     851 Dec 17 10:51 UpdateLicense.sh
-rw-r--r--   1 wluser   beaproject      23 Dec 17 10:51 beahomelist
drwxr-xr-x   6 wluser   beaproject     512 Dec 17 10:51 jdk150_10
-rw-r--r--   1 wluser   beaproject   12081 Dec 17 10:51 license.bea
drwxr-xr-x   2 wluser   beaproject     512 Dec 17 10:52 logs
drwxr-xr-x   3 wluser   beaproject    1024 Dec 17 10:51 modules
-rw-r--r--   1 wluser   beaproject     917 Dec 17 10:52 registry.xml
drwxr-xr-x   3 wluser   beaproject     512 Dec 17 10:51 utils
drwxr-xr-x  10 wluser   beaproject     512 Dec 17 10:54 weblogic92
bash-3.00$ uninstall.sh -mode=console 

<----------------------- BEA Uninstaller - BEA Products ---------------------->

Welcome:


Welcome to the BEA Products uninstaller. If you wish to 
proceed with the uninstallation type Next, otherwise, please type 
Exit to cancel.

Enter [Exit][Next]>  

<----------------------- BEA Uninstaller - BEA Products ---------------------->

Choose Components to uninstall: 

-------------------------------

Check the BEA Products components you want to uninstall. 

    Release 9.2.2.0 

    |_____WebLogic Server [1] x
         |_____Server [1.1] x



Enter number exactly as it appears in brackets to toggle selection OR 

[Exit][Previous][Next]> 

 

<----------------------- BEA Uninstaller - BEA Products ---------------------->

Setting Up

 

<----------------------- BEA Uninstaller - BEA Products ---------------------->

Removing Files

<----------------------- BEA Uninstaller - BEA Products ---------------------->

Removing BEA Registry Entries

<----------------------- BEA Uninstaller - BEA Products ---------------------->

Uninstall Completed Successfully!

<----------------------- BEA Uninstaller - BEA Products ---------------------->

Uninstallation Complete

Uninstallation of selected components has completed successfully.

Press [Enter] to continue

bash-3.00$ cd bea 

bash-3.00$ ls -la
total 42
drwxr-xr-x   6 wluser   beaproject     512 Dec 18 06:41 .
drwxr-xr-x   6 wluser   beaproject     512 Dec 17 10:50 ..
-rwxr-xr-x   1 wluser   beaproject     851 Dec 17 10:51 UpdateLicense.sh
-rw-r--r--   1 wluser   beaproject      23 Dec 17 10:51 beahomelist
drwxr-xr-x   6 wluser   beaproject     512 Dec 17 10:51 jdk150_10
-rw-r--r--   1 wluser   beaproject   12081 Dec 17 10:51 license.bea
drwxr-xr-x   2 wluser   beaproject     512 Dec 17 10:52 logs
drwxr-xr-x   3 wluser   beaproject    1024 Dec 17 10:51 modules
-rw-r--r--   1 wluser   beaproject     324 Dec 18 06:40 registry.xml
drwxr-xr-x   3 wluser   beaproject     512 Dec 17 10:51 utils

Note: Weblogic92 folder disappear.

3.Uninstalling the Weblogic Server in Silent Mode

Go to the following directory: WL_HOME/uninstall Here WL_HOME represents the directory in which you installed WebLogic Server.
At the prompt, enter the following command:
bash-3.00$ sh uninstall.sh -mode=silent -log=/export/home/wluser/logs/uninstall.log

Weblogic Installation on Sun Solaris

2010-01-26T09:51:00.000-08:00

When I was preparing for the WebLogic Certification there is a dedicated topic for Installing WebLogic. If you wish to prepare for the same, Let me share you my experiance with the Installation on Sun Solaris SPARC machine. You, smart WLA need to choose what kind of installation required for the environment first. Normally for the Developer who want to test their application frequently they don't need a Production installation, At a given point of time you will get one or two hits to the application so the Development mode is sufficient. The Performance Engineer, work for pre-production environment tests requires Production installation. In the production environment the user hits to the application could be thousands at a any given time. So the need is huge you need Production mode installation. I hope, you should understand the basic differences between Development and Production mode installation perfectly then go ahead for the next section for experimenting. Here my focus on console type of installation which is most of the non-GUI environments requires and most of the WebLogic Administrator work from remote locations so this method is suggestable way. Other option GUI you can choose X11 forwarding with X emulator softwares.

Product Installation
[1] Install the JDK/JRE if required on supported platforms (if it is not included with jar distribution)
[2] Installing WebLogic Server on supported platforms

Installation Modes:
1. GUI
2. console
3. silent

Installing on Sun Solaris 5.10

When you are on the oracle download page you need to choose proper installer that should match your platform. If your system uses Sun Solaris 5.10, your installer could have a
server923_solaris32.bin(WebLogic 9.2 MP3) or wls1033_solaris32.bin (WebLogic 10.3.3/11g) as binary file name. If your installer has the .bin extension,that means the installer includes Java Development Kit (JDK).

To run the installer you need to use .bin file if you have it available on a CD or on Disk then , follow
these steps:
1.Logon to the system as the user whoever have previllages to work as WebLogic System Administrator.
2.Open a command-line shell.
3.Insert the WebLogic CD in the CD-ROM drive or disk where the bin file is located.

Change to the weblogic_platform directory on the CD or disk.
and Invoke the following command:

./server923_solaris32.bin -mode=console -Djava.io.tmpdir=/tmp -log=/export/home/wluser/logs/BEA_install.log

Note: Don't Copy the commands directly from pdf/webpage files to Unix/sunsolaris
console this may cause problem (Symbols can not be identified)

Sample installation Run given for your reference:

bash-3.00$ ls -lrt
-rwxr-xr-x 1 wluser beaproj 608240443 Dec 16 10:53 server922_solaris32.binbash-3.00$ ./server922_solaris32.bin mode=console
Invalid command line argument: [mode]. //Refer Note
#ERROR due to - missed before mode 2.Console Mode Installation
bash-3.00$ ./server922_solaris32.bin -mode=console
Extracting
0%....................................................................................................100% <----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Welcome:
--------
This installer will guide you through the installation of BEA Products. Type
"Next" or enter to proceed to the next prompt.
If you want to change data entered previously, type "Previous". You may quit the
installer at any time by typing "Exit".

Enter [Exit][Next]>

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
BEA Systems License Agreement:
------------------------------
BEA SYSTEMS, INC. SOFTWARE LICENSE AGREEMENT
USE OF SOFTWARE ORDERED FROM BEA SYSTEMS, INC. ("BEA") IS PROVIDED ONLY UNDER
LICENSE FROM BEA. PLEASE READ THE FOLLOWING
LICENSE CAREFULLY AND INDICATE YOUR ACCEPTANCE BY CLICKING THE ACCEPTANCE BOX.
CERTAIN CAPITALIZED TERMS ARE DEFINED IN
SECTION 11.

1. LICENSE TERMS
a. WebLogic SDK Use. The terms of this Section 1(a) are applicable to you if
you have registered as a WebLogic SDK
customer. Subject to the terms of this Agreement, BEA grants to you a
non-exclusive, non-transferable, royalty-free license
to use WebLogic SDK solely for Development Use and Scale-Limited Personal Use for
the number of users and/or developers and
the number of CPU's, Servers and/or at the Sites, as specified at the time of
registration. Third party software products or
modules supplied by BEA, if any, may be used solely with the Software. All rights
not specifically granted to you herein are
retained by BEA.
b. WebLogic SDK Pro Use. The terms of this Section 1(b) are applicable to you if
you have registered as a WebLogic SDK Pro
customer. Subject to the terms of this Agreement, BEA grants to you a
non-exclusive, non-transferable, fee-bearing license to use WebLogic SDK Pro
solely for Development Use and Scale-Limited Commercial Use for the number of
users and/or developers
and the number of CPU's, Servers and/or at the Sites, as specified on BEA's
invoice. Third party software products or modules supplied by BEA, if any, may be
used solely with the Software. All rights not specifically granted to you herein
are retained by BEA.
c. Evaluation Use. The terms of this Section 1(c) are applicable to you if you
have registered as an Evaluation Use
customer. Subject to the terms of this Agreement, BEA grants to you a
non-exclusive, non-transferable, license to use the
Use above value or select another option:
1 - Yes, I agree with the terms of the license
2 - No, I do not agree with the terms of the license

Enter option number to select OR [Down][Exit][Previous]> 1

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Choose BEA Home Directory:
--------------------------
"BEA Home" = [Enter new value or use default "/export/home/wluser/bea"]

Enter new BEA Home OR [Exit][Previous][Next]>

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Choose Install Type:
--------------------
Select the type of installation you wish to perform.
->1Complete
Install the following software components and examples:
- WebLogic Server
- Workshop for WebLogic Platform
2Custom
Choose software components to install and perform optional configuration.

Enter index number to select OR [Exit][Previous][Next]> 2

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Choose Components to install:
-----------------------------
Release 9.2.2.0
_____WebLogic Server [1] x
_____Server [1.1] x
_____Server Examples [1.2] x
_____Web Server Plug-Ins [1.3]
_____Workshop for WebLogic Platform [2] x
_____Workshop [2.1] x
_____Workshop Examples [2.2] x

Enter number exactly as it appears in brackets to toggle selection OR
[Exit][Previous][Next]> 2

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Choose Components to install:
-----------------------------
Release 9.2.2.0
_____WebLogic Server [1] x
_____Server [1.1] x
_____Server Examples [1.2] x
_____Web Server Plug-Ins [1.3]
_____Workshop for WebLogic Platform [2]
_____Workshop [2.1]
_____Workshop Examples [2.2]

Enter number exactly as it appears in brackets to toggle selection OR
[Exit][Previous][Next]>

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Choose Product Installation Directories:
----------------------------------------
BEA Home Directory: [/export/home/wluser/bea]
Product Installation Directories:
"Default Product Home" = [Enter new value or use default
"/export/home/wluser/bea/weblogic92"]

Enter new Default Product Home OR [Exit][Previous][Next]>
Dec 16, 2008 11:04:46 AM java.util.prefs.FileSystemPreferences$2 run
INFO: Created user preferences directory.

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Installing files..
0% 25% 50% 75% 100%
[------------------------------------------------]
[***************************************************]

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Installing JDK....
0% 25% 50% 75% 100%
[------------------------------------------------]
[***************************************************]
Performing String Substitutions...

Creating Domains...

<----------------------------------------------- BEA Installer - BEA Products ---------------------------------------------->
Installation Complete
Congratulations! BEA Products has been successfully installed to
/export/home/wluser/bea/weblogic92.
Press [Enter] to continue or type [Exit]>
bash-3.00$
2. Silent Mode Installation(Using XML):(Depricated)
Though it is depricated it is simple and smooth to use. That makes still WLA love to use this method, So I want to do an experiment it
Set the classpath in .profile as shown below
export CLASSPATH=/export/home/wluser//bea/jdk150_10/jre/lib/rt.jar:/export/home/wluser/bea/weblogic92/server/lib/weblogic.jar:
export PATH=/export/home/wluser/bea/weblogic92/common/bin:$PATH
bash
1. Log in to the Windows system.
2. Create a silent.xml file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode
Get the sample silent.xml form the below bea site
http://e-docs.bea.com/common/docs92/install/scripts/silent.xml
Note:Please keep (<)open and close(/>) tags in every line in the xml
becuase removed that not displaying the xml content in the blog

?xml version="1.0" encoding="UTF-8"?
bea-installer # open tag
input-fields # open tag
data-value name="BEAHOME" value="/export/home/wluser/bea"
data-value name="USER_INSTALL_DIR" value="/export/home/wluser/bea/weblogic92"
data-value name="INSTALL_MERCURY_PROFILING_TOOLS" value="true"
data-value name="COMPONENT_PATHS" value="WebLogic Server/Server"
data-value name="INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER" value="yes"
input-fields #close tag
bea-installer #close tag

./server922_solaris32.bin -mode=silent -silent_xml=silent1.xml -Djava.io.tmpdir=/tmp -log=/export/home/wluser/logs/BEA_install.log

To enable NodeManager following silent script can be used:
Note:Please keep (<)open and close(/>) tags in every line in the xml
becuase removed that not displaying the xml content in the blog
?xml version="1.0" encoding="UTF-8"?
bea-installer #open tag
input-fields #Open tag
data-value name="BEAHOME" value="/home/wluser/bea"
data-value name="USER_INSTALL_DIR" value="/home/wluser/bea/weblogic92"
data-value name="INSTALL_MERCURY_PROFILING_TOOLS" value="true"
data-value name="INSTALL_NODE_MANAGER_SERVICE" value="yes"
data-value name="NODEMGR_PORT" value="5513"
data-value name="COMPONENT_PATHS" value="WebLogic Server/Server"
data-value name="INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER" value="yes"
input-fields #closing tag
bea-installer #closing tag

The explanation of the above command:
1.To install the Bea in Silent mode , we need to specify the arguments as "-mode=silent"
2.and Specify the silent.xml path
Silent.xml contains, the BEA Home path,Installation Directory path,Need to specify which component need to install
3.Optionally we can specify the path for the temp directory for extracting the compressed jars
4.Optionally we can specify the log path which can be used for the Tracing the installation errors or exceptions.

Final Overview Steps for installation:
--This is taken from one of blog

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)
.
References
Oracle WebLogic 10.2 Installation Guide

JVM Troubleshooting Tools

2010-01-09T10:51:00.000-08:00

JVM Troubleshooting Tools:
If you look at Java tools section of the JDK 1.5 documentation page, you will see a group of new experimental tools called
"Troubleshooting Tools":
"jinfo": Prints configuration information for a given JVM process or a Java core file on the local machine or on a remote
machine through a debug server.
"jhat" - Heap Dump Browser: Starts a Web server on a Java heap dump file (eg, produced by "jmap -dump"), allowing the heap to
be browsed.
"jmap" - Memory Map: Prin00:24 10-01-2010ts shared object memory maps or heap memory details of a given JVM process or a Java
core file on the local machine or on a remote machine through a debug server.
"jsadebugd" - Serviceability Agent Debug Daemon: Attaches to a JVM process or a Java core file and acts as a debug server for
remote tools to connect.
"jstack" - Stack Trace: Prints a stack trace of threads for a given JVM process or a Java core file on the local machine or
on a remote machine through a debug server.
Note that not all functions described above are available on Windows systems. See next sections on how to use those tools
provided in JDK 1.6 on a Windows system.
1)'jinfo' - VM Option Value Checker
The first JVM troubleshooting tool I want try is the "jinfo" tool.
The "jinfo" tool included in the Windows version of JDK 1.6 only supports functions to view and modify HotSpot VM options of
the specified JVM process. Here is the "jinfo" command syntax:
C:\Pani>\Progra~1\java\jdk1.6.0_02\bin\jinfo
Usage: jinfo

Types of Clustering and WebLogic

2010-01-09T10:16:00.000-08:00

Introduction to Clustering

The WebLogic Clusters offer a cost-effective, high-performance, and highly available architecture for the cluster-aware applications. There are many types of clusters in various environments, and capacity plannings. Generally, clusters are classified based on their functionality. Here I am breifly discussing about the types of clusters they are:

Failover Clusters
Scalable High Performance Clusters
Application Clusters
Network Load balancing clusters
Other types of clusters

Let us examine the similarities and differences of each class of clusters.

Failover Clusters
This class of cluster is the most widely used in today’s e-commerce environment. Sometimes they are also called HA clusters or segregated clusters. With this type, the emphasis is on complete avoidance of unplanned downtime and also on achieving high availability.

If one of the nodes in a cluster becomes unavailable, due to either planned downtime for maintenance or unplanned downtime due to failure, another node takes over to provide the service to the end-user—a process known as failover. When failover occurs, users who are accessing the cluster service continue to access the service, and are unaware that it is being provided from a different server (node). This architecture emphasizes the availability of the database or application service, rather than performance or load balancing.

High availability clusters
allow multiple servers, in conjunction with shared disk storage units, to quickly recover from failures. Hardware or software failures, affecting either a critical component or an entire system, trigger a failover from one system in the cluster to another. Application processing and access to disk-based data is typically restored within minutes, although recovery times vary depending upon the specific characteristics of the application and the system configuration.

Scalable High Performance Clusters
This class of cluster provides scalability, high-performance, load balancing, and high availability through the use of parallel middleware. These are also sometimes called parallel clusters or high performance computing clusters (HPCC). They provide a single system image, or in other words, the application can be executed on any of the servers within the cluster. They are used to execute compute-intensive and data-intensive problems by running the job on multiple nodes at the same time.

These clusters utilize parallel-aware software that breaks the task down into smaller chunks, which are dispatched across a network of interconnected systems. The network processes the chunks concurrently and communicates with the nodes using message-passing libraries to coordinate and synchronize the results. Cluster-aware applications take advantage of the network architecture in three ways:

Parallel Computing, Multi-Threading, and Modularization
Load Balancing
Automatic Failure

Parallel database clusters like Oracle Real Application Clusters, IBM Sysplex Database Cluster, and Beowulf Computers fit into this group of clusters. Beowulf clusters are of particular interest to the scientific and educational communities. Beowulf clusters are built by using commodity systems – PCs, workstations, or servers running software such as Linux. They feature a parallel computing system consisting of multiple interconnected nodes and are able to execute parallel jobs.
Through message passing, nodes synchronize data and share results. Oracle RAC uses message passing to process requests and update data on each node, resulting in fast data access and a consistent database.

Application Server Clusters
Nodes running application server clusters are connected to provide availability and scalability. In this type of cluster, each node runs an instance of the application server. They run the application server independently from each other’s instance. There is no concept of failover. When clustered in this way, the state of certain objects is maintained synchronously. Web server clients can connect to either of the application server instances. Application servers such as WebLogic Server, Websphere, and Oracle Application server are examples of this category of clusters.

As an example, the WebLogic Server cluster consists of multiple copies of the WebLogic program running simultaneously and working together to provide increased scalability and reliability. The cluster appears to the web server clients as a single WebLogic Server instance. In WebLogic deployment, Servlets, JSPs, EJB, Remote Method Invocation (RMI) objects, Java Messaging Service (JMS) destinations, and Java Database Connectivity (JDBC) connections are usually clustered.

Clustering in J2EE, as in the Oracle Applications server, is implemented across a number of tiers, namely the client tier, Web tier, EJB tier, and EIS tier. Every tier has load balancing and failover.

Other Types of Clusters
The term cluster is loosely used to specify a condition when two networking components or two storage units are joined to provide backup and failover facility. Two or more clusters can also be located at remote locations and be linked to form a global cluster. Some of the other widely known clusters include:

NetApp Filer Clusters
Network Load Balancing Clusters
Global Clusters

SSL Configuaraion with Oracle Weblogic Server 11g

2009-11-27T22:36:00.000-08:00

Hey Smart WLA!! here I am again for sharing my neew experiment on SSL Configuration on Oracle WebLogic 11g. Initially I thought of sharing in step-by-step sequance for the experiment.

***********************************************************************************
Step1: Create a new WLS domain ***********************************************************************************
(If you already have a domain , Not required to create it ...Just enable the SSL port in WebLogic Admin console)
run config.cmd script
MW_HOME=\Oracle\MiddlewareMW_HOME\wlserver_10.3\common\bin\config.cmd
or config.sh in Solaris box
create a new weblogic configuration
select next...
select OracleWebLogic Server Domain
select next...
Select Express Installation
select next...
username/password = weblogic/weblogic10
select next...
select default development mode/Sun SDK 160_11
select next...
select the configuration name=domain name = ssldomain
click create
in my case - my domain is created under : \Oracle\Middleware\user_projects\domains\ssldomain
This domain is created with only http listen port(7001) enabled. .Now, enable the SSL listen port as below:
go to Servers --> myserver --> general tabselect the "SSL Listen Port Enabled"
By default this will listen on port 7002 using default weblogic demo certificates.
click on apply. At this point - WLS is configured for one way SSL using default demo certificates.
Restart the server.

***********************************************************************************
Step 2: Getting our own Certificate and setup SSL on Weblogic
***********************************************************************************
As of now, Our server is using default private key/default public key(certificate) and default trust.
Now, steps to use your own certificate and setup SSL on Weblogic is as follows:
1. get your own private key/certificate/trust for your certificate
2. create identity keystore (which will have your private key + certificate)
and create trust keystore (which will have trust cert for your own digital cert)
3. Use the identity and trust keystore created in step 2
and configure WebLogic to replace demo keystores with your own keystores.
Now, details for step 1:
create private key using keytool command
- --go to your domain dir and run setENV.cmd or setEnv.sh script
---now run the following keytool command to create private key
(use your own name and rest you can keep the same)
C:\Oracle\Middleware\user_projects\domains\ssldomain> keytool -genkey -keyalg RSA -alias mykey -keystore panikeystore.jks
Enter keystore password: weblogic10
Re-enter new password: weblogic10
What is your first and last name? [Unknown]: Sarangapani
What is the name of your organizational unit? [Unknown]: support
What is the name of your organization? [Unknown]: MyCompany
What is the name of your City or Locality? [Unknown]: Hyderabad
What is the name of your State or Province? [Unknown]: AP
What is the two-letter country code for this unit? [Unknown]: IN
Is CN=Sarangapani, OU=support, O=MyCompany, L=Hyderabad, ST=AP, C=IN correct? [no]: yes

Enter key password for (RETURN if same as keystore password): weblogic10
Re-enter new password: weblogic10
As a result you obtain a file: panikeystore.jks (in the same dir),
containing a private key, and a self-signed public key
-------------------------------------------------------------
Now, its time to send your public key for getting it signed by trusted authority (we will send it to verisign)
This is done by retrieving the CSR (Cert Signature Request) from panikeystore.jks and sending it to one of the Certificate Authorities like VeriSign.

Run the following command to get CSR:
C:\Oracle\Middleware\user_projects\domains\ssldomain>keytool -certreq -keystore panikeystore.jksEnter keystore password: weblogic10
-----BEGIN NEW CERTIFICATE REQUEST-----
MIIBqzCCARQCAQAwazELMAkGA1UEBhMCSU4xEjAQBgNVBAgTCUthcm5hdGFrYTESMBAGA1UEBxMJ
QmFuZ2Fsb3JlMQwwCgYDVQQKEwNCRUExEDAOBgNVBAsTB1N1cHBvcnQxFDASBgNVBAMTC1JhbWFr
cmlzaG5hMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCxB2BdG1iBsIJvK3x2lcnn7GclEShT
ib5sbiHa7h1DBqMZZc1lezGI55Nz1YSUZukgj7aZj9N4K7haV93LoD4pNREpLcp7DGxNODNclp5F
DHTevqWx0rXqjwei5Euh2f5ACSFo3tL5o5QXkS3o4TeZ2QSypAyeu/+qtnk7Od/xGQIDAQABoAAw
DQYJKoZIhvcNAQEEBQADgYEAXOYBI9LJPBVA+OyK/4od6ORkJnew/K7WWMjeLwZjwKI7INCHw4VG
dG0v7z2JnSpgi43fipWyywt5fmXZqfKNtki5SNxV3kLHAWxardgZbZ8H/kO95CtbOcFtagPLH8pi
+rp2iGFSlH6+UYtW1qXL3FM0srIxam6RgYqCixf5gGQ=
-----END NEW CERTIFICATE REQUEST-----
C:\Oracle\Middleware\user_projects\domains\ssldomain>
===============================================================
We need to copy and paste all this (including -----BEGIN NEW CERTIFICATE REQUEST----- and -----END NEW CERTIFICATE REQUEST-----) to the Certification Authority.
open a notepad and copy it there.

Now we will go to verisign site to get this signed.

Go to
https://www.verisign.com/cgi-bin/clearsales_cgi/leadgen.htm?form_id=0110&toc=w63780188130110000&ra=65.205.251.51&email=

Enter your information and follow the instructions to submit the CSR

First Name: Sarangapani
Last Name: M
e-mail: your email@MyCompany.com
ompany: MyCompany
phone: 1234567890
state: Outside the US or Canada
Zip: 500081
Country: India
select "research only"
select "no budget"
select "research only"
click "Submit" button.
click the "Continue" button
again, click the "Continue" button
====================================
Technical details:
enter you details.................................
E-mail - your email. specify company email id. (eg. your email@MyCompany.com)====================================
select server platform = "all others" and paste your CSR
if it ask for password/chalenge phrase = weblogic10
====================================
once done, verisign will send you your digital cert in an email.
when you receive your email goto step3.
************************************************************************************
Step 3: Creating RootCA certification files(testrootca.cer) and PEM content of public key file(mycert.pem)
************************************************************************************
Verisign will then send you an email with the PEM content of the public key.

Scroll at the end of the email and Save it under a file name mycert.pem.

It also contains a link to get a root CA cert for your certificate i.e. a link to download
the Test CA Root.
follow the link to download Test CA Root - getcacert.cer.
save it under your domain dir.

This file is in binary format.
Lets convert this in txt format.
double click on this file.

click on details tab page --> copy to file (at the bottom) --> base 64 encoded x.509 format --> save as testrootca.cer under your domain dir.

now you have
your cert - mycert.pem
test ca cert - testrootca.cer

now open a textpad editor and merge testrootca.cer in your mycert.pem

so at the end -you will have
your cert - mycert.pem (which will have a chain i.e. your cert + test ca root)
test ca cert - testrootca.cer

**********************************************************************************
Step 4: Creating Identity key Store and Trust Key Store
**********************************************************************************
Import the public key into your identity keystore. It will go on the same alias as the private key:
C:\Oracle\Middleware\user_projects\domains\ssldomain>keytool -import -alias mykey -file mycert.pem -keystore panikeystore.jks
Enter keystore password: weblogic10

Top-level certificate in reply:

Owner: OU=For VeriSign authorized testing only. No assurances (C)VS1997, OU=www.verisign.com/repository/TestCPS Incorp. By Ref. Liab. LTD., O="VeriSign, Inc"Issuer: OU=For VeriSign authorized testing only. No assurances (C)VS1997, OU=www.verisign.com/repository/TestCPS Incorp. By Ref. Liab. LTD., O="VeriSign, Inc"Serial number: 52a9f424da674c9daf4f537852abef6eValid from: Sun Jun 07 05:30:00 IST 1998 until: Wed Jun 07 05:29:59 IST 2006Certificate fingerprints: MD5: 40:06:53:11:FD:B3:3E:88:0A:6F:7D:D1:4E:22:91:87 SHA1: 93:71:C9:EE:57:09:92:5D:0A:8E:FA:02:0B:E2:F5:E6:98:6C:60:DE
... is not trusted. Install reply anyway? [no]: yes
Certificate reply was installed in keystore

C:\Oracle\Middleware\user_projects\domains\ssldomain>
===========================================================
Lets create the trust keystore:
C:\Oracle\Middleware\user_projects\domains\ssldomain>keytool -alias mytkey -trustcacerts -import -file getcacert.cer -keystore panitruststore.jks -storepass weblogic10

Owner: OU=For VeriSign authorized testing only. No assurances (C)VS1997, OU=www.verisign.com/repository/TestCPS Incorp. By Ref. Liab. LTD., O="VeriSign, Inc"Issuer: OU=For VeriSign authorized testing only. No assurances (C)VS1997, OU=www.verisign.com/repository/TestCPS Incorp. By Ref. Liab. LTD., O="VeriSign, Inc"Serial number: 52a9f424da674c9daf4f537852abef6eValid from: Sun Jun 07 05:30:00 IST 1998 until: Wed Jun 07 05:29:59 IST 2006Certificate fingerprints: MD5: 40:06:53:11:FD:B3:3E:88:0A:6F:7D:D1:4E:22:91:87 SHA1: 93:71:C9:EE:57:09:92:5D:0A:8E:FA:02:0B:E2:F5:E6:98:6C:60:DE
Trust this certificate? [no]: yes
Certificate was added to keystore

C:\Oracle\Middleware\user_projects\domains\ssldomain>
===========================================================
the above command will create panitruststore.jks i.e., our trust keystore.

so at this time - we have
1. identity keystore = panikeystore.jks
2. trust keystore = panitruststore.jks
cheers.. you are almost done.
now just need to configure wls to use the above keystores instead of default demoidentity
and default demo trust keystore.

**********************************************************************************************Step5: Step 5: Configuring Keystores and SSL in Weblogic11g console
**********************************************************************************************so Finally, we all done in creating our own custom Identity keystore which contains our private key + our certificate signed by VeriSign.
and Our own custom trust keystore which contains test root CA.

now lets setup SSL on your server using your custom keystores.

Our server is currently using default demo cert.

Setup SSL in the admin server console under "Keystores & SSL" Tab Page.
Click on "change" and then select "Custom Identity and Custom Trust" from the drop down menu. click continue.
Then specify the full path for Identity(panikeystore.jks) and Trust Keystore(panitruststore.jks). Specify the passwords for both the stores. click continue.
Now specify the password and alias for private key. apply the changes
and you will need to restart the server.

The above steps will configure SSL. WLS will use the private/public key (certificate) from our Identity keystore and the trust certificate from the trust keystore.

Restart the server and test it.
go to https://localhost:7002/console
it will warn you as this is a test cert.
you are done setting up one way SSL with your own custom keystores.

Cheers,
Your Pani the WLA

Sun One WebServer7 Proxy for Weblogic 11g

2009-11-18T08:21:00.000-08:00

Installation Steps

I am going to install sun webserver on Solaris operating environment. Every operating environment will have different supporting installation bundles will be available for download. Download the sjsws-7_0-solaris-sparc[1].tar from sun and Extract it into one folder (Ex: sun)

Step2: Go to sun folder and execute the following command

$HOME/sun$ ./setup --console
You are running the installation program for Sun Java System Web Server 7.0.You will be asked to specify preferences that determine how Sun Java System WebServer 7.0 is installed and configured.

Are you sure? [yes]
To accept the default, press Enter.
To provide a different answer, type the information at the command prompt and
then press Enter.
Welcome to the Sun Java System Web Server 7.0 Installation Program

Sun Microsystems, Inc. ("Sun") SOFTWARE LICENSE AGREEMENT ("SLA") andENTITLEMENT for SOFTWARE
<--[28%]--[ENTER To Continue]--[n To Finish]-->
<--[57%]--[ENTER To Continue]--[n To Finish]-->
<--[86%]--[ENTER To Continue]--[n To Finish]-->
Have you read the Software License Agreement and do you accept all terms [no] {"<" goes back, "!" exits}? Yes
Sun Java System Web Server 7.0 Installation Directory [/sun/webserver7] {"<" goes back, "!" exits}: $HOME/sun/webserver7/
Specified directory $HOME/sun/webserver7
does not exist Create Directory? [Yes/No] [yes] {"<" goes back, "!" exits} Yes
Select the Type of Installation
1. Express
2. Custom
3. Exit
What would you like to do [1] {"<" goes back, "!" exits}? 2
Component Selection
1. Server Core
2. Server Core 64-bit Binaries
3. Administration Command Line Interface
4. Sample Application
5. Language Pack
Enter the comma-separated list [1,2,3,4,5] {"<" goes back, "!" exits}: 1,3
Based on component dependencies for your selection...
The following components will be installed:
Server Core

Administration Command Line Interface

Java Configuration
Sun Java System Web Server 7.0 requires Java Standard Edition. Provide the path to a Java Standard Edition 1.5.0_09 or greater.
1. Install Java Standard Edition 1.5.0_09
2. Reuse existing Java SE 1.5.0_09 or greater
3. Exit
What would you like to do [1] {"<" goes back, "!" exits}? 2
Enter the path to an existing, compatible Java Standard Edition installation. [] {"<" goes back, "!" exits} $HOME/Oracle/Middleware/jdk160_11
Administration Options
1. Create an Administration Server and a Web Server Instance
2. Create an Administration Node
Enter your option [1] {"<" goes back, "!" exits} 1
This panel collects some required information for creating an administrationserver. Host Name [$HostName] {"<" goes back, "!" exits} $HostName
SSL Port [8989] {"<" goes back, "!" exits} <
Administration Options
1. Create an Administration Server and a Web Server Instance
2. Create an Administration Node
Enter your option [1] {"<" goes back, "!" exits} 1
This panel collects some required information for creating an administrationserver. Host Name [$HostName] {"<" goes back, "!" exits} $HostName
SSL Port [8989] {"<" goes back, "!" exits} 9898
Create a non-SSL Port [yes/no] [no] {"<" goes back, "!" exits}:
Administrator User Name [admin] {"<" goes back, "!" exits}
Administrator Password: Retype Password:
A web server instance is created as part of the installation. This panel letsyou customize some of the server settings.
Server Name [$HostName] {"<" goes back, "!" exits} sunonepani
HTTP Port [8080] {"<" goes back, "!" exits} 8686
Document Root Directory [$HOME/sun/webserver7/https-sunonepani/docs] {"<" goes back, "!" exits}
Product : Sun Java System Web Server
Location : $HOME/sun/webserver7
Disk Space : 115.43 MB------------------------------------------------------ Server CoreAdministration Command Line Interface Ready to Install
1. Install Now
2. Start Over
3. Exit
Installation What would you like to do [1] {"<" goes back, "!" exits}? 1 Installing Sun Java System Web Server-1%--------------25%-----------------50%-----------------75%--------------100%Installation Successful.
Next Steps:
1. Start the Administration Server by executing: $HOME/sun/webserver7/admin-server/bin/startserv
2. You can access the Web Admin Server by accessing the following
URL:https://$hostname:9898/
3. Refer to the installation log file at$HOME/sun/webserver7/setup/Sun_Java_System_Web_Server_install.logfor more details.

WebServer Proxy Configuration
Step 3: Copy the proxy plugin (ex:libproxy_61.so)
from $MW_HOME/weblogic10_3/server/plugins/solaris/sparc/ to sun/webserver7/http-instancename/config/
Step 4: Add the following lines in obj.conf file
$HOME/sun/webserver7/https-sunonepani/config]$ vi obj.conf
Open a Object tag and keep it as below under <>
name="weblogic" ppath="*/weblogic/*"
Under Object tag body means before closing the object tag , we need to keep as below ...
Service fn=wl_proxy WebLogicHost=Myhostserver WebLogicPort=8992 PathTrim="/weblogic"
then Close the Object tag

Step 5: Add the following lines in magnus.conf file
$HOME/sun/webserver7/https-sunonepani/config]$ vi magnus.conf
Init fn="load-modules"funcs="wl_proxy,wl_init"shlib="libproxy_61.so" Init fn="wl_init"

Step 6: start the weblogic instance which is under wl_domain
$HOME/$WL_DOMAIN/bin]$ startWebLogic.sh

Step 7: start the sun one admin server instance
$HOME/sun/webserver7/admin-server/bin]$ startserv

Step 8: start the sun one webserver instance
$HOME/sun/webserver7/https-sunonepani/bin]$ startserv

Good References for WL domain creation
Dynamic Domain creation

Apache Installation & Configuaration

2009-11-17T02:35:00.000-08:00

Here we were experimenting with Apache Webserver Installation and Configuaration plug-in with the weblogic server

Installation made simple Steps which you can follow them

Step1: Download the any stable version of httpd for your operating environemnt (Now I am intersted in Solaris) suitable binaries given as tar/zip file (Ex: httpd-2.2.11.tar) and Extract it

tar -xvf httpd-2.2.11.tar

Step2: Go to httpd-2.2.11 directory and execute the confiure command to configure the apache in one folder (Ex: apache2)

cd httpd-2.2.11
./configure --prefix=$Home/apache2

Step3: We need to execute the below commands to build I mean compile the binaries

make
make install

Step4: take the backup of httpd.conf file

cd apache2/conf
cp httpd.conf httpd.conf_original

Step5: Edit the httpd.conf configuration file

vi httpd.conf
ServerRoot "$Home/apache2"
(ServerRoot is the path to the server's configuration, error and log files.It is possible to change this path, provided all the necessary files are copiedto the new location accordingly)
Listen IPAddress:Port (Ex: Listen 4.192.50.25:9999)
LoadModule weblogic_module modules/mod_wl_22.so
User wlusername
#main content of wl application details to update in httpd.conf file
Open tag of IfModule
#keep the info in open tag of IfModule ---mod_weblogic.c
WebLogicCluster hostname:9902,hostnamevir1:9902
MatchExpression *.jsp
close tag of IfModule
Open tag of Location
#keep /application root folder name in Lacation
SetHandler weblogic-handler
DynamicServerList ON
HungServerRecoverSecs 600
ConnectTimeoutSecs 40
WLCookieName JSESSIONID
DebugConfigInfo OFF
Debug ON
WLLogFile /$Home/apache2/logs/web1.log
ConnectRetrySecs 2
Idempotent ON
FileCaching ON
WLProxySSL OFF
SecureProxy OFF
Debug OFF
Close tag of Location

ServerAdmin sarangapani.matoori@gmail.com
ServerName 4.192.50.25 (we can use dns name , if we don't have it then we can use the ip)

Step6:copy the mod_wl_22.so module file from $Home/wl923/bea/weblogic92/server/plugin/solaris/sparc to $Home/apache2/modules
cp $Home/wl923/bea/weblogic92/server/plugin/solaris/sparc/mod_wl_22.so $Home/apache2/modules/
Step7:check the status of apche configuaration is ok
cd $Home/apache2/bin
apachectl -t
Step8: Now the starting your newly installed Apache webserver
apchectl -k start or httpd -k start

Step9: Access the application with the apache port
http://hostip:port(which%20is%20kept%20in%20httpd.conf/ file)/ProjectName/jsp/Logon.jsp
Step10: Stop the Apache
apchectl -k stop or httpd -k stop

Good Reference for creating your WL domain:
Dynamic WebLogic Domain configuration