Zhengol: Let's start here

Fix Error 1720 - Windows Installer Error

2011-02-22T23:04:00.000+08:00

Fix Error 1720 - Windows Installer Error

The detail error message is :

Error 1720: There is a problem with this windows installer package. A script required for this install to complete could be run. Contact your support personnel or package vendor.

The ways to fix this issue:

a. Install proper windows installer and try again.

b. If a does not work, register dll and ocx as below

Regsvr32 wshom.ocx

Regsvr32 scrrun.dll

Mark-- What happened to IBM Rational Forum today?

2011-01-18T18:29:00.001+08:00

Mark-- What happened to IBM Rational Forum today?

What happened to IBM Rational Forum today? I posted a problem yesterday on ClearQuest forum and today found there is no thread in ClearQuest Forum at all. Many other forums have the same problem. Have a mark here. J

IBM Rational Forum

http://www.ibm.com/developerworks/forums/dw_rforums.jspa

IBM ClearQuest Forum

http://www.ibm.com/developerworks/forums/forum.jspa?forumID=329

IBM ClearCase Forum

http://www.ibm.com/developerworks/forums/forum.jspa?forumID=333

FW: ClearQuest Ldap Settings with Windows Active Directory

2010-12-31T16:45:00.001+08:00

ClearQuest Ldap Settings with Windows Active Directory

In ClearQuest, it gives ldap option for user authentication. I have a try to setup the Windows AD as ldap server and enable integration between ClearQuest and Windows AD. Here are the summary of the setup.

a. In windows 2003 or 2000 server, setup domain controller. After promoted as domain controller, the server plays the role of ldap server as well. You can check whether the ldap service is up or not by below commands,

Netstat –a | find “ldap”

If the service is up, it outputs that ldap port is listening.

b. Download Ldap Admin Tool which acts as a ldap client to check the directory structure. It is a must to know this before you can successfully know its structure. For the Windows AD, the directory structure looks like,

DC=VM_TESTINGLAB -- VM_TESTINGLAB is the domain name of windows AD

CN=Users

CN=Administrator --the default administrator user name

CN=Cert Publishers

CN=cq_search -- another domain user which will be used later as the search user to look up ldap entries.

CN=Domain Admins -- the default domain administrator group

CN=Domain Computerrs -- the computer list in the domain

……………..

c. After we know the structure, we can enable the integration then by running below commands

installutil setauthenticationalgorithm db_set_name cq_admin_user cq_admin_user_pwd CQ_ONLY -- this command is to set ClearQuest to use itself as a user authentication method.

installutil setldapinit db_set_name cq_admin_user cq_admin_user_pwd "-h ldap_server_name -p 339 -D cn=cq_search,cn=Users,dc= VM_TESTINGLAB -w cq_search_password" -- this command is to set ldap related information for ClearQuest like what is the ldap server name, which port is used by that ldap server, which user ClearQuest should use for ldap entries search, what is this user’s DN?. In above command, the ldap server is ldap_server_name, port is 339 (default ldap port), cq_search is the user for ClearQuest to check the ldap entries. So this id must be added in windows AD and have ldap lookup privilege. According to the directory structure above, the user’s DN is cn=cq_search,cn=Users,dc= VM_TESTINGLAB. Actually I do not know how to setup a user with ldap directory lookup privilege in a AD but just add this user as administrators group instead. A member in administrators group must have full access right to all resources.

installutil setldapsearch db_set_name cq_admin_user admin_user_pwd "-s sub -b dc=vm_ol (&(objectCategory=person)(sAMAccountName=%login%)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))" -- this command is to set the search string for ClearQuest to lookup ldap user entries. –b specifies the base DN. In this case, it is dc=vm_ol. –s indicate ClearQuest to search the sub entries under vm_ol. (&(objectCategory=person)(sAMAccountName=%login%)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) string is what the ClearQuest help document says, just follow it without any changes.

installutil setcqldapmap db_set_name cq_admin_user admin_user_pwd CQ_LOGIN_NAME sAMAccountName -- this command is to set which user attribute to map to the ldap sAMAccountName (also a attribute of a AD user). CQ_LOGIN_NAME means to map the login to sAMAccountName. There are other options you can use like CQ_EMAIL, CQ_FULLNAME, CQ_LOGIN_NAME, CQ_MISC_INFO, or CQ_PHONE. For example, if CQ_LOGIN_NAME is used, then input the login name to login ClearQuest. If CQ_EMAIL is used, then input the user mail address to login ClearQuest instead of login name. But in this case, the email address must be same as the value of sAMAccountName in ldap side.

installutil validateldap db_set_name cq_admin_user admin a_ldap_user a_ldap_user_pwd -- this command is to check if the setup is correct. I failed many times during my setup. It mainly caused by 2 issues. Firstly, the search user in setldapinit step must be created in AD and should have directory lookup privilege(just give this id a administrator role). Secondly, search string(filter) in setldapsearch is not setup correctly. Remember just put the top dn after –b.

installutil setauthenticationalgorithm db_set_name cq_admin_user admin CQ_FIRST -- this command is to let ClearQuest know it’s time to use ldap for user authenticatiton.

d. After all those done, you can open ClearQuest user administration tool to add a user and check the ldap option . Then when user login ClearQuest, the login will pass to ldap for login authentication.

PS, keep in mind that do not change cq_search and its password in AD, else any ldap enabled user can not login ClearQuest. In multisite, if all sites’ settings are same, just run the exact commands in working master site and then sync those updates to other sites. Else with –site option in each site. Lastly, you can disable ldap with below commands

installutil setauthenticationalgorithm db_set_name cq_admin_user admin_user_pwd CQ_ONLY

installutil setldapinit db_set_name cq_admin_user admin_user_pwd -allsites -remove

installutil setldapsearch db_set_name cq_admin_user admin_user_pwd -allsites -remove

installutil setcqldapmap db_set_name cq_admin_user admin_user_pwd -allsites –remove

or temporily disable ldap with below command,

installutil setauthenticationalgorithm db_set_name cq_admin_user admin_user_pwd CQ_ONLY

This is pretty much of what I know about ClearQuest and LDAP integration.

VOB Creation Error Handling

2010-10-19T00:49:00.003+08:00

Users with ClearCase Administrator role sometimes still can not create VOB successfully although it have RW access control right to storage locations. Below alert message will prompt up

Creating VOB:

VOB Creation Wizard:Error:Failed to record hostname "xxxx" in storage directory "xxxxxx".Check the root or the ClearCase administrators group has permission to write to this directory.

VOB Creation Wizard:Error:Unable to create versioned object base "xxxxxx"

In this situation, user should check access right of the log on user of system service "Atrial Location Broker" and make sure the user has also RW right to the storage location. Add that user to administrators group on the machine which host the storage location if no.

PS, for any exception during cc operations, users can check Log Browser which logs the detailed error messages for further investigation.

CM API Usage Guide

2010-05-04T14:49:00.001+08:00

CM API Usage Guide

CM API is introduced in Rational 7.1. It has implement java interface between JAVA and CC/CQ applications. Using CM API, java client can do task like,

1. populate users in cq database

2. submit, update, delete records in cq database

3. check out/in a element version

4. others like perl, vbs do in privious version.

Here is brief introducton of CM API.

http://www.svn8.com/xm/200907/25-7686.html

How to Set Dynamic Parameter of Query From External Script

2010-04-23T14:45:00.001+08:00

How to Set Dynamic Parameter of Query From External Script

Below is the perl code

##############################################

my $workSpace=$userSession->GetWorkSpace(); #$userSession should be created before

#Personal Queries/Dymic is a query with 2 dynamic fields state and submit date
my $queryDef=$workSpace->GetQueryDef("Personal Queries/Dymic");
my $rstSet=$userSession->BuildResultSet($queryDef);

# set state value list
$rstSet->AddParamValue(1,"Submitted");
$rstSet->AddParamValue(1,"Assigned");

# first set compare operator for the submit date. 9 means "between"
$rstSet->SetParamComparisonOperator(2,9);
# then set 2 time value for between
$rstSet->AddParamValue(2,"2010-04-23 00:00:00");
$rstSet->AddParamValue(2,"2010-04-23 23:59:59")
$rstSet->Execute;
print $rstSet->GetSQL();

##############################################

The output likes this,
select distinct T1.dbid,T1.id from new_defect T1,statedef T2 where T1.state = T2.id and (T1.dbid 0 and ((T2.name in ('Submitted','Assigned') and T1.submit_date between {ts '2010-04-21 08:00:00'} and {ts '2010-04-23 08:00:00'})))

How to share folders under Linux Ubuntu

2010-04-22T14:15:00.001+08:00

Here is the detail steps to setup

https://help.ubuntu.com/community/SettingUpSamba

Best Regards
Oliver Zheng
Tel: 86-756-3398810

How to Resolve Data Incosistent in ClearQuest and ClearCase

2010-02-26T17:39:00.001+08:00

How to Resolve Data Incosistent in ClearQuest and ClearCase

After ClearQuest and ClearCase Integration, users may happend to below error,

Could not perform requested operation: a UCM/ClearQuest data

inconsistency may exists:

"activityxxxxx.xxxxx" was expected to be linked to a ClearQuest record, but is not.

What is the cause of the problem,

This occurs when there are multiple ClearQuest user databases with the same name as the one that is UCM enabled.

How to diagnosing the problem,

Run below command,

cleartool checkvob -ucm -force -crm_only project:<UCM_ENABLED_CC_PROJECT_NAME>@\PVOB_NAME

Note: this command will list all problem cc activities under ucm project

How to Resolving the problem,

Determine which connection to be removed

Run below 2 commands in order

cleartool checkvob -ucm -fix -crm_dbname <CLEARQUEST_USERDATABASE> -project project:<UCM_ENABLED_CC_PROJECT_NAME>

Note: this command will find a most likely record(for example,headline is same) in <CLEARQUEST_USERDATABASE> and match its id into cc activity

cleartool checkvob -ucm -fix -force -crm_only project:<UCM_ENABLED_CC_PROJECT_NAME>@\PVOB_NAME

Note: this command will create UCMActivities in CQ db if no matched cq records are found.

Putty Usage Guide

2010-02-26T09:51:00.001+08:00

Putty Usage Guide -- very detailed guide from 柴锋

http://chaifeng.com/blog/2007/06/putty_200611.html

Setup Summary of a Ubuntu Linux machine

2010-02-24T17:30:00.001+08:00

Setup Summary of a Ubuntu Linux machine

We plan to setup a Linux machine to run some jobs and also it can provides us a environment to practice in Linux. So we decide to use Ubuntu 9.10.

The whole installation was smooth since it really simple. Just insert Installation disk into CD-ROW and reboot the machine to start installation.

This post is to log the issues when I setup the whole machine and the way I solve those issues.

How to remotely control Ubuntu from windows desktop ?

a. Install TightVNC Viewer into windows client. You can download the file here,

http://sourceforge.net/projects/vnc-tight/

b. Configure Ubuntu to allow user control the machine remotely.

Click System->Preferences->Remote Deksop

In the Remote Desktop Preferences, click ‘Allow other users to view your desktop’ and ‘Allow other users to ontrol your desktop’ and click Close.

c. In windows machine, open TightVNC Viewer and input the Ubuntu machine name/IP address into VNC server and click Connect button.

So far, you can see the Ubuntu desktop in the viewer. If some security settings are enabled in Remote Desktop Preferences, you may input the password when connect to Ubuntu via TightVNC Viewer.

Notes: if you can not login Ubuntu via viewer, you need to check if the Ubuntu has enable the network.

How to setup FTP server in Ubuntu

I googled this topic and find a command to do this,

sudo apt-get update

sudo apt-get install vsftpd

But with back luck, I got below erros,

407 Proxy Authentication Required (The ISA Server requires authorization to fullfill the request.Access t the Web proxy service is denied). I still do not resolve this issue by now although I tried many many ways. So I suggest you to skip this issue to install the package directly and let it be. It saves you lots of time especially if you are newbie like me.

a. Check your machine has valid IP address via command: ifconfig. I can get the IP address once I finish installation.

b. Configure FireFox to access internet web pages. (in most cases, you need to input proxy server information as in Windows platform)

c. Login Ubuntu packages website and download vsftpd deb package. Do not use google this time, just this website and it is almost enough.

http://packages.ubuntu.com/

d. Use below command to install the package

sudo dpkg –i vsftpd-xxx-xxx.deb

e. Then configure the ftp. You can find the configure file under /etc/vsftpd.conf. Here is the detail for your refernece,

http://vsftpd.beasts.org/vsftpd_conf.html

f. And start the services with root. The ftp service will start once Ubuntu reboot as a service.

/etc/init.d/vsftpd start|stop|restart|reload|status

Hah. You can ftp from your windows to Ubuntu if all go smooth.

Send Mail via remote SMTP Server on Ubuntu

2010-02-22T16:17:00.001+08:00

Sometimes we need to send out mail from linux but do not want to setup a mail server on it. Below is a simple way to implement this function with a existing smtp server.

a. install package nail with below command

apt-get install nail

or you can search the nail package in http://packages.ubuntu.com

b. edit /etc/nail.rc and add below lines in the end of the file

set smtp=the_existing_smtp_server

c. use below command to send out mail

nail -s your_subject -a your_attachment to_add1 to_add2 < msg_content_file

How to check CQ License Usage

2010-01-28T10:24:00.001+08:00

How to check CQ License Usage

After CQ client installed, some useful tools can be founder under Common folder.

If we want to check the CQ license usage, we can use lmutil.exe command sets by below command

lmutil.exe lmstat -f CLEARQUEST (detail information)

lmutil.exe lmstat -i CLEARQUEST (summary information)

Actually lmutil can find out all types of licenses information which host on FLEXlm server. For example, below commands list out CC license data.

lmutil.exe lmstat -f CLEARCASE (detail information)

lmutil.exe lmstat -i CLEARCASE (summary information)

To find out usage of lmstat, you can use

lmutil.exe lmstat -h

to find out all sub command sets of lmutil, you can use

lmutil.exe -h

Log4J Configuraton (ZT)

2009-12-10T17:50:00.001+08:00

Log4J的配置文件(Configuration File)就是用来设置记录器的级别、存放器和布局的，它可接key=value格式的设置或xml格式的设置信息。通过配置，可以创建出Log4J的运行环境。

1. 配置文件
Log4J配置文件的基本格式如下：

#配置根Logger
log4j.rootLogger  =   [ level ]   ,  appenderName1 ,  appenderName2 ,  …

#配置日志信息输出目的地Appender
log4j.appender.appenderName  =  fully.qualified.name.of.appender.class
　　log4j.appender.appenderName.option1  =  value1
　　…
　　log4j.appender.appenderName.optionN  =  valueN

#配置日志信息的格式（布局）
log4j.appender.appenderName.layout  =  fully.qualified.name.of.layout.class
　　log4j.appender.appenderName.layout.option1  =  value1
　　…
　　log4j.appender.appenderName.layout.optionN  =  valueN

其中 [level] 是日志输出级别，共有5级：

FATAL       0
ERROR      3
WARN       4
INFO         6
DEBUG      7

Appender 为日志输出目的地，Log4j提供的appender有以下几种：

org.apache.log4j.ConsoleAppender（控制台），
org.apache.log4j.FileAppender（文件），
org.apache.log4j.DailyRollingFileAppender（每天产生一个日志文件），
org.apache.log4j.RollingFileAppender（文件大小到达指定尺寸的时候产生一个新的文件），
org.apache.log4j.WriterAppender（将日志信息以流格式发送到任意指定的地方）

Layout：日志输出格式，Log4j提供的layout有以下几种：

org.apache.log4j.HTMLLayout（以HTML表格形式布局），
org.apache.log4j.PatternLayout（可以灵活地指定布局模式），
org.apache.log4j.SimpleLayout（包含日志信息的级别和信息字符串），
org.apache.log4j.TTCCLayout（包含日志产生的时间、线程、类别等等信息）

打印参数: Log4J采用类似C语言中的printf函数的打印格式格式化日志信息，如下:

　  %m   输出代码中指定的消息
　　%p   输出优先级，即DEBUG，INFO，WARN，ERROR，FATAL
　　%r   输出自应用启动到输出该log信息耗费的毫秒数
　　%c   输出所属的类目，通常就是所在类的全名
　　%t   输出产生该日志事件的线程名
　　%n   输出一个回车换行符，Windows平台为"\r\n"，Unix平台为"\n"
　　%d   输出日志时间点的日期或时间，默认格式为ISO8601，也可以在其后指定格式，比如：%d{yyy MMM dd HH:mm:ss , SSS}，输出类似：2002年10月18日  22 ： 10 ： 28 ， 921
　　%l   输出日志事件的发生位置，包括类目名、发生的线程，以及在代码中的行数。举例：Testlog4.main(TestLog4.java: 10 )

2. 在代码中初始化Logger:
1）在程序中调用BasicConfigurator.configure()方法：给根记录器增加一个ConsoleAppender，输出格式通过PatternLayout设为"%-4r [%t] %-5p %c %x - %m%n"，还有根记录器的默认级别是Level.DEBUG.
2）配置放在文件里，通过命令行参数传递文件名字，通过PropertyConfigurator.configure(args[x])解析并配置；
3）配置放在文件里，通过环境变量传递文件名等信息，利用log4j默认的初始化过程解析并配置；
4）配置放在文件里，通过应用服务器配置传递文件名等信息，利用一个特殊的servlet来完成配置。

3. 为不同的 Appender 设置日志输出级别：
当调试系统时，我们往往注意的只是异常级别的日志输出，但是通常所有级别的输出都是放在一个文件里的，如果日志输出的级别是BUG！？那就慢慢去找吧。
这时我们也许会想要是能把异常信息单独输出到一个文件里该多好啊。当然可以，Log4j已经提供了这样的功能，我们只需要在配置中修改Appender的Threshold 就能实现,比如下面的例子：

[配置文件]

### set log levels ###
log4j.rootLogger = debug ,  stdout ,  D ,  E

### 输出到控制台 ###
log4j.appender.stdout = org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target = System.out
log4j.appender.stdout.layout = org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern =  %d{ABSOLUTE} %5p %c{ 1 }:%L - %m%n

### 输出到日志文件 ###
log4j.appender.D = org.apache.log4j.DailyRollingFileAppender
log4j.appender.D.File = logs/log.log
log4j.appender.D.Append = true
log4j.appender.D.Threshold = DEBUG ## 输出DEBUG级别以上的日志
log4j.appender.D.layout = org.apache.log4j.PatternLayout
log4j.appender.D.layout.ConversionPattern = %-d{yyyy-MM-dd HH:mm:ss}  [ %t:%r ] - [ %p ]  %m%n

### 保存异常信息到单独文件 ###
log4j.appender.D = org.apache.log4j.DailyRollingFileAppender
log4j.appender.D.File = logs/error.log ## 异常日志文件名
log4j.appender.D.Append = true
log4j.appender.D.Threshold = ERROR ## 只输出ERROR级别以上的日志!!!
log4j.appender.D.layout = org.apache.log4j.PatternLayout
log4j.appender.D.layout.ConversionPattern = %-d{yyyy-MM-dd HH:mm:ss}  [ %t:%r ] - [ %p ]  %m%n

[代码中使用]

public   class  TestLog4j  {
     public   static   void  main(String[] args)  {
        PropertyConfigurator.configure( " D:/Code/conf/log4j.properties " );
        Logger logger  =  Logger.getLogger(TestLog4j. class );
        logger.debug( " debug " );
        logger.error( " error " );
    }
}

运行一下，看看异常信息是不是保存在了一个单独的文件error.log中

log4j.properties 使用
一.参数意义说明
输出级别的种类
ERROR、WARN、INFO、DEBUG
ERROR 为严重错误主要是程序的错误
WARN 为一般警告，比如session丢失
INFO 为一般要显示的信息，比如登录登出
DEBUG 为程序的调试信息
配置日志信息输出目的地
log4j.appender.appenderName = fully.qualified.name.of.appender.class
1.org.apache.log4j.ConsoleAppender（控制台）
2.org.apache.log4j.FileAppender（文件）
3.org.apache.log4j.DailyRollingFileAppender（每天产生一个日志文件）
4.org.apache.log4j.RollingFileAppender（文件大小到达指定尺寸的时候产生一个新的文件）
5.org.apache.log4j.WriterAppender（将日志信息以流格式发送到任意指定的地方）
配置日志信息的格式
log4j.appender.appenderName.layout = fully.qualified.name.of.layout.class
1.org.apache.log4j.HTMLLayout（以HTML表格形式布局），
2.org.apache.log4j.PatternLayout（可以灵活地指定布局模式），
3.org.apache.log4j.SimpleLayout（包含日志信息的级别和信息字符串），
4.org.apache.log4j.TTCCLayout（包含日志产生的时间、线程、类别等等信息）
控制台选项
Threshold=DEBUG:指定日志消息的输出最低层次。
ImmediateFlush=true:默认值是true,意谓着所有的消息都会被立即输出。
Target=System.err：默认情况下是：System.out,指定输出控制台
FileAppender 选项
Threshold=DEBUF:指定日志消息的输出最低层次。
ImmediateFlush=true:默认值是true,意谓着所有的消息都会被立即输出。
File=mylog.txt:指定消息输出到mylog.txt文件。
Append=false:默认值是true,即将消息增加到指定文件中，false指将消息覆盖指定的文件内容。
RollingFileAppender 选项
Threshold=DEBUG:指定日志消息的输出最低层次。
ImmediateFlush=true:默认值是true,意谓着所有的消息都会被立即输出。
File=mylog.txt:指定消息输出到mylog.txt文件。
Append=false:默认值是true,即将消息增加到指定文件中，false指将消息覆盖指定的文件内容。
MaxFileSize=100KB: 后缀可以是KB, MB 或者是 GB. 在日志文件到达该大小时，将会自动滚动，即将原来的内容移到mylog.log.1文件。
MaxBackupIndex=2:指定可以产生的滚动文件的最大数。
log4j.appender.A1.layout.ConversionPattern=%-4r %-5p %d{yyyy-MM-dd HH:mm:ssS} %c %m%n
日志信息格式中几个符号所代表的含义：
-X号: X信息输出时左对齐；
%p: 输出日志信息优先级，即DEBUG，INFO，WARN，ERROR，FATAL,
%d: 输出日志时间点的日期或时间，默认格式为ISO8601，也可以在其后指定格式，比如：%d{yyy MMM dd HH:mm:ss,SSS}，输出类似：2002年10月18日 22：10：28，921
%r: 输出自应用启动到输出该log信息耗费的毫秒数
%c: 输出日志信息所属的类目，通常就是所在类的全名
%t: 输出产生该日志事件的线程名
%l: 输出日志事件的发生位置，相当于%C.%M(%F:%L)的组合,包括类目名、发生的线程，以及在代码中的行数。举例：Testlog4.main (TestLog4.java:10)
%x: 输出和当前线程相关联的NDC(嵌套诊断环境),尤其用到像java servlets这样的多客户多线程的应用中。
%%: 输出一个"%"字符
%F: 输出日志消息产生时所在的文件名称
%L: 输出代码中的行号
%m: 输出代码中指定的消息,产生的日志具体信息
%n: 输出一个回车换行符，Windows平台为"\r\n"，Unix平台为"\n"输出日志信息换行
可以在%与模式字符之间加上修饰符来控制其最小宽度、最大宽度、和文本的对齐方式。如：
1)%20c：指定输出category的名称，最小的宽度是20，如果category的名称小于20的话，默认的情况下右对齐。
2)%-20c:指定输出category的名称，最小的宽度是20，如果category的名称小于20的话，"-"号指定左对齐。
3)%.30c:指定输出category的名称，最大的宽度是30，如果category的名称大于30的话，就会将左边多出的字符截掉，但小于30的话也不会有空格。
4)%20.30c:如果category的名称小于20就补空格，并且右对齐，如果其名称长于30字符，就从左边较远输出的字符截掉。
二.文件配置Sample1
log4j.rootLogger=DEBUG,A1,R
#log4j.rootLogger=INFO,A1,R
# ConsoleAppender 输出
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%-d{yyyy-MM-dd HH:mm:ss,SSS} [%c]-[%p] %m%n
# File 输出一天一个文件,输出路径可以定制,一般在根路径下
log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
log4j.appender.R.File=blog_log.txt
log4j.appender.R.MaxFileSize=500KB
log4j.appender.R.MaxBackupIndex=10
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSS} [%t] [%c] [%p] - %m%n
文件配置Sample2
下面给出的Log4J配置文件实现了输出到控制台，文件，回滚文件，发送日志邮件，输出到数据库日志表，自定义标签等全套功能。
log4j.rootLogger=DEBUG,CONSOLE,A1,im
#DEBUG,CONSOLE,FILE,ROLLING_FILE,MAIL,DATABASE
log4j.addivity.org.apache=true
###################
# Console Appender
###################
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.Threshold=DEBUG
log4j.appender.CONSOLE.Target=System.out
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n
#log4j.appender.CONSOLE.layout.ConversionPattern=[start]%d{DATE}[DATE]%n%p[PRIORITY]%n%x[NDC]%n%t[THREAD] n%c[CATEGORY]%n%m[MESSAGE]%n%n
#####################
# File Appender
#####################
log4j.appender.FILE=org.apache.log4j.FileAppender
log4j.appender.FILE.File=file.log
log4j.appender.FILE.Append=false
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n
# Use this layout for LogFactor 5 analysis
########################
# Rolling File
########################
log4j.appender.ROLLING_FILE=org.apache.log4j.RollingFileAppender
log4j.appender.ROLLING_FILE.Threshold=ERROR
log4j.appender.ROLLING_FILE.File=rolling.log
log4j.appender.ROLLING_FILE.Append=true
log4j.appender.ROLLING_FILE.MaxFileSize=10KB
log4j.appender.ROLLING_FILE.MaxBackupIndex=1
log4j.appender.ROLLING_FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.ROLLING_FILE.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n
####################
# Socket Appender
####################
log4j.appender.SOCKET=org.apache.log4j.RollingFileAppender
log4j.appender.SOCKET.RemoteHost=localhost
log4j.appender.SOCKET.Port=5001
log4j.appender.SOCKET.LocationInfo=true
# Set up for Log Facter 5
log4j.appender.SOCKET.layout=org.apache.log4j.PatternLayout
log4j.appender.SOCET.layout.ConversionPattern=[start]%d{DATE}[DATE]%n%p[PRIORITY]%n%x[NDC]%n%t[THREAD]%n%c[CATEGORY]%n%m[MESSAGE]%n%n
########################
# Log Factor 5 Appender
########################
log4j.appender.LF5_APPENDER=org.apache.log4j.lf5.LF5Appender
log4j.appender.LF5_APPENDER.MaxNumberOfRecords=2000
########################
# SMTP Appender
#######################
log4j.appender.MAIL=org.apache.log4j.net.SMTPAppender
log4j.appender.MAIL.Threshold=FATAL
log4j.appender.MAIL.BufferSize=10
log4j.appender.MAIL.From=chenyl@yeqiangwei.com
log4j.appender.MAIL.SMTPHost=mail.hollycrm.com
log4j.appender.MAIL.Subject=Log4J Message
log4j.appender.MAIL.To=chenyl@yeqiangwei.com
log4j.appender.MAIL.layout=org.apache.log4j.PatternLayout
log4j.appender.MAIL.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n
########################
# JDBC Appender
#######################
log4j.appender.DATABASE=org.apache.log4j.jdbc.JDBCAppender
log4j.appender.DATABASE.URL=jdbc:mysql://localhost:3306/test
log4j.appender.DATABASE.driver=com.mysql.jdbc.Driver
log4j.appender.DATABASE.user=root
log4j.appender.DATABASE.password=
log4j.appender.DATABASE.sql=INSERT INTO LOG4J (Message) VALUES ('[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n')
log4j.appender.DATABASE.layout=org.apache.log4j.PatternLayout
log4j.appender.DATABASE.layout.ConversionPattern=[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n
log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender
log4j.appender.A1.File=SampleMessages.log4j
log4j.appender.A1.DatePattern=yyyyMMdd-HH'.log4j'
log4j.appender.A1.layout=org.apache.log4j.xml.XMLLayout
###################
#自定义Appender
###################
log4j.appender.im = net.cybercorlin.util.logger.appender.IMAppender
log4j.appender.im.host = mail.cybercorlin.net
log4j.appender.im.username = username
log4j.appender.im.password = password
log4j.appender.im.recipient = corlin@yeqiangwei.com
log4j.appender.im.layout=org.apache.log4j.PatternLayout
log4j.appender.im.layout.ConversionPattern =[framework] %d - %c -%-4r [%t] %-5p %c %x - %m%n
三.高级使用
实验目的：
1.把FATAL级错误写入2000NT日志
2. WARN，ERROR，FATAL级错误发送email通知管理员
3.其他级别的错误直接在后台输出
实验步骤：
输出到2000NT日志
1.把Log4j压缩包里的NTEventLogAppender.dll拷到WINNT\SYSTEM32目录下
2.写配置文件log4j.properties
# 在2000系统日志输出
log4j.logger.NTlog=FATAL, A8
# APPENDER A8
log4j.appender.A8=org.apache.log4j.nt.NTEventLogAppender
log4j.appender.A8.Source=JavaTest
log4j.appender.A8.layout=org.apache.log4j.PatternLayout
log4j.appender.A8.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
3.调用代码：
Logger logger2 = Logger.getLogger("NTlog"); //要和配置文件中设置的名字相同
logger2.debug("debug!!!");
logger2.info("info!!!");
logger2.warn("warn!!!");
logger2.error("error!!!");
//只有这个错误才会写入2000日志
logger2.fatal("fatal!!!");
发送email通知管理员：
1. 首先下载JavaMail和JAF,
  http://java.sun.com/j2ee/ja/javamail/index.html
  http://java.sun.com/beans/glasgow/jaf.html
在项目中引用mail.jar和activation.jar。
2. 写配置文件
# 将日志发送到email
log4j.logger.MailLog=WARN,A5
# APPENDER A5
log4j.appender.A5=org.apache.log4j.net.SMTPAppender
log4j.appender.A5.BufferSize=5
log4j.appender.A5.To=chunjie@yeqiangwei.com
log4j.appender.A5.From=error@yeqiangwei.com
log4j.appender.A5.Subject=ErrorLog
log4j.appender.A5.SMTPHost=smtp.263.net
log4j.appender.A5.layout=org.apache.log4j.PatternLayout
log4j.appender.A5.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
3.调用代码：
//把日志发送到mail
Logger logger3 = Logger.getLogger("MailLog");
logger3.warn("warn!!!");
logger3.error("error!!!");
logger3.fatal("fatal!!!");
在后台输出所有类别的错误：
1. 写配置文件
# 在后台输出
log4j.logger.console=DEBUG, A1
# APPENDER A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
2．调用代码
Logger logger1 = Logger.getLogger("console");
logger1.debug("debug!!!");
logger1.info("info!!!");
logger1.warn("warn!!!");
logger1.error("error!!!");
logger1.fatal("fatal!!!");
--------------------------------------------------------------------
全部配置文件：log4j.properties
# 在后台输出
log4j.logger.console=DEBUG, A1
# APPENDER A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
# 在2000系统日志输出
log4j.logger.NTlog=FATAL, A8
# APPENDER A8
log4j.appender.A8=org.apache.log4j.nt.NTEventLogAppender
log4j.appender.A8.Source=JavaTest
log4j.appender.A8.layout=org.apache.log4j.PatternLayout
log4j.appender.A8.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
# 将日志发送到email
log4j.logger.MailLog=WARN,A5
# APPENDER A5
log4j.appender.A5=org.apache.log4j.net.SMTPAppender
log4j.appender.A5.BufferSize=5
log4j.appender.A5.To=abc@abc.com
log4j.appender.A5.From= abc@ abc.com
log4j.appender.A5.Subject=ErrorLog
log4j.appender.A5.SMTPHost=smtpapp1
log4j.appender.A5.layout=org.apache.log4j.PatternLayout
log4j.appender.A5.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
全部代码：Log4jTest.java

/*
* 创建日期 2003-11-13
*/
package edu.bcu.Bean;
import org.apache.log4j.*;
//import org.apache.log4j.nt.*;
//import org.apache.log4j.net.*;
/**
* @author yanxu
*/
public class Log4jTest
{
public static void main(String args[])
{
   PropertyConfigurator.configure("log4j.properties");
   //在后台输出
   Logger logger1 = Logger.getLogger("console");
   logger1.debug("debug!!!");
   logger1.info("info!!!");
   logger1.warn("warn!!!");
   logger1.error("error!!!");
   logger1.fatal("fatal!!!");
//在NT系统日志输出
   Logger logger2 = Logger.getLogger("NTlog");
   //NTEventLogAppender nla = new NTEventLogAppender();
   logger2.debug("debug!!!");
   logger2.info("info!!!");
   logger2.warn("warn!!!");
   logger2.error("error!!!");
   //只有这个错误才会写入2000日志
   logger2.fatal("fatal!!!");
//把日志发送到mail
   Logger logger3 = Logger.getLogger("MailLog");
   //SMTPAppender sa = new SMTPAppender();
   logger3.warn("warn!!!");
   logger3.error("error!!!");
   logger3.fatal("fatal!!!");
}
}

Tibco Products Installation Sequences

2009-11-04T14:02:00.001+08:00

Tibco Products Installation Sequences

In this post, we only talk about the tibco products of EMS, Administrator, Running Agent, BusinessWorks, BusinessEvents. Here are the sequence to install the products,

1. install TIBCO EMS. EMS is a messaging system to produce/consume message to/from queues/topics.

2. install Tibco Running Agent. It incluses Tibco Rendezvous, Tibco Hawk (Tibco monitor tool), Tibco Designer (BE, BW development tool)

3. install Tibco Administrator which is the running env for BE, BW or others.

4. install Tibco BusinessWorks which can integrate with many products besides tibco product itself and run as process.

5. install Tibco BusinessEvents which is another tool to handle event/concept/scroecard with rules.

TIBCO EMS: Destination Features

2009-10-14T10:10:00.001+08:00

TIBCO EMS: Destination Features

You can set a secure mode for access control at the queue or topic level

You can set threshold limits for the amount of memory used by the EMS

You can route messages sent to destinations to other servers

You can also create bridges between destinations of the same or different types to create a hybrid messaging model for your application

You can control the flow of messages to a destination

You can exchange messages with other message services.Queues can receive TIBCO Rendezvous and TIBCO SmartSockets messages. Topics can either receive or send Rendezvous and TIBCO SmartSockets messages

You can set queues to be exclusive or non-exclusive. Only one receiver can receive messages from an exclusive queue

You can specify a redelivery policy for queues. When messages must be redelivered, you can specify a property on the queue that determines the maximum number of times a message should be redelivered

You can trace and log all messages passing through a destination

You can include the user name of the message producer in the message with sender_name and sender_name_endorced

Administrator operations can use wildcards in destination names

You can set the failsafe mode on a topic or queue to direct the server to write persistent messages to disk synchronously to guarantee messages are not lost under any circumstances.

You can specify that a consumer is to receive batches of messages in the background to improve performance

EMS: Setup Fault Tolerance

2009-10-12T16:20:00.001+08:00

EMS: Setup Fault Tolerance

Here is the summary to setup fault tolerance servers, tcp://ems1:7222 and tcp://ems2:7222 for example,

In server ems1,ems2, change the property server to same values EMS-SERVER for example.

b. In server ems1, change ft_active to tcp://ems2:7222. In server ems2, change ft_active to tcp://ems1:7222.

c. In both servers, set properties ft_heartbeat, ft_actiation, ft_reconnect_timeout in file tibemsd.conf. The values can be different in bot servers.

d. Make sure both servers use the shared configuration files (users.conf, groups.conf and others) except tibemsd.conf and shared state files(meta.db, async-msgs.db,sync-msgs.db). tibemsd.conf should have 2 copies seperately in both servers. In server ems1, setup 2 folders for configuration and shared state files. Copy all configuration files to the configuration folder named Con for example. Copy all shared state files to another one named DataStore for example.

e. In server ems1, ems2, map above folders to a same driver, like Z: for example.

f. In server ems1,ems2, set properties users, groups, topics, queues, acl_list, factories, routs, bridges, transports, tibrvcm, durables like below to let the server know where to get those configuration files.

users = Z:/Con/Configureusers.conf

groups = Z:/Con/groups.conf

g. In server ems1, ems2, set properties store value like below

store=Z:/DataStore

Note that above property only specify the folder path

h. In servers ems1,ems2, set the property store_minimum_sync, store_minimum_async to the same value

i. If authorized property is set enabled, create a TIBCO EMS id/password pairs. The id should be same as the server property value. In this example, create id named EMS-SERVER. And set the password property accordingly in servers ems1, ems2.

j. Restart TIBCO EMS service in both servers to validate the settings.

All properties above can be founder in tibemsd.conf file.

祖国生日快乐

2009-10-01T14:47:00.001+08:00

祖国生日快乐

祝愿我们伟大祖国繁荣昌盛!!!

祝愿我们伟大的民族长盛不衰!!!

EMS: Steps to Send/Receive Message

2009-09-29T14:28:00.001+08:00

EMS: Steps to Send/Receive Message

Here are the steps to send/receive message from client side, (java code)

Create a connection factory.

ConnectonFactory f = new com.tibco.tibjms.TibjmsConnectionFactory(String serverURL);

Create a connection

Connection c = f.createConnection(String username, String password);

If the server property authorization is disabled, you do not need to specify the username and password.

Create a session

Session s=c.createSession(Boolean transcationFlag, Int delivery_mode);

Get destination

Javax.jms.Queue d=s.CreateQueue(String queueName);

Javax.jms.Topic d=s.CreateTopic(String topicName);

Once the Queue/Topic exists, then return the destination object.

Create message producer to send message, or

MessageProducer p=s.createProducer(Destination d);

Create a Message object, TextMessage object for example,

TextMessage tm = s.createTextMessage();

You can set property for the message and the text body.

tm.setText(String textBody);

tm.setStringProperty(String propertyName, String propertyValue);

p.send(tm);

Create message consumer to receive message

MessageConsumer p=s.createConsumer(Destination d, String selector);

For synchronously receiver,

p.receive();

For asynchronously receiver, you need to implement MessageListener class and restruture the onMessage function.

Class myMessageListener implements MessageListener

{

Public void onMessage(Message message)

{

// add code here to handle if message is sent to queue/topic

System.out.println(“The imcoming message is: “+message);

}

In the main class, set consumer listener

p.setMessageListener(new myMessageListener);

Note that, for the MessageConsumer class, you need to start the connection before receive message from Queue/Topic

start();

Note: another way to get the ConnectionFactory/Queue/Topic object JNDI interface.

TIBCO EMS: Access Control

2009-09-25T14:05:00.001+08:00

TIBCO EMS: Access Control

EMS Permissions

administrator permission

The permission defines the right for users/groups to create, modify, delete, and view users, destinations, routes, factories and others.

Notes: users in admin group have all administrator permissions regardless of the permission settings.

You can not grant revoke administrator permissions from any users in admin group.

Users with change-admin-acl and view-user/group permission can grant or revoke permissions to other users but can only grant or revoke permissions that have been granted.

Users in groups inherit the administrator permission.

destination-based administrator permission

The permission defines the right for users/group to create, modify, delete, purge, view destinations.

Notes: any destination-lever permission granted to a user or group for a wildcard destination is inherited for all child destinations.

user permission

The permission defines the right for users/group to send, receive to/from queue or publish, subscribe to/from topic. Besides, it defines the right to create durable subscriptions to topics.

Server/Destination Connection Settings

Once the authorization is disabled (default setting), the server grants any connection request and doest not check permissions when a client connects to a destination.

Note: users must always log in with the correct administration username and password to perform any administrative function.

Once the authorization is enabled, the server grants connections only from authorized users. The server will check the destination permission if the destination has secure property.

Note: secure is a destination-based property. The server will not check the destination permission even if the destination permissions have defined but the secure property does not set.

TIBCO EMS: Ways to Persistent Message

2009-09-18T16:49:00.001+08:00

TIBCO EMS: PERSISTENT MESSAGE

Persistent messages sent to Queues

Note: server always persistent the message to disk

Persistent messages published to Topics

Note: only persistent the message if the subscribe is one of Durable Consumer or Fault Tolerant Consumer.

Persistent Messages and Failsafe Destinations

Note: once the failsafe in queue or topic are set, the producer or publisher will wait until server persistent the message to disk. Else the server return control to producer or publisher before complete the persistent operations.

TIBCO EMS: Message Delivery Modes

2009-09-18T16:35:00.001+08:00

TIBCO EMS: Message Delivery Modes

There are 3 types delivery mode in the message which is put into JMSDeliveryMode message header field.

PERSISTENT

Note:Server sends confirmation message to producer. The message is persisted on disk by the server.

NON_PERSISTENT

Notes: It depends on authorization and npsend_check_mode (defins in file tibemsd.conf) settings to send confirmation message to producer.

RELIABLE_DELIVERY

Note: a extended delivery mode by TIBCO itself. It has the benefit feature of PERSISTET and not its performance issue.

Hello to solve the error -1072896636 when load xml file

2009-09-06T23:03:00.001+08:00

I have a xml file which defines a internal DTD to validate its contend and make sure the format is valid.

But when I used xmlms 6.0 XML DOM object to load the xml file, the property parseError of the dom object says that there is a parse error. The error code is -1072896636 and its error message is DTD is prohibited.

The reason is that later than xmlms 6.0 one property named prohibitDTD's default value is changed to true by default while it was false in previous versions. So before load any xml file with internal DTD, you should remember to set the property to false before proceed to load the xml file.

Set xmlDoc = CreateObject("Msxml2.DOMDocument.6.0")

xmlDoc.setProperty "ProhibitDTD",False

xmlDoc.load xmltoload.xml

..........

Base ClearCase and ClearQuest Integration

2009-03-17T14:49:00.002+08:00

Base ClearCase and ClearQuest Integration

There are 2 ways to use ClearCase, UCM and Base ClearCase. Both usage patterns can integrate with ClearQuest. In this post, the mainly integration steps between Base ClearCase and ClearQuest will be covered. Below are the steps to enable the CQ and CC integration from scratch,

a. In ClearCase side, Create a ClearCase VOB and mount it.

b. Create views , edit the config spec if need to view and upload source codes.

c. In ClearQuest, setup schema repository and create one production user database.

d. In the CQ designer, apply ClearCase 1.0 package and enable the package to the CQ record type. The package can be applied to any state entity and all those entities can be used to associate with ClearCase versions.

e. Check in the schema and upgrade the user database.

f. Start configuring the integration. In the Base CC and CQ integration, ClearQuest Integration Configuration tool is used to configure the integration settings instead of ClearCase Project Explorer which is used for the UCM CC and CQ integration. Here are the main steps to setup the settings.

Open ClearQuest Integration Configuration tool
Specify the VOB which need to enable the integration
Specify Checkout Policy. (Table 1)
Specify Checkin Policy. (Table 2)
Specify Type Restrictions. (Table 3)
Specify Element Type Restrictions. (Table 4)
Specify Trigger Selection for different platform. (Table 5)
Specify ClearQuest Record Type. Only one record type can be specified here.If the trigger type is V2-Perl, multiple record types which have applied CQ package “ClearCase 1.0” can be used for the integration but need to specify those record types in configure.pl.

g. Edit config.pl to specify the CQ connection and User DB. (Table 6)

The configuration file contains parameters that define local policy choices and how to access Rational ClearQuest user database. The configuration file is located under

ccase-home-dir\lib\CQCC\config.pl.

Define the Rational ClearQuest user database and database set

CQCC_DATABASE_SET- to define the db set value

CQCC_DATABASE_ENTITY_LIST- to define the record types to associate with the CC changes.

For example,

&SetConfigParm("CQCC_DATABASE_SET", "CQCONNECTION");

&SetConfigParm("CQCC_DATABASE_ENTITY_LIST ", "DBNAME: entity1,entity2");

Customize CQSchema object

It accomplishes the following tasks:

Defines a new CQSchema and provides a set of similar record types and properties.(DefineCQSchema)

$s = &DefineCQSchema(NAME=>"MainSchema",

ENTITY_LIST => "entity1,entity2",

RESTRICTIONS => "STANDARD");

Relates the field names of the defect record type to those used by the record types that you specify. (ChangeFieldMap). If multiple record types are used, the field names in the mapping must be present in all record types.

$s->ChangeFieldMap(OWNER => "Owner",

STATE => "State",

ID => "id", #Note: ID shouldn't need to change

HEADLINE => "Headline",

RATL_MASTERSHIP => "ratl_mastership",

# Other mappable names

QUERY_STATES => "Submitted,Assigned,Opened",

MODIFY => "modify"

);

Defines one or more queries(SetQuery) that are used by the trigger to provide the Query option that the developers see and specifies the final RESTRICTIONS check that is made before associations are made.

$s->SetQuery("STANDARD",

"<OWNER> eq <*USER*>",

"<STATE> in <QUERY_STATES>");

Defines the query output format

$s->SetResultSet("STANDARD",

"<ID>,<STATE>,<HEADLINE>",

"%s %-9.9s %1.1s %1.1s %-45.45s");

Below changes in the config.pl can minim meet the requisite to run the Base CC and CQ integration. For the detailed specification of config.pl, you should read

http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?rcss=isacc&topic=/com.ibm.rational.clearcase.int.doc/topics/cc_cq_int/default_topic.htm

h. use cqcc_launch -test to check the configuration

Table 1. Checkout Policy

Policy Settings	Comments
Never prompt the user for change requests	No need to associate CQ record when do check out action.
Prompt the user for optional change requests	Prompt the user to specify the CQ record to associate with the changes optional. Optional here means when system prompts the user to specify the CQ record, user can assign a CQ record to associate or not.

Table 2. Checkin Policy

Policy Settings	Comments
Never prompt the user for change requests	No need to prompt user to specify the CQ record when user does check in action. If there is a CQ record has associate with the checked-out file, the change set will log into the CQ record after check in
Prompt user for optional change requests	Prompt user to specify the CQ record to associate with the changes optional. If no CQ record specified, the function works as the setting “Never prompt the user for change requests” If CQ record specified, log the changeset in this CQ record no matter the CQ record is same as the check-out one or not.
Prompt user and require one or more change request	Prompt the user to specify the CQ record to associate with the changes. Once the option is set, one or more CQ record must be associate with the changes. If multiple CQ records selected, log the changeset in each of the CQ record

Table 3. Branch Type Restrictions

Policy Settings	Comments
Policies apply to branches of all types	Apply the check out/in policies to all branch types.
Policies apply to branches of selected types	Apply the check out/in policies only to the selected branch types.

List 4. Element Type Restrictions

Policy Settings	Comments
Policies apply to branches of all types	Apply the check out/in policies to all element types.
Policies apply to branches of selected types	Apply the check out/in policies only to the selected element types.

Table 5. Trigger Selection

Policy Settings	Comments
V1-VisualBasic	Can be used only in Windows platform
V1-Perl	Can be used both in Windows and Unit/Linux platform
V2-Perl	The new version of V1-Perl. If V2-Perl is set, you have the following options. Use a local configuration file and local trigger scripts Use a shared, centrally located configuration file and local copies of trigger scripts Use a shared, centrally located configuration file and shared trigger scripts. (set the option “Use the trigger scripts in Path directory” and place the cqcc_launch.bat/pl in the same directory of config.pl

Table 6. Variables in confige.pl

Configuration parameter	Description
CQCC_ASSOC_BATCH_CONFIRM	Displays a window that confirms that the batch completed successfully.
CQCC_ASSOC_BATCH_ENABLE	Allows delay in processing multiple Rational ClearQuest association transactions until end of single Rational ClearCase operation or user-defined batch
CQCC_ASSOC_BATCH_SERIES	Specifies that a user-defined series is active and normal Rational ClearCase series-end processing should be suppressed
CQCC_AUTO_ASSOCIATE	Sets one or more change requests for automatic association on checkout and checkin without user interaction
CQCC_AUTO_ASSOCIATE_ENABLE	Specifies whether developers can use CQCC_AUTO_ASSOCIATE
CQCC_COMMENT_PATTERN	Sets pattern by which developers can make associations in a checkout or checkin comment
CQCC_CQWEB_ONLY	Forces use of Rational ClearQuest Web interface
CQCC_CQWEB_VERSION	Specify either 2.0 (Java™) or "1.0" (ASP with IIS) as Rational ClearQuest Web server protocol
CQCC_DATABASE_ENTITY_LIST	Defines logical name of database and related record types (entities) that support associations.
CQCC_DATABASE_SET	Database set name (connection) for one of multiple schema repositories; used with CQCC_DATABASE_ENTITY_LIST
CQCC_DEBUG	Controls level of output generated for problem diagnosis; 0 (none), 1 (basic), 2 (verbose)
CQCC_GUI_ENABLE	Allows use of Perl/TK graphic user interface
CQCC_LOG_OUTPUT	Records to a log file messages for problem diagnosis
CQCC_MULTIPLE_ASSOCS	Allows or prevents multiple defects to be associated with change
CQCC_MULTISITE	Enables Rational ClearCase MultiSite support
CQCC_POSTCHECKIN_COMMIT	Allows commitment of associations in Rational ClearQuest user database to be delayed until checkin completes in Rational ClearCase VOB
CQCC_QUERY_ENABLE	Allows developer-selected queries for making associations
CQCC_QUERY_FILTER	Controls which queries are presented to developers for associations
CQCC_RESTRICTIONS_TIMEOUT	Specifies number of seconds that a restrictions check can be reused during batch processing
CQCC_SERVER	Name of Rational ClearQuest Web server
CQCC_SERVERROOT	Name of folder in which Rational ClearQuest Web server is located
CQCC_SERVER_SSL	Enables secure communications for the Rational ClearQuest Web connection.
CQCC_TIMER	Allows recording of internal timing data
CQCC_WEB_DATABASE_SET	CQCC_DATABASE_SET for Web server
CQCC_REPLICA_NAME	For Rational ClearQuest Web client to specify user database replica name

The Main Difference between UCM/Base ClearCase and ClearQuest Integration

2009-03-17T14:49:00.001+08:00

The Main Difference between UCM/Base ClearCase and ClearQuest Integration

In Base CC and CQ integration, it is in VOB lever. In UCM CC and CQ integration, it is UCM Project Lever.

In Base CC and CQ integration, the configuration is more flexible. Once the VOB has enabled CQ and CC integration, it also can configure the check-out/in policies and can specify which branch type or element type use the policies settings. In UCM CC and CQ integration, all changes in that UCM project must associate with CQ items. In other words, Base CC and CQ integration, it is a loose integration while it is more close in UCM CC and CQ integration.

In Base CC and CQ integration, one change/version can associate multiple CQ records but it does not in UCM CC and CQ integration.

In Base CC and CQ integration, same CQ record can use in different branches while in UCM CC and CQ integration, same CQ record can only work on one stream.

In Base CC and CQ integration, it can use the web interface to do integration without any CQ client installed while in UCM CC and CQ integration, it is a must to install the CQ client.

To use which type of integration mainly depends on the model you use the CC. In most cases, UCM is more easy/standard process to use compared with Base ClearCase. In UCM model, user do not need to know more details about the CC working mechanism itself like, config spec, branch, element type and others but only need to know the relationship between view,stream,integration stream and know when to deliver, merge, rebase.

Usage of Config Spec

2009-03-09T17:18:00.001+08:00

Usage of Config Spec

Config Spec is used to select file versions based on the rules defined in that configuration. It is a must to know if base ClearCase pattern is used. Below is the detailed usage of Config Spec.

https://publib.boulder.ibm.com/infocenter/cchelp/v7r1m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_proj.doc/c_bcfg_hwcfgwrk.htm