Wednesday, March 27, 2013

How to Increasing the heap size (virtual memory) for JBoss in Quality Center

For Windows, you can increase the heap size by uninstalling/reinstalling the Quality Center Service and modifying the InstallJbossService.bat file. For Linux/Unix, you need to modify the file.
Recommended heap sizes, depending on the number of concurrent user sessions:
Small: 128 - 256MB ~ Up to 10 concurrent user sessions

Medium: 256 - 512MB ~ Up to 100 concurrent user sessions

Large: 512 - 1024MB ~ Up to 250 concurrent user sessions

Very Large: 1024 - 2048MB ~ Up to 350 concurrent user sessions

The max value cannot be more than your max RAM size.

On any Windows 32-bit installation you cannot set a heap size larger than 1024 MB of RAM.

Uninstall/Reinstall QC Service for Windows:
Note: Verify that users are not working on Quality Center and Quality Center Service is stopped. 1. Open Command Prompt and navigate to "<Drive Letter:>\program files\Mercury Interactive\Quality Center\jboss\bin" folder.
Note: For Quality Center 9.0 and 9.2 the path is "<Drive Letter:>\program files\Mercury\Quality Center\jboss\bin"
           For Quality Center 10 the path is "<Drive Letter:>\program files\HP\Quality Center\jboss\bin

2. Execute the following command (this will uninstall the existing service):
   InstallJbossService.bat -uninstall
3.Edit the InstallJbossService.bat file.
If the heap memory is currently:
   set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx512m
increase the heap size as follows:
   set JAVA_OPTS=%JAVA_OPTS% -Xms512m -Xmx1024m
4. Save and close the InstallJbossService.bat.
5. Execute the following command (this will install the service with the modified heap size parameter):
   InstallJbossService.bat -c default (-help shows options)
6. Verify that the service has been installed, Control Panel -> Administrative Tools -> Services.
7. Start the Quality Center Service.
8. Check that the Quality Center Debug Console shows heap size that was specified as available memory:

For Quality Center 9.0 and 9.2:

For Quality Center 10:


If you are using a cluster environment, the hostname should be the cluster machine name, and you will need to apply the above steps to each cluster.

Also edit the run.bat file to ensure it is synchronized with the way the QC service runs.

Add the following parameter in site administration's 'Site Configuration' tab to grant access to the debug info log:
     Value: N Modify the run.bat file:
1. On the application server, locate the JBoss bin folder under your TD for QC installation. By default, the location is <System Drive:>\Program Files\Mercury Interactive\Quality Center\JBoss\bin. Note: For Quality Center 9.0 and 9.2 the path is <System Drive:>\Program Files\Mercury\Quality Center\JBoss\bin.
           For Quality Center 10 the path is <System Drive:>\Program Files\HP\Quality Center\JBoss\bin
2. Edit the run.bat file (or for Linux/Unix).
If the heap memory is currently:
   set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx512m
increase the heap size as follows:
   set JAVA_OPTS=%JAVA_OPTS% -Xms512m -Xmx1024m
3. Save and close the run.bat.
4. Execute the file only for Linux/Unix.

Tuesday, March 12, 2013

step by step how to Configure Apache Webserver with Weblogic Server

Step 1) Make sure the Apache server runs on port 8080.( This is because sometimes IIS, or some antivirus s/w runs on that port).This can be done by modifying the httpd.conf present at
D:\Program Files\Apache Group\Apache2\conf
Modify the Listen port to 8080
Listen 8080
Step 2) Copy the from <bea_home>\wlserver_10.3\server\plugin\win\32 to
D:\Program Files\Apache Group\Apache2\modules
Step 3) Add these lines in the httpd.conf file
LoadModule weblogic_module modules/
<Location />
SetHandler weblogic-handler
<IfModule mod_weblogic.c>
WebLogicCluster localhost:7003,localhost:7005
Debug ON
WLLogFile c:/temp/wlproxy.log
WLTempDir c:/temp
Step 4) Restart Apache and access the application deployed on the Cluster using
This will forward the request to the Weblogic Cluster

Saturday, March 9, 2013

How to upgrade Java version from 1.6 to 1.7

Step 1: First download the tar file of java ( jre-7u5-linux-i586.tar.gz) using below URL

Step 2: tar -zxvf /Path to 'jre-7u5-linux-i586.tar.gz'/
Step 3: Move extracted folder to /usr/lib/jvm

#sudo cp -r jre1.7.0_05 /usr/lib/jvm/
Step 4: Install java now
#sudo update-alternatives –install /usr/bin/java java /usr/lib/jvm/jre1.7.0_05/bin/java 3

Step 5: Now choose the upgraded java version from :-
#sudo update-alternatives –config java


We have to select 4 for my system.. choose :- /usr/lib/jvm/jdk1.7.0_04/bin/java
Step 6: Now create a soft link:-
#sudo ln -s /usr/lib/jvm/jre1.7.0_05/lib/i386/ ~/.mozilla/plugins/

Step 7: Now check java version with the below command
#sudo java -version
you should get 1.7 java version in the output.

Tuesday, March 5, 2013

LDAP and how is it used by Weblogic server?

Lightweight Directory Access Protocol (LDAP) is a protocol that programs use to look up contact information from a server. Much like a relational database, every LDAP database (or directory) has a schema. An LDAP schema is implemented as a set of object class definitions and attribute definitions.
Some common terms used in LDAP are:
  • dc= domain component
  • o = organization
  • ou= organizational unit
  • cn= common name
  • dn= distinguished name
  • uid= user id
When you need to search for an entry in LDAP, you must provide the base of the search and a filter.
For example:
ldapsearch -b "dc=beasys,dc=com" uid=fred
This will return all the attributes of the user who has uid=fred as specified in the filter:
uid=fred,ou=People, dc=beasys,dc=com   //this is what is referred to as Full DN
cn=Fred A

This entry is seen in the LDAP tree as the following:

/     (root)          \
/                          \
/                             \
ou=people             ou=otherusers

WLS can read and search information from an external directory server, giving it the right configuration information to connect, bind, search (base and filter), etc.

For this you need to configure the following fields in WLS:
  • LDAP server host and port
  • Principal/password used to connect and make the search
  • User Base DN: used as a base when making a user search
  • User filter: used as a filter when making a user search
  • Group Base DN: used as a base when making a group search
  • Group filter: used as a filter when making a group search
  • Group membership filter: used as a filter when doing a search to find groups a user belongs to
Within these fields, you can find the following characters:
%u is replaced by the user id
%g is replaced by the group
%M is replaced by the Full DN of the user

When WLS needs to verify that a user exists and has privilege/role to access a resource, it connects to LDAP using the principal defined and then does a search on the user, verifies that it exists, and authenticates using its password. After that, it searches the groups the user belongs to.
Following is some concise pseudocode for the membership check algorithm:
check_membership(group g, principal p):
for each group g1 that contains p directly:
if g1 == g or check_membership(g, g1)
then return success
return failure

Once this is done, WLS verifies if the user that belongs to the groups found has the privilege/role to access the resource requested, and based on that either permits the access or denies it.

Common LDAP servers used in WLS

The common LDAP servers used in WLS (as authentication providers) are:
  • Default Authenticator (Embedded LDAP)
  • IPlanet
  • Active Directory
  • OpenLDAP
  • Novell