WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Operating system registry keys

Use the installation procedures to register WebSphere® ESB and associated products with the native operating system registry. This topic describes possible registry key values.

Installations are registered with the native operating system registries, such as the Red Hat Package Manager (RPM) on Linux® systems.
Note: It is not possible to register with the native operating system registries when performing a non-root installation.
The InstallShield MultiPlatform (ISMP) installation wizard also creates the .nifregistry and vpd.properties files that contain a list of product codes that ISMP uses to track installations that it has performed.
For i5/OS operating system The licensed program product codes for i5/OS® are: If you install any of the other WebSphere ESB options, you will see 5724L01 WebSphere Process Server V6.2.
See Limitations of non-root installers for more information about registry entries.
For i5/OS operating system Note: Non-root installation is not available on i5/OS platforms.
Table 1. Keys used to register WebSphere Process Server and WebSphere Enterprise Service Bus
Registry file location WebSphere Process Server WebSphere Enterprise Service Bus
vpd.properties WSEAA62 WSEAA62
AIX® WSEAA62 WSEAA62
HP-UX WSEAA62 WSEAA62
i5/OS WSEAA62 WSEAA62
Linux WSEAA62 WSEAA62
Solaris WSEAA62 WSEAA62
Windows® HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Process Server\6.2 HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Enterprise Service Bus\6.2

In addition to the vpd.properties file, the installation programs also create a record of installed products in an installation registry file and creates a catalog signature file for use by IBM® Tivoli® License Compliance Manager.

The installation registry file

The version 6.2 installation registry file is an XML file that contains data entries for all of the installed products that are listed in the preceding table:

The catalog signature files

Packages installed by a non-root installer might not register using native operating system mechanisms.

For AIX operating system For example, a WebSphere ESB version 6.2 product installed as a non-root user on an AIX version 5.3 operating system cannot register to the AIX lpp command. Thus, running the ls lpp command does not list the current WebSphere ESB version that is installed.

You can use the IBM Tivoli License Compliance Manager to manage the WebSphere ESB license and version.

To enable the IBM Tivoli License Compliance Manager to detect and monitor WebSphere ESB software components, obtain the ITLMReadinessOfferings.xml catalog file. This file is also referred to in IBM Tivoli License Compliance Manager as the IBMUseOnlySoftwareCatalog_****-**-**.xml or IBMSoftwareCatalog_****-**-**.xml file. The IBMUseOnlySoftwareCatalog_****-**-**.xml file is used with the Sub-Capacity version. The IBMSoftwareCatalog_****-**-**.xml file is used for the Full version.

The catalog file lists software signature recognition and usage files in XML format that are used by the IBM Tivoli License Compliance Manager components to identify and monitor software found on the agents. You can obtain the catalog file from IBM Tivoli License Compliance Manager.

Example package entries

For Linux operating system Issue the following command on a Linux system to show packages for WebSphere ESB:
rpm -qa | grep WS

topic Topic topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/rins_registry.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).