Contents Upgrading BFInventory iii

Transcription

1 Upgrading

2 ii Upgrading

3 Contents Upgrading Upgrading to IBM Tivoli Endpoint Manager for Software Use Analysis version Planning and preparing for the upgrade Installing the server Configuring the connection to the Tivoli Endpoint Manager database Migrating the BFInventory database Migrating the catalog into IBM Tivoli Software Knowledge Base Toolkit iii

4 iv Upgrading

5 Upgrading Use this section to learn how to upgrade from IBM Tivoli Endpoint Manager for Software Use Analysis version 1.3 to version 2.0. Upgrading to IBM Tivoli Endpoint Manager for Software Use Analysis version 2.0 You upgrade the Software Use Analysis server from version 1.3 to 2.0 by installing a new instance of the server and then migrating the data. About this task Upgrading to Software Use Analysis 2.0 is optional. If you want a slower transition, you can run version 1.3 and 2.0 side-by-side without having to uninstall the Software Use Analysis 1.3 server. However, if you put significant effort into customizing you users, groups, computer properties, or software catalog and you want to migrate this data into Software Use Analysis 2.0, it is better to upgrade. Click the steps in the diagram to view the selected topics Start the upgrade Plan and prepare for the upgrade Install the new instance of Software Use Analysis server Configure the connection to the Tivoli Endpoint Manager database Migrate the BFInventory database 1. Plan and prepare for the upgrade Before you upgrade, review the prerequisites and types of data that are migrated during the upgrade. 2. Install the new instance of Software Use Analysis server Use the interactive installer to specify all parameters as the installation proceeds. 3. Configure the connection to the Tivoli Endpoint Manager database After you install the server, set up the connection to the Tivoli Endpoint Manager database. 4. Migrate the BFInventory database After you connect to the Tivoli Endpoint Manager database, migrate the BFInventory database. You must also specify the credentials of the database administrator. 5. Optional: Migrate the catalog into IBM Tivoli Software Knowledge Base Toolkit If you want to preserve catalog customizations in Software Use Analysis 2.0 you must migrate the software catalog from Software Use Analysis 1.3 to Software Knowledge Base Toolkit. If you have no customizations that you want to migrate, you can skip that task. Migrate the catalog to Software Knowledge Base Toolkit Start using the product 1

6 Planning and preparing for the upgrade Before you upgrade to Software Use Analysis version 2.0, review the upgrading prerequisites and the types of data that are migrated during the upgrade. Before you begin When you use Windows Auth to connect to Tivoli Endpoint Manager server database in Software Use Analysis 1.3 and you install Software Use Analysis 2.0 on a different computer, you need to make sure that the Windows Auth user is able to connect to Tivoli Endpoint Manager database with the same credentials from Software Use Analysis 2.0 computer. Otherwise, you will loose computer properties mapping during migration. About this task Procedure 1. Review the hardware and software prerequisites. 2. Review the types of data that can be migrated: Users Only active (not deleted) users are migrated. Contracts and saved reports Contracts and saved reports are not migrated. You can find information about contracts and saved reports in the migration log. Roles Roles are not migrated. Computer groups All computer groups must be migrated. Data sources Multiple data sources are supported. Important: To migrate the data, the Software Use Analysis 2.0 server must be able to access the Software Use Analysis 1.3 database. If you install both versions of the application on the same computer, you can set the path to the database as the localhost. If you install each version on a separate computer, you must provide a valid network path to the database server. 3. Optional: To verify the upgrade and migration process, examine the information that is stored in the following log file: SUA_INSTALLATION_DIRECTORY\work\tema\webapp\WEB-INF\log\ settings_migration.log 4. Prepare the image for upgrading the server. Installing the server Use the installation wizard to specify all parameters as the installation proceeds. Before you begin Microsoft SQL server is a prerequisite for Tivoli Endpoint Manager for Software Use Analysis. Install and configure the database software before starting this procedure. Procedure 1. Copy the tema.msi file to a temporary directory on the computer hard disk and double-click to begin installation. A welcome pane opens. 2 Upgrading

7 2. Read carefully the terms of the license agreement, and if you accept them all, select I accept the terms of the license agreement, and click Next. Otherwise click Cancel to quit the installation. 3. Accept or modify the default installation path, accept, or change the port that is to be used by the HTTP server running on the server computer. Click Next. 4. Specify the user account that runs the Software Use Analysis service. If you configure Software Use Analysis to connect to the SQL Server through a user that is authenticated by Windows authentication, the Software Use Analysis service must be configured to run as that same user. Select This account, and provide the user name and the password of the user account. Click Next. A summary panel opens. 5. Click Install. The installation of the Software Use Analysis server begins. 6. When the process finishes, select Launch browser to complete configuration, and click Finish to exit the installer. The final panel prompts you to start a web browser to complete the setup. What to do next After the installation, use the server web interface to complete the server setup. If you configure the system at a later time, you must start a supported web browser on the Software Use Analysis server and go to replacing port with the port that you configured during the installation. Important: You can do the initial setup only from the localhost. Configuring the connection to the Tivoli Endpoint Manager database The first task after installing the server is to set up the connection to the Tivoli Endpoint Manager database. Procedure 1. On the main configuration page of the Tivoli Endpoint Manager console, set up the connection to the Tivoli Endpoint Manager for Software Use Analysis database: a. Enter the host and database name. b. Select one of the types of authentication: v Windows Authentication v SQL Server Authentication In this scenario, the SQL Server Authentication option is described. c. Enter the Username, and Password. d. Click Create to connect to the Software Use Analysis database. A new pane opens. 2. Click Skip migration if you do not want to migrate the database. 3. Create the administrator account: provide the user name and password, confirm the password, and click Create. The last pane opens. 4. Connect to the IBM Tivoli Endpoint Manager database: a. Enter the host and database name. b. Select one of the types of authentication: v Windows Authentication v SQL Server Authentication Upgrading 3

8 In this scenario, the SQL Server Authentication option is described. c. Enter the User name, and Password. d. Click Create to connect to the Tivoli Endpoint Manager database. Note: You can also set up the web reports database by providing the same information on the right side of the pane. Migrating the BFInventory database After you connect to the Tivoli Endpoint Manager database, migrate the BFInventory database. About this task Migration of the Software Use Analysis 1.3 database is a read-only process. After the migration, you can continue using the database with Software Use Analysis 1.3. You can also discard the database if you plan to use only Software Use Analysis 2.0. Procedure 1. On the main configuration page, set up the connection to the Tivoli Endpoint Manager for Software Use Analysis database: a. Enter the host and database name. b. Select the authentication type: v Windows Authentication v SQL Server Authentication In this scenario, the SQL Server Authentication option is described. c. Enter the Username and Password. d. To connect to the Software Use Analysis 1.3 database, click Create A new pane opens. 2. On the migration configuration page, set up the connection to the BFInventory database: a. Enter the host name and, in the database name field, specify BFInventory. b. Select the authentication type: v Windows Authentication v SQL Server Authentication In this scenario, the SQL Server Authentication option is described. c. Specify the Username and Password of the user who is to authorize the connection to the version 1.3 BFInventory database, and click Create. d. To start the migration process, click Migrate. Tip: You can also set up the web Reports database by providing the web reports database information about the right side of the pane. If the web Reports database is not specified, web report users are not migrated. After the migration finishes, the login page opens. e. Log in to the application with your credentials from Software Use Analysis Upgrading

9 Migrating the catalog into IBM Tivoli Software Knowledge Base Toolkit To migrate catalog customizations from Software Use Analysis 1.3 to Software Knowledge Base Toolkit, you must migrate the software catalog. Use a converter tool to generate a canonical 2.0 XML file that contains the software catalog customizations, and then import the file into Software Knowledge Base Toolkit. Before you begin Before you can migrate the catalog, you must have: v The Software Use Analysis 1.3 to Canonical 2.0 converter tool that consists of the following two files: sua1tocan2.bat sua1tocan2.jar v v The files are stored in the installation catalog of Tivoli Endpoint Manager for Software Use Analysis 2.0 The following software installed in your infrastructure: IBM Tivoli Endpoint Manager for Software Use Analysis 1.3 IBM Tivoli Endpoint Manager for Software Use Analysis 2.0 IBM Tivoli Software Knowledge Base Toolkit Read, write, and execute permissions for the Tivoli Endpoint Manager for Software Use Analysis 2.0 home directory. About this task Migrating the catalog is necessary only if you have catalog customizations that you want to preserve in Software Use Analysis 2.0. It is not required if you want to use the latest catalog published by IBM with no customizations from Software Use Analysis 1.3. Procedure 1. Open the Windows Command Prompt, and change to the Software Use Analysis 2.0 home directory. 2. To generate a canonical XML 2.0 file, run the sua1tocan2.bat batch file by using one of the following commands: v To use Integrated Windows Authentication to access the SQL server: sua1tocan2.bat output_catalog.xml db_hostname db_name v To specify Software Use Analysis 1.3 database credentials and use SQL Server Authentication: sua1tocan2.bat output_catalog.xml db_hostname db_name db_user db_password Where: output_catalog.xml Is the name of the canonical XML 2.0 catalog file that is created by the tool. If this file is already present on the file system, it is overwritten. db_hostname Is the Software Use Analysis 1.3 database host name. db_name Is the Software Use Analysis 1.3 BFInventory database name. Upgrading 5

10 db_user Is the Software Use Analysis 1.3 database user name. db_password Is the Software Use Analysis 1.3 database password. 3. In the Software Knowledge Base Toolkit navigation bar, select Manage Imports > Canonical XML Document. 4. Click New Import. 5. In the New Canonical XML Import window: a. Enter a name for the import task. b. Optional: To choose advanced mode instead of overwrite mode, clear the Overwrite knowledge base content check box. c. Provide a reason for importing the document into the knowledge base. All entries that are created or modified as a result of the import include the reason in their history event records. d. To select the XML file that you want to import, click Browse. e. To start importing the file, click OK. When the import finishes, the status of the import process changes from Processing changes to Completed or to Conflicting. 6. If the status of the task is Conflicting, you must resolve all conflicts: a. Open the task. b. Select a conflict area from the Conflict Area column. c. Resolve each conflict, select either the Resolve using existing or Resolve using incoming option. After you finish, the value in the Unresolved conflict column must be 0. d. In the Canonical Import Details window, select all items and click Reimport areas. e. Confirm that you want to rerun the import for the chosen areas. f. Enter a reason for the import. What to do next After you migrate catalog customizations from Software Use Analysis 1.3 to Software Knowledge Base Toolkit, you must import the updated catalog from Software Knowledge Base Toolkit to Software Use Analysis Upgrading