Skip to content
CA Output Management Web Viewer - 12.1
Documentation powered by DocOps

Migrate Data from Release 11 to 12.0

Last update February 11, 2016

Administrators can migrate data from CA OM Web Viewer Release 11 to Release 12.0. Release 12.1 does not support a direct upgrade from Release 11.x. However, most of the configurations can be migrated, using the Release 11.5 Database Export tool in the current version. The tool processes select configuration settings from an 11.0 or 11.5 database. The tool exports the settings to (three) XML files that can be then uploaded into the Version 12.1 administration database through the import feature in Version 12.1.

Important! The CA OM Web Viewer Version 12.1 installation does not replace, or otherwise impact, an existing 11.5 product installation. This includes the database upgrade procedure. The database upgrade does not alter the existing 11.5 database, but, only exports (copies) the 11.5 administrative configuration to a format that can then be imported into the Version 12.1 database.

Supported Configuration Settings

The following definitions can be migrated from the 11.0 or 11.5 database to 12.1:

  • Folder definitions for the DRAS folder are migrated as Repository Objects.
    • The Repository Object name is set to the Folder name.
    • Local and Document Server folders support is dropped for 12.1 and are not migrated.
  • Generic users with folder set definitions are combined and migrated as Role Objects.
    • The Role Object name is set to the (generic) user name.
    • Additionally, Role Objects are derived for defined (non-generic) Users. The Role Object name is set to a value like DerivedRole_00000001.
  • Defined (non-generic users that are defined through the AdmTool) and Personal User accounts are migrated as User Objects.
    • The User Object name is set to the user name.
    • Defined users are assigned to the Role Object derived from the user definition.
    • Personal user accounts are assigned to the Role Object based on its generic user definition.
    • Temporary users (users who log in using generic credentials) are not migrated.

Export the Database

Important! The CA OM Web Viewer r11.5 Database Export can be run from a computer which has access to the Microsoft SQL Server system that holds the r11.0 or r11.5 database. You do not require access to the computer where r12.1 is installed (the copy/move of the resulting XML files are beyond the scope of this application). You can use the export tool on any platform of the CA OM Web Viewer install if a JDBC driver URL is provided.

You can export the database any time after installing and deploying 12.1, but, before the repositories, roles, and users are exported.

Export Using the Console

The Release 11.5 Database Export tool is located in the util directory.

Note: If you chose to install the embedded Apache Tomcat you must start the embedded Apache Tomcat at least once, before you can start the migration tool.

You can now start the application through the console and export the required database.

  1. To begin the export process, execute the following command:

    DVWEB_MigrationTool_Console_mode
    

    The introduction to the application displays.

  2. Review the displayed instructions.
    1. Use the command back to modify a previous step.
    2. Use the command quit to end the export, at any time.
  3. Press Enter to continue.

Enter the Microsoft SQL Server Information

The CA OM Web Viewer r11.5 (or older) database resides on a Microsoft SQL Server. Enter the Microsoft SQL Server information to connect to this database.

  1. Provide the required Microsoft SQL Server information.
    • SQL Node Name
      Defines the name of the computer where the Microsoft SQL Server, that contains the r11.0 or r11.5 database, resides.
    • (Optional) SQL Instance Name
      Defines the Microsoft SQL Server instance name, if you are not using the default instance.

      Note: Press Enter if you have no instance.
    • SQL Port
      Defines the Microsoft SQL Server port. Press Enter to accept the default. If you are not using the default port (likely if using a named instance), enter the port number.
      Default: 1433
    • SQL UserID
      Defines the Microsoft SQL Server user ID.
    • SQL Password
      Defines the Microsoft SQL Server password.
    The SQL information is validated and the CA OM Web Viewer databases are detected. If the information is incorrect, you are prompted to start again.

Select the Database

You can select the required Microsoft SQL Server database from the list of displayed databases, by its number, and then press Enter.

Example

Select the SQL Database by number:
        1       dvweb_r11       11.5

If the database you want to export is not displayed, you can exit through the quit command or change Microsoft SQL Server information through the back command.

Specify the Output Folder

You can specify the output folder directory to receive the XML files (exported settings).

If the specified folder does not exist or you do not have sufficient write permissions, you are prompted to specify another folder.

The output files on the USS platform are written in EBCDIC encoding. Convert these files to ACSII before you use the files. Use the ftp command from the windows command line, and download the file in ASCII mode. This download converts the EBCDIC files to ASCII automatically.

Enter the CCI Server Information

The export tool has to resolve mainframe repository information which entails a DRAS Discovery. This can be bypassed for the following:

If the Common Communications Interface (CCI) Server is not accessible, enter yes.

If you select this option, the repository type value is incorrect for any non-CA View repository. You can review and correct the values, after import into r12.1, through repository administration.

If all repositories are defined as CA View, you can select (yes) Bypass DRAS Discovery for a quicker export.

  1. Complete the following information:
    • Bypass DRAS discovery
      Defines if you want to perform DRAS Discovery.
      Default: no
    • CCI (Common Communications Interface) Server
      Defines the CCI Server (mainframe name or IP address).
    • CCI (Common Communications Interface) Port
      Defines the CCI Server Port number.
      Default: 1202

Review the Options and Complete the Export

Review the entered information and your options through the selection summary and make any required changes.

Example

  • SQL Node Name
    nnnnn-sqlsrv.ca.com
  • Port
    1433
  • SQL UserID
    userid
  • SQL Password
    password
  • Database Name
    dvweb_r11
  • Output Directory
    d:\temp
  • CCI (Common Communications Interface) Server
    nnnnn.ca.com
  • CCI (Common Communications Interface) Port
    1202

Press Enter to export the database.

When the export is complete, the file names and folder are listed in the results.

Example

DRAS Discovery

Connecting to the source database...
0% done

Creating Repository records...
5% done

Creating Role records...
20% done

Creating User records...
50% done

Disconnecting from the source database...
70% done

Preparing data for export...
75% done

Export ending...
99% done
Export Complete.  Files...
Repository.xml
Role.xml
User.xml
created in folder
d:\temp.

Import the Database

Note: For information about how to use the Admin Import interface, see the Online Help.
  1. Log in to [set to your product name] r12.1 using an account that has System Admin privileges.
  2. Select the Administration tab, sub tab Repositories.
  3. Click Import (above the Repository list).
    The Admin Object Import form displays.
    The output files on the USS platform are written in EBCDIC encoding. Convert these files to ACSII before you use the files. Use the ftp command from the windows command line, and download the file in ASCII mode. This download converts the EBCDIC files to ASCII automatically.
  4. Select Repository, and then browse and select the Repository.XML file that was created during export.
  5. (Optional) Select Role and User, and then browse and select the Role.XML and User.XML files that were created during export. If you are doing individual imports, use the following order:

    • Repository
    • Role
    • User

    Otherwise, Repository-to-Role and Role-to-User assignments can be lost.

  6. Click Import to perform the import.
    1. If Role.XML was not previously processed, select the sub tab Roles and then repeat steps 3-6 for Roles.
    2. If User.XML was not previously processed, select the sub tab Users and then repeat steps 3-6 for Users.

Review the Resulting r12.1 Objects

After you import the repositories, roles, and users into Web Viewer Version r12.1, it is important to review the resulting r12.1 objects.

  • Review Repository objects

    Important! If the DRAS Discovery was either bypassed during the r11.0 or r11.5 export or the DRAS tasks were inactive or inaccessible, the Repository Type is incorrect for any CA Dispatch or CA Bundl repository. You can correct the Repository Type before users can access.
    • If you plan to use DRAS load balancing, select Alternate Locations for the affected repositories.
    • Review and update, the repository Definition and Properties as needed.
    • Index rules defined in r11.5 are not exported. Rules must be redefined through Properties, Filter under the Index Filter section.
  • Review Role objects
    • Nongeneric users defined in r11.0 or r11.5, derived roles are exported to Version r12.1. The result Role Object names are set to values like DerivedRole_00000001 (the actual name can be localized). Rename as appropriate.
    • Roles that are created from generic users are named after the generic account. Rename as appropriate.
    • Review and update the role Definition and Properties. In particular, the Role Type, as needed.
  • Review User objects
    • Review and update the user information as needed.
Was this helpful?

Please log in to post comments.