如何从数据库层面直接读取Remedy ARS系统中的业务数据？首先你需要在Remedy User中查询和确认你需要读取的form的名称，之后在用Remedy develop studio中确认你需要读取字段在数据库中的database ID，然后使用SQLPLUS 查询出form的数据库视图名称，最后编写一条sqlplus语句验证查询的结果。确认了表和字段在数据库中的ID之后，你就可以使用任何数据库客户端直接绕过Remedy应用系统来读取业务数据了。这样做比API的调用开发难度要小些。

下面是一个例子：用Remedy默认的用户名密码登录，查询BMC.CORE:BMC_ComputerSystem form在数据库中视图的名称为T517，在BMC Remedy Developer Studio中查询字段的ID（点击查看大图）在此视图中查询CI名称里含有test-fc关键字的CI，并返回所有CI的name, inc id 和TotalPhysicMemory属性值。

[oracle@ars ~]$ sqlplus ARAdmin/AR#Admin#@remedy
SQL*Plus: Release 11.2.0.1.0 Production on Wed Jun 29 21:51:39 2011
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.2.0.1.0 – 64bit Production

SQL>
SQL> select schemaid from arschema where name='BMC.CORE:BMC_ComputerSystem';
  SCHEMAID
----------
       517
SQL>
SQL> desc T517;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 C1                                                 VARCHAR2(31)
 C2                                                 VARCHAR2(254)
 C3                                        NOT NULL NUMBER(15)
 C4                                                 VARCHAR2(254)
 C5                                        NOT NULL VARCHAR2(254)
 C6                                        NOT NULL NUMBER(15)
 C7                                        NOT NULL NUMBER(15)
 C8                                        NOT NULL VARCHAR2(254)
 C112                                               VARCHAR2(255)
 C179                                               VARCHAR2(38)
 C60513                                             VARCHAR2(255)
 C200000001                                         VARCHAR2(254)
 C200000003                                         VARCHAR2(60)
 C200000004                                         VARCHAR2(60)
 C200000005                                         VARCHAR2(60)
 C200000020                                         VARCHAR2(254)
 C200000021                                         NUMBER(28)
 C200000022                                         NUMBER(28)
 C200000023                                         VARCHAR2(30)
 C200000025                                         VARCHAR2(254)
 C200000026                                         VARCHAR2(254)
 C200000028                                         VARCHAR2(254)
 C200000029                                         VARCHAR2(254)
 C200000032                                         VARCHAR2(60)
 C200000033                                         VARCHAR2(30)
 C200000034                                         VARCHAR2(30)
 C200000035                                         VARCHAR2(30)
 C200003000                                         CLOB
 C240000007                                         VARCHAR2(254)
 C240000008                                         CLOB
 C240001002                                         VARCHAR2(254)
 C240001003                                         VARCHAR2(254)
 C240001005                                         VARCHAR2(254)
 C260100002                                         NUMBER(15)
 C260140117                                         VARCHAR2(254)
 C260400001                                         NUMBER(28)
 C260400002                                         NUMBER(28)
 C300927600                                         NUMBER(15)
 C301002800                                         VARCHAR2(254)
 C301002900                                         VARCHAR2(254)
 C301003400                                         VARCHAR2(255)
 C301016000                                         VARCHAR2(254)
 C301016100                                         CLOB
 C301016200                                         NUMBER(15)
 C301016700                                         NUMBER(15)
 C301016800                                         NUMBER(15)
 C301016900                                         NUMBER(15)
 C301017000                                         NUMBER(15)
 C301017100                                         NUMBER(15)
 C301017200                                         NUMBER(28)
 C301017300                                         NUMBER(28)
 C301019500                                         NUMBER(15)
 C301019600                                         VARCHAR2(254)
 C301019800                                         VARCHAR2(254)
 C301019900                                         VARCHAR2(30)
 C301089100                                         VARCHAR2(80)
 C301118000                                         NUMBER(15)
 C301172600                                         NUMBER(15)
 C301182000                                         NUMBER(15)
 C301186800                                         VARCHAR2(254)
 C400079600                                         VARCHAR2(38)
 C400124500                                         NUMBER(15)
 C400127400                                         VARCHAR2(127)
 C400129100                                         NUMBER(15)
 C400129200                                         VARCHAR2(38)
 C400131200                                         VARCHAR2(255)
 C400131300                                         VARCHAR2(255)
 C490001289                                         VARCHAR2(127)
 C530010100                                         VARCHAR2(254)
 C530010200                                         VARCHAR2(254)
 C530010600                                         NUMBER(15)
 C530014300                                         NUMBER(15)
 C530014400                                         NUMBER(15)
 C530014500                                         NUMBER(15)
 C530019500                                         CLOB
 C530031600                                         NUMBER(15)
 C530032500                                         NUMBER(15)
 C530034500                                         VARCHAR2(255)
 C530035200                                         VARCHAR2(255)
 C530041601                                         NUMBER(15)
 C530043901                                         VARCHAR2(255)
 C530054200                                         NUMBER(15)
 C530058400                                         VARCHAR2(254)
 C530058500                                         VARCHAR2(254)
 C530059800                                         VARCHAR2(255)
 C530060100                                         NUMBER(15)
 C530060200                                         VARCHAR2(255)
 C530060300                                         NUMBER(15)
 C530062400                                         VARCHAR2(254)
 C530067430                                         NUMBER(15)
 C530067920                                         NUMBER(15)
 C530067930                                         VARCHAR2(127)
 E0                                        NOT NULL VARCHAR2(15)
 E1                                        NOT NULL VARCHAR2(15)

SQL>
SQL>  select C200000020,C179,C200000022 from T517 where  C200000020 like 'test-fc%';
C200000020
--------------------------------------------------------------------------------
C179                                   C200000022
-------------------------------------- ----------
test-fc-2.testlab.bigcorp.com
OI-48A6276C70E411E0A984000C29455AB9           448

test-fc-5.testlab.bigcorp.com
OI-4CCD50C270E411E0AA53000C29455AB9           320

test-fc-4.testlab.bigcorp.com
OI-4D1B433670E411E0AA57000C29455AB9           160

C200000020
--------------------------------------------------------------------------------
C179                                   C200000022
-------------------------------------- ----------
test-fc-6.testlab.bigcorp.com
OI-4E9E37C270E411E0AA69000C29455AB9           256
SQL>

鸣谢 炮灰向钱冲和我对以上技术细节的讨论。

Related posts:

1. How to deploy mid-tier to tomcat 7
2. BMC Atrium CMDB 类定义迁移

用tideway用户登录ADDM服务器，运行下面的命令

[tideway@localhost .ssh]$ ls
[tideway@localhost .ssh]$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/usr/tideway/.ssh/id_rsa):  “敲回车”
Enter passphrase (empty for no passphrase):  “敲回车”
Enter same passphrase again:  “敲回车”
Your identification has been saved in /usr/tideway/.ssh/id_rsa.
Your public key has been saved in /usr/tideway/.ssh/id_rsa.pub.
The key fingerprint is:
27:20:55:fc:f9:9a:41:35:11:ef:6d:b7:6c:4e:78:00 tideway@localhost.localdomain
[tideway@localhost .ssh]$ ls
id_rsa  id_rsa.pub
[tideway@localhost .ssh]$

下载和安装key文件部署工具

http://code.google.com/p/keploy/downloads/list

下载 keploy-0.5.tgz
上传到ADDM服务器的/usr/tideway/.ssh目录中

[tideway@localhost .ssh]$ ls
id_rsa  id_rsa.pub  keploy-0.5.tgz
[tideway@localhost .ssh]$ tar zxvf keploy-0.5.tgz
keploy-0.5/
keploy-0.5/keploy
keploy-0.5/LICENSE
keploy-0.5/README
keploy-0.5/INSTALL
keploy-0.5/CHANGELOG
[tideway@localhost .ssh]$ ls
id_rsa  id_rsa.pub  keploy-0.5  keploy-0.5.tgz
[tideway@localhost .ssh]$ cd keploy-0.5
[tideway@localhost keploy-0.5]$ ls
CHANGELOG  INSTALL  keploy  LICENSE  README
[tideway@localhost keploy-0.5]$ ./keploy -v

NOTICE: You may be prompted for you password,
NOTICE: this is directly from the ssh client, not keploy

Preparing to deploy ssh key...
ERROR: No targets defined.
[tideway@localhost keploy-0.5]$ ./keploy -h
Usage: keploy [options] [hosts]

Options:
  -i ID_FILE            specifies identity file
  -l USERID, --login=USERID
                        define userid for remote connections
  -f TARGET_FILE, --file=TARGET_FILE
                        read list of targets from file
  -k, --use-known       read list of targets from known_hosts files
  -r, --remove          remove primary identity from remote(s)
  -c OLD_ID_FILE, --change=OLD_ID_FILE
                        replace old identity with new one on remote(s)
  -A                    enable/disable agent forwarding on remote
  -v                    give verbose output
  -q, --quiet           quiet the output
  --version             show program's version number and exit
  -h, --help            show this help message and exit
[tideway@localhost keploy-0.5]$

在keploy-0.5生成一个文件hostlist，里面每一行放一台机器的IP，回头让工具自动读取该文件

Linux被采集帐号准备

建议直接把ADDM采集机的key文件部署到root用户上，如果用户觉得这个做法不安全的话，我们可以建立一个不普通用户，把特权命令用sudo处理一下，下面是具体的做法

运行ssh的证书认证

用root登录被采集机，修改/etc/ssh/sshd_config文件，将如下参数的注释符号（#）去掉，以启用这些参数：
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
重启sshd服务
#/etc/init.d/sshd restart

配置sudo

Linux平台对采集账户需要配置sudo。以root用户登录被管服务器，修改/etc/sudoers文件，在文件末尾追加一行：
tideway ALL=(root) NOPASSWD:/usr/sbin/dmidecode,/usr/sbin/hwinfo, /usr/sbin/hbanyware/hbacmd,/usr/sbin/lsof,/sbin/ethtool,/sbin/mii-tool

增加采集帐号tideway

操作步骤如下（以root用户登录服务器）：
[root@ars home]# useradd tideway
[root@ars home]# passwd tideway
Changing password for user tideway.
New UNIX password: “使用tideway做密码，采集成功后可以修改掉”
BAD PASSWORD: it is based on a dictionary word
Retype new UNIX password: “使用tideway做密码，采集成功后可以修改掉”
passwd: all authentication tokens updated successfully.
[root@ars home]#

部署ADDM ssh 密钥到被采集机

部署

在采集机部署前，查看/home/tideway 目录

[root@ars home]# cd tideway/
[root@ars tideway]# pwd
/home/tideway
[root@ars tideway]# ls -la
total 36
drwx------ 3 tideway tideway 4096 Jun 17 00:55 .
drwxr-xr-x 4 root    root    4096 Jun 17 00:55 ..
-rw-r--r-- 1 tideway tideway   33 Jun 17 00:55 .bash_logout
-rw-r--r-- 1 tideway tideway  176 Jun 17 00:55 .bash_profile
-rw-r--r-- 1 tideway tideway  124 Jun 17 00:55 .bashrc
-rw-r--r-- 1 tideway tideway  515 Jun 17 00:55 .emacs
drwxr-xr-x 4 tideway tideway 4096 Jun 17 00:55 .mozilla
-rw-r--r-- 1 tideway tideway  658 Jun 17 00:55 .zshrc
[root@ars tideway]#

注意这里没有.ssh目录
开始使用我们下载的工具部署，登录到ADDM采集机上

[tideway@localhost keploy-0.5]$ vi hostlist
[tideway@localhost keploy-0.5]$ cat hostlist
192.168.189.154
[tideway@localhost keploy-0.5]$ ./keploy -f hostlist

NOTICE: You may be prompted for you password,
NOTICE: this is directly from the ssh client, not keploy

Preparing to deploy ssh key...
Using user-defined host list from file: hostlist
./keploy:164: DeprecationWarning: os.popen3 is deprecated.  Use the subprocess module.
  si, so, se = os.popen3(execute)
        Found host(s):
                192.168.189.154
        Found identity:
                /usr/tideway/.ssh/id_rsa.pub
        Working on host: 192.168.189.154
The authenticity of host '192.168.189.154 (192.168.189.154)' can't be established.
RSA key fingerprint is de:4e:f0:c8:9b:86:ee:25:af:a9:1c:19:8f:20:90:ad.
Are you sure you want to continue connecting (yes/no)? yes
tideway@192.168.189.154's password:  "输入目标机上tideway用户的密码，我用的是tideway"
                Public Identity Key: deployed
[tideway@localhost keploy-0.5]$

可以到被采集机的/home/tideway/.ssh下面看看传过去的正式文件，这种方式极大的避免了，手工创建.ssh目录，设置它和key文件权限的工作量

验证

在采集机上，使用tideway用户登录被采集服务器。

[tideway@localhost keploy-0.5]$ ssh 192.168.189.154
Last login: Fri Jun 17 01:08:21 2011 from 192.168.189.147
[tideway@ars ~]$

Related posts:

1. openssh 5.2 Aix5.3 bug
2. BMC Atrium CMDB 类定义迁移
3. CMDB中存什么？

上图显示了Overloay对象的地位和功用，我们都是工作在BMC原厂的开箱即用的程序对象层面上，所有安装程序首次安装到系统上的应用的所有对象都是Base对象。在这个基础之上我们做定制和开发，定制和开发出来的对象有两种，一种是Overlay对象，中文翻译为叠加对象，这种叠加对象并不会对原有的Base对象进行修改，而是覆盖在其之上的，两者是和谐共存的。另外一种对象就是纯客户化的对象，即以前没有，开发人员新加入的对象，这种对象和其他两种对象是没有冲突的。

Overlay可以是Base对象保持原状有什么意义？最重要的一点就是对升级有好处，以前我们开发的所有Remedy应用系统，大家都不敢做升级，当客户或者BMC的support要求要升级的时候，我们都会抵制或反对，这里的原因相信大家心里都知道。那么以后大家就不必这样了，只要在开发定制的过程中合理的使用Overlay对象做定制开发，方能保证定制后的系统对补丁和升级来者不拒。

那么如何使用到Overlay对象呢？在Dev Studio中选中需要修改的对象，点右键选择create overlay，你就能在原厂的对象上做一个叠加对象了。这里提出一个7.6.04 Dev Studio的错误做法：默认登录到Dev Studio以后，你可能会发现在默认的最佳实践模式下，你不能向以前一样任意修改东西，发现在切换到另外一个模式（好像是经典模式）之后又什么都能修改了，所以你就认为找到了修改的方法，其实这种操作恰恰是绕过了Overlay功能。在这种模式等于在以前旧版本产品的模式下开发做。

老外如是说：What the overlay feature does is to simply allow you to do the following:

1) Add new items that are identified as custom items you have added.  They are flagged as custom items in the displays.  You can easily sort by and get a list of custom items.  And it is COMPLETE.  You don’t have to worry if you are missing one or if you forgot about something you added.
2) Update existing items by leaving the original definition there and updating a copy of that definition with your changes.
a) all the benefits of #1 are present AND your changes have the exact same name/identification as the original
b) you can at any time see your version vs. the original to see exactly what has changed from out of the box
c) Not have to deal with “ripple changes”.  By this I mean that if in the past you copied a filter to a new name (to avoid overwrite at upgrade), you had to copy any guide that included it and then any workflow that called the guide to use the new name.   The fact that the items are the SAME ITEM means that there is no need to change other things.
d) When an upgrade occurs, the definitions in the base layer are changed but NOTHING about the items you have overlaid (or added custom) are changed. So, your changes are not overwritten.  In fact, your changes continue to be the overlay and continue to sit on top of and override the definition that was newly imported with the same name/id.
e) After the upgrade, you can again compare your overlay with the new out of the box definition to see if there is anything that should change.  Maybe the out of the box does the right thing now and you should remove your overlay or maybe there is an extended set of actions and you need to pick up one or more of the new actions in your overlay.

The key is that it provides an automatic and inherent layer that is YOUR layer that sits over the out of the box definition and allows you to safely, clearly, and cleanly adjust or augment the defintions if needed for your environment.

This is a feature that allows you to gain further and tighter control over your environment.  It is something that provides you with the ability to better understand what is stock and what is custom and what is changed about the solution.  It is one that preserves all changes you have made across upgrades with a layer of independence and yet links so that changes stay tied into the solution without the change you have made being updated by the upgrade itself.

突然想讲这样的一个故事，如果曾经发生在你身上，就当是个笑话吧。Remedy ITSM套件就好比是一个精装别墅，BMC一般会告诉客户，那里面有世界上最豪华的设施和装修，直接拿着行李入住就行了，事实如此！不过客户往往没有先看进屋看个究竟（其实往往用户没有这个机会，因素复杂，我不说你懂得），就找来施工队，提出我是有这样那样生活习惯和品位的，这都是对此房子的期望和需求，我的上帝客户啊！东西你都买了为啥就不先试住一下呢？尝试新鲜事物的精神您有木有？接着施工队的工人（也就是我们的Remedy程序开发人员）被工头（项目经理）带着就进屋了，说我们就是专业干这个的，能保证按时上线，您就等好吧！客户在院子里站着，瞧着施工队拿着需求分析书和开发工具进进出出，在屋里叮叮当当紧着忙活，几个月之后，项目经理过来说，我们可以做上线培训了（或者试运行/或者UAT测试了），这下客户才真的走进屋，客户开始纳闷了，心里直嘀咕，这真的是别墅么？好像有点糙啊！项目经理说，我们正式按照您的指示，已经把它做成中式风格了，老美的东西怕您用不惯。就这样客户茫然的也就入住了，其实客户可能只也住在了别墅某一层的一间屋里。通往其它房间的门都被封了，并且贴上了壁纸，或者被新打的大衣柜给挡住了，每次回家都是从窗台爬梯子上去。

对任何项目而言，在原厂产品上的定制开发是必须的，但是往往是项目的无底洞，那么如何规避这种风险？怎样让Remedy ITSM产品开箱即用的功能发挥到最大化？无疑对产品已有能力的挖潜和利用也要花时间精力成本去研究，这个时间和开发定制的工作时间是冲突矛盾的。那么：让客户先试住，在逐步装修，可能才是平衡矛盾的关键。客户也应该把项目实施和开发的资金做一个规划，切勿在前期投入太大，项目的前期，应该是学习产品和适应最佳实践的过程。实施方应该想方设法的让客户先进屋看清楚，和客户一起住一段时间，之后在去开工装修，这个过程应该是项目美好的蜜月期。

Related posts:

1. BMC Atrium CMDB 类定义迁移
2. BMC Atrium CMDB CI数据迁移
3. 在Oracle上备份和恢复 Remedy ARS数据库

ARInside is a free open-source utility to create a static html documentation of your AR-Server. If you need something to quickly browse through your workflow, ARInside might be worth a try.
ARInside 3.0.2 has some new features, lots of bugfixes and other improvements.
Just to name a few:
- documentation improvements
- 64-bit platform support
- experimental support for Solaris and AIX
- basic ARS 7.6.x support
- huge performance plus on big installations

这是一个ARS服务器扫描的工具，可以形成一个静态的文档，能够作为一个状态的参考极限，这样方便你对当前的服务器上的所有对象和工作流有个全面的了解。最大的好处是能够统计和技术，而且不用登陆Dev Studio了。一图胜千言，下面大家看后就明白它能做什么。

看后还闲着干嘛，赶紧去下载使用吧。

其他的关于Remedy ARS 开源的项目我也在sf.net里面大致搜索了一下，下面是个简单的参考清单。

Remedy Outlook Integration Updated 2006-09-08

The Remedy Integration for Outlook (ROI) synchronizes tickets from any Remedy AR System application to your Outlook task list or calendar.

Remedy ARAPI PHP extension Updated 2009-07-19

Extension to PHP for integration to Remedy Action Request System. First release will be focused on reading and manipulating data. Later version will give access to arapi-application structure functions.

Jasper Reports data provider for Remedy Updated 2006-08-16

jaspars provides a Jasper Reports custom data source (JRDataSource) compatible with the Remedy AR System. See http://www.mypathworks.com/arslist/Public?id=8ae4b6940c259f32010c3707fbae01bf for more information and usage instructions.

ARSperl Updated 2008-05-06

ARSperl is an integration kit for Perl5 and Remedy ARSystem API. It provides a large subset of the functionality found in the ARS C API

AR Cache Purge Updated 2009-05-27

AR Cache Purge automates the process of clearing BMC Remedy user cache on client machines. It first checks the registry for the Home folders(s) and then removes the .arf and .arv files. It handles multiple users and home folders on a single machine.

pyARS Updated 2010-12-20

The pyARS python module allows developers to use BMC’s ARSystem (Remedy ARS) and Atrium CMDB functions from within Python. Using Python’s interactive shell, it is extremely easy to retrieve and modify data entries as well as workflow objects.

COM Objects for the AR System Updated 2006-01-10

Coarse (COM Objects for the AR System), provides an automation compatible COM API to the AR System (Remedy only provides a C API and a Java API). It is compatible with VB6, VBA, VBScript, and JScript. Based on the RTL Sourceforge project.

Related posts:

1. BMC课程通知: BMC Remedy AR 7.5 管理员培训
2. Remedy ITSM 7.6.04 套件快速安装
3. 在Oracle上备份和恢复 Remedy ARS数据库

众所周知Remedy ARS上运行的所有程序代码都是在数据库中存储的，几乎所有的程序代码和相关数据都是存储在后端的数据库里的。基于这种特性，我们可以很方便地从数据库层面实现对ARS系统的备份和恢复。所谓基于数据库的备份和恢复就是指数据库的全库导入和导出。在这方面Oracle做的很好，他所提供的imp和exp命令行工具能很好的完成此项任务。

When you may backup BMC Remedy ARS system Database

Remedy ARS系统数据库全备份可能会发生在下面的几个时间点：

1. 在安装过程中，Remedy ITSM套件的安装都是从ARS开始一个模块一个模块增加安装的，可以在安装每个新模块之前，做一个数据库备份，用于安装失败情况下的现场恢复

2. 在系统上线前，当系统需要做升级/代码更新等等大规模操作之前可以考虑做一次数据库的导出备份

3. 在做系统迁移的情况下，我们甚至可以生产库迁移到开发机上进行问题的重现，或者代码的修改，或者测试，完成之后再导回生产系统（如果生产系统再次期间处于维护状态的话）

How-to

下面是我总结的相关操作步骤参考。

备份ARSystem数据库

exp aradmin/ar#admin@itil file=c:\before-patch7.dmp log=c:\exp.log compress=n statistics=none

参数解释：
aradmin/ar#admin  是ARS系统默认的用户名和口令
@itil 是ARSystem数据库所在的数据库实例名
file=c:\before-patch7.dmp log=c:\exp.log  是导出的数据库文件和日志文件路径

删除ARAdmin用户数据

drop user aradmin cascade;

创建和授权ARAdmin用户

CREATE USER ARADMIN
IDENTIFIED BY ar#admin#
DEFAULT TABLESPACE ARSYSTEM
TEMPORARY TABLESPACE ARTMPSPC
PROFILE DEFAULT
ACCOUNT UNLOCK;

GRANT ARADMINROLE TO ARADMIN;
ALTER USER ARADMIN DEFAULT ROLE ALL;
ALTER USER ARADMIN QUOTA UNLIMITED ON ARSYSTEM;

导入备份的数据文件

imp ARAdmin/AR#Admin@ars file=c:\CMDB2010-12-13_13.dmp log=c:\imp.log  fromuser=ARAdmin touser=ARAdmin ignore=y

Credit to：以上操作步骤由神州太岳工程师李成旗协助编写和测试.

Related posts:

1. BMC课程通知: BMC Remedy AR 7.5 管理员培训
2. Remedy ARS 开源工具知多少
3. Remedy ITSM 7.6.04 套件快速安装

错误的现象是：在启动服务的时，安装程序一直停止在“Starting Remedy ARS services….”的屏幕，去arerror日志里面可以看到无法连接到SQL数据库的错误。

我的安装错误的原因其实很简单：

1. 如果是64为的Windows操作系统，默认的安装路径是C:\Program Files (x86)\目录
2. Oracle客户端没有正确的安装

解决的方法如下：

1. 修改ars默认的安装路径，尽量把它放在一个较短的而且没有特殊字符的路径里，如D:\bmc\
2. ARS 7.5 sp6支持的Oracle客户端是32位的，如果你在64位OS上安装的是64位的Oracle数据+客户端（sqlplus），那么默认的这个64为的客户端是不能用的，需要安装一个62位的客户端，而且需要时10g的，此版本也不支持11g的客户端；另外在安装32位的oracle客户端的时候最好也不要在路径中有特殊字符如符号和下划线之类的

ARS7.5本身是32位的可支持程序，所以它所需要的JDK和Oracle都需要是32位的版本。如果你安装的是7.6.04，就不需要考虑32位的问题，由于它本身就是64位的程序了，所以JDK和Oracle都需要使用相应的64为的程序。

Related posts:

1. ARS启动故障修复案例
2. 如何读取Remedy中的数据

CI数据导出示例

Command: xexpdt
XEXPORT DATA
Export instance data from all classes? (F):
Classes to export data from:
Class and its subclasses, From namespace (1,2) (1):
Namespace (): BMC.CORE
Class name (): BMC_ComputerSystem
Dataset ID (): BMC.ASSET
Filename for exported data: C:\DEMO\cs-ci
Exporting Class BMC_ComputerSystem
i=0: namespaceName = BMC.CORE, className = BMC_ComputerSystemExported without errorsExporting Class BMC_MainframeExporti
ng Class BMC_PrinterExporting Class BMC_StorageSubsystem
CMDBExportData  results
ReturnCode:  OK
Status List : 0 items

到相应目录下面找到导出的文件，导出的结果至少是两个文件一个是META_FILE其他的才是CI数据文件。

关系数据导出示例

Command: xexpdt
XEXPORT DATA
Export instance data from all classes? (F):
Classes to export data from:
Class and its subclasses, From namespace (1,2) (1):
Namespace (): BMC.CORE
Class name (): BMC_Dependency
Dataset ID (): BMC.ASSET
Filename for exported data: C:\DEMO\REL-DEP.XML
Exporting Class BMC_Dependency
i=0: namespaceName = BMC.CORE, className = BMC_DependencyExported without errorsExporting Class BMC_AccountOnSystemExpor
ting Class BMC_HostedAccessPointExporting Class BMC_HostedServiceExporting Class BMC_InventoryBulkItemsExporting Class B
MC_InventoryComputerSystemsExporting Class BMC_InventoryEquipmentExporting Class BMC_InventorySystemComponents
CMDBExportData  results
ReturnCode:  OK
Status List : 0 items

到相应目录下面找到导出的文件，导出的结果至少是两个文件一个是META_FILE其他的才是CI数据文件。

导入数据示例

Command: impdt
IMPORT INSTANCE DATA
Handle duplicate Instance Ids:
(Error/New ID for Dup/Merge/New ID for All) (1-4) (1): 3
Filename containing import data: c:\demo\cs-ci_0_0  (导入包含CI数据的文件)

CMDBImportData  results
ReturnCode:  OK
Status List : 0 items
Total items Processed             :  2
Items Imported successfully       :  2
Items for which Import failed     :  0

Command: impdt
IMPORT INSTANCE DATA
Handle duplicate Instance Ids:
(Error/New ID for Dup/Merge/New ID for All) (1-4) (1): 3
Filename containing import data: c:\demo\REL-DEP.XML_0_0 (导入包含关系数据的文件)

CMDBImportData  results
ReturnCode:  OK
Status List : 0 items
Total items Processed             :  1
Items Imported successfully       :  1
Items for which Import failed     :  0

导入完毕之后使用Remedy User到相应的表格中查找，确认导入的数据是否正确。

Related posts:

1. BMC Atrium CMDB 类定义迁移
2. Stop to build CMDB for your IT – CMS是怎样炼成的？
3. Remedy ARS 7.6.03 overlay

cmdbdriver.exe能支持的参数

Options:
-u<USER>
-a<AUTHORSTRING>
-p<PASSWORD>
-l<LOCALE>
-s<SERVER>
-x<INPUTFILE_FULLPATH>
-t<PORT_NUMBER>
-q<QUIET_MODE_NUMBER>

登录CMDBdriver 实例：   cmdbdriver -u Demo -p bmc@XXX -s atriumcmdb -t 9988

登录之后在运行另外用于初始化的两个命令 init 和log

Command: init
INITIALIZATION

CMDBInitialization  results
ReturnCode:  OK
Status List : 0 items

Command: log
Control record:
Authentication string () :
User name () : Demo
Password () : **********
Locale[.charSet] () :
TimeZone () :
Server () : atriumcmdb

导出类定义的方法实例
Command: xexpdf
XEXPORT DEFINITION
Export all classes? (F):
Classes to export:
Class and its subclasses, From namespace (1,2) (1):
Namespace (): BMC.CORE
Class name (): BMC_ComputerSystem
Export all attributes with classes? (T):
Filename for exported data: c:\demo\BMC_ComputerSystem.xml

CMDBXExportDef  results
ReturnCode:  OK
Status List : 0 items

使用文本编辑器查看c:\demo\BMC_ComputerSystem.xml的导出结果

导入类定义的方法：
Command: impdf
DEFINITION IMPORT
Import Item List:
Number of import items (0):
Import option : Create/Overwrite (1-2) (1): 2
Filename containing import data: c:\demo\cs.xml

CMDBImportDef  results
ReturnCode:  OK
Status List : 0 items

使用Remedy User，用Demo登录，把语言切换到英文，然后在查BMC_ComputerSystem表达，在custom 2 ～n的tab页面里面查看哪些导入的属性。或者使用class manager查看确认导入是否成功。

Related posts:

1. BMC Atrium CMDB CI数据迁移
2. Remedy ARS 7.6.03 overlay
3. Stop to build CMDB for your IT – CMS是怎样炼成的？

For as long as there have been computers, operating systems and business critical applications, there has been monitoring of these items to make sure they were working (available) and performing well for their constituents. In the early days of the computer industry (through about 1982) computer systems were vertical monoliths where a customer would buy “an accounting system” and that purchase would include hardware, systems software, and applications software. All of this usually came from one vendor so there was one throat to choke when it did not work.

Starting with the delivery of the PC, then Ethernet LAN’s and Novel Netware, and finally Windows Servers and the Internet, the industry reorganized along horizontal dimensions. A computer system was now a multi-layer cake and you could buy each cake from one of many vendors whose products were largely interchangeable with each other, and compatible with adjacent layers. So you could buy an Intel based server from one of N vendors, put either Linux or Windows on it, but a Java applications server from one of N vendors on that and then buy applications from thousands of different vendors.

This horizontal layering of the industry was heavily promoted by Microsoft and Intel (who “owned” two key layers of the cake), and also ushered in the tremendous innovation and price competition that continues to drive our industry today. Moore’s Law says that microprocessor performance doubles roughly every 18 months or so, and with those increases in price/performance come the more for less mentality that we have all become accustomed to.

With this freedom of choice at every layer of the cake however came problems. The first problem was complexity. There were now too many cooks in the kitchen which meant that there were both too many and not one single throat for the CIO to choke when something went wrong. The management software industry reacted to this by inventing a marketecture, Business Service Management (BSM). The idea behind BSM was to identify the key business services that applications or combinations of applications delivered to users (the ability to enter and order and ship the resulting product is a business service as is the ability of a consumer to transfer funds from one banking account to another), and to then map all of the software and hardware infrastructure that this business service depended upon and to manage that collection of linked resources as an entity.

While Business Service Management sounded like a great idea, it in fact ended up as a miserable failure. The reasons were:

• There were many applications for which it was just too hard to measure their performance (in response time terms). Web applications turned out to be pretty easy, but fat client Win32 applications written to proprietary client/server protocols turned out to be very hard. It turned out that for most enterprises, more than half of the business critical applications were in the hard pile (fat client/Win32) and less than half were the easy web applications.
• Many BSM frameworks relied upon scripts and synthetic transactions to measure response time and end user experience. However this approach failed for many enterprises due to the large number of applications that comprised a business service and how rapidly these applications were changing. For example if synthetic transactions were used to measure the performance of a set of transactions, and a company had 500 business critical applications (not a very high number – some companies have thousands), and each application was updated once a year, then that would translate into 10 updates a week for the monitoring scripts.
• The same is true for most passive monitoring approaches that rely upon templates to identify transactions in applications protocols. There are many products that can measure the response time of transactions from the perspective of the web server by attaching physical or virtual appliance to a span port on the switch that services the web server. However all such products require configuration to understand what set of granular http request/responses combine to create a transaction of interest. Maintaining these configurations across hundreds of applications and thousands of transactions proved to be a major impediment to instrumenting their service level in any kind of a broad and systematic manner.
• It turned out to be a nightmare to identify the hardware and software that supported each business service. This gave rise to the need for Configuration Management Databases (CMDB’s) that were supposed to get populated with the hardware and software assets and their relationships to each other. The effort to put in place a CMDB and to maintain it turned out to doom the CMDB projects and the associated BSM projects at many companies.
• The BSM vendors were unable to evolve their products at the same rate as the innovation of the vendors who contributed products to the layers in the cake. New devices (laptops that were not always connected), new protocols (ICA, VOIP), new operating systems (Linux), new languages (Java, C#), and new user interfaces (first the browser and then rich Internet applications) all occurred at a pace that no one vendor could keep up with.
• When the BSM vendors got overwhelmed by innovation, vendors of point monitoring solutions stepped in to monitor the newest layer or item in a layer.  This lead to a proliferation of monitoring tools which were not integrated with each other.
• When a problem occurred even if one had a BSM product and a CMDB it still horribly difficult to know exactly what path the failed transaction took through the entire hardware and software infrastructure. The BSM tools were rarely aware of every element of the stack and the tactical monitors that had been bought to fill in the cracks were not integrated with the BSM tools nor each other.

In summary we entered the age of virtualization and the cloud with both BSM and their supporting CMDB’s having failed at monitoring and managing a static infrastructure where applications and services largely stayed on dedicated hardware. In other words, before virtualization and the dynamic data center it was impossible for anyone in IT to see a problem and get told in a deterministic manner exactly where the problem was and how to fix it.

The Impact of Virtualization and the Cloud

Since holistic end-to-end monitoring of business services was essentially broken (or not attainable) before virtualization, it is reasonable to assume that virtualization and the cloud will only make this problem worse. This will occur for the following reasons:

1. Virtualization increases workload density and the dynamic operation of workloads. This will require both continuous mapping of application to infrastructure dependencies and more more frequent (near real time) collection of performance data. Just the requirements for real time mapping and real time data completely overwhelm existing monitoring systems. Hyperic has a good blog on this point here.
2. Inferring application performance from resource utilization statistics becomes impossible. This was possible on physical hardware, but on hardware that is shared via virtualization it no longers works. Hence the need for Infrastructure Performance Management solutions that measure Infrastructure Response Time. We expect Infrastructure Performance Management solutions from vendors like Akorri, CA Technologies (CA Virtual Assurance), Virtual Instruments, and Xangati to form the foundation layer of whatever will replace BSM.
3. Application will now get moved from cluster to cluster and ultimately from data center to data center (private cloud – hybrid cloud – public cloud). APM solutions will need to track the applications no matter where they go, and seamlessly work across different IP networks. Leading virtualization aware APM solutions like those from AppDynamics, BlueStripe, and New Relic meet these needs today and will likely form the APM layer of whatever replaces BSM.

All of the above together combine to create one new result for Systems Management. That new result is that in the general case it will be impossible to deterministically do root cause in a dynamic environment. This was explored in detail in this post.

The Significance of the Integrien Acquisition

The Integrien acquisition by VMware is significant because it means that VMware has recognized that only a dynamic, statistical, self-configuring,  and self-learning approach can keep up with the rate of change in these new dynamic IT environments. The self-learning approach simply means that you feed the system the metrics that get collected about the system and it figures out which ones are important, how the metrics are related to each other, and lets you know when anomalies have occurred.

This acquisition is all the more significant because this is not garden variety technology. There have only ever been three companies this this space. ProactiveNet was acquired by BMC a few years ago. Netuitive has been around since the late 1990′s and it took the company until the mid 2000′s before the product had matured into something that really just worked when you plugged it in. Integrien is a fairly recent entry in this field and is now part of VMware – which leaves Netuitive as the only remaining independent player.

The New Dynamic BSM – Service Assurance

Since the old BSM is dead due to a brittle and difficult to update technology approach it is reasonable to ask what will replace it. The answer is most likely a set of Infrastructure Performance Management tools (Akorri, CA Virtual Assurance, Virtual Instruments, Xangati) integrated with a set of next generation APM tools (AppDynamics, BlueStripe, New Relic) vis these self learning technologies. When this occurs, we will have a system that adapts on its own to changing conditions in the environment leaving IT staff available to interpret results (and not raw monitoring data). We will also have taken an important step towards dynamic service assurance which was discussed in detail in this post.

Understanding and Evaluating these Technologies

For most IT professionals either they or someone on their staff can digg in and understand how the technologies that they use work. However unless you have an advanced degree in statistics and/or mathematics you are not going to be able to dig an and decide for yourself based upon how these products work which one you should choose. Rather what you should do is apply the following criteria in making your selection:

1. Decide exactly what you want the product to do for you. These products are extremely flexible. You can feed them every alarm that is generated by all of your monitoring solutions and let them sort out the good ones from the bad ones. Or you can feed them revenue per minute for one key business application and let them figure what causes degradations in revenue per minute.
2. Make sure that the product has connectors to what you already use to collect metrics from your systems. These products are not in the data collection business (with some exceptions). They rely upon other products to collect data from them. They must therefore be interfaced with your existing monitoring solutions.
3. How hands off and plug and play will the product be in practice? This is the key criteria to the long term value of such a solution to your enterprise. Previous attempts at statistical approaches (neural nets) failed because the product had to be “retrained” every time conditions changed. Make sure that the product you select can automatically select and weight the inputs that it bases decisions off of and these these decisions are automatically updated over time. Self-learning needs to be a continuous thing, not just a one time or periodic thing.
4. Make sure that the product can handle time based (time series) as well as event based data. Performance metrics tend to be time based, but many performance problems are caused by configuration changes which are events. Make sure that the product can cross-correlate configuration change events with performance degradations.
5. Carefully assess the scale of the solution. This means how many inputs can the solution take per unit of time. Right now most of these solutions operate at 15 minute or 5 minute intervals. Monitoring a dynamic system may require intervals of 10 or even 5 seconds (or perhaps even real time continuous streams of monitoring data).

Summary

Self-learning performance management solutions like Integrien and Netuitive are going to be absolutely an essential part of the migration to dynamic data centers and IT as a Service. Once these dynamic data centers scale out to the thousands of applications in a typical enterprise, and scale up to address the most performance critical applications, the rate of change in the environment will be too high for legacy tools and manual administration to be able to keep. up. These automated self-learning approaches will be the only way in which IT Operations will be able to stay on top of these new environments while staying within staffing and budget constraints.

Related posts:

1. 图书推荐《服务建模：原理与应用》
2. 让Remedy飞一会
3. 老美真的很扯，一个职位的帖子被顶了22次