IBM Maximo Asset Management

Version 7.1 SAP Business Objects Crystal Reports

Copyright International Business Machines 2011

Overview
In Version 7.1, an IBM Report Integration is available to the SAP Business Objects XI Product
Suite (BO) . The integration enables users to see and execute BO reports within the V7.1 instance.
This document will detail the various components of the V7.1 BO Integration including
1. Overview of Business Objects XI Product Suite
2. Licensing
3. Accessing Reports
4. Integrating V7.1 to work with Business Objects
5. Adding Reports to Central Management Console
6. Registering Reports to V7.1 Report Administration Application
7. Report Parameters
8. Developing V7.1 Reports
9. Enabling Sub Reports for V7.1 Integration
10. Upgrading from Previous Versions
11. Integration Properties

1. Overview of BusinessObjects XI Product Suite Overview

The V7.1 integration requires BusinessObjects Enterprise XI Release 2, Service Pack 2 Release. The
following components are required to enable this in V7.1:

Business Objects Enterprise Server, including the

- Central Management Console (CMC)
- Web Component Adapter

Notes:
A. Crystal Reports XI is also required for report design.
B. An application server separate from the V7.1 application server is required. The integration
component runs as a web application on this server, as do several Business Objects applications. The
BO Enterprise Server includes an optional install of Tomcat. It is recommended that Tomcat be used
for the integration.
C. For best performance, IBM recommends that your configuration contains the following dedicated
servers:

V7.1 Application server

BusinessObjects Enterprise server (The BO/Tomcat Application Server may be installed on
this Server.)
Database server

D. When you integrate V7.1 to run with BO, you are responsible for using products that BO and V7.1
support. The specific product platforms that BO runs on can vary from those of Version 7.1.

1. Licensing
IBM does not provide you with any Business Objects or Crystal licenses and does not support any
specific Business Objects or Crystal issues. You must purchase and maintain your Crystal license
separately with Business Objects.
IBM developed this V7.1 integration using a Processor based license. Therefore, all BO reports that
you run through this integration execute against a single, name user account. Optional Crystal
Licenses are available, including Named User Licenses. If you encounter any integration licensing
conflicts, you must resolve the issue separately with Business Objects.

3. Accessing Reports from V7.1

End users will access BO Reports in the same way that they access other reports within V7.1. This is
by
a. Selecting the Run Report action within an application

b. Or via the Reports Menu.

2. A listing of available BO Reports will then be visible in the On Demand Reports subtab of the
Reporting Window.
3. Once the user submits his report request, the BO Report will be displayed in a separate BO
browser session.
4. The integration enables BO Reports that use either the Current/Selected Record Set or
Bound Parameters.

5. For the V7.1 Release, three Out of the Box reports will be delivered. These are
a. Job Plan List Report, jobplan.rpt
b. PO List Report, po.rpt and
c. PO Details report, poprint.rpt
These reports are located in <V7.1>\applications\bocrystal\reports
V7.1 BO Job Plan List report displayed in BO Browser

4. Integrating V7.1 with Business Objects

This section describes how V7.1 integrates with the BO Crystal Web Application (bocrystal.war) and
how to integrate with your Business Object Enterprise Server.
A top level description of the BO/Crystal Maximo Integration is detailed below. When a BO report is
requested from Maximo, Maximo submits a form post to the bocrystal web application, and includes
as parameters all of the information needed to execute the report. Some of this information is used
by the BO Enterprise server (for example, logon and locale info, the name of the report), and some is
passed to the report through parameters (for example the Maximo where clause). The work of
retrieving and executing the report is done within the webapp using three separate BO SDKs:
Enterprise, RAS, and Viewers. The SDKs enable communication with the BO services running on the
BO Enterprise server.
To enable this integration, BO is deployed as a separate war file on the Business Objects Enterprise
Server. Its main components include the V7.1 BO Integration, and the Crystal API and Viewer
Libraries.
The BO directory <V7.1>\applications\bocrystal contains the following folders:
Folder Name
(main level directory)
Bofiles
META-INF
Properties
Reports
WEB-INF

Contents
JSP files including error.jsp, interactiveViewer.jsp,
runBOCrystalReport.jsp, and utilities.jsp
Folder you use to copy files from your Business Objects Enterprise
Application
Information about Manifest and Apache Software Versions
V7.1 Error messages you may see when using Crystal
Sample Job Plan List Report
web.xml and class files

NOTE: To enable the integration, you must edit the properties in the System Properties application
to successfully complete this integration. Information on these property files are contained at the
end of this document.

To integrate V7.1 to work with BO, complete the following sections in order.
A. Copy BusinessObjects Enterprise server files to the V7.1 Application Server
B. Build bocrystal.war
C. Deploy bocrystal.war

A. Copy Business Objects Enterprise Server files to the V7.1 Application Server
1.

On your BusinessObjects Enterprise server, go to the location where you installed

BusinessObjects Enterprise. If you chose the default location, BusinessObjects Enterprise is
located in the following directory:
Program Files\Business Objects directory

2. Copy the following folder:

For Windows: <BusinessObjects Enterprise Root>\common\3.5\java\lib
For Unix: <BusinessObjects Enterprise Root>/java/lib
NOTE : If the V7.1 Application server has disk space or network limitations, you can omit the
following two files:
Inventory.xml
Log.txt
3. Paste the lib folder to the following location on the V7.1 Application server:
<V7.1>\maximo\applications\bocrystal\bofiles
4. Return to the Business Objects Enterprise server and copy the following folder.
For Windows:
<BusinessObjects Enterprise Root>\common\3.5\crystalreportviewers115
For Unix:
<BusinessObjectsEnterpriseRoot>/enterprise115/JavaSDK/crystaleportviewers115
NOTE: If the V7.1 Application server has disk space or network limitations, you can omit the
following two subfolders:
Javaplugin
Offline
5. Paste the crystalreportviewers115 folder to the following location on the V7.1 Application
server:
<V7.1>\maximo\applications\bocrystal\bofiles

B. Build bocrystal.war
1. On the V7.1 Application server, open a command prompt.
2. Change the directory to the following location
<V7.1>\maximo\deployment
3. Type buildbocrystalwar.cmd and press Enter. After V7.1 successfully completes the command,
close the command prompt window.

C. Deploy bocrystal.war
The bocrystal.war file needs to be deployed on the Business Objects Enterprise Application
server. To deploy the file, consult the application server documentation. The bocrystal.war file
resides in the following location:
<V7.1>\maximo\deployment\default

Note: If you update your BusinessObjects Enterprise server, you must repeat the steps
described in this chapter so that the server and the bocrystal.war file remain at the same
revision level.

5. Adding Reports to Central Management Console

This section describes how the administrator can use BusinssObject XIs Central Management
Console (CMC) to perform the following tasks:

Creating the report folder structure

Adding a new report
Setting security privileges

Creating your Report Folder Structure

The report structure enables V7.1 to locate the .rpt files within the BO Server. This section
describes how to create a folder structure for V7.1 reports in the CMC. You must create your Report
Folder structure before you register any reports. To do this, complete the following steps.
1. Log on to the CMC as the Report Administrator

10

2. On the CMC home page, click Folders to open your report folder structure.

3. Next, create a report structure in the following format:

A top level-rpt folder

o A subfolder for each V7.1 application that you have Reports for. (ex. JOBPLAN).
This subfolder must match the name of the Report Folder field.

A reports subfolder beneath each application folder. This is where your
crystal report (.rpt) files will be placed.

Example
rpt
JOBPLAN
Reports
Job Plan Crystal Report 1.rpt
Job Plan Crystal Report 2.rpt
LABOR
Reports
SECURGROUP
Reports

11

Adding a New Report

Each report must be registered in the CMC (and in the V7.1 Report Administration application). This
section details how to register the sample report delivered with the V7.1 Integration (jobplan.rpt) in
the CMC.
a.

Open the CMC and navigate to the following folder:

Rpt>JOBPLAN>reports

b. Click the Objects tab

c. To open the New Object window, select New Objects . . .
d. To locate the folder that contains the report file, click Browse. . .
Note: This sample report is located in:

<V7.1>\Applications\bocrystal\reports

e. Click OK to open the Properties tab.

f. In the Report Title field, enter the filename for the report.
Note:
The filename you enter must have an .rpt suffix for the report to run correctly. The filename
must also match the value you entered in the Report File Name field in V7.1 Report
Administration so that V7.1 can locate the requested report.
g.

Click Update to save your updated report title to the Central Management Console.

12

Setting Security Privileges

For your V7.1 users to run BO reports you must establish security for one BO user through the CMC.
When a V7.1 user runs a BO report, they silently log in to BO through this single, named user account.
The following section describes how to grant Edit Objects privileges, at the rpt folder level, for your
users via a single named user account.
Note:

By setting the Edit Objects option to explicitly granted, you are providing the minimum level
of rights required for the V7.1 Integration with BO. You should determine if any additional
rights need to be granted to your users.

The following instructions explain how to set security privileges in the CMC for user MXES.
1. Log on to the CMC as the Administrator. The CMC Home Page appears. To open the Top Level
Folders dialog box, click Folders.

2. To display the subfolders for the rpt folder, click rpt.

13

3. Click the Rights subtab. For existing user MXES, go to the Access Level dialog box and select View
on Demand. To add rights for a new user, create that user and return to this subtab.

4. To submit the change to the server, click Update

5. For existing user MXES go to the Access Level drop-down list and select Advanced . . . to open the
Advanced Rights dialog box.

6. Change the Edit Objects option from Not Specified to Explicitly Granted. To accept this change
and refresh the page, click Apply.
7. To return to the Rights sub tab, click OK.

14

15

6. Registering Reports to V7.1 Report Administration Application

BO Reports must also be registered to the V7.1 Database using the Report Administration
Application. This enables the BO Reports to be visible within V7.1.
a. A report type of CRYSTAL is used to identify the Crystal Reports in the Database.
b. After registering the BO Report, the Administrator must use the Create XML
functionality to generate the reports Request page.
After registering the report and creating the XML, the security for this report needs to be granted.
In V7.1, security can be granted at
(1)
For All Reports
(2)
For All Reports within a specific Application or
(3)
For an Individual Report

To set report security at the report level, access the report in Report Admin. Click on the Security
Tab, and add the Security Group(s) who can run that specific report. Only those Security Groups who
have Run Report Security Group Access to the Application will be available for selection.

16

To set report security at the application level (meaning the group can see ALL reports registered to
that specific application), access Report Admin. From the Action Menu, click Set Application
Security. Select the Application, and then choose the Security Group(s) who should have access.
Additionally, you can grant report app security to all Report Types, or to specific report types like
Crystal or Custom.

NOTE: Setting Report Security for All Reports is enabled via similar functionality.

17

7. Report Parameters
BO Reports in the V7.1 Integration can use two types of parameters. The first is the
Current/Selected Record Set and the second is Bound Parameters.
Unbound parameters those that do not have relationships with the V7.1 database are not supported
for the BO Integration. More information on these types of parameters is detailed below.
Description

Unique Characteristics

Current/Selected
Record Set

Passes the Current/Selected

Does not display on report's request page
Record Set from the Maximo
Application to the Report.
This saves the user multiple
steps as he does not have to reinput his query.

Bound User
Inputted Parameter

Exist in the main table of the

application that the report is
registered to - or exists
via a maxrelationship that has
been set up for the application.
Bound parameters are
appended to the V7.1 Where
Clause.

End users typically will not now if

parameters bound or unbound. However,
they are visible to report admin as the
Attribute Value will be populated.

18

More details on Bound versus Unbound parameters are contained in the chart below.
Bound

Unbound

Parameter Name

Can be - but does not have to be - defined in Must be defined in report's design
report's design file
file

Attribute Name

ALWAYS Populated

NEVER Populated

Lookup Name

Can be populated or not

Can only be used for unbound dates

(Date Lookup)

Operator (<, >, =)

Optional

NEVER Populated

Multi-Lookup
Enabled?

Yes or No

Yes or No

Display Sequence

Numeric Value

Numeric Value

Override Label

Any Text

Any Text

Default Value

Can be populated or not

Can be populated or not

Required?

Yes or No

Yes or No

19

8. Developing V7.1 Reports

This section details using command tables to create V7.1 reports. Command tables are required for
V7.1 to pass the where clause from the V7.1 applications to BO properly.
The BO Reports used in the V7.1 Integration can only contain a single command table.
If you try to use both command tables with a combination of database tables, the report will fail
because V7.1 only updates the database connection for one command table.
Additionally, BO does not recommend using command tables in combination with database tables. This
is a Business Objects/Crystal Issue, and leads to report performance being slower than expected.
This occurs because command objects have custom SQL statements. When a command object is
linked to a table or is linked to another command object, two separate SQL statements are executed
on the server. However, the linking is not done on the server.
All the records from both SQL statements are returned to the Crystal Reports Designer. In addition,
the join between the command object and tables or the join between the two command objects is
performed locally in the Report Designer. These behaviors affect the performance of the report.
To improve the report performance, do not generate a link between the command objects and the
tables in Crystal Reports. Instead, use one of the following methods:
- Modify the command object to use the table within its custom SQL Statement.
- Create a stored procedure that creates a link between multiple SQL Statements on the server and
then returns a single result set to Crystal Reports.

20

Below are steps in how to create a BO report using command tables.

1. Open the BO Reports start page

2. Click Blank Report to open your database in the Database Expert dialog box.
Note: Oracle reports use an Oracle connection, while DB2 and SQL Server reports use an
ODBC connection.

21

The following figures show both types of database dialog boxes.

Database Expert Dialog Box (Oracle database)

Database Expert Dialog Box (DB2 and SQL Server database)

Note: The remaining screenshots are for an Oracle database only.

22

3. Double-click Add Command (below the server name) to open the Add Command to Report dialog
box.

Note: As noted earlier in this section, you must use the Command Table editor for this integration.
You cannot create reports by selecting individual tables to include in your BO report.

23

4. A blank dialog will display in the Add Command to Report Dialog. For this example, type the
following SQL query in the Enter SQL query in the box below field.
select po.ponum,po.description,po.vendor,
companies. name,
po.requireddate, po.vendeliverydate,
po.purchaseagent,
po.status,po.mnetsent
from po, companies,
where po.orgid = companies.orgid
and po.vendor = companies.company

24

5. In the next steps, you will define a parameter required for this integration. To do this, open the
Command Parameter dialog box, and click Create
6. In the Parameter Name field, type where as shown below.
7. Click OK to return to the Add Command to Report dialog box.

25

8. Place your cursor at the end of the SQL query. Type and (as shown), then double click where in
the Parameter List dialog box to place the parameter at the end of the SQL query.
After completing this step, your SQL query statement should look like
statement in the following figure.

the SQL query

Note: If your original SQL statement does not include a where clause, you must insert the
where parameter at the end of the statement as shown in the example below.
select po.ponum, po.description, po.vendor, po.requireddate,
po.vendeliverydate, po.purhcaseagent, po.status, po.mnetsent from po
where (?where)

26

Note: If you use an Oracle database, as in this example, you must also add a schema parameter
before each table name. To do this, follow steps A thru H below.
A. Click Create, to open the Command Parameter dialog box. click Create.
B. In the Parameter Name field, type SCHEMA.
C. To return to the Add Command to Report dialog box, click OK.
D. Place your cursor before each table name (po and companies) on the From line and double-click the
schema parameter in the Parameter List to add it to the SQL query.
E. Add a period (.) between the schema parameter and each table name
After completing this step, your SQL query statement should look like the SQL query statement
below.

F. Click OK to open the Enter Values dialog box. Enter values for each of the parameters in the
Parameter list.
1 In the Schema field, enter the owner of the database schema
2 In the Where field, type 1=1.
G. To accept these values, click OK. BO reopens the Database Expert dialog box.
H. To return to the report, click OK

27

28

9. To open a list of database fields selected for your report (as determined by your SQL statement),
select View> Field Explorer.

10.
Drag database fields from Field Explorer to the Details section of your report. As you do so,
each field appears in the Page Header section.

29

11. To see how your completed report appears, click Preview.

12. Edit the report as needed. To save your report, select File> Save.

30

9. Enabling SubReports for V7.1 Integration

This section describes how to create BO Subreports for the V7.1 integration. When you include a
subreport in a report against an Oracle database, you must pass the schema name from the main
report to the subreport.
Note: These steps are not necessary if your are working in a Microsoft SQL Server database.
In the following instructions, you work with a Purchase Order Details report that contains a
subreport for Purchase Order Line information. The main report must pass the database schema
name to the subreport.
To enable the V7.1 integration, complete the following steps.
1 Open the Purchase Order Details report.
2 Open the SQL Query for the subreport and create a new parameter called subschema. The
new parameter accepts the schema from the main report when you generate the sub report.

31

3 Open the Subreport Links dialog box in the Purchase Order Details Report to connect the
new subschema parameter to the schema in the main report.
Note In the Subreport parameter field to use drop-down list, you must select the
subSchema parameter.

32

10. Upgrading from Previous Versions

The following is an overview of the changes required to upgrade your Crystal Integration from the
previous version of Maximo 6.
1.

Upgrade your BusinessObjects Enterprise install to Release 2, Service Pack 2.

2.
You do not need to upgrade the BusinessObjects application server. However, you must
configure the application server to use Java 1.5. If you are using Tomcat, there are instructions on
how to do this in the BusinessObjects Enterprise XI Release 2 Installation Guide, in Appendix B,
"Deploying on Tomcat with the JDK 1.5".
3.
Copy the new BusinessObjects files to your application server as described in Section 4 of
this document, and rebuild bocrystal.war.

33

11. Integration Properties

The following table lists the database properties used in the Business Objects XI Product Suite
Integration. Use the System Properties Application to set values for each one.
Property Name
mxe.report.bo.db.connnectstring

mxe.report.bo.db.databaseName
(SQL Server and DB2 only)
mxe.report.bo.serverURL

mxe.report.bo.rootFolder

mxe.report.bo.rptServerLogonName

mxe.report.bo.rptServerLogonPass
mxe.report.bo.cmsName

Description
The V7.1 database connection string (Oracle) or ODBC DSN
(SQL Server and DB2) defined on the BusinessObjects
Enterprise server.
The database name for the V7.1 database.
The URL of the BusinessObjects Enterprise server, including
port number and folder. V7.1 uses this URL to access the
bocrystal.war Web application.
Example: http://BOSERVER:8080/bocrystal
The BusinessObjects Enterprise root folder name. This should
be rpt unless you used another value in step 3 under Adding
Reports to Central Management Console above.
The BusinessObjects Enterprise logon name. This user must
have specific rights to any report you will access from Maximo.
See Setting Security Privileges in this document.
The BusinessObjects Enterprise password.
Unless you changed the name of the Central Management
Server (CMS) when you installed BusinessObjects Enterprise,
this property is the name of the server where you installed
BusinessObjects Enterprise and the server port number,
separated by a colon. To verify the correct values, open the
CMC Logon page and check the System field.
Example: BOSERVER:6400.

34

Miscellaneous: Report Functionality Not Enabled or Supported

The table below details the report features in V7.1 that are not enabled or supported with the BO
integration:
BO Features Not Enabled or Supported
Feature
Description
Licensing
Multi Server
Configurations
Report Browser
Hyperlinks

IBM does not include a BusinessObjects/Crystal License

IBM will not support configurations of multiple servers to one BO
Enterprise Server
No customization of the Report Browser will be done to mimic the UI and
functionality of the V7.1 Release.
Report Hyperlinks from one BO Report to another

V7.1 Reporting Functionality Not Enabled or Supported

View Reports
Previously executed BO reports are not retained, and will not be available
for display in V7.1
Schedule Reports
Scheduling of BO Reports via the Report Request Page. This functionality
is hidden for BO Report Types.
Email Reports
Emailing of BO Reports via the Report Request Page. This functionality is
hidden for BO Report Types.
Unbound Parameter An unbound parameter is a parameter that has no relationship to the
Reports
applications main table or maxrelationships.
Application Toolbar Direct Access to BO Reports from the toolbar in the various applications,
Access
either via Browser View, Direct Print or Direct Print with Attachments
Print Attached
Not enabled for BO Reports
Documents
Report Label
The visibility and ability to update report titles and labels via Report
Features
Admin is not available
Priorities
Administrators can input values for priorities for BO Reports. However,
the V7.1 Integration will not use this functionality it will be up to the
client to extend this functionality if needed.

35

Additional References
The following lists additional references available at the time this guide was prepared. To locate
these documents, perform a search on IBMs Support Site on the report title highlighted below, or on
its support reference number directly next to the title.
IBMs support site can be found at this url:
http://www-947.ibm.com/support/entry/portal/Overview/Software/Tivoli/Maximo_Asset_Management

Additionally, the url's below are available with the additional information including blogs,
forums and a wiki site
https://www.ibm.com/developerworks/servicemanagement/am/index.html

https://www.ibm.com/developerworks/wikis/display/maximo/Home

36

Title
V7 Report Feature Guide

Reference Number
1305020

V7 Report Booklet

1305005

V7 QBR Ad Hoc Reporting

141.417 (7.1.1.6+)
136800 (Pre 7.1.1.6)

Designing V7 Reports

1305009

V7 Report Planning Guide

1421371

V7 Report Performance

1305031

Enabling secondary Database

Configuration for BIRT
reports

1304936

Report Developers Guides

Report Development
Configuration and Download
Report Development Guide

Customizing out of the box

BIRT reports

1390372 (7.1.1.5+)
1315837 (Pre 7.1.1.5)
1447958

1438532

Description
Details how the embedded report engine is utilized, including
a review of the file structure, installation and database
structure. Includes information on Security, Scheduling,
Administration, Queuing, and Property Files.
Contains listings, file names, descriptions, details on
parameters, formatting (grouping, sorting) and a pdf copy of
each of the OOB (Out of the Box) Delivered Reports.
Details how users can Create and Execute Ad Hoc Reports,
and the Administrative setup work involved in enabling Ad
Hoc Reports, including security features and creating Report
Object Structures.
Clients often require custom reports to communicate their
individual business needs. This reviews the data analysis
options available, including KPIs, Application List Downloads,
QBR and Reports. Details report templates available,
parameter options and a variety of items to consider when
designing reports
Reviews each of the data analysis options available in V7,
including a detailed review of each report option.
Details various administration and configuration
recommendations to optimize report performance. This
includes BIRT Report Only Server (BROS) Configurations,
along with Clustering.
Describes additional ways of configuring your database for
reporting, including enabling (1) All reports to execute
against a reporting database or (2) A portion of the reports
to execute against the reporting database.

Contains the designer download link, along with additional

details on installing and configuring it.
Intended for the Report Developer, contains detailed
information and examples on developing reports within
Design Tool, database access, parameters, common
development techniques like hyperlinks and date formats and
various debug features and utilties.
Details how to customize out of the box BIRT reports by
deleting and adding new fields. The Work Order Details
report is used as an example to step you through this
process

37

Report Logging

1423974

V7 Report Update Utility

1433106

V7 Report Toolbar Access

Direct Print and Related
Information

1370440

Enabling barcodes in BIRT

Reports
Changing logos in BIRT
reports
Adding username to a V7
BIRT report
V7 BIRT Page Information

1304925

1317577

Misc Guides
Upgrading to BIRT 232 in V7

1390274

1304923
1403958

System Administration Guide

Report Integration Guides

Maximo Cognos Integration
Installation Guide
Maximo Cognos Integration
Guide

Business Objects/Crystal
Report Integration Guide

Explains the report logging features available to report

developers and administrators. Includes features available
to report developers within the BIRT report designer, and
then reviews the features available to report developers and
administrators from within the V7 applications.
Details report update utilities which can be used to automate
the process of applying updates to report designs, rather
than manually editing each report.
Describes functionality that can be configured with BIRT
Reports to enable their quick display, including Browser View,
Direct Print and Direct Print with Attachments. Details
report requirements, property files and troubleshooting
techniques.
Details how to implement bar code fonts for use within BIRT
reports.
Discusses how you can change the logos displayed within the
V7 reports to your unique company logos.
Provides instructions on adding the username who executed
report to the reports header section
This document reviews the components impacting report
page sizes and orientation used in the V7 BIRT Reports. It
also details how you can customize them to meet your
individual business needs.
Discusses the enhancements enabled in BIRT 2.3.2, along
with report considerations when upgrading your custom
reports from BIRT 2.1.2 to 2.3.2.
Reference this guide for additional information on
Localization, using the TDT and XLIFF files, along with
Advanced Server Configuration details in the System
Configuration Chapter.

1421365
1421312

1303812

Provides steps for enabling the report integration, including

enabling the creation of the meta data layer.
Details on how the report integration works between the two
systems, including publishing report object structures as
Cognos packages, security group synchronization and report
file creation.
For the Version 7.1x releases, contains information on the
Business Objects Enterprise XI Release 2, Service Pack 2
Release reporting integration. Details its (1) Licensing
Requirements (2) Integration and (3) Development of
reports.

38

ERI (External Report

Integration) Guide

1304916

The ERI enables clients to integrate essentially any

reporting tool with V7. This integration is similar to the
Business Objects/Crystal Integration, except it is report
system and report version independent. This document
includes the ERI (1) Requirements (2) Installation (3)
Administration and (4) FAQs.

39

Accessing the Report Support Guides

You can access these guides by following the steps below:
1. Access IBMs support site at the URL below:
http://www-947.ibm.com/support/entry/portal/Overview/Software/Tivoli/Maximo_Asset_Management

2. Input the reference number or the document title from the charts below

3. This leads to the page below. Find the specific guide from the list and click on it.
*Note: Many of the report documents have a key in front of them. This indicates that you must
first sign in to IBM support before downloading.

40

4. After clicking on the name, it brings you to the IBM support log in page. Sign in with your
username and password. If you do not have an IBM support username and password, click on the
register now link highlighted by the top arrow.

5. After you have signed in, you will be brought to the page where the document can be downloaded.

41

Revision History
Revision 2 Updated Reference Documents, Updated References to 7.1x
Revision 1 February 2011 - Updates include (1) Addition of Overview Section (2) Reordering of
sections

42

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local
IBM representative for information on the products and services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may
be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property
right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing,
to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such provisions are
inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without
notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner
serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any
obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy
of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of nonIBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as
completely as possible, the examples include the names of individuals, companies, brands, and products. All of these
names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely
coincidental.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp.,
registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other

43

companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at
www.ibm.com/legal/copytrade.shtml.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United
States, other countries, or both

44