BMC Portal

Release Notes

Version: 2.4.00

May 31, 2007

BMC Software is releasing version 2.4.00 of the BMC Portal product. These release notes provide information about the enhancements, resolved problems, and open issues in this version. This information supplements and supersedes information in the documents listed in "BMC Portal documents".

---

NOTE:

Before you install the BMC Portal, BMC Software recommends that you check the Customer Support web page at http://www.bmc.com/support_home for updated information about this version. Flashes, technical bulletins, and solutions on the support web page provide the latest information, including details about any fixes that were issued for this version after its release.

---

Overview of BMC Portal

Internationalization and localization

Requirements and supported resources

BMC Portal requirements

Additional system requirements for modules

Installation information

What’s new

What’s changed

Product download from the web

Product installation issues

Product upgrade paths

Product upgrade issues

What’s new in BMC Portal Server

Integrating the Portal with AlarmPoint 3

Open issues and workarounds in BMC Portal Server

Corrected problems in BMC Portal Server

BMC Performance Manager Portal 2.4.00

What’s new in BMC Performance Manager Portal

What’s changed in BMC Performance Manager Portal

Open issues and workarounds in BMC Performance Manager Portal

Corrected problems

BMC Performance Manager SDK 2.4.00

What’s new in BMC Performance Manager SDK

What’s changed in BMC Performance Manager SDK

Open issues and resolutions in BMC Performance Manager SDK

Corrected problems in BMC Performance Manager SDK

BMC Performance Exception Detector 1.3.10

What’s new in BMC Performance Exception Detector

Open issues and workarounds in BMC Performance Exception Detector

BMC Impact Portal 7.0.02

Version compatibility between BMC Impact Portal and BMC Impact
Manager 46

What’s changed in BMC Impact Portal

Open issues and workarounds in BMC Impact Portal

Corrected problems for BMC Impact Portal

BMC Impact Service Model Editor (SME) 7.0.02

What’s changed in BMC Impact Service Model Editor

Open issues and workarounds in BMC Impact Service Model Editor

Corrected issues in BMC Impact Service Model Editor

BMC Impact Publishing Server 7.0.02

What’s changed in BMC Impact Publishing Server

Open issues and workarounds in BMC Impact Publishing Server

Corrected issues in BMC Impact Publishing Server

BMC Impact Integration Web Services 2.2.00

What’s new in BMC II Web Services Server

What’s changed in BMC II Web Services Server

Open issues and workarounds in BMC II Web Services Server

Corrected issues in BMC II Web Services Server

Requirements and supported resources

Support for BMC II Web Services Server

Support for BMC Portal

Levels of support

BMC Portal documents

Where to view the latest product information

How to order the products

Customer support

Overview of BMC Portal

The BMC Portal (the Portal) provides a common, web-based interface for BMC Software modules. Each module provides programs that integrate with the BMC Portal server and other modules in the Portal. This integration provides data from multiple sources to a single, customizable entry point for viewing the status and performance of your infrastructure, exceptions, and business service environment.

At any time, you can access pages that provide different views of your account and the objects that compose the account.

This version of BMC Portal includes the following modules, and each module is licensed separately:

Component	Version
BMC Performance Manager Portal	2.4.00
BMC Performance Exception Detector	1.3.10
BMC Impact Portal	7.0.02

The BMC Performance Manager Portal module uses agentless and agent-based technologies to monitor IP-addressable infrastructure. If you use PATROL Agent 3.5.x or later in your environment, you can integrate its agent-based technology with the Portal, enabling you to view your entire infrastructure from a single point. For more information about this module, see "BMC Performance Manager Portal 2.4.00".

The BMC Performance Exception Detector module enables you to integrate your existing BMC Performance Assurance environment with the BMC Portal to identify performance and capacity issues that require attention before they impact key business services. For more information about this module, see "BMC Performance Exception Detector 1.3.10".

The BMC Impact Portal module provides views of business services and shows how the status of these services is impacted when infrastructure components have problems. With these views, you can understand how infrastructure problems affect the business services used by your company. For more information about this module, see "BMC Impact Portal 7.0.02".

Table 1 shows the relationship between the features and the modules available in the BMC Portal, as well as other BMC Software products required for the module.

Table 1 Relationship between BMC Portal features and the Portal modules 

Type of environment	BMC Portal features	Module to select during installation	Other BMC products required
BMC Performance Manager (agentless)	agentless monitoring provided by the Portal and RSM program	BMC Performance Manager Portal	Performance Managers
PATROL (agent-based)	agent-based monitoring provided by the Portal, the RSM program, and PATROL Agents	BMC Performance Manager Portal	PATROL Knowledge Modules and PATROL Agents
BMC Performance Assurance	automatic summarization and trend identification for key performance exceptions provided by the Portal and the Exception Detector data service	BMC Performance Exception Detector	BMC Performance Assurance, BMC Visualizer
BMC Service Impact Manager	web-based common user interface for service impact management and reporting; centralized user administration	BMC Impact Portal	BMC Impact Manager

For more information about the features in the BMC Portal modules, see the Help and the documents described in "BMC Portal documents".

Internationalization and localization

Table 2 lists the platforms on which the BMC Portal runs and the languages in which you can view the product.

Table 2 Internationalization and localization support for BMC Portal modules

Module	French		German		Japanese		Korean		Simplified Chinese		Traditional Chinese
	Runs a	View	Runs	View	Runs	View b	Runs	Viewb	Runs	Viewb	Runs	Viewb
BMC Performance Manager Portal	²		²		²	²	²		²	²	²	²
BMC Performance Exception Detector c
BMC Impact Portal	²		²		²		²		²		²

a Product executes in the operating system for the specified language and can also accept input, process, and display data in that language. b To display the user interface in a different language, users and administrators must log on and change the default language settings. a This module operates only in English.

The online Help for all modules is displayed in English. The default language settings for Portal users and administrators is English.

Requirements and supported resources

This section provides release-specific information about requirements and supported resources for BMC Portal 2.4.00. For requirements that are specific to a module, see the section for that module in this document.

BMC Portal requirements

Table 3 shows the supported platforms for the Portal and Table 4 on page 6 and Table 5 on page 7 on the following pages list specific requirements for each platform.

Table 3 Platform matrix for BMC Portal

Operating system	Web and application servers	Database server	Web browsers				RSM a
			Firefox		Internet Explorer
			1.5	2.0	6.x	7.x
Sun® Solaris 8 (64-bit), Sparc	²	²	²	²
Sun Solaris 9 (64-bit), Sparc	²	²	²	²
Sun Solaris 10 (64-bit) b , Sparc	²	²	²	²
Microsoft Windows 2003 (x86) Standard Server (32- and 64-bit)	²	²	²	²	²	²	²
Microsoft Windows 2003 (x86) Enterprise Server (32- and 64-bit)	²	²	²	²	²	²	²
Microsoft Windows 2003 (x86) Datacenter Server (32- and 64-bit)	²	²	²	²	²	²	²
Microsoft Windows 2003 (x86) Web Server (32- and 64-bit)	²	²	²	²	²	²	²
Microsoft Windows 2000 (x86) Server	²	²	²	²	²		²
Microsoft Windows 2000 (x86) Advanced Server	²	²	²	²	²		²
Microsoft Windows 2000 (x86) Datacenter Server	²	²	²	²	²		²
Microsoft Windows 2000 (x86) Professional			²	²	²
Microsoft Windows XP (x86)			²	²	²	²

b The RSM is applicable for BMC Performance Manager Portal module only; Table 6 on page 9 contains specific system requirements for the RSM. c Zone support is optional.

Table 4 on page 6 lists the minimum requirements necessary for entry-level deployment of the BMC Portal. Any additional requirements for the BMC Portal, its modules, and the database are listed later in this document, the BMC Portal Installation Guide, and the BMC Performance Manager Portal Performance and Scalability Guidelines document. You can find the BMC Performance Manager Portal Performance and Scalability Guidelines document on the BMC Performance Manager Portal 2.4.x Support website at http://www.bmc.com/support_home.

Table 4 BMC Portal application server and web server system requirements (part 1 of 2)1

Resource	Minimum requirements	Comments
platform	either of the following processors: Intel compatible (32-bit) Pentium 4 processor or equivalent AMD Opteron/Intel Xeon 64 EM64T processor (64-bit)	minimum of 2 CPU 3.2 GHz processor (with hyperthreading enabled) minimum of 4 GB RAM Ultra320 SCSI disk subsystem
	UltraSPARC IIIi equivalent or later	2 CPU 1.28 GHz minimum of 4 GB RAM a high-performance disk subsystem recommended if you install datastore on same computer
disk space	Windows: 200 GB available Solaris: 200 GB available	Solaris requires 250 MB in /var/tmp for installation program
operating system	Microsoft Windows 2000 Server (32-bit)	requires a user account with administrator rights and permissions Service Pack 4 or later; BMC Software recommends the latest Service Pack
	Microsoft Windows 2003 Server (32-bit, 64-bit)	requires a user account with administrator rights and permissions Service Pack 1 or later; BMC Software recommends the latest Service Pack
	Sun Solaris 8 (64-bit), Sparc Sun Solaris 9 (64-bit), Sparc Sun Solaris 10 (64-bit), Sparc	The web server component requires the following items: random patch on Solaris 8 b libsendfile.so.1 on Solaris 8 c libiconv library d libuuid patch e
third-party products	running SMTP server (optional)	The installation program verifies the presence of a running email server.
	J2SE Java Runtime Environment (JRE) on client computers f	The BMC Portal Help requires version 1.4.2 or later. If necessary, you can download the latest JRE from the Java download site at http://www.java.sun.com.
	Network Time Protocol (NTP) (recommended)	NTP continuously adjusts the time on a computer to match that of another computer, typically the atomic clock.
BMC Software products	BMC Atrium CMDB	The BMC Atrium CMDB is not required, but the BMC Performance Manager Portal can integrate with version 2.0.01 patch 3 or later.
web browser	One of the following browser versions: Firefox 1.5 or 2.0 Microsoft Internet Explorer (IE) 6.x or 7.x	The IE browser on Windows 2003 requires the medium security setting. Do not run BMC Portal with the high security setting.

b Disk space and memory requirements do not include the BMC Datastore. For these requirements, see Table 5. c You can download this patch from http://sunsolve.sun.com/search/document.do?assetkey=112438. You must reboot the computer after you install the patch. d To obtain this library, install Sun patch 111297-01 or later. You can download this patch from http://sunsolve.sun.com/search/document.do?assetkey=111297. e See the BMC Portal Installation Guide for the download locations of the libiconv library. f See the BMC Portal Installation Guide for the download locations of the libuuid patch. You must reboot the computer after you install the patch. a Full access to the BMC Portal Help requires the JRE on the computer that you use to access the Portal. If you do not have the JRE installed, you can still access the Help, but some of its navigation tools will be inoperable.

Table 5 BMC Datastore system requirements (part 1 of 2)1

Resource	Minimum requirements	Comments
platform	Intel compatible (32-bit) Pentium 4 processor or higher	minimum of 2 CPU 3.06 GHz processor (with hyperthreading enabled) 2 GB RAM dedicated to the datastore Ultra320 SCSI disk subsystem
	UltraSPARC IIIi equivalent or higher	2 CPU 1.28 GHz processor 2 GB memory external Ultra320 SCSI 10K RPM disk subsystem
disk spacea	trial 5 GB (initial requirement) 40 GB (required after 428 days)	Solaris also requires the following temporary space: /tmp: 400 MB (for database component) /var/tmp: 250 MB (for installation program) /opt: 50 MB (for database component) Note: Monitoring infrastructure with the BMC Performance Manager Portal affects the disk space required for each of the datastore models. For database sizing requirements, see the BMC Portal Installation Guide. If you install any of the other modules (without the BMC Performance Manager Portal), select the smallest database size.
	small 60 GB (initial requirement) 200 GB (required after 428 days)
	medium 90 GB (initial requirement) 350 GB (required after 428 days)
	large 175 GB (initial requirement) 550 GB (required after 428 days)
operating system	Microsoft Windows 2000 Server (32-bit)	requires a user account with administrator rights and permissions Service Pack 4 or later; BMC Software recommends the latest Service Pack
	Microsoft Windows 2003 Server (32-bit, 64-bit)	user account with administrator rights and permissions Service Pack 1 or later; BMC Software recommends the latest Service Pack
	Solaris 8 (64-bit), Sparc Solaris 9 (64-bit), Sparc Solaris 10 (64-bit), Sparc	installing user account with root privileges The datastore requires the following packages on Solaris: SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWtoo
Oracle® database	version 10.2.0.2 or later with partitioning enabled and the January 2007 Critical Patch Update (CPU) installed	You can use the BMC Datastore installation program to install Oracle and create the Portal database instance, or you can use an existing Oracle database installation and manually configure it. For installation prerequisites and instructions, see the BMC Portal Installation Guide.

b Disk space and memory requirements do not include the Portal web server and application server. For additional requirements, see Table 4 on page 6.

Additional system requirements for modules

The modules that you choose to install can add system requirements for the BMC Portal.

Remote Service Monitor system requirements for BMC Performance Manager Portal module

The BMC Performance Manager Portal module requires that you install at least one instance of the Remote Service Monitor (RSM) program on the Portal server or another computer. When installing the BMC Performance Manager Portal, ensure that the computers on which you want to install the RSM program meet the system requirements listed in Table 6 on page 9. You can install only one instance of the RSM program on any computer.

Table 6 System requirements for RSM program 

Resource	Minimum requirements	Comments
platform	Intel Pentium 4 or equivalent	2 CPU 3.06 3 GHz processor (with hyperthreading enabled) 2 GB RAM dedicated to the RSM IDE disk subsystem 2 GB disk space
operating system	Microsoft Windows 2000 Server a	Service Pack 4 or later; BMC Software recommends the latest Service Pack
	Microsoft Windows 2003 Server	Service Pack 1 or later; BMC Software recommends the latest Service Pack
third-party products	NTP (recommended) b	NTP continuously adjusts the time on a computer to match that of another computer, typically the atomic clock.

a To monitor Windows services and event logs, you also need to apply a hot fix from Microsoft. See the following Microsoft Knowledge article for more information: http://support.microsoft.com/default.aspx?scid=kb;EN-US;911262 b Install NTP on the Portal server and each of the RSM computers to ensure that the system clocks on the RSM computers are in sync with the system clock on the Portal computer.

BMC Performance Exception Detector data service requirements

The BMC Performance Exception Detector module accesses data from BMC Visualizer databases through the use of a data service program. The data service consolidates the connections for multiple databases, runs the daily scans and any test scans, presents the lists of exceptions to the Status, Events, and Reports tabs in the BMC Portal, and provides a service to automatically generate or update statistical analysis policies.

If you are upgrading from BMC Performance Exception Detector version 1.1, you must also upgrade to version 1.3.10 of the data service. You install the data service on the computers where you have BMC Visualizer and BMC Automator installed.

See the BMC Performance Exception Detector Implementation Guide for the complete list of requirements and installation instructions for the BMC Performance Exception Detector data service program.

Installation information

This section highlights changes to the installation process for this release. For complete planning information and procedures for installing the BMC Portal, see the BMC Portal Installation Guide.

What’s new

The BMC Datastore and BMC Portal installation programs have been enhanced with the following new features.

Updated platform support

You can now install the BMC Datastore on computer with Solaris 10 operating system.

Support for Solaris nonglobal zones

You can now install the BMC Datastore and the BMC Portal in different nonglobal zones on the same Solaris 10 computer. For guidelines for configuring the zones, see the BMC Portal Installation Guide.

Installation of loopback adapter required for Windows computers using DHCP

If you will be installing the BMC Datastore on a computer that uses the Windows Dynamic Host Configuration Protocol (DHCP) service, you must install and configure a loopback adapter before you install the BMC Datastore. For details, see the BMC Portal Installation Guide.

What’s changed

This section describes changes in the BMC Datastore and BMC Portal installation programs.

Updated Oracle version support

The BMC Portal now requires Oracle version 10.2.0.2 for the BMC Datastore. You can use the BMC Datastore installation program to install or upgrade to version 10.2.0.2. For details about BMC Portal versions that you can upgrade, see "Product upgrade paths". For details about prerequisites for installing and upgrading, and for installation and upgrade instructions, see the BMC Portal Installation Guide.

Process name changes for Portal application server and web server

The process name for the Portal application server on Solaris has changed from java to BMCPortal.

The process name for the Portal web server on Solaris and Windows has changed from BMCWebserver to BMCPortalWebserver.

Name changes for installation and uninstallation programs

Table 7 lists the changes for this release.

Table 7 Name changes for installation and uninstallation programs

Components	Platform		Old name	New name
BMC Datastore, BMC Portal, RSM	Windows	installation	setupwin32.exe	setup.exe
		uninstallation	uninstaller.exe	uninstall.exe
BMC Datastore, BMC Portal	Solaris	installation	setupsolarisSparc.bin	install
		uninstallation	uninstaller.bin	uninstall
BMC Datastore		uninstallation	scrubber tool	cleanup tool

For details for using the cleanup tool, see the BMC Portal Installation Guide.

Archive logging turned off during datastore upgrade

In previous versions of the BMC Datastore, if you configured the database for ARCHIVELOG mode, the installation program would not change this setting during an upgrade of the datastore. In this release, the installation program disables archive logging for the datastore upgrade. You must use the BMC Datastore installation tool to enable it again after the upgrade of both the datastore and Portal are completed.

Product download from the web

This section contains instructions for downloading and installing the BMC Portal from the BMC Software Electronic Product Download (EPD) web page, http://www.bmc.com/ega/. You might want to print these instructions or save this file to reference later.

---

NOTE:

If you download BMC Portal 2.4.00 from the BMC Software EPD web page, the product file that you download might contain some or all of the patches listed on the product’s BMC Software Customer Support web page. If the EPD page shows that a patch is included in the product file, then you do not need to obtain that patch.

---

Contact your Sales Representative for the user name and password that you will need to access the product download page.

To download the product from the web

1 Create a temporary directory on your computer.

---

NOTE:

On Windows computers, ensure that the temporary directory that you create is only one directory level into the directory structure. The EPD package creates a directory in the temporary directory when you extract the files, and the directory that contains the installation image should not be located in a directory deeper than two levels into the directory structure.

---

2 From the EPD web page, http://www.bmc.com/ega/, access the page for BMC Performance Manager Infrastructure and Solutions.

3 Select BMC Performance Manager Portal.

4 On the BMC Performance Manager Portal page, select BMC Portal.

5 On the BMC Portal page, right-click Release Notes, and select Save Target As.

6 Select one of the following platforms to download:

BMC Portal 2.4.00 (Windows)

BMC Portal 2.4.00 (Solaris)

Supplemental Materials

The Supplemental Materials option contains open source third-party programs used in the BMC Portal product. You do not need these files to install or run the product.

7 Click Continue.

8 Click BMC Portal Documentation and save to the temporary directory.

9 Click Download Product File for the BMC Portal 2.4.00 Infrastructure and save to the temporary directory that you created in step 1 on page 12.

10 Click Download Product File for the BMC Datastore 2.4.00 and save to the temporary directory that you created in step 1 on page 12.

For Windows platforms, select the file that is applicable for your operating system, either 32-bit or 64-bit.

11 Return to the BMC Performance Manager Infrastructure and Solutions page, download the BMC Performance Manager Portal Solutions to a different temporary directory from the one that you used for the BMC Portal and the BMC Datastore, and extract the file.

For details about downloading the BMC Performance Manager Portal Solutions, see the BMC Performance Manager Solutions Release Notes.

12 Using the release notes and the BMC Portal Installation Guide, carefully review the installation requirements and prerequisites for your platform.

Some prerequisites are tasks that you must perform before you launch the installation programs.

13 Use one of the following procedures to install the product in a Windows or Solaris environment:

To install the downloaded product on Windows. See page 14

To install the downloaded product on Solaris. See page 14.

To install the downloaded product on Windows

1 Navigate to the temporary directory that you created in step 1 on page 12.

2 To extract the datastore files from the archive in the temporary directory, double-click datastore_32_ALL_2400.exe or datastore_64_ALL_2400.exe.

The bmc_products directory is created and the files are extracted to the bmc_products\BMCDatastore directory.

3 To extract the Portal files from the archive in the temporary directory, double-click PORTAL_ALL_2400.exe.

The files are extracted to the bmc_products\BMCPortalKit directory.

4 From the bmc_products\BMCDatastore\disk1 directory, run setup.exe to launch the BMC Datastore installation program.

5 Using Chapter 5 in the BMC Portal Installation Guide, follow the procedure for installing the BMC Datastore.

6 After completing the BMC Datastore installation, from the bmc_products\BMCPortalKit\disk1 directory, run setup.exe to launch the BMC Portal installation program.

7 Using Chapter 5 in the BMC Portal Installation Guide, follow the procedures for installing the BMC Portal application server, web server, modules, and Performance Managers, depending on your installation scenario.

8 After completing the installations, you can delete the temporary directory and its contents.

To install the downloaded product on Solaris

1 Navigate to the temporary directory that you created in step 1 on page 12.

2 To extract the datastore files from the archive in the temporary directory, untar the datastore_ALL_2400.tar file.

The bmc_products directory is created and the files are extracted to the bmc_products/BMCDatastore directory.

3 To extract the Portal files from the archive in the temporary directory, untar the PORTAL_ALL_2400.tar file.

The files are extracted to the bmc_products/BMCPortalKit directory.

4 From the bmc_products/BMCDatastore/disk1 directory, run install to launch the BMC Datastore installation program.

5 Using Chapter 5 in the BMC Portal Installation Guide, follow the procedure for installing the BMC Datastore.

6 After completing the BMC Datastore installation, from the bmc_products/BMCPortalKit/disk1 directory, run install to launch the BMC Portal installation program.

7 Using Chapter 5 in the BMC Portal Installation Guide, follow the procedures for installing the BMC Portal application server, web server, modules, and Performance Managers, depending on your installation scenario.

8 After completing the installations, you can delete the temporary directory and its contents.

Product installation issues

This section describes problems that you might encounter when installing the BMC Datastore and the BMC Portal.

On Solaris computers, cdrom/bmc_portal directory in the fully qualified path causes error in launching installation

To enable changing CDs during an installation on computers running Solaris, you must change from the directory that contains the installation image to a different directory (such as /tmp), and then specify the fully qualified path to the BMC Portal installation program on CD 1. If you specify the cdrom/bmc_portal directory instead of the cdrom0 directory when you change CDs to install the BMC Performance Manager Solutions and then reinsert CD 1 into the CD-ROM drive, the following error message is displayed:

Source media error
Disk 1 not found in the source drive

To avoid this issue, when you launch the installation program, always specify the cdrom0 directory in the fully qualified path as follows:

cd /tmp

/cdrom/cdrom0/install

Product upgrade paths

The BMC Portal 2.4 installation program supports upgrades of Portal components, including the RSM, from the following product versions only:

BMC Portal 2.1.x

BMC Portal 2.3.x

To upgrade from versions earlier than 2.1, you must perform a phased upgrade as described in the following table:

Product name	Comments
BMC Portal 1.2.00.02	Upgrade to BMC Portal 2.3 and then upgrade to BMC Portal 2.4.00. BMC Software recommends that you have the latest BMC Portal patch applied to version 1.2 before you begin the upgrade.
BMC Portal 1.1.x	Upgrade to BMC Portal 1.2, then upgrade to BMC Portal 2.3.00, and then upgrade to BMC Portal 2.4.00.
BMC Impact Portal 5.1.01 (BMC Portal Server 2.0.00)	Upgrade to BMC Portal 2.4 if the Portal does not contain the BMC Performance Manager Portal module.
PATROL Express 3.0.02.07	Upgrade to BMC Portal 2.1 and then upgrade to BMC Portal 2.4.00.

See "Upgrade issues for the BMC Performance Manager Portal".

The installation program terminates if it detects any version of PATROL Express on the target computer.

Product upgrade issues

In addition to the upgrade considerations described in the BMC Portal Installation Guide, consider the upgrade issues described in this section.

Datastore upgrade fails if more than one ORACLE_HOME is defined in the Oracle inventory

If a second copy of Oracle is installed on the same computer as the Portal datastore, the datastore upgrade fails. In this case, you cannot use the BMC Datastore installation program to perform the upgrade. If you encounter this issue, contact BMC Software Customer Support.

Upgrade issues for the BMC Performance Manager Portal

The installation program detects the installed version of the module and can upgrade from BMC Performance Manager Portal 2.1.00 and BMC Performance Manager Portal 2.3.00. If you have an earlier version of the product, you must upgrade to version 2.1 or 2.3 and then upgrade to the current version.

During the upgrade, the installation program converts the events and then purges any events older than 100 days. Because of the time required to convert events, if your Portal has events for a period longer than 100 days, BMC Software recommends that you purge events before you start the Portal upgrade.

See the procedures listed in Table 8 for more information about purging events before upgrading the Portal.

Table 8 Purging events before upgrading the BMC Performance Manager Portal module

Version number	Name and location of procedure
2.3.x	Technical bulletin (QM001514112) on the BMC Performance Manager Portal 2.1.00 Support page (http://www.bmc.com/support_home)
2.1.x	Technical bulletin (QM001514112) on the BMC Performance Manager Portal 2.1.00 Support page (http://www.bmc.com/support_home)
1.2.x	"Upgrading from BMC Performance Manager Portal 1.2.x"
1.1.x	"Upgrading from BMC Performance Manager Portal 1.1.x"
3.0.02	"Upgrading from BMC Performance Manager Express 3.0.02"

Upgrading from BMC Performance Manager Portal 1.2.x

You cannot upgrade directly from BMC Portal 1.2.x to BMC Portal 2.4.00. You must first upgrade to BMC Portal 2.3.00, and then upgrade to version 2.4.00.

Upgrading to BMC Performance Manager Portal Installation Notes contains guidelines and the steps necessary to upgrade from version 1.2.x to 2.3. You can find this document on the BMC Performance Manager Portal 2.3.00 and 1.2.x Customer Support websites (http://www.bmc.com/support_home) or with the product documentation.

1 Contact your BMC Software sales representative to obtain the BMC Performance Manager Infrastructure and Solutions 2.3 kit.

2 To purge all events, run the following SQL script; otherwise proceed to Step 3:

A Open a Command Prompt window.

B Use the sqlplus utility to connect to the database as the Portal database user (pe by default).

C Type the following commands:

TRUNCATE TABLE event_notification;

ALTER TABLE event_notification DISABLE CONSTRAINT fk_event_notification_event;

TRUNCATE TABLE event;

ALTER TABLE event_notification ENABLE CONSTRAINT fk_event_notification_event;

/

3 To purge events older than 100 days, see solution SLN000000229226 on the Support website for a script and procedures that describe how to use it.

4 Upgrade from BMC Portal 1.2.x to BMC Portal 2.3, referring to the following BMC Portal 2.3 documentation:

BMC Portal Installation Guide, version 2.3

BMC Performance Manager Portal Performance and Scalability Guidelines Installation Notes, version 2.3.00

5 If you have Portal or RSM clusters, remove the cluster properties from these clusters so that they revert to individual Portals or RSMs; otherwise, skip to Step 7.

6 When the upgrade to 2.1 is finished, reconfigure the Portal and RSM clusters to complete the upgrade of all components and verify the configuration.

For information about reestablishing Portal clusters, see the BMC Portal Getting Started guide. For information about reestablishing RSM clusters, see the BMC Performance Manager Portal Monitoring and Management Guide.

7 Allow the Portal server to complete the upgrade of solution Performance Managers and to start the RSM upgrade.

This process can take several hours. On the first startup of BMC Portal 2.3.00, you cannot log on to the Portal until the upgrade of the individual solution Performance Managers is complete.

8 When the upgrade process is complete, start the Portal, log on, and validate the configuration and parameter history.

If you used a second system for database backup, update the DNS to link the old URL to the new web server. Table 9 lists other adjustments that you might need to make after the upgrade, depending on your configuration:

Table 9 Possible adjustments after an upgrade from version 1.2 to 2.3 

Task	Supporting documentation
provide additional configuration information for database application classes	BMC Performance Manager Express for Databases Release Notes
modify enterprise event management configuration	BMC Portal Release Notes for version 2.1.00 describes SNMP management information base (MIB) changes. BMC Portal Getting Started describes the organization of the MIB.

9 Upgrade to BMC Portal 2.4.00 as explained in this document and the BMC Portal Installation Guide.

Upgrading from BMC Performance Manager Portal 1.1.x

To upgrade from BMC Performance Manager Portal 1.1.x, you must first upgrade to BMC Performance Manager Portal 1.2, and then version 2.3. Contact your BMC Software sales representative to obtain the BMC Performance Manager Portal 1.2 and version 2.3 kits.

Upgrading from BMC Performance Manager Express 3.0.02

You cannot upgrade directly from BMC Performance Manager Express 3.0.02 to BMC Portal 2.4.00. You must first upgrade to BMC Portal 2.1.00, and then upgrade to version 2.4.00.

Upgrading to BMC Performance Manager Portal Installation Notes contains guidelines and the steps necessary to upgrade from version 3.0.02 to 2.1. You can find this document on the BMC Performance Manager Portal 2.1.00 Customer Support website (http://www.bmc.com/support_home) or with the product documentation.

1 Contact your BMC Software sales representative to obtain the BMC Performance Manager Infrastructure and Solutions 2.1 kit.

2 To purge events and optimize the Portal datastore, follow the procedure in solution SLN000015012358 on the Support website.

3 Upgrade from BMC Performance Manager Express 3.0.02 to BMC Portal 2.1, referring to the following BMC Portal 2.1 documentation:

BMC Portal Installation Guide, version 2.1

BMC Performance Manager Portal Performance and Scalability Guidelines Installation Notes, version 2.1.00

4 If you have Portal or RSM clusters, remove the cluster properties from these clusters so that they revert to individual Portals or RSMs; otherwise, skip to Step 6.

5 When the upgrade to 2.1 is finished, reconfigure the Portal and RSM clusters to complete the upgrade of all components and verify the configuration.

For information about reestablishing Portal clusters, see the BMC Portal Getting Started guide. For information about reestablishing RSM clusters, see the BMC Performance Manager Portal Monitoring and Management Guide.

6 Allow the Portal server to complete the upgrade of solution Performance Managers and RSMs.

This process can take several hours. On the first startup of BMC Portal 2.1.00, you cannot log on to the Portal until the upgrade of the individual solution Performance Managers is complete.

7 After the RSM upgrades are complete, log on to the Portal and confirm that upgrade was successful and data is collecting normally.

8 Complete any other post-upgrade configuration steps identified in the Portal 2.1.00 documentation (for example, configuring certain database-monitoring Performance Managers).

9 To confirm that data migration is complete, monitor the status of the event migration process:

A Log on to the database from the Oracle sqlplus utility using the database credentials that were specified during installation.

B Execute the following commands:

Command	Result
select * from all_jobs	returns the scheduled event upgrade job When all events data has been migrated, this command will return no rows selected.
select count(*) from event12	returns a count of events data remaining to be migrated This count should decrease continually.
select count(*) from event	returns a count of events data that has been migrated This count should increase continually as the events from the old table are migrated to the new one.

10 Log on to the Portal and confirm that upgrade and migration were successful.

11 Upgrade to BMC Portal 2.4.00 as explained in this document and the BMC Portal Installation Guide.

Portal upgrade process for BMC Impact Portal 5.0.01 or 5.1.00

If you are upgrading the BMC Impact Portal from version 5.0.01 or 5.1.00, you must upgrade the BMC Portal in two stages: from 1.x to 2.3, and then from 2.3 to 2.4. See the BMC Impact Portal Installation Notes.

BMC Performance Exception Detector upgrade considerations

In addition to the requirement to upgrade to version 1.3.10 of the Exception Detector data service, consider that this version of the BMC Performance Exception Detector module does not support the use of default detectors or custom detectors designed for mainframe environments. If you used mainframe exception detectors in the previous version, you must disable or delete those detectors, or contact BMC Customer Support for a script that automatically disables all mainframe detectors.

Otherwise, the installation program performs all necessary migration tasks.

See the BMC Performance Exception Detector Implementation Guide for the complete list of requirements and installation instructions for the Exception Detector data service program.

What’s new in BMC Portal Server

The BMC Portal Server provides the features common to all modules in the BMC Portal.

For information about new features for the modules, see the following topics:

"BMC Performance Manager Portal 2.4.00"

"BMC Performance Exception Detector 1.3.10"

"BMC Impact Portal 7.0.02"

The following features are new in this release of the BMC Portal Server:

You can now use the postinstallation utility to cluster the Portal application servers. See the BMC Portal Getting Started guide for more information.

The pe user that is created during the Portal datastore installation now has the permissions required by BMC Performance Manager Express for Databases and other BMC Software products to monitor the Portal datastore.

The Portal provides a new action script that you can use to integrate Portal events with AlarmPoint 3. This new support was added after publication of the procedures for configuring integration with AlarmPoint (in the BMC Portal Getting Started guide). See the updated procedure under "Integrating the Portal with AlarmPoint 3."

You can now enable the Portal to write LDAP errors to the portal.log file.

Integrating the Portal with AlarmPoint 3

Use the following information to update the BMC Portal Getting Started guide’s instructions for configuring AlarmPoint.

Copy the sample scripts from the following locations on the application server to the destination directories shown in Table 10:

(Windows) %BMC_PORTAL_KIT_HOME%\appserver\util\BPM_AlarmPoint

(UNIX) $BMC_PORTAL_KIT_HOME/appserver/util/BPM_AlarmPoint

Table 10 Sample scripts and text files for integration with AlarmPoint3

File name	Target directory
bpm_portal_ap3.aps	AlarmPointManagerInstallDirectory\Log
bpm_portal.xml	AlarmPointJavaClientInstall\etc\integrations

To integrate the Portal with AlarmPoint3

1 On the AlarmPoint Java Client host, stop the AlarmPoint Java Client service or APAgent.

2 Navigate to the APAgent/etc folder and create a backup copy of APAgent.xml.

3 In an ASCII text editor, edit APAgent.xml, replacing the <http port="2010" /> string with the following lines:

<http port="2010">     <socket-listener host="<APAgent HOST IP ADDRESS>" port="2010"/>   </http>

4 On the next line, insert the following parameters required by the BMC Portal script, and then save and close the file:

<alarmpoint-agent-client id="bpm_portal" filename="integrations/bpm_portal.xml" />

5 Restart the AlarmPoint Java Client service or APAgent.

6 On the Alarm Point server, use the Alarm Point integrated development environment (IDE) to import the BPM_Portal_AP3.aps action script.

7 Validate and check in the action script tree.

8 Finish the configuration by performing the following procedures in the BMC Portal Getting Started guide:

To verify the communication between the BMC Performance Manager Portal and AlarmPoint

To configure the Portal to send user notifications to AlarmPoint

To configure the Portal to send enterprise-wide notifications to AlarmPoint

1 Log on to AlarmPoint as superadmin, and select the Developer tab.

2 On the Developer tab, select the Event Domains task.

3 Click Add New, and add an event domain that uses the BPM_Portal_AP3 script that you imported.

The event domain name will be used by the Portal as the client id when configuring AlarmPoint server.

4 Create an AlarmPoint user to receive the notification messages from the Portal.

The new user name will be used in alert rule definition as Person or Group ID.

Open issues and workarounds in BMC Portal Server

Table 11 lists problems that remain open in this release. If applicable for the issue, a workaround is also included.

Table 11 Open issues and workarounds for the BMC Portal Server (part 1 of 2)

Tracking ID	Description
QM000532955	If an administrator’s Portal has been idle for an extended period of time, when a user is impersonated, an application error occurs when the administrator clicks any of the tabs in the user’s Portal. Workaround: Log off and log on again.
	When you configure the Portal to send SNMP traps, you cannot view all of the values in the PATROL Explorer Event Log. Only the first trap contains all of the required information for SNMP traps. All subsequent traps for the parameter or element are displayed as RECURRING and the tokens are set to UNKNOWN. The Text column contains the parameter name value as it is displayed in the first trap for Token1. Workaround:
QM001521718	After upgrading the Portal from version 2.1 to 2.4, for each general system problem notification rule, the Portal migrates a general system problem and a status change notification rule. Workaround: Delete the status change notification that was created for the GSP notification rule.
QM001522363	If you use more than one LDAP server to authenticate users and if one of the LDAP servers is down, the user logon times out and eventually fails. Workaround: If the LDAP server can receive the ping command, the Portal can receive the return status from the LDAP server. Based on the status that it receives from the LDAP server, the Portal determines whether it will use the LDAP server for authentication users. 1. To configure the Portal to receive a return status from the LDAP server, open the internal.properties file, and change the LDAP timeout value from -1 to 10000 (10 seconds). See the BMC Portal Getting Started guide for the file location. 2. Restart the Portal application server. If the LDAP server cannot receive the ping command, use one of the following options to access a user account when one or more LDAP server is down: Log on as an administrator and impersonate a user. Log on as a Portal administrator, select the Portal tab, and clear the LDAP server selection.
QM001523224	If a user has None rights for Blackout Account and Full rights for Blackout Periods, the user can still edit, delete, stop, and resume blackout periods for an account. A user with this combination of rights cannot create blackout periods for an account. No workaround exists.

Corrected problems in BMC Portal Server

The following problems were reported in earlier releases of BMC Portal Server and have been corrected in this release.

Table 12 Corrected problems in BMC Portal Server (part 1 of 2)

Tracking ID	Description
QM001515620	The configuration between Apache and Tomcat sometimes caused HTTP 503 errors as client connections increased.
QM001521320	If the LDAP user authentication process failed, the Portal lacked diagnostic logging messages. The BMC Portal Getting Started guide describes how to enable LDAP logging messages in portal.log.
QM001512797	After upgrading a version 2.1 Portal to version 2.3, an application error occurred when you tried to configure a notification template.
QM001521977	The portal.log file contained many INFO messages about payloads increasing on the BMC Portal server while the ANALYZE TABLE EVENT COMPUTE STATISTICS job was running.
Issues in non-English version
QM001514279 QM001516345	The customized notification template did not properly display multibyte characters in email messages or in the SNMP trap receiver.

BMC Performance Manager Portal 2.4.00

The BMC Performance Manager Portal module leverages agentless and PATROL Agent technologies to remotely monitor and report on the performance of your IT infrastructure.

This section describes the new features, corrected problems, and open issues for BMC Performance Manager Portal 2.4.

What’s new in BMC Performance Manager Portal

This section lists the new features for this release. For more information about these new features, see the BMC Performance Manager Portal Monitoring and Management Guide and the Help.

Health At A Glance report enhancements

The Health At A Glance report has been enhanced with the following features:

The report now shows the availability of an element. By default, only critical alarms can affect the status, but you can modify the formula used by the Portal to calculate availability by modifying a property file.

You can now view the report as a PDF file. To view all report components in the PDF file, install Adobe Acrobat 6 or later.

Top N report enhancements

When viewing the Top N report, you can now perform the following actions:

export the parameter data points from a Top N report to a CSV file

view the report as a PDF file

Enhanced support for child applications in an application class

Some application classes have child application instances that you can now configure.

You can specify child instances and their properties when adding an element to the Portal, when editing application class properties, or when creating or editing an element profile.

You can now delete child application instances from the Portal.

When you delete a discovered instance, you can delete only the instances that no longer exist on the monitored element. If you delete a discovered instance that still exists on the element, the RSM will rediscover the instance during the next collection time.

Command-line interface (bpmcli) enhancements

The following features were added to the bpmcli:

ability to discover PATROL Agents by using the bpmcli

The addPATROL command initiates the process that adds one or more elements to the Portal, based on a list of PATROL Agents. The PATROL integration Performance Managers assigned to the elements correspond to the KM application classes found on the corresponding PATROL Agents. The Portal synchronizes the thresholds for the newly added PATROL integration Performance Managers with their corresponding values on the PATROL Agents.

ability to export historical (summarized) data to an external datasource

The exportParameterHistory command runs the Historical Data Export utility, which complements the Continuous Data Export utility (which continuously writes specified raw parameter values to an external data source). For each parameter in the external datastore, the exportParameterHistory command exports historical summarized data to the same external datastore.

You can use the exported data to create reports in a reporting program like Crystal Reports. You can request a copy of Crystal Reports from your BMC Software sales representative.

Ability to override element profile attributes

For new and existing elements, you can override properties and threshold settings specified in an element profile without disassociating the profile from the element.

When overriding properties, you can change credentials, properties, and collection interval.

When overriding thresholds, you can change warning and alarm threshold values (including the on and off flags) and Alert After properties.

When overriding a profile, the following rules apply:

Setting an override does not disassociate the element from the profile. If you make changes to the profile, those changes (unless overridden) are applied to the element.

If you disable an override, the affected thresholds and properties return to the values specified in the element profile.

What’s changed in BMC Performance Manager Portal

This section lists changes from earlier versions of the product.

The following changes were made to the continuous data export feature (datafeed utility):

— The configuration files from the 2.3 version do not apply for 2.4 and are deleted during the upgrade. Following the completion of the Portal upgrade, reconfigure the Portal to export parameter data.

— The table structures for the exported data have changed from version 2.3, and views to the existing data are not available by default.

See the BMC Performance Manager Portal Monitoring and Management Guide for information about this feature.

In the Performance Manager Editor, buttons have been renamed as follows:

— Add changed to Create

— Import changed to Upload

In earlier releases, the Portal applied global thresholds when discovering or refreshing thresholds on PATROL Agents. The Portal now applies local thresholds to discovered instances. If local thresholds do not exist, the Portal applies the global thresholds to the instance.

Open issues and workarounds in BMC Performance Manager Portal

Table 13 lists problems that remain open in this release. It groups the issues by feature and includes the tracking ID if one has been assigned to the issue. If applicable for the issue, a workaround is also included.

Table 13 Open issues and workarounds in BMC Performance Manager Portal (part 1 of 4)

Tracking ID	Issue
General
QM001510760	If an element triggered a notification more than 24 hours ago, the Element Events section of the Health At A Glance report shows event data and a Notified link, but if you click the Notified link, the Nothing found to display message appears. Workaround: Access the Events tab and select the Notified link for the event.
QM000548295	If you change the credentials on an RSM so that the RSM type changes, the RSM stops communicating with the Portal. For example, changing from user credentials to administrator credentials changes the RSM type from dedicated to shared. No workaround exists. Changing RSM types is not supported.
QM000555050	When you launch the Health At A Glance report from Impact Explorer for a Business object, the following message is displayed: The component providing the selected view is not available. This problem can occur if you try to cross-launch a business object that does not have a corresponding infrastructure object in the BMC Atrium CMDB. No workaround exists. If you use a product that enables you to view configuration items (CIs) in the CMDB, the Health At A Glance option is listed for all CIs, regardless of whether a corresponding infrastructure object exists for the CI.
QM001523109	Sometimes the internal names for application classes and parameters are displayed in the Portal user interface. Workaround: In most cases, restarting the Portal corrects the problem.
QM001523448	When you use the Historical Data Export (HDE) utility to export parameter data to an external Oracle datastore, any parameter values greater than 8 characters cause the HDE utility to fail and generate the following error message: Status: Failed (URL=jdbc:oracle:thin:@PortalName:1521:BMCPDS, table=DATAFEED_USER.PARAMETER_DETAIL, error=ORA-01438: value larger than specified precision allowed for this column Workaround: Use the procedure described in "Modifying the HDE script" to modify the script that builds the target datastore.
QM001524202	If you assign an element profile to an element, you cannot change the credentials or threshold setting for the element if you remove it from the profile. Workaround: Perform one of the following actions: Do not remove elements from their assigned element profile. If you remove an element from its profile, use the procedure described in "Changing the credentials and thresholds for an element that was a member of a deleted profile".
Infrastructure elements—agentless monitoring
QM000520459	When you install the RSM program on a Windows 2003 (SP1) computer, the RSM is adversely affected by a memory leak caused by Microsoft WMI. The Microsoft Article ID for this problem is 911262. Access the Microsoft Hotfix Page for more information about this problem.
QM001518391	If you use an application class that uses the WMI collector (for example, Windows services using WMI), the application does not interpret the proper error messages if you remove and replace the network cable on the monitored computer. After replacing the network cable, some monitored instances show the following error message: Bad credentials for host: hostName:patsdk-wmi. Workaround: For the affected element, access its Properties page, and under General Properties, click Edit and change the Monitoring Status to Off and then On.
QM001519468	You cannot use shared credentials for a local account to monitor an application class on a Windows computer. Under normal circumstances, you use the following format to specify the computer name of the local account and the user name: HostName\userName. If you specify a dot in place of the host name (.\userName) on shared credentials, you get a credential conflict error. Workaround: Explicitly type credentials for a local account.
QM001522399	When you use the Performance Manager Editor (PME) to create a custom Performance Manager, the PME cannot validate the Performance Manager Archive (PAR) file if the Portal does not have direct Internet access. A validation error occurs if Internet access is denied or if a proxy server is required to access the Internet. The PME uses the following website to validate the PAR file: http://jakarta.apache.org/commons/dtds/validator_1_1.dtd. Workaround: Use the procedure described in "Enabling Internet access through a proxy server" to enable Internet access through a proxy server.
Infrastructure elements—agent-based monitoring
QM001517377	If you use BMC Performance Manager Integration with PATROL for Microsoft Exchange Servers, the synchronization operations (Refresh PATROL Integration option or refreshPATROL command) update the one of the following application classes and add the other application class: PATROL integration Performance Managers that contain overlapping application classes: PATROL – Microsoft Exchange Servers (Cluster) PATROL – Microsoft Exchange Servers Performance Managers You need only one of these application classes. Workaround: Delete the application class that the Portal added during the synchronization process, or manually configure the parameter thresholds in the required application class instead of running a synchronization operation.
BMC Atrium CMDB integration
SW00263695	Instances of BMC_OperatingSystem and BMC_FileSystem in the BMC Topology Import dataset cannot be identified against instances in BMC Performance Manager Portal dataset, causing duplicate instances in BMC Asset after reconciliation. This is because BMC Topology Discovery 1.4 and earlier and BMC Performance Manager Portal do not populate the TokenId attribute identically. Workaround: If you need to use one of these CIs in a service model, choose the one that came from the BMC Performance Manager Portal. Using the CI from BMC Topology Discovery does not allow you to see the effects of events on the model. To determine which application created a particular CI, examine the value of the TokenId attribute. For BMC_FilesSystem CIs and BMC_OperatingSystem CIs for UNIX computers, BMC Performance Manager Portal populates TokenId, but BMC Topology Discovery does not. For BMC_OperatingSystems CIs for Windows computers, BMC Performance Manager Portal uses the format OS_name:path while the CI created by BMC Topology Discovery uses the format OS_name|path. Alternatively, BMC Topology Discovery 1.4 patch 004 supplies matching TokenId values for BMC_OperatingSystem CIs for both Windows and UNIX computers.
Upgrading from BMC Portal 2.3
QM001521164	When an upgrade removes all application classes from an element, the element is not deleted from the Portal. If you open the Properties page for the element, its Monitoring Status is Off. If you had elements that were assigned application classes that used only the rstatd collector, those application classes are removed during the upgrade to version 2.4. Workaround: For elements whose Monitoring Status is Off and do not have any application classes, use the Elements task to delete the elements from the Portal.
QM001510612	If you do not upgrade the solution Performance Managers during a Portal upgrade, you might see a mismatch of statuses between the Health At A Glance report and the current status of the element. When this problem occurs, the Key Parameters list is empty. Workaround: Perform the following actions: 1. After manually upgrading the solution Performance Managers, confirm that they were upgraded to the latest version, and that they have a status of Published. 2. Access the Properties page for the element, and under General Properties, click Edit and change the Monitoring Status to Off and then On.
Upgrading from BMC Portal 2.1 or 2.3
QM000554905	Large Portal environments that have a large number of elements can cause background upgrade processing to linger for a significant time after the Portal has completed its primary upgrade sequence. Workaround: Administrators should wait up to one hour after the upgrade finishes before logging on to the Portal to publish new solution Performance Managers from the Performance Managers page.
Upgrading from BMC Portal 2.1
QM001520950	If you upgraded the Portal during a scheduled blackout period, the element’s status changes to offline when the upgrade is finished. This problem occurs when the blackout period’s start and end times occur during the time required to upgrade the Portal. Workaround: For the affected element, access its Properties page, and under General Properties, click Edit and change the Monitoring Status to Off and then On.
QM001522359	After an upgrade of BMC Portal 2.1 to 2.4, the BMC Performance Manager Integration with PATROL for WebSphere 2.4 Performance Manager fails to Publish. Workaround: Contact BMC Customer Support for the latest version of BMC Performance Manager Integration with PATROL for WebSphere.
QM001523030	After upgrading a Solaris application server, the Help systems for the 2.1 solution Performance Managers are still present on the application server and are displayed when Help is selected. Workaround: Log on to the Support website and use the procedure described in Knowledge Article KM-000010022821.
Issues in non-English version
QM000547687	If a host name contains multibyte characters, you cannot add an element unless you specify an Element Profile in the Add Element wizard. No workaround exists. You cannot specify a host name that contains multibyte characters.
QM001521819	If you save a PDF version of the Health At A Glance report, the Portal creates a file name based on the name of the element. If the element name contains multibyte characters, underscore characters appear in the file name instead of the multibyte characters. No workaround exists.

Modifying the HDE script

Use the following procedure to resolve the problem described in tracking ID QM001523448 on page 29, or as directed by Customer Support. You must make this change before you can configure the Continuous Data Export and HDE utilities as described in the BMC Performance Manager Portal Monitoring and Management Guide.

1 Locate sampleOra.sql in one of the following locations on the Portal application server, and open it in a text editor:

(Windows) /util/BPM_Datafeed

(UNIX) \util\BPM_Datafeed

2 In the script, locate the line highlighted in the following example:

CREATE TABLE PARAMETER_SUMMARY ( PARAMETER_GUID VARCHAR2(32), PARAMETER_VALUE NUMBER(12,4), SAMPLE_TIMESTAMP_UTC TIMESTAMP(0), CONSTRAINT PK_PARAMETER_SUMMARY PRIMARY KEY ( PARAMETER_GUID, SAMPLE_TIMESTAMP_UTC ) )

3 Remove (12,4) so that the text appears as shown in the following example:

CREATE TABLE PARAMETER_SUMMARY ( PARAMETER_GUID VARCHAR2(32), PARAMETER_VALUE NUMBER, SAMPLE_TIMESTAMP_UTC TIMESTAMP(0), CONSTRAINT PK_PARAMETER_SUMMARY PRIMARY KEY ( PARAMETER_GUID, SAMPLE_TIMESTAMP_UTC ) )

4 Save the file.

Changing the credentials and thresholds for an element that was a member of a deleted profile

Use the following procedure to resolve the problem described in tracking ID QM001524202 on page 30, or as directed by Customer Support.

1 Log on with user credentials, and select the Configure tab.

2 Under Tasks, select Element Profiles, and click Add.

3 Using the Add a profile based on an existing element option, create a new element profile.

4 On the Element Profiles–Add–Create From Element page, select Make the selected element a member of the element profile, select the element from the object tree, and click Finish.

5 Under Properties in the navigation pane, select the element, and select the Configure tab.

6 On the Properties page for the element, scroll down to Application Classes, and click Override Profile.

7 For each property or threshold to change, select the Override check box and change the corresponding value.

8 Click Save to return to the Properties page.

Enabling Internet access through a proxy server

Use the following procedure to resolve the problem described in tracking ID QM001522399 on page 30, or as directed by Customer Support.

1 Using a text editor, open one of the following files:

(Solaris) $BMC_PORTAL_KIT_HOME/appserver/appserver/websdk/bin/run.sh

(Windows) %BMC_PORTAL_KIT_HOME%\appserver\websdk\conf\sdkwrapper.conf

2 Locate Java Additional Parameters.

The highlighted text shows the sections that you need to update:

# Java Additional Parameters wrapper.java.additional.1=-server wrapper.java.additional.2=-Dprogram.name=run.bat wrapper.java.additional.3=-Duser.timezone=UTC wrapper.java.additional.4=-Duser.language=en wrapper.java.additional.5=-Duser.region=US wrapper.java.additional.6=-Dswing.volatileImageBufferEnabled=false wrapper.java.additional.7=-Djava.awt.headless=true wrapper.java.additional.8=-XX:PermSize=64m wrapper.java.additional.9=-XX:MaxPermSize=128m # Uncomment to add in debugging #wrapper.java.additional.10=-ea #wrapper.java.additional.11=-Xdebug #wrapper.java.additional.12=-Xrunjdwp:transport=dt_socket,address=9999,server=y,suspend=n

3 Insert a line above # Uncomment to add in debugging, and add the following text: wrapper.java.additional.10=-Dhttp.proxyHost=IpAddress, where IpAddress is the IP address of the proxy server.

4 Insert another line above # Uncomment to add in debugging, and add the following text: wrapper.java.additional.11=-Dhttp.proxyPort=PortNumber, where PortNumber is the port number that receives requests on the proxy server.

5 Under # Uncomment to add in debugging, change 10, 11, and 12 to 12, 13, and 14, as shown in the following sample file:

# Java Additional Parameters wrapper.java.additional.1=-server wrapper.java.additional.2=-Dprogram.name=run.bat wrapper.java.additional.3=-Duser.timezone=UTC wrapper.java.additional.4=-Duser.language=en wrapper.java.additional.5=-Duser.region=US wrapper.java.additional.6=-Dswing.volatileImageBufferEnabled=false wrapper.java.additional.7=-Djava.awt.headless=true wrapper.java.additional.8=-XX:PermSize=64m wrapper.java.additional.9=-XX:MaxPermSize=128m wrapper.java.additional.10=-Dhttp.proxyHost=192.168.3.11 wrapper.java.additional.11=-Dhttp.proxyPort=8080 # Uncomment to add in debugging #wrapper.java.additional.12=-ea #wrapper.java.additional.13=-Xdebug #wrapper.java.additional.14=-Xrunjdwp:transport=dt_socket,address=9999,server=y,suspend=n

6 Restart the Portal application server.

Corrected problems

The problems in the following table were reported in earlier releases of BMC Performance Manager Portal and have been corrected in this release. The table groups the issues by feature.

Table 14 Corrected problems in BMC Performance Manager Portal (part 1 of 3)

Tracking ID	Issue
General
QM000553515	The RSM spawned hundreds of awk processes, requiring monitoring to be stopped.
QM001514970	The Health At A Glance report was very slow, which degraded the database performance.
QM001514112 QM001515291	Event data was not purged from PE.EVENT and PE.EVENT_NOTIFICATION tables, which caused the following symptoms: In some cases, you might have observed high disk activity and an impact on database performance. The following message might have appeared in the alert_BMCPDS.log or the portal.log file: ORA-1653: unable to extend table PE.EVENT by 6400 in tablespace.
QM001518192	If a provider-level event cleared before the time at which the Portal should send an event, the Portal still sent the event.
SW00255138 QM001510458	If you used BMC Atrium CMDB with a SQL Server database, an error could occur when you imported the BMC Performance Manager dataset.arx file. The log file contained the following message: Failure during SQL operation to the database -- View or function 'T201' is not updatable because the modification affects multiple base tables. (SQL Server 4405) ( 552)
QM001511700	The Alert After threshold was not propagated to discovered instances.
Infrastructure elements—agentless monitoring
QM000547718	When you used the SNMP Trap Listener application class and you specified an invalid host name, the application class showed error code 1 instead of 4.
QM001515624	When monitoring version 1 and version 2 SNMP traps, the RSM did not recognize any community string other than public.
Infrastructure elements—agent-based monitoring
QM001511616 QM000554214	The Portal displayed extended ASCII characters from the PATROL Agent as junk characters. The RSM would sometimes fail when communicating with the agent.
QM001518813	When you used the Refresh PATROL Integration option or the refreshPATROL bpmcli command to synchronize parameter thresholds, the following error message appeared in the log file: Skipping aggressive-release due to open resources on batcher
Issues in non-English version
QM000554214	Extended ASCII characters from a PATROL Agent were displayed as junk characters in the Portal.
RSM and collectors
QM001515619	If you used the SSH Text log collector to monitor a UNIX® text log file, the parameter status sometimes changed to alarm when no changes occurred between collection intervals.
QM001520186	If you were monitoring PATROL integration Performance Managers and tried to stop the RSM, sometimes it took several minutes for the RSM service to stop.
QM001518098	Previously, due to timing and performance issues, authentication errors occurred even though the valid credentials were available. The Portal marks the application as having bad credentials and does not retry the connection. With this release, the RSM can be set to automatically retry authentication.
QM001519799	On Solaris, the Jbossout.log file increased until it consumed all the space on the file system and caused the server to terminate abnormally.

BMC Performance Manager SDK 2.4.00

If BMC Software does not have a Performance Manager that meets your monitoring needs, use the Performance Manager Editor (PME) to create a custom Performance Manager. If the PME does not enable you to create a Performance Manager that meets your needs, the BMC Performance Manager Portal Software Development Kit (SDK) provides an API that you can use to create custom Performance Managers. The API provides Java class libraries, tools, and sample Performance Managers to help you build your own Performance Managers.

For more information about the features in the BMC Performance Manager SDK, see BMC Performance Manager Development and Certification Guide.

What’s new in BMC Performance Manager SDK

This section lists the new features for the BMC Performance Manager SDK 2.4.00.

Support for 2.x solutions

Solutions built using the 2.1 and 2.3 versions of the BMC Performance Manager SDK will run unmodified in BMC Portal 2.4 environment. However, if you alter a solution using BMC Performance Manager SDK 2.4, you may need to make additional changes to the solution to account for validation enhancements in 2.4.

Accumulator parameter

BMC Performance Manager SDK 2.4.00 introduces an accumulator parameter type. This parameter type is a standard, numeric parameter with the following distinct behavioral differences:

It aggregates the collected value until the parameter is reported.

The parameter value is reset to 0 whenever the parameter value is reported.

It shares most of the same characteristics as other parameters, including the ability to be derived parameters. This capability enables you to monitor both moment-to-moment activity as well as the cumulative effect of that activity.

An accumulator parameter does not support thresholds or alerts (as defined by value-analysis-definition elements) and must contain a summarization element with a type attribute equal to accumulated. The accumulated value is stored in the database. The Reports tab of the BMC Portal displays the accumulated value as a total over time.

Paramlet statistics

Through the JMX Console, you can monitor the performance of paramlets by gathering performance statistics for a paramlet on a specific RSM. For each paramlet and version, the following statistics are provided:

accumulated clock time in milliseconds (maximum, minimum, average, and total)

accumulated CPU usage in milliseconds (maximum, minimum, average, and total)

batched job count (maximum, minimum, average, and total)

number of invocations

invocation times (newest and oldest)

Filter properties

Filter properties enable end users and solution developers to optimize the collection of data by limiting the discovered instances that are monitored. A filter property consists of a collection of rules that you can use to restrict the application instances that the RSM monitors. Filter properties are part of a filter, which is implemented in the following components of a solution:

the paramlet that collects the data for the applications

the paramlet interface definition for that paramlet

the application definition, which contains the filter properties

The capabilities of a filter, also known as the filtering logic, are defined within the paramlet. The application definition (an XML file) determines which set of the paramlet’s capabilities the filter uses and who, either the solution developer or the end user, provides the filter criteria. The interface ensures that the criteria and their attributes are properly formatted as the information is passed from the RSM to the paramlet.

What’s changed in BMC Performance Manager SDK

This section describes changes in the BMC Performance Manager SDK 2.4.00.

Expanded versioning scheme

The versioning scheme has been expanded to better support patch-level changes. It is now

vv.rr.mm.ppp

All components of the version scheme are integer values. Preceding zeros are optional, so 02.04.11.005 is the same as 2.04.11.05 and 2.4.11.5.

Upgrade descriptor supports multiple versions

The BMC Performance Manager SDK enables you to create a single upgrade-descriptor file that upgrades from several previous versions, using the fromVersion attribute, with the same architecture and structure to the current version. You can define the mappings for the upgrade in a single upgrade-descriptor file. You can then use that file for all versions that share the same structure and possess identical mappings. This capability prevents you from introducing errors by replicating upgrade descriptors.

Table 15 lists the valid values for the fromVersion attribute in an upgrade descriptors.

Table 15 Upgrade-descriptor values for fromVersion

fromVersion value	Result
*	upgrades all previous versions to the latest version
V.*	upgrades all previous releases to the latest version
V.R.*	upgrades all maintenance releases to the latest version
V.R.M.*	upgrades all patches to the latest version

Preserve hierarchy when removing parent containers

The upgrade process supports moving an application up one level in the application hierarchy and deleting its parent application. This restructuring can occur at any level within the hierarchy, except the root level. However, the parent application scheduled to be deleted cannot be the root application. This feature preserves applications whose parents are being deleted during an upgrade, regardless of their levels.

Upgrade process adds filter properties

In the upgrade-descriptor file, new filter properties are added to the root application using the property-add directive. The upgrade process ensures that they are implemented for the intended application.

Paramlet’s JobSessionListenerV2 class supports instance deletion

The JobSessionListenerV2 class is an extension of the JobSessionListener class. The extended class contains an overloaded version of the notify( ) method that accepts an additional parameter, object data:

notify(JobSessionEvent) notifies the paramlet of the following events:

— BEGIN_COLLECTION_CYCLE

— END_COLLECTION_CYCLE

— CONFIGURATION_CHANGE

— SCHEDULE_CHANGE

— REMOVE

notify(JobSessionEvent, ObjectData) notifies the paramlet of the REMOVE_INSTANCE event, and provides the ID of the deleted application.

This functionality has been added to the paramlets that ship with the SDK. To support deleting instances in solutions that use custom paramlets, add this extended class and implement the overloaded method in support of the REMOVE_INSTANCE event.

Validation of solution

To ensure that the new version of a solution runs properly, the following validation enhancements have been added to version 2.4. The errors detected by these validation rules are implemented in the upgrade-descriptor file.

During PAR creation

If the version of the solution does not match what is stored in the database, no applications in the solution will load properly after the upgrade. Thus, the following validation is performed during the creation of the PAR file.

A warning is logged if the toVersion attribute of the solution-upgrade directive does not match the PAR solution version.

Required attributes are verified to be present and not contain an empty string.

Optional attributes are verified and either are not present or are present and their value is not an empty string. The solution-upgrade directive has only one optional attribute, the newSolutionName.

The toVersion attribute is verified and its value is not null or an empty string. The value also matches the solution definition version.

The solutionName, or the newSolutionName is verified if the solution being renamed, matches the name in the solution definition.

At runtime

If the fromVersion attributes for multiple descriptors overlap in a single solution, the wrong upgrade might be applied, which could result in all applications in that solution being in a broken state after the upgrade. To ensure that the situation does not occur, the following validation is performed at run time:

For multiple upgrade descriptors, their fromVersion values are verified as not overlapping for a given toVersion.

The PAR file will fail to be published if the toVersion attribute of the solution-upgrade directive does not match the PAR solution version.

Open issues and resolutions in BMC Performance Manager SDK

This section describes issues that remain open in this release. The following table includes the tracking ID if one has been assigned to the issue. If applicable for the issue, a workaround is also included.

Table 16 Open issues and workarounds in BMC Performance Manager SDK 

Tracking ID

Issue

QM001522538

Due to a bug that was fixed in 2.4, the default behavior of instanceName changed. Prior to 2.4, the instanceName was populated for discovered applications and static sub-applications but not for static applications. In 2.4, the instanceName is always populated. Developers using the content of the instanceName in their paramlets should check to ensure that this change in behavior does not affect the paramlet’s processing.

Corrected problems in BMC Performance Manager SDK

The problems in the following table were reported in earlier releases of BMC Performance Manager SDK and have been corrected in this release.

---

WARNING:

If you implemented the workaround prescribed for QM001510965, you must remove it for the fix to take effect.

---

Table 17 Corrected problems in BMC Performance Manager SDK 

Tracking ID

Issue

QM001510965

Prior to this release, Maven was unable to download java archives files (.jar) from ibiblio.org. The inability to access these files caused the creation of the template solution (maven patsdk-solution-template) to fail the build (maven par) to fail with the following error message or one similar to it Error retrieving artifact from [http://www.ibiblio.com/maven/velocity-dvsl/jars/velocity-dvsl-0.45.jar]:java.io.IOException: Unknown error downloading; status code was: 301 WARNING: Failed to download velocity-dvsl-0.45.jar. The build cannot continue because of the following unsatisfied dependencies: velocity-dvsl-0.45.jar The prescribed workaround required you to create a build.properties file in your user home directory and place a single variable maven.repo.remote and its corresponding value in it. For this fix to be fully implemented, you must delete the build.properties file.

BMC Performance Exception Detector 1.3.10

The BMC Performance Exception Detector consists of the Exception Detector module installed on the BMC Portal, and the Exception Detector Data Service installed on the computers where you have BMC Visualizer and BMC Automator. To use the Exception Detector module, you also must have a functioning BMC Performance Assurance environment with data automatically populated into a BMC Visualizer database on a daily basis.

See the BMC Portal online Help and the BMC Performance Exception Detector Implementation Guide for additional information about the features of this module and procedures and guidelines for configuring and using the module.

What’s new in BMC Performance Exception Detector

This section lists the new features for this release.

Configure a link to a running instance of BMC Performance Perceiver. After the link is configured, you can launch a BMC Performance Perceiver view that relates to a specific event from the Events tab.

Send detail charts and report data by using the email icon on the Status page and Exception Details window. For the Status page, the email includes the message text and the status table. For the Exception Details window, the email includes the message text, the table that briefly describes the detector, and one chart for each metric specified in the exception detector.

Create detectors for virtual systems by using the following new object types and associated metrics:

— Solaris zone

— Microsoft Virtual Server

— Microsoft Virtual Machine

View improvements to data service log files. The log files for the data service (PEDScanWS.log and PEDUpdateWS.log) now

— have standard date and time stamps

— display additional messages for the process of creating a data source

These messages provide more detail if the Data Service has a problem creating the data source.

— display the data server port number

— are stored in a standard output folder (C:\Program Files\BMC Software\EDService\log)

Open issues and workarounds in BMC Performance Exception Detector

Table 18 lists the issues that remain open in this release, groups them by feature, and includes the tracking number if one has been assigned to the issue. If applicable for the issue, a workaround is also included.

Table 18 Open issues and workarounds in Exception Detector (part 1 of 2)

Tracking number	Issue
Supported environments
none	The BMC Performance Exception Detector module has not been certified in a clustered Portal environment. It is not a supported environment for the module.
Installation and uninstallation
511026	If you uninstall the data service, you might see a dialog box that indicates that you need to close either the BMC Visualizer program or the BMC Automator program. The message is erroneous and is a known issue in the Microsoft Windows Installer, versions 3.0 and earlier. Workaround: You can either click Ignore to proceed with the uninstallation process or close the BMC Visualizer or BMC Automator program.
Exception detector elements
QM000535570	Test scans for long intervals (such as several weeks) might time out. Subsequent attempts to retrieve the test scan data by clicking Retry might not return any additional exceptions, and the operational status messages at the top of the page indicate that the scans for each requested day have timed out. Workaround: Shorten the time range for the test scan in the date range filter and resubmit the scan request.
QM001510600	The character limit for the System pattern and Object pattern fields on the Add/Edit Detector pages is 255 characters. You can enter 256 characters in these fields, but when you try to save the detector the request fails with a system error.
Data service
none	When password encryption for BMC Automator is turned on, the data service cannot access the BMC Visualizer database because it does not have password decrypting capability. Workaround: Impersonate a user with more authority, such as a power user, by completing the following steps: 1. Locate the following file: DataServiceInstallDirectory\EDService\web.config 2. Insert the following section into the web.config file after the tag </authorization>: <!-- identity Attributes: impersonate="[true|false]" - Impersonate Windows User userName="Windows user account to impersonate" | empty string implies impersonate the LOGON user specified by IIS password="password of above specified account" | empty string --> <identity impersonate="true" userName="power_user_name" password="power_user_password"/> 3. Replace power_user_name and power_user_password with the user name and password for the user that you want to impersonate. 4. Save and close the file.
ISS03052345	The BMC Performance Exception Detector module times out when scanning for exceptions across multiple data sources. This problem can occur when you attempt to scan a large number of data sources (more than 10 data sources per data server). Workaround: Increase the number of active threads available to the data service by making the following changes: For Internet Information Services (IIS), edit the IIS configuration file settings to increase the value of AspProcessorThreadMax from its default value of 25 to 50. See the Microsoft documentation for version-specific instructions about editing the configuration files. In IIS 5.0, the settings are contained in the MetaBase.bin file, a binary file you can edit by using the IIS Management console. Later versions of IIS store configuration settings in a XML file called MetaBase.xml. For the data service, increase the value of the MaxThreads key in the web.config file from the default of 10 to 50. The web.config file is located in the EDService directory (by default, C:\Program Files\BMC Software\EDService), and you can edit it with a standard text editor such as Notepad or Wordpad. As a general rule, limit the number of data sources to a maximum of 20 for each data server (the BMC Visualizer and BMC Automator server that is used to populate the data).

BMC Impact Portal 7.0.02

The BMC Impact Portal is a browser-based console that you use to monitor the status of business services and their service components. Through the BMC Impact Portal, you view the current status of a business service and those components that support the service, and generate and view relevant reports. You can view the events originating from a particular service component and the events that propagate to a service component, both of which might determine its current state.

Through the BMC Impact Portal, you can view and configure the following properties of service components:

users and user groups that have access to the components

report goals

image views

In addition, you deploy and launch the BMC® Impact Service Model Editor (SME) and the BMC Impact Explorer console to local desktops from the BMC Impact Portal.

---

NOTE:

When you install the BMC Impact Portal, you also install its related applications automatically: BMC Impact Service Model Editor BMC Impact Publishing Server BMC Impact Integration Web Services

---

Version compatibility between BMC Impact Portal and BMC Impact Manager

The BMC Impact Portal version 7.0.02 and its related applications are compatible with version 7.0.01 and 7.0.02 of the BMC Impact Manager product. They are not compatible with previous versions of the products. The BMC Impact Manager product provides the core functionality for event management and service impact management. Version 7.0.02 of BMC Impact Manager is backward-compatible with version 5.x of BMC Impact Manager. It is not, however, compatible with versions prior to 5.0. For more information about the BMC Impact Manager, see “About BMC Impact Manager” in any of the following guides that are packaged with the 7.0.02 release:

BMC Impact Solutions: Event Monitoring

BMC Impact Solutions: Knowledge Base Development

BMC Impact Solutions: Administration

What’s changed in BMC Impact Portal

This section describes changes in BMC Impact Portal.

BMC product support

The BMC Impact Portal supports BMC Impact Solutions 7.0.02.

Desktop status indicator supports HTTPS

With this version, the desktop status indicator supports not only the standard HTTP protocol but also the secure HTTPS protocol.

Improved reporting performance

By default, data for reports is collected, summarized, and stored in the BMC Impact Portal database for all components and for all report types. The Reports Configurator utility enables you to prevent the summarization of report data for all components or report types or for specific components or report types. Reducing the volume of summarization data reduces the time required for report generation, which is especially useful in environments with large service models.

Open issues and workarounds in BMC Impact Portal

Table 19 describes issues that remain open for the BMC Impact Portal 7.0.02. The tracking ID is listed if one has been assigned to the issue.

Table 19 Open issues and workarounds in BMC Impact Portal (part 1 of 3)

Tracking ID	Issue
QM000457816	BMC Impact Portal and BMC Performance Manager Portal modules do not share a report time range selection. This means that some elements within the environment are not synchronized in terms of time range.
QM000469955	If you press Enter while searching for components in Dashboard => Add => Providers Status Table =>Select Object to Show, the system shows the previous page instead of the search results.
QM000472966	If you are a Service Executive user, you do not have permissions to the Configure tab. However, you are still granted permissions to options available through the Configure tab, such as About, Account Information, and Blackout Periods.
QM000477027	The Restricted Objects in the Object Group Navigation tree erroneously display a check box. If you clear the check box, the system might display an error page.
QM000477134	The group name is missing from the titles of group properties pages.
QM000482375	The icon that indicates the default sorting order in tables does not appear.
QM000505470	The AR System server name is not updatd when it is changed on the BMC Portal. Workaround: See "AR System server name is not updated when it is changed on the BMC Portal"
QM000505595	If you log off a Service Model Editor session that has been open for an extended period of time and log on to the BMC Portal, you can access only the BMC Service Model Editor. The BMC Portal logon screen does not enable access to the BMC Portal. Workaround: Open the BMC Portal in a new browser window to log on.
QM000539075, SW00250490	On Solaris, AR Server exception error messages in non-English language might not be displayed correctly in the Portal => Synchronize User Groups page. Workaround: Select a UTF-8 locale (for example, ja_JP.UTF-8) to log on, and then restart the BMC Portal.
QM000540747	Desktop Status Indicator might display question marks when the JNLP file contains characters outside the ASCII character set. More information about the issue is available on the Sun Microsystems website at: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6205837
QM000542991	During an upgrade from version 5.1, changes to the default user group and descriptions are not handled correctly. One section uses an old name while another section uses the new name.
QM001521390	When upgrading the BMC Impact Portal, the cost value for a given CI might be incorrectly displayed.
QM001522121	The section “To associate an icon with a service model component class” in BMC Impact Solutions: Administration is missing an additional location for the component_icon.properties file. Workaround: The correct information for this section is: Edit the component_icon.properties file. By default, the component_icon.properties file is located in the following directory paths: Solaris—$BMC_Portal_Kit_Home/appserver/websdk/tools/jboss/server/all/data /smsConsoleServer/Image/Icon and $BMC_Portal_Kit_Home/appserver/websdk/tools/jboss/server/all/conf/properties /smsConsoleServer Windows—%BMC_Portal_Kit_Home%\appserver\websdk\tools\jboss\server \all\data\smsConsoleServer\Image\Icon and %BMC_Portal_Kit_Home%\appserver\websdk\tools\jboss\server\all\conf\ properties\smsConsoleServer
SW00227787	The icons for the components defined for the following classes are not consistent between service impact management components such as BMC Impact Portal, BMC Impact Explorer, and BMC Service Model Editor: ConnectivityGroup ConnectivitySegment LNsGroup SAPService SAPSoftwareComponent BMC Computer System subclasses
SW00250831	When an admin or superadmin user logs on as a different user, the set status functionality is not available. When the user logs in directly, the functionality is available if the user has the appropriate permissions.

AR System server name is not updated when it is changed on the BMC Portal

To ensure that the AR System server name matches the name that was entered in the Configure tab of the BMC Portal, update the name of the AR System server by using the Remedy Configuration Tool.

1 Access the Remedy Configuration Tool in one of the following ways:

Open a browser and enter the following URL:
http://webserver_port/contextpath/apps/shared/config/config.jsp

— webserver is the fully qualified name of Remedy Mid Tier, such as server_name.company.com.

— port is an optional port number, required if the web server is not using the default port (port 80).

— contextpath is the path to the location of the Remedy Mid Tier (arsys by default).

If the Remedy Mid Tier is installed on the local computer in the default directory, enter the following URL in your browser:
http://localhost/arsys/apps/shared/config/config.jsp.

On a Windows computer where the Remedy Mid Tier is locally installed, choose Start => Programs=> Action Request System => Remedy Mid Tier => Configure ARSYSTEM on Localhost.

2 Log on to the Remedy Configuration tool using your password (the default password is arsystem).

3 Change the appropriate configuration parameters to match those entered in the BMC Portal.

For more information about the Remedy Configuration tool, see the Action Request System 6.0 Configuring AR System document.

User and user group visibility across BMC Impact Solutions components

Be aware of the following considerations when working with users and user groups across different BMC Impact Solutions products:

Users and user groups created in the BMC Atrium CMDB are not visible in the BMC Impact Portal.

User groups created in the BMC Atrium CMDB, such as those created with the User tool or another component such as Remedy IT Service Management (ITSM), are not visible in the BMC Impact Portal.

Users created in the BMC Impact Portal are not visible in other BMC Business Service Management (BSM) Solutions components, such as Remedy IT Service Management (ITSM).

Duplication of user groups in the BMC Atrium CMDB

Do not create the same sets of users and user groups in both the BMC Atrium CMDB and the BMC Impact Portal. Maintaining duplicate user groups and users in both the BMC Atrium CMDB and the BMC Impact Portal causes the creation of additional duplicates of these same users and user groups in the BMC Atrium CMDB.

Corrected problems for BMC Impact Portal

Table 20 describes problems that were reported in earlier releases of BMC Impact Portal that have been corrected in this release:

Table 20 Corrected problems for BMC Impact Portal 7.0.02 (part 1 of 2)

Tracking number	Issue
Problems corrected in version 7.0.02
QM000473999	The Business folder indicated CRITICAL when all its components had a status of OK after PS reinitialization of the cell.
QM000474374	When you viewed all events from the Events tab in a sorted list, only the first five events were sorted.
QM000481272	The mean time between failures (MTBF) and mean time between service incidents (MTBSI) descriptions did not display the correct associated icon.
QM000519689	On the Reports tab, when you sent email, it did not contain the chart or the data for Status History.
QM000520704	After installation, the cell waited 3 seconds for registration. If it was still not registered, you had to go to the Impact Manager Administration page and re-register the cell.
QM000540745	When you were using the BMC Impact Portal in a localized environment, mouse tooltips did not display the correct text.
QM000548080	Cost Unit values were not displayed in the Losses report on the Reports tab.
QM001510514	The BMC Impact Portal did not correctly display object permissions.
Problems corrected in version 7.0.01
QM000472939	If an object status was manually set, nothing on the Events tab indicated that this status was manually set.
QM000482380	Some database icons did not display transparency properly.
QM000489732	When you created a custom name for the logon screen, the Product Name field allowed entry of single and double quotation marks, but did not display them correctly on the Portal logon screen.
QM000492122	If you attempted to install the datastore for BMC Impact Portal, the system prompted you for a BMC Impact Manager instance (cell), even though none is required with the datastore alone.
QM000515921	After BMC Impact Manager was down for some time, the Portal would no longer try to reconnect to it. The list of BMC Impact Managers in the Portal was displayed as successfully registered, but the portal.log file indicated that the cell was not connected.

BMC Impact Service Model Editor (SME) 7.0.02

The BMC Impact Service Model Editor (SME) is a GUI-based editing tool, interfaced with the BMC Atrium CMDB, that you use to create and edit service model data in user sandbox datasets and then promote these data to the CMDB production dataset. From there, automated publishing sends the service model data to specified BMC Impact Managers (cells).

Within the SME, you create component instances from templates by using drag-and-drop techniques, define relationships among those instances, and specify which instances and relationships to distribute to your BMC Impact Manager instances.

The component templates in the SME reference class definitions in the Common Data Model (CDM) of the BMC Atrium CMDB. The SME enables you to access the Class Manager Console through the Remedy Mid Tier. New or updated class definitions in the CDM must be synchronized with the class definitions in the service impact management (SIM) Knowledge Base (KB) of the BMC Impact Managers (cells).

What’s changed in BMC Impact Service Model Editor

This section describes changes in BMC Impact Service Model Editor 7.0.02.

Enhanced CI editing

Configuration items can be more easily edited, with several interface enhancements in the SME. These enhancements include:

a new magnifier function that enables you to zoom in on small icons

cascading and tiling of views

an enhanced template pane

quick creation of multiple components of the same class with default values and attributes

a new table view of CIs

the ability to edit components from within the table views

the ability to specify the number of components of the same type that you want to add to the Sandbox view window

a warning when you attempt to edit a component is already being edited

Open issues and workarounds in BMC Impact Service Model Editor

Table 21 describes issues that remain open for the SME. The table lists the tracking ID if one has been assigned to the issue.

Table 21 Open issues and workarounds in BMC Impact Service Model Editor (part 1 of 4)

Tracking ID	Issue
QM000469034	If you cut a component from a view, it will still appear in the Topology view when you right-click and select Show Topology for the top component.
QM000469498	If you create a new folder in the console navigation tree and then delete or rename the folder, the entire tree collapses. The tree still exists but you must re-expand it.
QM000469783	The Options feature of the Service Model Editor log displays the following erroneous message after you enter a new value in the Buffer Size field: Changing the log buffer size will discard current log entries However, the current log entries are retained after the change.
QM000470343	After you restart the BMC Portal application server and the BMC Publishing Server services (or daemons), you must close Service Model Editor and then relaunch it. When you restart a BMC Portal application server, you must exit any active BMC Impact Service Model Editor session and reopen it.
QM000475071	When you launch searches in the Find dockable window, you cannot use the underscore (_) in your search strings. When connected with an Oracle database, the AR System server does not support search strings that use the underscore.
QM000475285	Under the Mozilla browser on Solaris, the Service Model Editor Help button on the Export Cell Meta Data dialog box is dimmed. Workaround: You can find the Help text for the Export Cell Meta Data dialog box under the Help topic “To synchronize class definitions in the SIM KB.”
QM000476712	The Help dialog available box from Saved Finds displays in the BMC Performance Manager Portal Web Console with an error message.
QM000499539	When you initially open the BMC Impact Service Model Editor on a localized system, if you create a component with a multibyte character name in the view, the multibyte characters are displayed as square marks. Workaround: Click Tools => Personal Options and select a font that is appropriate for the current language locale.
QM000501503	When you specify a Windows style path for the log file during installation and then launch BMC Impact Service Model Editor from a UNIX system, the saved path information is not valid because a Windows style separator (\) is used instead of the UNIX style (/).
QM000506562	Sometimes when you expand a handle to show the provider relationships, the related component instances are displayed, but the + symbol is still visible.
QM000507613	When you install BMC Performance Manager Portal first and then do an over-the-top installation of BMC Impact Portal, BMC Impact Service Model Editor cannot create a component instance.
QM000517974	Client-to-RMI communications are not completely tunneled over HTTP. An environment with a firewall between client and server (with HTTP port open) causes client failure until ports 9378 and 9386 are opened in the firewall.
QM000545418	The SIM workflow is not taking into account attributes that are added to SIM CDM class BMC_Impact. This could cause values of those attributes to be overwritten with old values.
QM000549671	Promoted objects that are added to the navigation tree in BMC Impact Service Model Editor but are not published appear in the Portal tree as nonexistent—they should not appear at all until published.
QM000552003	When creating a component, entering string data into some fields of the Other tab (including Site, Region, and Company) sometimes fails and prevents input from being saved. This happens when ITSM is installed in the system along with SIM.
QM000553667	Under certain circumstances, canceling the promotion of a service model might fail due to timing issues. After an object has been pushed to the reconciliation engine, it cannot be recalled by clicking the Stop button.
QM001510281	If discovery merges updated values into BMC.ASSET while a CI is being edited (for example, a CI being moved to in-model) in the BMC Impact Service Model Editor sandbox and not yet promoted, then a subsequent promotion will reset the old values. Workaround: Do not merge discovery sources into BMC.ASSET while CIs are edited in the BMC Impact Service Model Editor sandbox.
QM001510282	After a CI is incorporated into a service model by way of BMC Impact Service Model Editor sandbox and promotion, it can be updated only by means of the BMC Impact Service Model Editor. Updates from discovery sources and AM are not merged into the asset dataset, because the default precedence of BMC Impact Service Model Editor is highest; thus, attributes belong to SIM.SANDBOX (as indicated in AttributeDataSourceList). Workaround: Increase the default precedence of other datasets in the BMC Default Merge Precedence Set. However, this will imply that updates in BMC Impact Service Model Editor sandbox will not be merged into BMC.ASSET.
QM001511072	The Promotion in Progress status might not be updated when you promote models up to 3K from the SME. Workaround: Manually verify that the promotion was successful and exit SME to clear the dialog box. To verify that a model was successfully published, use the Impact Manager command mgetinfo -n cellname -v services.
QM001522096	The section “Guidelines for associating a custom icon with a service model component class” in BMC Impact Solutions: Administration provides an incorrect path to the BMC Impact Service Model Editor icons. Workaround: Replace the following incorrect paths in the documentation with the correct paths, as follows Incorrect paths: (Windows) %BMC_Portal_Kit_Home%\appserver\websdk\tools\jboss\server\all\modules\ smsSme.sar\smsSme.war\images (Solaris) $BMC_Portal_Kit_Home/appserver/websdk/tools/jboss/server/all/modules/smsSme.sar/ smsSme.war/images Correct paths: (Windows) %BMC_Portal_Kit_Home%\appserver\websdk\tools\jboss\server\all\modules\ smsSme.sar\smsSme.war\images \objects (Solaris) $BMC_Portal_Kit_Home/appserver/websdk/tools/jboss/server/all/modules/ smsSme.sar/smsSme.war/images/objects If the objects subdirectory is missing, create it and then move all the files under the images directory to the new objects subdirectory.
QM001522099	After you associate a custom icon to a service model component class, the icon is displayed in the Sandbox view, but it does not display in the Templates pane. Instead, the default question mark icon is displayed.
none	If you load an update to the reconciliation rules for compatibility with BMC Topology Discovery and Marimba Configuration Discovery rules, object linking does not function.
SW00225607	If you perform a discovery and generate impacts with BMC Topology Discovery and export the data to the BMC Atrium CMDB, then retrieve those components and impacts in the BMC Service Model Editor, if you then promote, the relationship name might appear truncated in the Promotion Preview dialog box.
SW00225688	User and user group visibility issues exist across BMC Impact Solutions components.
SW00225788	If you create service models in BMC Service Model Editor, do not create infrastructure components (those that can be discovered from BSM discovery tools), because this might lead to duplicate components in the BMC Atrium CMDB. In some cases a new component is created by the discovery tool and some attribute values, such as Description, are not restored.
SW00227787	The icons for the components defined for the following classes are not consistent between service impact management components such as BMC Impact Portal, BMC Impact Explorer, and BMC Service Model Editor: ConnectivityGroup ConnectivitySegment LNsGroup SAPService SAPSoftwareComponent BMC Computer System subclasses
SW00228019	Workaround: See "Issues in marking components for deletion."
SW00253184	MBCS name is displayed with garbage characters when you export a component with the MBCS name and then import the XML file.

Issues in marking components for deletion

Consider the following issues with marking components for deletion:

Components that are marked for deletion in the BMC Service Model Editor (as when you use the Delete from CMDB function) might be rediscovered by BMC Topology Discovery or Marimba Configuration Discovery".

Topology Discovery finds a computer and this computer is subsequently disconnected. If you mark the computer for deletion, the discovery application deletes it from the BMC Topology Discovery dataset. If you later reconnect this computer, when discovery is run again, the discovery tool rediscovers this computer and adds it back to the BMC Asset dataset.

Relationships that were automatically deleted when a component was marked for deletion in the BMC Service Model Editor might not be restored when a component is rediscovered.

Discovered components might appear and disappear without the intervention of a BMC Service Model Editor user. This is expected behavior if discovery tools are used.

If an object has been permanently deleted (as when purge activities are done) and the object is subsequently rediscovered, BMC Topology Discovery will create a new instance that might not be reconciled properly, resulting in a duplicate in the BMC Asset dataset.

Corrected issues in BMC Impact Service Model Editor

Table 22 describes issues that have been corrected in BMC Impact Service Model Editor 7.0.02.

Table 22 Corrected issues in BMC Impact Service Model Editor (part 1 of 2)

Tracking ID	Issue
Problems corrected in version 7.0.02
QM000504250	In Publish History, when you selected Open in New View, there was no notification that the object was opened in a new View.
QM000505567	In the Promotion Preview dialog box, the management data name did not display properly.
QM000514197 SW00225688	Users in the Service Administrator user group could not log on to BMC Impact Service Model Editor.
QM000520073	When the client did not have Java Web Start installed, BMC Impact Service Model Editor did not launch.
QM001510903	In some cases, assigning a large number of CIs to a cell in one operation could cause the Portal to crash.
Problems corrected in version 7.0.01
QM000466163	If you created a component, you were not listed as the component editor.
QM000490361	The Remedy Application Service (reconciliation engine) updated components nightly around 11 P.M. It also erroneously caused the component-edited icon to be displayed against components that had not been edited.
QM000505426	On the console navigation tree, two shortcut keys, Crtl-O (Open in New View) and Crtl-P (Place in Selected View), do not function.
QM000506284	Even when you were logged out of BMC Impact Service Model Editor you could configure and rearrange columns in Find.
QM000509639	When you viewed publishing logs from the Service Model Editor which involved SIM_MATCH_TABLEs, the publishing log might not have displayed correctly.
QM000507818 QM000508225	If you created two alias formulas that used the identical input matching, you could not publish the formulas successfully.
QM000517778 SW00229210	The SIM MATCH CLASS extension failed to load if you were installing from an image on the network because the CMDB image is located on the network and extension loader could not resolve the current directory.

BMC Impact Publishing Server 7.0.02

The BMC Impact Publishing Server is the behind-the-scenes application that publishes a service model to specified BMC Impact Managers (cells). The Publishing Server

triggers an automated publication at the termination of BMC Impact Service Model Editor’s promotion or any reconciliation run

publishes CMDB asset service model data to cells as manually requested by way of the publish CLI

exports the class definitions to BAROC files, ready for distribution to the BMC Impact Managers

stores a master copy of the published service model in the CMDB impact dataset

What’s changed in BMC Impact Publishing Server

The section describes changes in the BMC Impact Publishing Server product.

BMC Impact Publishing Server now supports BMC Impact Solutions 7.0.02.

You can now enable or disable automated publishing for each publish environment.

You can now define the HomeCell parameter for the publish environment. If this parameter is set, all the data of the publish environment will be published to the specified cell. In this case, HomeCellAliases are not used.

You can now define a default HomeCell parameter value. If you define a default HomeCell value, CIs without a defined HomeCellAlias value are published to the default HomeCell.

Multiple publish environments can now be defined on the same asset dataset.

Open issues and workarounds in BMC Impact Publishing Server

Table 23 describes issues that remain open for the BMC Impact Publishing Server 7.0.02.

Table 23 Open issues and workarounds in BMC Impact Publishing Server (part 1 of 3)

Tracking ID	Issue
QM000474574	There is no publication progress indicator. Publication of large scale service models (5,000 or more objects) might take 20 minutes or longer.
QM000515488	The Publishing Server does not set propagated attributes like SystemName and SystemClassId attributes in impact datasets which results in: the asset instance and the impact instance having differences so that, at publication, the instance is detected as modified, when it has not actually been modified after reinitialization, these slots have no value in cells
QM000551174	Diary fields hang in impact datasets. This causes a failure in the RDBMS, which causes the Publishing Server to fail. Workaround: To prevent Publishing Server failures, the Notes (Diary) fields are not set in impact datasets. This means that the asset and impact instances might appear as modified when they are not Diary slots have no value after cell reinitialization
QM000553150	If you add a purge or merge activity to an existing reconciliation job after the Publishing Server is started, the activity is not considered during automated publishing. Workaround: Restart the Publishing Server any time you modify a recon job.
QM000553157	Automated publishing does not executing reconciliation jobs that have an “Execute Job” activity. Workaround: Replace the “Execute Job” activity with the activities from the called job.
QM000554963	You cannot publish successfully when you move CIs that were published to a cell that was unregistered. For more information, see "Cannot publish when moving CIs that were published to a cell that was unregistered".
QM000554964	When you re-register a cell that was unregistered, the cell is not automatically initialized. Workaround: Manually reinitialize the cell using the pinit command.
QM001513365	For publish environments with overlay asset datasets and an overlay publish mode, automated publication is by default disabled. When you are running in automated mode, a promotion from SME does not trigger an automated publish of SME's test service model.
QM001519712	When you use the -v option with the publish command to publish a large service model (greater than 2 K) that has invalid data, the Publishing Server might hang with the error JMSException:NullPointerException, and the request log file contains only the request. Workaround: Publish in small chunks and correct the invalid data as identified by the failed publication.
QM001519714	When you publish a large service model (greater than 2K) with invalid data (including, for instance, CIs that point to a nonexistent PropagationModel) the publication might hang on connection with smmgr with an IOException. Workaround: Publish in small chunks and correct the invalid data as identified by the failed publication.
QM001519839	When the BIPUserName or BIPPassword configuration parameters in %PS_HOME%/etc/pserver.conf contain an error, the Publishing Server tries 15 times to connect BMC Impact Portal before exiting with error code 14 (unable to initialize publish environments). An error message Unable to authenticate user <BIPUserName> is created on every trial. Workaround: Correct the BIPUserName or BIPPassword in pserver.conf. If you reenter the password, specify it in plain text and restart the Publishing Server to encrypt it.
QM001519845	In a clustered environment, the BMC Impact Portal incorrectly updates the pserver.conf and pclient.conf files with the physical host name rather than the virtual host name. Workaround: See "Updating configuration files with virtual host name in a clustered environment".
QM001519848	In a clustered environment, the user of the Publishing Server CLI must authenticate on the Publishing Server host. Workaround: Set BIPServers, BIPUserName and BIPPassword in pclient.conf.
QM000520156	If a component is modified with an invalid StatusModel and you attempt to publish the service model, the Publishing Server does not prevent the completion of the publish job. Workaround: Set a valid StatusModel and publish again.
QM001521946	Information about configuring timeout parameters between the Publishing Server, smmgr, and cell is missing from the section “Troubleshooting publication failures” in BMC Impact Solutions: Administration. Workaround: See "Configuring timeout parameters between the Publishing Server, smmgr, and cell for publishing large service models".
QM001521953	Information about configuring timeout parameters between the Publishing Server and BMC Atrium CMBD is missing from the section “Troubleshooting publication failures” in BMC Impact Solutions: Administration. Workaround: See "Configuring timeout parameters between the Publishing Server and the BMC Atrium CMDB for publishing large service models".
SW00244023	When the NOTIFY plug-in is not loaded, reconciliation job runs hang and remain in a started status. This causes BMC Impact Service Model Editor promotion and every other reconciliation job to hang. Workaround: Ensure that the NOTIFY plug-in configuration and the AR plug-in environment variables are correct so that the NOTIFY plug-in is loaded. For information about verifying that the plug-in is loaded, see “Verify the Notify ARDBC plug-in” in BMC Impact Solutions: Administration.

Cannot publish when moving CIs that were published to a cell that was unregistered

Move the CIs that have been published to a cell that you want to unregister, before unregistering the cell.

If you did not move the CIs before unregistering, use the following procedure:

1 Re-register a cell using the name of the unregistered cell.

2 Initialize the cell using the CLI command pinit.

3 Move the CIs from the cell that needs to be unregistered to another cell.

4 Publish.

5 Unregister the cell.

Updating configuration files with virtual host name in a clustered environment

Perform the following steps to update the pserver.conf and pclient.conf files with the virtual host name:

1 Edit the pserver.conf file as follows:

A Add the line BIPFailoverConfig=F.

B Set the JNPServers and BIPServers parameters with the virtual host address.

2 Edit the pclient.conf file as follows:

A Add the line BIPFailoverConfig=F.

B Set the JNPServers and BIPServers parameters with the virtual host address.

Configuring timeout parameters between the Publishing Server, smmgr, and cell for publishing large service models

When publishing large models, ensure that the following timeout configuration parameters are set high enough:

%MCELL_HOME%/etc/smmgr.conf MessageBufferKeepSent (timeout for communication between smmgr and cell)

%PS_HOME%/etc/pserver.conf SMMMessageBufferKeepSent (timeout for communication between Publishing Server and smmgr)

By default, the Publishing Server estimates the timeout needed. If this fails, set SMMMessageBufferKeepSentEstimate=F and increase SMMMessageBufferKeepSent.

If publication fails with the message Publish validation of IMs failed, use the following information to troubleshoot the problem according to the message you receive:

IM <CellName> failed to upload service model from SMM

The MessageBufferKeepSent of smmgr is not high enough and expires before the cell has terminated uploading service model from smmgr.

IM <CellName> did not answer the request

The SMMMessageBufferKeepSent of Publishing Server is not high enough and expires before the smmgr has applied the verification or upload.

In both cases, the cell continues to upload and, after a while, the service model will be available in the cell. Nevertheless, reinitialize the cell and publish again to avoid subsequent publish failures with the message Unique data identifier not/already in use.

Configuring timeout parameters between the Publishing Server and the BMC Atrium CMDB for publishing large service models

When publishing large models, ensure that the %PS_HOME%/etc/pserver.conf ARSXLongTimeOut configuration parameter is set high enough. This parameter specifies the timeout value for the communication between the Publishing Server and the CMDB.

By default, the Publishing Server estimates the timeout needed. If this fails, set ARSXLongTimeOutEstimate=F and increase ARSXLongTimeOut.

If publication fails with the message Failure while applying publish on CMDB - Error - 92 Timeout during database update, the operation has been accepted by the server and will usually complete successfully, the ARSXLongTimeOut of Publishing Server is not set high enough and expires before the CMDB has terminated committing modifications in impact dataset.

The CMDB continues to commit modifications in the impact dataset, and after a while, the service model will be available in the impact dataset. Ensure that the parameters are set correctly.

The same failure might occur when you initialize the CMDB with large service models.

Corrected issues in BMC Impact Publishing Server

Table 24 describes issues that have been corrected in BMC Impact Publishing Server.

Table 24 Corrected issues in BMC Impact Publishing Server (part 1 of 2)

Tracking ID	Issue
QM000549914	When the AR Server was down, the Publishing Server attempted to reestablish a connection. If you used psstat to determine its status, it returned misleading information that the service was started in automatic mode when it was not.
QM000554739	The CellAliases of an environment in BMC.IMPACT.PROD reflected the situation at the time of the last successful publish. When closing an environment, all the Publishing Server internal data should be removed but could contain obsolete CellAliases when reinitialized.
QM000554853	For a publish environment with AssetDataSetType= Overlay and PublishModeServiceModel=Current, publication failed if the CI’s ServiceModelSet was set to IN without taking the other endpoint of an existing impact relationship in the asset overlay dataset.
QM000554860	Publishing server CLIs displayed an exception when launched in an unwritable directory.
QM000554993	When EnvId matches TEST and AssetDataSetType= Overlay and PublishModeServiceModel=Overlay, publication problems occurred.
QM000555080	The command pinit -a did not work before a first successful publication.
QM001510280	Merges to BMC.ASSET that did not use the BMC Default Merge Precedence Set caused publication issues.
QM001510763	The ps_env_open process failed after the Publishing Server was reinstalled because the impact dataset already existed in the CMDB.
QM001515688	The publishing server could not successfully publish a large service model, and it reported the following error: "SMM <name> did not answer the request." See "Configuring timeout parameters between the Publishing Server, smmgr, and cell for publishing large service models" for additional information about configuring timeout intervals. See the section “Diagnosing publication failures” in BMC Impact Solutions: Administration for additional information.
QM001516987	If the BMC Atrium CMDB encountered an exception during a large publish job, the publishing server incorrectly reported that the publish job failed. See "Configuring timeout parameters between the Publishing Server and the BMC Atrium CMDB for publishing large service models" for information about configuring timeout intervals. See the section “Diagnosing publication failures” in BMC Impact Solutions: Administration for additional information.
Problems corrected in version 7.0.01
QM000516577	Component Aliases with semicolons were not parsed correctly and caused the publish to fail.
QM000517328	When an error occurred while CMDB was committing, the error message was too generic.
QM000545531	Publish failed in a mixed BMC Event Manager and BMC Impact Manager environment.
QM000554024	When a component or relationship ended with a backslash character (\), a syntax error occurred and the model could not be published.

BMC Impact Integration Web Services 2.2.00

The BMC Impact Integration Web Services Server (BMC II Web Services Server) provides a loosely coupled interface based on Web services, which can be used for exchanging events and information with BMC Impact Manager solutions. BMC Performance Manager, for example, uses BMC II Web Services Server to send events to BMC Impact Manager.

The BMC II Web Services Server is installed automatically when you install the BMC Impact Portal module of the BMC Portal product. You can also install the BMC Impact Integration Web Services Server and sample client code manually from the BMC Impact Manager 7.0.02 installation CD or the BMC Impact Solutions DVD.

---

NOTE:

The BMC II Web Services Server is also a component of the BMC Impact Integration Developer’s Kit. You can view information about the Kit at http://shop.bmc.com.

---

What’s new in BMC II Web Services Server

Version 3.0 of the BMC Impact Integration Web Services Server has an additional configuration parameter, DisableSlotListSet, in the iiws.conf file and now includes supplemental selector files that facilitate event filtering.

DisableSlotListSet

The DisableSlotListSet configuration parameter, which should always be set to Yes, enables the BMC II Web Services Server to process incoming messages that are enclosed within brackets as regular slot strings.

Supplemental selector files

The following supplemental message selector files serve the purpose of filtering for incoming and outgoing events:

recvfilterin.selector

recvfilterout.selector

sendfilterin.selector

sendfilterout.selector

On the BMC II Web Services Server side, these supplemental message selector files are stored under %installDirectory%\mcell or $installDirectory/mcell. By default, the filters contained in these files are turned off (Enable=FALSE). When you enable them and define the selectors, they are used in conjunction with the iiws.selector file to help filter events in or out.

All incoming and outgoing events that are sent or received by the BMC II Web Services Server are first scanned by the filters in these message selector files. These filters are global, applying to all clients and to all events that are passed back and forth between the BMC II Web Services Server and the cell. If the incoming events are not rejected by the supplemental message selector files, then they are scanned by the filters in the BMC II Web Services Server’s iiws.selector file, which is specific to the client request.

What’s changed in BMC II Web Services Server

The section describes changes in the BMC II Web Services Server component.

Enforced typing

The BMC II Web Services Server 3.0 enforces type implementation. When you program your integration client, if the slot type is LIST_OF, in the client code you must define a corresponding nameValue type XY_ARRAY with an assigned array value. For example, if the slot type to be passed is LIST_OF STRING, you define the corresponding nameValue type as STRING_ARRAY.

Open issues and workarounds in BMC II Web Services Server

This section describes issues that remain open in this release.

Table 25 Open issues and workarounds in BMC II Web Services Server  

Tracking ID	Issue
QM000546853	During a command-line installation, if you attempt to exit the installation utility after rejecting the terms of the license agreement, the installation utility will not exit. Workaround: To exit the installation utility, accept the terms of the license agreement and then exit the installation utility.
QM000544638	When you install the BMC II Web Services Server from the CD or DVD, the command ./installScript -is:javahome /directoryPathToJRE does not work n Red Hat Linux®. Workaround: None. Ensure that Java is installed under the /usr/bin directory.
QM000417404	Basic C APIs might terminate unexpectedly. Workaround: See "Basic C APIs might terminate unexpectedly".
none	When a web service client is using an unreliable subscription call and the BMC II Web Services Server is restarted, the client no longer receives events. The bmciiws_getEvents operation returns an error message similar to The client context is not subscribed to requested filter.File impl.cpp, Line 1106. Workaround: None. Restart the web service client and initiate another subscription call.

Basic C APIs might terminate unexpectedly

The Basic C APIs might terminate unexpectedly on startup if the configuration file (integration_name.conf file) contains a syntax error, such as an extra equal sign (=), in a statement. For example, if you enter the equality operator (==) instead of the assignment operator (=) as shown:

ServerDirectoryName==$MCELL_HOME/etc/mcell.dir

To work around this issue, ensure that the configuration file is formatted as specified in the BMC Impact Integration Developer’s Kit documentation and that it does not contain spelling errors.

Corrected issues in BMC II Web Services Server

The following issues were reported in earlier releases of the BMC Portal and have been corrected in this release.

Table 26 Corrected issues in BMC II Web Services Server  

Tracking ID	Description
QM000547464	Multiple web service clients can submit queries to the same cell within the same millisecond caused accurate results.
QM000523846	When you installed the BMC II Web Services Server in console mode on UNIX platforms, all default values were not visible.

Requirements and supported resources

This section provides release-specific information about requirements and supported resources for version 3.0 of BMC II Web Services Server. For general information about requirements and supported resources, see the BMC Impact Integration Web Services Server Installation and Configuration Guide.

Product requirements

Table 27 on page 67 lists the versions and features of BMC Impact Manager (BMC IM) that the BMC II Web Services Server supports. Versions 5.1 and later are able to run in an operating system that is in Simplified Chinese, Traditional Chinese, Korean, or Japanese.

Table 27 BMC II Web Services Server support for BMC IM 

BMC IM version	Event and data exchange	Service model queries	Language support
5.0.01	yes	yes	no
5.1	yes	yes	yes
5.1.01	yes	yes	yes
7.0.x	yes	yes	yes

OpenSSL compatibility

Version 3.0 of the BMC II Web Services Server supports version 9.6 of OpenSSL on all supported platforms.

Operating system support

Table 28 lists the operating systems that version 3.0 of the BMC II Web Services Server supports.

Table 28 Supported operating systems 

Operating system	Version or service pack
Microsoft Windows 2000 Pro	SP3, SP4
Microsoft Windows 2000 Server	SP4
Microsoft Windows XP Professional Edition	SP1, SP2
Microsoft Windows 2003 Server	SP1
Red Hat Enterprise Linux Advanced Server (Intel)	3.0, 4.0
SUSE Linux Enterprise Server (Intel)	9.0
Sun Solaris (SPARC)	9, 10
HP-UX (PA-RISC)	11.0, 11.11
IBM AIX (POWER)	5.2, 5.3

Intention to drop support

BMC intends to drop support for Red Hat Enterprise Linux Advanced Server (Intel) 3.0 and for HP-UX (PA-RISC) 11.0 in the next release of the BMC II Web Services Server.

Support for BMC II Web Services Server

This section provides information about

BMC Software support for BMC II Web Services Server

documents that support the product

Levels of support

The following table shows the schedule for full support and limited support for the version 3.0 BMC II Web Services Server component. The dates are shown in m/dd/yyyy format.

Version	Full support ends	Limited support ends
3.0	to be determined	to be determined
2.2.00	12/31/2007	12/31/2008
2.1.00	6/30/2007	6/30/2008

Product document

The BMC Impact Integration Web Services Server Installation and Configuration Guide supports this product.

Support for BMC Portal

This section provides information about

BMC Software support for the modules (licensed products) that compose the BMC Portal

documents that support the BMC Portal modules

how to obtain the latest information about the BMC Portal modules

how to order the BMC Portal modules

how to contact BMC Software Customer Support

Levels of support

BMC Software supports the following product versions and releases for the BMC Portal modules:

Module and version	Level of support
BMC Performance Manager Portal
BMC Performance Manager Portal 2.4.x	full
BMC Performance Manager Portal 2.3.x	full
BMC Performance Manager Portal 2.1.x	full
BMC Performance Manager Portal 1.2.x	limited a
BMC Performance Exception Detector
BMC Performance Exception Detector 1.3.x	full
BMC Performance Exception Detector 1.1.x	full
BMC Impact Portal
BMC Impact Portal 7.0.02	full
BMC Impact Portal 7.0.01	full
BMC Impact Portal 5.1	full b
BMC Impact Portal 5.0	limited c

c Support for this product release will be dropped in August 2007. Support for this product release changes to limited on October 31, 2007 and will be dropped on December 31, 2007. Support for this product release will be dropped on June 30, 2007.

For more information about the latest Support policies and guidelines, see the Customer Support page of the BMC Software website at http://www.bmc.com/support_home.

BMC Portal documents

The following documents support the BMC Portal modules:

Table 29 BMC Portal documentation 

Module	Document title
all modules	BMC Portal Installation Guide
	BMC Portal Getting Started
	Creating, obtaining, and installing SSL certificates for the Portal web server installation notes
BMC Performance Manager Portal	BMC Performance Manager Portal Monitoring and Management Guide
	BMC Performance Manager Development and Certification Guide
	PATROL Security User Guide
	BMC Portal Architecture Diagram
BMC Performance Exception Detector	BMC Performance Exception Detector Implementation Guide
BMC Impact Portal	BMC Impact Solutions Release Notes
	BMC Impact Solutions Installation Guide
	BMC Impact Solutions System Configuration, and Administration Guide
	BMC Impact manager Knowledge Base Reference Guide
	BMC Service Model Development, Maintenance, and Administration Guide
	BMC Configuration Management Database Configuration Guide
	BMC Service Impact Monitoring and Management Guide
	BMC Impact Explorer User Guide
	BMC Impact Integration for PATROL User Guide
	BMC Event Management Administrator Guide
	BMC Impact Event Adapters Installation and Configuration Guide
	BMC Impact Integration Web Services Installation and Configuration Manual
	BMC Impact Integration Web Services Server Installation and Configuration Guide

Where to view the latest product information

The latest BMC Performance Manager Portal, BMC Impact Portal, and BMC Performance Exception Detector information is available on the BMC Software Customer Support web page at http://www.bmc.com/support_home.

---

TIP:

If you do not already have a user name and password that allow you to fully access the BMC Software Customer Support web page, you can register for a user name and password on the page.

---

From the BMC Software Customer Support web page, you can perform several tasks, including

viewing the latest product documentation (manuals, release notes, flashes, technical bulletins, online Help, and parameter information)

subscribing to Proactive Notification to receive e-mail messages that inform you of new release notes, flashes, and technical bulletins for your products

searching for existing product resolutions and frequently asked questions (FAQs)

How to order the products

The BMC Impact Portal is available on CD and DVD. The BMC Performance Manager Portal and BMC Performance Exception Detector are available on CD and DVD or electronically from one of the BMC Software product download web pages (The BMC Portal server is included in these products). You can obtain the products in the following ways:

Order BMC Performance Manager Portal, BMC Impact Portal, or BMC Performance Exception Detector through a BMC Software sales representative by calling 800 793 4262.

If you have purchased a license for BMC Performance Manager Portal or BMC Performance Exception Detector through a BMC Software sales representative and need to download the product, or if you want to upgrade to the latest version of the product, download it from http://www.bmc.com/ega. Use the user name and password that your BMC Software sales representative gave you.

Customer support

If you have problems with or questions about a BMC product, see the Customer Support website at http://www.bmc.com/support_home. You can view or download product documents, find answers to frequently asked questions, and download product updates and maintenance. If you do not have access to the web and you are in the United States or Canada, contact Customer Support at 800 537 1813. Outside the United States or Canada, contact your local BMC office or agent.

*67949*