本来想塞到上一主题，想想还是清晰点好。
标题是直接复制OBE的，看起来贼官方。
http://www.oracle.com/technology/obe/obe_bi/bi_ee_1013/index.html

OBI EE的OBE并没有全部做过，但内容大概没有生疏的。何况人很容易自我麻痹，比如我就觉得我看看就能看出点关键来，sigh！
官方的内容顺序：
Creating Interactive Dashboards and Using Oracle Business Intelligence Answers  
Creating a Repository Using the Oracle Business Intelligence Administration Tool  
Installing the Oracle Business Intelligence Enterprise Edition on Windows
Using Oracle OLAP With Oracle Business Intelligence Enterprise Edition  
Integrating Oracle BI Publisher with Oracle Business Intelligence Enterprise Edition  
Sending Alerts Using Oracle Business Intelligence Delivers
Using Microsoft Office Addin
按官方数据这些实验做下来也就10几个小时，24h以内。估摸着这些全部做一遍，您就可以接活了。
较好的顺序是：
Installing the Oracle Business Intelligence Enterprise Edition on Windows ->
Creating Interactive Dashboards and Using Oracle Business Intelligence Answers  ->
Creating a Repository Using the Oracle Business Intelligence Administration Tool  ->
Integrating Oracle BI Publisher with Oracle Business Intelligence Enterprise Edition  ->
Using Microsoft Office Addin ->
Using Oracle OLAP With Oracle Business Intelligence Enterprise Edition  ->
Sending Alerts Using Oracle Business Intelligence Delivers ||

Part I - Installing the Oracle Business Intelligence Enterprise Edition on Windows
http://www.oracle.com/technology ... nstalloraclebee.htm

1234呢人家官网很详细了，偶当复习一样过一下这些HandsOn.
给人培训过，也培训过别人。要搞懂一个东西，起码你得能把道理给另一个人讲通了。一堂课下来谁的收货最大？讲师！尤其是非专业的讲师！

安装么什么好补充的，忒细了。自己前面的帖子简直就是n级索引了。
其实看那么大堆Prerequisites别慌，出了问题再看不迟呵呵。

遇到的问题有两：
1，Application Server
很久以前试图部署到自己的iAS上，没有成功。
2，IIS
更久以前无数次试图部署到IIS上，没有成功。
现在一直安于Tomcat或者OC4J.

Part II - Creating Interactive Dashboards and Using Oracle Business Intelligence Answers
http://www.oracle.com/technology ... e_1013/saw/saw.html
前端的东西比较感性，看得见摸得着。先玩Dashboard，有兴趣的自然会记着Admintool.
开过的为数不多的课程里面，按此顺序比较好。不过看课程时间，也看对象：用户or开发者。
官方报时2h，其实要不熟悉，来回切换页面至少得4小时做的完。所以最好双屏，启用第二显示器，大大加快试验速度。
最初没有完全做完，后来做了10几张报表，算是遍历其中的操作。

[ 本帖最后由 北冥 于 2008-3-19 16:02 编辑 ]

Part III - Creating a Repository Using the Oracle Business Intelligence Administration Tool
http://www.oracle.com/technology ... _admin/biadmin.html
精华。
官方报时4个小时。没有6个小时不行，天才不在此列，熟练工也不算。
过这个实验的时候基本瞄图片而已。后来有时间瞄文字了，发现果然还是文字的信息量比较大

补充：
1，odbc数据源要求是系统dsn，因为import源数据信息的时候只显示系统dsn的列表。
2，Physical Diagram或者其他的Diagram的大小无法自适应，只能手动缩放比例。这个有点遗憾，虽然不甚重要。

接着补充：
3，个人习惯完全手动建维度。毕竟难得客户或者自己的表足够标准。但是使用Wizard还真挺快，呵呵，其实编辑也挺费力。别迷信Wizard。但是也别歧视它。
4，维度Level里面Number of elements这项奇怪，其实随便写或者完全不写都不会怎的。也许基于某种优化的考虑，我有兴趣知道，但是还没有兴趣到去试验到底多大不同。
5，格式方面。尤其是对象签出，老是会有提示，个人喜欢关闭该项，绝对省心。

补充继续：
6，Logical Level Key
维度的每一level必须要有有一个logical level key，否则check in的时候会有个一个警告。我同样好奇其必须性，又不够好奇去探究个所以。
----------------------------------------
Level keys. Each logical level (except the topmost level defined as a Grand Total level) needs to
have one or more attributes that compose a level key. The level key defines the unique elements
in each logical level. The dimension table logical key has to be associated with the lowest level
of a dimension and has to be the level key for that level.
A logical level may have more than one level key. When that is the case, specify the key that is
the primary key of that level. All dimension sources which have an aggregate content at a
specified level need to contain the column that is the primary key of that level. Each logical level
should have one level key that will be displayed when an Answers or Intelligence Dashboard user
clicks to drill down. This may or may not be the primary key of the level. To set the level key to
display, select the Use for drill down check box on the Level Key dialog box.
----------------------------------------

7，Time Dimension
时间维度在任何BI产品中都会是一个特殊的维度，因此自然有许多特殊的属性和函数可以应用。
时间层次还要求一个chronological keys，时间函数的机理所在。
----------------------------------------
You can identify a dimension (for example, Year) as a time dimension. At least one level of a time dimension must have a chronological key. The
following is a list of some guidelines you should use when setting up and using time dimensions:
■ At least one level of a time dimension must have chronological key. For more information,
■ All time series measures using the Ago and ToDate functions must be on time levels. Ago and
ToDate aggregates are created as derived logical columns.
■ Any physical table that is part of a time logical table cannot appear in another logical table.
This prevents using date fields from calendar table as measures.
■ Physical tables in time sources, except the most detailed ones, cannot have joins to table
outside their source. The join has to be between the time table and the fact table. The join
can only be based on foreign key; it cannot be a complex join.
■ Ago or ToDate functionality is not supported on fragmented logical table sources.
----------------------------------------

今天，加入ITPUB满4周年了

8，Use for drilldown
可以多个logical level key，但是钩选Use for drilldown后，嘿嘿，试试就知道了。

好贴，请继续