Professional Documents
Culture Documents
Release Notes
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind
with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness
for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks
used herein are the property of their respective owners.
Copyright 2011 EMC Corporation. All rights reserved.
Revision History:
December 2011: Added BAM-4955 to the Known Problems and Limitations chapter.
August 2011: Expanded Whats New features descriptions. Updated Technical Notes chapter specifying how to connect
to Oracle RAC databases.
June 2011: Updated Environment and System Requirements chapter.
April 2011: Initial Release.
Table of Contents
Chapter 1
Chapter 2
Chapter 3
.....................................................................................................
Documentum Business Activity Monitor documentation.....................................
Software download information ........................................................................
Troubleshooting and getting help ......................................................................
Overview
7
7
7
8
.....................................................
Improved product quality .................................................................................
.....................................................
Hardware requirements ....................................................................................
Browser machine requirements .....................................................................
Web application server machine requirements ................................................
Software requirements ......................................................................................
Browser environment ...................................................................................
Web application server environment ..............................................................
Java version support .....................................................................................
Content Server and Business Activity Monitor environment ............................
Process Reporting Services client ...................................................................
Additional operating environments ...............................................................
VMware support ......................................................................................
IBM Logical Partitioning support ...............................................................
Sun Microsystems support ........................................................................
Citrix support...........................................................................................
Siteminder support ...................................................................................
RSA support ............................................................................................
Native 64-bit support ................................................................................
11
11
11
12
12
13
16
20
22
26
26
26
27
27
28
28
28
28
29
29
29
29
30
30
........................................................................................... 33
Fixed Problems................................................................................................. 33
Chapter 4
Fixed Problems
Chapter 5
...............................................................
Known problems ..............................................................................................
Limitations.......................................................................................................
Additional information about limitations .......................................................
Migrating custom entities designed with SDTs BAM-3912 ...........................
Oracle script .........................................................................................
MS SQL Server script ............................................................................
37
37
39
41
41
42
43
Table of Contents
Chapter 6
Technical Notes
........................................................................................... 47
47
47
48
48
48
48
Table of Contents
List of Tables
Table 1.
12
Table 2.
13
Table 3.
14
Table 4.
15
Table 5.
17
Table 6.
18
Table 7.
21
Table 8.
23
Table 9.
26
Table 10.
26
Table 11.
Table 12.
27
27
Table 13.
Citrix support.......................................................................................................
28
Table 14.
29
Table of Contents
Chapter 1
Overview
The Business Activity Monitor (BAM) is a product of EMC Documentum that gives business users
insight into processes executing in the Documentum Process Engine. It provides the ability to generate
alerts in real time and creates a dashboard view that shows process status and performance statistics.
Overview
Chapter 2
New Features and Changes for BAM 6.7
This chapter describes the following new features and changes for BAM 6.7:
Improved product quality, page 9
10
Chapter 3
Environment and System
Requirements
This chapter lists the hardware (machine) requirements and software versions supported with this
release. Machine resources, non-Documentum software components (Operating System, Java
Runtime Environment, and so forth), and other EMC Documentum products determine the unique
environment for each EMC Documentum product. Hardware requirements, page 11, addresses basic
machine resource requirements. Software requirements, page 12, addresses specific software versions
that are required for the installation platform.
Business Activity Monitor (BAM) gives business users insight into processes executing in
Documentum Process Engine. It provides the ability to generate alerts in real time and creates a
dashboard view that shows process status and performance statistics. Business Activity Monitor
enables organizations to detect problem conditions that may exist in executing processes, to diagnose
these problems to determine their root cause, and to correct them. It also provides valuable historical
information about process execution to enable long-term process improvement. The supported
browsers, web application servers, and database platforms are detailed in the Business Activity
Monitor tables.
Hardware requirements
This section lists nominal machine resources required for product installation and use.
11
RAM [2]
CPU
Minimum:
2 GB
Note: The following specific notes apply to the web application server machine requirements table:
[1] You must also have sufficient free disk space to handle temporary content transfer files, which
can vary substantially from one enterprise to another.
[2] The amount of RAM that is available after taking into consideration all other RAM utilization
requirements.
Software requirements
This section provides information on supported software environments.
The tables in this section reflect the latest versions of third-party products, upon which the EMC
Documentum product depends, that are supported at the time of this release. EMC Documentum
recommends that you upgrade third-party products to the version listed for this release. If you
cannot upgrade your third-party products to the version listed for this release, EMC Documentum
continues to support all third-party product versions supported for EMC Documentum product
versions 6.x and 5.3x, with the following caveats:
The third-party product is not of the same or earlier version than those versions listed in Table
2, page 13
The third-party product version is still supported by the third-party vendor
The third-party product version is forward compatible with the version supported in this release
For information on currently supported environments and future updates, refer to the Product
Information System on the Powerlink website: http://powerlink.EMC.com.
12
Product category
Operating system
Database
Application server
Browser
JRE (client)
Java (server)
Portal server
Third-party product
Version
Windows
Mac OS X
10.2.8, 10.3.9
Solaris
AIX
5.2
HP-UX
HP-UX 11
3.x
Oracle 9i
9.2.0.8, 10.1.0.5
SQL Server
2000 SP4
DB2 UDB
Sybase
Not Supported
8.1 SP6
Tomcat
5.0.28
IBM WebSphere AS
5.1.1.13, 6.0.2.17
Oracle AS 10g
9.0.4.3, 10.1.2
Mozilla
1.7.13
Netscape
7.2
Safari
1.3.2
Sun JRE
1.4.2_13
Microsoft JVM
5.0.0.3810
Apple Java
1.3.1 Release 2
Java
1.4.x
8.1 SP6
5.1.0.4
Browser environment
The user interface for Business Activity Monitor runs in a browser environment. The browser
environment consists of a specific combination of operating system, browser, and JRE. The browser
environment tables for Business Activity Monitor (Table 3, page 14, and Table 4, page 15) lists the
supported browser environments.
13
Operating system/Processor (1 of 2)
Win XP
SP3 (32bit)/IA32, x64
Browser
JRE
Firefox 3.5.9
Firefox 3.6.12
Win
Vista
SP2 (32bit)/IA32, x64
Win 7
(32-bit)/
IA-32,
x64
Win 7
(64-bit)/
x64
Win
Server
2008 SP2
(32-bit)/
IA-32,
x64
Win
Server
2008 SP2
(64-bit)/
x64
Win
Server
2008 R2
(64-bit)/
x64
Note: The X symbol denotes the supported combination of browser, JRE, and operating system.
14
Operating system/Processor (2 of 2)
Solaris
10/UltraSPARC
RHEL
4.8/IA-32,
x64
RHEL
5.4/IA-32,
x64
SUSE
Linux Enterprise
Desktop
10 SP3/
IA-32, x64
SUSE
Linux
Enterprise
Desktop
11/IA-32,
x64
SUSE
Linux Enterprise
Server 10
SP3/IA32, x64
SUSE
Linux
Enterprise
Server 11
SP1/IA32, x64
Browser
JRE
Firefox 3.5.9
Firefox 3.6.12
Note: The X symbol denotes the supported combination of browser, JRE, and operating system.
15
Note: The following specific notes indicated by [ ] apply to the browser environment table:
[1] Build number of this browser is 7.00.5730.1300.
[2] Build number of this browser is 7.00.6001.1800.
[3] Build number of this browser is 8.00.6001.18702.
[4] Build number of this browser is 8.00.7000.00000.
Note: The following general notes apply to the browser environment table:
The following Windows Server 2008 editions are supported: Standard, Enterprise, Data Center.
IA-32 = Intel Architecture 32-bit
x64 = 64-bit Architecture which includes AMD64 and Intel 64
For Windows environment, disable its built-in popup-blocker, or add the application server
as a trusted site if you are using IE7 or IE8.
Turn off User Account Control for each user or in the browser add the site to the list of trusted
sites in IE and in the application set the UCF client configuration registry mode value to file
instead of windows.
Cookies must be enabled in the browser.
The following Red Hat Enterprise Linux editions are supported: AS, ES, WS, and Desktop.
Tier 1 language versions of the operating system and browser are supported. Tier 1 languages
are French, Italian, German, Spanish, Swedish, Brazilian-Portuguese, Dutch, Simplified Chinese,
Japanese, Korean, Russian, and Arabic.
16
Operating system/Processor (1 of 2)
Web application server
X [1]
X [1]
X [1]
X [1]
X [1]
X [1]
17
Operating system/Processor (2 of 2)
Web
application
server
18
AIX 5L
V5.3
TL12,
SoAIX
laris
10/Ul- V6.1
TL5
traSPARC /Power
[3]
[3]
HP-UX 11i
v2 Update
2 (B.11.23),
v3 Update
6 (B.11.23)/
PA-RISC
2.0 [3]
HP-UX 11i
v2 Update
2 (B.11.
23), v3
Update 6
(B.11.23)/
Itanium 2
[3]
RHEL
RHEL 4.8,
5.5/
4.8,
x64
5.5/
IA-32 [3]
SUSE
Linux
Enterprise
Server 10
SP3/IA32, x64
SUSE
Linux Enterprise
Server 10
SP3/x64
[3]
SUSE
Linux Enterprise
Server 11
SP1/IA32, x64
SUSE
Linux Enterprise
Server 11
SP1/x64
[3]
Apache
Tomcat 5.5.31
Apache
Tomcat 6.0.29
Oracle
WebLogic
Server 10g
(10.3) [2]
X [1]
Oracle
WebLogic
Server 11g
(10.3.3) [2] [4]
X [1]
IBM WAS
V6.1 Fix Pack
31 (6.1.0.31)
X [1]
X [1]
X [1]
X [1]
X [1]
X [1]
X [1]
X [1]
IBM WAS
V7.0 Fix Pack
9 (7.0.0.9)
X [1]
X [1]
X [1]
X [1]
X [1]
X [1]
X [1]
X [1]
Operating system/Processor (2 of 2)
Web
application
server
AIX 5L
V5.3
TL12,
SoAIX
laris
10/Ul- V6.1
TL5
traSPARC /Power
[3]
[3]
Oracle AS 10g
R3 (10.1.3.3.0)
HP-UX 11i
v2 Update
2 (B.11.23),
v3 Update
6 (B.11.23)/
PA-RISC
2.0 [3]
HP-UX 11i
v2 Update
2 (B.11.
23), v3
Update 6
(B.11.23)/
Itanium 2
[3]
RHEL
RHEL 4.8,
5.5/
4.8,
x64
5.5/
IA-32 [3]
SUSE
Linux
Enterprise
Server 10
SP3/IA32, x64
SUSE
Linux Enterprise
Server 10
SP3/x64
[3]
SUSE
Linux Enterprise
Server 11
SP1/IA32, x64
SUSE
Linux Enterprise
Server 11
SP1/x64
[3]
X [1]
X [1]
X [1]
X [1]
X [1]
X [1]
Oracle
GlassFish
Enterprise
Server v3 [5]
Note: The X symbol denotes the supported combination of operating system and web application server.
19
Note: The following specific notes indicated by [ ] apply to the web application server environment
table:
[1] Clustering (failover) support. See general notes for exceptions below.
[2] WebLogic web application server clustering support requires external load balancer or Web
Server acting as a load balancer.
[3] Support 64-bit version of operating system in native mode.
[4] Oracle WebLogic 10.3 is also supported since it is a 10g release as per Oracle.
[5] Sun Java System Application Server was renamed to Oracle GlassFish Enterprise Server.
Note: The following general notes apply to the web application server environment table:
The following Windows Server 2008 editions are supported: Standard, Enterprise, Data Center.
IA-32 = Intel Architecture 32-bit
x64 = 64-bit Architecture which includes AMD64 and Intel 64
Support 32-bit version and 64-bit version of web application server.
English, Simplified Chinese, Japanese, Korean, Russian (English with regional setting set to
Russian), and Arabic (English with regional setting set to Arabic) versions of the operating system
are supported.
20
Java
Oracle WebLogic
Apache Apache Server
Tomcat Tomcat 10g
(10.3)
6.0.29
5.5.31
5.0.x
6.0.x
Oracle
WebLogic
Server 11g
R1 (10.3.3)
IBM WAS
V6.1 Fix
Pack 31
(6.1.0.31)
IBM WAS
V7.0 Fix
Pack 9
(7.0.0.9)
X
X
Oracle
AS 10g
R3 (10.1.
3.3.0)
Red Hat
JBoss
EAP
4.3.0
Red Hat
JBoss EAP
5.1
Oracle
GlassFish
Enterprise
Server
v2.1
Note: The X symbol denotes the supported combination of Java and web application server.
21
22
Database
Oracle 11g
Release 2
(11.2.0.1.0)
SQL
Server
2008 R2
SQL
Server
2008
SP2 [3]
DB2 Universal
Database
(UDB) V9.5
FixPak 6a
DB2
Universal
Database
V9.7 Fix Pak
2
Operating system
Processor
Oracle 10g
Release 2
(10.2.0.5)
IA-32, x64
x64
x64
Solaris 10
UltraSPARC
Power
Power
PA-RISC 2.0
Itanium 2
X [2]
X [2]
PA-RISC 2.0
X [2]
X [2]
Itanium 2
X [2]
X [2]
IA-32, x64
X [2]
X [2]
23
Database
Oracle 11g
Release 2
(11.2.0.1.0)
Operating system
Processor
Oracle 10g
Release 2
(10.2.0.5)
IA-32, x64
X [2]
X [2]
IA-32, x64
X [2]
X [2]
IA-32, x64
X [2]
X [2]
SQL
Server
2008 R2
SQL
Server
2008
SP2 [3]
DB2 Universal
Database
(UDB) V9.5
FixPak 6a
DB2
Universal
Database
V9.7 Fix Pak
2
Note: The X symbol denotes the supported combination of operating system and database.
24
Note: The following specific notes indicated by [ ] apply to the Content Server and Business Activity
Monitor environment table:
[1] AIX version 9.0 and version 10.0 C++ runtimes are supported.
[2] eSignature now supports Chinese, Japanese and Korean languages (CJK).
[3] MS SQL server 2008 requires KB956717 patch . Refer to MS knowledge base to obtain the
patch for 32 and 64 bit databases.
Unless otherwise noted:
The following items are not supported for HP-UX with Itanium:
eTrust Siteminder Single Sign-on
eSignature manifestations for Trusted Content Services do not support Adobe PDF 8.0.
The Oracle MAX_COMMIT_PROPAGATION_DELAY has been deprecated in Oracle 10g2 (10.2+)
and higher releases.
Note: The following general notes apply to the Content Server and Business Activity Monitor
environment table:
The following Windows Server 2008 editions are supported: Standard, Enterprise, Data Center.
IA-32 = Intel Architecture 32-bit
x64 = 64-bit Architecture which includes AMD64 and Intel 64. This is related to processor and
not with Windows Server OS (32-bit) mode.
Content Server is a 32-bit application that can run on 32-bit or 64-bit operating systems as
long as that operating system supports 32-bit applications. You do not need to manually set
a compatibility mode. The 64-bit operating system automatically manages Content Server as
a 32-bit application.
The database can be either a local or remote installation. The database can be installed on any
operating system supported by the database vendor, provided the database client can be installed
on the Content Server host. For example, Content Server can be installed on a Windows host and
use a database installed on a Solaris host. When the database is installed remotely, verify that
you can connect to the database by using a database client from the system where you intend to
install Content Server.
A private copy of JBoss web application server is installed. This web application server is required
for LDAP user synchronization, Java Lifecycles, and the ACS server.
XWindows is required for the GUI installer on UNIX operating systems.
Support Microsoft Cluster. The Installation Guide contains more details.
The data partitioning feature of Documentum Archive only supports Oracle and SQL Server
database.
Content Server does not support Oracle instant client.
English, Japanese, Korean and Simplified Chinese versions of the operating system are supported.
Supports Kerberos V5 1.6.3.
Supports VMware vSphere vCenter Server Version 4.1.0 Build 258902, ESX 4.1.0 Build 260247,
and Atmos versions.
25
Operating system
Processor
IA-32, x64
IA-32, x64
IA-32, x64
Note: The following general note applies to the Process Reporting Services client table:
The following Windows Server 2008 editions are supported: Standard, Enterprise, Data Center.
IA-32 = Intel Architecture 32-bit
x64 = 64-bit Architecture which includes AMD64 and Intel 64
Support 32-bit version and 64-bit version of web application server.
VMware support
The following table lists the VMware product versions supported on specific operating system(s).
Table 10. VMware support
Product
Operating system
Processor
VMware Server
IA-32, x64
VMware Workstation
IA-32, x64
N/A
IA-32, x64
Note: The following general notes apply to the VMware support table:
IA-32 = Intel Architecture 32-bit
x64 = 64-bit Architecture which includes AMD64 and Intel 64
26
Documentum fully supports all of our products running on a guest operation system supported
by the version of VMware products listed as long as that same version of operating system
is supported by the appropriate EMC Documentum product. VMware supports only x86
microprocessor architecture.
Supports VMware vSphere vCenter Server Version 4.1.0 Build 258902, ESX 4.1.0 Build 260247,
and Atmos versions.
Product versions
Operating system
Processor
Power
Note: The following specific note indicated by [ ] applies to the IBM Logical Partitioning support table:
[1] LPAR specific tuning, performance guidelines, recommendations, and specific setup issues
would be provided and communicated directly by IBM to the customer. We are currently not
aware of any Documentum specific LPAR setup issues. We expect the customer to perform
relevant use case scenario based pre-production testing on LPAR. This support assumes that
these tests with relevant configurations perform successfully prior to going into production. If
the issue is determined to be related to incompatibility of the LPAR environment, EMC and the
customer will jointly pursue with IBM for resolution.
Product
Operating system
Processor
Solaris 10
UltraSPARC
Solaris
UltraSPARC
27
Citrix support
The following table lists the Citrix product versions supported on specific operating system(s).
Table 13. Citrix support
Product versions
Operating system
Processor
IA-32, x64
IA-32, x64
Note: The following specific note indicated by [ ] applies to the Citrix support table:
[1] Citrix Presentation Server 4.5 FP2 was renamed to XenApp 5.0.
Note: The following general notes apply to the Citrix support table:
IA-32 = Intel Architecture 32-bit
x64 = 64-bit Architecture which includes AMD64 and Intel 64
Siteminder support
eTrust Siteminder Policy Server 6.0 SP6 and eTrust Siteminder Policy Server r12 SP2 are supported
for all supported web application servers and operating systems, except there is no Firefox browser
support. libstdc++-libc6.2-2.so.3 package is required to load netegrity plugin on SUSE Linux 11.
RSA support
RSA Access Manager 6.0.4 is supported for all supported web application servers and operating
systems.
28
Prerequisites to run Documentum versions 6.5 and later in the native 64-bit
mode
You must ensure that your 64-bit environment comprises the following prerequisite components
before you install Documentum 6.5 or later products:
64-bit processor
64-bit operating system
64-bit Java Virtual Machine
64-bit web application server (if needed). Ensure that the web application server is bundled with
64-bit Java Virtual Machine.
IPv6 support
Documentum 6.5 and later supports dual-stack (IPv4 or IPv6) and native IPv4 operations. In addition
to this, Documentum 6.5 and later products which are Java based applications also support native
IPv6 operation. Support for dual-stack operation enables Documentum 6.5 and later products to use
the appropriate protocol (IPv4 or IPv6) when communicating with third-party products and other
Documentum products.
Documentum Foundation Classes determines the operating mode, and by default, DFC is configured
for dual-stack and native IPv6 operation. The Documentum Foundation Classes Installation Guide
provides information on how to configure DFC for native IPv4 operation.
Note: Information on protocol support for third-party products is provided in the third-party
product documentation.
Table 14. Business Activity Monitor IPv6 compliance
Product
Dual-stack
(IPv4 & IPv6)
Native IPv6
X
29
Dual-stack
(IPv4 & IPv6)
Product
Native IPv6
Content Server
Process Builder
Process Integrator
Process Engine
Forms Builder
TaskSpace
Composer
Note: The X symbol denotes the support started with 6.5 release.
Embedded products
Installing EMC Documentum products includes the following additional products.
30
31
32
Chapter 4
Fixed Problems
Within two weeks of the release, EMC will post a list of the fixed problems in the release on the
Powerlink website (http://powerlink.EMC.com).
2.
Select the Search Support tab and then click Advanced Search.
The Search Support page appears.
3.
Under the Search Support heading, click All Support Resources and select Documents from
the list.
4.
5.
6.
7.
8.
Scroll down to see the search results that list the Fixed Bugs documents for each release of the
product.
9.
Fixed Problems
This section identifies problems that have been resolved, which were previously documented in the
release notes as a known problem or limitation. A full list of the fixed problems for this release
can be found in Powerlink.
The following table lists the defect numbers and a description of the problems fixed in BAM 6.7:
Defect #
BAM-2042
33
Fixed Problems
Defect #
BAM-2034
We resolved the problem where if the date format settings of the BAM JDK
were anything but mm/dd/yyyy hh:mi:ss, the formatting of SDT repeating
date values failed. This meant that all new SDT and package attribute values
did not appear in reports.
BAM-2030
BAM-2019
We resolved the issue where Composer 6.6 could not be used to migrate
business data aggregration configurations from older versions to newer
versions of BAM.
BAM-2015
We fixed the problem where reports designed with the Activity Execution
5 minutes report entity and filtered to include only manual activities
(AUT.Manual=True) did not display data.
BAM-2005
BAM-1983
We fixed the problem where the Activate and Deactivate buttons on the
Server Management page in TaskSpace did not refresh properly when
selected.
BAM-1973
We fixed the problem where reports designed with SDTs could not be the
target report in a multi-drill-down report.
BAM-1972,
BAM-1898
The problem where the Process and Activity aggregation jobs and the
Incomplete Process and Incomplete Activity aggregation jobs did not run on
older versions of a process is resolved.
BAM-1969
The issue with report names not having special characters is resolved.
Reports were not displayed correctly in the dashboard and drill-down
reports failed to open. The special characters were &, <, >, ", =. and .
BAM-1961
We fixed the problem where the report preview feature in PRS did not work
if Flash Player was not installed on the PRS machine.
BAM-1952
BAM-1948
We resolved the problem where the BAM purge interval buffer did not allow
for more than 10 weeks of historical process data to be saved.
BAM-1946
We fixed the problem where BAM would miss Audit Trail events when
Content Server transactions took more than one minute to complete.
BAM-1919
We fixed the problem where the following special characters did not work
with single and multi-search filters: % (percent) and _ (underscore).
BAM-1821
34
Fixed Problems
Defect #
BAM-1807
When BAM used a DB2 database, SDT attribute values could not be more
than 256 characters. This issue has been resolved.
BAM-1687
We fixed the problem where data source filters written in a locale different
from the BAM database filtered all results from the report. This occurred
only with a SQL Server BAM database.
BAM-1345
We resolved the problem where the Alert dashlet did not filter properly
when a dashboard user selected either Process ID or Activity ID in a
corresponding multi-drill-down report.
BAM-850
We resolved the problem where the JDBC driver shipped with the supported
version of the DB2 database was not compatible with Oracle application
server version 10.1.3.3.
BAM-123
BAM-119
We fixed the problem where titles in table charts were truncated when the
header font size exceeded 12 points in size.
35
Fixed Problems
36
Chapter 5
Known Problems and Limitations
This chapter identifies problems and limitations that may affect your use of the product.
EMC Documentum makes the latest information about customer-reported issues and known
problems available on the Powerlink website (http://powerlink.EMC.com). You must have a software
support agreement to log in and access the list of issues.
Note: This chapter may refer to platforms or features that are not supported for this release of your
product. Check Chapter 3, Environment and System Requirements to verify requirements.
Known problems
This section describes known problems in EMC Documentum software and documentation that
may affect your use of the product.
The following table lists the known problems for BAM 6.7:
Defect #
BAM-4955
If you are upgrading to version 6.7, ask for Technical Support for assistance.
When upgrading from BAM version 6.6 (or earlier) to 6.7 string type data is
lost and cannot be used in reports.
BAM-4149
BAM filters that return a large number of results can consume high database
CPU resources. The issue stems from a BAM filter mechanism that uses a
nested IN clause. To work around this issue:
Do not frequently run reports containing more than 10,000 records.
Modify the filter to return a small subset of results. Date filters in
particular are useful in paring down results.
Use aggregation, where appriopriate.
BAM-3627
BAM-2837
37
Defect #
BAM-2121
BAM-2093
PRS and the BAM server can be installed in different time zones. When this
happens, the report preview in PRS and the data set preview in PRS display
different times when either the Start Date and Time or the Finished Date
and Time entity fields are included in a report. The report preview displays
the time in the time zone in which the BAM server is installed; the data set
preview displays the time in the time zone in which PRS is installed. This
happens because the data displayed in the report preview is formatted by
the BAM server, whereas the data displayed in the data set preview does
not pass through the BAM server, and uses the locale of PRS.
BAM-2022
Filter expressions containing more than 2083 characters filter all data out
of a report. This problem is limited to Internet Explorer 7 only, and is not
experienced on other browsers (FireFox, Safari, Opera). This is a limitation
of the browser and not BAM.
BAM-1968
BPM-1842
Form template names and form field names that have a special character,
such as an ampersand (&) or single quotation mark, result in malformed
XML that is generated for reporting. Due to the malformed XML, BAM
cannot consume the reporting data for packages that are forms. The problem
only occurs if the form with the special characters is used in a package and
marked for reporting in BAM.
BAM-1648
PRS displays an entity not found error message when a report is saved for the
first time and all of the following conditions occur:
The report is designed with an SDT.
The report is not saved.
The SDT used in the report is modified and saved in Process Builder.
After the error message PRS users see an empty SDT entity added to the
report. The report entity must be removed from the report, and then added
again.
38
Defect #
BAM-1548
Mandatory filters in a dashboard do not work when they are designed in one
locale and then used in another locale. If a mandatory filter is configured by
a dashboard designer in an English locale, then all dashboard users must
also select English in order for the mandatory filters to work.
BAM-195
The BAM piping process fails to restart when the connection to the
Documentum Server is lost. If the Documentum Server is down for any
period of time, and then restarted, the BAM pipe process is stuck on the time
of when the connection was lost even though the Documentum Server is up
and running. To work around this issue you must restart the BAM server.
Limitations
This section describes limits on the usability of current functionality. The limitations may be part of
the product design or may result from issues with associated third-party products.
The following table lists the known limitations for BAM 6.7:
Defect #
Description of limitations
BAM-4017
Crystal Report parameter fields are not supported in PRS. The mandatory
filters feature of a BAM dashboard provides a similar capability.
BAM-3997
All custom aggregations for certain time intervals are executed in a single
transaction by the BAM server. If two daily custom aggregations are
defined, they are associated with single scheduler job called AggrCustomD.
The scheduled job executes all aggregations in a single database transaction.
Before exiting, each job updates the LAST_PIPE_RUN timestamp in the
BAM database. This timestamp update allows the job to run the next time it
is scheduled. If an issue occurs (for example, there may be incorrect syntax,
data integrity violation or database lock), the LAST_PIPE RUN timestamp is
not entered and the entire AggrCustomD job stops working.
For a solution to this problem, please refer to this post on the EMC
Community Network.
BAM-3912
39
Defect #
Description of limitations
BAM-3787
BAM-1897
1.
Restart PRS.
2.
3.
Change the state of the alert from Published to Draft, and save the alert.
4.
Change the state of the alert from Draft to Published, and save the alert.
BAM-1804
BAM-1686
PRS can be used to export report definitions from a repository. PRS can
also be used to import report definitions into a repository. PRS users might
expect that an export of a parent drill-down report would also include
all children report definitions. But this does not happen. When a single
or multi-drill-down parent report is exported, children reports are not
automatically included and must be exported separately.
A work around also applies to importing drill-down reports. When a parent
drill-down report is imported before the children reports, PRS displays an
Exception error message. Exceptions are generated when report definitions
reference another report that is not yet in the repository. As a work around,
all children reports must be imported first, followed by the parent.
Note: Exporting and importing reports using PRS is a deprecated, but still
supported, feature. Documentum Composer is the correct product to use for
moving reports between repositories.
40
Defect #
Description of limitations
BAM-1505
BAM cannot monitor SDTs and packages that have the same name. If a SDT
and package have the same name, then the tables in the BAM database that
hold the SDT and package data become corrupt and data is lost. This is
because the BAM database cannot have two business data tables with the
same name. When SDT and package names are unique, then a unique set of
tables in the BAM database holds execution data. But when another SDT or
package with the same name is synchronized with the BAM database the
existing table (and all execution data) is dropped from the BAM database.
Lost execution data cannot be recovered.
To work around this problem you must:
BAM-86
1.
2.
3.
If a user navigates between two or more open reports in PRS, the results
displayed in the Data Source Preview window disappear from view. This
happens because PRS does not cash result sets prior to displaying the
selected report. As a work around, click the Refresh button in the Data
Source Preview window.
41
Oracle script
Connect to SQL/PLUS: SQL>Conn user/password@database_name_alias.
create or replace
FUNCTION
GetAttributeColumnName (entity in
varchar2 , attribute1 in varchar2 )
RETURN varchar2
IS output VARCHAR2(30);
BEGIN
select
FIELD_COLUMN_NAME INTO output
from
DEF_SDT_FIELDS
WHERE
FIELD_NAME = attribute1
AND
SDT_NAME = entity;
RETURN(output);
END;
/
--set serveroutput on
BEGIN
--Select all SDTs into a cursor.
FOR sdt_cursor IN (SELECT sdt_name,n_name, table_name
FROM def_sdt_tables)
LOOP
DECLARE create_view VARCHAR2(32767);
fields_count NUMBER;
BEGIN
--For each SDT start creating a CREATE VIEW statement
create_view := CREATE or REPLACE VIEW V_ ||
SUBSTR(sdt_cursor.table_name,1,28) || AS SELECT ;
--Select all fields for SDT into a cursor.
SELECT count(*) into fields_count FROM def_sdt_fields
where field_table = sdt_cursor.table_name;
DECLARE CURSOR field_cursor IS
SELECT field_name, field_column_name FROM def_sdt_fields
where field_table = sdt_cursor.table_name;
BEGIN
FOR current_field in field_cursor
LOOP
create_view := create_view || current_field.field_column_name
|| "|| current_field.field_name ||" ;
--DBMS_OUTPUT.PUT_LINE(current_field.field_column_name || ||
field_cursor%ROWCOUNT );
IF field_cursor%ROWCOUNT < fields_count THEN
create_view := create_view || ,;
END IF;
END LOOP;
END;
--execute the create view for SDT.
create_view := create_view || FROM || sdt_cursor.table_name;
-- No fields from SDT, exit this itration and dont run View creation.
IF fields_count > 0 THEN
EXECUTE IMMEDIATE create_view;
42
END IF;
--dbms_output.put_line(create_view);
--EXECUTE IMMEDIATE create_view;
END;
END LOOP;
END;
/
varchar(30), @table_name
varchar(30)
OPEN sdt_cursor;
FETCH NEXT FROM sdt_cursor
INTO @sdt_name,@n_name, @table_name
WHILE @@FETCH_STATUS = 0
BEGIN
substring(@table_name,1,28)
43
+ AS SELECT ;
DECLARE @fields_count INT
--Count the number of fields for this SDT.
SET @fields_count = (SELECT count(*) FROM DEF_SDT_FIELDS
FIELD_TABLE = @table_name)
where
varchar(30)
OPEN field_cursor;
FETCH NEXT FROM field_cursor
INTO @field_name, @field_column_name
WHILE @@FETCH_STATUS = 0
BEGIN
SET @create_view = @create_view + @field_column_name + AS " +
@field_name + "
FETCH NEXT FROM field_cursor
INTO @field_name, @field_column_name
IF @@FETCH_STATUS = 0
BEGIN
SET @create_view = @create_view + ,
END;
END;
CLOSE field_cursor;
DEALLOCATE field_cursor;
IF (@fields_count>0)
BEGIN
--PRINT (@drop_view);
EXEC (@drop_view);
SET @create_view = @create_view + FROM +@table_name
--PRINT (@create_view);
EXEC (@create_view);
END;
FETCH NEXT FROM sdt_cursor
INTO @sdt_name,@n_name, @table_name
END;
CLOSE sdt_cursor;
DEALLOCATE sdt_cursor;
44
go
45
46
Chapter 6
Technical Notes
This section provides configuration and usability notes for current product features.
Note: This chapter may refer to platforms or features that are not supported for this release of your
product.
The Understanding when to use Simple reports and Crystal Reports section of the Designing Reports
with Process Reporting Services chapter is updated.
47
Technical Notes
48