QualityCenterAPI

Someone might have accidentally deleted the Test scripts/ Test Runs/ Defect even then no need to worry since we found a solution to retrieve deleted artifacts in HP ALM/QC

2016-04-29T02:42:00.000-07:00

Did you ever got into a situation where you are pressurized to retrieve the deleted artifacts in ALM and when you looked at DB backup those records are there. No need to worry if your backend is oracle.

When we got into this situation below are SQL statements which we have executed to retrieve the deleted test scripts in Test Plan module.

Below are Queries which you can execute it to retrieve the deleted test scripts in the test plan module. If you want to test these follow the below steps.

Create a test folder and underneath create test scripts in test plan module. Delete the folder and then execute the following queries by updating the date and time when those test scripts are created.

insert into test
SELECT * FROM TEST as of timestamp to_timestamp('26-03-2016 12:27','DD_MM_YYYY HH24:MI') where ts_test_id not in (select ts_test_id from TEST)

insert into TEST_CONFIGS
SELECT * FROM TEST_CONFIGS as of timestamp to_timestamp('26-03-2016 12:27','DD_MM_YYYY HH24:MI') where tsc_test_id not in (select tsc_test_id from TEST_configs)

insert into TEST_CRITERIA
SELECT * FROM TEST_CRITERIA as of timestamp to_timestamp('26-03-2016 12:27','DD_MM_YYYY HH24:MI') where tcr_test_id not in (select tcr_test_id from TEST_CRITERIA)

QC/ ALM – Bug. As an end user we say it is Bug but HP says that’s how the product is designed and they say it’s a client specific requirement.

2016-04-25T03:29:00.000-07:00

This is the story of one of fortune 100 HealthCare company. Since they are into HealthCare business, any application which is either directly or indirectly dealing with the patient related information it should be a validated system, meaning should comply with CFR part 12 FDA guidelines. For these applications Quality Center/ ALM tool is being used for the test management hence as per the requirements QC/ALM should be validated.

Robust workflows are created using QC/ALM customization to comply with FDA guidelines and satisfy the compliance requirement. These workflows are working fine if the end users are trying to perform any action (correctly restricting the update/delete of approved entity) using front end UI. And the problem comes in when all the rules are bypassed if the users are trying to update an approved entity using excel plug-In. We got into a situation where we need to disable the excel upload feature to the end users and allow it only to specific users(ALM administrators).

Below is the trigger which is being deployed to accomplish.

create or replace TRIGGER Val_user

BEFORE INSERT ON PROJECT_SESSIONS

FOR EACH ROW

DECLARE

CType varchar(255);

uname varchar(255);

BEGIN

select LS_Client_Type,LS_USER_NAME into CType,uname from Login_Sessions where ls_id=:New.ps_ls_id;

IF CType= 'OTAClient' and uname not in(‘<User Name>’) and

((instr(:New.PS_PROJECT_NAME,'_GxP') >1))) then

RAISE_APPLICATION_ERROR(-20000, 'Y');

End if;

END;

Perfromance Testing.

2013-05-11T10:27:00.001-07:00

What is performance testing all about?

Let me give you a real time example that if you want to check your balance in an ATM center you will insert your card in ATM and the ATM machine will ask you to enter your PIN number after validating that information it will ask you to select what type of transaction you would like to make.
In the above example what if ATM machine is taking around 15 minutes to ask your PIN and so on…
Will you be able to wait such a long period and will show interest in using that ATM again.
Answer for that without second thought is NO.
It means performance of the application is poor so performance is directly propositional to the response time. Unfortunately most of the developers including me will not follow the coding standards that resulting in poor performance.
If the client requirement is to add 2 numbers, being a developer I may or may not follow the coding standards while declaring variables and also defining the formula but I will make sure that it will accept the input values from the user and will give the result by adding those 2 numbers but there is no guaranty that this will work if “N” numbers of users are using it at a time. Unfortunately I am least bothered about it.

Who (Business Owner/Development Lead/Testing Lead/Developer/Tester) is responsible for it?

Everyone is responsible for this. But unfortunately nobody will take the responsibility of it.

Quality Center LDAP Authentication

2012-08-16T12:11:00.000-07:00

Important distinction should be made when working with LDAP. There are two phases. First is the import. In this phase you need an LDAP account that has the privileges to import users. Of course, an ‘admin’ of the LDAP is the best suitable.

The second phase is the actual usage of the imported account by the QC user. In this phase, the user does not make usage of the "importer" LDAP account. QC delegates the user's DN ('Distinguished Name' – a unique user identifier) as imported before to the LDAP and grants or denies access according to the LDAP reply.

The user's password is not stored in QC - it is managed by the LDAP. When a user password is modified in the site, QC does not need to know about it.

Importing users from LDAP:

Obtain the URL of your LDAP server and enter it in the ‘Authentication Settings->Directory Provider URL’. The URL convention is: ldap://myserver:port. You can use this convention in the following combinations:

'<Server name>'

'ldap://<server name>'

'ldap://<server name>:<custom port>'

· Check with LDAP administrator if secure LDAP is used. In this case you might need to use ‘ldaps’ when creating the connection (‘ldaps://<server name>’).

· The default ports for LDAP are 389 (regular) and 636 (secure)

· This check verifies only the connection URL, not access rights.

Once you have successfully established a connection you can continue to importing users. Open the ‘LDAP Import Settings’ Dialog.
‘Directory Provider URL’ will be similar to what you have used in the previously in ‘‘Authentication Settings’
Depending on your site policy you can choose between ‘Anonymous’ account if that was set with sufficient privileges to import users or you must obtain a user account that was given appropriate grants. Notice that in sites using security it is not likely that ‘Anonymous’ will have sufficient grants.
If ‘Anonymous’ is not used then a ‘Simple->Authentication Principle’ account is to be used. LDAP identifies any object (a 'user' object in our case) in the tree as a path combination of nodes from current node to root node. This unique string combination is called a DN (distinguished name). For example, consider the below screen shot of an LDAP tree, that starts with a domain called 'CSOIL'.

In this example the ‘Administrator’ 'node' is a DN combined of the 'nodes' going from end to start:

'CN=Administrator, CN=Users, DC=CSOIL'

· The above DN is partial path only. In real example it will be with more root elements.

· You will need to ask your LDAP admin for the DN to authenticate with.

In order to understand more about LDAP terminology find table below with famous LDAP abbreviations and terms that are usually concerning an object of type 'user':

LDAP term	Explanation
CN	Common Name. CN is the combination of First name and last name. Attribute is made up from givenName joined to SN (surname). For example: CN=Yariv Gadish
DN	Distinguished Name. DN is simply the most important LDAP attribute. For example: CN=Yariv Gadish, OU=CSO ,DC= CO ,DC=IL
OU	Organizational unit. For Example: OU=CSO
DC	Domain Components. For example: DC=IL
SN	SN is the last name or surname. For example: SN=Gadish
sAMAccountName	sAMAccountName is the NT 4.0 logon name. For example: sAMAccountName=gadishy
userPrincipalName	userPrincipalName. Often abbreviated to UPN, and looks like an email address. For example: userPrincipalName=yariga@mercury.com
givenName	Firstname also called Christian name
name	Name. The same as CN. Example: name=Yariv Gadish

After completing the first dialog of ‘LDAP Import Settings’ the next screen will ask you for more details.
‘Directory base’. Here you can choose if you want to import from the root of the LDAP tree, or from a sub node.

Another way to filter objects is to use the ‘Base Filter’. Here you can specify classes that will fit certain objects only. You can use logical ‘OR’ (‘|’) and/or ‘AND’ (‘&’) to create a condition made of several sub conditions.

For example, search for users which are defined of class ‘user’ or of class ‘person’:

(|(objectClass=user)(objectClass=person))

Another example - Search for a Single User:

(&(|(objectClass=user)(objectClass=person))(CN=Yariv))

Note that:

· The logical operator joining the conditions is at the start of the statement.

· A user entity might be defined as made of different ObjectClass.

Next you have two possible buttons, ‘Set Default for Active Directory’ and ‘Set Default for LDAP’. Pressing this buttons will set the field mappings between the LDAP user and the imported QC user. As the name of the buttons implies, these will set the mappings to the default standards used in either category. Note that ‘Active Directory’ means the Microsoft implementation for LDAP.
If you do not have default names used for your user objects, you need to click the ‘advanced’ button.
In the ‘advanced->Field Mapping’ dialog you can specify your naming conventions as used on your LDAP server.

Sending Email from the Quality Center Workflow

2012-08-16T12:04:00.001-07:00

Sending an E-Mail from the Workflow

Purpose: The following code template allows sending any object in TestDirector (Defect, Test, etc.) by e-mail. The code can be used to extend the automatic mail notifications with custom conditions, not available for Send All Qualified. The template uses TestDirector mailing functions.

Code Location: The code for the each object should be placed in the script of the corresponding module. For example: SendDefect function should be placed in Defects module.

Arguments:

iObjectId – The ID of the object that should be sent (see the note below on how to obtain the object ID).

strTo – The TestDirector names or e-mails of the people that will appear in To field of the e-mail (the names and e-mails should be separated by semicolon. For example: “user@domain.com;admin;alice_td”).

strCc – The TestDirector names or e-mails of the people that will appear in Cc field of the e-mail (the names and e-mails should be separated by semicolon. For example: “user@domain.com;admin;alice_td”). Specify an empty string (“”) to omit this parameter.

strSubject – The e-mail Subject. Specify an empty string (“”) to omit this parameter.

strComment – The e-mail comment (will appear at the top of the e-mail). Specify an empty string (“”) to omit this parameter.

Notes:

1. The object ID value can always be retrieved using the {Object}_Fields collection, by retrieving the Value property of the ID field. The example below shows how to retrieve the Ids of Defect, Test and Requirement:

’ Defect ID – for SendDefect

Bug_Fields(“BG_BUG_ID”).Value

’ Test ID – for SendTest

Test_Fields(“TS_TEST_ID”).Value

’ Requirement ID – for SendReq

Req_Fields(“RQ_REQ_ID”).Value

2. The templates for Defect, Test and Requirement are provided. However the function may be used to work with any object that has Mail function.

3. The third parameter in Mail function allows specifying e-mail options. In the templates below this parameter is hard-coded (its value 2 means that the object History will be sent). However you can change this value to any of the values of TDMAIL_FLAGS. You can use sum to combine the mail properties. For example: 1 – means “send attachments”; 2 – means “send history”. In order to send the mail with attachments and history, specify 3 for this argument.

Return Value: None

Code Template:

Sub SendDefect (iObjectId, strTo, strCc,

strSubject, strComment)

On Error Resume Next

Dim objBugFactory, objBug

Set objBugFactory = TDConnection.BugFactory

Set objBug = objBugFactory.Item(iObjectId)

objBug.Mail strTo, strCc, 2, strSubject, strComment

Set objBug = Nothing

Set objBugFactory = Nothing

PrintError “SendDefect”

On Error GoTo 0

End Sub

^{''''''''''''''''''''''''''''''''''''''''''}

Sub SendTest (iObjectId, strTo, strCc,

strSubject, strComment)

On Error Resume Next

Dim objTestFactory, objTest

Set objTestFactory = TDConnection. TestFactory

Set objTest = objTestFactory.Item(iObjectId)

objTest.Mail strTo, strCc, 2, strSubject, strComment

Set objTest = Nothing

Set objTestFactory = Nothing

PrintError “SendTest”

On Error GoTo 0

End Sub

^{'''''''''''''''''''''''''''''''''''''''''''''}

Sub SendRequirement (iObjectId, strTo, strCc,

strSubject, strComment)

On Error Resume Next

Dim objReqFactory, objReq

Set objReqFactory = TDConnection.ReqFactory

Set objReq = objReqFactory.Item(iObjectId)

objReq.Mail strTo, strCc, 2, strSubject, strComment

Set objReq = Nothing

Set objReqFactory = Nothing

PrintError “SendRequirement”

On Error GoTo 0

End Sub

^{''''''''''''''''''''''''''''''''''''''''}

Usage Example: In the following example when the test status is changed, the e-mail notification is sent to the designer of the test, cc to all the members of the [QA Testers] group.

Sub TestPlan_Test_FieldChange(FieldName)

On Error Resume Next

Dim strSubject, strComment

If FieldName = "TS_STATUS" Then

strSubject = “Test Change Notification” & _

“ for project “ & TDConnection.ProjectName & _

“ in domain “ & TDConnection.DomainName

strComment = “The user “ & User.FullName & _

“ changed the status of the test ” & _

Test_Fields(“TS_NAME”).Value & _

“ to “ & Test_Fields(“TS_ STATUS”).Value

SendTest Test_Fields("TS_TEST_ID").Value, _

Test_Fields(“TS_RESPONSIBLE”).Value, “[QA Testers]”, _

strSubject, StrComment

End If

On Error GoTo 0

End Sub

Error Handling

2012-08-16T11:58:00.003-07:00

. Error Handling

Use “On Error Resume Next” statement at the beginning of each procedure and function.
Use “On Error GoTo 0” at the end of each procedure or function
Show errors to the user in some standard message box

Compare the following code fragments:

If Bug_Fields(“BG_SEVERITY”).Value = “4-Urgent” Then

Bug_Fields(“BG_PRIORITY”).Value = “4-Urgent”

End If

On Error Resume Next

...

If Bug_Fields(“BG_SEVERITY”).Value = “4-Urgent” Then

Bug_Fields(“BG_PRIORITY”).Value = “4-Urgent”

End If

...

PrintError “SomeSub”

On Error GoTo 0

The both code fragments will work the same way when no problems arise during the code execution. But what happens if, for example, the user has no permissions to modify BG_PRIORITY field? The left fragment will not update the field and will cause the browser crash. The second will not update the field, but it will show the correct error to the user and the browser will not crash.

How to Know the audit log entries of a Bug

2012-03-01T10:45:00.000-08:00

Below is the query which will provide the complete information of a bug. This info will be extracted from the audit table. You need to update the bug id in the where for which you wanted the info.

SELECT AL.AU_USER, AL.AU_TIME, AP.AP_PROPERTY_NAME,

AP.AP_NEW_VALUE, AP.AP_NEW_LONG_VALUE, AP.AP_NEW_DATE_VALUE,AL.AU_ACTION

FROM AUDIT_LOG AL, AUDIT_PROPERTIES AP, BUG B

WHERE (AL.AU_ACTION_ID = AP.AP_ACTION_ID)

AND (TO_CHAR(B.BG_BUG_ID) = TO_CHAR(AL.AU_ENTITY_ID))

AND (B.BG_BUG_ID = <Bug Id>)

AND (AL.AU_ENTITY_TYPE = 'BUG')

ORDER BY AU_TIME ASC

Quality Center Project Migration

2012-03-01T10:38:00.000-08:00

I just wanted to share my experience in migrating a project from QC9.2 to QC10

We have got a requirement from the user to migrate QC9.2 project using SQL server 2005 as backend to QC10 Oracle. I had tried couple of options to migrate this and finally finalized the below process to complete this task. We even contacted the HP to know the best approach but unfortunately they don’t have process to accomplish this.

1) We have created DB user (QC) on QC9.2 SQL server 2005.

2) Added SQL Server DB server in QC10 server using DB servers Tab

3) Created a project in QC10 using SQL Server 2005 DB server which was added in the previous step.

4) Created a project in QC9.2 by selecting make a copy of existing project.

5) Removed project from site admin and Updated the db.xml file of the project which is created in step 2 with the project schema which is created step 4.

6) Upgraded the project in QC10 by following steps (Verify, Repair and Upgrade).

7) Exported the upgraded project to generate .qcp file.

8) Imported the upgraded file by selecting Oracle as DB ( Migration from SQL server 2005 to Oracle was completed in this step by tool itself).

9) Copied the attachments folder from QC9.2 NAS to Our QC10 NAS.

Quality Center Project Migration

2011-09-05T05:52:00.000-07:00

If you want to migrate a project from one server to another you need to export the project schema in source server and import it in the target server. Export and import process depends on the backend which you are using. In addition to that you have to execute the below steps depending on the type of the db you using.

Steps for SQL Server:
Run the following SQL procedure on imported schema.
· EXEC sp_change_users_login 'Report'
This unlinks the "td" user.
· EXEC sp_change_users_login 'Update_One', 'td', 'td';
This links the "td" user of the TestDirector database to the same ID as the "td" user

Restore Process:(Common for both SQL and Oracle)
On the new Quality Center Site Administrator follow the next steps in order to restore the projects:
•Create a backup of the repository.

<Drive>:\Program Files\Mercury\Quality Center\repository\qc\<Domain>\<Project>\

•Create an empty project pointing to the new database server to compare the parameters of the dbid.xml file.

•Edit the parameters on the dbid.xml file as explained on the bellow image:

•Go to the QC Site Administrator and restore the project.
•Upgrade the project.

QC API Reference Guides

2011-08-30T04:48:00.000-07:00

Below are the links to download the OTA and site admin reference guides.
OTA Client Reference Guide
Site Admin Reference Guide

C# .NET program that uses the Quality Center API

2011-08-23T02:25:00.000-07:00

How to create a C# .NET program that uses the Quality Center API?
Description:
This example adds a defect to a project using C# .NET.
Usage:
1. Select File -> New -> Project.
2. Select Console Application for template.
3. Give the project a Name.

Example:
AddDefect
4. In the menu, select Project -> Add Reference.
5. Navigate to the COM tab.
6. Select OTA COM 8.0 Type Library.
7. Click <OK>.
8. In the Solution Explorer tab, select the Class1.cs file.
9. Add the code below.
Code:
using System;
using TDAPIOLELib;

namespace AddDefect
{
   /// <summary>
   /// Summary description for Class1.
   /// </summary>
   class Class1
   {
      /// <summary>
      /// The main entry point for the application.
      /// </summary>
      [STAThread]
      static void Main(string[] args)
      {
         TDConnectionClass td = new TDAPIOLELib.TDConnectionClass();
         try
         {
            td.InitConnectionEx("http://<servername>/tdbin");
            //Note: For Quality Center, connect by using the URL below:
            td.InitConnectionEx("http://<servername>:port/qcbin");
            td.ConnectProjectEx("DomainName","ProjectName","Username","Password");
         }
         catch
         {
            Console.WriteLine("Failed to connect to server.");
         }
         try
         {
            IBugFactory bfact = td.BugFactory as IBugFactory;
            IBug mybug = bfact.AddItem("MyBug1")as IBug;
            mybug.Summary = "This is a test.";
            mybug.Status = "Open";
            mybug.AssignedTo = "admin";
            mybug.Post();
         }
         catch
         {
            Console.WriteLine("Failed to add defect.");
         }
         try
         {
            td.DisconnectProject();
            td.ReleaseConnection();
         }
         catch
         {
            Console.WriteLine("Failed to disconnect server and/or project.");
         }
      }
   }
}

VB Script application using Quality Center API

2011-08-23T02:20:00.000-07:00

How to create a VBScript application using Quality Center API?
Description:
This example adds a defect to a project using VBScript.
Usage:
1. Open a text editor.
2. Add the code below.
3. Save it with .asp extenstion.
4. Place the file on your Web server.

Example:
C:\inetpub\scripts
5. Open the .asp page by entering the URL:
   http://<servername>/scripts/AddDefect.asp
Code:
<%@ LANGUAGE=VBSCRIPT %>

<HTML>
<HEAD>
<TITLE> Example using TDAPI </TITLE></HEAD>
<BODY>
<FORM NAME="Example TDAPI">

<%
dim td 'TDConnection
dim mybug
dim bfact

'Create TDConnection object
set td = createobject("TDApiOle80.TDConnection.1")

'Connecting to your tdserver
td.initconnectionex "http://<servernam>/tdbin"
'Note: For Quality Center, connect by using the URL below:
'td.InitConnectionEx "http://<servername>:port/qcbin"
'Connecting to the project
td.ConnectProjectEx "DomainName", "ProjectName", "UserName", "Password"

'Get bug factory
Set bfact = td.BugFactory

'Add defects
Set mybug = bfact.AddItem("Defect")
mybug.Summary = "Test"
mybug.Status = "Open"
mybug.Post

'Release Project Connection.

if td.Connected then
    if td.ProjectConnected then
       td.DisconnectProject
    end if
    td.releaseconnection
end if

%>

Defect added!!!
</FORM>

</BODY>

</HTML>

<%
mybug = null
bfact = null
td = null
%>

Visual Basic Program that uses the Quality Center API

2011-08-23T02:17:00.000-07:00

How to create a Visual Basic program that uses the Quality Center API?

Description:
This example adds a defect to a project using Visual Basic 6.0.
Usage:
1. Open Microsoft Visual Basic 6.0.
2. From the menu, select File -> New Project, and choose Standard EXE.
3. From the menu, select Project -> References -> OTA COM 8.0 Type Library.
4. Click <OK>.
5. Double-click on the form.
6. Add the code below.

Code:
Private Sub Form_Load()
Dim td As New TDConnection
td.InitConnectionEx "http://<servername>/tdbin"
'Note: For Quality Center, connect by using the URL below:
'td.InitConnectionEx "http://<servername>:port/qcbin"
td.ConnectProjectEx "DomainName", "ProjectName", "UserName", "Password"

Dim bfact As BugFactory
Dim mybug As Bug
Set bfact = td.BugFactory
'Add defects
Set mybug = bfact.AddItem("Defect")
mybug.Summary = "Test"
mybug.Status = "Open"
mybug.Post

td.DisconnectProject()
td.ReleaseConnection()
MsgBox ("Added 1 new defect!")
Set mybug = Nothing
Set bfact = Nothing
Set td = Nothing
End Sub

C++ program that uses the Quality Center API

2011-08-23T02:14:00.000-07:00

How to create a C++ program that uses the Quality Center API?

Description:
This example adds a new defect to a project using Visual C++.
Usage:
1. Open Microsoft Visual C++ 6.0.
2. From the menu, select File -> New.
3. Navigate to the Projects tab.
4. Select Win32 Application.
5. Enter a name for your project. Example:
AddDefect
6. Select a location for your project.
7. Click <OK>.
8. Select the "A Simple Win32 application" radio button.
9. Click <Finish>.
10. Click <OK>.
11. Select the File View tab in the Workspace window.
12. Under the Source Files folder, open AddDefect.cpp.
13. Add the code below.
Code:
#import "C:\Program Files\Common Files\Mercury Interactive\TD2000_80\OTAClient80.dll" no_namespace named_guids
void AddDefect();
int APIENTRY WinMain(HINSTANCE hInstance,
   HINSTANCE hPrevInstance,
   LPSTR lpCmdLine,
   int nCmdShow)
{
   // !!! You are working with COM -every thread (main thread also) must initialize COM run-time library
   CoInitialize(NULL);
   // Call the AddDefect function here
   AddDefect();
   // Release COM run-time library
   CoUninitialize();
   return 0;
}
void AddDefect()
{
    try
    {
      _bstr_t mydata;
      // Creating a new TDConnection object and all the required objects for a TestDirector connection.

      ITDConnectionPtr sp_td;
      IBugFactoryPtr bFact;
      IBugPtr mybug;
      variant_t myBugData(mydata);
      //Connect to the server and project
      sp_td.CreateInstance(CLSID_TDConnection);
      sp_td->InitConnectionEx("http://<servername>/tdbin");

      //Note: For Quality Center, connect by using the URL below:
      sp_td->InitConnectionEx("http://<servername>:port/qcbin");
      sp_td->ConnectProjectEx("DomainName", "ProjectName","UserName", "Password");
      MessageBox(NULL,"Connected to project !","",0);
      //TODO: Place code here to add defect
      //The following code will add a new defect.
      bFact = sp_td->GetBugFactory();
      mybug = bFact->AddItem(myBugData);
      //Adding value to the Assigned To and the Project field for this new defect
      //To add information to other fields of this defect, just enter the information here.
      mydata = "admin";
      mybug->PutAssignedTo(mydata);
      mydata ="Project";
      mybug->PutProject(mydata);
      mybug->Post();
      MessageBox(NULL,"A new defect added !","",0);
      //Disconnect from project and release connection from the server.
      sp_td->DisconnectProject();
      sp_td->ReleaseConnection();
      MessageBox(NULL,"Done !","",0);
   }
   //Catch exception by reference (the most optimal way to catch exceptions)
   catch(_com_error& err)
   {
      MessageBox(NULL,err.Description(),"",0);
   }
}

QC10 Upgrade Issues

2011-08-23T01:19:00.000-07:00

Benchmark document and kit for ALM 11

2011-08-23T01:02:00.000-07:00

Use the below link to download ALM 11 benchmark tool kit.
http://support.openview.hp.com/selfsolve/document/KM1112929

Quality Center JBoss cluster with Apache as the load-balancer

2011-08-22T23:01:00.001-07:00

How to implement a JBoss cluster with Apache as the load-balance?

Below are the steps explained in the KM189086 to implement this.

Configuring Apache as a load-balancer for JBoss cluster nodes1. Download and install Apache2 Web Server.
2. Make sure that it is working properly before proceeding further. Example:
http://<servername>
3. Install Quality Center on the 1st server node. Below are some steps that need to be taken:

Since this is the first node, you will want to select the "First node/Standalone" option during installation when selecting Cluster configuration.
For repository path, you need to select a shared folder that is accessible for all your Secondary nodes.
Example:
\\&ltservername>\respository
Note:
For information on how to performed a mount on Linux/Unix, please refer to the link below:
Document ID 35095 - How to mount a file system for Quality Center 8.2 in a cluster environment
For Web Server Configuration, select Apache as the "Web Server that you want to integrate with JBoss."

4. After installation has completed, you need to confirmed that Apache-JBoss integration works correctly.
Example: http://<Server_Name>/qcbin
5. Install Quality Center on the 2nd, 3rd, etc. nodes.
Note:
There are a few points to consider during installation of Secondary nodes:

Secondary nodes must be installed on the same operating system. You cannot have one node that is install on Windows 2000 and others on Windows 2003 or Linux 9 or Unix 8.
You must select the "Secondary node" option when selecting Cluster configuration.
Secondary nodes will need to run JBoss as the web server. As a result, you need to select "Run JBoss As Web Server" option for Web Server Configuration.
The domain repository must points to the same shared (mounted) repository. In this case, the domain repository is the same shared folder that was entered in installation of the 1st server node. Again, you will need to use a network path that is accessible for all nodes.
The Site Administrator Database Name must be the same. This means that you will need to connect to the same database server and schema.
Example:
qcsiteadmin_db

6. Open the Apache configuration file, httpd.conf, under <APACHE_HOME>\conf on the 1st server node. You will see the following lines were added:

Windows:

Unix

Linux

Notes:

The first line loads the mod_jk which is the JBoss-Apache plug-in that handles communication between JBoss and Apache. The second line request Apache to read the configuration setting in the mod_jk.conf file.
If Apache fails to integrate with JBoss after installation on a Linux/Unix OS, please refer to Document ID 35254 - Failed to install Quality Center on Solaris/Linux when integrating with Apache.
Your JBoss installation path is dependent on where you installed Quality Center. Please make a note of this when implementing the procedures below. The path given here is the default path.

7. Open the mod_jk.conf file located in the path indicated in step 6. Edit the file as indicated below:

Windows:

Unix:

Linux:

8. Open the workers.properties file located under the path specified in step 7. Make the following modifications:

Note:

9. Restart the server node. Please refer to Document ID 33218 - How to start/stop the deployment of Quality Center on the application server for more information. 10. Log into the Site Administrator and navigate to the Servers tab. You should now see two cluster nodes.
Note:
Any update made to one cluster node will be reflected in all nodes in the cluster. If a node goes off-line, Apache will check its state periodically and in the meantime, forward requests to peer workers (application server nodes). The load-balancer schedule is based on a weighted round-robin load balancing system with sticky sessions.
Related Articles:
Document ID 34235 - How to implement a WebLogic cluster using Apache as a load balancer for QC 8.0

Increasing the heap size (virtual memory) for JBoss

2011-08-22T10:33:00.000-07:00

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 run.sh 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
Notes:

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.
Example:
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:
   http://hostname:8080/qcbin/servlet/tdservlet?method=debuginfo
   http://hostname:8080/sabin/servlet/tdsiteadminservlet?method=debuginfo

For Quality Center 10:
   http://hostname:8080/qcbin/debug

Notes:

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:
Name: DISABLE_CONSOLE_DEBUG_INFO
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 run.sh for Linux/Unix).
Example:
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 run.sh file only for Linux/Unix.

Quality Center Useful SQL Statements

2011-08-22T10:08:00.000-07:00

Below is the link to get the list of KB which talks about useful QC SQL statements.

http://support.openview.hp.com/selfsolve/document/KM179211

Quality Center LDAP

2011-08-21T22:28:00.000-07:00

How to change the authentication from LDAP to Quality Center when LDAP server is down?

Below are the steps to change the Authentication from LDAP to QC.
1. In the qcsiteadmin_db database, find the PARAMS table.
2. Look for the record where PARAM_NAME = 'Authentication'. Change the PARAM_VALUE to 'QualityCenter'.
3. Look for records where PARAM_NAME starts with 'LDAP', and delete all of them except one 'LDAP_SEARCH_USER_CRITIRIA'.
4. Restart the Quality Center service using the Quality Center icon in system tray.
5. Users should be able to log in using Quality Center authentication.

Quality Center multi language support

2011-08-12T02:42:00.000-07:00

How to enter different language in Quality Center?

1) Go To Start--> Control Panel--> Regional and Language Option

2) Select your desired language in Standards and formats field under Regional Options tab

3) Select the same language selected in step 2 in Language for non-Unicode programs under advanced tab.

4) Click on apply button.

5) Pop up windows appears asking you to restart the machine to apply changes

6) Click on ok button to restart the machine

7) On restarting the machine login to Quality Center and select the preferred language keyboard layout

8) Type the required data so that selected language would be visible in QC.

NOTE: All the project team users need to update the language settings in their individual machine to overcome the corrupted data. If one user uses Chinese language and enter the data and other user with English language settings go to that particular data only junk letters will be visible. Though the user with Chinese settings checks backs the data later on, only junk letters will be visible. It is advisable that whole team uses the same settings before logging into Quality Center.

DB server migration

2011-08-11T01:15:00.000-07:00

Below are the detailed steps to move the Database to another server.

You will need to:

1. Update the siteadmin.xml file on the application server

2. Modify the dbid.xml for all the projects.

Step 1. Updating the siteadmin.xml file on the application server

Note: Remember to make a backup of DB and Repository before any change. Also, move all the DB to the new DB server before perform the following steps.

For JBoss
1.Make a backup copy of the 20qcbin.war file found in the <QC_HOME>/application directory.

Linux/Unix:
mv -i 20qcbin.war sabin_bak.war

2. Move 20qcbin.war from <QC_HOME>/jboss/server/default/deploy to <QC_HOME>/application, and rename it to qcbin.war. This step will ensure all previous modifications are preserved.

Linux/Unix:
cp -i <QC_HOME>/application/jboss/server/default/deploy/20qcbin.war qcbin.war

3. Extract qcbin.war to a temporary directory (Ex. qcbin).

Example:
cd <QC_HOME>\application\20qcbin
jar xf <QC_HOME>\application\20qcbin.war

4. Open the siteadmin.xml file for editing (e.g., this file will be found at <QC_HOME>\application\20qcbin\WEB-INF).

5. Update the siteadmin.xml file using a text editor. Modify the <DbUrl>jdbc:mercury:sqlserver://qcsrv10:1433</DbUrl> with the correct information for the new DB server.

6. Zip up the qcbin.war file.

Example:

cd <QC_HOME>\application\qcbin
jar cvf qcbin.war *

7. Copy the qcbin.war file from <QC_HOME>\application\qcbin to <QC_HOME>\jboss\server\default\deploy.

Linux/Unix:
cp -i qcbin.war <QC_HOME>/jboss/server/default/deploy/qcbin.war

8. Rename the qcbin.war file to 20qcbin.war.

Linux/Unix:
mv -i qcbin.war 20qcbin.war

9. Restart the Quality Center service.

For Weblogic

Please refer to Document ID KM188675 - How to manually deploy or undeploy Quality Center Web application modules on WebLogic server

For WebSphere

Please refer to Document ID KM191173 - How to manually deploy or undeploy Quality Center web application modules on WebSphere server

Note:
Please refer to Document ID 186840 - How to start/stop the deployment of Quality Center on the application server for instructions on how to start/stop the deployment of Quality Center.

Notes:

· <QC_HOME> is the installation directory of Quality Center.

· The default location on Windows is C:\Program Files\Mercury Interactive\Quality Center.

· The default location on Linux/Unix is /opt/Mercury_Interactive/Quality_Center/.

Step 2. Modify the dbid.xml for all the projects

You need to update all the dbid.xml files for all the projects to update the information about the new DB server.

1. Log into the Site Administrator.

2. Remove one of the projects.

3. Search for it dbid.xml file.

4. Edit the file:

* <DB_CONNSTR_FORMAT>jdbc:mercury:sqlserver://qcsrv10:1433</DB_CONNSTR_FORMAT> (Use the same as in the siteadmin.xml file)

* <DBSERVER_NAME>qcsrv10</DBSERVER_NAME>

* <PHYSICAL_DIRECTORY>C:\Quality Center\repository\qc\Domain\ProjectName\</PHYSICAL_DIRECTORY>

5. Save the file.

6. Return to Site Administrator.

7. Right click on the Domain and click on Restore.

8. Search for this dbid.xml file and click on Restore.

9. After the project is restored, click on Upgrade.

10. Activate the project.

11. Try to login to this project.

12. Repeat the steps from 1 to 11 for the rest of the projects.

Quality Center: Export and Import Oracle database

2011-08-08T07:27:00.000-07:00

Exporting Oracle Users

When migrating an Oracle project database, you export users from the source database server and import them to the target database server.
To export an Oracle user:
1. Open the exp utility in the Command Prompt dialog box and log in to theserver with administrator permissions.

Choose Start -> Run. The Run dialog box opens.

In the Open box, type cmd and click OK.

In the Command Prompt dialog box, type exp and press Enter.

Specify the user name and password of the user that has administratorpermissions. For example, system. 2. When the Enter array fetch buffer size: 4096 prompt is displayed, pressEnter to select the default size.
3. When the Export file: EXPDAT.DMP prompt is displayed, specify the pathand the name of the target dump file with the .DMP extension. For example,d:exportmy_proj.dmp.
4. When the (1)E(ntire database), (2)U(sers), or (3)T(ables): (2)U prompt isdisplayed, press Enter to select the default option (2)U(sers).
5. For the prompts that follow, press Enter to accept the default values.
6. When the User to be exported: (RETURN to quit) prompt is displayed,specify the user name that you want to export and press Enter. If you wantto export several users to the same dump file, perform the same step for eachuser.
7. Press Enter to exit the User to be exported: (RETURN to quit) prompt andstart the exporting process.

Importing Oracle Users

To import an Oracle user you need to create a tablespace for the user and then create a default Oracle user. You can then import the TestDirector Oracle user from the dump file. To import an Oracle user:
1. Create a tablespace with the same name as the one on the source Oracleserver, as follows:

In the DBA Studio, under the Storage root, right-click the Tablespacesfolder and choose Create.

Specify the name and the size of the tablespace. The name must be thesame as the one on the source Oracle server. The size of the tablespacemust be set according to the imported user.

Click Create.

2. Create the Oracle user in the tablespace, as follows:

In the DBA Studio, under Security node, right-click the Users folder andchoose Create.

Specify the user name. It is recommended that you use the same name asthe one used in the source database server.

In Enter Password and Confirm Password, type the password for thisuser.

In the Tablespaces section, select the tablespace you have previouslycreated.

Select a temporary tablespace.

Click the Quota tab. Select the tablespace you have previously created,and select Unlimited.

Select the temporary tablespace you have previously selected, and selectUnlimited.

Click Create. Note: You can also create a user using the following query:
CREATE USER <dbUser> IDENTIFIED BY password DEFAULT TABLESPACE <tableSpace>
TEMPORARY TABLESPACE <tempTableSpace> QUOTA UNLIMITED ON
<tableSpace>QUOTA UNLIMITED ON <tempTableSpace>
Note:
You should grant the dbUser the following permissions for TestDirector 7.2, 7.6, and 8.0:
GRANT CONNECT, RESOURCE TO <dbUser>;
3. Create a batch file (with the .BAT extension) to invoke the Oracle importutility and the user from a given dump file.
Specify the command as follows:
imp <user name>/<password> file=<source dump file> log=<log file>
IGNORE=Y GRANTS=Y BUFFER=20000 FEEDBACK=1000
fromuser=<original user name> touser=<the new user>
Where:

Syntax	Description
<user name>	The user name with administrator permissions on the Oracle server. For example, system.
<password>	The password of the specified user.
<source dump file>	The location and the source dump file (with the .DMP extension).
<log file>	The location and file name to be used by the imp utility when logging the import process.
<original user name>	The original name of the Oracle user on the source Oracle server.
<the new user>	The name of the new user.

Example:
imp system/manager file=d:/exportmy_proj.dmp log=d:/importmy_proj_imp.log IGNORE=Y GRANTS=Y BUFFER=20000 FEEDBACK=1000 fromuser=td_project_db touser=td_new_project_db
To import several Oracle users, you create new users on the target databaseserver, and specify the source and target users in the fromuser and touserparameters. Make sure that you separate each user by a comma.
For example, suppose you want to import 2 users (td_proj1 and td_proj2) tothe new users (td_new1 and td_new2):
imp system/manager file=d:exportmy_proj.dmp log=d:importmy_proj_imp.logIGNORE=Y GRANTS=Y BUFFER=20000 FEEDBACK=1000 fromuser=td_proj1,td_proj2 touser=td_new1,td_new2
4. Execute the batch file created in the previous step. After the importingprocess is complete, you can view the log file.
Note: If you are only importing one user, then you can run the imp command directly from the Dos-Prompt.

Load Runner Silver light protocal

2011-08-08T01:06:00.000-07:00

Load Runner Javaoverhttp protocal

2011-08-08T00:52:00.000-07:00