Troubleshooting

The following procedures describe how to troubleshoot problems with WebSphere Partner Gateway installations.

This chapter contains the following sections:

Locating Database Loader errors

If you encountered problems while installing the Database Loader, consult the Database Loader logs in the system temp/bcgdbloader/logs directory for information on the problem. Once the problem is resolved, do the following to delete the created database:

  1. Run the Database Loader uninstaller and remove the database.
  2. Once you have deleted the database, rerun the Database Loader wizard.

If you experience problems installing the WebSphere Partner Gateway components, review the following component installation logs:

{INSTALL DIR}/logs/bcgconsole

{INSTALL DIR}/logs/bcgreceiver

{INSTALL DIR}/logs/bcgdocmgr

You should also examine the following runtime logs:

Embedded WebSphere Application Server

{INSTALL DIR}was/profiles/bcgconsole/logs

{INSTALL DIR}was/profiles/bcgreceiver/logs

{INSTALL DIR}was/profiles/bcgdocmgr/logs

WebSphere Application Server v6.0

{INSTALL DIR}profiles/bcgconsole/logs

{INSTALL DIR}profiles/bcgreceiver/logs

{INSTALL DIR}profiles/bcgdocmgr/logs

Recovering from incorrect version detection problems

The InstallShield wizard stores product data in a file named vpd.properties. Equivalent information is also stored in the operating system software registry, if applicable. For example, RPM on Linux, lslpp on AIX and pkginfo on Solaris.

The information includes a unique ID key (UID), version.release information and the installed directory for each product and component. These three pieces of information form a unique logical key for each entry.

The information stored in vpd.properties file, operating system software registry, or both is used to resolve already installed conditions, etc. Occassionally the information in vpd.properties file, the native operating system software registry, or both becomes inaccurate and does not represent the state of the system. This can occur when two or more install or uninstall wizards run concurrently. There are numerous other scenarios that can also corrupt this information.

The location of the vpd.properties file varies per operating platform:

The following information will guide you through the process of manually removing data for products or components that are no longer installed. The process is the same for each operating system:

  1. Make a backup copy of vpd.properties before proceeding. All products that use InstallShield MultiPlatform or InstallShield Universal Install wizards update vpd.properties. Corrupting the contents of vpd.properties could cause future upgrades, maintenance installs or uninstalls to fail.
  2. Open vpd.properties using an editor of your choice. If possible, turn line wrap off or use an editor that does not wrap the lines.
  3. Each line in vpd.properties represents a product or product component. The first entry in the line is the unique ID (UID). Each field in the line ("record") is separated by a vertical bar (|). Approximately the next 4 fields are the version, release, modification and update fields. Visually scan across the line to locate the install location path.
  4. Using the information described in step 3 above, manually identify all the entries which point to products/components that are no longer installed.
  5. Save and close the vpd.properties file.

AIX

  1. Clean up vpd.properties as described above.
  2. Search for entries that are no longer installed using smit or lslpp. For example, from the command line use the following command to find all entries for WebSphere Business Integration Connect v4.2.2 and older. Note the names that are returned:
    lslpp -l | grep -i wbic
  3. Delete each package name returned from step 2 using the geninstall -u command.
  4. If the geninstall -u command does not work, consult with your AIX support for instructions on manually cleaning the object data manager (odm).

Linux

  1. Cleanup vpd.properties as described above.
  2. Search rpm for entries that are no longer installed, using the tool of your choice. For example, use the following command from the command line to find all the entries for WebSphere Business Integration Connect v4.2.2 and older. Note the package names returned:
    rpm -qa |grep -i wbic
  3. Delete each package name returned from step 2 delete them from rpm using the tool of your choice. For example, from the command line use rpm -e
  4. If the list contains packages that you intend to delete and no others, remove all of the packages with the following command:
    rpm -qa | grep -i wbic | xargs rpm -e

Solaris

  1. Cleanup vpd.properties as described above.
  2. Search for entries that are no longer installed using pkginfo. For example, from the command line use the following command to find all entries for WebSphere Business Integration Connect v4.2.2 and older. Note the names that are returned:
    pkginfo | grep -i wbic
  3. Delete each package name returned from step 2 using the geninstall -u command.
    1. Change directory to where the package information is registered
      cd /var/sadm/pkg
    2. Execute the pkgrm -n command on each package name to be removed. For example:
      ls |grep -i wbic | xargs -i pkgrm -n {}
    3. If there is a problem running the pkgrm -n command, try removing the related package directories and then rerun the pkgrm -n command. For example:
      - rm -rf /var/sadm/pkg/WBICpackageName1/

Windows

  1. Cleanup vpd.properties as described above.
  2. As a precaution, backup the Windows Registry using the regback.exe program from the Windows Resource Kit.
  3. Use regedit.exe to search for and remove keys for versions which are no longer installed under these keys:
    1. HKEY_LOCAL_MACHINE\Software\IBM
    2. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\
      CurrentVersion\Uninstall\

Copyright IBM Corp. 2003, 2005