Hints and tips for diagnosing problems in WebSphere® Appliance Management Center.
| Problem | Explanation |
|---|---|
|
This message is produced if you try to run the installer on a 32-bit Windows system. WebSphere Appliance Management Center supports 64-bit operating systems only. |
Error code: CWZBA1502E |
A browser bug means that large files are not uploaded successfully. Use a different browser to upload the image (for example, Internet Explorer or a newer version of Mozilla Firefox) or use the option to upload from a remote location URL. |
The messages.log file contains entries of the following form:
|
This error occurs when a browser caches an LTPA security token from a different instance of the server and is attempting to pass on requests to this server. This error can occur if, for example, WebSphere Appliance Management Center is reinstalled. The error is benign. A new LTPA security token is provided to the browser. |
|
On Linux, when you provide an installation path that contains a space, the installer attempts to create the link in a parallel path where the space is replaced by an underscore (_). For example, installing in /opt/ibm/w amc results in an attempt to create the link in /opt/ibm/w_amc/bin. If the installer is unable to create this path, you can find the program in the installation_directory/jre/jre/bin directory. |
You could not deploy configuration by using deployment policy from default domain with WebSphere Appliance Management Center. Attempting to deploy configuration to a domain by using a deployment
policy from the default domain on the same or another appliance results
in the following error:
|
Before version 5.0 firmware, the implementation of the Appliance Management Protocol on the appliance, by design, exports only the objects from the default domain that are not referenced by a service. Therefore, any deployment policies on the default domain cannot be exported. You can export the deployment policy by using the appliance WebGUI and then set the deployment policy as the deployment policy for the target domain by using WebSphere Appliance Management Center. Alternatively, create the deployment policy in a domain other than the default domain. This problem is resolved in the version 5.0 firmware. |
You receive the following message in the WebSphere Appliance Management Center installer: cannot execute binary file. The WebSphere Appliance Management Center installation program exits with an error because the wrong installer for the operating system was chosen or an unsupported operating system is being used. The installer exits with an error similar to the following message:
|
This error indicates that the Java™ binary is not of the correct format for
the operating system. The cause is likely to be one of the following
reasons:
Check that the system on which you are installing uses a 64-bit word length. 32-bit systems are not supported. Check
the name of the downloaded installation archive. The following list
shows which archives are intended for which operating system:
Note: The release date, for example, 2012-06-26, in the middle of the file name, changes for each release.
|
You receive the following message when you attempt to upgrade the
firmware on an appliance:
|
You can receive the message in the following scenarios:
|
| You receive the following message when you try to deploy an exported
domain configuration to a newly created managed domain.
|
When you are deploying a domain configuration export, the Appliance Management Protocol implementation on the appliance attempts to switch to the named domain before it completes the import, which results in the error. This issue is resolved in version 4.0.1 of the firmware and later. For earlier versions of the firmware, you can use a backup of the appliance configuration that contains the required application domain, rather than an export of the domain configuration. In the appliance WebGUI, this action corresponds to selecting Create a backup of one or more application domains, rather than selecting Export configuration and files from the current domain. |
Valid firmware downgrade options are not shown in WebSphere Appliance Management Center. You can use WebSphere Appliance Management Center to manage IBM WebSphere DataPower appliance firmware. Typically you can use this action to update firmware on managed appliances, but you can also use the feature to downgrade to older firmware versions. In some cases, valid firmware downgrade options are not displayed in WebSphere Appliance Management Center. |
WebSphere Appliance Management Center determines that a IBM WebSphere DataPower firmware image is suitable for deployment to a IBM WebSphere DataPower appliance only if the appliance model and type match the firmware and the firmware image provides all of the features that are currently enabled on the appliance. Over time, new appliance features are added to the IBM WebSphere DataPower firmware images. After you upgrade an appliance to a firmware level that includes a new feature, WebSphere Appliance Management Center does not consider that older firmware images without this feature are valid for deployment to the appliance. For example, firmware version 5.0.0.3 introduced an IPv6 feature. After an appliance is upgraded to version 5.0.0.3, WebSphere Appliance Management Center considers that only those firmware images that provide the IPv6 feature are valid for the appliance. This situation means that firmware images before version 5.0.0.3 cannot be deployed to the appliance by using WebSphere Appliance Management Center. If you want to downgrade an appliance to an older firmware version and that firmware version does not support all of the appliance features that are provided by the currently deployed version, you must downgrade the firmware by using the IBM WebSphere DataPower appliance WebGUI or CLI. If you use the WebGUI, you are warned that the firmware that you are deploying does not contain support for all of the currently deployed features but you can choose to continue anyway. |
Following the expiry of IBM WebSphere DataPower certificates that are used by default to secure the WebGUI and XML manager on 9235 appliances that are running firmware levels before version 5.0.0.0, what do I have to do to configure WebSphere Appliance Management Center to manage these appliances? |
The default certificates that are used to secure access to the WebGUI and the XML manager on 9235 appliances that are running firmware levels before version 5.0.0.0 expired in June 2013. The problem is described in detail in this Technote: DataPower default WebGUI certificate is expiring or expired; an internal DataPower CA certificate is expiring or expired (www-01.ibm.com/support/docview.wss?uid=swg21633306). Upgrade to the June 2013 release, or later, of WebSphere Appliance Management Center. This release allows expired certificates to be accepted by WebSphere Appliance Management Center. You can use your appliance in the same way as any other appliance and no further changes are required. |