Documente Academic
Documente Profesional
Documente Cultură
Administrator's Guide
Third-party Business Objects products in this release may contain redistributions of software
Contributors licensed from third-party contributors. Some of these individual components may
also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required
notices, can be found at: http://www.businessobjects.com/thirdparty
Contents
Chapter 1 Welcome to the Data Source Migration Wizard 7
About this guide...........................................................................................8
What is the Data Source Migration Wizard?..........................................8
Chapter 6 Troubleshooting 47
Understanding the log file..........................................................................48
INFO messages...................................................................................49
ERROR messages...............................................................................50
WARNING messages...........................................................................54
Index 59
1
1 Welcome to the Data Source Migration Wizard
About this guide
The Data Source Migration Wizard allows you to migrate reports that are
based on Crystal queries, dictionaries, and InfoViews to a BusinessObjects
Enterprise deployment. By migrating your reports, you can take advantage
of the new features that are offered by BusinessObjects Enterprise while
maintaining the functionality of the reports and data sources from your Info
installation.
2
2 Architecture and Requirements
Overview
This section provides information about the components that are involved
when you use the Data Source Migration Wizard to migrate your files. It lists
the requirements of each component, and then describes the interaction that
occurs between the components during the migration process.
Overview
The Data Source Migration Wizard allows you to migrate reports that are
based on Crystal queries, dictionaries, or InfoViews, to a BusinessObjects
Enterprise deployment.
You migrate two types of objects: reports and data sources. The wizard
converts the data source of each report into an object that is usable in
BusinessObjects Enterprise, and then resets the data source location of the
report to point to the new object. The result is that you are able to make use
of the new features of BusinessObjects Enterprise, while keeping the
functionality of the reports and data sources from your Info installation.
Component architecture
The process of migrating your reports and your report data sources to
BusinessObjects Enterprise involves three component groups: the source
files, the migration wizard, and the target files.
Source files
Source files are the reports and the report data sources that you want to
migrate to BusinessObjects Enterprise. They are objects that exist within
your current system and are used in your Info deployment.
Typically, each report has a corresponding data source object. When you
choose to migrate a report, you select its data source for migration as well.
The wizard migrates both files concurrently.
Reports
The reports are standard .rpt files that are based on Crystal queries,
dictionaries, or InfoViews. By default, the wizard migrates only those reports
that are based on these data sources; it bypasses any reports that are based
on other sources.
Data sources
Three types of data sources act as source files for the migration wizard:
queries, dictionaries, and InfoViews. The wizard converts these objects into
data source types that can be used in BusinessObjects Enterprise.
To migrate your source files, you need access to the reports and data sources
that you want to migrate. Before you run the wizard, make sure that you have
the necessary rights to access the locations where all of these objects are
stored.
Migration wizard
Use the Data Source Migration Wizard to migrate your source files to
BusinessObjects Enterprise. Note that the wizard overwrite your files; it
creates copies of the original files, converts the copies, and saves the
migrated copies in a new location.
Target files
Reports
The migrated reports are copies of the reports that you selected as source
files. They are essentially the same reports, but with one significant difference:
their data source locations are now set to the converted data source objects
in BusinessObjects Enterprise.
Data sources
After the migration, the data sources that were included in your source files
are transformed into objects that are usable in BusinessObjects Enterprise.
Depending on the type of data source, the wizard creates one of two objects
in the BusinessObjects Enterprise Repository: Crystal queries are converted
into SQL Command objects, and dictionaries and InfoViews are converted
into Business Views.
To create the target reports, you must have write permissions for the location
where you want to save the files. To create the target data source files, you
must have write permissions for the BusinessObjects Enterprise Repository
where the converted objects will be stored.
Migration workflow
You begin the migration by selecting the source files that you want to migrate.
These typically consist of pairings between a Crystal report and the query,
dictionary, or InfoView that acts as the report's data source.
After prompting you to specify the reports that you want to migrate, the wizard
analyzes each file and determines the type of data source that is associated
with each report. Depending on the type of data source, the migration wizard
creates one of two objects in the BusinessObjects Enterprise Repository:
Crystal queries become SQL Command objects, and dictionaries and
InfoViews are converted into Business Views.
Note: New objects are created in the repository; that is, the wizard does not
overwrite the original data sources during the migration.
After the new data sources are created in the repository, the migration wizard
makes copies of the reports and saves them to a specified location. The
wizard then resets the data source locations of the report copies to point to
the corresponding data source objects in the BusinessObjects Enterprise
Repository.
For example, if you choose to migrate a report that is based on a query, the
migration wizard first creates an SQL Command object in the BusinessObjects
Enterprise Repository. Then, it makes a copy of the report and saves it in a
location that you specify. Afterwards, the wizard resets the data source
location of that report to point to the SQL Command object in the repository.
3
3 Installation and Deployment Planning
Overview
This section describes the two paths that you can follow to migrate your files.
It offers deployment suggestions on how to optimize the migration process,
and then provides instructions for installing the migration wizard on your
system.
Overview
The Data Source Migration Wizard runs on any computer that has either
Crystal Reports or BusinessObjects Enterprise installed. This arrangement
allows a number of possible environments in which you can perform a
migration. (For example, you can run the wizard directly on the
BusinessObjects Enterprise server, or you can migrate your files from a
computer on your network.) However, each deployment has its advantages,
and an installation setup for one system may not necessarily facilitate the
most efficient migration for another.
Each migration path has a different application and set of advantages, which
are described in the sections below. From the information that is provided,
you can determine which path is most suited to your situation and your
migration needs.
Use the Data Source Migration Wizard to migrate your files moving the reports
to BusinessObjects Enterprise if you want to do the following:
• Migrate and test only a subset of reports and data sources at a time.
• Change your security model or authentication provider.
• Move to a new folder structure in BusinessObjects Enterprise.
If you choose this migration path, you may install the migration wizard on
any computer that has Crystal Reports or BusinessObjects Enterprise
installed locally. For information about the possible deployments to use in
this migration path, see For migrating the files first on page 18.
Use the Data Source Migration Wizard to migrate your files moving the reports
and data sources to BusinessObjects Enterprise if you want to do the
following:
• Include report instances in the migration.
• Retain the folder settings and/or custom settings that were set on the
reports from your Info system.
If you choose this migration path, you must install the migration wizard on
the BusinessObjects Enterprise server. As well, you must use the Import
Wizard to move your reports and data sources to BusinessObjects Enterprise
before you begin the migration.
For more information about this deployment, see For moving the files first
on page 20. For information about using the Import Wizard, see "Importing
with the Import Wizard" in the BusinessObjects Enterprise Administrator's
Guide.
This section outlines the four deployments that you can use if you choose
to migrate your files before publishing the reports to BusinessObjects
Enterprise.
You can install and run the migration wizard on the computer where you plan
to save the migrated reports. This deployment has these advantages:
• The migration is fast, because the reports are processed and stored on
the same computer that performs the migration.
• The transfer of substantial amounts of data less demanding on your
system (when compared to migrating your files through a separate
computer in a network.)
For the migration to work, the target report location must have Crystal Reports
installed and have access to the BusinessObjects Enterprise server where
you want to save the migrated data sources.
You can also install the migration wizard on a separate computer that has
access to both the Crystal Enterprise server and your target report location.
This deployment offers a different set of benefits:
• Because the files are processed on a separate computer, resources on
the Crystal Enterprise server and the target report location are not used.
• The migration can be done on any computer, provided it has Crystal
Reports installed.
Among the four deployments, this arrangement is the most flexible; however,
it has a disadvantage. Because the files need to be transferred through a
network, the migration may be slow, and it can substantially increase the
traffic in your system.
You can also install and run the migration wizard on the BusinessObjects
Enterprise server having to import your files first.
However, the migration wizard makes use of local memory. As a result, any
other BusinessObjects Enterprise processes that are running may slow down
during the migration.
Because you need to install and run the migration wizard on the
BusinessObjects Enterprise server, the deployment for this migration path
has all of the advantages that are described in On the BusinessObjects
Enterprise server on page 19 and On the BusinessObjects Enterpriseserver
and target report location on page 19. As a result, in terms of migration speed
and efficiency, moving your reports and data sources to BusinessObjects
Enterprise before migrating them offers the best deployment. However,
because the files are processed on the BusinessObjects Enterprise server,
other server processes may slow down during the migration.
Installation procedures
The Data Source Migration Wizard is distributed as a standard .zip file. Extract
all of the contents of the file before you begin the installation.
This dialog box displays the path to the directory where the migration
wizard will be installed. You cannot modify this location; the Data Source
Migration Wizard needs to be installed within the specified directory.
3. Click Next.
The "Ready to Install the Application" dialog box appears.
This dialog box confirms that the program is ready to be installed on your
computer.
4. Click Install.
The program installs the Data Source Migration Wizard on your computer.
5. Click Finish.
Note: If you are installing the migration wizard for the first time, you may
be prompted to restart your computer before the new settings take effect.
4
4 Report and Data Source Migration
Overview
This section lists step-by-step instructions for migrating your reports and
data sources through the Data Source Migration Wizard. It gives information
about how to modify the migration settings, and then describes how to locate
the migrated files.
Overview
By migrating your reports and data sources, you can take advantage of the
new features and extended functionality offered by BusinessObjects
Enterprise. As an integrated suite for reporting, analysis, and information
delivery, BusinessObjects Enterprise provides a solution for increasing
end-user productivity while reducing administrative costs.
Note: If you want to migrate query files that were created with the native
driver for DB2, you have the latest version of the DB2 Unicode driver installed
on your system. If you attempt to migrate the files without the driver installed,
the migration will fail.
To obtain the driver, visit the Business Objects Download Center:
http://www.businessobjects.com/products/downloadcenter/
Note: For additional information about special cases and particular issues
that are involved when using the Data Source Migration Wizard, see the
Release Notes, which are included in your product distribution.
You need to have the appropriate rights to be able to migrate the data
source files to the repository of your BusinessObjects Enterprise system.
For more information about system rights, see the BusinessObjects
Enterprise Administrator's Guide.
4. Click Next.
The "Select a File" dialog box appears.
7. Click the ... button to specify the location where you want the report files
to appear after the migration.
Note: The location that you specify must be able to access your
BusinessObjects Enterprise system. Otherwise, the migration wizard will
be unable to reset the data source location of the reports to point to the
migrated data sources in BusinessObjects Enterprise.
Tip: Select any of the check boxes to modify your migration settings. For
more information about these options, see Modifying the migration settings
on page 31.
8. Click Next.
The "Specify the Target Location for the Business Views" dialog box
appears.
11. Check to make sure that you have selected all of the files that you want
to migrate, then click Next.
The "Migrating Objects" dialog box appears.
13. Click Migrate Another to migrate more files, or click Finish to close the
wizard.
Tip: Select the "Show migration log" check box to view the log file of your
migration. This .txt file contains information that is useful for
troubleshooting potential errors in the migration process.
Migration options
These options are enabled by selecting the check boxes in the migration
wizard's "Specify the target location for the report files" dialog box. For more
information, see To migrate your reports and your report data sources on
page 26.
Copy all reports, including reports that are not based on queries,
dictionaries, or infoviews
By selecting this option, you enable the wizard to migrate other kinds of
Crystal reports. As a result, the migration wizard also saves copies of reports
that are not based on queries, dictionaries, or InfoViews to the new location.
However, because the data sources of these reports are not migrated, you
may need to reset their data source locations to point to different data sources
manually.
Examples of other Crystal report types include reports that are based on
direct database connections and reports that are based on Microsoft Excel
spreadsheets.
Force report migration even when the infoview file is not found
Select this option when you want to migrate an InfoView-based report that
does not have its corresponding InfoView available. The migration wizard
saves a copy of the report on the target location, and attempts to use the
cached version of the InfoView to create a Business View in the
BusinessObjects Enterprise Repository. Note, however, that even if the
wizard is successful in creating the Business View, all of the row restriction
formulas that were defined in the original InfoView are lost.
If this option is not selected, then reports with missing InfoView files are not
migrated.
Force report migration even when the query does not have SQL
text
This option allows you to migrate reports that are based on queries that do
not contain SQL text. (Queries that were created in Query Builder do not
contain SQL text.) If this option is selected, the migration wizard will create
an SQL Command object in the BusinessObjects Enterprise Repository
repository; however, like the original query, the Command will not contain
SQL text. A report that is based on this Command will still work, but because
the Command does not have SQL text, you will be unable to modify it in the
future.
To add the appropriate SQL text to the Command object, see Working with
the migrated data sources on page 39. For more information about SQL text,
see SQL text on page 32.
SQL text
Command objects typically consist of three parts: a data connection, a set
of parameters, and SQL text.
Migrated reports
After the migration, you can find the migrated reports in the folder that you
selected in the "Specify the target location for the report files" dialog box.
Note: For more information, see To migrate your reports and your report
data sources on page 26.
In this folder, the migration wizard creates directory paths, which are identical
to the directory paths of the source reports, and saves the migrated reports
correspondingly.
For example, if you chose to migrate five reports from their original locations:
• c:\Source_Directory\Report1.prt
• c:\Source_Directory\Folder1\Report2.prt
• c:\Source_Directory\Folder2\Report3.prt
• c:\Source_Directory\Folder2\Folder_2A\Report4.prt
• c:\Source_Directory\Folder2\Folder_2A\Report5.prt
• c:\Target_Directory\Folder1\Report2.prt
• c:\Target_Directory\Folder2\Report3.prt
• c:\Target_Directory\Folder2\Folder_2A\Report4.prt
• c:\Target_Directory\Folder2\Folder_2A\Report5.prt
After the migration, you can find the migrated data sources in the
BusinessObjects Enterprise Repository folder that you selected in the "Specify
the Target Location for the Business Views" dialog box.
Note: For more information, see To migrate your reports and your report
data sources on page 26.
In this folder, the migration wizard creates two subfolders: Commands and
Business Views.
Commands folder
The Commands folder contains the SQL Command objects that were created
from the original Crystal query files. Within this folder, the migration wizard
creates directory paths, which are identical to the directory paths of the
original query files, and saves the Command objects correspondingly.
Note: The filename of the migrated data source object in the repository is
the of the original data source from which it was converted.
The Business Views folder contains the Business Views that were created
from the original dictionary/InfoView files. In this folder, the migration wizard
creates directory paths which are identical to the directory paths of the original
dictionary/InfoView files, and saves the Business Views correspondingly.
Note:
• The filename of the migrated data source object in the repository is the
of the original data source from which it was converted.
• The migration wizard also creates a separate folder called Connections,
which contains the data connections that are used by all of the Business
Views.
5
5 Post-Migration Practices
Overview
This section describes the tasks that administrators must do after they have
finished migrating their files. It gives instructions for checking the migration
log and for verifying the functionality of the migrated reports. The section
also details some considerations about the migrated data sources, and briefly
discusses report publication to BusinessObjects Enterprise.
Overview
After the migration, you can find the migrated files in their new locations: the
reports are in the target folder that you specified, and the data sources are
in their respective folders within the BusinessObjects Enterprise Repository.
As the administrator, you need to perform a few tasks to ensure that the
migration was successful.
The wizard saves the log as a .txt file in the root of the folder that you specified
for your target reports.
For more information about using the log file to troubleshoot your migration,
see Troubleshooting on page 47.
Queries
The migration wizard creates SQL Command objects directly from the Crystal
queries that you selected. As a result, the Command objects will have
configurations that are identical to those of the original queries. (For example,
the objects will have the same parameter values, the same prompting text,
the same SQL text, and so on.)
If the original query does not contain SQL text (Queries that were created in
Query builder do not contain SQL text), then the resulting Command object
will also not have SQL text, and you will be unable to modify it in the future.
However, if you successfully migrated the report that was based on the query,
you can use Crystal Reports to find and add the appropriate SQL text to the
Command object.
Note: For more information about SQL text, see SQL text on page 32.
1. Find the report that is based on the SQL Command object, and open it
in Crystal Reports.
2. On the Database menu, click Show SQL Query.
The "Connection Information" dialog box appears.
3. Type your User ID and your Password, and select the Database that
you want to access.
4. Click Finish to log on to your data source.
5. Click OK.
The main window in Crystal Reports appears.
7. In the Selected Tables area, right-click the query, and, from the shortcut
menu that appears, select View Command.
The "View Command" dialog box appears.
8. In the Enter SQL query in the box below area, select and copy the SQL
text.
9. Click OK.
You are returned to the "Database Expert" dialog box.
10. In the Selected Tables area, right-click the query, and, from the shortcut
menu that appears, select Disconnect from Repository.
The "Connection Information" dialog box reappears.
11. Log on to the data source once again. When you click Finish, you return
to the "Database Expert" dialog box.
12. In the Selected Tables area, right-click the query, and, from the shortcut
menu that appears, select Edit Command.
13. In the Enter SQL query in the box below area, paste the SQL text, and
click OK.
The SQL Command on which the report is based now contains SQL text.
The Data Source Migration Wizard migrates the formulas and filters from
the original dictionaries/InfoViews to the new Business Views. However, the
wizard does not migrate the column-level security definitions that were set
in the original data sources. As a result, you may need to reset the security
definitions in each of the Business Views to ensure that they have the same
security capabilities as the data sources from which they were migrated.
3. Find the object for which you want to set security and right-click the object.
On the shortcut menu that appears, click Edit Rights.
The "Edit Rights" dialog box appears.
6
6 Troubleshooting
Understanding the log file
This section provides information about issues that may occur during the
migration. In particular, it focuses on specific situations that may result in
failed migrations and gives tips for using the log file to resolve common
problems.
The log file contains information that is useful for identifying any errors that
may have occurred in the course of the migration. It includes a list of every
report and data source that was processed by the wizard, and a record of
the actions that the wizard performed on each object.
INFO messages
Log file messages that are preceded by the [INFO] tag indicate that the
migration wizard is able to process the files successfully. Depending on the
report file, the data source type, and the migration settings enabled, different
messages may appear in the log.
Message Explanation
Message Explanation
ERROR messages
Log file messages that are preceded by the [ERROR] tag indicate that the
migration wizard encountered a problem. When this happens, the wizard
does not stop the migration process; it logs the error, bypasses the file, and
continues to migrate the rest of your files. You must always check the log
file to troubleshoot any errors that may have occurred during the migration.
Message Explanation
Message Explanation
Message Explanation
WARNING messages
Log file messages that are preceded by the [WARNING] tag indicate that
the migration wizard encountered situations that require the administrator's
attention.
Explanation
[WARNING] The row restrictions This message states any row restric-
defined in the original Crys tions that were defined in the InfoView
tal Infoview are not applied are not present in the Business View.
to any user. Please re-apply The administrator must review the
the corresponding Data Founda Business View's Data Foundation filters
tion filters if necessary. to re-apply the appropriate restrictions.
Explanation
A
A Get More Help
http://www.businessobjects.com/support/
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
http://www.businessobjects.com/services/training
documentation@businessobjects.com
Note: If your issue concerns a Business Objects product and not the
documentation, please contact our Customer Support experts. For information
about Customer Support visit: http://www.businessobjects.com/support/.
data connection 44
data foundation 44
E
data sources 8 ERROR messages 50
migrated 35
R security, column-level 43
source files 11
reports 8 definition 11
format 44 requirements 12
migrated 34 SQL Commands 13
other kinds 31 strings, date-time 44
publishing 44
source files 11
target files 12
T
testing 38 table 44
title 44 target files 12
version 44 definition 12
requirements 10 requirements 13
migration 10 testing reports 38
source files 12 troubleshooting 48
target files 13
W
S
WARNING messages 54
saved data 33 wizard, migration 8, 12
security definitions 43 workflow, migration 13