Release notes for IBM PureApplication System W1500 and W1700 Version 1.1.0.3

Release notes


Abstract

This release notes document contains information about known issues in this release.

Content

The following issues are known in this release.

Administering the system

Command-line tool

Backup and restore

Managing virtual systems and virtual applications

IBM Image Construction and Composition Tool

Database performance monitoring

Advanced Middleware Configuration


Administering the system



Chargeback report problems
Problem You might experience the following problems when using chargeback reports:
  • Filtering the report results by metric does not work. Regardless the metric you select (CPU, Hypervisor, Memory, Network, Products, or Storage), the same report, containing all data, is generated.
  • Some values in the report, such as 'record_time', display incorrect values.
Resolution These are known limitations.

Cannot log in to the workload console if the user name has a colon character
Problem You cannot log in to the workload console if your user name has a colon character in it.
This problem might happen when logging in for the first time if the user has access to the workload console but not the system console, or when switching from the system console to the workload console.
Resolution No workaround currently exists. To avoid this problem, do not use the colon character in user names.


Cannot log in to the System Monitoring Portal from client systems with Oracle 32-bit JDK 7u45 and 7u51
Problem You cannot log in to the System Monitoring Portal from a client system running Oracle Java™ SE Development Kit 7, Update 45 (JDK 7u45) and Update 51 (JDK 7u51).
This problem occurs as a result of increased security requirements set in that JDK.
Resolution No workaround currently exists. To avoid this problem, do not download or upgrade to Oracle JDK 7u45 or 7u51 on client systems where the System Monitoring Portal is used.

CWZIP4643W, CWZIP4682E, and CWZIP4683E error messages during users/groups import
Problem When importing users and groups using an LDIF file exported from an Oracle LDAP server, the following errors might occur:

CWZIP4643W The LDAP service cannot authenticate a user. An exception occurred: java.lang.Exception : CWZIP4682E User name <user_name> does not match the value <user_name> from the LDAP server.   

CWZIP4643W The LDAP service cannot authenticate a user. An exception occurred: java.lang.Exception : CWZIP4683E Group name <group_name> does not match the value <group_name> from the LDAP server. 
Resolution The problem is caused by trailing space characters in the user name and group name fields in the LDIF file. Delete the trailing space characters and import the users and groups again.

Removed network switches appear available in the infrastructure map
Problem When a network switch is removed from the system, an event is generated to report that the device is removed.
However, in the infrastructure map tree view, the state of the network switch remains as Available.
Resolution Wait for about an hour and the state of the switch will be displayed correctly as Unknown on the user interface.

Cannot revert back to DB2 with BLU Acceleration Pattern type version 1.1.0.7 after upgrading to version 1.1.0.8 or 1.1.0.9
Problem If you have deployed the Web Application Pattern type 1.0 or 2.0 after upgrading to the DB2 with BLU Acceleration Pattern type version 1.1.0.8 or 1.1.0.9 from version 1.1.0.7, you cannot revert back to the DB2 with BLU Acceleration Pattern type version 1.1.0.7.
Resolution This is a known limitation.

Null pointer exception when updating the DB2 and Advanced Middleware Configuration patterns
Problem Failures occur when you update the following virtual system patterns:
  • Advanced Middleware Configuration Version 1.1.0.0 to Version 1.1.0.1
  • DB2 Enterprise Server Edition Version 10.1.0.2 to Version 10.1.0.3
  • DB2 Advanced Workgroup Standard Edition Version 10.5.0.0 to Version 10.5.0.2

Options for selecting the new images are provided in the console. When you select the options, however, a null pointer exception occurs and the following message is displayed in the console:

At least one part in the pattern is not defined by the selected virtual image.
Resolution For Advanced Middleware Configuration Version, no fix is currently available.

For DB2 Enterprise Server Edition and DB2 Advanced Workgroup Standard Edition patterns, a script is available on Fix Central.

You can access the script by downloading APAR IT00136. Before you try to update the virtual system patterns again, use the following steps to download and apply the script:

1. Download the APAR from Fix Central. To access the specific fix download page, enter IT00136 in the APAR or SPR field.
2. Run the CleanUpDB2ConceptualPart.py script using the command-line interface as follows:

pure -h hostname -u username -p password -f path_to_CleanupDB2ConceptualPart.py

Note: For patterns created with the DB2 parts before this fix, you will encounter problems updating the part versions even after you run the script. In these cases, replace the part in the pattern being edited with the new part.

Only the Log Analysis node is displayed with the external System Monitoring service
Problem When using the external System Monitoring service, only the Log Analysis node is displayed under the Monitoring Agent for WebSphere Applications in the PureApplication System Monitoring Portal.
Resolution Manually install the application support for Monitoring Agent for IBM WebSphere Application Server Version 7.2.0.0.3 in the external IBM Tivoli Monitoring environment. You can download the 7.2.0.0.3 fix from the ITCAM Agent for WebSphere Applications V7.2 fixes site.

For more information about manual installation, go to the IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.2 information center and follow the instructions.

Views for System Monitoring for WebSphere Application Server connected to external Tivoli environment display no data
Problem Views for System Monitoring for WebSphere Application Server connected to an IBM Tivoli Monitoring environment through the external-mode System Monitoring shared service fail to display data, resulting in SQL errors in the Tivoli Enterprise Portal (TEP). This condition is the result of historical data collection sets not being enabled for System Monitoring for WebSphere Application Server on the external ITM server.
Resolution To use System Monitoring for WebSphere Application Server and avoid the SQL errors in the TEP, you must enable historical data collection sets on the external ITM server. Enable the following attribute groups on the external ITM server:
o Client Communications
o Container Object Pools
o Container Transactions
o DB Connection Pools
o Dynamic Cache
o EJB Containers
o High Availability Manager
o Messaging Engine Communications
o Messaging Engines
o Portlet Summary
o Web Services
o WMQ Client Link Communications
o WMQ Link Communications

For more information about the collection sets and attribute groups, see Historical data collection for the WebSphere Applications agent.

CPU and memory limits for server type licenses are not enforced
Problem CPU and memory limits that you specify when adding server type licenses to virtual images are not enforced. If you exceed the limits, no warning messages are generated.

Note that the total number of server licenses allowed for use is still enforced.
Resolution This is a known limitation.

Monitoring agent for IBM HTTP Server virtual machine does not collect metrics
Problem The monitoring agent for IBM HTTP Server (IHS) does not collect metrics when IHS is installed as part of a WebSphere Application Server virtual system machine.
Resolution Deploy the System Monitoring for IHS shared service before deploying a virtual system that uses the monitoring agent to collect metrics data.

Optionally, you can add an IHS part that is separate from the WebSphere Application Server part in the virtual system pattern. In this scenario, the monitoring agent on the IHS virtual machine functions with no problems even when the pattern is already deployed.

Problems occur when applying WebSphere Application Server interim fix to an upgraded virtual system instance
Problem When applying a WebSphere Application Server interim fix to an upgraded virtual system instance, the service history might show the following failed status:
Unable to apply service on virtual machine.
Resolution Follow the procedures for downloading and installing interim fixes in the WebSphere Application Server product documentation. Interim fixes for your version of WebSphere Application Server are available for download on IBM Fix Central at http://www.ibm.com/support/fixcentral/. For installation procedures, see the WebSphere Application Server Information Center for your product version, for example:
· WebSphere Application Server Version 8.5 Information Center
· WebSphere Application Server Version 8.0 Information Center
· WebSphere Application Server Version 7.0 Information Center

PureSystems Manager seems to reboot after being powered off
Problem When using the command-line tool or physical power button on the hardware to power down the active PureSystems Manager, the PureSystems Manager turns back on after a brief delay of five to 30 minutes. The active PureSystems Manager powers down but is automatically restarted by the other PureSystems Manager.

Due to the power-off action on the active PureSystems Manager, a failover occurs and processes are started on the non-active PureSystems Manager. When one PureSystems Manager starts when the other one is powered down, the first PureSystems Manager automatically starts the second one.

When powering down the non-active PureSystems Manager, it does not reboot because a failover does not occur.
Resolution Power down the PureSystems Manager in the system console. Click Hardware > Management Nodes, select the desired PureSystem Manager, and click Power Off.

Powering down a PureSystem Manager from the system console does not cause it to reboot, regardless of whether it is the active or non-active node.

The 'Physical cores' view of a compute node incorrectly shows 32 cores per CPU
Problem For PureApplication System W1700 systems, the Physical cores view for compute nodes incorrectly shows 32 cores per CPU. However, the correct value is eight cores per CPU.

To see the physical cores for a compute node, perform the following steps:

1. Open the system console.
2. Click Hardware > Compute Nodes.
3. Select a compute node in the left navigation pane.
4. In the main window, expand the Physical cores section.
Resolution The incorrect value of 32 does not affect your deployments. The value only displays incorrectly in the user interface and in the REST API informational messages that describe the physical characteristics of CPU modules.

Command-line tool



Cannot export virtual system patterns using the downloadAll option with the command line interface
Problem When using the command line interface to export a virtual system pattern, if you use the downloadAll option to export the pattern's associated artifacts such as virtual images, script packages, and add-ons, the export might not complete successfully.
Resolution Export the virtual system pattern without using the downloadAll option in your export command, and then export the pattern images separately.

For more information, see the Exporting virtual system patterns and Exporting virtual imagestopics in the Information Center.


Extra default configure NIC add-ons are imported into a pattern after running the importPatterns.py script
Problem After creating a virtual system pattern from an image with multiple network interface controller (NIC) cards and then exporting the pattern from PureApplication System by using the exportPattern.py script, the parts section of the patterns.json file might contain extra entries in the add_ons sections for the corresponding parts, for example:

"add_ons": [
               {
                  "add_on_ref": 0,
                  "parameters": [
                  ]
               }
             ]

Then, if you import this same virtual system pattern into PureApplication System with the importPatterns.py script, the pattern contains extra default configure NIC add-ons.
Resolution Remove the extra add-on entries from the patterns.json file and run the importPatterns.py script again. The patterns.json file is located in the directory or TGZ file that you specified when exporting the virtual system pattern.

Backup and restore



Existing private key file for backup data encryption can be overwritten
Problem PureApplication System allows you to upload a new private key file for backup data encryption, even when your backup host already contains a private key file. Uploading a new key file overwrites the existing key file.

Perform the following steps to check whether a key file already exists:

1. Perform the following steps to locate the path to the private key file:
    A. Click System > Settings.
    B. Expand the System Backup and Restore section.
    C. Under the Backup section, click the Step 1: Configure certificate and private key storage link.
    D. In the Path field, copy the path to the key file.  
2. Navigate to the following directory on the key host server:

<Path to key file from previous step>/<rack_model>/backupSecurity

3. Run the following command: "ls -a". If a key file already exists, the following files are listed:

backupCertificate
backupPrivateKey
.cmodulus
.kmodulus
.oldkeyflag
Resolution Do not upload a new private key file when the backup host already contains a private key file, even though the user interface allows the upload action. A full backup and all subsequent delta backup data must be encrypted by the same key file.

If you do overwrite the existing key file, you can retrieve it from the following folder:

<path to key file>/<rack_model>/backupSecurity/restorePrivateKeys


Backup of emergency fixes fails for an invalid or incomplete emergency fix
Problem If the backup operation is configured to include emergency fixes, and there is an invalid or incomplete emergency fix on the system, the backup operation fails. The following error message is displayed:

CWZIP9569E One or more efix artifacts failed to backup or restore.
Resolution Before the backup operation, ensure that all emergency fixes to be backed up are valid and complete. A valid, complete emergency fix must contain the following artifacts:
  • A script that installs the fix.
  • A service.xml file that specifies information about the emergency fix and deployment requirements.

For more information, see the Packaging emergency fixes topic in the PureApplication System information center.

Key-based authentication in backup and restore settings supports a maximum key size of 2048 bits
Problem The private key used for key-based authentication (instead of password authentication) when communicating with the key host system and the backup system can have a maximum length of 2048 bits.

If you use a longer private key during a backup operation, the export of images fails, resulting in the following error messages in the log file for the IaaS Backup job:

There was an internal database error - see the trace file for details.

CWZIP1900E An internal error com.ibm.iaas.backup.util.BackupRestoreException: CWZIP9569E One or more virtualimage artifacts failed to backup or restore. Examine log for more details.  Failure: View log for more details occurred. For details, see the log/trace files.

The following messages can be found in the workload console logs:

Caused by: com.ibm.pdq.runtime.exception.DataRuntimeException: [pdq][10104][2.7.116] An error prevented the update operation from completing successfully.; Caused by: com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.14.113
Resolution This is a known limitation.

Error 'Cannot update script package - it is read-only' when restoring read-only artifacts
Problem The following artifacts have read-only attributes:
  • Add-ons
  • Script packages
  • Virtual System pattern definitions

If these artifacts are configured as read-only at the time of restore, they cannot be restored unless they are first deleted from the system you are trying to restore to.

These artifacts can be deleted only if they are not being used by patterns (for add-ons and script packages) or by deployed virtual machines (for virtual system pattern definitions).

If you attempt to restore these read-only artifacts without first deleting them, you get the following error:
Cannot update script package - it is read-only.
Resolution This is a known limitation.


Managing virtual systems and virtual applications



Virtual system patterns fail with count error during import
Problem When importing virtual system patterns that were exported from previous versions of PureApplication System, if these patterns require the IBM OS Image for Red Hat Linux System base image, the import action might fail with a count error that looks similar to the following example:

Importing pattern "Pattern_name" ...
Traceback (most recent call last):
File "/file_path/patternloader.py", line 795, in JSONtoPattern
ppart.count = part[COUNT]
File "/file_path//ppart.py", line 79, in _setCount
raise AttributeError('count')
AttributeError: count
Resolution To resolve the issue, perform the following steps:
1. Delete the IBM OS Image for Red Hat Linux Systems 2.0.0.4 image from the image catalog.
2. Import the IBM OS Image for Red Hat Linux Systems 2.0.0.3 into the image catalog.
3. Import your virtual system patterns from previous versions of PureApplication System.
4. Import the IBM OS Image for Red Hat Linux Systems 2.0.0.4 image into the image catalog.

For more information, see Importing virtual images.

Degraded performance in virtual application patterns when vertical scaling increases the Java heap size to a value beyond the available large page memory
Problem When the heap size for the WebSphere Application Server JVM in a virtual application pattern is increased by vertical scaling, large pages are not used if the available large page memory is not large enough to support the increased heap size.
This situation might degrade the performance of the virtual application.
Resolution This is a known limitation.

Emergency fix required before updating Database Performance Monitoring Pattern
Problem An emergency fix is required before updating Database Performance Monitoring Pattern V1.0.1.1 to V1.0.1.2.

If you attempt to update without the emergency fix, the update process might fail at the uninstallation step, with the following error in the 0config.log file:

Uninstalling failed in the node.
Resolution Perform the following steps to update the emergency fix:

1. Download the 124818.zip file from FixCentral. This file contains the emergency fix.
2. Add the emergency fix to the catalog by using the information in the Adding emergency fixes to the catalog topic in the PureApplication System information center.
3. Update all deployed patterns by using the information in the Updating deployed pattern types topic in the PureApplication System information center.

Manual scale-out operation fails with CWZMO1332E error if the incremental instance count exceeds the maximum number allowed
Problem A manual scale-out operation in a deployed running virtual application might fail with the following error message:

CWZMO1332E: The manual scale out operation failed. See the trace for more details.

This error occurs when the value of the incremental instance count that was configured for the manual scale-out operation of the middleware exceeds the maximum instance number that is allowed in the application scaling policy.

For example, when configuring the scale-out policy for instances of WebSphere Application Server in a virtual application, you might specify 10 as the maximum number of instances allowed in the scale-out operation. If you deploy the application with eight instances of WebSphere Application Server and then submit a manual scale-out operation with an instance count of '3', the operation fails with the CWZMO1332E error message.
Resolution Change the number of incremental instances that are allowed in the manual scale-out operation. Perform the following steps:

1. In a deployed virtual application, click Manage to open the Virtual Application Console.
2. In the Operations tab, select the middleware agent in the left navigation area.
3. In the main window, expand the Manual Scaling section.
4. In the Horizontal Scaling subsection, update the number of instances in the Incremental instance count field so that the total number of the incremental instance count plus the existing instance count for this role does not exceed the maximum instance count.
5. Click Submit.

High paging activity occurs when virtual machines deployed on PureApplication System W1700 have less than 4 GB of memory
Problem On PureApplication System W1700, when checking memory usage on a deployed virtual machine, you might notice high paging activity. This activity occurs when AIX virtual machines are configured with less than 4 GB of memory.
Resolution To avoid high paging activity, perform the following steps on a deployed AIX virtual machine:

1. Click Cloud > Virtual Machines in the system console.
2. Select the virtual machine, and click Configure.
3. In the Virtual Memory field, increase the memory to at least 4 GB.

HTTP connection errors occur for monitoring components on PureApplication System W1700
Problem HTTP connection errors might occur when monitoring components try to retrieve operating system-level metrics. These errors occur on PureApplication System W1700 in AIX virtual system deployments with large workloads that create high memory usage.
In these cases, vertical scaling does not occur on the virtual machines since the monitoring component does not have the metrics to determine when to trigger the scaling process.
Resolution To prevent HTTP connection failures and other errors, deploy the virtual machine with a memory of 4 GB or more. Perform the following steps:

1. Click Cloud > Virtual Machines in the system console.
2. Select the virtual machine, and click Configure.
3. In the Virtual Memory field, increase the memory to at least 4s GB.

Scaling up virtual systems from one virtual CPU to two virtual CPUs fails on PureApplication System W1500
Problem When autoscaling from one to two virtual CPUs, the virtual machine might hang with a 'STOPPED' status on the deployment details window.
For example, this condition can occur on PureApplication System W1500 after adding a generic CPU scaling script package to a virtual system pattern to autoscale virtual machines based on CPU metrics.
Resolution If you want to enable autoscaling for a virtual system, configure the virtual machine to start with two virtual CPUs as a minimum. Then, the virtual system can scale up from two virtual CPUs to the maximum number of CPUs without errors.

Alternately, you can stop an already deployed virtual machine with one virtual CPU in the system console, manually change it to two virtual CPUs, and then restart the virtual machine.

For more information about limitations with vertical scaling, see Vertical scaling support matrix (pattern type and platform).

Note: This issue does not occur in virtual application patterns, since the virtual machines start with two virtual CPUs by default when autoscaling is enabled.

Manual scale-up operation fails with CWZMO1376E error when the CPU count for a virtual machine instance for the same middleware role exceeds the maximum allowed in the scaling policy
Problem A manual scale-up operation on a middleware role in a virtual machine instance fails with the following error message:

CWZMO1376E: Manual scaling operation of resetting vCPU count failed due to vCPU count cannot be decreased, Current vCPU count has reached.

This error occurs when at least one of the virtual machines in the middleware role already contains a CPU count that is higher than the maximum CPU count that is allowed in the scaling policy. If even one role exceeds the maximum CPU count, then the entire scale-up operation fails for all middleware roles.

This error occurs for a manual scale-up operation in the Operations tab of the Virtual Application Console if a user has previously reset the CPU count for one of the virtual machines for this role in some other location, for example:
· In the Cloud > Virtual Machines > Configure window in the system console.
· In the Instances > Virtual Machines > Configure window in the workload console.

Note: In normal circumstances, this failure does not occur because all the virtual machines in the same middleware role follow a common virtual machine template and have the same number of virtual CPUs.
Resolution Avoid resetting the CPU count of any single virtual machine to a value that is different from the other virtual machines. The CPU count for a virtual machine should never be higher than the maximum CPU count that is allowed for the same role in the virtual application.

After deploying a DB2 10.5 database with BLU Acceleration and default advanced options, the database is not displayed
Problem A DB2 10.5 database with BLU Acceleration will not deploy if the default advanced options are selected because the default option for Collating sequence is incorrectly set to SYSTEM. The only collation sequence option that is supported for DB2 10.5 with BLU Acceleration is IDENTITY.
Resolution When you are initially deploying a database, go to Advanced options and set the Collating sequence field to IDENTITY.

Increasing Linux DB2 HADR database resources more than once causes the scale up operation to hang
Problem If you attempt to increase the resources for an HADR database more than once, the scale up pane of the workload console might hang.
Resolution In the workload console, click Instances > Databases, then select the database. Stop the database and wait until the details for the database indicates that it is in a stopped state, then restart the database.

Cannot view storage scale up information
Problem After increasing the storage for a an existing database, the History section of the specified database does not display any information about the scale up procedure.
Resolution From the workload console, select the database you are working with and click Manage. In the new tab, click Database > Virtual Instance. In Operation, click Execution Results. The information about the storage scale procedure up is displayed.

Brief throughput failures after applying an emergency fix to a virtual system with an ODR dynamic cluster and APC elasticity enabled
Problem If a deployed virtual system is using on demand router (ODR) dynamic cluster and application placement controller (APC) elasticity, and if an emergency fix is applied after the initial deployment, the elasticity addition to the ODR dynamic cluster might trigger throughput errors.
Resolution To apply required emergency fixes to extended images and avoid throughput errors, see Applying required fixes for virtual images in Version 3.1.0.2 and complete steps 1-6. http://www-01.ibm.com/support/docview.wss?uid=swg21598785

Increasing allocated CPU or memory resources might require stopping or rebooting the database or virtual machine
Problem When using IBM PureApplication System W1500, certain limitations exist when scaling the allocated memory or number of CPUs of a deployed virtual machine that is powered on. You might see the error CWZIP1987E in log files.

Because of these limitations, you might need to take additional steps when any of the following situations apply:

* The allocated memory is less than or equal to 3 GB and you want to increase it to a value greater than 3 GB
* You want to increase the allocated memory to more than 16 times the memory allocation when the virtual machine was last started
* The current CPU allocation is one virtual CPU and you want to add more virtual CPUs
* You want to increase the CPU allocation to a value greater than eight virtual CPUs
Resolution Perform the following steps to modify the allocated virtual CPUs or memory size of the virtual machine:
1. Stop the virtual machine instance.
2. Resize the allocated memory or number of virtual CPUs.
3. Restart the virtual machine instance.

Memory utilization values differ between the 'Virtual Machine' and 'Virtual Application' pages
Problem When viewing memory utilization values on the Virtual Machine page or Virtual Machines section of the pages for virtual systems, virtual applications, or shared services in the workload console, you might notice that the values are different than the ones that are reported on the virtual machine monitoring area in the Virtual Application Console.

The scaling policy that is applied to a workload might seem to not be triggered, even though the scaling threshold has been exceeded. Also, the Health Status for a virtual machine or deployment might be in Warning or Critical state, even though the displayed utilization metrics are below the defined thresholds.
Resolution This different in values is expected. These pages all use data that is returned from the hypervisor, which is only returning the active memory usage at any given point in time and not the allocated or in-use memory usage across a reasonable time frame.

The Scaling Policies and Health Status for workloads use utilization values that are provided by tooling inside the guest operating system of the virtual machine, which has a more accurate view of in-use memory. Complete the following steps to view memory values that are used for these functions:

1. Go to the Virtual Application page and click Manage to open the Virtual Application Console.
2. In the Monitoring tab, select the virtual machine to view the utilization graphs.

This utilization data is provided directly by the monitoring agents that are running on the operating system of the virtual machines and have access to both the guest operating system and hypervisor view of in-use memory.

Names of archive files uploaded to script packages and emergency fixes must be comprised only of ASCII characters
Problem Errors can occur when applying emergency fixes that use uploaded archive files with names containing non-ASCII characters. Similarly, errors can occur when script packages are deployed by using archive files with non-ASCII characters.
Resolution Before uploading archive files to script packages or emergency fixes, ensure that the archive file name contains only ASCII characters.

'Name or service not known' error after adding Default add NFS add-on to virtual system
Problem When deploying a virtual system after adding a Default add NFS (Network File System) add-on, a 'Name or service not known' error might occur.
Resolution Before deploying the virtual system, specify the IP address of the NFS add-on instead of the host name in the HOST_NAME field in the Pattern Editor.

If you have already deployed the virtual system and see the 'Name or service not known' error, perform the following steps:

1. Open the workload console.
2. Click Patterns > Virtual Systems.
3. Select the pattern in the left navigation pane.
4. Click Edit to open the Pattern Editor.
5. On the canvas, locate the Default add NFS add-on, and click the edit option to open the Parameters for Default add NFS window.
6. In the HOST_NAME field, replace the host name with the IP address of the network file system.
7. Redeploy the virtual system.

Cannot add users to the 'Access granted to' list for virtual applications and virtual systems
Problem When working with instances of virtual applications and virtual systems in the workload console, you cannot add new users to the Access grant to field when 500 users are already in the system. 500 is the maximum amount of users that you can add through the user interface.
Resolution Use the command line interface tool to add users beyond the 500-user limit. See the Share a virtual application with another user section in the Virtual application instance command-line interface reference topic for more information.

WebSphere Application Server virtual machines that are approaching memory limits cause errors
Problem When running both the System Monitoring shared service and the System Monitoring service for WebSphere Application Server, certain WebSphere Application Server virtual machines that are approaching their memory limit in a virtual system pattern might not display in the System Monitoring Portal, or those virtual machines might display with 'Error' or 'Critical' status.

Also, the virtual system pattern deployment might display a health status of 'Running but with error (Workload agent failure)'. If you view the details for the virtual system pattern deployment, you might see a First failure data capture (FFDC) 'error=12, Not enough space' error in the agent logs in the /opt/IBM/maestro/agent/usr/servers/${servername}/logs/FFDC.log file.
Resolution Edit the virtual system pattern to increase the memory for each WebSphere Application Server (including CustomeNode, Dmgr, and others). For PureApplication System W1500, increase the memory to 4 GB. For PureApplication System W1700, increase the memory to 6 GB. Also, check the virtual machine to confirm that it is not using too much memory.

Network issues occur in DB2 HADR environments using IPv6
Problem The database pattern versions that are provided in the initial release of PureApplication System version 1.1.0.2 do not support high availability disaster recovery (HADR) environments with Internet Protocol version 6 (IPv6). With IPv6 enabled, the primary system is unable to contact the standby system.
Resolution Update the database patterns on your system to the version that supports IPv6. For more information, see Installing database pattern and database performance monitoring updates for IPv6 with HADR support in PureApplication System Version 1.1.0.2.

Cannot log in to the VNC web console with the virtuser account
Problem The password for the virtuser account must contain at least six characters. A password with fewer than six characters results in a log-in failure.
Resolution Change the virtuser password so that it contains six or more characters.

Database deployments and cloning fail when up to 2 TB of storage space is specified 
Problem The initial storage size limit for AIX DB2 database deployment is 1 TB, and the limit for a Linux DB2 database deployment is 1.8 TB. If this limit is exceeded, the deployment will fail but an error message is not displayed. Cloning will also fail if the storage limits are exceeded.
Resolution If you want to deploy a database with a storage size of up to 2 TB, you must first create either an AIX database with a storage size no greater than 1 TB, or a Linux database with a storage size no greater than 1.8 TB. After the database is created, use the workload console to increase the storage size. If you want to clone a database deployment, the storage size for a database on AIX cannot exceed 1 TB, and the storage size for a database on Linux cannot exceed 1.8 TB.

IBM Image Construction and Composition Tool



Problems using WebSphere Application Server 8.5.x virtual images in Image Construction and Composition Tool
Problem When using PureApplication System W1500 and WebSphere Application Server 8.5.x virtual images in Image Construction and Composition Tool, note that the VMware ESX cloud provider does not work correctly for these images.

The following images are affected:

· WebSphere Application Server 8.5.0.2 64-bit RHEL 6 x86-64 (VMWare)
· WebSphere Application Server 8.5.0.2 32-bit RHEL 6 x86-64 (VMWare)
· WebSphere Application Server 8.5.5.0 64-bit RHEL 6 x86-64 (VMWare)
· WebSphere Application Server 8.5.5.0 32-bit RHEL 6 x86-64 (VMWare)
Resolution For this type of images, use the PureApplication System cloud provider instead.

Database performance monitoring



Revert function is not available when upgrading the Database Performance Monitoring shared service
Problem During the upgrade of the Database Performance Monitoring shared service from 1.0.0.3 to 1.0.1.0, if you click the Revert button the revert action will not complete and the upgrade will hang. The revert action is not supported for Database Performance Monitoring shared service upgrades.
Resolution If the error has occurred, delete the Database Performance Monitoring shared service and deploy it again. To avoid the error, do not click Revert when you are upgrading the Database Performance Monitoring shared service, either by itself or when you are upgrading multiple system-plugins including DPM.

Error occurs about database not being configured for tuning
Problem After you have tuned some queries successfully, you might see an error message that says the database is not configured for tuning when you attempt to tune additional queries.

This problem can occur when you tune DDL statements using the web console, for example by selecting Tune All with This Web Console from the Execution Summary tab in the SQL dashboard. When DDL statements are tuned, they are also executed under the user ID who deployed the database, and some of the tables that are created under that user ID's schema can cause problems with query tuning.
Resolution Connect to the database that you are monitoring with the Database Performance Manager and look for tables that match this list under the schema of the user ID that was used to deploy the database.
Issue the DROP command on the following tables, which can cause the error:

ADVISE_*
EXPLAIN_*
OBJECT_METRICS

You can also issue the DROP command on the following tables, since they are not needed:

QT_*
OPT_PROFILE

To prevent the error from happening again, ensure that you do not tune DDL statements. You can use dashboard filters in the database performance monitor web console to remove DDL statements from the grid so that you do not tune them as part of a workload.

HTTP 404 error occurs after registering database and starting the Database Performance Monitoring shared service
Problem After registering a database and starting the Database Performance Monitoring shared service, an HTTP 404 error occurs when attempting to access the registered database. This error occurs when the database registration fails.
Resolution Perform the following steps to confirm that the database registration failed:
1. In the workload console, click Instances > Shared services > Database Performance Monitoring - [Cloud group] > Endpoint.
2. Confirm that the database is not listed in the Health Summary section of the shared service.
3. Perform the following steps to confirm the error in the database log file.
    A. In the workload console, click Instances > Virtual Applications or Databases > {Application or database} > Log.
    B. Navigate to database-db2.nnnn > IWD Agent > .../logs/database-db2.nnnn.OPMDB2 > trace.log, and open the log file.
    C. Scroll approximately 20 lines and locate a line similar to the following:

    url_effective = xx.xx.xx.xx:55000/dbperfmon/register<⁄code>

    This line confirms that the HTTP 404 error message is caused by a failed database registration.

Perform the following steps to re-register the database:

1. In the workload console, click Instances > Shared services > Database Performance Monitoring - [Cloud group] > Manage.
2. In the Virtual Application Console, click Operations > Database-Performance-Monitor.OPM > Database Performance Monitoring > Restart > Submit.
3. For each unregistered database, perform the following steps:
    a. In the workload console, click Instances > Virtual Applications or Databases > {Application or database} > Manage.
    b. In either the Virtual Application Console or the Database Service Console, click Operations > database-db2.DB2 > Database Performance Monitoring > Restart database monitoring > Submit.
    c. Confirm that the database is registered with the shared service. If registration is not successful, repeat these steps.

Deployed databases are not enabled for monitoring
Problem Databases that are deployed through a virtual system pattern before the Database Performance Monitoring shared service is started are not enabled for database monitoring.
Resolution To enable database monitoring for a virtual system pattern, start the Database Performance Monitoring shared service before you deploy the database.


After an HADR failover occurs, the Database Performance Monitor does not recognize the new primary database
Problem When a high availability disaster recovery (HADR) primary database fails, the secondary database becomes the new primary. However, the Database Performance Monitor will not recognize the old secondary database as the new primary database.
Resolution This is a known limitation. After the initial primary database is restored, database monitoring will resume.

Deleted databases remain listed on the Database Performance Monitor page
Problem When deleting deployed databases that are listed on the Instances > Shared Services > Database Performance Monitoring - [cloud group] > Endpoint page, note the following behaviors:

If you stop databases and then delete them, those databases remain in the user interface. This is because the databases do not get removed from the shared service registry.

However, if you delete databases that are running, those databases are removed from the user interface because the shared service registry gets updated.
Resolution Delete databases when they are running so that they get removed from the shared service registry. You can also manually remove databases instances that were not removed from the registry in the workload console by doing the following steps:

1. Open the workload console.
2. Click Instances > Shared Services > Database Performance Monitoring - [cloud group] > Endpoint.
3. On the Database Performance Monitor page, click the Database tab.
4. In the table, click the database connection, and click the trash can icon above the table.

Advanced Middleware Configuration



Password for automation engine client is not documented
Problem The root password for the Advanced Middleware Configuration automation engine is not given anywhere in the information center.
Resolution The password is root and should be changed immediately from within the automation engine client.

Advanced Middleware Configuration script packages are supported only on Linux and AIX
Problem Advanced Middleware Configuration script packages are not supported when attached to Windows based images.
Resolution This is a known limitation in this release.

Configuration properties files can be lost during upgrades
Problem If you upgrade from a version of Advanced Middleware Configuration earlier than 1.0.0.1, configuration properties files (env-config.properties) are not copied from the old location (the RAFW_HOME/work directory) to the new location (the RAFW_HOME/user/preserve/envgen directory).
Resolution The preferred workaround is to back up the RAFW_HOME/work directory before you upgrade, and then copy the contents to the RAFW_HOME/user/preserve/envgen directory after the upgrade. If you have already upgraded and lost your properties files, use the existing configuration option of the configuration editor to recreate the missing configuration definitions.

Custom templates fully supported for WebSphere Application Server and WebSphere Portal only
Problem For middleware products other than WebSphere Application Server and WebSphere Portal, you might see errors due to mismatched token names between the user-created templates and the product templates. The automated creation of custom templates is not available for the WebSphere Application Server Liberty profile.
Resolution For products other than WebSphere Application Server and WebSphere Portal, use product templates and customize the configuration definitions manually.

Clusters cannot recognize custom node types
Problem Nodes define what types of servers you can create on them. Clusters define what types of nodes their servers go onto. Servers are located on nodes, but are managed by clusters. Therefore, existing cluster types do not recognize custom nodes and will not allow you to create servers on them. The custom nodes are not even available in the configuration editor to add to a cluster.
Resolution For this release, do not use custom node types if you want servers on those nodes to be clustered. Instead, add custom questions for the standard node types.

RAFW_EnvironmentGenerationWizard automation plan no longer created
Problem RAFW_EnvironmentGenerationWizard automation plan is missing.
Resolution Due to extensive changes in the generation process, this plan is no longer needed. Existing copies of the plan are not deleted when you upgrade from a version earlier than 1.1, but the plan is no longer created if you install version 1.1.

User change logging suppressed in Tomcat logs
Problem The user change function in the automation engine is being invoked frequently enough that logging the activity was causing very large log files.
Resolution If you want to restore those messages, comment out the following line in the RAFW_HOME/server/tomcat/conf/logging.properties file:

com.buildforge.services.server.api.AuthContext.level=WARNING

Use a number sign (#) as the comment character.

-genCloudPattern option is no longer supported in rafwEnvBuild
Problem The -genCloudPattern option was removed from rafwEnvBuild.
Resolution With the current release, you use the Eclipse client to generate virtual system patterns (VSPs).

Default OS_RAFW_HOME changed
Problem In previous releases, the default value for OS_RAFW_HOME on UNIX and Linux target systems (such as AIX_RAFW_HOME) was "/opt/RAFW". With the new release, the value is now "/tmp/RAFW". The value for Windows target systems did not change.
Resolution You can change this default value by editing the configure.properties file on the framework server in the RAFW_HOME path.

Property name change for WebSphere Application Server Liberty profile
Problem If you are using a WebSphere Application Server Liberty profile configuration properties file that was created in a previous version of Advanced Middleware Configuration, you cannot generate the configuration definition from the existing file.
Resolution You must make a manual change to the properties file before you regenerate the configuration definition file.

Open the configuration properties file (RAFW_HOME//user/preserve/envgen/env-config.properties) in an editor. Change the name of the LIBERTY_ENVIRONMENT property to ENVIRONMENT. Change the name of the LIBERTY_PROFILE_NAME property to CONFIGURATION.

Save the properties file and regenerate the configuration definition.

Generation process for new configurations creates four automation plans
Problem Generation creates unexpected automation plans.
Resolution With this release, when you create a configuration definition from scratch, the generator not only creates the RAFW_env_config plan to create the live configuration on the target system, but also creates the same three automation plans that are generated for an existing configuration: RAFW_env_config_compare, RAFW_env_config_execute, and RAFW_env_config_import.

Problems validating the Rational Asset Manager repository URI
Problem The Rational Asset Manager repository URI does not require the context root for the Rational Asset Manager GUI. This is different from the Rational Team Concert repository URI which does require the context root. For example, if your Rational Asset Manager server is at ramsvt2.example.com:9080/ram/ and your Rational Asset Manager web services are ramsvt2.example.com:9080/ram.ws/RAMSecure/rootservices, then specify ramsvt2.example.com:9080/ram.ws as the value for the repository URI.
Resolution Make sure the URIs are formatted correctly for the product you use.

Configuration not checked into source control because of "ambiguous workspace"
Problem Due to a problem with Rational Team Concert, if you accept the default value when creating a workspace, duplicate workspaces might be created. If two or more workspaces exist with the same name, regardless of who created them, the configuration is not checked in and a message that reads "Ambiguous workspace/stream" is written to the log.
Resolution Do not use the default value when creating a Rational Team Concert workspace.

Rational Asset Manager and Rational Team Concert integrations not available on Windows
Problem You can use Rational Asset Manager or Rational Team Concert to store configuration definitions for a Advanced Middleware Configuration server on UNIX or Linux systems only. The integrations with Rational Asset Manager and Rational Team Concert are not available for an Advanced Middleware Configuration server running on Windows.
Resolution This is a known limitation in this release.

Use "-product" option when creating Liberty profile through the command line wizard
Problem When creating a configuration definition for WebSphere Liberty profile through the command line wizard, do not use the Liberty profile option in the product list. For new configurations, the definition is created in the wrong directory. For existing configurations, the wizard fails.
Resolution Start the rafwEnvBuild command with the "-product liberty" option.

Cannot add WebSphere Application Server nodes to WebSphere Service Registry and Repository clusters
Problem When you create a configuration definition for a WebSphere Service Registry and Repository cell, you can add only WebSphere Service Registry and Repository nodes to a cluster. At this time, you cannot add WebSphere Application Server or other types of nodes to the clusters.
Resolution This is a known limitation in this release.

Warnings in log after running integrateToBF
Problem When you run integrateToBF createAll on a new installation of Advanced Middleware Configuration , you might see "Missing required parameter 'env.uuid'" warnings in the catalina log file.
Resolution You can ignore these warning messages.

Concurrent imports of the same cell cause deadlock
Problem If you have two configuration definitions based on the same WebSphere Application Server cell and you run the import automation plans from both configurations at the same time, neither plan completes.
Resolution Do not run the import automation plans from both configurations at the same time.

Configure actions excluded for standalone servers
Problem The following two configure actions are not included in the was_common_configure_all action for WebSphere Application Server cells with a standalone server:

was_common_configure_health_policies
was_common_configure_service_policies
Resolution The problem is related to the base installation code for WebSphere Application Server. If you have a cell with a standalone server that you created using WebSphere Application Server Network Deployment installation code, you can run these two actions separately after the was_common_configure_all action completes.

False positive result of configuration storage automation plans
Problem When you run one of the "get" or "put" automation plans for either Rational Team Concert or Rational Asset Manager, the plan may fail while indicating success. These plans determine their success or failure using text filters to find specific strings within the command output. If none of these strings match, then the command is deemed successful. It is possible that the command was unsuccessful, and either returned an unexpected string or possibly no string at all.
Resolution When running a configuration storage automation plan, scan the output and verify that no errors were reported.

Administrative agent questions displayed for Network Deployment cells
Problem When creating a WebSphere Application Server version 7.0, 8.0, or 8.5 configuration definition in the Advanced Middleware Configuration console, it is possible to specify a “Standalone” cell type, answer “Yes” for administrative agent, and then change the cell type to “Network Deployment. “ In this case, the administrative agent setting remains "Yes".
Resolution Do not change from “Standalone” to “Network Deployment” if you have already set the administrative agent to “Yes”. If you have already made this change, delete the configuration definition and reenter the information.

Date does not change after VSP update
Problem If you update a VSP from a template, but do not remove the VSP from IBM Workload Deployer and reload it, your changes show up in IBM Workload Deployer, but the displayed date of the VSP does not change.
Resolution No workaround is required, because the VSP is updated correctly.

Generating with rafEnvBuild from older configuration properties files results in missing or incorrect values
Problem Advanced Middleware Configuration version 1.1 added a scope data file to the generation process. If you generate an older configuration properties file using the command line, that file is not available and errors can result.
Resolution Open the file in the configuration editor and generate it there.

Framework server fails to start due to missing password
Problem If you upgraded from Advanced Middleware Configuration version 1.0.0.3 or earlier, you might not be able to start the framework server.
Resolution Edit RAFW_HOME/buildforge.propeties. Add a BF_ROOT_PASSWORD property and set it to the Rational Build Forge root user password. If you don't know the root password, and BF_USERNAME is set to root, you can copy the value from BF_PASSWORD to BF_ROOT_PASSWORD. Save the buildforge.properties file and restart the framework server.

was_common_configue_sibus_all does not properly update Messaging bus entries
Problem When you run was_common_configue_sibus_all in execute mode, the attributes are imported, but any changes to the sib.xml file are not propagated to WebSphere Application Server when executed.
Resolution Delete the messaging engine and recreate it with the desired datasource attributes.

Possible confusion over name of was_common_configure_security_ssl action
Problem The was_common_configure_security_ssl action corresponds only to Security > SSL certificate and key management > SSL configurations in the WebSphere Application Server console.
Resolution If you want the action that corresponds to Security > SSL certificate and key management > Dynamic outbound endpoint SSL configurations, which you use to import, execute, or work with changes, use the was_common_configure_security_global action.

WebSphere Application Server administrative console permits invalid characters in passwords
Problem You can include the "$" and "&" characters in a password that you create through the WebSphere Application Server administrative console. However, if you then use that password in the Advanced Middleware Configuration configuration editor, or any other process that uses a SOAP connection, the password will not be recognized.
Resolution The best workaround is to not create a password that uses invalid characters. You can still use a password with some invalid characters (such as "$" and "&") by prefacing them with a backslash, or by enclosing the entire password in single quotes.

The was_common_configure_start_cluster action times out
Problem The was_common_configure_start_cluster action times out if the cluster fails to start within 30 minutes. This can be caused by a cluster that is simply very slow to start.
Resolution Use the was_common_configure_ripple_start_cluster action instead. This action cycles through all the servers in the cluster, stopping and restarting each one in turn so that at least one server is available at all times to handle processing.

Eclipse client uses system browser to create configuration definition
Problem Unexpected browser used. In previous releases, the Eclipse client used an internal browser to display the Environment Generation wizard. With the current release, configuration definitions are created in the new console interface. When you click "Create Configuration Environment" in the Eclipse client, the console is displayed in the system browser rather than the internal Eclipse browser.
Resolution No action is required.

Creating virtual system pattern from template results in pattern for unintended part
Problem The VSP generator chooses parts based on the way those parts identify themselves. If, for example, a new image is an extension of a WebSphere Application Server image, but still identifies itself as the WebSphere Application Server part, Advanced Middleware Configuration might use the new image rather than the intended WebSphere Application Server part.
Resolution Instead of generating a VSP, use the same interface to generate a custom script package based on the template. You can then manually create a VSP in the Workload Console and add the custom script package as well as the Cleanup, Import, and Integration script packages. Alternatively, you can edit the generated VSP, remove the incorrect image, and replace it with the appropriate one.

Virtual system pattern generation fails due to missing script package
Problem When generating a virtual system pattern from a template, the following error message is displayed:

CRWSE0307E No matches for script package with name AMC Xxxxxx Script Package
Resolution You must have the following script packes in the IBM PureApplication System catalog:

· AMC Cleanup Script Package
· AMC Import Script Package
· AMC Integration Script Package

If any packages are missing, upload them from the following location on the framework server:

/opt/IBM/RAFServer/rafw/framework/wca/

The following files are available:

· CleanupScriptPackage.zip
· ImportScriptPackage.zip
· rafwScriptPackage.zip (contains AMC Integration Script Package)

After all three script packages are displayed in the catalog, generate the VSP again.


The Advanced Middleware Configuration integration with Rational Asset Manager is not available on AIX
Problem Version 1.1 of Advanced Middleware Configuration does not support Rational Asset Manager integration on the AIX platform.
Resolution This is a known limitation in this release.

Deploying an instance of Advanced Middleware Configuration from a hypervisor image fails with messages about integrateToBF
Problem Deployment fails with the following messages.

Unable to retrieve the UUID for the entry BF_RAFW_GLOBAL_ENV_UUID in buildforge.properties. Ensure the integrateToBF script has been run. The most common symptom of this problem is later project failing to expand the MODE variable
com.ibm.rational.rafw.wsadmin.RafwException: Unable to retrieve the UUID for the entry BF_RAFW_GLOBAL_ENV_UUID in buildforge.properties. Ensure the integrateToBF script has been run. The most common symptom of this problem is later project failing to expand the MODE variable.

This is a rare condition. It is likely that Tomcat does not start and run the services for Advanced
Middleware Configuration in a timely way. This condition prevents the integrateToBF script from running, which is
required for deployment.
Resolution Delete the instance and deploy it again.

File name differences in /tmp directory are deliberate and should not be changed
Problem The default working directory of integration script package is /tmp/rafw (lower case). The LINUX_RAFW_HOME
defined in the configure.properties file for the server is /tmp/RAFW (upper case).
Resolution This naming is deliberate and should not be changed.

Common messages produced when you restore by amcBackupAndRestore.sh
Problem When you are using the amcBackupAndRestore.sh script to restore
Advanced Middleware Configuration, you may see the various messages.
Resolution 1) These messages are produced when the database is being restored on the
new image of AMC. You can ignore them.

Restoring database 'RAFDB'...
Executing:Â  su - db2inst1 -c "db2 restore database RAFDB taken at xxxxxx without prompting"
SQL2540WÂ  Restore is successful, however a warning "2539" was encountered
during Database Restore while processing in No Interrupt mode.

DB2 warning message 2539 means that a database with the given name (in this case RAFDB) already

exists and that the data in that database will be
overwritten. That overwrite is what is intended during a restore.
You can ignore this message.

2) The following messages are produced when the script is attempting to create the Advanced Middleware Configuration web UI tab. The tab is no longer used in AMC v1.1 and later releases.

Executing:  /opt/IBM/RAFServer/rafw/bin/integrateToBF.sh removeUITab
Advanced Middleware Configuration for PureScale Application System version 1.1.0.1 build 20130917-1729
CRWFW0471I Invalid argument supplied:
ERROR: A valid argument was not found in the argument list.

The usage statement for integrateToBF.sh is then shown.

You can ignore this message.

Upgrading from version 1.0.x requires manual reinstallation of agents
Problem Upgrading from version 1.0.x requires manual reinstallation of agents.
Resolution If you are upgrading from Advanced Middleware Configuration 1.0.x, you need to reinstall Build Forge agents manually.

1. Inside the downloaded fix pack for version 1.1.0.1, find 1.1.0.1-Rational-BFAgents-All-FP0001.zip.
2. Copy the file to a temporary directory on the deployed instance you are upgrading.
3. Unzip the file.
4. Run the agent installer for your operating system. See the information center for Build Forge version 7.1.3.5. Instructions for each operating system are in Installing agents.

If you are upgrading from version 1.1.0.0 or later, you do not need to reinstall agents manually.

Cannot stop server1 during execution of RAFW_WAS_Admin_Agent_Uninstall_Helper_Library step
Problem
This note applies when is the version of Websphere Application Server is any of V7.0, V8.0, or V8.5.

When you install an Administrative Agent topology using RAFW_WAS_ _Admin_Agent_Install_Library, a default application server named server1 is created on each managed node in the cell. The server1 server is not included in the Rational Automation Framework environment. It cannot be configured using actions.

Resolution
Stop and delete server1 manually before running RAFW_WAS_Admin_Agent_Uninstall_Helper_Library.

Administrative Agent installation plan fails when no application server is defined
Problem
This note applies when the version of WebSphere Application Server is V7.0, V8.0, or V8.5.

The installation plan RAFW_WAS_ _Admin_Agent_Install_Library for the WebSphere Application Server administrative agent fails if no application servers were defined for the managed nodes in the cell during definition of a new configuration for the Administrative Agent.

Resolution
Disable steps for the application servers before running RAFW_WAS_ _Admin_Agent_Install_Library
· RAFW_WAS_Admin_Agent_Uninstall_Helper_Library: disable the "Stop servers" step.
· RAFW_WAS_Admin_Agent_Install_Helper_Library: disable the "Create servers" and "Start servers" steps.

Note that you should avoid creating a configuration that does not contain at least one application server.


Cluster member in WebSphere Application Server version 6.1, 7.0, 8.0, and 8.5 is set to the wrong SERVER_TYPE after upgrade from Advanced Middleware Configuration 1.0.0.0 and regeneration
Problem
After upgrade, when you regenerate the configuration, the SERVER_TYPE is set to APPLICATION_SERVER. It should be APPLICATION_SERVER_MEMBER.
Resolution
Edit the configuration manually, then regenerate.

was_common_configure_all fails with On Demand Router server: When the action runs, the following exception is returned
Problem
[exec] WASX7017E: Exception received while running file
"c:/RAFW/product/actions/configure/was/common/scripts/manageServer.py";
exception information:
com.ibm.websphere.management.exception.InvalidConfigDataTypeException:
ADMG0007E: The configuration data type CustomProperty is not valid.
The problem is caused by a problem with Websphere Application Server.
Resolution
Manually configure On Demand Router servers using Websphere Application Server tools.


Related:
List of fixes in IBM PureApplication System W1500 and W1700 Version 1.1.0.3
IBM PureApplication System release notes by version

Rate this page:

(0 users)Average rating

Document information


More support for:

PureApplication System

Software version:

1.1.0.3

Operating system(s):

AIX, Linux Red Hat - xSeries, W1500, W1700, Windows

Reference #:

7041771

Modified date:

2014-04-18

Translate my page

Machine Translation

Content navigation