Xi3 Bip Importwiz en
Xi3 Bip Importwiz en
Copyright
2008 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and the Business Objects logo, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight, the Inxight Logo, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. Business Objects is an SAP company. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. All other names mentioned herein may be trademarks of their respective owners. Business Objects products in this release may contain redistributions of software 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 2008-06-02
Third-party Contributors
Contents
Chapter 1 Getting Started 7 What's new..................................................................................................9 Before you begin .......................................................................................10 Chapter 2 Import Wizard overview 13
Importing objects.......................................................................................14 Security migration overview.......................................................................16 Delegated administration...........................................................................16 Life cycle management..............................................................................17 Chapter 3 Importing information From Crystal Enterprise or BusinessObjects Enterprise 19 What kinds of objects can be imported?....................................................20 Importing users and groups.......................................................................21 Importing folders........................................................................................22 Importing report objects.............................................................................23 Importing rights..........................................................................................24 Importing events, servers, and server groups...........................................24 Chapter 4 Importing Information From BusinessObjects 5.x or 6.x 27
Before importing from BusinessObjects Enterprise 5.x/6.x.......................28 Ensure that you have appropriate rights..............................................28 To map the Import Wizard to Inbox and personal files.........................28 Export locally stored objects.................................................................29 Back up your source repository............................................................29 Importing objects from BusinessObjects Enterprise 5.x/6.x......................29
Contents
What kinds of objects can be imported?..............................................29 Security migration options....................................................................30 BusinessObjects documents................................................................32 Folders, domains, and categories........................................................34 Connections.........................................................................................35 Universes and universe connections...................................................37 Application Foundation objects............................................................39 Third-party documents.........................................................................39 Chapter 5 Using the Import Wizard 41
Specifying the source environment...........................................................42 To specify BusinessObjects 5 or 6 as a source environment...............43 To specify an Application Foundation source.......................................44 To specify Crystal Enterprise 9 as a source environment....................44 To specify Crystal Enterprise 10 as a source environment..................45 To specify BusinessObjects Enterprise XI or XI Release 2 as a source environment..........................................................................................45 To specify a BusinessObjects Enterprise XI 3.0 source environment...46 To specify a Business Intelligence Archive Resource file as a source environment..........................................................................................46 To specify a Text file as a source environment.....................................47 Specifying the destination environment.....................................................47 To set the destination environment......................................................49 Selecting objects to import.........................................................................49 Selecting an import scenario.....................................................................50 To select an import scenario when importing from BusinessObjects or XI 3.0........................................................................................................51 To select an import scenario when importing from other versions.......55 Selecting incremental import options.........................................................58 Selecting security migration options .........................................................60 Selecting specific objects to import...........................................................61
Contents
To select users and groups..................................................................61 To select group import options.............................................................62 To populate database credentials for users.........................................62 To select access levels.........................................................................63 To select categories..............................................................................63 To select folders and objects................................................................64 To select application folders and objects..............................................64 To select import options for universes and connections.......................64 To select universe folders and universes.............................................66 To select import repository objects options..........................................67 To select import options for publications..............................................67 To select remote connections and replication jobs...............................68 To select personal documents and inbox documents..........................68 To select Broadcast Agent Publisher External Users and Groups.......68 To select Broadcast Agent Publisher Publications...............................69 To select Broadcast Agent Publisher Profiles......................................69 To select domains and documents.......................................................69 To select locales and platform options ................................................70 Finalizing the Import..................................................................................70 Free disk space warning......................................................................70 Preparing for import..............................................................................71 Completing the import..........................................................................71 Updating imported events..........................................................................73 Chapter 6 Using text files with the Import Wizard 75
Text file format...........................................................................................76 Importing users, groups and profiles.........................................................76 Example Group record...............................................................................78 Importing data source credentials.............................................................79
Contents
Chapter 7
81
To back up server configuration settings to a BIAR file.............................83 To restore server configuration settings.....................................................83 Restoring server configuration scenarios.............................................85 To import nodes from one cluster to another ............................................95 Chapter 8 Life Cycle Management 97
Promoting report objects..........................................................................100 To promote report objects with existing universes.............................102 To promote report objects with new business views..........................103 To promote report objects with existing business views.....................104 Promoting universes and universe connections .....................................105 To promote universes and universe connections...............................105 Promoting users, groups, and object rights.............................................106 To promote new users and existing groups........................................107 To promote new groups with existing users.......................................108 To promote new object rights for existing users and groups..............109 Appendix A Get More Help 111
Index
115
Getting Started
The Import Wizard provides a series of screens that guide you through the process of importing and exporting Business Intelligence content such as user accounts, groups, folders, reports, universes, security, servers, and other objects. Various dialog boxes may appear depending on the source environment and the types of information that you choose to import. You can use the Import Wizard to import content from BusinessObjects, Crystal Enterprise, or BusinessObjects Enterprise into your current BusinessObjects Enterprise deployment. You can also export content from a BusinessObjects Enterprise XI 3.0 deployment to a Business Intelligence Archive Resource (BIAR) file, or import content from a BIAR file to your BusinessObjects Enterprise XI 3.0 deployment. You can choose to merge the contents of the source repository into the destination repository, or you can update the destination with the contents of the source CMS. You may also choose to import from or export to BIAR (Business Intelligence Archive Resource) files. You can also use the Import Wizard to back up XI 3.0 server configuration settings to a BIAR file, and restore server settings from an XI 3.0 BIAR file to an XI 3.0 deployment.
Note: Business Objects does not support moving Business Intelligence (BI)
content from a recent version of BusinessObjects Enterprise to an earlier version of the same release using BIAR files, the Import Wizard, or any other Business Objects Life Cycle Management (LCM) Tool. For example, reports, documents, and any other content from a BusinessObjects Enterprise XI Release 2 SP3 system cannot be moved to a BusinessObjects Enterprise XI Release 2 SP2 environment. Before starting this procedure, ensure that you have the Administrator account credentials for both the source and the destination environments. You can use a Delegated Administrator account for an XI 3.0 source or destination environment. The overall process is divided into the following general procedures: 1. 2. 3. 4. Specifying the source environment. Specifying the destination environment. Selecting the types of objects to import. Selecting an Import Scenario, which determines whether to merge or update the objects that you import. 5. Selecting the specific objects to import.
What's new
The Import Wizard introduces significant new features with this release.
BCA Publisher
With the BusinessObjects XI 3.0 Import Wizard, users can import BCA Publisher objects from 5.x/6.x, including: Mail Publications Web Publications BusinessObjects internal users and groups BCAP External users and groups Profiles Pending publication jobs
Note: Subscriptions are not imported. Users need to subscribe to publications
after migration.
Updating objects
When importing content, you can choose to update objects by name and path or by CUID.
Note: Matching objects by name and path is only supported for the following
object types. Folders and objects under public folders and personal folders Corporate Categories Personal Categories Universes, Overloads and Connections Dashboards Profiles Schedules
There are more options for importing only the desired documents from 5.x/6.x Inboxes and personal folders. The filtering options include: Import unread Inbox documents from repository Import read Inbox documents from a file system location
Delegated Administration
Delegated administrators, which have less than full administrative rights, can now use the Import Wizard to log on to XI 3.0 source and destination environments and import only those users and objects that they have access to.
Server configuration settings
With the Import Wizard, you can back up server configuration settings to a BIAR file, restore the settings from the BIAR file, and also re-point nodes from one XI 3.0 deployment to another XI 3.0 deployment.
Miscellaneous
A completely new interface to the full documentation set now has guides for all Business Objects products. The new online documentation library has the most up-to-date version of the Business Objects product documentation, posted upon publication and updated regularly. You can browse the library contents, run full-text searches, read guides on line, and download PDFs. http://support.businessobjects.com/documentation/product_guides/default.asp
10
If you are importing content from a BusinessObjects 5.x or 6.x source environment, see Importing Information From BusinessObjects 5.x or 6.x on page 27, and read the BusinessObjects Enterprise XI 3.0 Migration Guide. When you are ready to begin importing content, read Using the Import Wizard on page 41 for specific instructions on specifying the source and destination environments, selecting the objects and object types that you want to import, and selecting the appropriate import scenario and incremental import options. For the most up-to-date information on using the Import Wizard, go to the online documentation library at http://support.businessobjects.com/documen tation/product_guides/default.asp.
11
12
This section provides background information on importing Business Intelligence content from a BusinessObjects, Crystal Enterprise, or BusinessObjects Enterprise system to a BusinessObjects Enterprise XI 3.0 system.
Importing objects
When importing objects from a BusinessObjects 5.x, 6.x, Crystal Enterprise 10, or Business Objects XI, XI Release 2, or XI 3.0 source environment, you can specify what you want the Import Wizard to do when it finds objects on the source and destination environments with the same name and path or the same CUID.
Note: When you are importing objects from Crystal Enterprise 9, the Import
Wizard uses the objects' CUID to identify matching object. It automatically renames any source object that already exists on the destination environment, by appending a number to the end of the name.
When you are importing from a BusinessObjects 5.x or 6.x environment, or from an XI 3.0 source environment, you can choose to match objects by name and path or by CUID. When you choose to match objects by CUID, and the Import Wizard finds a matching object, you choose one of the following: Update the destination object, and in case of a name conflict, rename the object. Update the destination object, and in case of a name conflict, do not import the object. Do not import the object. When you choose to match objects by name and path, and the Import Wizard finds a matching object, you can choose one of the following: Keep the destination object and import a renamed copy of the object. Update the destination object. Do not import the object.
14
When you are importing objects from Crystal Enterprise 10, Business Objects XI, or XI Release 2, you can merge the source system with the destination system, or update the destination system. When you merge the environments, the Import Wizard uses the name and path of the source objects to determine whether those objects already exist on the environment. The Wizard adds all of the selected objects from the source to the destination CMS without overwriting objects in the destination environment. All of the objects in the destination environment are preserved. When you update the destination environment, objects in the source are added to the destination CMS. If a source object has the same unique identifier as an object in the destination environment, the destination object is overwritten. If you do not want the Import Wizard to overwrite objects on the destination on the "Incremental import" screen, you can choose to not overwrite existing objects, rights, groups, and group memberships. In this case, the objects that already exist on the destination are not overwritten by the selected source objects. If you are updating the destination environment and the Import Wizard finds an object on the destination with the same name and path as an object that you are importing but a different CUID, you have the option to Automatically rename objects if an object with the same title already exists in the destination folder. If you choose this option, the Import Wizard renames the source object and imports it. If you don't choose this option, the Wizard does not import the source object.
Incremental import options
If you are updating objects that already exist on the destination environment, you can choose appropriate incremental import options. These provide you with options to overwrite or not overwrite objects, universes, universe connections, user and group membership, and object rights. For example, even though you choose to update and overwrite report objects, you can decide to not overwrite the universes and universe connections that your reports use.
Related Topics
15
Delegated administration
You can use delegated administration to divide administrative tasks between functional groups within your organization. For example, you may want people from different departments to manage their own users and groups. When you use the Import Wizard, you can log into a source and destination environment for the import with an administrative account. You can also let delegated administrators that have less than full administrative access to log into XI 3.0 source and destination environments and import only those users and objects that they have access to. If delegated administrators are importing objects from an XI 3.0 system, they require the View and Copy right on those objects. To import users, they require the Modify User Password right.
16
If delegated administrators are importing objects that don't already exist on the destination, they require the View, Copy, and Add rights on the folder or area on the destination that the objects belong to. For example, if a delegated administrator is importing Report A into Folder A on the destination, the administrator requires View, Copy, and Add rights on Folder A. If delegated administrators are importing objects that already exist on the destination, they require the View, Edit, Copy, and Modify Rights rights on the objects. For example, if a delegated administrator is importing Report A , and that report already exists on the destination, the administrator requires the View , Edit, Copy, and Modify Rights rights on Report A on the destination. If delegated administrators are importing users, they require the Modify User Password for those users, whether the users already exist on the destination or not. For more information on delegated administration, refer to the BusinessObjects Enterprise Administrator's Guide.
17
18
Importing information From Crystal Enterprise or BusinessObjects Enterprise What kinds of objects can be imported?
The following sections describe importing objects from a Crystal Enterprise or BusinessObjects Enterprise system to a BusinessObjects Enterprise XI 3.0 system.
The following object types can be imported from a BusinessObjects Enterprise XI 3.0 source environment. Server intelligence objects Access levels Remote connections Replication jobs
Note:
If you are importing unmanaged objects from Crystal Enterprise 9, you must first upgrade the objects to an intermediate version and then import the objects into XI 3.0.
20
Importing information From Crystal Enterprise or BusinessObjects Enterprise Importing users and groups
You can use the Import Wizard to import managed objects from Crystal Enterprise 9. The Import Wizard does not import Olapi reports (.car files) from Crystal Enterprise 10.
21
belong to the New Sign-Up group, the group is migrated to the destination BusinessObjects Enterprise XI environment.
Aliases
If a user in the destination system has an alias that is identical to a user who is being imported, the destination user keeps all aliases, and the imported user loses that particular alias.
Windows AD
When importing users that employ Windows Active Directory authentication, ensure that the administrative credentials are the same on both the source and destination systems. Active Directory authentication must also be enabled on the destination system.
LDAP
When importing users that employ LDAP authentication, the Host list and Base LDAP name need to be the same on both the source and destination systems. LDAP authentication must also be enabled on the destination system.
Related Topics
Importing objects on page 14 Selecting an import scenario on page 50 Selecting incremental import options on page 58
Importing folders
Folders are imported, whether or not they exist already in the destination environment. To ensure that existing folders are not overwritten, make sure you choose to rename the folders on the "Import scenarios" screen If you are importing from Crystal Enterprise 10, or BusinessObjects Enterprise XI or XI Release 2, and are matching objects by name and path, you can choose the Automatically rename top-level folders that match top-level folders on the destination system option on the "Import scenario" screen to rename the source folders when you import them. If you don't select this option, and the Import Wizard finds folders on the destination with the same name and path, the Import Wizard doesn't import the source folders.
22
Importing information From Crystal Enterprise or BusinessObjects Enterprise Importing report objects
If you are matching objects by CUID, you can choose Automatically rename objects if an object with that title already exists in the destination folder. If you do not choose this option, the Import Wizard does not import the folder. If you are importing from BusinessObjects Enterprise XI 3.0, are matching by name and path, and do not want to overwrite existing folders, on the "Import scenarios" screen select either Keep the destination object and import a renamed copy of the object or Do not import the object. If you choose to rename folders, the Import Wizard appends a number to the end of any duplicated folder names to indicate the number of copies. For example, if you import a folder called Sales Reports when a folder called Sales Reports already exists, then the imported folder is added to BusinessObjects Enterprise with the name Sales Reports(2).
Related Topics
23
Related Topics
Importing rights
When you import folders and reports from one BusinessObjects Enterprise system to another, the associated object rights are imported for every user or group who is imported at the same time. If the user or group is not imported at the same time, or if the user or group does not already exist on the destination environment, the object rights are discarded. If you do import the appropriate user or group, and the user or group already exists by name in the destination environment, then the corresponding object rights are imported and applied to the existing user or group. If you are importing from a Crystal Enterprise 10 or BusinessObjects Enterprise XI, XI Release 2, or XI 3.0 source environment, you have the additional option of not overwriting existing object rights on the destination environment. To do this, on the "Incremental import" screen, ensure that you clear the Overwrite object rights checkbox.
Related Topics
Importing objects on page 14 Selecting an import scenario on page 50 Selecting incremental import options on page 58
24
Importing information From Crystal Enterprise or BusinessObjects Enterprise Importing events, servers, and server groups
When importing report objects associated with a server group, if the server group exists on the destination system, the report objects are added to the existing group and the source system's server group is not imported. If you have jobs scheduled or pending on a server or server group that you are importing, you might notice odd behavior on the destination system with the individual jobs involved until they run or time out.
Objects that have server group restrictions lose the restrictions if the objects are imported and the server group is not. For example, if a report is scheduled to run only under server group A and that server group is not imported, the report loses that restriction and will run under any server group. You need to import the server group at the same time as the objects that use it to keep the relationship between them. The same logic applies for events: if an object is set up to wait for an event or to trigger an event, you need to import the event at the same time as the object. Otherwise, the object is imported without the dependency and no longer waits for, or triggers, the event.
Note:
If Event A is being imported from the source system but there is already an Event A on the destination system, and it is a different type (for example, a File event instead of a Custom event), the wizard removes the dependency on Event A from the object when it is imported. Events are based on Event Servers. Because servers are not imported from previous versions of BusinessObjects Enterprise, if you are importing events, you must run an EventUpdater script to associate the events with new event servers after you complete the import process. For more information, see Updating imported events on page 73.
After you use the Import Wizard to import events to a destination environment, you must run the EventUpdater script to associate the imported events with the destniation Central Management Server (CMS).
Related Topics
Backing up and restoring server configuration settings on page 81 Updating imported events on page 73
25
Importing information From Crystal Enterprise or BusinessObjects Enterprise Importing events, servers, and server groups
26
Importing Information From BusinessObjects 5.x or 6.x Before importing from BusinessObjects Enterprise 5.x/6.x
The following sections describe importing objects from a BusinesObjects 5.x or 6.x system to a BusinessObjects Enterprise XI 3.0 system. For more information, see the BusinessObjects Enterprise XI 3.0 Migration Guide.
28
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
$INSTALLDIR\nodes\<nodename>\<clustername>\storage\mail if you are importing the read content of users' Inbox folders
29
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
Inbox, personal, and corporate documents Third-party ("agnostic") documents (such as .pdf, .ppt, .doc, .xls, .txt, .rtf) Personal and corporate categories Broadcast Agent Scheduler tasks that are supported in XI 3.0 Application Foundation 6.x objects Third-party documents used by Application Foundation objects (includes .svg, .xml, .swf, .csv, .gif, .jpg, .bmp, and .png) Broadcast Agent Publisher publications, profiles and external users
Potential limitations
In the current version, the Import Wizard does not import: Business Objects Services Administrator settings Administration Console settings Web Intelligence OLAP Custom applications and interfaces created using the SDK Broadcast Agent Scheduler tasks that are not supported in XI 3.0 BusinessObjects Auditor InfoView personal settings some user settings, such as timestamps BusinessQuery
30
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
If you want to import both objects and principals at one time, however, you can still import the objects without their rights by choosing the appropriate option in the Import Wizard's Security Migration Options dialog box. When you select users/groups to be imported, rights may be imported as well: If you have selected objects as well, users' rights on these objects will be imported. Rights on applications, such as InfoView and Web Intelligence are always imported. To give you more flexibility in how these rights are migrated, the Import Wizard provides three security migration options which allow you to import objects either with their rights or without them; if you import security, it also allows you to restrict user rights.
Performance Management folder (top level) access level All Desktop Intelligence rights All Web Intelligence rights All Designer rights
No Access
31
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
As these rights are set for the Everyone group, they apply to all users, unless they are explicitly assigned another value. To give them access, administrators must use the CMC to explicitly grant the proper users the appropriate rights. This is the most secure option, selected by default. The second option imports the objects' contents and rights, in order to reproduce the source security model, but does not set the restrictions in the target CMS that it sets in the first option. Default settings are set in the Everyone group for some rights, and apply to all users. As these default values may be different from the version 6.x defaults, this may allow migrated users to have more rights than they had in the source environment. If you want to avoid this, use the first option or do not migrate security and recreate it in the new environment. In both cases, the Import Wizard sets the access level for the Everyone group to No Access for all imported domain folders. This restricts access for all users for whom no default rights are given. After the import, you must use the CMC to explicitly give access to users and groups for specific folders. If you give access to a domain folder to the Everyone group, all users will have access to this folder and be able to see all documents in it. Before doing this, make sure you have thoroughly reviewed the security using the CMC.
BusinessObjects documents
When you import a 5.x/6.x BusinessObjects (.rep) document to XI 3.0, the following occur: universe ID pointer is updated so that it references a universe in the CMS. an InfoObject is created in the CMS for this document and for the saving of this document properties are updated and displayed in the CMC
32
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
BusinessObjects template (.ret) documents do not contain cubes or a connection to a universe. Therefore, all that occurs is: the locale of the document is updated an InfoObject is created in the CMS
To convert migrated 5.x/6.x .rep documents to .wid format, you can use the Report Conversion Tool, delivered with the XI 3.0 suite. See the Report Conversion Tool Guide for more information. If you migrate security during the import of BusinessObjects documents, version 5.x/6.x security commands are converted to XI 3.0 application-level and document-level rights. Some commands have been eliminated and others renamed. The Administrators group in XI 3.0 has Full-Control access to documents. The Everyone group has View access.
Limitations
Keep in mind the following limitations when you import BusinessObjects documents: XI 3.0 can read BusinessObjects 5.x/6.x .rep documents, but after you save these documents in XI 3.0, they cannot be accessed by a 5.x/6.x version of the software. BusinessObjects 5.x/6.x cannot open XI 3.0 Desktop Intelligence documents. OLAP data providers are not supported in XI 3.0. BusinessObjects 5.x/6.x documents based on an OLAP data provider are view-only in XI 3.0. There is no document password protection, on the server side, in XI 3.0. XI 3.0 Desktop Intelligence cannot access a version 5.x/6.x repository.
BusinessObjects SDK
The platform-related portion of the BusinessObjects SDK has evolved, which means that code developed for 5.1/6.x requires updates for platform interactions (authentication, send document, receive document).
33
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
Send to Users and Send to Broadcast Agent Server are not available in XI 3.0. Instead, you need to use the Platform COM SDK. The server-side report engine is not multi-document. This means that add-ins is not loaded on the server. For example, for a document based on a custom data provider (DPVBAInterface) implemented in an add-in, refresh will fail.
Calculator changes
XI 3.0 uses a different report engine than BusinessObjects 5.x/6.x. Therefore, there are differences in the way the calculator is handled. Because of this, there may be issues with BusinessObjects documents after they are imported to XI 3.0.
34
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
imported user, selected personal categories are imported to a new subfolder (named after the user) under the Personal Categories folder. You can select individual Corporate categories and import Web Intelligence documents grouped by Corporate category. Personal categories, however, can be imported only as part of the batch import.
Connections
When you import version 5.x/6.x universes, the associated connections are imported automatically and are converted into connection objects. Make sure that the Import Wizard can access the 5.x/6.x database the same way that version 5.x/6.x accesses it. You may need to install database drivers or configure connection settings on the machine. For example, if you import SQL Server connection objects from a 5.x/6.x source environment, you must configure the connections on the destination machine via the Control Panel before you import the connection objects. You must use the same name and settings as the connection used on the source machine when you created the domain key.
BOUSER/BOPASS
In version 5.x/6.x, users could use @Variable('BOUSER') and @Variable('BOPASS') in the connection information for the universe. The variables were replaced at runtime with the user's enterprise username and password, and used to log on to the database. For security reasons, however, XI 3.0 does not permit the retrieval of user passwords. Therefore, universe connections that previously used the BOUSER and BOPASS variables must now use database credentials (DBUSER and DBPASS). Those database credentials can be populated by the Import Wizard and later edited in the CMC, on the Properties tab for each user account. When migrating, the Import Wizard: replaces BOUSER and BOPASS with DBUSER and DBPASS in universes proposes automatically populating these variables for users to migrate
35
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
There are three ways to synchronize enterprise and database credentials in the XI 3.0 system. You can: choose the Import Wizard option that batch imports user names and passwords from version 5.x/6.x to auto-populate database credentials in XI 3.0. run a batch upload of a user's file. User names and passwords are loaded from a file, stored and used as database credentials. create a custom application using Enterprise SDK to set DBUSER and DBPASS information.
Access restrictions
In a 5.x/6.x system, access restrictions (object restrictions, table mapping, and row restrictions) are defined with the Supervisor application and associated with users and groups. A user who belongs to multiple groups is said to have multiple user instances (one instance per group).
Note: Universe overloads in version 5.x/6.x are called access restrictions
in XI 3.0. They are managed in Designer. The Import Wizard enables you to import all access restrictions that are associated with the imported universes for any of the selected users and groups being imported. If no principal users or groups are selected for import, no access restrictions are imported and none are created. The imported access restrictions are converted into objects. They remain connected to the universes to which they were connected in the source environment. The Import Wizard may create additional access restrictions in the destination environment in order to preserve the restrictions for all imported users. Connections for access restrictions are not migrated automatically. You must manually migrate these connections.
36
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
Access restrictions are migrated using both object names and object IDs to identify universe components.
37
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
the connection is saved in the FRS and an InfoObject is created in the CMS the universe and its linked documents are copied into the FRS universe overloads defined in 5.1/6.x, if migrated, are mapped to access restrictions in XI 3.0 ). ACEs are created to migrate universe-related security commands the locale is preserved
Imports all universes and all connection Import all universes and all connection objects. You cannot select individual objects universes or connections. Import all universes and only connec- Imports all universes, and only connection objects used by these universes tion objects used by those universes. Imports all universes and connections Import the universes and connections used by the selected documents. This that the selected Web Intelligence and option also enables you to select addiBusinessObjects documents use directtional universes to import, even if they ly are not used by any document.
When you select a Web Intelligence or BusinessObjects document to import, the Import Wizard automatically selects the associated universes for import.
Note: The Import Wizard also imports any universes with the same name
that exist in other domains. BusinessObjects documents may have been created outside the repository, using a "short name"; that is, a reference to a universe stored on a local machine. If the universe has a short name, its linked documents may not be imported if more than one universe is found in the CMS with the same short name. Universe domains are converted into subfolders under the Universe folder. Each universe folder is named after the corresponding version 5.x/6.x
38
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
universe domain. When you import a universe from a domain, it is placed in the corresponding domain folder. If the universe is a derived universe, then all relevant core universes and their connections are also imported.
Note: Designer 5.x/6.x cannot open universes created with Designer XI 3.0. Related Topics
BusinessObjects XI 3.0. The Performance Manager repository structure in XI 3.0 is similar to that of Application Foundation. There is no significant change in the architecture.
Third-party documents
BusinessObjects Enterprise 5.x/6.x supports third-party (also known as "agnostic") documents. The Import Wizard imports these documents into XI 3.0 if the format is supported. Formats supported in XI 3.0 include Adobe Acrobat PDF; Microsoft Power Point, Word, RTF, and Excel; and *.txt documents. For the most up-to-date list of supported formats for third-party documents, see the list of supported platforms.
39
Importing Information From BusinessObjects 5.x or 6.x Importing objects from BusinessObjects Enterprise 5.x/6.x
40
The Import Wizard provides a series of screens that guide you through the process of importing and exporting Business Intelligence content such as user accounts, groups, folders, reports, universes, security, servers, and other objects. Various dialog boxes may appear depending on the source environment and the types of information that you choose to import. The overall process is divided into the following general procedures: 1. 2. 3. 4. Specifying the source environment. Specifying the destination environmnent. Selecting the types of objects to import. Selecting an Import Scenario, which determines whether to merge or update the objects that you import. 5. Selecting the specific objects to import.
Note: The process of importing users, groups and profiles from a text file is
a less complex task. Both the format for the text file and the procedure are outlined in Using text files with the Import Wizard on page 75.
Related Topics
Specifying the source environment on page 42 Specifying the destination environment on page 47 Selecting objects to import on page 49 Selecting an import scenario on page 50
42
43
You can import Application Foundation objects only if you selected BusinessObjects Enterprise 6.x (or XI) in the Source list. 5. Click Next. A warning appears that summarizes the items that can be imported. 6. Click Next.
44
Related Topics
45
content than will fit in a single file, the Import Wizard exports the content to multiple BIAR files. To import content that is stored in these files, it is only necessary to select the head BIAR file. The Import Wizard automatically imports the content from the other files. 3. Click Next The "Destination environment" screen appears.
Related Topics
46
Specifying the destination environment on page 47 Using text files with the Import Wizard on page 75
47
There are two choices of destination environments for BusinessObjects Enterprise XI 3.0: 1. BusinessObjects Enterprise XI 3.0 - your content will be placed into the CMS system database and/or the File Repository Server (FRS) file system according to the objects you select. 2. Business Intelligence Archive Resource (BIAR) File - your content will be placed in a compressed file for backup or importing into a different deployment.
Note:
The BIAR file destination is only available if your source environment is XI 3.0 or higher. The BIAR file destination is not available if your source is also a BIAR file. If the content that you choose to export is too large for a single BIAR file, the content is exported to multiple BIAR files. The Import Wizard puts the files into the same directory.
48
Server groups are imported without their member servers. After the import is complete, you need to manually add the desired servers to the imported server groups.
49
If you do not manually add the servers, the server groups are not valid, and you will not be able to run any reports that depend on the server groups. If you import documents without importing any related universes, and those universes don't already exist on the destination environment, the imported documents lose the relationship with their universes. If you import objects that have rights attached to them, and you want to import object rights for the objects, you must either import the users and groups for whom the rights are set, or ensure that the users and groups already exist on the destination environment. If you are importing root level objects from BuinessObjects Enterprise XI Release 2, BusinessObjects Enterprise XI 3.0, or from and XI 3.0 BIAR file, you can also import the rights that have been explicitly specified on the root level folders. To do this, on the "Import users and user groups" screen, select Import root folder rights. If you import reports that use repository objects, and you do not also import those repository objects, those repository objects must already exist on the destination environment. If you want to import universe overloads, you must ensure that you also import the appropriate users, groups, and universes. If you want to back up your server configuration settings to a BIAR file so that you can restore them later, select Export server configuration.
50
When you are importing an object from BusinessObjects 5.x/6.x, BusinessObjects Enterprise XI 3.0, or from an XI 3.0 BIAR file to an XI 3.0 destination environment, you have two options to identify the object and determine if the object already exists on the destination environment: 1. Use the source object's unique identifier (CUID). 2. Use the source object's name and path. You must decide how you would like the Import Wizard to handle scenarios where the objects already exist on the destination environment.
51
The following table describes the options that are available to you if are matching by CUID, and the Import Wizard finds existing objects on the destination.
Table 5-1: Option 1. If the Import Wizard detects an object in the destination with the same unique identifier:
Action
Description
If the Import Wizard finds an object in the destination environment with the same CUID, it updates the destination's object. Update the destination object. In case of name conflict, rename it. If the Import Wizard does not find an object in the destination environment with the same CUID, but it finds an object with the same name, it imports the object from the source environment and then renames that object. If the Import Wizard finds an object in the destination environment with the same CUID, it updates the destination's object.
Update the destination object. In case of name conflict, do not import If the Import Wizard finds an object it. on the destination environment with the same name but different CUID, it does not import the object from the source environment. If Import Wizard finds an object on the destination environment with the same CUID, it does not import the object.
52
The following table describes the options that are available to you if you are matching by name and path, and the Import Wizard finds existing objects on the source environment.
Table 5-2: Option 2. If the Import Wizard detects an object in the destination with the same name and path:
Action
Description
If Import Wizard finds that an object already exists on the destination environment with the same name and Keep the destination object and im- path, it imports the source's object port a renamed copy of the object. and renames it. After the import, both the destination's original and the source's versions are on the destination. If Import Wizard finds that an object already exists on the destination environment with the same name and path, it updates the destination environment's version with the source's. If Import Wizard finds that an object already exists on the destination environment with the same name and path, it does not import the source's version.
Note:
Matching objects by name and path is only supported for the following object types: Folders and objects under public folders and personal folders Corporate Categories Personal Categories Universes, Overloads and Connections
53
All other object types will use the matching by unique identifier scheme. Matching objects by name and path is not an option when importing content from a BIAR file. When you import from BIAR files, objects will be matched by CUID. If you choose update objects on the destination, whether you are matching objects by CUID or name and path, you can choose incremental import options on the next screen. These options allow you to specify which types of objects that you want the Import Wizard to overwrite, and which types of objects you want to leave untouched.
54
When you are importing content from Crystal Enterprise 10, or BusinessObjects Enterprise XI, you can either merge the source and destination environments, or you can update the destination environment without merging.
Note: When you are importing content from Crystal Enterprise 9, the Import
Wizard only matches by CUID. If the Import Wizard finds an object on the destination with the same CUID as on the source environment, it automatically imports the source object and renames it.
55
Action
Description
The Import Wizard uses the object's name and path to determine if the source object already exists on the destination system. The Wizard adds all the selected objects from the source to the destination without overwriting objects on the destination environment. All of the objects on the destination environment are preserved.
If the Import Wizard finds top-level folders with the same name and path on both the source and destination Automatically rename top-level fold- environments, the Wizard renames ers that match top-level folders on and imports the source folders. the destination system. If you do not choose this option, the Import Wizard does not update matching top-level folders. The Import Wizard uses an object's CUID to determine if the source object already exists on the destination environment. All of the selected obI want to update the destination sys- jects from the source are added to tem by using the source system as the destination, but if the source oba reference. ject has the same CUID as an object on the destination, and you choose to overwrite objects on the" Incremental import" screen, the destination object is overwritten.
56
Action
Description
Automatically rename objects if an object with that title already exists in If you do not choose this option, the the destination folder. Import Wizard does not import the object.
The Import Wizard renames objects from the source that have the same name and path but a different CUID.
Note:
If you choose to update the destination system by CUID, you can choose incremental import options on the next screen. These options allow you to specify which types of objects that you want the Import Wizard to overwrite, and which types of objects you want to leave untouched. When CUIDs are changed, links between documents, rules, and other objects that refer to each other using CUIDs may be impacted. If you import objects with links to other objects, the safest option for migration is the second option (Updating the destination environment).
in Update mode, even when the Merge option is selected. 2. Decide if you want the documents or folders to be renamed during the import. If you want the Import Wizard to automatically rename a folder or object that already exists in the destination environment, select the check box. If you don't want automatic renaming, ensure that the check box is clear. 3. Click Next to continue.
Related Topics
57
For example, if you chose to overwrite objects on the destination environment, but do not want to overwrite universe objects, you can chose to not overwrite universes by ensuring the Overwrite universe contents is not selected. This screen allows you the following options:
58
Option
Description
If the Import Wizard finds a matching object on the destination environment, it overwrites the object. An object refers to any type of object except universes, universe connections, and groups. If the Import Wizard finds a matching universe on the destination, it overwrites the universe. If the Import Wizard finds a matching universe connection on the destination, it overwrites the connection.
If the Import Wizard finds matching groups on the destination, it replaces the group membership information on the destination with the group Overwrite group and user member- membership information of the source. ship If you do not choose to overwrite group membership, the Import Wizard adds new members and leaves existing members untouched.
59
Option
Description
If the Import Wizard finds a matching object on the destination environment, and the users or groups that the object's rights pertain to are either on the destination or are being imported, the wizard overwrites any existing rights on the object for those users or groups. If you do not select to overwrite object rights, the Import Wizard adds any new rights to the object that aren't already specified on it. It does not add or modify any existing rights on the object.
60
61
If the "Import Groups Option" screen appears, the 6.x source and the XI 3.0 destination environments are configured for LDAP or Active Directory. You need to have the same LDAP or Active Directory configuration on the source and destination. For information about setting alias creation and assignment for LDAP and Active Directory users, see the BusinessObjects Enterprise Administrator's Guide.
2. Click Next.
62
2. Click Next to continue. For detailed information on the import of database credentials, see the BusinessObjects Enterprise XI 3.0 Migration Guide.
rights of that object. If the object's rights are based on an access level, and that level is not imported and does not exist on the destination, the Import Wizard gives the individual rights specified in the level on the object for the user. 1. Select the access levels that you want to import. The default access levels are: Full Control. No access. Schedule. View . View on demand. If you have created any additional access levels, they also appear on the list. 2. Click Next to continue.
To select categories
If you are importing categories, the "Categories" screen appears. 1. Select the categories that you want to import. For large document domains, you can import incrementally, and import documents one category at a time. 2. To import all the objects associated with the category, select the Import all objects that belong to the selected categories check box. 3. Click Next to continue .
63
64
This screen allows you to select one of three options: Import all universes and all connection objects. Import all universes and only connection objects used by these universes. Import the universes and connections that the selected Web Intelligence and Desktop Intelligence documents use directly.
Note: If you select the third option, you can select additional universes to
import on the next screen. 1. Select an import option for the universes and their connections. 2. To import universe overloads, select Keep universe overloads for imported users and groups. If you are importing universe overloads, you must also select the users, groups, and universes during previous steps in the Import Wizard. You must also select Overwrite existing objects on the "Incremental Import" screen. If you did not select those options, click Back until you get to the appropriate screen, and make the required selections.
65
Note:
If you choose to import users and groups, universe overloads and other objects, and do not want to overwrite all of the object rights for the users and groups and objects that you've selected, either: Ensure that you've only selected the universes that you want to import, and then import the other objects in another import process. Delete the universe overload on the destination environment, clear the Overwrite existing objects and Overwrite object rights options on the "Incremental Import" screen. In this case, the Import Wizard only imports the universe overloads that don't exist on the destination environment. 3. Click Next to continue.
automatically. Before you can import connection objects from BusinessObjects 5.x/6.x, ensure that the Import Wizard can access the database the same way that the source environment accesses it. This may involve installing database drivers or configuring connection settings on the machine. For example, if you import SQL Server connection objects from a BusinessObjects 6.x source environment, you must configure the connections
66
on the destination machine via the ODBC Data Source Administrator settings in the Windows Start Menu Control Panel before you import the connection objects. You must use the exact same name and settings as the connection used on the source machine when you created the domain key.
67
BusinessObjects Enterprise XI, the Import Wizard always imports the personal documents, inbox documents, and favorite folders for all selected users. 1. To import inbox documents, you can Import unread inbox documents. Import read documents from the location that you specify. Import inbox documents received after the date that you specify. 2. To import personal documents, you can Import personal documents from the location that you specify. Import personal documents that were modified or created after the date that you specify. 3. Click Next to continue.
68
To select groups without selecting the users in those groups, hold SHIFT , and select the groups. You can also choose to Select groups that contain selected users and Import BCA Publisher Profiles for selected users and groups 2. Click Next to continue.
69
Third-party
The list contains a separate branch for each domain. Domains that cannot be opened are greyed out. If you previously chose to import all the documents of a given category, they are preselected and cannot be cleared. 1. Select the domains and documents you want to import . 2. Click Next to continue.
into the .wid format before importing them. In a BusinessObjects 5.x/6.x repository, some Web Intelligence 2.x (.wqy) documents and BusinessObjects documents may not store their locales. In order to set locales in these documents when they are saved in the CMS (after conversion to .wid), the default locales provided by the user are added to the documents. 1. Select the default locale of the documents to import. 2. Select the default locale of the platform used to create documents to import. If they are not already saved in the documents, these locales will be saved during the import. 3. Click Next to continue.
70
The Import Wizard copies the objects that you select to your destination environment's temporary directory, as specified in the Temp environment variable. If the free disk space warning appears, and there is not enough room in the destination environments Temp directory: 1. Click Back to return to the previous dialog box. 2. Either free up additional disk space on the destination environment or specify a new location for the temporary directory by modifying the Temp variable on the destination environment. 3. On the dialog box, click Next.
71
1. To view the details of the import, click View Detail Log. The "Detail Log" dialog box appears This dialog box lists all the objects the Import Wizard has migrated and their status, as well as any errors that may have occurred. You can sort the entries according to any column, by clicking the column's heading. For more details on a given item, select it from the list. The details are displayed at the bottom of the dialog box.
Note:
The information that appears in the Detail Log is also written to a log file. The log file starts with the name ImportWiz, and is located in the
C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\Logging\ directory by default.
The log file includes a system-generated ID number, a title that describes the imported information, and a field that describes the action and the reason why it was taken. A version of the log file in .CSV format is also written, in the same directory.
72
2. Click Done. If you are importing objects any source environment other than BusinessObjects Enterprise XI 3.0 or an XI 3.0 BIAR file, the Import Wizard displays a dialog box informing you that it will run a rights verification tool. This tool looks for child objects on the destination that have rights explicitly granted on them that their parent object does not have. If it finds any such objects, the Import Wizard removes the rights on the child. The details of any rights that have been removed on objects during the import process appear in a .CSV file, located in the C:\Program
Files\Business Objects\BusinessObjects Enterprise 12.0\Logging\ directory by default.
3. If the dialog box appears, click OK to start the tool. The Import Wizard adjusts the rights on imported child objects.
73
Parameter
Description
-oldeventserv The friendly name of the event server on the system that the event was exported from. er -neweventserv The name of the event server on the XI 3.0 system that you want to associate the event with. er -cms -user -password The name of any CMS on the XI 3.0 destination system. The username for a BusinessObjects Enterprise administrator account. The password for the BusinessObjects Enterprise administrator account.
-authentication The authentication method. The accepted values are secEnter prise, secWinAd, and secLdap.
1. Locate the appropriate script, depending on your platform. 2. Run the script with the necessary parameters. On Windows, run
c:\Program Files\Business Objects\BusinessObjects Enter prise 12.0\win32_x86\scripts\eventupdater.bat" -olde ventserver <old event server friendly name> -neweventserv er <new event server name> [-cms <cms>] [-user <username>] [-password <password>] [-authentication secAuthType]
On UNIX, run
./bobje/eventupdater.sh -oldeventserver <old event server friendly name> -neweventserver <new event server name> [-cms <cms>] [-user <username>] [-password <pass word>] [-authentication secAuthType]
74
Using text files with the Import Wizard Text file format
The Import Wizard can import any of the following from text files: Users Groups Profiles Data source credentials
A combination of users, groups and profiles can be in one file, but data source credential must be in a separate text file.
76
Using text files with the Import Wizard Importing users, groups and profiles
Each field must have separator between it and the next field. Each field, can potentially be blank except for field 1.
One single record can define either a group or a user or a group, a user and a profile. Text files must be saved in UTF-8 format.
Note:
The default separator is a comma but this can be changed on the Select options for file import dialog box. If a character in the any field of the record is the same as the character used for a separator it must be delimit. The default delimiter character is a double quote.
Field Number
Contents of field
Group name User Name Full name of user Email address of user Profile name for user. Profile value for user.
Note: Profile values must be enclosed in quotes. See Text file format on
77
Using text files with the Import Wizard Example Group record
The previous record would create an account name or username of "psanders" in BusinessObjects Enterprise. The name Paula Sanderson, and the e-mail address of psanders@Acme.com would be associated with this account name. The username "psanders" would be member of the group "Sales". The username psanders and would be assigned the profile "Manager" with the profile value of "West Region".
Group Record Format
Field Number
Contents of field
Group name Null Description of group. Field is ignored. Profile name for group. Profile value for group.
Note: Profile values must be enclosed in quotes. See Text file format on
78
Using text files with the Import Wizard Importing data source credentials
The previous record would create the "Best" group, with description of "Group for sales". The profile Sales would be assigned the profile value "General".
The previous example create the account name "dbuser" and the password "Dbpasw0rd" associated with Enterprise user Psanders. The option "Enable Data Source Credentials for Business Object Universes" would also be selected for username Psanders.
79
Using text files with the Import Wizard Importing data source credentials
80
Backing up and restoring server configuration settings To back up server configuration settings to a BIAR file
The Import Wizard lets you to back up your server configuration settings to a BIAR file, and then use that BIAR to restore those settings at a later date. Server groups are objects that group related servers together. If you are restoring servers and you are not restoring their related server groups, and the destination system does not contain the same server groups (matched by CUID), you lose the relationship between the server group and the exported server. When you re-import the server, you need to either manually add the server to the desired server groups or create new server groups. You can set up reports to run on particular server groups. If you are exporting reports and the related server groups are not imported, and do not already exist on the destination, the reports lose their relationship to the server group. If you want the report to use particular server group, and that group does not exist on the destination, you need to manually configure the server groups. Similarly, if you are importing servers, server groups, or reports without importing the users that have rights on those objects, and those users do not already exist on the destination environment, the rights on those objects are dropped. You may have security settings on those objects that are not correctly set.
Note:
The Import Wizard supports the backing up and restoring of entire deployments, including all of the servers and nodes in the deployments. The Import Wizard Command Line Tool does not support the importing and exporting of server configuration settings. If your destination deployment already has servers with the same server identifier as the servers in your BIAR file, then those servers may fail to import. If the import process fails, determine which servers on the destination system have conflicting server identifiers. You can see the server list by viewing the Import Wizard's Detail Log, or by opening the log file ImportWiz.log. If there are servers that conflict because they have the same server identifiers, use the CMC to delete those servers from the destination deployment, and repeat the server import process. By default, ImportWiz.log is located in C:\Program Files\Business
Objects\BusinessObjects Enterprise 12.0\Logging\
82
Backing up and restoring server configuration settings To back up server configuration settings to a BIAR file
If you've created additional servers or nodes after you backed up your configuration settings, and use the Import Wizard to restore the configuration settings, the Import Wizard doesn't update or delete these servers or nodes. However if such servers used configuration templates then they can become reconfigured. This is because during restore process the configuration templates are updated, affecting the server's configuration. If you want to get your system to the same server configuration state as it was at the time of the backup, and your
83
Backing up and restoring server configuration settings To restore server configuration settings
BusinessObjects Enterprise deployment has more servers than the BIAR file that you are restoring from does, you may want to delete the servers through the CMC before you restore. If you delete servers from your BusinessObjects Enterprise deployment, you must ensure that the deployment has at least one CMS to run the Import Wizard. Do not restore server configuration settings from a Windows deployment to a UNIX deployment or from a UNIX deployment on a Windows deployment. Always restore server configuration settings from a Windows deployment to a Windows deployment and from Unix deployment to Unix deployment.
1. Specify the BIAR file that contains the server configuration settings that you want to import as the source environment. 2. Specify your BusinessObjects Enterprise XI 3.0 system as the destination environment. 3. On the "Select objects to import" screen, select Restore Full Cluster Server Configuration, and click Next.
Note: If you select Import node(s) from a different cluster, you can't
select Restore Full Cluster Server Configuration . 4. On the "Import Scenarios" screen, specify what you want the Import Wizard to do if it finds an object with the same unique identifier on the destination environment.
Note: When you are importing objects from a BIAR file, the option to
match objects by name and path is not available. The options that you can select are: Update the destination object, in case of name conflict, rename it. Use this option when you want to restore all server objects that are in a BIAR file to a deployment. If the deployment already has other servers with the same names, then some of the updated servers may be renamed. If a server in the BIAR files has a unique identifier that matches a server's unique identifier on the deployment, then the server on the deployment will be overwritten with the configuration settings of the server located in the BIAR file. If, during the import process, the Import Wizard discovers that the deployment already has another server with the same name as the
84
Backing up and restoring server configuration settings To restore server configuration settings
server from the BIAR file, the Import Wizard imports the server and renames it. The server's new name will be server name as it appears in the BIAR file, appended with a number in brackets. Update the destination object, in case of name conflict, do not import it. Use this option when you want to restore all server objects from the BIAR file to a deployment, except the servers with different unique identifiers but with the same names. Do not import the object Use this option if you do not want servers on deployment to be overwritten with settings from the BIAR file. This will cause only servers not existing on your deployment (but existing in the BIAR file) to be restored. See Restoring server configuration scenarios on page 85 for examples that describe how server configuration settings can be restored from BIAR files. 5. On the "Incremental import" screen, select whether you want to overwrite object contents or overwrite right contents. 6. Click Next until the "Ready to Import" screen appears. 7. On the "Ready to Import" screen, click Finish. The "Import Progress" screen appears. After the import is complete, the screen displays a summary of the import. 8. Click Done to close the Import Wizard.
85
Backing up and restoring server configuration settings To restore server configuration settings
Server Name
Value
mynode.cms mynode.eventserver
1 2
6401 2
When you export these settings to a BIAR file, the file contains the same server settings.
Table 7-2: Initial Server Configuration Settings in the BIAR file
Server Name
Value
mynode.cms mynode.eventserver
1 2
6401 2
All of the folowing scenarios assume that we are importing the server configuration settings from this BIAR file. Suppose that you modify the server configuration settings on the deployment so that the deployment now has the configuration settings described in the following table.
Table 7-3: New Server Configuration Settings on the Deployment
Server Name
Value
mynode.cms
Request Port
6402
86
Backing up and restoring server configuration settings To restore server configuration settings
Server Name
Value
mynode.eventserver
The following two scenarios describe how the options on the "Import scenario" screen affect the process of restoring server configuration settings from the BIAR file.
Scenario 1
This scenario describes what the Import Wizard does when, on the Import scenario screen, you select Use the object's unique identifier to determine whether it already exists in the destination system, and then select one of the following options. Update the destination object. In case of name conflict, rename it, or Update the destination object. In case of name conflict, do not import it.
The deployment's initial configuration settings are described in the following table.
Table 7-4: Initial Server Configuration Settings on the Deployment
Server Name
Value
mynode.cms mynode.eventserver
1 2
6402 3
When you import the servers from the BIAR file, the Import Wizard finds servers in the BIAR file and on the deployment with matching unique
87
Backing up and restoring server configuration settings To restore server configuration settings
identifiers. The Import Wizard overwrites the values on the deployment with the values from the BIAR file. In other words, the deployment's original settings are restored. The server configuration settings on the deployment after this workflow are described in the following table.
Table 7-5: New Server Configuration Settings on the Deployment
Server Name
Value
mynode.cms mynode.eventserver
1 2
6401 2
Scenario 2
This example explains what happens when, on the Import scenario screen, you select the Use the object's unique identifier to determine whether it already exists in the destination system. and Do not import the object options. The deployment's initial configuration settings are described in the following table.
Table 7-6: Initial Server Configuration Settings on the Deployment
Server Name
Value
mynode.cms mynode.eventserver
1 2
6402 3
88
Backing up and restoring server configuration settings To restore server configuration settings
When you match by unique identifier and choose the Do not import the object option, the Import Wizard finds servers with the matching unique identifiers, and does not import the server configuration settings. The servers on the deployment are not updated.
Scenario 3
The following examples show what happens when you modify the server configuration settings on the deployment, and then try to restore the settings from the BIAR file that you imported the settings to. Suppose that you make the following three changes on the deployment. Rename the mynode.cms server to mynode.primarycms. Add a new server, called mynode.cms, with the Request Port property set to 6404. When a new server is added, it is automatically assigned a new unique identifer. Delete the event server.
The following table describes the server settings on the destination deployment after these modifications.
Table 7-7: Server Configuration Settings on the Destination Deployment
Server Name
Value
mynode.primarycms mynode.cms
1 3
6402 6404
When you restore the server configuration settings from the BIAR file, the particular settings that are imported to the deployment depends on the options that you select on the "Import scenarios" screen.
89
Backing up and restoring server configuration settings To restore server configuration settings
Scenario 3.1
Suppose that you use the Import Wizard to restore the server configuration settings from the BIAR file, and that on the Import scenarios screen, you select Use the object's unique identifier to determine whether it already exists in the destination system and Update the destination object, in case of name conflict, rename it. Use this option when you want to restore all servers from a BIAR file to a deployment. The deployment's initial configuration settings are described in the following table.
Table 7-8: Initial Server Configuration Settings on the Deployment
Server Name
Value
mynode.primarycms mynode.cms
1 3
6402 6404
When you match by unique identifier and choose the Update the destination object, in case of name conflict, rename it option, the Import Wizard finds that the unique identifier for mynode.cms from BIAR is 1, and that the unique identifier of the mynode.primarycms server on the deployment is also 1. However, when it detects that the deployment already has another server with mynode.cms name, it renames the restored server. Furthermore, because the mynode.cms server doesn't exist in the BIAR file, that server is not updated during the import process. This results in the deployment described in the following table.
90
Backing up and restoring server configuration settings To restore server configuration settings
Server Name
Value Result
mynode.cms(2)
This server is restored with a new name. This server is restored. This server is not updated, because it does not exist in the BIAR file.
mynode.eventserver
mynode.cms
Scenario 3.2
Suppose that you use the Import Wizard to restore the server configuration settings from the BIAR file, and that on the Import scenarios screen, you select Use the object's unique identifier to determine whether it already exists in the destination system and Update the destination object, in case of name conflict, do not import it. Use this option when you want to restore all server objects from a BIAR file to a deployment, except servers with different unique identifiers but with the same name. The deployment's initial configuration settings are described in the following table.
91
Backing up and restoring server configuration settings To restore server configuration settings
Server Name
Value
mynode.primarycms mynode.cms
1 3
6402 6404
When you match by unique identifier and choose the Update the destination object, in case of name conflict, do not import it option, the Import Wizard does not import the server settings from the BIAR file for mynode.cms, even though the unique identifiers of mynode.cms (in the BIAR file) and mynode.primarycms (on the deployment) are the same. This is because the Import Wizard detects a server on the destination with the same name, and does not import the server. The results in the deployment are described in the following table.
Table 7-11: Server Configuration Settings on the Deployment
Server Name
Value Result
mynode.primarycms
mynode.eventserver
92
Backing up and restoring server configuration settings To restore server configuration settings
Server Name
Value Result
mynode.cms
This server is not updated, because it does not exist in the BIAR file.
Scenario 3.3
Suppose that you use the Import Wizard to restore the server configuration settings from the BIAR file, and that on the Import scenarios screen, you select Use the object's unique identifier to determine whether it already exists in the destination system and Do not import the object on the "Import scenario" screen. Use this option when you do not want the servers on a deployment to be overwritten by servers from a BIAR file. This option only restores servers that do not exist on the deployment, but that are in the BIAR file. The deployment's initial configuration settings are described in the following table.
Table 7-12: Initial Server Configuration Settings on the Deployment
Server Name
Value
mynode.primarycms mynode.cms
1 3
6402 6404
When you match by unique identifier and choose the Do not import the object option, the Import Wizard does not import the server settings from
93
Backing up and restoring server configuration settings To restore server configuration settings
the BIAR file for mynode.cms, even though the unique identifiers of mynode.cms (on the BIAR file) and mynode.primarycms (on the destination environment) match. This is because you've selected to not import objects where the source and destination environments have the same unique identifier. The results in the deployment are described in the following table.
Table 7-13: Server Configuration Settings on the Deployment
Server Name
Value Result
mynode.primarycms
This server is not updated, because you've chosen not to overwrite existing servers on the deployment. This server is restored. This server is not updated, because it does not exist in the BIAR file.
mynode.eventserver
mynode.cms
94
Backing up and restoring server configuration settings To import nodes from one cluster to another
Wizard does not import configuration templates from BIAR files. To re-point a node on a Test deployment so that the node joins the cluster on the Production deployment: 1. On the Test deployment, start the Import Wizard and export the server configuration settings to a BIAR file. For information on importing nodes to a BIAR file, see To back up server configuration settings to a BIAR file. 2. On the Test deployment, stop the Server Intelligence Agent . 3. On the Production deployment , use the Import Wizard to import the node from the BIAR file. a. Start the Import Wizard. b. Select the BIAR file that contains the node as the source environment. c. On the "Select objects to import" screen, select Import node(s) from a different cluster , and click Next. d. On the "Import scenario" screen, select what you want the Import Wizard to do if it finds any objects on the destination environment with the same unique identifier. e. On the "Incremental import" screen, select whether you want the Import Wizard to overwrite any objects or object rights that already exist on the destination environment.
95
Backing up and restoring server configuration settings To import nodes from one cluster to another
f. On the "Nodes" screen, select the node that you want to import, and click Next. g. On the "Ready to Import" screen, click Finish. h. On the "Import Progress" screen, click Done. 4. If you are not re-pointing all of the nodes that are on the Test deployment, then reconfigure the Test deployment's node that you are re-pointing: If you are re-pointing a node on a Windows deployment, follow these steps. a. On the Test deployment, start the CCM. b. Right-click the node that you imported to the Production environment, and select Properties > Startup. A list of local and remote CMS Servers is displayed. c. Click Remove, to remove the link to the CMSs that you are not re-pointing. d. Click OK. If you are re-pointing a node on a UNIX deployment, run the server config.sh script to remove the link to the CMSs that you are not re-pointing. 5. If the node that you've imported contains a CMS: On Windows, perform the following steps. a. On the Test deployment, start the CCM. b. Right-click the Server Intelligence Agent for the node that you are re-pointing, and select Properties > Configuration. c. Click Select a Data Source. d. Type the DSN for the Production database, and click OK. On Unix, run the cmsdbsetup.sh script to change the node's data source to the Production database. 6. On the Test deployment, start the re-pointed Server Intelligence Agent.
Related Topics
96
Many deployments of BusinessObjects Enterprise contain different stages such as a Development, QA, and Production within the same version. Reports and other Business Intelligence objects often require modification or enhancement as a result of changing information needs. Administrators must control how objects are promoted through these stages, whether the objects are completely new or whether they overwrite or update objects that already exist in the destination environment. This is referred to as Life Cycle Management. An important consideration in Life Cycle Management within the same version, is how the objects will exist in the new environment. Will the promoted objects be completely new objects in the new environment, or will the promoted objects overwrite similarly named objects in the new environment, or will the promoted objects simply update existing objects in the new environment? In BusinessObjects Enterprise XI 3.0 there are new import scenario options, and a feature called Incremental importing, which greatly enhance the administrators choices for content promotion.
Import scenarios
When using the Import Wizard to promote an object from one BusinessObjects Enterprise XI 3.0 deployment to another, the wizard allows you use either the objects CUID or its name and path to determine whether the object already exists on the destination environment. It also lets you specify what you want the wizard to do when it finds that an object already exists on the destination environment. When you are matching objects by CUID, and the Import Wizard finds a matching object on the destination environment, you have three options: Update the destination. In case of name conflict, rename the object. If the Import Wizard finds an object in the destination environment with the same CUID, it updates the destination's object. If the Import Wizard does not find an object in the destination environment with the same CUID, but it finds an object with the same name, it imports the object from the source environment and then renames that object. Update the object. In case of name conflict, do not import it. If the Import Wizard finds an object in the destination environment with the same CUID, it updates the destination's object.
98
If the Import Wizard finds an object on the destination environment with the same name but different CUID, it does not import the object from the source environment. Do not import the object. If Import Wizard finds an object on the destination environment with the same CUID, it does not import the object. If the Import Wizard does not find an object with matching CUID, it imports the source object. When you are matching objects by name and path, and the Import Wizard finds a matching object on the destination environment, you have three options: Keep the destination object and import a renamed copy of the object. If Import Wizard finds that an object already exists on the destination environment with the same name and path, it imports the source's object and renames it. Update the destination object If Import Wizard finds that an object already exists on the destination environment with the same name and path, it updates the destination environment's version with the source's. Do not import the object If Import Wizard finds that an object already exists on the destination environment with the same name and path, it does not import the source's version. Matching objects by name and path is only supported for the following object types: Folders and objects under public folders and personal folders Corporate Categories Personal Categories Universes, Overloads and Connections Dashboards All other object types will use the matching by unique identifier scheme.
99
Matching objects by name and path is not an option when importing content from a BIAR file. When you import from BIAR files, objects will be matched by CUID.
Incremental imports
By default, the Import Wizard automatically imports dependent objects. For example, when you import report objects, the Import Wizard will also import the universes and universe connections that the reports use. The Incremental import screen allows you to import objects without overwriting dependent objects that already exist on the destination environment. If you want to import report objects without importing a universe or connection that would overwrite a universe or connection on the destination environment, you can specify this on the Incremental import screen. The Incremental screen gives you the following options: Overwrite object contents Overwrite universe contents Overwrite connection contents Overwrite group and user membership Overwrite object rights
Note: Business Objects does not support moving Business Intelligence (BI)
content from a recent version of BusinessObjects Enterprise to an earlier version of the same release using BIAR files, the Import Wizard, or any other Business Objects Life Cycle Management (LCM) Tool. For example, reports, documents, and any other content from a BusinessObjects Enterprise XI Release 2 SP3 system cannot be moved to a BusinessObjects Enterprise XI Release 2 SP2 environment.
100
When you use the Import Wizard to import report objects, the wizard automatically imports any universe and universe connections that the reports are dependent on. If you want to import a report object from one environment that uses universes or connections, those universes or connections already exist on the destination environment, and you do not want to overwrite those objects on the destination environment, you must ensure that you chose to not overwrite those objects on the Incremental import screen.
Note:
If you import a reports without import dependent universes, and those universes do not already exist on the destination environment, the reports will lose the relationship with the universes and will not run properly on the destination environment. If you import a report that has rights set on it for users and groups, and you want to import the object rights on the report, you must either import those users and groups or ensure that the users and groups already exist on the destination environment. If you are importing a report that relies on a server group or an event that already exists on the destination, do not overwrite the server group or event. On the "Select objects to import" screen, do not select the server group or event. If you're importing server groups or events, the Import Wizard does not allow you to import specific objects. You must import all events or server groups, or none of them. If you've modified an event or server group on the source environment, and only want to import that one object, delete the object from the destination environment, and then ensure that you clear the Overwrite object contents on the "Incremental import" screen. This ensures that the modified server group or event is the only one that is imported. If you're importing a modified report that uses a modified event or server group, perform the import in two steps. Delete the event or server group from the destination environment and then import the modified object, making sure that you do not overwrite any objects on the destination environment. Then import the report object, ensuring that you select "Overwrite object contents" on the "Incremental import" screen.
101
102
repository objects such as business views, the Import Wizard does not allow you to choose specific repository objects to import. On the "Import Repository objects options" screen, you can choose one of three options. Import all repository objects. Import only repository objects that the selected reports use directly. Import repository objects that the selected reports use directly, as well as any other repository objects they depend on. 1. Start the Import Wizard, and specify your source and destination environments. 2. On the "Select objects to import" screen, select Import folders and objects, and click Next. 3. On the "Import Scenarios" screen, select whether you want to use the objects' CUID or name and path to determine whether the objects already exist on the destination environment, and what you want the Import Wizard to do if it finds matching objects, and click Next. 4. On the "Incremental import" screen: a. Clear Overwrite object contents, to ensure that repository objects on the destination environment are not overwritten. b. To ensure that you don't overwrite universe and universes connection objects on the destination environment, clear the Overwrite universe contents and Overwrite connection contents checkboxes. c. If the Overwrite group and user membership or Overwrite object rights checkboxes appear on the screen, ensure that they are cleared. d. Click Next to continue. 5. On the "Import Repository objects options" screen, select Import only repository objects that the selected reports use directly. 6. On the "Folders and objects" screen, select the reports that you want to import. 7. Complete the import process.
103
104
7. On the "Folders and objects" screen, select the reports that you want to import. 8. Complete the import process. The Import Wizard imports the business view to the destination environment. Because the business view does not exist on the destination, the business view is imported, even though you choose to not overwrite object contents on the destination. No other repository objects on the destination are touched.
imports dependent universe connection objects to the destination environment, unless you choose to not overwrite the universe connections.
105
a. If you want to update a universe that already exists on the destination environment, select the Overwrite universe contents checkbox. b. Specify whether you want to overwrite the universe connections on the destination. If you want to update universe connections that already exist on the destination environment, select the Overwrite connection contents checkbox. c. To ensure that you don't overwrite any objects or object rights, clear the Overwrite object contents and Overwrite object rights checkboxes. d. If the Overwrite group and user membership checkbox appears, ensure that it is cleared. e. Click Next to continue. 5. On the Import options for universes and connections screen, select Import all universes and only connection objects used by these universes. 6. Complete the import process. The Import Wizard imports the universes that you selected to the destination environment. If you choose to not overwrite universes connections, the connections that the selected universes rely on are not imported, and the universe connections that exist on the destination environment are not touched. The relationships between the universes and the universe connections are maintained.
Wizard deletes any user-to-group relationships that exist on the destination environment but don't exist on the source environment.
106
If you want to add users from the source to the destination environment, on the "Incremental import" screen, ensure that you clear the Overwrite group and user membership checkbox. To replace destination groups with source groups, ensure that you select Overwrite group and user membership.
107
108
109
110
Business Objects offers a full documentation set covering all products and their deployment. The online documentation library has the most up-to-date version of the Business Objects product documentation. You can browse the library contents, do full-text searches, read guides on line, and download PDF versions. The library is updated regularly with new content as it becomes available. http://support.businessobjects.com/documentation/product_guides/
Additional developer resources
http://devlibrary.businessobjects.com
Online customer support
The Business Objects Customer Support web site contains information about Customer Support programs and services. It also has links to a wide range of technical information including knowledgebase articles, downloads, and support forums. http://www.businessobjects.com/support/
Looking for the best deployment solution for your company?
Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in relational and multidimensional databases, in connectivities, database design tools, customized embedding technology, and more. For more information, contact your local sales office, or contact us at: http://www.businessobjects.com/services/consulting/
Looking for training options?
From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. Find more information on the Business Objects Education web site: http://www.businessobjects.com/services/training
112
Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line, and we will do our best to ensure that your suggestion is included in the next release of our documentation: mailto: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/.
For information about the full range of Business Objects products, visit: http://www.businessobjects.com.
113
114
Index
.rep files migrating 32 .ret files and migration 32 .wid files migrating orphan documents 32 @Variable('BOPASS') 35 @Variable('BOUSER') 35
B
backing up server configuration settings 82 backing up repository 29 broadcast agent publisher external users and groups, importing 68 broadcast agent publisher profiles, importing 69 broadcast agent publisher publications, importing 69 Business Objects Services Administrator settings migration 30 business views importing 103, 104 BusinessObjects migration of document rights 32 BusinessObjects documents import limitations 33 importing 32 migrating OLAP data providers 33 migration of rights 32 BusinessObjects SDK Send to BCA 33 Send to Inbox 33
A
access levels, importing 63 ACEs on import of universe-related security commands 37 AD authentication, importing 21 add-ins migration 33 Administration Console settings migration 30 administrators delegated 16 agnostic documents importing 39 aliases 21 application folders and objects, importing 64 Application Foundation object migration 39 authentication 21 LDAP 21 Windows AD 21
C
Categories folder 34 categories, importing 63 CMS 39 connections BOUSER/BOPASS variables 35 how the Import Wizard imports 37 connections, importing 64
115
Index
converting .rep files to .wid 32 .rep files to .wqy 32 CSV format 76 CUIDs 37 custom access levels, importing 63
G
groups, importing 61
I
Import Groups Option dialog box 62 import scenarios 50, 98 Import Summary 71 Import Wizard and third-party documents 39 how it imports domains 34 how it imports universe connections 35 how it imports universes and connections 37 limitations 30 log file 71 mapping to Inbox and personal files 28 overview 8 security migration options 30 Security Migration Options dialog box 30 specifying source 42 specifying source and destination 42, 47 importing application folders and objects 64 Broadcast agent publisher external users and groups 68 broadcast agent publisher profiles 69 broadcast agent publisher publications 69 categories 63 custom access levels 63 database credentials 62, 76 domains 34 domains and documents 69 folders 22, 64 group and user membership 58 groups 21, 76 importing security 16 instances 23 mapping Import Wizard to Inbox and personal documents 28 nodes 82
D
database credentials, importing 62 databases synchronizing enterprise and database credentials 35 using the DBUSER/DBPASS variables 35 delegated administrators 16 derived universe 37 Designer 5/6 and XI 3.0 compatibility 37 and access restrictions in XI 3.0 36 destination environment, and importing 47 document passwords 33 domains importing 34 importing universe domains 37 domains and documents, importing 69
E
events 24 events, updating 73 exporting objects 29
F
folders Universe 37 folders, importing 64 free disk space warning 70 FRS connection storage 37
116
Index
importing (continued) object rights 58 objects 58 personal documents and inbox documents 68 profiles 67, 76 publication recipients 67 remote connections and replication jobs 68 repository objects 67 rights 24 security options 60 server configuration settings 82 specifying source and destination 42, 47 text files 76 universe folders and universes 66 universes and connections 58, 64 users and groups 61 users with aliases 21 users with LDAP authentication 21 Web Intelligence documents 70 importing business views 103, 104 importing object rights 106 importing reports 100, 102, 103, 104 importing universes 100, 102, 105 importing users and groups 106 Inbox documents mapping Import Wizard to 28 inbox documents, importing 68 incremental import 98 installation required rights 28
M
matching objects, by CUID 50 objects, by name and path 50 migrating BusinessObjects documents 32 connections 35 domains 34 specifying source and destination 47 third-party documents 39 migration security migration options 30
N
nodes, importing 82
O
object IDs 36 object rights importing 106 object rights, importing 58 objects exporting 29 restrictions 36 objects, importing 23 orphan documents defined 32 overwriting group and user membership 58 object rights 58 objects 14, 50, 58 universes connections 58
L
life cycle management 17, 98 promoting business views 103, 104 promoting object rights 106 promoting reports 100, 102, 103, 104 promoting universes 100, 102 promoting universes and universe connections 105 promoting users and groups 106
117
Index
P
passwords using the DBUSER/DBPASS variables 35 performance management repository 39 Personal Categories folder 34 personal documents mapping Import Wizard to 28 personal documents, importing 68 Platform COM SDK 33 profiles, importing 67 promoting business views 103, 104 promoting object rights 106 promoting reports 100, 102, 103, 104 promoting universes 100, 102 promoting universes and universe connections 105 promoting users and groups 106 publication recipients, importing 67
SDK 30 security migration options 30 synchronizing enterprise and database credentials 35 security commands migration of universe-related 37 Security Migration Options dialog box 30 security options, importing 60 security, importing 16 server configuration settings, importing 82 server groups, importing from Crystal Enterprise 24 source environment, specifying 42, 47 SQL Server importing connection objects from 5/6 35 Supervisor universe access restrictions 36 synchronizing enterprise and database credentials 35
R
remote connections, importing 68 replication jobs, importing 68 reports importing 100, 102, 103, 104 reports, importing 23 repositories backing up 29 exporting locally-stored objects 29 repository objects, importing 67 restoring server configuration settings 82 rights importing 24 migration of BusinessObjects document rights 32 row restrictions 36
T
table mapping 36 text file delimiter 76 text file format 76 text file separator 76 third-party documents importing 39
U
universe connections see connections 35 universe folders and universes, importing 66 universes exclusive overloads 37 how they are imported 37 importing 100, 102 importing associated universes 37 modes of import 37 overload aggregation 37 overload collapsing 37
S
scheduling 23
118
Index
universes (continued) short name 37 the BOUSER/BOPASS variables 35 using the DBUSER/DBPASS variables 35 universes and universe connections importing 105 universes and universe connections, importing 58 universes, importing 64 users and groups importing 106 users, importing 21, 61
V
version 5/6 Inbox and personal storage 28 version XI 3.0 access restrictions 36
W
Web Intelligence documents, importing 70 WebIntelligence migrating orphan documents 32 WebIntelligence OLAP migration 30
119
Index
120