Release notes for IBM PureApplication System W1500 and W1700 Version 1.1.0.0

Problem	PureApplication System supports nine or fewer cloud groups.
Resolution	Do not deploy more than nine cloud groups. This is a known restriction.

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

New deployments do not appear immediately on the product license page

Problem	New deployments do not immediately appear in the In the cloud now section on the product license page. New deployments are recognized by the license timer every 30 minutes to ensure that no erroneous entries exist.
Resolution	Wait 30 minutes, and check the product license page again.

Missing DisplayItem choices in monitoring agent for PureApplication System situation definitions

Problem	When creating situation definitions by using data from the monitoring agent for PureApplication System, the following error message displays when you attempt to specify a display item in the situation editor: KFWITM047E. The display item feature can not be used with this situation because no attributes are eligible for use as a display item in group The DisplayItem field in a situation definition allows you to identify an attribute that uniquely identifies event instances that are associated with various resources that are being monitored by the situation. Although some of the attribute groups in this agent have DisplayItem choices, other groups have only few or no DisplayItem choices.
Resolution	This is a known limitation in this release.

License usage that has been exceeded does not show warnings in history page

Problem	Licenses used in deployments might exceed the warning thresholds that are specified in the product license page. In these cases, the product license page shows that the warning level has been exceeded, but the history of the virtual instance does not show any warning messages.
Resolution	This is a known limitation.

WebSphere Application Server restarts even when the option to restart automatically is disabled

Problem	After deploying the System Monitoring service for IBM WebSphere Application Server with the Restart WAS servers automatically option disabled, the application servers unexpectedly restart when configuring monitoring services in both virtual applications and virtual systems.
Resolution	On cloud groups with existing WebSphere Application Server deployments, disable the Start monitoring agent when existing deployments discover Shared Service for the first time option when deploying the System Monitoring service for WebSphere Application Server. For new deployments, deploy the service into a cloud group where the System Monitoring service for WebSphere Application Server is not deployed.

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.

Exception occurs when adding 90 or more VLANs to the customer network configuration

Problem	PureApplication System automatically defines a maximum of 127 spanning tree group numbers for each VLAN that is assign to a spanning tree group. When the total number of VLANs exceed 127, the spanning tree is automatically disabled. In this design, PureApplication System does not support more than 90 VLANs in the VLAN range. To manage virtual local area network (VLAN) information, open the system console and click Hardware > Customer Network Configuration. In the VLAN Information section, you can specify VLAN ranges and enable spanning tree (PVRST).
Resolution	Do not define more than 90 VLANs when specifying the VLAN range.

Name of system being shut down is not displayed in the CWZIP6088I message

Problem	When shutting down PureApplication System, a CWZIP6088I message displays to confirm the shutdown process. The message should specifically mention the name of the system that is being shut down. However, only a ${0} variable name displays.
Resolution	Ignore this error. You can see the name of the system in the Source column, which is located beside the Event Text column in the events console.

System maintenance report is missing information

Problem	In the system console, click System > Settings and expand System Maintenance Report to view details about hardware, including machine type models, serials numbers, device types, firmware, and more. In the table, you might notice that certain cells are empty. Empty cells indicate that the information is not currently available for the component.
Resolution	To access hardware details, open the Hardware menu in the system console and click the individual components, for example Hardware > Compute Nodes.

PureApplication System base operating system image uses IPv6 to connect to customer data networks

Problem	The base operating system image that is provided by default with PureApplication System W1700 uses Internet Protocol version 6 (IPv6) to connect to customer data networks. However, certain enterprises might not want their data networks connecting through IPv6 for security reasons.
Resolution	Do the following steps to extend and capture the base operating system image so that it does not use IPv6 to connect to data networks: 1. Run this command to connect to your virtual machine and log in as root: ssh root@<ip_addr>. 2. Run this command to open the rc.tcpip file in edit mode: vi /etc/rc.tcpip. 3. Locate the following section in the rc.tcpip file: # Start up autoconf6 process start /usr/sbin/autoconf6 "" " -i en1 " start /usr/sbin/autoconf6 "" " -i en0 " #start /usr/sbin/autoconf6 "" 4. Comment out this line: start /usr/sbin/autoconf6 "" " -i en1 " 5. Save your changes. 6. Capture the image with your changes and use it in your deployments.

Health status indicator warnings for high memory utilization on AIX 7.1 operating systems

Problem	For PureApplication System W1700, when using the AIX 7.1 operating system with a virtual application such as the Web Application Pattern, the health status indicator might display warnings about high memory utilization.
Resolution	You can ignore the warnings or use the system console to add more memory to the virtual machines.

Command-line tool

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.

Error occurs when running the startup command for the command-line tool

Problem	When using a Microsoft Windows operating system, after downloading the PureApplication System command-line tool and extracting the contents of the ZIP file, the following error might occur when you run the startup command: Cannot find or load org.python.util.jython This error occurs because the target directory for the extraction contains the term bin in the path name, for example C:\\tools\bin\,
Resolution	Do not extract the command-line tool ZIP file into a directory that includes the term bin in the path name.

Disaster recovery

Misleading messages about cloud groups and IP groups used on a disaster recovery backup system

Problem	On a disaster recovery backup system, you might see misleading messages that describe how to make cloud groups and IP groups available. If you view a cloud group on the backup system, you might see one of the following messages: Unavailable (You must add at least an IP group to the cloud group to make it available) Unavailable (You must add at least one available compute node and one available ip group to the cloud group to make it available) If you view an IP group on the backup system, you might see the following message: Unavailable (You must add IP addresses to the IP group to make it available). These messages are misleading because management objects such as cloud groups and IP groups are read-only on a disaster recovery backup system. When the backup role is enabled on the disaster recovery backup system, you cannot add IP groups to a cloud group or add addresses to an IP group.
Resolution	Ignore the message on the backup system. You can edit these objects on the primary system to make them available.

Simplified disaster recovery disk replication provides application consistency only within cloud groups

Problem	The application consistency provided by disaster recovery disk replication provides point-in-time consistency only when recovering all of the virtual machines within each cloud group. After all storage volumes for a cloud group have completed initial copying and reached an available state, all disk writes within that cloud group are replicated in consistent order from the primary system to the backup system. If your deployment spans more than one cloud group, or your application contains tiers that span more than one cloud group, disaster recovery disk replication does not provide point-in-time consistency across your entire deployment or application.
Resolution	If your application supports inconsistent ordering of disk writes between its virtual machines or tiers, no changes are required. If your application requires point-in-time data consistency across all virtual machines and tiers, reconfigure your workload so that all virtual machines and tiers run within the same cloud group. This reconfiguration requires you to delete portions of your deployment or application and redeploy them within another cloud group.

Backup and restore

Current limitations when using REST API to obtain estimated size of system backup

Problem	To retrieve the estimated space requirement of a system backup, you can log in to PureApplication System as the default administrator user and use the following REST API call: https://<RACK_IP>/admin/resources/backup/backupsize <RACK_IP> is the IP address of the system that is being backed up. Note the following limitations when using this REST API call: The estimated size does not include the size of other components that are exported, for example virtual images and virtual appliances. The estimated size does not differentiate between a base and a differential backup size.
Resolution	Do the following actions to work around these limitations: If exporting default images that are provided with the system, add an additional 50G to the backup size estimate. If exporting custom virtual images or virtual appliances, take into account the size of those components when exporting with the backup. For example, when exporting custom images with attached disks and volumes, look at the size of the attached disk and volume and add that number to the backup size estimate. For differential backups, be aware that the backup size might be smaller when running a subsequent backup to the same remote host location and path.

New certificate-key pairs cannot be used with existing system backups

Problem	After generating a certificate-key pair and performing a system backup, if you regenerate the certificate-key pair and then attempt to perform another backup, the following exception might occur: java.lang.Exception: Status 400 returned by POST on localhost/resources/backup during workload backup, output: Unable to create a differential backup where there exists a baseline backup encrypted with different keys
Resolution	Only regenerate a new certificate-key pair when changing the backup storage path and creating a baseline backup.

Connectivity issues

Duplicate warning events occur: CWZIP1812: Unknown host ((no host))

Problem	When experiencing network connectivity problems, you might notice several duplicate occurrences of the following event on the Events page of the system console: CWZIP1812: Unknown host ((no host)): Either the host IP address was incorrect, not supplied, or there are network connectivity problems. These multiple duplicate events might display one after the other in a very short amount of time, resulting in an inaccurate count of times that the network connectivity issue actually occurred.
Resolution	To determine the actual number of occurrences of network connectivity problems, click System Console > System > Events, and view the list of event time stamps.

Managing virtual systems and virtual applications

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, go to the following website and complete steps 1-6: http://www-01.ibm.com/support/docview.wss?uid=swg21598785

License types are incorrect for cloned virtual system patterns

Problem	After adding licenses to a cloned OS virtual image, creating a virtual system pattern with the cloned virtual image, and finally deploying the virtual system pattern, you might notice that license types are not listed accurately in the Instances > Virtual System Instances page in the workload console. For example, in the main window of details for the virtual system, in the Virtual machines > IBM products (with license count for isolated usage) section, you might see products with processor value unit (PVU) licenses, but the licenses are actually compute node or per core licenses.
Resolution	To view licenses for virtual system patterns that are created with cloned virtual images, click System > Product Licenses in the system console. Licenses are listed in the Non-catalog product licenses section.

System Monitoring service shows launching status when running

Problem	When viewing status of the middleware in the Virtual machine perspective section in the Shared Service Instances page in the workload console, you might notice that the Middleware role status column does not show any status and indicates that the overall deployment status is 'launching', even though the System Monitoring shared service is running. In most cases, the deployment status returns to 'running' after a few minutes.
Resolution	No action is required. The System Monitoring service is still running, even though the middleware role status in the details window is missing and overall deployment status is 'launching'. The status should return to 'running' after a few minutes.

Additional storage disk space is not reflected in the environment profile

Problem	If a pattern that includes a disk add-on is deployed with an environment profile, and the disk add-on storage causes the deployment to exceed the storage limit for the environment profile, the disk add-on is ignored, and the In Use and Reserved values for storage space do not include the add-on. For example, if a pattern with 9 GB of disk space and a disk add-on of 50 GB is deployed using an environment profile with only 25 GB of unused storage space, the deployment does not include the disk add-on, and the pattern will consume only 9 GB of PureApplication System cloud resources. To confirm reserved disk space after deploying patterns, open the workload console, click Cloud > Environment Profiles, and open the Environment limits section in the details window.
Resolution	No workaround exists for this issue.

Memory and CPU status are displayed incorrectly

Problem	When using PureApplication System W1500, the virtual machine reports in the system console might display incorrect information. On System Console > Reports > Machine Activity > Virtual Machine Usage, the data reported for 'CPU in use(%)', '30-day average CPU Utilization (%)' and 'Memory usage (%)' might show values over 100%, or values different than the same parameter checked in the Virtual Network Computing (VNC) console.
Resolution	This is a known limitation.

The PID number of a cloned virtual image does not carry over to additional clones of that image

Problem	When cloning a virtual image, you can add the product ID (PID) of the original image to the cloned image on the Catalog > Virtual Images page of the workload console. Then, if you clone the newly created clone, you might notice that the PID number that you added to the first clone does not get added to the second clone. Note: To locate PID numbers of non-catalog product licenses, open the system console, click System > Product Licenses, and open the table in the Non-catalog product licenses section.
Resolution	Manually add the PID number to the second clone.

Host names do not resolve in DB2 Enterprise Server Edition 10.1.0.2 and 9.7.0.8 HADR environments using IPv6

Problem	In DB2 Enterprise Server Edition 10.1.0.2 and 9.7.0.8 high availability disaster recovery (HADR) environments, the primary system is unable to contact the standby system by its host name using Internet Protocol version 6 (IPv6).
Resolution	This is a known limitation. DB2 Enterprise Server Edition 10.1.0.2 and 9.7.0.8 currently does not support IPv6 for HADR.

Increasing allocated CPU or memory resources might require stopping or rebooting the virtual machine

Problem	When using IBM PureApplication System W1500, certain Linux virtualization limitations exist when scaling an active virtual machine. Because of these limitations, you might need to take additional steps when one or more of the following scenarios apply to your environment: The Linux virtual machine was created with less than 4 GB of memory. The Linux virtual machine was created with only 1 virtual CPU. The Linux virtual machine was created with eight or more virtual CPUs. Allocated CPU or memory resources were removed from the Linux virtual machine.
Resolution	Complete the following steps to modify the allocated virtual CPUs or memory size of the virtual machine: Stop the instance. Resize the allocated memory or number of virtual CPUs. Restart the 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.

Virtual Application Console contains erroneous message about starting and restarting WebSphere Application Server when using non-English browsers

Problem	For virtual machines with WebSphere applications, you can manually start and restart WebSphere Application Server, regardless of whether the status of the server is in failed state. In non-English browsers, the Virtual Application Console incorrectly indicates that selecting this option starts or restarts the server only when the server is in failed state.
Resolution	Ignore the message in the Virtual Application Console that says that the option starts or restarts the server only when the status of the server is in failed state. This option starts or restarts the server when the server fails and also when it is not reporting any problems. This error in the user interface does not exist in English browsers.

Names of archive files uploaded to script packages and emergency fixes must be comprised only of ASCII characters </a>]

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.

Database pattern type must be upgraded for PureApplication System 1.1

Problem	The database pattern type from previous releases is not compatible with PureApplication System 1.1.
Resolution	Upgrade the database pattern type to version 1.1.0.7. The database pattern type 1.1.0.7 requires the foundation pattern type 2.0.1.0.

Deployments fail on AIX when installing pattern files that are greater than 2 GB

Problem	On PureApplication System W1700, when deploying a pattern on AIX that includes a file that is greater than 2 GB, the deployment fails with errors.
Resolution	This is a known limitation. As a workaround, try breaking the file into smaller files that are less than 2 GB.

Cannot deploy virtual applications on PureApplication System W1700 using the IBM OS Image for AIX Systems 1.0.x

Problem	After creating virtual applications based on the IBM Foundation Pattern Type 2.0.1.0, if you attempt to deploy those virtual applications on PureApplication System W1700 using the IBM OS Image for AIX Systems 1.0.x as the default image in theCloud > Default Deploy Settings window in the workload console, the deployments fail with errors. This image is based on IBM AIX version 6.1.
Resolution	Use IBM OS Image for AIX Systems 2.0.0.1 as the default image in the Cloud > Default Deploy Settings window in the workload console. This image is based on IBM AIX 7.1.

Monitoring does not work using AIX 6.1 in PureApplication System W1700

Problem	When using AIX 6.1 in PureApplication System W1700, the monitoring agent does not collect metrics data.
Resolution	For virtual systems, change the core operating system to IBM OS Image for AIX Systems 2.0.0.1, which is based on IBM AIX 7.1.

IBM Image Construction and Composition Tool

Maintenance fix required before you upgrade to Image Construction and Composition Tool V2.2.1.1

Problem	Virtual applications that are running Image Construction and Composition Tool V2.2.0.0 require a maintenance fix to be applied before you upgrade to Image Construction and Composition Tool V2.2.1.1.
Resolution	Follow these steps to apply the maintenance fix to virtual applications in PureApplication System V1.1.0.0 and higher. 1. Download the maintenance fix package icct-1.2.0.4efix (IV43476.zip) from Fix Central at http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&function=fixId&fixids=icct-1.2.0.4efix. 2. Following the information on the Fix Central page, apply the maintenance fix to all virtual applications running Image Construction and Composition Tool V2.2.0.0 that require upgrading to V2.2.1.1. 3. Upgrade the virtual application by using the information in Upgrading deployed pattern types at http://www.ibm.com/support/knowledgecenter/SSNLXH_1.1.0/com.ibm.puresystems.appsys.1500.doc/iwd/apgst_upgradepattern.html. Note: If you apply the upgrade and then revert it, the virtual application is reverted to the state in which it was before applying the maintenance fix. If you intend to upgrade after the revert operation, you must apply the maintenance fix before attempting the upgrade again.

Restriction when using environment profiles for Image Construction and Composition Tool

Problem	When synchronizing virtual images in Image Construction and Composition Tool, restrictions apply for environment profiles defined in the Cloud provider parameters wizard. If the field IP addresses provided by in the environment profile is set to the value Pattern Deployer, then the environment profile cannot be used for Image Construction and Composition Tool or the Image Construction and Composition Tool virtual application pattern.
Resolution	This is a known limitation.

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

Page continues to load and then logs out of the session

Problem	When checking the status of the Database Performance Monitoring service in the workload console on the Shared Service Instances page, if you click Endpoint in the Middleware perspective section on the main details page, first a Loading message displays followed by a Your session has been logged out message.
Resolution	Restart the Database Performance Monitoring service in the workload console: Click Instances > Shared Services. Select the Database Performance Monitoring service in the list of services. Click Manage to open the Virtual Application Console. Click Operations > Database-Performance-Monitor.OPM > Restart > Submit.

'Can't find server' error when accessing advanced monitoring

Problem	After selecting a database on the Database Instances page in the workload console, and then clicking Manage > Monitoring > Middleware > Advanced monitoring, the browser displays a Can't find the server error message.
Resolution	Restart the Database Performance Monitoring service in the workload console: Click Instances > Shared Services. Select the Database Performance Monitoring service in the list of services. Click Manage to open the Virtual Application Console. Click Operations > Database-Performance-Monitor.OPM > Restart > Submit.

'No component exists' error even though Database Performance Monitoring service is deployed

Problem	After selecting a database on the Database Instances page in the workload console, and then clicking Manage > Monitoring > Middleware, a No component exists error message displays.
Resolution	Restart the Database Performance Monitoring service in the workload console: Click Instances > Shared Services. Select the Database Performance Monitoring service in the list of services. Click Manage to open the Virtual Application Console. Click Operations > Database-Performance-Monitor.OPM > Restart > Submit.

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.

DB2 warning message during amcBackupAndRestore command

Problem	While restoring the database on a new Advanced Middleware Configuration image, the following warning is displayed: `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.`
Resolution	The DB2 warning message 2539 indicates that a database with the given name (in this case RAFDB) already exists and that the data inside that database will be overwritten. This is the expected action, so you can ignore this message.

Error message during restoration of AMC tab [

Problem	While recreating the AMC tab, the following error is displayed: Recreating the AMC UI Tab [Executing: /opt/IBM/RAFServer/rafw/bin/integrateToBF.sh removeUITab CRWWA9904E Unable to connect to the automation engine services. Using hostname=nnn.nnn.nnn.nnn port=3966 username=root ldap domain= Caused by: com.buildforge.services.common.db.DBException: CRRBF0558I: Failed SQL query: [org.apache.commons.dbcp.DelegatingPreparedStatement@21d021d0] => [com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=BF_SHARECOUNT, DRIVER=3.63.75]
Resolution	This usually happens because Advanced Middleware Configuration did not start correctly. Restart Advanced Middleware Configuration by first running the /opt/IBM/RAFServer/rc/buildforge stop command and then verifying that the product was stopped by running the ps -ef \| grep RAFServer command. No processes should still be running. Start Advanced Middleware Configuration again by running the /opt/IBM/RAFServer/rc/buildforge start command. Run /opt/IBM/RAFServer/log and watch for output similar to the following: `Thu 01 Nov 2012 01:37:46 PM CDT: CRRBF0507I: 2306: LicMgr: Server clusters are enabled.` `Thu 01 Nov 2012 01:37:46 PM CDT: CRRBF0801I: 2306: LicMgr: Enterprise license found.` `Thu 01 Nov 2012 01:37:46 PM CDT: CRRBF0997I: 2306: LicMgr: Multiplatform support is enabled.` `Thu 01 Nov 2012 01:37:46 PM CDT: CRRBF0428I: 2306: LicMgr: BOM generation is enabled.` `Thu 01 Nov 2012 01:37:46 PM CDT: CRRBF1255I: 2306: LicMgr: Production mode server.` `Thu 01 Nov 2012 01:37:46 PM CDT: CRRBF1009I: 2306: LicMgr: Manifests are enabled.` `Thu 01 Nov 2012 01:37:47 PM CDT: CRRBF1349I: 2306: LicMgr: Reports are enabled.` `Thu 01 Nov 2012 01:37:47 PM CDT: CRRBF1564I: 2306: LicMgr: Reflectors are enabled.` `Thu 01 Nov 2012 01:37:52 PM CDT: CRRBF0571I: 2306: DB: Database [rafdb] has reached size of [xxxxxx], current threshold [2000000000]. [These lines indicate that the product has started. Run "/opt/IBM/RAFServer/rafw/bin/integrateToBF.sh removeUITab" followed by "/opt/IBM/RAFServer/rafw/bin/integrateToBF.sh createUITab" to recreate the UI tab.`

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.

Resolving conflicts in template creation

Problem	When you use the Eclipse client to create a template from a configuration definition, the new template must pass a number of validation steps. The template can fail validation if any of the following conditions apply: You select more than one scope of the same type. You select files from a second scope of the same type as the selected scope, even if that second scope is not itself selected. You select child scopes (such as nodes and application servers) from a second scope of the same type as the selected scope, even if that second scope is not itself selected.
Resolution	Correct your selections and generate the template again.

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.

Can't 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.

The VSP generator creates a VSP with the wrong WebSphere Application Server version

Problem	When you generate a VSP from a template, the VSP in IBM PureApplication System might have a different version of WebSphere Application Server than the template.
Resolution	Edit the VSP in IBM PureApplication System to replace the Operating System part with one that contains the correct version of WebSphere Application Server.

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.

Documentation

Virtual systems created after a snapshot image are still present

Problem	The documentation regarding restoring a virtual system instance to a previous state by using a snapshot image does not address what happens to virtual machines that are added after the snapshot image was taken.
Resolution	To clarify, when you restore a virtual system instance to a previous state by using a snapshot image, any virtual machines that are added after the snapshot was taken are still present in the environment.

WebSphere Application Server 8.5.5 supported as automation target

Problem	The information center does not include the following update: You can use all existing WebSphere Application Server 8.5 actions with WebSphere Application Server 8.5.5.
Resolution	This is a known limitation in this release.

Microsoft Windows Server 2012 support

Problem	The information center does not include the following update: Microsoft Windows Server 2012 (W2K12) is supported as a platform for WebSphere Application Server 8.5 target systems.
Resolution	This is a known limitation in this release.

Fix pack support

Problem	The information center does not include the following update: The current release supports the following fix packs for IBM WebSphere Application Server and IBM HTTP Server: 70027, 8003, 8004, 8005, 8501.
Resolution	This is a known limitation in this release.

Configuration editor questions reorganized for ND managed nodes

Problem	The information center topic named "Configuration reference for managed nodes" lists a number of configuration editor questions for each managed node under the heading "Questions for Stand-alone Server". Prior to release, these questions were reformatted. There are now two sections, one named "Application Servers on this node" and the other named "Proxy Servers defined on this node".
Resolution	For each application server on the node, provide a name in the "Server name" field. For each proxy server, provide a server name in the "Server name" field and select a template from the "WebSphere Proxy Server template" list.

[{"Product":{"code":"SSM8NY","label":"PureApplication System"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF002","label":"AIX"}],"Version":"1.1.0.0","Edition":"","Line of Business":{"code":"","label":""}}]

Tips

Release notes for IBM PureApplication System W1500 and W1700 Version 1.1.0.0

Release Notes

Abstract

Content

Administering the system

Command-line tool

Disaster recovery

Backup and restore

Connectivity issues

Managing virtual systems and virtual applications

IBM Image Construction and Composition Tool

Database performance monitoring

Advanced Middleware Configuration

Documentation

Administering the system

Command-line tool

Disaster recovery

Backup and restore

Connectivity issues

Managing virtual systems and virtual applications

IBM Image Construction and Composition Tool

Database performance monitoring

Advanced Middleware Configuration

Documentation

Was this topic helpful?

Document Information

UID

Share your feedback

Need support?