Portlet unavailable on webcenter page that contains many portlets

 Hi,
A quick tip here which i experienced few days back. Sometimes you might see a ‘portlet unavailable’ message in one of the portlets in a web-center page that contains many portlets.

Note: We are using Extended webcenter spaces on Patch SET 1 (11.1.1.2) and there is a bug in that release (confirmed by oracle support)

Primary reason for this is that the Queue size is not large enough to take all requests.

Solution:

Increase the parallelQueueSize and parallelPoolSize for webcenter page in adf-config.xml which resides on server running webcenter.

<adf-portlet-config xmlns="http://xmlns.oracle.com/adf/portlet/config">
<parallelPoolSize>400</parallelPoolSize>
<parallelQueueSize>400</parallelQueueSize>
……
So, where to find the file? well it resides in tmp folder of your managed server you can find the find using following command on linux machine

1. go to $MIDDLEWARE_HOME/user_projects/domains/domain_name/servers
2. Run the following command
$ find ./ -name adf-config.xml -print |grep webcenter
3. Result would be similar to this
./WLS_Spaces/tmp/_WL_user/webcenter/8gco54/adf/META-INF/adf-config.xml
4. Edit the file using your favorite editor and save it
5. Restart the Admin and managed servers
Check the following documentation link as well http://download.oracle.com/docs/cd/E12524_01/webcenter.1013/e12434/jpsdg_files.htm#CHDECFBC

Problem:
We are using Extended webcenter spaces on Patch SET 1 (11.1.1.2) and there is a bug in that release (confirmed by oracle support) so i have to fix that in cache files only because of that whenever we clear the tmp cache of the server we have to do this change again.

Quote from Oracle support

Yes, there is a bug on version before WC PS3 (11.1.1.4).
Bug 9892137: MAKE IT EASIER TO CHANGE CONFIGURATION FILES FOR WEBCENTER
Changes made on the configuration files could be lost. So you will have to backup those files in case of any upgrade, change.
On version above PS3, it was solved:
http://download.oracle.com/docs/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#CHDGEDGJ
Changes must be done using Enterprise Manager or WLST, so the configuration will be saved on the MDS directly.

Hope you like it,
Zeeshan Baig

How to Change Weblogic Domain MODE to Production and Development

Hi all,

Last week i experienced a little task to change the "Production mode" settings to TRUE in weblogic domain. Setting up the mode to true was easy and straight forward but a little trick comes where for some reasons we had to rollback that change to test some issues.

If you want to know what are the differences between the two modes check this post

To configure all servers in a domain to run in production mode:

1. Login to Weblogic Console
2. In the left pane of the WebLogic Console, under Domain Structure, select the domain name.
3. Select Configuration > General and select the Production Mode check box.
4. Click Save, and then, to activate these changes, in the Change Center, click Activate Changes.
5. Start and stop any servers that are currently running.

You can see the settings on the following screen shot after making change you should be able to see the following messages in log files.

Reminder: Once the mode set to PRODUCTION you cannot change it from Weblogic Console

So here are the steps to configure all servers in a domain back to development mode. Weblogic server stores its information in a configuration file.

1. Stop the servers running in a domain.
2. Open the config.xml file location under MIDDLEWARE_HOME/domains/domain_name/config
3. Change the production-mode entry to false and save the file and exit
4. Start all servers you should be able to see the following message on console.

P.S  you can also set the value PRODUCTION_MODE to true or false in setDomainEnv.sh file but if you want to backout the change you need to change the config.xml file

Hope you find it useful,
Zeeshan Baig

Difference between Weblogic Production and Development Mode

Hi all,

Here is a quick view of a differences between Production and Development mode of Weblogic server.

Development mode:

1. The default JDK for development domain is Sun Hotspot.
2. Admin Server uses an automatically created boot.properties during startup
3. The debugFlag which is used to start the WebLogic Workshop Debugger is enabled.
4. You can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL. For more information about managing security, see "Configuring SSL" in Securing WebLogic Server at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs90/secmanage/ssl.html
5. WebLogic Server instances can automatically deploy and update applications that reside in the domain_name/autodeploy directory (where domain_name is the name of a domain).It is recommended that this method be used only in a single-server development environment.For more information, see "Auto-Deploying Applications in Development Domains" in Deploying Applications to WebLogic Server at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs90/deployment/deploy.html#autodeploy.
6. When you start a server, the server automatically renames (rotates) its local server log file as server-name.log.n. For the remainder of the server session, the server rotates its local log file whenever the size of the file reaches 500 kilobytes.

Production mode:

1. The default JDK for production domain is JRockit
2. If you use the demo certificates for SSL a warning is displayed
3. Admin Server prompts for username and password during startup
4. The default maximum capacity for JDBC Datasource is 25
5. The debugFlag which is used to start the WebLogic Workshop Debugger is disabled.
6. The auto-deployment feature is disabled, so you must use the WebLogic Server Administration Console, the WebLogic Deployer tool, or the WebLogic Scripting Tool (WLST)
7. A server rotates its local log file after the size of the file reaches 5000 kilobytes. When the server is configured for production mode, by default, all versions of the log files are retained. Administrators may want to customize the number of log files retained.

Feel free to add more

Have a nice day,

Zeeshan Baig

Jdeveloper Release 2 (11.1.2) is out

Hi all,

The biggest news of the year for Fusion developer is that Jdeveloper release 2 is available to download. JDEV R2 supports JSF 2.0 and Facelets and many great features.

Check the following links

Download http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html


New Features http://www.oracle.com/technetwork/developer-tools/jdev/jdev-11gr2-nf-404365.html

Tutorials http://download.oracle.com/docs/cd/E18941_01/tutorials/toc.htm

Documentation Lib http://download.oracle.com/docs/cd/E16162_01/index.htm

Don't forget to follow me on Twitter and subscribe this blog on email and Rss to get tutorials.

Happy Jdeveloping,
Zeeshan Baig

Compressing application EAR files from Jdeveloper

Hi,

A quick tip before deploying your application project you can compress it as well. this will help to make lesser time to deploy to weblogic server.

To compress the ear file do the following before deployment

1. Go to Application properties Click on deployments
2. Click Edit after selecting the deployment profile

3. Select EAR Options on left panel. Click Compress archive and choose compress level as shown in the slide.

4. Deploy the file to ear and you can see the result files are of different sizes.

Have a nice day,
Zeeshan Baig