在instanceconfig.ini文件中增加如下配置可以修改数据透视表的最大行数和大小。
<CubeMaxRecords>50000</CubeMaxRecords> <CubeMaxPopulatedCells>1500000</CubeMaxPopulatedCells>
OBIEE11g被看做是nQuire的成人版。在3年的研究和开发过程中，一些新的特性被增加到已经很出名的10g版本中。有新的计分板引擎，全新的UI,动作框架被集成进来支持业务流程，新的地理地图功能，OLAP的用户界面，支持多类型的层次，跳过级别和递归的。特别地，OLAP支持将独立于底层的数据库。所以OLAP的下钻针对哪些关系型数据库，比如Oracle，DB2也是可行的。
导航到得目标报表是否有下载链接，取决于，来源目标有没有下载链接，一般如果在仪表盘页面上指定了报表的链接会传递到导航的报表上去。
There is a NQSconig.ini parameter that, by default, limits the server to 100 concurrent threads (db queries).
You change parameters as follows to allow more sessions to run concurrently:
[ SERVER ]
MAX_SESSION_LIMIT = 40000;
MAX_REQUEST_PER_SESSION_LIMIT = 500;
SERVER_THREAD_RANGE = 450-450;
In addition, when conducting performance tests I have noticed usage tracking cannot keep up and increased parameter settings:
[ USAGE_TRACKING ]
BUFFER_SIZE = 100 MB ;
BUFFER_TIME_LIMIT_SECONDS = 5 ;
NUM_INSERT_THREADS = 20 ;
MAX_INSERTS_PER_TRANSACTION = 10 ;
Setting the above parameters have enabled us previously to simulate 100s of concurrent users running queries simultaneously.
11g的新功能介绍，有时间可以去看看
11g中如何创建answer和dashboard的一个课件
):
sending alerts
http://st-curriculum.oracle.com/obe/fmw/bi/biee/r1013/delivers/delivers.htm
Creating and Modeling Aggregate Tables
http://st-curriculum.oracle.com/obe/fmw/bi/biee/r1013/aggpersist/aggpersist.htm
用户跟踪
http://st-curriculum.oracle.com/obe/fmw/bi/biee/r1013/usage_tracking/usage_tracking.htm
通过go链接来修改会话变量：
http://www.doc88.com/p-94367819123.html
OC4J对于BI Publisher和schedule是可替换的模块。
如果在RPD文件中队多个数据连接池指定"Execute Queries Asynchronously"，可能会导致BI server挂掉。
./run.sh -service >> /usr/local/OracleBIData/web/log/javahost.out.log 2>&1 &
北冥的论坛文章：http://ms.itpub.net/viewthread.php?tid=1090110
obiee的性能优化手段：
http://www.iwarelogic.com/blog/performance-increasing-obiee-724
升级OBIEE 10g的RPD
http://www.divinesystems.com/blog/?p=78
安装的论坛文章
http://kr.forums.oracle.com/forums/thread.jspa?threadID=1119816
调用OBIEE的web service
控制仪表盘提示下拉列表展示过多值：
<Prompts><MaxdropdownValues>256</MaxdropdownValues></Prompts>
<CubeMaxRecords>3000000</CubeMaxRecords>
<CubeMaxPopulatedCells>3200000</CubeMaxPopulatedCells>
<CubeMaxPopulatedCells>3200000</CubeMaxPopulatedCells>
<PivotView>
<MaxCells>3000000</MaxCells>
</PivotView>
<CubeMaxRecords>3000000</CubeMaxRecords>
<CubeMaxPopulatedCells>3200000</CubeMaxPopulatedCells>
<MaxCells>3000000</MaxCells>
</PivotView>
<CubeMaxRecords>3000000</CubeMaxRecords>
<CubeMaxPopulatedCells>3200000</CubeMaxPopulatedCells>
登陆重定向
定制logoncontrolmessages.xml文件
从\\OracleBI\web\msgdb\messages下复制到\\OracleBIData\web\msgdb\customMessages下
编辑kmsgAuthenticateUnableToLogon部分,如下,
<td class="ErrorTitle">
<sawm:messageRef name="kmsgAuthenticateUnableToLogon" />
<SCRIPT>location.href="http://www.google.com"</SCRIPT>
</td>
重新启动Presentation Service.
定制logoncontrolmessages.xml文件
从\\OracleBI\web\msgdb\messages下复制到\\OracleBIData\web\msgdb\customMessages下
编辑kmsgAuthenticateUnableToLogon部分,如下,
<td class="ErrorTitle">
<sawm:messageRef name="kmsgAuthenticateUnableToLogon" />
<SCRIPT>location.href="http://www.google.com"</SCRIPT>
</td>
重新启动Presentation Service.
定制默认组合视图，copy自Venka的Blog(
http://oraclebizint.wordpress.com/)
But what the customer basically wanted was to include a filter and table view by default (i.e filter view instead of title view). The method is given in the bookshelf. But unfortunately it does not work as specified due to a documentation bug. In order to make this work, go to {OracleBI}\web\msgdb\messages folder and you would find a file called answerstemplates.xml. Copy this file to {OracleBIData}\web\msgdb\customMessages. If you dont have this folder then create it. Now edit this file and search for kuiCriteriaDefaultViewElements. This is the message that handles all the default values possible in Answers. Now add the the following tags to this message after the HTML tags,
<view signature=”compoundView” >
<cv signature=”tableView” />
<cv signature=”filtersView” />
</view>
Once this is done restart your presentation services. Now you would see that by default you would have got Table and Filter views within your compound layout.
But what the customer basically wanted was to include a filter and table view by default (i.e filter view instead of title view). The method is given in the bookshelf. But unfortunately it does not work as specified due to a documentation bug. In order to make this work, go to {OracleBI}\web\msgdb\messages folder and you would find a file called answerstemplates.xml. Copy this file to {OracleBIData}\web\msgdb\customMessages. If you dont have this folder then create it. Now edit this file and search for kuiCriteriaDefaultViewElements. This is the message that handles all the default values possible in Answers. Now add the the following tags to this message after the HTML tags,
<view signature=”compoundView” >
<cv signature=”tableView” />
<cv signature=”filtersView” />
</view>
Once this is done restart your presentation services. Now you would see that by default you would have got Table and Filter views within your compound layout.
oc4j vs iAS
有哥们obiee原装standalone oc4j，后需要部署到iAS上，因为要集成sso和portal，可是又不想重装obiee，直接重新部署analytics.war包到as的oc4j上。如果iAS和biee presentation在同一机器上，问题不大。不在呢，也不大。
解压analytics.war包，编辑web-inf\web.xml
- <init-param>
<param-name>oracle.bi.presentation.sawserver.Host</param-name>
<param-value>localhost</param-value>
</init-param>
- <init-param>
<param-name>oracle.bi.presentation.sawserver.Port</param-name>
<param-value>9710</param-value>
按需设置这2个参数，重新打包，然后发布。
其实个人不晓得是不是万无一失，如果是，那obiee安装时候就应该允许这样后续迁移发布。如果不是，俄，以上方案仅供参考。
有哥们obiee原装standalone oc4j，后需要部署到iAS上，因为要集成sso和portal，可是又不想重装obiee，直接重新部署analytics.war包到as的oc4j上。如果iAS和biee presentation在同一机器上，问题不大。不在呢，也不大。
解压analytics.war包，编辑web-inf\web.xml
- <init-param>
<param-name>oracle.bi.presentation.sawserver.Host</param-name>
<param-value>localhost</param-value>
</init-param>
- <init-param>
<param-name>oracle.bi.presentation.sawserver.Port</param-name>
<param-value>9710</param-value>
按需设置这2个参数，重新打包，然后发布。
其实个人不晓得是不是万无一失，如果是，那obiee安装时候就应该允许这样后续迁移发布。如果不是，俄，以上方案仅供参考。
oc4j or iAS (p17)具体不说了，补充2点，
1怎么不自动起oc4j
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" you will notice that an entry named "oc4j" is created during the installation, which starts up OC4J.
2,怎么注册成服务
venka的blog提过，
javaservice -install "Oracle BI: OC4J Service" "x:\jdk1.5.0_09\jre\bin\client\jvm.dll" -XX:MaxPermSize=128m -Xmx512m "-Djava.class.path=x:\OracleBI\oc4j_bi\j2ee\home\oc4j.jar" -start oracle.oc4j.loader.boot.BootStrap -description "Oracle BI Oc4J Service"之类
scheduler(p20)，仍然需要手动到目录（ \\OracleBI\server\Schema）依据目的数据库类型选择相应脚本运行，创建相关表。
b31769.pdf-Web Service Guide
Venka的blog( http://oraclebizint.wordpress.com/)上无数的例子可供参考。该老兄全能，不像我，一个小工具主义者来着。
该GUIDE99%的内容用时翻阅即可，但是开篇（P9,10）那几段话画龙点睛来着。
What is Oracle BI Web Services?
Oracle BI Web Services is an application programming interface (API) that implements SOAP. Oracle
BI Web Services allows you to perform three types of function:
■ Extract results from Oracle BI Presentation Services and deliver them to external applications.
■ Perform Oracle BI Presentation Catalog management functions.
■ Execute Oracle Business Intelligence alerts (known as iBots).
Oracle BI Web Services allows external applications such as J2EE and .NET to use Oracle Business
Intelligence as an analytical calculation and data integration engine. It provides a set of Presentation
Services that allow external applications to communicate with Oracle BI Presentation Services. You
can use Oracle BI Web Services to extract results from Oracle BI Presentation Services and deliver
them to external applications and Web application environments. You can reference a saved report
or send the criteria for the report to Oracle BI Web Services.
The formal definition of services and methods in Oracle BI Web Services can be retrieved in WSDL
(Web Services Definition Language) format. Proxy classes for the services can be generated
automatically.
The XML Schema Definition (XSD) file for the services is the file SawServices.xsd, which is located
in the \Web\App\Res\Wsdl\Schemas directory in the Oracle Business Intelligence Platform
installation directory. The XSD file is used internally and cannot be used separately. You can access
the WSDL document at the following Oracle BI Web Services URL:
http://<somehost>/analytics/saw.dll?WSDL
Oracle BI Web Services is supported on Oracle JDeveloper, Apache Axis, and the Microsoft .NET
framework.
P12关于LICENSE事情，非商务者PASS；）
应该都是<WebMessage name="kmsgLicenseSOAPAccess"><TEXT>Oracle Engineering</TEXT></WebMessage>
关于soap访问权限问题倒是有意思，默认是所有用户都能的。可以在administration的previledge设置中显式deny。然后据说抛错“Access Denied”（么亲眼见过哈）。
具体开发按类找对应方法、参数和相关解释，这是本纯粹的手册：
HtmlViewService Service on page 33
iBotService Service on page 39
MetadataService Service on page 40
ReplicationService Service on page 44
ReportEditingService Service on page 46
SAWSessionService Service on page 47
SecurityService Service on page 52
WebCatalogService Service on page 57
XMLViewService Service on page 71
最后有一个code sample，我么跑起来呵呵。错误和sawbridge配置有关。
Venka的blog( http://oraclebizint.wordpress.com/)上无数的例子可供参考。该老兄全能，不像我，一个小工具主义者来着。
该GUIDE99%的内容用时翻阅即可，但是开篇（P9,10）那几段话画龙点睛来着。
What is Oracle BI Web Services?
Oracle BI Web Services is an application programming interface (API) that implements SOAP. Oracle
BI Web Services allows you to perform three types of function:
■ Extract results from Oracle BI Presentation Services and deliver them to external applications.
■ Perform Oracle BI Presentation Catalog management functions.
■ Execute Oracle Business Intelligence alerts (known as iBots).
Oracle BI Web Services allows external applications such as J2EE and .NET to use Oracle Business
Intelligence as an analytical calculation and data integration engine. It provides a set of Presentation
Services that allow external applications to communicate with Oracle BI Presentation Services. You
can use Oracle BI Web Services to extract results from Oracle BI Presentation Services and deliver
them to external applications and Web application environments. You can reference a saved report
or send the criteria for the report to Oracle BI Web Services.
The formal definition of services and methods in Oracle BI Web Services can be retrieved in WSDL
(Web Services Definition Language) format. Proxy classes for the services can be generated
automatically.
The XML Schema Definition (XSD) file for the services is the file SawServices.xsd, which is located
in the \Web\App\Res\Wsdl\Schemas directory in the Oracle Business Intelligence Platform
installation directory. The XSD file is used internally and cannot be used separately. You can access
the WSDL document at the following Oracle BI Web Services URL:
http://<somehost>/analytics/saw.dll?WSDL
Oracle BI Web Services is supported on Oracle JDeveloper, Apache Axis, and the Microsoft .NET
framework.
P12关于LICENSE事情，非商务者PASS；）
应该都是<WebMessage name="kmsgLicenseSOAPAccess"><TEXT>Oracle Engineering</TEXT></WebMessage>
关于soap访问权限问题倒是有意思，默认是所有用户都能的。可以在administration的previledge设置中显式deny。然后据说抛错“Access Denied”（么亲眼见过哈）。
具体开发按类找对应方法、参数和相关解释，这是本纯粹的手册：
HtmlViewService Service on page 33
iBotService Service on page 39
MetadataService Service on page 40
ReplicationService Service on page 44
ReportEditingService Service on page 46
SAWSessionService Service on page 47
SecurityService Service on page 52
WebCatalogService Service on page 57
XMLViewService Service on page 71
最后有一个code sample，我么跑起来呵呵。错误和sawbridge配置有关。
1. Aggregate table - 由于BIEE可以设置多个数据源connection，性能问题是最值得考虑的问题。我想oracle所做的测试性能的数据能如此好，主要是aggregate table设计的比较好。
--Aggregate table的附加问题是粒度设计和数据更新。
2. current/history table - BIEE支持配置current/history table，这个也是提高性能的关键技术。
--回去瞄瞄。偶现在基本自废了，惭愧啊。
3. dimension - 合理的dimension设计也是比较关键，涉及到报表drilldown问题。
--不言自明。多路钻取，维度间的交互也有意思。
4. physical layer - 尽量保持原有table，少用view。对于join关系要确保符合逻辑，不要形成多路join。采用alias是BIEE的best practice。
--原则就是扬长避短，能db处理的逻辑尽量交由db。至于join，其实很多时候取决于开放给我们的物理结构。事实上，80%的时间还是在db/dw。Alias其实更多地保持模型的清晰化和可维护性。
--Aggregate table的附加问题是粒度设计和数据更新。
2. current/history table - BIEE支持配置current/history table，这个也是提高性能的关键技术。
--回去瞄瞄。偶现在基本自废了，惭愧啊。
3. dimension - 合理的dimension设计也是比较关键，涉及到报表drilldown问题。
--不言自明。多路钻取，维度间的交互也有意思。
4. physical layer - 尽量保持原有table，少用view。对于join关系要确保符合逻辑，不要形成多路join。采用alias是BIEE的best practice。
--原则就是扬长避短，能db处理的逻辑尽量交由db。至于join，其实很多时候取决于开放给我们的物理结构。事实上，80%的时间还是在db/dw。Alias其实更多地保持模型的清晰化和可维护性。
5. business layer - 采用星型结构。这个是BIEE最核心的layer，东西很多，需要加强练习，明白各个页面的意思和作用是能否成功完成设计的关键。
--理想化的情况下简单即强大。小雪花也不错啊。
6. presentation layer - 由于一张报表基于一个subject area，设计合理的subject area也是比较重要问题。
--这点不晓得是不是偶理解得偏差。一个主题的目标不是符合一张报表，应该是一套、一系列、一个专题的需求。主题多起来的时候自己会琢磨是不是设计上不合理。为一张报表定制一个主题，肯定什么地方出了问题...
7. report page- 尽量将相同filter的report整合到一个page中，通过下拉菜单实现选择不同报表。biee又一best practice。
--不敢苟同。信息的组织方式和信息本身一样都有附加价值。性能不成瓶颈的情况下我更优先用户的使用习惯。相同filter很容易造成数据访问热点，而且很多情况下客户并不需要同时刷出多类信息。大布局很容易造成访问障碍。个人优先优化访问路径。总之，信息的组织优于信息的返回。
--理想化的情况下简单即强大。小雪花也不错啊。
6. presentation layer - 由于一张报表基于一个subject area，设计合理的subject area也是比较重要问题。
--这点不晓得是不是偶理解得偏差。一个主题的目标不是符合一张报表，应该是一套、一系列、一个专题的需求。主题多起来的时候自己会琢磨是不是设计上不合理。为一张报表定制一个主题，肯定什么地方出了问题...
7. report page- 尽量将相同filter的report整合到一个page中，通过下拉菜单实现选择不同报表。biee又一best practice。
--不敢苟同。信息的组织方式和信息本身一样都有附加价值。性能不成瓶颈的情况下我更优先用户的使用习惯。相同filter很容易造成数据访问热点，而且很多情况下客户并不需要同时刷出多类信息。大布局很容易造成访问障碍。个人优先优化访问路径。总之，信息的组织优于信息的返回。
8. union - 报表展现可采用union技术，即combine with similar request
--慎用。个人用combine的时候第一个自问便是：这是因为我设计的模型上的限制么？不过minus很好用。
9. presentation variable/request variable/session variable/server variable - 理解这些不同类型variable应用范围和使用方法
--嗯，同意。可惜，文档缺乏。改天整整。
--慎用。个人用combine的时候第一个自问便是：这是因为我设计的模型上的限制么？不过minus很好用。
9. presentation variable/request variable/session variable/server variable - 理解这些不同类型variable应用范围和使用方法
--嗯，同意。可惜，文档缺乏。改天整整。
10，修改首页的logo的路径为：OracleBI\web\app\res\s_oracle10\b_mozilla_4，可以调整CSS，也可以对原图片进行ps一把。