With IBM Business Process Manager (BPM), Installation Manager detects an imported package that is not synchronized

Technote (troubleshooting)


Problem(Abstract)

Applying WebSphere Application Server fixes using IBM WebSphere Update Installer (UPDI) requires that you import for IBM Installation Manager synchronization prior to applying fixes to IBM Business Process Manager.

Symptom

You will encounter an error when you attempt to apply maintenance fix packs or install other products. The following error messages are displayed when you run the IBMIM command:
Installation Manager detected an imported package that is not synchronized.
Installation Manager cannot manage the package until it is synchronized.


Cause

An Installation Manager import step was skipped after maintenance was applied with Update Installer.

Resolving the problem

To resolve the problem, locate and install the fixes using the Update feature of IBM Installation Manager, or download interim fixes from the Fix Central support site for IBM Business Process Manager. These fix packs also include Recommended fixes for WebSphere Application Server and are installed using IBM Installation Manager as the preferred method.

You can install WebSphere Application Server V7 fix packs using the Update Installer but careful planning is required as the process might cause conflicts in the future. Refer to the "Using the Update Installer utility (UPDI) to apply interim fixes and updates can cause inconsistencies with IBM Installation Manager" document. Installation Manager can import information about some WebSphere offerings that were installed or updated with tools other than Installation Manager. Importing these offerings adds their information to the list of installed packages and enables Installation Manager to install additional packages to the package group. However, Installation Manager has limited abilities to modify, update, roll back, and uninstall imported installation packages.

WebSphere Application Server V7.0.0 fix pack versions are available in Installation Manager repository packaging.

When a WebSphere Application Server fix is needed, but not yet available for Installation Manager install, you can request one from IBM Support. In the event that you choose to install a WebSphere Application Server fix with Update Installer, use the following process:

  1. Use the Recommended fixes for WebSphere Application Server site to upgrade WebSphere Application Server and the Java™ Software Development Kit (SDK) for WebSphere Application Server to the latest version or interim fix from Fix Central using the Update Installer for WebSphere Software. Follow the procedures shown in the fix pack release notes provided with the fix. WebSphere Process Server install and update process requires the SDK and the WebSphere fix pack versions to be at the same level.

  2. Install the latest version of IBM Installation Manager.

  3. Import the new version of WebSphere Application Server to IBM Installation Manager to synchronize the repositories with the upgrade. This approach maintains the consistency of the IBM Installation Manager-based WebSphere Process Server installation. Failing to import the new version renders the IBM Installation Manager repositories out-of-sync, and future update operations to WebSphere Process Server might fail. The steps for importing are provided below.

Importing WebSphere Application Server to Installation Manager registry

These steps synchronize the WebSphere Application Server fix pack with the IBM Installation Manager registry. The first section shows you how to use the graphical interface. The second section shows how to import using silent mode. This procedure is explained in detail in the Installation Manager Information Center.

Repository location: If the installed system has access to the Internet, check to see whether the following repository location is configured in your Installation Manager properties.
<repository location="http://public.dhe.ibm.com/software/websphere/repositories/" />
If the system is isolated from Internet access, download Installation Manager repositories for fix packs, transfer the was.7.0.import.zip file, and extract it to the /tmp/was.7.0.import directory. Set <repository location="/tmp/was.7.0.import" />

  1. Run IBMIM
    Installation Manager detects that WebSphere Application Server has been upgraded and prompts you to synchronize its repositories.



  2. Click No.

  3. Open the File > Preferences > Repositories page and set the location to
    http://public.dhe.ibm.com/software/websphere/repositories/
    or /tmp/was.7.0.import

  4. Click Import, or restart IBM Installation Manager, so that the repository synchronization is displayed again and click Yes.



Silently Importing WebSphere Application Server using Installation Manager
  1. Create a response file.
    Use a copy of the response file with which you installed and add the
    <repository location='/tmp/was.7.0.import'/> entry. Alternatively, you can create a new response file by downloading the Sample_AppServer_import.xml.


  2. Edit the copy of the response file and change the following sections:


    Repository location
    <repository location="http://public.dhe.ibm.com/software/websphere/repositories/" />
    or
    <repository location='/tmp/was.7.0.import'/>


    Import profile
    <import profile='IBM WebSphere Application Server - ND_20100406_1142' type='WAS'/>


    Find the id for your current installation. You can retrieve this value from the installed.xml file in the agent data location directory. The default agent data locations are:
    UNIX-based operating systems: /var/ibm/InstallationManager
    Windows operating systems: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager.
    example:
    grep "location id=" ~/var/ibm/InstallationManager/installed.xml | awk -F"'" '{print $2}'
    returns id
    IBM WebSphere Application Server - ND_20100406_1142


    Cache
    <preference value='/u01/wps/IBM/BPMShared' name='com.ibm.cic.common.core.preferences.eclipseCache'/>

    You can find the cache value in the com.ibm.cic.agent.core.prefs file. Example:
    grep Cache ./var/ibm/InstallationManager/.settings/com.ibm.cic.agent.core.prefs
    com.ibm.cic.common.core.preferences.eclipseCache='/u01/wps/IBM/BPMShared'

  3. Run the IBM Installation Manager command silently to import the WebSphere Application Server upgrade.
    example:

    tools/imcl -acceptLicense -s -sVP -input import.xml -log /tmp/imlog

  4. Check the results in the log file.
    The installation log file does not contain any error messages when the import is successful. You can find detailed log files in the <IBM IM agent database location>/logs directory.

    Example log file content on success:
    <?xml version="1.0" encoding="UTF-8"?>
    <result>
    </result>


    Example import.xml file
    <?xml version="1.0" encoding="UTF-8"?>
    <agent-input>
    <server>
    <repository location='/tmp/was.7.0.import'/>
    </server>
    <import profile='IBM WebSphere Application Server - ND_20100406_1142' type='WAS'/>
    <preference value='/u01/wps/IBM/BPMShared' name='com.ibm.cic.common.core.preferences.eclipseCache'/>
    <preference value='30' name='com.ibm.cic.common.core.preferences.connectTimeout'/>
    <preference value='30' name='com.ibm.cic.common.core.preferences.readTimeout'/>
    <preference value='0' name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount'/>
    <preference value='false' name='offering.service.repositories.areUsed'/>
    <preference value='false' name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode'/>
    <preference value='false' name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication'/>
    <preference value='NTLM' name='http.ntlm.auth.kind'/>
    <preference value='true' name='http.ntlm.auth.enableIntegrated.win32'/>
    <preference value='true' name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'/>
    <preference value='false' name='PassportAdvantageIsEnabled'/>
    <preference value='false' name='com.ibm.cic.common.core.preferences.searchForUpdates'/>
    </agent-input>



Common Errors:
  • CRIMAA7FD095E ERROR: Existing Eclipse at /u01/wps/7 could not be initialized. Check installation logs for more information.
    Cause: The eclipseLocation value was set to the wrong directory.
    Correction: Set to users' instance of Installation Manager ~/IBM/InstallationManager/eclipse

  • CRIMD9B31CD83E ERROR: The Software Development Kit version is not the same as the IBM WebSphere Application Server - ND version.
    Use another tool, such as the Update Installer for WebSphere Software, to synchronize the versions.
    Cause: The Software Development Kit (SDK) and WebSphere Application Server fix packs are not at the the same version.
    Check using the versionInfo.sh command. Example: bin/versionInfo.sh -maintenancePackages | grep -e "Software Developer Kit 7.0.0.21" -e "WebSphere Application Server 7.0.0.21 FixPack"
    Correction: Install fix packs.

  • CRIMAD5C4712E ERROR: There is already a package installed at "/u01/wps/7". The installation directory must not be the same as a previously used installation directory.
    Cause: The installation location is set.
    Correction: Comment or remove the 'profile installLocation' section:
    <profile installLocation='/u01/wps/7' id='IBM WebSphere Application Server - ND_20100406_1142'>
    <data key='eclipseLocation' value='/u01/wps/IBM/InstallationManager/eclipse'/>

Cross reference information
Segment Product Component Platform Version Edition
Business Integration IBM Business Process Manager Standard Installation / Configuration AIX, Linux, Linux zSeries, Solaris, Windows 7.5.1, 7.5
Business Integration IBM Business Process Manager Express Installation / Configuration Linux, Linux zSeries, Windows 7.5.1, 7.5

Product Alias/Synonym

BPM

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Business Process Manager Advanced
Installation / Configuration

Software version:

7.5, 7.5.1

Operating system(s):

AIX, Linux, Linux zSeries, Solaris, Windows, z/OS

Reference #:

1618167

Modified date:

2013-02-04

Translate my page

Machine Translation

Content navigation