Usage and Accounting Manager 7.1 Release Notes
- Compatibility issues with earlier versions
- System requirements
- Installing Usage and Accounting Manager 7.1
- Getting started
- Known problems
Usage and Accounting Manager Version 7.1 provides an excellent solution for customers who are seeking to perform resource accounting, cost allocation, and, optionally, chargeback billing based on actual usage of virtually any IT resource across the enterprise — ranging from mainframes to virtualized servers to storage networks and more.
- IBM Tivoli Usage and Accounting Manager Enterprise Edition
- IBM Usage and Accounting Manager Virtualization Edition for System p
- IBM Usage and Accounting Manager Virtualization Edition for System x
- Detailed product description, including a description of new functions
- Product-positioning statement
- Packaging and ordering details
- International compatibility information
Compatibility issues with earlier versions
Compatibility issues are address in the Migrating to Version 7.1 section of the Usage and Accounting Manager 7.1 Information Center. If you are migrating to Usage and Accounting Manager 7.1 from a previous release of Usage and Accounting Manager or CIMS Server, you must follow the migration path outlined in the information center to ensure that your database is successfully converted to the UNICODE format that is now used by Usage and Accounting Manager. In addition, there are other important compatibility issues outlined in the migration section, including:
- Usage and Accounting Manager Version 7.1 does not support Crystal Reports for new installations. Microsoft SQL Server Reporting Services is the supported tool for Web reporting.
- There have been changes to the Acct and Bill programs (formerly CIMSAcct and CIMSBill) in the Processing Engine. These changes include changes to the input files, output files, and control statements that are supported.
- The archive and restore feature has been removed . It is recommended that you use the built-in archive features provided with your database. Usage and Accounting Manager continues to support automated database purge capabilities through the DBPurge process that has been added to the job file structure.
- All job files must be converted to accommodate changes made for Usage and Accounting Manager Version 7.1. Usage and Accounting Manager includes a conversion utility to assist you in converting your job files to the 7.1 format.
- All conversion definitions files must be converted to a job file. Usage and Accounting Manager includes a conversion utility to assist you in converting conversion definitions to job files.
For information about hardware and software compatibility, see the detailed system requirements in the Usage and Accounting Manager 7.1 Information Center. Separate requirements are provided for Linux and UNIX and Windows Server 2003 platforms.
For step-by-step installation instructions, see the installation topics in the Usage and Accounting Manager 7.1 Information Center.
The following is information that will help you to get started using Usage and Accounting Manager. For more information about configuring Usage and Accounting Manager and getting started using the application, see the configuration topics in the Usage and Accounting Manager 7.1 Information Center.
Start Integrated Solutions Console to set up and configure the Usage and Accounting Manager.
Start a Internet Explorer or Firefox Web browser, and type http://<hostname>:11052/ibm/console/ in the address bar. In this case <hostname> defines the server that is running Integrated Solutions Console such as server name or IP address.
If your port number is not the default 11052, replace 11052 with the correct port number. If you have security enabled on, the address will be automatically routed to the secure port.
Configure the appropriate JDBC driver.
JDBC is an application program interface (API) specification for connecting programs written in Java to the data in a wide range of databases. To enable Usage and Accounting Manager Processing Engine to access a DB2, SQL Server, or Oracle database, the appropriate JDBC drivers must be available on the server running Usage and Accounting Manager. The database JDBC drivers are not shipped as part of the install.
If you plan to use the Usage and Accounting Manager Web reporting feature, install Microsoft Report Viewer 2005 SP1.
Usage and Accounting Manager Web Reporting Web site requires an additional component: Microsoft Report Viewer 2005 SP1. If a previous version of the Microsoft Report Viewer is installed, remove it first. The Web Reporting Web site will not run or view reports until the Microsoft Report Viewer 2005 SP1 component is installed.
The following information is specific to Embedded WebSphere Application Server (eWAS), which is used by Usage and Accounting Manager.
eWAS Installation defaults:
- Profile - the default profile defined during installation is: AppSrv01
- Server - the default server defined for profile AppSrv01 during installation is: server1.
- Port - the default port defined during installation is: 11052 (unsecured), 11053 (secured).
Finding your Integrated Solutions Console port number:
If the port 11052 or 11053 are already in use for the Integrated Solutions Console, the port numbers are increased until unused ones are found. To determine the exact port number that is defined for your installation, view the AboutThisProfile.txt file under the path: <Usage and Accounting Manager Install>\was\profiles\AppSrv01\logs. Search for the text: Administrative console port or Administrative console secure port.
Starting and stopping eWAS:
There are scripts for starting and stopping eWAS and (startserver.bat, startserver.sh, stopserver.bat and stopserver.sh) in the <Usage and Accounting Manager Install>\ewas\bin\ directory and the <Usage and Accounting Manager Install>\ewas\profiles\AppSrv01\bin\ directory. The scripts in the ewas\bin directory will work, but it is recommended that you use the scripts in the ewas\profiles\AppSrv01\bin\ directory. The name of the default server defined during installation is server1.
Windows: At the command prompt, start and stop eWAS as shown in the following examples:
- <Usage and Accounting Manager Install>\ewas\profiles\AppSrv01\bin\startserver server1
- <Usage and Accounting Manager Install>\ewas\profiles\AppSrv01\bin\stopserver server1
- <Usage and Accounting Manager Install>/ewas/bin/startServer.sh server1
- <Usage and Accounting Manager Install>/ewas/bin/stopServer.sh server1
Known problems are documented in the form of individual technotes in the Support knowledge base . As problems are discovered and resolved, the IBM Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems.
At time of publication, the following installation and other problems were known:
The VMware data collector errors out. (APAR IZ08385)
When the VMware data collector is run in IBM Tivoli Usage and Accounting Manager 7.1, the initial Integrator stage fails with a severe error message. The following error messages will be written to the VMware job log:
SEVERE: AUCIN0305E The CollectorInput stage failed during the following process: Initialization. Refer to the log messages and trace files to determine the problem and take the appropriate actions. If the problem persists, contact IBM Software Support.
SEVERE: AUCIN0303E The Integrator process ended unsuccessfully with the following exception: com.ibm.tivoli.tuam.integrator.common.IntegratorException: Unable to Initialize Input Process: CollectorInput
Apply the interim fix for APAR IZ08385 that is available on Fix Central. The fix is in a zip file named Patch1.zip. A readme with instructions on how to apply the fix is provided in the zip file.
Reports do not have document maps in the Firefox Web browser. (Defect number 16340)
The document map is the navigation tree on the left pane of many of the reports. If the document map is required, the Usage and Accounting Manager Web Reporting user should use Internet Explorer Version 6 or 7.
Table Manager load issues occur when loading data from one Database Management System (DBMS) to another. (Defect number 19896)
Using Table Manager to move data from one DBMS to another is not supported (for example, Oracle to SQL Server, DB2 to Oracle, and so forth). Moving data from Oracle to Oracle, DB2 to DB2, or SQL Server to SQL Server is supported.
The Rebill.wsf script cannot be run on the following:
- A DB2 for z/OS database. The Rebill.wsf script can be run on a DB2 for Linux, UNIX, and Windows database. (Defect number 19313)
- A 64-bit Windows system. The Rebill.wsf script will fail with the ADODB error when run on a 64-bit Windows system. An error similar to the following is displayed: C:\data\tuam\bin\Rebill.wsf (196, 6) ADODB.Connection: Provider cannot be found. Run the Rebill.wsf script on a 32-bit system. (Defect number 19470)
Long running actions in AUIML/Integrated Solutions Console give no visual progress indication. (Defect number 19518)
Under Internet Explorer 6, long running tasks such as initializing the database, large deletions, and so forth, provide no hourglass, browser status bar, or spinning globe to indicate the process is executing. This leads to potential "second clicks" that cause many errors and can even bring eWAS down. Internet Explorer 7 provides the progress bar, but no hourglass. There are no issues under Firefox, progress is displayed properly.
Running the SampleDeployProcessCollector.xml job file to remove the Windows Processor data collector destroys the Usage and Accounting Manager 6.1 environment. (Defect number 19714)
For the Usage and Accounting Manager application server only. If you install Usage and Accounting Manager 7.1 over a Usage and Accounting Manager 6.1 environment that has the Windows Processor data collector installed, do not remove the collector using the SampleDeployProcessCollector.xml job file (RXA deployment) . The removal process will uninstall most of Usage and Accounting Manager 6.1.
This does NOT affect deployment of the Windows Processor data collector on remote computers.
The WASServiceMsg.dll file remains locked after Usage and Accounting Manager is uninstalled. (Defect number 17969)
When Usage and Accounting Manager is uninstalled from some systems, the <Usage and Accounting Manager Install>\ewas\bin\WASServiceMsg.dll file cannot be removed. Windows considers the file to still be "in use".
The following link provides more information about this problem and resolutions to the problem: WASServiceMsg.dll is locked when installing fix packs and cumulative fixes on Windows.
The Usage and Accounting Manager IBM Support Assistant (ISA) plugin does not display a warning message when Usage and Accounting Manager is not installed on the local computer. (Defect number 19862)
The Usage and Accounting Manager ISA plugin attempts to collect log files even when it is installed on a computer that does not have Usage and Accounting Manager installed locally. After attempting to collect Usage and Accounting Manager log files, the plugin displays a "collection has completed successfully" message.
Although an ISA log collection file has been generated, it will probably not contain meaningful Usage and Accounting Manager log files. A meaningful log file collection will contain files with names that start with a value other than:
Negative rate values are converted to positive values when loaded into the database. (Defect number 20352 )
A rate entered into the Rate table with a negative rate value (normally an adjustment transaction) will be erroneously converted to a positive value by the DBLoad program when the rate is loaded into the Summary table.
Contacting customer support
For information about how to contact IBM Software support, see the Contacting IBM Software Support topic in the Usage and Accounting Manager 7.1 Information Center.