Friday Dec 26, 2014

JSSE and WebLogic Server in WebLogic Server 11g

 Recently, several customers want to migrate to JSSE, because they would like to have stronger cipher suites.

If you have WebLogic Server 10.3.2 or earlier versions, you will need to upgrade your Weblogic Server to the latest 11g.
There is no supported way to enable JSSE in these versions.


To enable JSSE in weblogic server 10.3.3 and later, you can add a property to JAVA_OPTIONS as described below:

    -Dweblogic.security.SSL.enableJSSE=true (WLS 10.3.3)
http://docs.oracle.com/cd/E14571_01/web.1111/e13707/ssl.htm#BABIJEJD
    -Dweblogic.ssl.JSSEEnabled=true (WLS 10.3.4 and later)
http://docs.oracle.com/cd/E21764_01/web.1111/e13707/ssl.htm#BABIJEJD

Additional Details here:
http://docs.oracle.com/cd/E14571_01/web.1111/e13707/ssl.htm#SECMG494

Please notice that as this is a new feature, there are several recommended patches for known issues:
For WebLogic Server 10.3.3:
SHA2 Certificate Throws Log Message "Ignoring The Trusted CA Certificate" (Doc ID 1538488.1)

For WebLogic Server 10.3.5 and 10.3.6 make sure you are using the latest PSU delivered:
e.g:
Oracle WebLogic Server Patch Set Update 10.3.5.0.7 Fixed Bugs List (Doc ID 1544306.1)
Oracle WebLogic Server Patch Set Update 10.3.6.0.9 Fixed Bugs List (Doc ID 1935048.1)   

Enjoy! 

Wednesday Oct 08, 2014

Error Correction Policy and Lifetime Support for Weblogic Server

When you have a support contract you might want to know if you can request new patches.
Then, you might be interested in reading this doc.
Error Correction Support Dates for Oracle WebLogic Server (Doc ID 950131.1)

The document below explains the support stage you might have e.g: Premier Support, or  Extended
Support, and what are your support dates.


Enjoy!

Tuesday Aug 19, 2014

How to start WebLogic Server using default scripts?

There are a few common issues reported when starting weblogic server using scripts.
1. User is not able to access weblogic console.
2. After a few days/hours weblogic server stops abruptly.
3. When user closes putty, they are not able to connect to weblogic server anymore.
4. When user closes windows command prompt, they are not able to connect to weblogic server anymore.
5. Weblogic is started using startManagedWebLogic.cmd/startManagedWebLogic.sh.


By default, WebLogic Server does not run in background mode, so after you close the window the process finishes as well.

In Linux/Unix based platforms, you need to use:

nohup ./startManagedWebLogic.sh <Server> <URL> &

In Windows platforms, you need to start Managed Servers using Windows Services:

How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)

http://docs.oracle.com/cd/E23943_01/web.1111/e13708/winservice.htm


There a few more reasons that could cause similar symptoms, like JVM crash, signals sent by the Operating System, and many other reasons. 
But the above steps is the first one to start.

Enjoy!

Monday Apr 21, 2014

How to monitor JMS Queue counts using JConsole ?

The most common way to monitor your JMS resources is by using weblogic console, e.g.:

http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/jms_servers/MonitorJMSServers.html

You can also use WLST

http://docs.oracle.com/cd/E23943_01/web.1111/e13738/wlst.htm#i1047470

If you like JConsole, here is the trick:


1. Set your environment
   (Linux) . ./setDomainEnv.sh
   (Windows) setDomainEnv.cmd


2. Invoke jconsole using the arguments below    

jconsole -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote -J-Dcom.sun.tools.jconsole.mbeans.keyPropertyList=Location,type,Type,j2eeType,name,Name -debug


3. See messages counts as follows:


Related to the JMSServer
JMSServerRuntime > <MyJMSServer> > <MyWebLogicServer>  > Attributes > MessagesCurrentCount


Related to the a JMS Queue:
JMSDestinationRuntime > <MyQueueJNDIName>  >MyWebLogicServer > MyJMSServer > Attributes


References:
https://blogs.oracle.com/WebLogicServer/entry/managing_weblogic_servers_with


Tuesday Nov 26, 2013

How to enable Weblogic Server debugs using WebLogic Console?

This is a very useful topic for those that would like to have a first insight on why an issue is occuring.

1. The easiest way to enable debug flags in WebLogic Server is to use weblogic console. This is done in:

Environment > Servers > MyServer > Debug > weblogic

Then, enable the level of debug you need, e.g.: security, servlet, jdbc.

This change does not require weblogic Server Restart.

2. You need Make sure the severity is set to debug in weblogic console:

Environment > Servers > MyServer > Logging >Advanced > Minimum severity to log: Debug

This change requires server restart.

Enjoy!

About


My name is Luz Mestre. I work as Principal Technical Support Engineer at Oracle Support. I'll post here the most interesting challenges I have in my daily work. The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.

Search

Categories
Archives
« March 2015
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
    
       
Today