In this section: |
This section describes WebFOCUS migration considerations and provides the procedures for migrating WebFOCUS Content.
For information on migrating Reporting Server configuration settings, see the Server Administration manual.
Note: The following special considerations apply to WebFOCUS migration:
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3/EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
In this section: How to: |
The following types of authentication and authorization models can be migrated from WebFOCUS 7.x to WebFOCUS 8. Managed Reporting authorization rules from these authorization scenarios are migrated, but the security settings are not.
In WebFOCUS 8, the migration:
You can perform migrations of all content or of content selected by a file that lists the Domain HREFs or group HREFs to be migrated. You can also choose whether or not to include deferred tickets or deferred output in the migration.
Note:
Hex 20 = , ' & * ( ) | ; " ? /
During the migration process, these characters will be converted to an underscore (_).
You can migrate all Managed Reporting content, but you can also choose to migrate only the content for specified groups or Domains. Exported content always includes all users associated with the group or Domain. For groups, the content also includes all Domains associated with a group, and for Domains, the content also includes all groups associated with a Domain. In both full and partial migration, all the roles in the system are always exported.
Note: In a partial migration, you can specify content by group or by Domain, but not by a combination of both groups and Domains.
To migrate a subset of groups or Domains, you must create a plaintext file specifying the groups or Domains and place it in the mr directory before you begin the migration process. The file must list the HREF of each group or Domain on a single line. For groups, the HREFs must begin with a pound sign (#). Group and Domain HREFs are case-sensitive.
For example, you would specify the export of multiple groups with the following entries in a plain text file:
#domain1group#domain2group
You would specify the export of multiple Domains with the following entries in a plain text file:
domain1/domain1.htmdomain2/domain2.htm
To determine a Domain HREF, right-click the Domain folder and select Properties.
The procedure for determining group HREFs varies depending on whether WebFOCUS uses internal or external authorization. If WebFOCUS uses internal authorization, the group HREF information is stored in the user.htm file in the basedir directory. If WebFOCUS uses external authorization, the group HREF information can be obtained from the WF_MRGROUPS table.
In the user.htm file, each group has an entry that includes the HREF, the group name, and the group display name, as shown in the following code example.
<A HREF='#groupname' NAME='GroupName'>Display Name</a>
The group HREF is based on the group name, but all special characters are removed and the HREF is made lower case.
If WebFOCUS uses external authorization, to determine the group HREF, you must first know the group name. You can find the group name by using the MRAdmin tool to view the group properties. Then, use the group name to find the group ID in the WF_MRGROUPS table. The group HREF is the group ID prefaced by a pound sign (#). For example, if the group ID is domain1group, the group HREF is #domain1group.
Once you have created the file listing the Domains or groups that you wish to export, you can begin the migration process.
The Managed Reporting migration utility exports the current 7x basedir, including Domains, procedures, content, users, groups, and role information, to a WebFOCUS7x\utilities\mr\export directory. Any authorization information stored externally using the Realm driver (SQL Repository or AD/LDAP) is also retrieved and extracted.
Note:
You are prompted for the WebFOCUS version from which you are migrating.
WebFOCUS notifies you when the export process is complete. By default, the exported files are saved in the WebFOCUS7x\utilities\mr\export directory. The export log, which is named mr_migrate_export.log, is saved in the same directory. The directory also contains a file named reposTree.xml, which lists all the users and Domains that have been exported. The reposTree.xml file is used during ReportCaster migration. For more information, see Migrating ReportCaster Content.
Now you can import the exported Managed Reporting content into WebFOCUS 8.
You must have already created and initialized the database repository with the default values contained within the initial load, using WFReposUtil and the original XML.
When you perform a partial migration, you have multiple choices for how the target environment will handle the newly migrated resources:
Skip. Do not import these resources at all.
Add new resources (do not update). Import new resources, but do not modify resources that already exist in the target environment. This is the default behavior.
Add new resources and update existing resources. All new resources will be added to the target environment. If a resource exists in both the import package and the target environment, the resource in the target will be overwritten with the version in the import package.
You can select individual import behavior for content resources, roles, groups, and users. For example, you can choose to skip content resources, add new roles, and add and update users. Add new resources (do not update), which is the default behavior, is also the most common selection.
Note: User IDs longer than 64 characters may cause errors in the import process.
WebFOCUS notifies you when the import is complete. Files are saved in the drive:\WebFOCUS81\migration_import\export directory, along with the import log file, which is named import_migration.log.
How to: |
When Dashboard content is migrated to WebFOCUS 8, the data is extracted from the earlier release into a file named migrate.zip. You can then copy the zip file to the WebFOCUS 8 Server, then run the migration utility to import the data from the file into WebFOCUS 8. You must use the Dashboard Migration utility to import the data. Manually copying directories and files into the WebFOCUS81 directory structure does not guarantee a functioning Dashboard environment.
The Dashboard Migration utility is in the drive:\ibi\WebFOCUS81\utilities\mr directory. It is named bid_migrate_extract.bat in Windows and bid_migrate_extract.sh in UNIX. It copies the relevant Dashboard files from the drive:\ibi\WebFOCUS7x\worp directory for use with the latest WebFOCUS release. The entire worp directory is not migrated, only the worp_users and worp_custom folders, and (if it exists) the userdata folder.
To migrate custom template directories located in the worp/worp_html directory automatically, prefix the custom template directory names with custom_. If the directory names are not prefixed with custom_, you can manually copy the custom templates to the drive:\ibi\WebFOCUS81\worp_html directory. If they exist, the mpv.xml and xxxx.tbx files are also migrated from the drive:\ibi\WebFOCUS7x\worp\worp\conf directory.
Note:
Dashboards can be migrated from WebFOCUS 7.1 and higher.
Unicode Dashboard migration to WebFOCUS 8 is only supported from WebFOCUS 7.7. If you are using an earlier version of WebFOCUS, first migrate the Unicode Dashboard settings to WebFOCUS 7.7, then migrate them from WebFOCUS 7.7 to WebFOCUS 8.
In full WebFOCUS 8 installs, the drive:\ibi\WebFOCUS81\ibi_html/publish directory and drive:\ibi\WebFOCUS81\ibi_html\template directory, which contained the background images selected by users during the creation of published pages in WebFOCUS 7.x , are no longer created. However, these directories are preserved during Service Pack installs and will be created as needed in the migration to WebFOCUS 8.
Saved searches from WebFOCUS 7.7 do not appear in WebFOCUS Release 8.0 Version 02 after performing the Business Intelligence Dashboard migration. The XML file containing the search is moved from WebFOCUS 7.7 to Release 8.0 Version 02, but it is not used. Saved Searches can be migrated as part of the Favorite migration utility, provided to migrate the Favorite and Mobile Favorites list of items for a user. The migration step should be performed after the Managed Reporting and Business Intelligence Dashboard migration steps have been completed. The Favorites content found in the favorites.xml file under the following user directory will be migrated to the new database repository, drive:\ibi\WebFOCUS81\worp\worp_users\username.
The Dashboard Migration Utility dialog box appears.
A directory may appear by default if the worp directory exists under the WebFOCUS installation directory.
Note: The migration utility also migrates the drive:\ibi\WebFOCUS7x\ibi_html\publish directory and the drive:\ibi\WebFOCUS7x\ibi_html\template directory. These directories are no longer created by the WebFOCUS install and will not appear in new full installations of WebFOCUS 8.
WebFOCUS notifies you when the extraction is complete. The migrate.zip and bid_extract.log files are saved in the drive:\ibi\WebFOCUS77\utilities\mr\export\ directory.
The Dashboard Migration prompt is displayed.
WebFOCUS displays a default path to the worp directory.
Note: The migration utility also migrates the drive:/ibi/WebFOCUS7x/ibi_html/publish directory and the drive:/ibi/WebFOCUS7x/ibi_html/template directory. These directories are no longer created by the WebFOCUS install and will not appear in new full installations of WebFOCUS 8.
The utility prompts for the WebFOCUS release number from which you are migrating.
WebFOCUS notifies you when the extraction is complete. The migrate.zip and bid_extract.log files are saved in the drive:/ibi/WebFOCUS77/utilities/mr/export directory.
WebFOCUS notifies you when the data is successfully loaded in the database. The bid_load.log file is created in the drive:\ibi\WebFOCUS81\migration_import directory.
The Dashboard Migration Utility prompt appears.
WebFOCUS notifies you when the data is successfully loaded in the database. The bid_load.log file is created in the drive:/ibi/WebFOCUS81/migration_import directory.
How to: |
In WebFOCUS 8, Favorites and Mobile Favorites content is stored in the database repository. A utility is provided to migrate the Favorite and Mobile Favorites list of items for a user. The migration step is to be performed after the Managed Reporting and Business Intelligence Dashboard migration steps have been completed.
The Favorites content that is found in the favorites.xml file under the following user directory will be migrated to the new database repository, drive:/ibi/WebFOCUS81/worp/worp_users/username.
The bip_favorites_migration.log file is created in the drive:\ibi\WebFOCUS81\migration_import\export directory.
The bip_favorites_migration.log file is created in the drive:/ibi/WebFOCUS81/migration_import/export directory.
In this section: How to: |
To migrate ReportCaster content from a WebFOCUS 7.x Repository to WebFOCUS 8, you need to export the content from the WebFOCUS 7.x Repository and then import it into WebFOCUS 8.
If you are migrating both Managed Reporting and ReportCaster content, you must export the Managed Reporting content before you export the ReportCaster content. When you are importing, you must also import the Managed Reporting content before you import the ReportCaster content.
The Managed Reporting export creates the reposTree.xml file, which lists the users and Domains exported by Managed Reporting. The ReportCaster export includes content for these users and for ReportCaster Administrators. You can also choose to export non-Domain-based content for these users and Administrators.
Optionally, you can filter the Library content by updating the rcLibraryExport2XML.properties file in the rc directory. This filter applies whether or not you are migrating Managed Reporting content. It is recommended that you use the filter in self-service installations where Managed Reporting is not installed. For more information, see Filtering Library Migration Exports by Date.
WebFOCUS 7.7, copy the drive:\ibi\WebFOCUS81\utilities\rc directory into the drive:\ibi\WebFOCUS77\ReportCaster directory.
WebFOCUS 7.6, copy the drive:\ibi\WebFOCUS81\utilities\rc directory into the drive:\ibi\ReportCaster76 directory.
WebFOCUS 7.1, copy the drive:\ibi\WebFOCUS81\utilities\rc directory into the drive:\ibi\ReportCaster71 directory.
Note:
WebFOCUS 7.7 or WebFOCUS 7.6, run rcExport2XML.bat on Windows or rcExport2XML.sh on UNIX or Linux.
WebFOCUS 7.1, run rc71Export2XML.bat on Windows or rc71Export2XML.sh on UNIX or Linux.
Note: Library content will be additionally filtered by the rcLibraryExport2XML.properties file.
The migration script exports content owned by ReportCaster Administrators and the users specified by reposTree.xml. The following content is exported:
Domain-based Schedules of report procedures associated with the Domains specified by reposTree.xml.
Domain-based Library Reports from procedures associated with the Domains specified by reposTree.xml.
Distribution Lists.
Library Access Lists.
Execution IDs.
Global Blackout Dates and Group Blackout Dates for the groups belonging to the users who are listed in reposTree.xml.
Schedules and Library Reports associated with Domains that are not listed in reposTree.xml are not exported.
If you choose to include non-Domain-based content, ReportCaster will also export non-Domain-based Schedules and Library Reports owned by ReportCaster Administrators and users specified by reposTree.xml.
WebFOCUS notifies you when the export process is complete. By default, the exported data saved in the drive:\ibi\WebFOCUS7x\ReportCaster\rc\rc_export directory, along with a log file named export_migration.log.
The export typically contains the following files and folders in addition to the log file:
accessList
addrBook
blackoutDate
execId
library
schedule
Now you can import the exported ReportCaster content into WebFOCUS 8.
In the rcExport2XML program, the file rcLibraryExport2XML.properties has an optional setting called libraryDateRange. This feature allows you to perform a partial migration to export only the Library items you need, rather than all Library items.
For example, you can choose to migrate Library items whose last execution falls within your specified date range. Migrating a smaller amount of data also avoids potential errors that may occur when migrating all of your Library report content.
If the date range parameter is populated, the rcExport2XML program exports all Library versions for any Library report that falls under the execution date stated by libraryDateRange.
Dates for the libraryDateRange setting must be in YYYY/MM/DD format, as shown in the following example:
libraryDateRange=19700105
Where 1970 is the year, 01 is January, and 05 is the 5th day of the month.
Note: When a Library item is selected for migration, all report versions in that Library item are exported. These versions may include versions outside your chosen date range.
The following example shows the libraryDateRange option with no date value, which allows all Library items to be exported.
libraryDateRange=
The following example shows the libraryDateRange option with a date value placed before a comma character, which allows Library items with a last execution date of July 1st, 2016 or later to be exported.
libraryDateRange=20160701,
The following example shows the libraryDateRange option with a comma character placed before a date value, which allows Library items with a last execution date up to and including July 1st, 2016 to be exported.
libraryDateRange=,20160701
The following example shows the libraryDateRange option with a comma character between two dates, which allows Library items with a last execution date between July 1st, 2016 and July 31st, 2016 inclusive to be exported.
libraryDateRange=20160701,20160731
Note: No more than two dates can be used for the libraryDateRange setting.
Note: If you are migrating both Managed Reporting and ReportCaster content, you must perform the Managed Reporting migration before you import ReportCaster content from an earlier release.
Note: If you are licensed for Managed Reporting and want to migrate Managed Reporting content, including WebFOCUS groups and users, you must first complete a Managed Reporting migration.
WebFOCUS notifies you when the import is complete. The log file created from the import is saved in the drive:/ibi/WebFOCUS81/migration_import/rc_export directory.
WebFOCUS notifies you when the import is complete. The log file created from the import is saved in the drive:/ibi/WebFOCUS81/migration_import/rc_export directory.
After migration, ReportCaster content is placed in designated folders in WebFOCUS 8. The migration import creates:
Two folders named ReportCaster and Library Content.
A My Content folder for each user who has migrated ReportCaster content. Schedules, Distribution Lists, and Access Lists that belong to a user are placed in the My Content folder for that user.
Folders for Categories under the Library Content folder. Under each Category folder, the import creates a Library item with the name of the migrated report and adds the report versions to that Library item. If the report is burst, a folder is created with the name of the report and a Library report item is created in that folder for each burst value. The report versions for each burst value are placed in the Library item for that burst value.
A Library Content folder under each domain folder that has Library report output. If that Library output was stored under a Category, the import also creates a Category folder under the Library Content. The Library item with the name of the migrated report is created under the Library Content or Category folder and the report versions are added to that Library item. If the report is burst, a folder is created with the name of the report and a Library report item is created in that folder for each burst value. The report versions for each burst value are placed in the Library item for that burst value.
When a schedule with distribution to a Prepared Report directory is migrated, the FTP Host and Location are set to the values of the Prepared Report directory in the previous installation. This schedule will continue to run, provided that the distribution server in WebFOCUS 8 has FTP access to this location.
If you migrate WebFOCUS 7.x ReportCaster schedules to WebFOCUS 8, and the Reporting Server node referenced in a particular schedule has not been defined in WebFOCUS 8, the migration process will automatically create a Reporting Server node with that name in the ReportCaster configuration file of the WebFOCUS 8 installation.
Migrated Managed Reporting schedules will display the Name information as the WebFOCUS 7.x path (HREF) value. New schedules created in WebFOCUS 8 will display the IBFS path value.
If a Library report from a domain that has been deleted from Managed Reporting is migrated, the report will be placed in a folder in the repository. The folder is named after the original Domain HREF and appended with the words (Domain not Found).
When migrating from WebFOCUS 7.x to WebFOCUS 8, in order to view migrated applet-based graphs in the Report Library, the WebFOCUS 7.x ibi_html alias must exist in WebFOCUS 8.
For example, if you have a WebFOCUS 7.x installation with an alias of ibi_html_7x, you will have a report with a src=ibi_html_7x/javaassist reference. If you install WebFOCUS 8 with an alias of ibi_html_81 and migrate the library from WebFOCUS 7.x, you will not be able to view migrated reports that contain applet graphs. To prevent this, add the ibi_html_7x alias to the application server and point that alias to the WebFOCUS 8 installation. You can have ibi_html_81 for the WebFOCUS 8 installation, but you must also have ibi_html_77 for migrated reports that contain applet graphs to work.
The following image shows the folder structure after a migration import.
As of WebFOCUS Release 8.0 Version 02, there is an alternate migration utility that enables a migration in place, that is, a conversion of a WebFOCUS 7.x repository into a WebFOCUS 8 repository without requiring the export and import of the Report Library. This utility is located in the WebFOCUS81\utilities\WFReposUtil folder and is named upgrade7xDBto8x.bat for Windows and upgrade7xDBto8x.sh for UNIX and Linux. It is available for Oracle, Derby, and Microsoft SQL Server 2008 and 2012 repositories. As of WebFOCUS Release 8.0 Version 09, it is also available for IBM DB2 repositories.
The BOTLDATA table, which contains the report output stored in the Report Library, is the table with the largest amount of data. The new utility allows for migration of existing WebFOCUS 7.x ReportCaster BOT tables to WebFOCUS 8 without dropping the WebFOCUS 7.x BOTLDATA table.
Note: This option should be specified if Managed Reporting content is not being migrated.
As the script is running, you will see the output indicating the status of the migration process. This also provides some insight into the specific tasks that are included in this process.
The following standard migration logs should be used for review of any import errors:
drive:\ibi\WebFOCUS81\utilities\WFReposUtil\WFReposUtilCmdLine.log
drive:\ibi\WebFOCUS81\migration_import\export\mr_migrate_import.log
drive:\ibi\WebFOCUS81\migration_import\rc_export\rc_migrate_import.log
As is the case for all migrated ReportCaster content in WebFOCUS 8, the schedules that run Reporting Server procedures are migrated to the ReportCaster folder. The Report Library content is migrated to the Library Content folder, as shown in the following image.
How to: |
If you are migrating from WebFOCUS 7.x to WebFOCUS 8, you must take additional steps to enable the display of the User Default Role tab in the Security Center and to configure the public user. If the WebFOCUS 7.x public user is named public, the user is migrated to WebFOCUS 8 and assigned the WF_Role_Public UDR. However, if the user has been given another name, the account will be migrated but not automatically assigned the WF_Role_Public UDR. You must manually update this account if you wish to continue using it as the public user.
Regardless of the account name, the WebFOCUS Reporting Server credentials for the public user are not migrated from WebFOCUS 8. The Reporting Server credentials must always be entered manually.
The Administration Console appears
The Security Center appears.
The New User or Edit User dialog box appears, with the Default Role tab enabled, as shown in the following image.
The WebFOCUS Reporting Server credentials for the public user are not migrated from WebFOCUS 8 and must be entered manually. Additionally, if the public user is not named public, the account will be migrated but not automatically assigned the WF_Role_Public UDR. You must manually update this account if you wish to continue using it as the public user.
The Administration Console appears
The Security Center appears.
WebFOCUS |