WebLogic Issues & Solutions

Apache Derby DataSource configuration in Weblogic Server

noreply@blogger.com (Sunil Nandargi) — Thu, 24 Oct 2013 10:45:00 +0000

Most of you might already worked on this. Anyone who has not got chance to work on it and a note to myself on the step by step Apache Derby datasource configuration in Weblogic.

Steps to Configure Apache Derby Datasource in Weblogic

A. Weblogic v10.3.3 and below
Pre-requisites:
--JDK 1.7 with Java DB [Apache Derby distribution] included.
Java DB is Oracle's supported distribution of the Apache Derby open source database. It supports standard ANSI/ISO SQL through the JDBC and Java EE APIs.

1a. Java DB startup - Navigate to JDK7 <JAVA_HOME_JDK7>/db/bin directory and execute the startNetworkServer.bat or startNetworkServer.sh per your OS preference.
By default, the Java DB listens on TCP/IP port 1527. The listen port can always be modified, refer this documentation.
1b. Download and supplement the Derby JDBC driver jar files to the Weblogic domain classpath in setDomainEnv.cmd or setDomainEnv.sh under <DOMAIN_HOME>/bin. Restart the Weblogic domain for the Derby JDBC driver class to be accessible.
derbyclient.jar - <JAVA_HOME_JDK7>/db/lib/derbyclient.jar
derbytools.jar - <JAVA_HOME_JDK7>/db/lib/derbytools.jar

Example:
set JAVA_HOME_JDK7=E:\Java\jdk1.7.0_25
set PRE_CLASSPATH=%JAVA_HOME_JDK7%\db\lib\derbyclient.jar;%JAVA_HOME_JDK7%\db\lib\derbytools.jar

B. Weblogic v10.3.4 and above
Starting version Weblogic 10.3.4 the Apache Derby DB is included in the installation along with Weblogic.

1a. Java DB startup - Set DERBY_FLAG to true in your setDomainEnv.cmd or setDomainEnv.sh under <DOMAIN_HOME>/bin. This setting would launch Java DB startup during the startup of Weblogic instance. Restart the Weblogic instance to bring up the Java DB along with Weblogic.

2. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

3. In the left pane, navigate to Services > JDBC > Data Sources

4. On the right pane, click on New to add new Data Source

5. Specify Name and JNDI name of the Data Source per your preference. Select the Database Type as Derby and appropriate Database Driver. Click Next

6. I have unchecked the Supports Global Transactions option.Again it is per your preference.

7. Specify the Connection properties and click Next

Database Name can be absolute path location of the database files to be saved.

Example: E:\DerbyDB\ApacheDerbyDB

Or
It can be relative path location, you will have to just mention dbName and the database files will be created under <JAVA_HOME_JDK7>\db\bin\ [Option A] or <WEBLOGIC_HOME>\common\derby\bin\ [Option B]

Example: If the dbName is blogdomain_db, E:\Java\jdk1.7.0_25\db\bin\blogdomain_db or C:\Middleware_10.3.4\wlserver_10.3\common\derby\bin\blogdomain_db would be the location of the database files.

Host Name where the database runs.

Port on which the database listens for connections

Username and Password

8. Verify Connection properties, click Test Configuration and proceed Next. If you notice under properties create=true is automatically added, the database will be automatically created if not present already.

9. Select targets for the Data Source. Click Finish

10. In the Change Center of the Administration Console, click "Activate Changes".

Flush Weblogic Cache

noreply@blogger.com (Sunil Nandargi) — Tue, 23 Jul 2013 10:11:00 +0000

Can't see the newly developed changes after the deployment of the build to Weblogic Server. This is because Weblogic Caches the application so that when you access the applications it can load faster every second attempt after the deployment. The only way to get new changes to be visible is to get rid of old one's. How is that done? Answer: Flush the Weblogic Cache on all Weblogic nodes where Applications is deployed to. Usually clearing the Weblogic cache results in resolving some unknown problems too.

Use the directives below to Flush the Weblogic Cache:

1. Shutdown the Weblogic nodes where Applications is deployed to.

2. Delete tmp and cache folders/directories located under <DOMAIN_HOME>/servers/<WEBLOGIC_NODE_SERVER>
OR
Rename or delete the WEBLOGIC_NODE_SERVER folder/directory located under <DOMAIN_HOME>/servers

3. Start the Weblogic nodes.

How to Prevent the 'WLS_DIAGNOSTICSxxxxxx.DAT' file from Growing Too Large

noreply@blogger.com (Sunil Nandargi) — Tue, 20 Sep 2011 21:33:00 +0000

The Archive component of the WebLogic Diagnostic Framework (WLDF) captures and persists all data events, log records, and metrics collected by WLDF from server instances and applications running on them. You can configure WLDF to archive diagnostic data to a file store or a Java Database Connectivity (JDBC) data source. If you choose to archive diagnostic data to a file store, this file would stored in <DOMAIN_NAME>/servers/<SERVER_NAME>/data/store/diagnostics.

Under some conditions, these archived files may grow bigger and bigger and can not be removed automatically if you have not done special configuration. e.g., if JDBC connection profiling is enabled, etc.

There are several ways to prevent the diagnostic archive files from growing too large:

1. For weblogic 10.0 and above, you can configure retirement features to periodically delete old diagnostic data from the archives.

For example, you can configure data of a specified age should be retired, or that the oldest data saved should be retired when your diagnostic file reaches a specified size.

2. For WebLogic 9.2.* and 10.*, if you want to permanently switch off the diagnostics data collecting, you can use the following arguments in your server startup script:

-Dcom.bea.wlw.netui.disableInstrumentation=true

-D_Offline_FileDataArchive=true

-Dweblogic.connector.ConnectionPoolProfilingEnabled=false

Steps to permanently switch off the diagnostics data collecting

Shutdown your WebLogic server.

Clear the <SERVER`>/data/store/diagnostics directories.

Apply the startup parameter, e.g, in setDomainEnv.sh, modify JAVA_OPTIONS:

JAVA_OPTIONS="${JAVA_OPTIONS} -D_Offline_FileDataArchive=true -Dcom.bea.wlw.netui.disableInstrumentation=true -Dweblogic.connector.ConnectionPoolProfilingEnabled=false" export JAVA_OPTIONS

Restart your WebLogic server.

Circular Group reference in external authenticator causes LDAP to hang

noreply@blogger.com (Sunil Nandargi) — Thu, 18 Aug 2011 22:13:00 +0000

The impact of the Circular Group reference in external authenticator causes LDAP to hang and impacts to Outage. By default, Oracle WebLogic Server does not check for Group circularity for any externally configured LDAP Authenticators (iPlanet, Active Directory, Novell, Open LDAP, etc.).

Circular Group reference example:

If Group A is a member of Group B
and Group B is a member of Group A

When a circular group [as above] exists in the backend LDAP, so many LDAP connections are created (due to the backend LDAP group having itself as a member), that a server crash can result.

Solution

A. Enabling the Ignore Duplicate Membership Flag

Starting from Oracle WebLogic Server 8.1 SP4 a new flag "IgnoreDuplicateMembership" is introduced. You can enable this flag in the Administration Console while configuring any external Authentication Provider. When the flag is enabled and a circular group exists, the server ignores the duplicate group and generates a warning (written to the log). By default, this flag is unchecked (disabled). Although this flag works in Production Mode, Oracle recommends that you use it only in Development Mode, as it can adversely affect performance.

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the security realms

3. In the right pane, click on myrealm

4. In the Settings for myrealm window navigate to Providers > Authentication tab.

5. Click on the Authentication Provider from the list which has the circular group issue. In my case it is ActiveDirectoryAuthenticator.

6. In the Settings for ActiveDirectoryAuthenticator window navigate to Configuration > Provider Specific tab.

7. Enable Ignore Duplicate Membership parameter

8. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

9. Restart all the Weblogic Server instances specified in the Restart-Checklist for changes to take effect.

B. Setting the Group Membership Searching to Limited

As an alternative workaround, you can set "Group Membership Searching"
to "limited" (the default is "unlimited") in the Authentication Provider
configuration. For configurations that use only the first level of nested group hierarchy, this attribute allows improved performance during user searches by limiting the search to the first level of the group.

If a limited search is specified, the Max Group Membership Search Level attribute must be specified. If an unlimited search is specified, the Max Group Membership Search Level attribute is ignored.

For example, if Max Group Membership Search Level attribute is set to 1, a search for membership in Group A will return direct members of Group A. If Group B is a member of Group A, the members of Group B will also be found by this search. However, if Group C is a member of Group B, the members of Group C will not be found by this search. Any positive number - Indicates the number of levels to search.

Note that when Use Token Groups For Group Membership Lookup is used during authentication, all the groups are returned in a single call, and the recursion limits and depth limits do not apply. They will apply in management operations.

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the security realms

3. In the right pane, click on myrealm

4. In the Settings for myrealm window navigate to Providers > Authentication tab.

5. Click on the Authentication Provider from the list which has the circular group issue. In my case it is ActiveDirectoryAuthenticator.

6. In the Settings for ActiveDirectoryAuthenticator window navigate to Configuration > Provider Specific tab.

7. Set Group Membership Searching to limited and Max Group Membership Search Level to a value that you think is appropriate. In my case I am setting the value to "3"

8. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

9. Restart all the Weblogic Server instances specified in the Restart-Checklist for changes to take effect.

That's it.
Please do leave your valuable comments.

JSAFE_PaddingException: Could not perform unpadding: invalid pad byte

noreply@blogger.com (Sunil Nandargi) — Tue, 16 Aug 2011 17:46:00 +0000

While working on a issue it was found the Managed server was not able to Authenticate to its Admin Server in a domain. As i was able to restart the Admin Server with the boot.properties on its host, so i tried copying the same boot.properties to Managed server host followed Managed Server startup. While startup the boot.properties will be read and immediately JSAFE_PaddingException: Could not perform unpadding: invalid pad byte was fired.

After some google it was stated that all domain as different salt [SerializedSystemIni.dat] for encryption so sometime if you miss to update the encrypted password with the new salt you get this error.

Below is the log excerpt for the Error.

[com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.].>
<Aug 3, 2011 8:33:02 PM GMT> <Critical> <Security> <BEA-090518> <Could not decrypt the password attribute value of {3DES}71DlKVGKD9YlbDlDZg7p9g\=\= from the file ./boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into ./boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException - with nested exception:
[com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.].>

Resolution

A. Using cleartext password

Edit all the occurrences of boot.properties with cleartext password and try restarting the Server instances.

For example:

boot.properties with encrypted values

#Thu Jul 05 19:35:48 GMT 2007
password={3DES}71DlKVGKD9YlbDlDZg7p9g\=\=username={3DES}71DlKVGKD9YlbDlDZg7p9g\=\=

boot.properties with cleartext password

#Thu Jul 05 19:35:48 GMT 2007
password=weblogic
username=weblogic

B. Using encrypted password

Use the encrypt utility provided along with Weblogic to encrypt the password first and edit all the occurrences of boot.properties with the encrypted passwords.

1. In a command prompt set the classpath by running the setDomainEnv script located under your domain’s bin folder/directory.
For example: C:\oracle\Middleware\user_projects\domains\base_domain\bin
2. Execute java weblogic.security.Encrypt command which will prompt for the password and the encrypted value is printed as output.

Reference: http://download.oracle.com/docs/cd/E11035_01/wls100/admin_ref/utils.html#wp1209592

Note: The encrypt utility must be run from the Domain folder as it uses the domain’s password salt file(SerializedSystemIni.dat) for encrypting the cleartext string.

If you are not in the domain directory-structure you can pass the domain folder using the -Dweblogic.RootDirectory parameter.

Windows:

java -Dweblogic.RootDirectory=C:\oracle\Middleware\user_projects\domains\base_domain -cp C:\oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar weblogic.security.Encrypt

Unix:

java -Dweblogic.RootDirectory="/app/oracle/Middleware/user_projects/domains/base_domain" -cp "/app/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar" weblogic.security.Encrypt

3. Edit all the occurrences of boot.properties with the encrypted passwords followed by server instance startup.

Please leave your comments/queries for this post.

[Management:141191]The prepare phase of the configuration update failed with an exception

noreply@blogger.com (Sunil Nandargi) — Wed, 20 Jul 2011 22:12:00 +0000

I found one of the DataSource in my domain was in Suspended state, giving "unable to allocate resources to the application" errors while testing it. I tried to untarget and re-target the DataSource so that it can create fresh connections to the database killing all pending connections and avoid restarting the servers but the untarget changes took so long to be activated so I navigated away from the page and tried to activate the changes one more time and it won't activate any changes that I made and the Error displayed on the console is as below. Restarting AdminServer did not solve the problem.

An error occurred during activation of changes, please see the log for details.
Message icon - Error [Management:141191]The prepare phase of the configuration update failed with an exception:
Message icon - Error java.lang.NullPointerException:

Below is the log excerpt seen in the Admin Server logs.

<Jul 20, 2011 3:45:43 PM GMT> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.management.provider.UpdateException: [Management:141191]The prepare phase of the configuration update failed with an exception:
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateDeploymentContext(RuntimeAccessDeploymentReceiverService.java:648)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:133)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:27)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:199)
Caused by: java.lang.NullPointerException:

Solution

I was able to perform the same changes successfully after I followed the steps below.

1. Stop the AdminServer & ManagedServers.
2. On your AdminServer cd to %WEBLOGIC_HOME%\user_projects\domains\base_domain.
3. Delete the files under pending and servers/domain_bak directory.
4. Repeat steps 2 & 3 one each ManagedServers in the domain.
5. Start the AdminServer & ManagedServers.
6. Login the AdminConsole and click on ReleaseConfiguration button.
7. Perform the same changes now.

Please leave your comments/queries for this post.

Steps to configure Apache HTTP Server Plug-In with Weblogic Server

noreply@blogger.com (Sunil Nandargi) — Mon, 18 Jul 2011 23:03:00 +0000

Considering the Apache HTTP Server [Apache2.2] is already running as Windows service on port 8089 we shall continue to configure Apache HTTP Server Plug-In with Weblogic Server.

I am making use of Apache 2.2 and Weblogic 10.3 for this Post and demonstrating to access the Weblogic Console via Apache HTTP Server.

Steps to configure Apache HTTP Server Plug-In with Weblogic server

1. Identify the plug-in shared object file for your version of Apache in below table.

Apache Version	Regular Strength Encryption	128-bit Encryption
Standard Apache Version 2.0.x	`mod_wl_20.so`	`mod_wl128_20.so`
Standard Apache Version 2.2.x	`mod_wl_22.so`	`mod_wl128_22.so`

2. Verify that the WebLogic Server Apache HTTP Server Plug-In mod_so.c module is enabled.

The Apache HTTP Server Plug-In will be installed in your Apache installation as a Dynamic Shared Object (DSO). DSO support in Apache is based on module mod_so.c, which must be enabled before mod_wl_20.so is loaded. If you installed Apache HTTP Server using the script supplied by Apache, mod_so.c is already enabled. Verify that mod_so.c is enabled by executing the following command:

%APACHE_HOME%\bin\httpd.exe -l

-- Where APACHE_HOME is the directory containing your Apache installation

3. Copy the appropriate Weblogic Proxy plug-ins from Weblogic Installation to Apache installation.

Windows: %WEBLOGIC_HOME%\server\plugin\win\32\mod_wl_22.so to %APACHE_HOME%\modules\10.3\mod_wl_22.so

Solaris: $WEBLOGIC_HOME/server/plugin/solaris/sparc/mod_wl_22.so to %APACHE_HOME%/modules/10.3/mod_wl_22.so

Note: To differentiate the version of Weblogic proxy plug-ins, create a directory named with Weblogic version under %APACHE_HOME%/modules

4. Install the Apache HTTP Server Plug-In module for Apache by adding the following line to your APACHE_HOME/conf/httpd.conf file manually:

#Weblogic Module

LoadModule weblogic_module modules/mod_wl_20.so

5. Modify the below configuration and add it to the same APACHE_HOME/conf/httpd.conf to redirect calls to Weblogic instances as per your requirement. In my example below I am trying to access Weblogic console via Apache re-direction.

<IfModule mod_weblogic.c>
WebLogicCluster     weblogicserver.com:7002
Match Expression    *
Debug                    ON
WLLogFile               c:/tmp/global_proxy.log
WLTempDir             "c:/myTemp"
DebugConfigInfo     On
KeepAliveEnabled     ON
KeepAliveSecs         15
</IfModule>
<Location /console>
SetHandler weblogic-handler
PathTrim /console
</Location>

The Apache HTTP Server Plug-In recognizes the parameters listed in General Parameters for Web Server Plug-Ins. To modify the behavior of your Apache HTTP Server Plug-In, define these parameters:

-- In a Location block, for parameters that apply to proxying by path, or

-- In an IfModule block, for parameters that apply to proxying by MIME type

6. Verify if the recently added configurations in the APACHE_HOME\conf\httpd.conf file is accurate with the following command:

%APACHE_HOME%\bin\httpd.exe -t

The output of this command reports any errors in your httpd.conf file or returns:

Syntax OK

7. Restart Apache HTTP Server.

8. Test the plug-in by opening a browser and setting the URL to the Apache Server + ":" + port + “/console”, which should bring up the default WebLogic Server HTML page, welcome file, or default servlet, as defined for the default Web Application on WebLogic Server.
For example:

http://apacheserver.com:8089/console

That's it.
Please do leave your valuable comments/queries on this post.

Steps to configure SunOne WebServer with Weblogic Server Proxy Plug-In

noreply@blogger.com (Sunil Nandargi) — Wed, 06 Jul 2011 23:36:00 +0000

Before proceeding with Configuring SunOne WebServer with Weblogic server Proxy Plug-In we shall learn "What is a Weblogic Web Server Plug-In" and "How Web Server Plug-Ins Work with WebLogic Server"

What is a Weblogic Web Server Plug-In?

Weblogic Web Server plug-ins are modules that you add to your third-party Web server installation and configure to enable interactions between WebLogic Server and applications running on Apache HTTP Server, Sun One Web Server, and Microsoft Internet Information Server.

Plug-ins usually use one of the two following architectures to enable applications running on third-party Web servers to use the capabilities of WebLogic Server.

-- As a load balancer for the Web server (proxying the requests to the backend servers)

-- To proxy requests for dynamic content to backend servers (the Web server can supply only static content and relies on WebLogic Server for dynamic content)

How Web Server Plug-Ins Work with WebLogic Server?

A user application running on a third-party Web server generates an HTTP request, which the Web server routes to the WebLogic Server plug-in. The plug-in sends the HTTP request based on configuration information that specifies a WebLogic Server cluster or instance. The targeted WebLogic Server instance processes the request and returns a response to the user application through the plug-in.

Steps to configure SunOne WebServer with Weblogic server Proxy Plug-In

Considering the SunOne WebServer https-Weblogic10.3 is already running on port 1080 we shall continue to configure SunOne WebServer with Weblogic Server Proxy Plug-In.

I am making use of SunOne WebServer 7.0 and Weblogic 10.3 for this Post and demonstrating to access the Weblogic Console via WebServer.

1. Copy the appropriate Weblogic Proxy plug-ins from Weblogic Installation to WebServer installation.

Windows: %WEBLOGIC_HOME%\server\plugin\win\32\proxy61.dll to %WEBSERVER_HOME%\plugins\lib\10.3\proxy61.dll

Solaris: $WEBLOGIC_HOME/server/plugin/solaris/sparc/libproxy_61.so to %WEBSERVER_HOME%/plugins/lib/10.3/libproxy_61.so

Note: To differentiate the version of Weblogic proxy plug-ins, create a directory named with Weblogic version under %WEBSERVER_HOME%/plugins/lib

2. Load the Weblogic proxy plug-ins to WebServer https-Weblogic10.3 by adding the below lines immediately after Init fn="load-modules" shlib="j2eeplugin.dll" in magnus.conf file located under %WEBSERVER_HOME%\https-Weblogic10.3\config.

Windows: Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="%WEBSERVER_HOME%/plugins/lib/10.3/proxy61.dll"

Solaris: Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="$WEBSERVER_HOME/plugins/lib/10.3/libproxy_61.so"

Note: Replace WEBSERVER_HOME value as per your WebServer installation path. In my case it is C:\oracle\Sun\WebServer7. Make sure you use "/" instead in all path locations.

3. Edit the obj.conf located under %WEBSERVER_HOME%\https-Weblogic10.3\config to forward the HTTP requests received at WebServer from a user application to a Weblogic Server. See below.

Add the below configuration at the end of obj.conf file

<Object name="console" ppath="*/console">
Service fn="wl_proxy" WebLogicCluster="localhost:7001" DynamicServerList="OFF" KeepAliveEnabled="false" Debug="ALL" DebugConfigInfo="ON" WLLogFile="%WEBSERVER_HOME%/https-Weblogic10.3/logs/https-Weblogic10.3.log"
</Object>

First add NameTrans fn="assign-name" from="*/console" name="console" immediately after AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true"

and add the below configuration at the end of the obj.conf file

<Object name="console">
Service fn="wl_proxy" WebLogicCluster="localhost:7001" DynamicServerList="OFF" KeepAliveEnabled="false" Debug="ALL" DebugConfigInfo="ON" WLLogFile="%WEBSERVER_HOME%/https-Weblogic10.3/logs/https-Weblogic10.3.log"
</Object>

Note: Replace WEBSERVER_HOME & WebServer value as per your WebServer installation path. In my case it is C:\oracle\Sun\WebServer7 & https-Weblogic10.3. Make sure you use "/" instead in all path locations.

Also replace appropriate application redirects in place of console as in my example above.

4. Restart the https-Weblogic10.3 WebServer via WebServer admin console or via the scripts located under %WEBSERVER_HOME%\https-Weblogic10.3\bin.

[06/Jul/2011:17:27:17] info ( 9008): CORE1116: Sun Java System Web Server 7.0U5 B03/10/2009 22:30
[06/Jul/2011:17:27:17] info ( 9008): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_15] from [Sun Microsystems Inc.]
[06/Jul/2011:17:27:22] info ( 9008): HTTP3072: http-listener-1: http://localhost:1080 ready to accept requests
[06/Jul/2011:17:27:22] info ( 9008): CORE3274: successful server startup

5. Access the application using http://localhost:1080/console and you should be set.

Please do valuable comments/queries on this post.

WebLogic Server startup Hangs at IIOP subsystem enabled

noreply@blogger.com (Sunil Nandargi) — Thu, 30 Jun 2011 15:31:00 +0000

If your WebLogic Server startup Hangs at IIOP subsystem enabled then this post will help you demonstrate the solution to this issue.

Below are last few logs of stack trace.

Solution

If there is NO activity after the IIOP subsystem enabled then there is some problem with the Initialization of some Security configuration(s). Usually after enabling IIOP subsystem weblogic server initiates "security" data located under ("\servers\<server_name>\data" folder) might have been corrupted. So you will have to rename the ldap folder located under ("\servers\<server_name>\data") and start the Weblogic Server.

WebLogic Server LifeCycle and Server States

noreply@blogger.com (Sunil Nandargi) — Thu, 23 Jun 2011 18:32:00 +0000

The series of states through which a WebLogic Server instance can transition itself from one state to next state is called the WebLogic Server life cycle. At any time, a WebLogic Server instance is in a particular operating state. Commands such as start, stop and suspend sources specific changes to the operational state of a server instance.

Below diagram illustrates the Weblogic Server life cycle with different states the Weblogic Server can transition itself.

Understanding the States in the WebLogic Server Life Cycle

You can make use either the WebLogic Administration Console or the weblogic.Admin weblogic utility to explicitly move the WebLogic Server to a new state. The following is various states the server can transition itself during its life cycle.

SHUTDOWN

A server is said to be in the shutdown state when it is not running. When a server is in the SHUTDOWN state, the only thing you can do is start it.

RUNNING > SUSPENDING > STANDBY > SHUTTING DOWN > SHUTDOWN

STARTING

A server is said to be in the starting state when a start command has been issued by a startup script, Node Manager or other Weblogic Utilities. In the STARTING state, a server instance cannot accept any client or administrative requests. During the Admin server instance STARTING obtains its domain configuration data including the domain security configuration, from its config directory. During the Managed server instance STARTING it contacts the Administration Server for its configuration and security data.

SHUTDOWN > STARTING > RUNNING

SHUTDOWN > STARTING > STANDBY

STANDBY

A server is capable of moving into the STANDBY state if and only if Administration port has been configured for that server. Otherwise, the server will move directly from the starting state to the running state. If the server is configured to start in STANDBY state without Administration port opened then it would immediately goto FAILED state as per error below. When a server is in the STANDBY state, all services are initialized and all application get deployed. With the exception of the administration port, however, all ports are closed. Therefore, the server is said to be in hot STANDBY and ready to go.

####<Jun 22, 2011 5:10:40 PM MDT> <Notice> <WebLogicServer> <NAND-W7> <ManagedServer_1> <main> <<WLS Kernel>> <> <> <1308784240405> <BEA-000365> <Server state changed to STANDBY>
####<Jun 22, 2011 5:10:40 PM MDT> <Notice> <WebLogicServer> <NAND-W7> <ManagedServer_1> <main> <<WLS Kernel>> <> <> <1308784240406> <BEA-000360> <Server started in STANDBY mode>

Server configured to start in STANDBY but no Administration Port opened

SHUTDOWN > STARTING > STANDBY

RUNNING > SUSPENDING > STANDBY > SHUTTING DOWN > SHUTDOWN

any state > STANDBY > SHUTDOWN

RUNNING

When a server is in the running state, it is fully functional, offers its services to clients and participating as a regular member of a WebLogic domain. A server instance transitions to the RUNNING state as a result of the Start command, or the Resume command from the ADMIN or STANDBY states.

####<Jun 23, 2011 10:48:08 AM MDT> <Notice> <WebLogicServer> <NAND-W7> <AdminServer> <main> <<WLS Kernel>> <> <> <1308847688806> <BEA-000365> <Server state changed to RUNNING>
####<Jun 23, 2011 10:48:08 AM MDT> <Notice> <WebLogicServer> <NAND-W7> <AdminServer> <main> <<WLS Kernel>> <> <> <1308847688818> <BEA-000360> <Server started in RUNNING mode>

SHUTDOWN > STARTING > RUNNING

STANDBY > RESUMING > RUNNING

RESUMING

During this transitional state, WebLogic Server performs the operations required to move itself from the STANDBY or ADMIN state to the RUNNING state.
A server instance transitions to the RESUMING state when you issue the Resume command and transitions through the RESUMING state when you issue the Start command.

####<Jun 23, 2011 11:11:40 AM MDT> <Notice> <WebLogicServer> <NAND-W7> <AdminServer> <main> <<WLS Kernel>> <> <> <1308849100330> <BEA-000365> <Server state changed to RESUMING>

STANDBY > RESUMING > RUNNING

SUSPENDING

A server is moved into the suspending state during a graceful shutdown or suspend. This allows the server to complete any processing it may be working on to enable a clean shutdown without loss of any important state information. This state will be skipped during a forced shutdown. During this transitional state, WebLogic Server performs the operations required to place itself in the ADMIN state

####<Jun 23, 2011 11:00:38 AM MDT> <Notice> <WebLogicServer> <NAND-W7> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1308848438424> <BEA-000365> <Server state changed to SUSPENDING>
####<Jun 23, 2011 11:00:38 AM MDT> <Notice> <HTTP> <NAND-W7> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1308848438440> <BEA-101278> <There are no active sessions. The Web service is ready to suspend.>

RUNNING > SUSPENDING > ADMIN

FORCE_SUSPENDING

A server is moved into the suspending state during a Forceful shutdown or Force suspend. This allows the server to cause loss of any important state information. During this transitional state, WebLogic Server performs the operations required to place itself in the ADMIN state.

####<Jun 23, 2011 11:28:36 AM MDT> <Notice> <WebLogicServer> <NAND-W7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1308850116168> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
####<Jun 23, 2011 11:28:36 AM MDT> <Notice> <Server> <NAND-W7> <AdminServer> <DynamicListenThread[Default[2]]> <<WLS Kernel>> <> <> <1308850116176> <BEA-002607> <Channel "Default[2]" listening on 10.1.36.206:7001 was shutdown.>

RUNNING > FORCE SUSPENDING > ADMIN

SHUTTING DOWN

A server will be moved into the shutting down state after it receives a shutdown command. If the server is in the running or standby state when the shutdown command is received, it shuts down gracefully & completing any pending transactions in progress, terminating all services and executing any configured shutdown classes.

####<Jun 23, 2011 11:54:05 AM MDT> <Notice> <WebLogicServer> <NAND-W7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1308851645844> <BEA-000365> <Server state changed to SHUTTING_DOWN>

RUNNING > SUSPENDING > STANDBY > SHUTTING DOWN > SHUTDOWN

FORCE_SHUTTING DOWN
A server will be moved into the force_shutting_down state after it receives a force_shutdown command. If the server is in the running or standby state when the shutdown command is received, it shuts down forcefully, terminating all services and executing any configured shutdown classes.

####<Jun 23, 2011 11:47:45 AM MDT> <Notice> <WebLogicServer> <NAND-W7> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1308851265079> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

RUNNING > FORCE SUSPENDING > STANDBY > FORCE_SHUTTING DOWN > SHUTDOWN

FAILED

A server is moved into the failed state when the health monitoring service determines that a critical service is not functioning properly during its life cycle or might be due to misconfiguration during the restart of the server. Once a server is put into the failed state, it can only be shut down. If you have enabled health monitoring, the Node Manager can automatically shut down and restart the server if it fails.

<Jun 22, 2011 10:29:46 PM GMT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: StartupMode is set to STANDBY. Server cannot start in STANDBY state without admin channel. Server will shutdown now.>
<Jun 22, 2011 10:29:46 PM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>

RUNNING > FAILED

SHUTDOWN > STARTING > STANDBY > FAILED

UNKNOWN

A server is said to be in the UNKNOWN state if it cannot be contacted.

Configuration Auditing for Weblogic Domain

noreply@blogger.com (Sunil Nandargi) — Tue, 21 Jun 2011 22:26:00 +0000

In an organization with more than one Administrator working on a typical Weblogic domain(s) there is a possibility of changes being made without one others knowledge [might not be at the same time] and might cause some issues. This post will demonstrate a step-by-step configuration on how to have an audit of all the configuration changes made.

To have an audit of all the configuration changes such as below the "Configuration Audit Type" of the domain should be set as appropriate. This feature can also audit any changes that were made and not activated but released in the audit log entries.

-- Addition/deletion of configuration items

-- Modification of a setting

-- Addition/deletion of a user, group, etc.
-- Password resets
-- And so on

Enable configuration auditing

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the domain name.

3. In the right pane, Select Configuration > General tab and click on Advanced link at the bottom of General settings tab page.

4. Select one of below the appropriate Configuration Audit Type value. Default is none. In my case I am using Change Log and Audit.

-- None - do not audit configuration change events.

-- Change Log - Configuration events will be written to the server log.

-- Change Audit - Configuration events will be directed to the Security Framework and handled by the Auditing provider.

-- Change Log and Audit - Configuration events will written to the server log as well as directed to the Security Framework and handled by the Auditing provider.

5. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

6. Restart all the Weblogic Server instances specified in the Restart-Checklist for changes to take effect.

Note: All the Configuration Changes audits are saved in Admin Server log. So before you restart the Admin Server make sure you keep a copy of the Admin Server log.

Testing the Configuration Auditing

Below are some of the configuration change audits when i created a 'test' user and assigned the user to Administrators group.

####<Jun 21, 2011 4:04:21 PM MDT> <Info> <Configuration Audit> <NAND-W7> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1308693861750> <BEA-159907> <USER weblogic INVOKED ON Security:Name=myrealmDefaultAuthenticator METHOD createUser PARAMS test; ****; Test User>

####<Jun 21, 2011 4:04:21 PM MDT> <Info> <Configuration Audit> <NAND-W7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1308693861841> <BEA-159907> <USER weblogic INVOKED ON Security:Name=myrealmDefaultAuthenticator METHOD getUserDescription PARAMS test>

####<Jun 21, 2011 4:07:05 PM MDT> <Info> <Configuration Audit> <NAND-W7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1308694025758> <BEA-159907> <USER weblogic INVOKED ON Security:Name=myrealmDefaultAuthenticator METHOD addMemberToGroup PARAMS Administrators; test>

Resolving XAER_NOTA : The XID is not valid

noreply@blogger.com (Sunil Nandargi) — Thu, 16 Jun 2011 22:40:00 +0000

The below Error occurs if you are using two different JDBCConnection Pools for the same Oracle Database or two DataSources for the same pool. This post will help you understand and resolve the below issue.

Cause: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_NOTA start() failed on resour

ce 'jdbc/TestDB': XAER_NOTA : The XID is not valid

oracle.jdbc.xa.OracleXAException

at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:938)

As defined XA protocol requires all SQL statements for one and the same transaction branch be issued between an xa_start() and an xa_end() call. In a distributed transaction, an individual database represents one XAResource that will have one transaction branch in one distributed transaction. The WebLogic Server transaction manager considers every JDBC connection pool as a separate XAResource, i.e., it cannot evaluate if different connection pools or data sources point to the same database.

WebLogic Server makes sure that every call to one XAResource has the correct sequence of calls: xa_start, sql statements, and xa_end. Also WebLogic Server represents a multi-threading system, where different operations occur in a highly parallel environment. Consequently, calls to different XAResources like JDBC connection pools will happen concurrently. If two XA-Resources are defined for the same database, nested xa_start - xa_end pairs may result.

For example if there are two different ConnectionPools in one transaction, the calls may happen as follows:
-- xa_start(NOFLAGS) to ConnectionPool-1
-- sql statement for ConnectionPool-1
-- xa_start(JOIN) to ConnectionPool-2
-- sql statement for ConnectionPool-1
-- sql statement for ConnectionPool-2
-- xa_end() for ConnectionPool-2
-- xa_end() for ConnectionPool-1

This scenario will work perfectly fine as long as ConnectionPool-1 and ConnectionPool-2 are pointing to different databases and therefore different resource managers which will complete Transaction smoothly. However, if ConnectionPool-1 and ConnectionPool-2 point to the same Oracle database, an Oracle issue will lead to the above exception.

Solution

If it is not possible to define only one connection pool for one database, using the Oracle OCI driver can be a solution for this problem, as it synchronizes xa_start calls.

Work Around

If you are facing this issue even after having one DataSource this work around shall work.

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the Data Sources under Services > JDBC > Data Sources.

3. In the right pane, Click on your configured DataSource. In my case it is JDBC Data Source-1

4. In the Settings for JDBC Data Source-1 page, select Configuration > Transaction tab.

5. Click the Set XA Transaction Timeout check box flag and set the XA Transaction Timeout to 0.

6. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

7. Restart all the WLS nodes targeted to this DataSource.
8. By completing steps1-6, the DataSource will now make of JTA Timeout specified under base_domain > Configuration > JTA

-- In the left pane, click on the domain name.

-- In the right pane, Select Configuration > JTA tab.

Steps to Configure HermesJMS console to monitor Weblogic JMS resources

noreply@blogger.com (Sunil Nandargi) — Fri, 10 Jun 2011 23:28:00 +0000

HermesJMS is a open-source tool developed by Colin Crist. It is used to interact with JMS providers making it easy to browse or search queues and topics, copy messages and delete them. This tool has ability to work with many JMS Providers like JBoss MQ, Active MQ, OpenJMS, Weblogic JMS, Tibco JMS, WebSphere MQ, WebMethods etc...

This post will demonstrate the detailed step-by-step "How to get HermesJMS installed and configured for use with WebLogic JMS". There is web-recording provided in HermesJMS Website to setup HermesJMS with Weblogic. Please click here to go through the web-recording.

Installation

1. Download and save the HermesJMS installer jar in a commonly used location.

http://sourceforge.net/projects/hermesjms/

2. Open a command prompt and navigate to your directory where the installer jar is saved. Run "java -jar hermes-installer-1.13.jar" to begin the installation.

3. In the Installation wizard

-- Click Next on Welcome Screen

-- Click Next on Information Screen

-- Accept the terms of License Agreement and click Next

-- Enter the appropriate Installation Path [for ex: C:\Program Files\HermesJMS]and click Next

-- Select the packs to be installed [Default is HermesJMS] and click Next

-- In Ready to Install, click Next

-- In Pack Installation progress, once Finished with installation click Next

-- In Setup Shortcuts screen, enter appropriate name for your Installation [Default is HermesJMS] and click Next

-- Click Done

4. Please be sure to use the same JVM with HermesJMS as the WLS you want to connect to. You can approach this by adding the PATH and JAVA_HOME variable in <HERMES_HOME>/bin/hermes.bat or hermes.sh file at the beginning of the file right after the REM comments.

For example: I am trying to connect to Weblogic 9.2 domain with JDK 1.5 so i set as below.

set PATH=C:\oracle\Java\jdk1.5.0_22\jre\bin
set JAVA_HOME=C:\oracle\Java\jdk1.5.0_22\jre

Note: If you are trying to connect to Weblogic 10.3 domain with JDK 1.6 as your JVM to start HermesJMS please make sure that you add -Dsun.lang.ClassLoader.allowArraySyntax=true to the classpath in hermes.bat or hermes.sh. If you don't set this you shall come across below Error. Thanks to James Bayer for this information.

javax.jms.JMSException: Could not create InitialContext: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
java.io.StreamCorruptedException: invalid type code: 31

Steps to configure HermesJMS with Weblogic JMS

1. Launch the HermesJMS

-- Windows: via <HERMES_HOME>\bin\hermes.bat or Start > Program Files > HermesJMS > Hermes

-- Unix: via <HERMES_HOME>/bin/hermes.sh

2. Right click on Sessions to create a New session. jms > sessions > New > New session...

3. On resulting prompt, goto the Providers tab [bottom] and right click to Add Group called "Weblogic" and right click on "Library" to Add JAR(s) and specify your path to <WEBLOGIC_HOME>\server\lib\weblogic.jar. Click "Don’t Scan" when prompted.

4. In the same windows, goto Sessions tab [bottom].

-- Enter a Session Name "TestSession"

-- In the Connection Factory > Loader section, select "Weblogic" from the drop-down (you may have to save and then edit the session to see the provider you just configured in the drop down for loader)

-- In the Connection Factory > Class section, select "hermes.JNDIConnectionFactory".

-- In the Plug In drop-down select "BEA Weblogic"
-- In the Connection Factory add the properties as below. Click OK once done.

Property	Value
binding	javax/jms/QueueConnectionFactory
initialContextFactory	weblogic.jndi.WLInitialContextFactory
providerURL	t3://<managedServer>:<managedPort>
securityCredentials	<adminPassword>
securityPrincipal	<adminUsername>

5. Right click on newly created session TestSession to discover/find all of the available destinations. jms > sessions > TestSession > Discover. Once you click Discover you shall see a message "Getting message stores" at the bottom of the window and a Dialogue box stating Discovered # destinations. Click Yes.

6. Right click on one of the discovered Queue/Topic destination under jms > sessions > TestSession > [queueName/topicName] and select Browse to list the contents of the queue/topic on right hand pane as below.

Hermes can monitor multiple queues at once, auto-refresh, use selectors, delete messages, etc.. For more information check user guide at http://www.hermesjms.com.

You should be set now to monitor your queues/topics in your organization.

JNDI Objects under JNDI tree is not listed for Weblogic Instance?

noreply@blogger.com (Sunil Nandargi) — Fri, 27 May 2011 07:43:00 +0000

As most of us know Weblogic Applications make use of naming services to locate objects in data sources, EJBs, JMS, MailSessions, and so on. A naming service associates names with objects and finds objects based on their given names. JNDI is defined to be independent of any specific naming or directory service implementation. It supports the use of a number of methods for accessing various new and existing services.

The WebLogic Server implementation of JNDI supplies methods that:

-- Give clients access to the WebLogic Server naming services
-- Make objects available in the WebLogic namespace
-- Retrieve objects from the WebLogic namespace

Each WebLogic Server cluster is supported by a replicated cluster-wide JNDI tree that provides access to both replicated and pinned RMI and EJB objects. While the JNDI tree representing the cluster appears to the client as a single global tree, the tree containing the cluster-wide services is actually replicated across each WebLogic Server in the cluster.

Unknowingly or accidentally some of you might have an empty or \ instead of / as <jndi-name> tag in your configuration files. For example an empty <jndi-name> tag was accidentally added in the data-source configuration file. The next time you restart the Weblogic Server instances your JNDI tree for a Weblogic instance will not be displayed and the below error will be logged in your server log file.

Data-Source Config:
<jdbc-data-source-params>
    <jndi-name>example/test/jndiname</jndi-name>
    <jndi-name></jndi-name>
    <global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>

Error Log
java.lang.StackOverflowError
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at weblogic.jndi.internal.ServerNamingNode_922_WLStub.listBindings(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.listBindings(WLContextImpl.java:333)
at javax.naming.InitialContext.listBindings(InitialContext.java:406)
at com.bea.jsptools.tree.JNDITreeHelper$PrintContextAction.run(JNDITreeHelper.java:105)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

Screenshot
No JNDI Tree visible.

This issue has been identified as a bug [#8164017] in Weblogic 9.2.2MP and is fixed in Weblogic 9.2.4 and higher versions.

The only solution to the issue is to identify and remove/fix all the empty or invalid <jndi-name> tag from your configuration files. You might need to restart your Weblogic Instances once you are done with the fixes.

Screenshot after the Fix:

Steps to Reproduce this problem
1. Create a DataSource
2. Enter a jndi-name with a blank space at the end or with a \ instead of /
3. Then target the data-source to the managed server
4. Activate the changes
5. Restart all the Weblogic Instances in the domain
6. Try to display the JNDI tree in Domain > Servers > ManagedServer > view JNDI tree
7. The JNDI objects are not listed

Securing the Weblogic Admin Console

noreply@blogger.com (Sunil Nandargi) — Wed, 25 May 2011 07:38:00 +0000

It would be very easy to hack [see Google search below] and access your Domain resources very easily. So one should think of Securing your Weblogic Admin and its Domain resources.

Just type in "Administration Console" "Sign in" WebLogic inurl:"console" in your Google Search engine and you would find a number of Weblogic Console URL's across globe.

There are 2 ways you can secure your Weblogic Admin Console.
A. Enable Administration Port
B. Changing the console context-path

A. Enable Administration Port

Weblogic Administration Port helps you secure access to Weblogic Admin Console. By default Weblogic Admin Console is deployed on the AdminServer listen port.

With the Administration Port enabled:

-- The console is only accessible over a non-standard port (which will not be available to world outside your firewall)
-- You will have to use SSL [https protocol] along with Administration Port to access your domain console.
-- You get a dedicated administration listen thread.
-- Administrative requests over any port other than the administration port are rejected.

-- Enables you to separate the Administration traffic from Application traffic in your domain. For example you can access the application with http & 7001 port but you cannot access Weblogic Admin Console with http & 7001 port. You will to use https & 9002 port to do so.

Steps to Enable Administration Port

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the domain name.

3. In the right pane, Select Configuration > General tab.

4. Click the Enable Administration Port check box flag and specify the appropriate Administration Port.

5. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

Note: No restart required you will be automatically switched to use Administration Port. If not check step6.

6. The Weblogic Admin console will no longer be accessible on your AdminServer Listen Port. You will have to use https protocol with Administration Port to access your Weblogic Admin Console now. For ex: https://localhost:9002/console.
Now that you are using Administration Port, if you try accessing Weblogic Admin console using standard listen port you would get below message displayed on your browser
"Console/Management requests or requests with <require-admin-traffic> specified to 'true' can only be made through an administration channel"

7. Now the Managed Server will have to use the new HTTPS URL during the start-up. If your Managed Server is starting via Windows service then you will have to re-install the service with new settings. Please refer WebLogic Server instance as Windows Service.

B. Changing the Console context-path

As the context-path for Weblogic Admin console is globally known, it would be very easy to hack [see Google search below] and access your Domain resources very easily. You can now change the Console context-path to your wish.

Steps to change the Console context-path

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the domain name.

3. In the right pane, Select Configuration > General tab and click Advanced link at the very bottom of the page.

4. Change the value for Console Context Path field. I am using as admin as my new Console Context Path.

5. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

6. Restart all the Weblogic Server instances specified in the Restart-Checklist for changes to take effect.

7. Once restarted test the Weblogic Console URL with new context-path.

That's it.
Please do leave your valuable comments.

Steps to Configure Weblogic Connection Filters

noreply@blogger.com (Sunil Nandargi) — Tue, 24 May 2011 19:51:00 +0000

Connection Filters allow you to deny access of UNWANTED Connections at the network level. Connection Filters can be used to protect server resources on individual servers, server clusters, or an entire internal network or Intranet. Connection filters are particularly useful when using the Administration port. Depending on your network firewall configuration, you may be able to use a connection filter to further restrict administration access. A typical use might be to restrict access to the Administration port to only the servers and machines in the domain.

WebLogic Server is having a built-in with a default connection filter called weblogic.security.net.ConnectionFilterImpl. This default connection filter accepts all incoming connections except the one's defined in your Administration Console as a Connection filter rule. You can write your own custom connection filter by implementing the classes in the weblogic.security.net package. This post will demonstrate the Steps to Configure Weblogic Connection Filters.

Steps to Configure Weblogic Connection Filters

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the domain name.

3. In the right pane, Select Security > Filter tab.

4. Click the Connection Logger Enabled attribute to enable the logging of accepted connections.

5. Specify the Connection Filter to be used with the domain.

I am making use of the default connection filter "weblogic.security.net.ConnectionFilterImpl"

6. Specify the Connection Filter Rules. Make sure that you use the syntax below while writing the rules.

Syntax:

target localAddress localPort action protocols 
where
-- target             specifies the client hosts that can connect to Weblogic Server instance.
-- localAddress  defines the host address of the Weblogic Server instance to which any client 
can connect. If you specify an asterisk (*), the match returns all local IP addresses.
-- localPort        defines the port on which the WebLogic Server instance is listening to which 
any client can connect. If you specify an asterisk (*), the match returns all available ports on 
the server.
-- action            specifies the action to perform. This value must be only allow or deny.
-- protocols       the list of protocol names to match. The following protocols may be specified: 
http, https, t3, t3s, giop, giops, dcom, ftp, ldap. If no protocol is defined, all protocols will match a rule.

7. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

Once saved an entry is made in the Config.xml for these settings as below:

config.xml

       <connection-filter>weblogic.security.net.ConnectionFilterImpl</connection-filter>
        <connection-filter-rule>10.1.xx.xx 10.1.xx.xx 7001 deny http</connection-filter-rule>
        <connection-logger-enabled>true</connection-logger-enabled>

8. Restart the all the Weblogic Server instance for changes to take effect.

9. Testing the Connection Filter rules.

Try to access the Weblogic server instance with the port from the target server mentioned in the rule.

Rejected Connection

####<May 24, 2011 1:34:50 PM MDT> <Notice> <Socket> <NAND-S77> <AdminServer> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1306265690809> <BEA-000445> <Connection rejected, filter blocked Socket[addr=10.1.xx.xx,port=48316,localport=7001], weblogic.security.net.FilterException: [Security:090220]rule 1>

Try to access the Weblogic server instance with the port from the target server which is not mentioned in the rule.

Accepted Connection

####<May 24, 2011 1:34:23 PM MDT> <Info> <Socket> <NAND-S77> <AdminServer> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1306265663662> <BEA-000431> <Accepted Connection: Filtering is set to: "true" Remote Address: "/0:0:0:0:0:0:0:1" Remote Port: "51655" Local Address: "0.0.0.0/0.0.0.0" Local Port: "7001" Protocol: "http">

That's it.

Please do leave your valuable comments.

Further reading on Connection Filter rules.
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/security/con_filtr.html#1029299

Steps to Configure Global Trust between Weblogic Domains

noreply@blogger.com (Sunil Nandargi) — Mon, 23 May 2011 19:30:00 +0000

WebLogic Server enables you to configure Weblogic Domains to inter-operate each other via Cross Domain Security Between WebLogic Server Domains & Global Trust between Domains. In this post I am going to demonstrate the "Steps to Configure Global Trust between Weblogic Domains".

When you enable global trust between two domains, the trust relationship is transitive and symmetric. In other words, if Domain A trusts Domain B then Domain B will also trust Domain A. How is this done? You do this by specifying the same Domain Credential for each of the domains. By default, the Domain Credential is randomly generated and therefore, no two domains will have the same Domain Credential. If you want two WebLogic Server domains to inter-operate, you need to replace the generated credential with a credential you select, and set the same credential in each of the domains.

Global trust between domains is established so that principals in a Subject from one WebLogic Server domain are accepted as principals in another domain. When this feature is enabled, identity is passed between WebLogic Server domains over an RMI connection without requiring authentication in the second domain. WebLogic Server signs Principals with the Domain Credential as Principals are created. When a Subject is received from a remote source, its Principals are validated.If validation fails, an error is generated. If validation succeeds, the Principals are trusted as if they were created locally.

Steps to Configure Global Trust between Weblogic Domains

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the domain name.

3. In the right pane, Select Security > General tab and click Advanced link at the very bottom of the page.

4. Enter the chosen password for the domain in the Credential & Confirm Credential text field.

5. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

6. Perform the same procedure from Steps 1-5 in other domains for which you want to enable global trust. Make sure that you pass same credentials in other domains too.

That's it with the configurations.

Please do your valuable comments.

Steps to Export & Import Weblogic Embedded LDAP Server [Security Realm]

noreply@blogger.com (Sunil Nandargi) — Mon, 23 May 2011 07:23:00 +0000

The Embedded LDAP server is the default security provider database for the WebLogic Authentication, Authorization, Credential Mapping and Role Mapping providers. It contains user, group, group membership, security role, security policy, and credential map information.
Unknowingly the Embedded LDAP data gets corrupted which is not a very good sign in Applications like Weblogic Portal Applications & Applications using Embedded LDAP for there login and if you have created users, groups, roles, etc in your embedded LDAP, you'd have to recreate them manually, after the domain is brought up the with new Embedded LDAP.

Fortunately, If you have similar environment running along with your Domain which does not work as expected, Weblogic Application Server suite comes with a tool to export the whole content of your Weblogic Security Realm and import into your Domain.

Steps to Exporting & Importing Weblogic Embedded LDAP Server

Exporting the Weblogic Embedded LDAP Data

1. In the left pane, click on the security realms

2. In the right pane, click on myrealm

3. In the Settings for myrealm window navigate to Migration > Export tab.

4. Input the Export Directory on Server and this path should be located on the server where your Domain is hosted.

For example I have created a directory called EmbeddedLDAP in my %DOMAIN_HOME% as my Export directory.

5. Click Save to export the Embedded LDAP data.

6. After Exporting 5 Files should be created in the designated folder.

Importing the Weblogic Embedded LDAP Data

1. In the left pane, click on the security realms

2. In the right pane, click on myrealm

3. In the Settings for myrealm window navigate to Migration > Import tab.

4. Copy the previously been exported Embedded LDAP data to the server where the domain is hosted.

For example I have created a directory called EmbeddedLDAP in my %DOMAIN_HOME% and saved the exported Embedded LDAP data.

5. Input the Import Directory on Server and this path is same step 4.

6. Click Save to import the Embedded LDAP data.

7. Verify the Users and Groups tab for Imported Embedded LDAP data under Security Realms > myrealm.

You domain should be back with data you had it before.

Please do leave your valuable comments.

Steps to Configure the Cross Domain Security Between WebLogic Server Domains

noreply@blogger.com (Sunil Nandargi) — Fri, 20 May 2011 23:12:00 +0000

Cross Domain Security establishes trust between domains such that principals in a Subject from one WebLogic Server domain can make calls in another domain.

WebLogic Server establishes a security role for cross-domain users, and uses the WebLogic Credential Mapping security provider in each domain to store the credentials to be used by the cross-domain users.

Configuration and use of cross-domain security is described in the following sections:

Configuring Cross-Domain Security

Configuring Cross-Domain User

Configure a Credential Mapping for Cross-Domain Security

Configuring Cross-Domain Security

1. If you have not already done so, in the Change Center of the Administration Console, click "Lock & Edit"

2. In the left pane, click on the domain name.

3. In the right pane, Select Security > General tab.

4. Check the Cross Domain Security Enabled.

5. Click Save and in the Change Center of the Administration Console, click "Activate Changes".

Configuring Cross-Domain User

1. In the left pane, click on the security realms

2. In the right pane, click on myrealm

3. Add new user "cross-domain" under Users and Groups > Users tab.

4. Click on the "cross-domain" user to add this user to "CrossDomainConnectors" group and click on Groups tab. Move the "CrossDomainConnectors" from available list to chosen list.

5. Click Save to save all the changes for "cross-domain" user.

Configuring Credential Mapping for Cross-Domain Security

1. In the left pane, click on the security realms

2. In the right pane, click on myrealm

3. Click new under Credential Mappings > Default tab.

4. Check "User cross-domain protocol" and In the Remote Domain field, enter the name of the remote domain that needs to interact with the local domain. Click next once done.

5. On the Create a New Security Credential Map Entry page, enter the following.
-- Local User: User configured in the local domain if not Automatically populated.
-- Remote User: User configured in the remote domain [base_domain2] that is authorized to interact with the local domain.
-- Remote Password: The password for the remote user.

6. Click Finish.

That's it. Now your Cross Domain Security Between WebLogic Server Domains should be enabled.

Please leave your valuable comments.

Steps to Reset the password for Weblogic Admin Console

noreply@blogger.com (Sunil Nandargi) — Thu, 19 May 2011 22:58:00 +0000

Forgot the password for the Weblogic Admin account and the boot.properties is not available in the domain to recover the password? You might wonder and ask a question to yourself "How do i get the password reset for the Weblogic Admin account?". This post is available to you to help Reset the password for Weblogic Admin Console. Just follow through the blog which provides the steps for the same.

Steps to Reset the password for Weblogic Admin Console

Step 1. Run setDomainEnv.cmd/setDomainEnv.sh from your %DOMAIN_HOME%/bin directory to set necessary domain environment variables in command prompt for windows and shell prompt for Unix as above tool requires weblogic.jar to run.

Note: Any information below should be updated to match your directory structures and information
%DOMAIN_HOME% - C:\oracle\Middleware\user_projects\domains\base_domain

Step 2. Backup or rename the DefaultAuthenticatorInit.ldift file located under your %DOMAIN_HOME%/security directory as Step 3 creates a new DefaultAuthenticatorInit.ldift file with modification specified.

Step 3. From %DOMAIN_HOME%/security directory run the below command.
"java weblogic.security.utils.AdminAccount weblogic <new_passwd> ."

Note: There is a . (DOT) at the end of the above command which represents the Current Directory. A new “DefaultAuthenticatorInit.ldift” file will be created after the command is executed in the current directory.

Step 4. Rename the data directory to data.bkp located under your %DOMAIN_HOME%/servers/AdminServer.

Step 5. Rename all the instances of boot.properties to boot.properties.bkp located under your %DOMAIN_HOME% [if any] and %DOMAIN_HOME%/servers/AdminServer/security directory.

Step 6. Create a new boot.properties with new password as below under %DOMAIN_HOME% [if any there was earlier] and %DOMAIN_HOME%/servers/AdminServer/security directory. As recommended to avoid prompting for Username and Password while starting the Weblogic instance this step is mandatory.

boot.properties

username=weblogic

password=<new_passwd>

Note: Make sure the boot.properties is not having any extra special characters (UTF or Invisible characters) or spaces except the above two lines. Also there should be no Heading or Trailing SPACE character in these two Lines.

Step 7. Issue a Startup command to Weblogic instance and monitor the logs. If you are using Windows service for startup of Weblogic then you might also need to delete the existing windows service and install the windows service with new credentials. Please refer WebLogic Server instance as Windows Service .

You would see something like below in your Server logs when you startup Weblogic Instance with new boot.properties.

####<May 19, 2011 3:27:01 PM MDT> <Notice> <Security> <NANDAR-W7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1305840421604> <BEA-090083> <Storing boot identity in the file: C:\oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\security\boot.properties>

Step 8. Your managed nodes also needs to be started with new boot.properties. You can follow step4 to step7 or just replace all the instances of boot.properties on your managed node with the one on AdminServer and rename the servers directory located under %DOMAIN_HOME% on managed node.

Note: Please leave your valuable comments once you visit this post.

Steps to Recover the lost or not known password for Weblogic Admin Console.

noreply@blogger.com (Sunil Nandargi) — Tue, 17 May 2011 23:18:00 +0000

Forgot the password or the password is not known? But the boot.properties is available in the domain and you can start the domain with it. When you try opening boot.properties to find the password and you see the values are encrypted. You might wonder and ask a question to yourself "How do i get the decrypted of those encrypted values". This post is available to you to help Recover the lost or not known password for Weblogic Admin Console. Just follow through the blog which provides the steps for the same.

Before starting, Just think once how is it possible to "Recover the lost or not known password for Weblogic Admin Console". The answer is: When you issue a startup command to Weblogic instance, it tries to decrypt the encrypted password of the boot.properties using a weblogic.security.internal.BootProperties class file which is built-in with Weblogic.jar.

STEPS TO RECOVER THE LOST OR NOT KNOWN PASSWORD FOR WEBLOGIC ADMIN CONSOLE.

Step 1. Save the below java & scripts files accordingly on your Domain hosting server in a commonly accessible location and change the directory to that location.

RecoverPasswd.java

RecoverPasswd.cmd - Windows

RecoverPasswd.ksh - Unix

Step 2. Run setWLSEnv.cmd/setWLSEnv.sh from your %WL_HOME%/server/bin directory to set necessary environment variables in command prompt for windows and shell prompt for Unix as above tool requires weblogic.jar to run.

Step 3. Now compile the Java code using below syntax.

Syntax: javac RecoverPasswd.java

Step 4. Copy the compiled class to your %DOMAIN_HOME% as this class file needs to be run from the domain directory.

Step 5. Now run RecoverPasswd.cmd or RecoverPasswd.ksh accordingly. Please see the syntax below before you run.

Syntax:

Windows - RecoverPasswd.cmd [domain_path]

Unix - ./RecoverPasswd.ksh [domain_path]

Windows:

Unix:

Steps to remove a Domain for WL10 and onwards

noreply@blogger.com (Sunil Nandargi) — Fri, 13 May 2011 18:44:00 +0000

As of now there is no such feature provided by either Oracle or BEA for Weblogic Config wizard or such other utility which can help you to clean remove or delete a domain. It is all manual if you are looking for deleting a domain for WL10 and onwards.

Steps to remove a Domain for WL10 and onwards

Consider I am trying to delete a domain named base_domain. Just follow simple steps below to clean remove the domain.

Step 1. Edit domain-registry.xml under $WL_HOME to remove the corresponding entry referring to base_domain. For example delete this line<domain location="C:\oracle\Middleware\user_projects\domains\base_domain"/> from domain-registry.xml

domain-registry.xml

<?xml version="1.0" encoding="UTF-8"?>
<domain-registry xmlns="http://xmlns.oracle.com/weblogic/domain-registry">
<domain location="C:\oracle\Middleware\user_projects\domains\base_domain"/>
</domain-registry>

Step 2. If you are NOT using NodeManager to stop and start the WebLogic instance then please IGNORE this step. Else edit nodemanager.domains file under $WL_HOME/wlserver_10.3/common/nodemanager directory to remove the corresponding entry referring to base_domain. For example delete this line base_domain=C\:\\Oracle\\Middleware\\user_projects\\domains\\base_domain from nodemanager.domains

nodemanager.domains

#Domains and directories created by Configuration Wizard
#Thu Apr 28 11:54:41 MDT 2011
base_domain=C\:\\Oracle\\Middleware\\user_projects\\domains\\base_domain

Step 3. Delete the domain directory under domains folder manually.

$WL_HOME/user_projects/domains/base_domain

NodeManager setup and WebLogic startup with NodeManager

noreply@blogger.com (Sunil Nandargi) — Sat, 30 Apr 2011 08:05:00 +0000

This is detailed guide for setting up the WebLogicServer NodeManager service and managing the WebLogicServer instance using this service. Also this post provides you an explanation on how to setup WebLogic Server processes to be automatically managed by Node Manager, when an OS instance is rebooted. When an OS instance is rebooted, WebLogic Server will return to the state as it was prior to the reboot.

Assuming the WebLogic Server installation has been done and a domain has been setup with the base configuration as you would like.

Note: Any information below should be updated to match your directory structures and information.

       - %WL_HOME% - C:\oracle\Middleware
       - %DOMAIN_NAME% - base_domain
       - %DOMAIN_HOME% - C:\oracle\Middleware\user_projects\domains\base_domain
       - %MACHINE_NAME% - localhost
   - Admin Server [Running] and ManagedServer [shutdown] in the domain

Installing the NodeManager service

      1. Open the Command Prompt
2. Run %WL_HOME%\wlserver_10.3\server\bin\setWLSEnv.cmd to set Weblogic Environment variables like WL_HOME, JAVA_HOME, PATH, CLASSPATH etc..
      3. Edit the installNodeMgrSvc.cmd to bind to a hostname for remote starts
set NODEMGR_HOST=localhost
      4. Now run the %WL_HOME%\wlserver_10.3\server\bin\installNodeMgrSvc.cmd

Validate the service from the services list as well using the services.msc utility

5. Start the NodeManager service named as above “Oracle WebLogic NodeManager…”
6. Make sure starting the NodeManager service should create a nodemanager.properties file under %WL_HOME%\wlserver_10.3\common\nodemanager

Setup NodeManager to restore servers to their last known state after a reboot

      1. Open nodemanager.properties located at %WL_HOME%\wlserver_10.3\common\nodemanager
      2. Set CrashRecoveryEnabled property value to true
CrashRecoveryEnabled=true
      3. Set StartScriptEnabled property value to true to invoke the startWeblogic script
          StartScriptEnabled=true
      4. Set StopScriptEnabled property value to true to invoke the stopWeblogic script and get the managed servers to shutdown cleanly
   StopScriptEnabled=false
      5. Restart of NodeManager service for each change to this nodemanager.properties file

Setup the machine

      1. Login to the AdminServer console
      2. Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Machines

     3. Create a new machine
          Name : localhost
    OS     : Other - as my operating system is Windows

      4. Create one machine for each instance of OS for a different host.
      5. Assign the ManagedServer to machines based on which machine the ManagedServer is hosted. Take Lock & Edit and navigate through %DOMAIN_NAME% -> Environment -> Machines -> %MACHINE_NAME% -> Configuration tab -> Servers tab

   6. Do not forget to save and Activate the changes.

Enrolling the domain with NodeManager

       1. Open command prompt
   2. Run %DOMAIN_HOME%\bin\setDomainEnv.cmd to set domain specific environment variables
   3. Start WLST using java weblogic.WLST
   4. At WLS prompt connect to AdminServer using
           connect ('weblogic','weblogic','t3://localhost:7001')

   5. Run nmEnroll(domainDir='C:/oracle/Middleware/user_pro
jects/domains/base_domain',nmHome='C:/oracle/Middleware/common/nodemanager')

           Make sure that you use forward slashes "/" instead of backward "\" as WLST does not recognize forward slashes
           If you use backward slashes "\" you get the below error.

        6. Once the domain is successfully enrolled with NodeManager the nodemanager.domains should be updated too with below values.
#Thu Apr 28 11:54:41 MDT 2011
            base_domain=C\:\\Oracle\\Middleware\\user_projects\\domains\\base_domain
            Also NodeManager should be reachable in AdminServer console. To validate this,
            a. Login to AdminServer console
            b. Navigate through %DOMAIN_NAME% -> Environment -> Machines -> %MACHINE_NAME% -> Monitoring -> Node Manager Status


Server Startup Configuration

1. Login to the AdminServer console

2. Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Servers -> ManagedServer_1 -> Configuration tab -> Server Start tab

3. Take Lock & Edit and input values as appropriate.

Java Home - C:\oracle\Middleware\jdk160_14_R27.6.5-32

Java Vendor - Sun - As I am using Sun JDK

BEA Home - C:\oracle\Middleware

Root Directory - C:\oracle\Middleware\user_projects\domains\base_domain

Classpath - Can be left blank as we have configured the nodemanager.properties to use startWeblogic script in Setup NodeManager to restore servers to their last known state after a reboot step 3 and you can setup necessary values in that script.

Arguments - Can be left blank as we have configured the nodemanager.properties to use startWeblogic script in Setup NodeManager to restore servers to their last known state after a reboot step 3 and you can setup necessary values in that script. But i am using memory arguments as input here "-Xms64m -Xmx128m"

Security Policy File - C:\oracle\Middleware\wlserver_10.3\server\lib\weblogic.policy

User Name - weblogic

Password - weblogic

Confirm Password - weblogic

4. Save and activate the changes

5. Repeat steps 1-4 for each ManagedServer in the domain.

NodeManager Domain Username and password

1. Login to the AdminServer console

2. Click on Domain name in the Domain Structure and navigate through %DOMAIN_NAME% -> Security tab -> General tab -> Advanced link

3. Take Lock & Edit and input the NodeManager username/password/confirm passwords fields and these could be unique from your weblogic console password. I have chosen to input same as my console credentials username: weblogic & password: weblogic. This setup would help user who use WLST to connect to NodeManager via nmConnect()

4. Save and Activate the changes

Finally the setup is complete and now its time to start your ManagedServer in Admin console using NodeManager.

Starting the ManagedServer using the NodeManager setup

1. Login to the AdminServer console

2. Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Servers -> ManagedServer_1 -> Control tab -> Start/Stop tab

3. Under the Server Status section select the ManagedServer and click on start button

When prompted to confirm the Action to be performed, click yes button

4. Monitor the server logs and after a while the server should be in RUNNING state

That's it. Please let me know if you have any queries on this setup guide.

WebLogic Server instance as Windows Service

noreply@blogger.com (Sunil Nandargi) — Thu, 28 Apr 2011 22:31:00 +0000

As in UNIX OS we have an option of auto-start [init.d and rc3.d] of WebLogic services immediately after the server is rebooted similarly we can implement the WebLogic services to auto-start in Windows OS as well. "How to do that?". This post provides you details explanation on how to install the WebLogic services [Admin and Managed Nodes] as windows service.

Installing
Just follow the simple steps below.

A. AdminServer as windows service
1. Go to domain home directory C:\oracle\Middleware\user_projects\domains\base_domain
2. Create install script named "InstallWindowsService_AdminServer.cmd" with content in it as described below.

Note: Update the values accordingly. Below is just an example for my domain

echo off
SETLOCAL

set DOMAIN_NAME=base_domain
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\base_domain
set SERVER_NAME=AdminServer
set WL_HOME=C:\Oracle\Middleware\wlserver_10.3
set WLS_USER=weblogic
set WLS_PW=w3bl0gic
set PRODUCTION_MODE=true
set JAVA_VENDOR=Sun
set JAVA_HOME=C:\oracle\Middleware\jdk160_14_R27.6.5-32
set MEM_ARGS=-Xms256m -Xmx512m
call "%WL_HOME%\server\bin\installSvc.cmd"

ENDLOCAL

3. Run this script in command prompt to track the output of the script and you would see
"beasvc base_domain_AdminServer installed" before the scripts exits.

Validate the service

a. This should create service with name of "beasvc base_domain_AdminServer" in

the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. The registry entry

contains such information as the name of the server and other start-up arguments

    b. You can check the same from the services list as well using the services.msc utility.

c. Verify whether the WebLogic Server is successfully installed as a service as below in
        command prompt.
    set WL_HOME=C:\Oracle\Middleware\wlserver_10.3
        set PATH=WL_HOME\server\bin;%PATH%

        cd C:\Oracle\Middleware\wlserver_10.3\server\bin
        beasvc -debug "beasvc base_domain_AdminServer"

4. You can start/stop the server from the services.msc utility or you can also use the below commands.

Starting the service:

net start "beasvc base_domain_AdminServer"

Stopping the service:

net stop "beasvc base_domain_AdminServer"

B. Managed Node as windows service

1. Go to domain home directory C:\oracle\Middleware\user_projects\domains\base_domain
2. Create install script named "InstallWindowsService_ManagedServer.cmd" with content in it as described below.
Note: Update the values accordingly. Below is just an example for my domain

echo off
SETLOCAL

set DOMAIN_NAME=base_domain
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\base_domain
set SERVER_NAME=ManagedServer1
set WL_HOME=C:\Oracle\Middleware\wlserver_10.3
set WLS_USER=weblogic
set WLS_PW=w3bl0gic
set PRODUCTION_MODE=true 
set JAVA_VENDOR=Sun
set JAVA_HOME=C:\oracle\Middleware\jdk160_14_R27.6.5-32
set ADMIN_URL=http://localhost:7001
set MEM_ARGS=-Xms64m -Xmx128m
call "%WL_HOME%\server\bin\installSvc.cmd"

ENDLOCAL

Note: DO NOT forget to specify the ADMIN_URL in the script. If you do then the Managed Server won't start and below error will be logged in your ManagedServer log file.

javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.]

3. Run this script in command prompt to track the output of the script and you would see

"beasvc base_domain_ManagedServer1 installed" before the scripts exits.

Validate the service

a. This should create service with name of "beasvc base_domain_ManagedServer1" in

the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. The registry entry

contains such information as the name of the server and other start-up arguments

4. You can start/stop the server from the services.msc utility or you can also use the below commands.

Starting the service:

net start "beasvc base_domain_ManagedServer1"

Stopping the service:

net stop "beasvc base_domain_ManagedServer1"

NOTE: FOLLOW STEPS 1-4 FOR MULTIPLE MANAGED SERVER INSTANCES

Uninstalling

Just follow the simple steps below.

A. AdminServer

1. Go to domain home directory C:\oracle\Middleware\user_projects\domains\base_domain
2. Create install script named "UninstallWindowsService_AdminServer.cmd" with content in it as described below.
Note: Update the values accordingly. Below is just an example for my domain

echo off
SETLOCAL

set DOMAIN_NAME=base_domain
set SERVER_NAME=AdminServer
set WL_HOME=C:\Oracle\Middleware\wlserver_10.3

call “%WL_HOME%\server\bin\uninstallSvc.cmd”

ENDLOCAL

sc delete "beasvc base_domain_AdminServer"

B. ManagedServer

echo off
SETLOCAL

set DOMAIN_NAME=base_domain
set SERVER_NAME=ManagedServer1
set WL_HOME=C:\Oracle\Middleware\wlserver_10.3

call “%WL_HOME%\server\bin\uninstallSvc.cmd”

ENDLOCAL

sc delete "beasvc base_domain_ManagedServer1"

How to get a New License for WebLogic Products

noreply@blogger.com (Sunil Nandargi) — Thu, 28 Apr 2011 08:55:00 +0000

One should be thinking 'How can I get a new License for WebLogic products?'. Well you don't need to worry about the licenses if your Weblogic Product version is not list below because from here on the WebLogic products 10.3 and higher does not require a license file.

BEA WebLogic Server Products - Version 6.1 - 10.0 MP1

BEA WebLogic Platform Products- Version 7.x - 10.2

BEA WebLogic Portal Products- Version 7.x - 10.2

BEA WebLogic Integration Products- Version 2.x - 10.2

for more Click Here

If your Weblogic Product version still falls in the above list then there is change in the license as well made by Oracle after acquiring BEA. Now Oracle no longer requires your IP address(es) in order to provide a license key. Oracle is now providing new generic license files that simplify the licensing process. Your new license keys will enable you to fully utilize all of the features of your Product.

While keys in the new licenses may remove technical restrictions, such as to the number of production CPUs, Users, etc. that may be executed on simultaneously, it does not authorize you to deploy BEA software for production use on the number of CPUs, Users, etc. greater than what you licensed for such use.

How can I get a new License for WebLogic products?

Answer: Please see BEA LicenseCodes where licenses can be downloaded for Weblogic products that require a license key.

To use one of these license files, please follow these steps:

1. Download you application suitable license
2.Take a backup of the old license file
cp license.bea license.bea_bkp
3. Place the downloaded new license file [for example: license.bea_new] in the BEA_HOME directory
4. Run the UpdateLicense utility against the new license file as below.
./UpdateLicense.sh license.bea_new
If the server starts up successfully, the license has been applied correctly.