CA Change Manager Enterprise Workbench r12 Patch P002

1.0 Welcome

2.0 Operating System Support

3.0 System Requirements

4.0 General Considerations
4.1 Patch P002 Efix Contents

5.0 Installation Considerations
5.1 Prerequisites
5.2 How to Install Patch P002
5.3 How to Uninstall the Patch

6.0 Contact CA Technologies

1.0 Welcome

This readme contains installation information and details about Patch P002 for CA Change Manager Enterprise Workbench (CA CMEW) r12.

2.0 Operating System Support

Supported operating systems are listed in the CA CMEW r12 readme, which is available from Technical Support at http://ca.com/support.

3.0 System Requirements

System requirements are listed in the CA CMEW r12 readme, which is available from Technical Support at http://ca.com/support.

4.0 General Considerations

General considerations for using CA CMEW are listed in the CA CMEW r12 readme, which is available from Technical Support at http://ca.com/support.

4.1 Patch P002 Efix Contents

Patch P002 includes the efixes described next. The following table lists the efixes by date.

Patch P001 efixes:

Patch P002 efixes:

CMEW 176

• Problem description

  The CA Endevor SCM started task can remain active when the last correlated CA CMEW session gets closed other than by using the logout function.

• Correction

  When the last CA CMEW session gets closed for a specific user, ensure that the STC gets ended, even if the session was closed due to the use of ALT-F4 or by pressing the upper-right corner X-button.

CMEW 206

• Problem description:

  A session can hang and be nonresponsive, while performing a Retrieve of an element into a Local Directory (LFS), when the following conditions are met:

  - The client computer is running JRE 1.6.0_13 and above.

  - The user is retrieving one or more elements.

  - The Input field Name (member name) is left blank.

• Correction:

  An element can be retrieved into a local directory without causing the CA CMEW session to hang.

CMEW 207

• Problem description:

  When displaying component changes for an element that has only one level in the component list (that is no changes), the API correctly replies:

  11:23:33 C1G0031W NO CHANGES EXIST AT THIS VV.LL OF THE ELEMENT

  11:23:33 API0000I

  11:23:33 API0000I RETURNED COUNT=00000000, SELECTED COUNT=00000000

  11:23:33 API0000I PROCESSING COMPLETE - RC=00004 REASON=00015

  However, CA CMEW translates this to the following incorrect conclusion: No component list for the selected element.

• Correction:

  If the component list exists and it has only one level, the following correct message is displayed:

  No changes in the component list for the selected element.

CMEW 208

• Problem description:

  When adding the element from a local file system, if the element name is entered, this string is not checked for validity. If the element name is left blank (defaulting to the filename), the check is done properly. For example, If you add file "A B" and the element name is omitted, CA CMEW correctly reports an error, because the element name defaults to the file name and a space is not allowed in the element name. However, If an invalid element name is entered, the check is not done, and CA CMEW does not report an error.

• Correction:

  When the element name is entered, it is checked for validity.

CMEW 210

• Problem description:

  An attempt to Transfer an element with a long name fails with the message:

  API0044E THE AETRA_RQ_ELM_THRU FIELD AND THE REQUEST EXTENSION BLOCK BOTH SPECIFIED.

  Also, the element name is truncated.

• Correction:

  Transfer long name elements and also do not truncate the name.

CMEW 211

• Problem description:

  The element gets uppercased when doing the Transfer of an element that has a mixed case name, but not a long name (for example, Rq12t10).

• Correction:

  Do not uppercase mixed case element names.

CMEW 212

• Problem description:

  CA Endevor SCM Service is not returning correct results for the getElementsByMap request.

• Correction:

  The CA Endevor SCM API LIST ELEMENT action with WHERE CCID selection criteria is being correctly processed, but the data is not reflected in the getElementByMap response. This is resulting in incorrect behavior in client applications that are using the CA Endevor SCM Service (for example the CA Endevor SCM Eclipse Plug-in).

CMEW 213

• Problem description:

  When browsing USS directories during the create CA Endevor SCM package action, the subfolders of directories with no files are not displayed, and only the "Selection list is empty" message is displayed.

• Correction :

  Display subfolders for directories containing no files.

CMEW 214

• Problem description:

  CA CMEW r12 does not accept mixed case passwords. New with RACF at the z/OS 1.9 level, mixed case passwords are now allowed and are being implemented at sites.

• Correction:

  CA CMEW r12 will no longer uppercase the password.

CMEW 215

Correction ensures that CA CMEW r12 is upwardly compatible with CA Endevor SCM r14.

CMEW 217

• Problem description:

  An attempt to execute the CA CMEW Define Data Sources & Deployment tool using Java Runtime Environment (JRE) version 1.6.0_12 and higher, results in a dialog display that is missing option selection buttons. The user is unable to select any of the options, and thus cannot use the tool to configure the product.

• Correction:

  The tool displays all the options for JRE 1.6.0_12 and higher.

CMEW 218

• Problem description:

  Package notes are not shown when displaying package details, even though they have been defined for the package.

• Correction:

  The package notes are shown on the package details page.

CMEW 220

• Problem description:

  CA CMEW r12 Patch 1 causes passwords to no longer be automatically converted to all uppercase for the CA Endevor Software Change Manager (CA Endevor SCM) host. Instead, CA CMEW expects users to type their password in the correct case. This change is causing confusion at sites that expect passwords to default to uppercase.

• Correction:

  A new parameter WebUI.EndevorPasswordUppercased is included in the ew.cfg file to enable or disable the default uppercasing of passwords for the CA Endevor SCM host.

CMEW 221

• Problem description:

  If the special character # is used in a field that is passed on by the URL, all the following characters are discarded. This causes some information not to pass from one screen to another. This behavior was observed when performing package SCL generate in Internet Explorer 7.

• Correction:

  Fields passed by the URL can contain special characters such as #.

CMEW 222

• Problem description:

  The SQL Server History report does not list the Enterprise package executed less than day ago. This time can vary depending on the user's time zone offset. Also, the SQL Server Forecast report does not list correct results.

• Correction:

  The SQL Server History and SQL Server Forecast reports now list correct results.

CMEW 223

• Problem description:

  Executing Endevor Package Search on packages that contain commas (,) in their records (for example, a package description), can fail with following error message:

  Error:UtEndev.getPackages() Error: Invalid Endevor CSV row:-1

• Correction:

  The CSV utility can correctly process records that contain commas.

CMEW 224

• Problem description:

  The Euro sign character is incorrectly converted from the local file system character set (Windows-1252) to the mainframe character set.

• Correction:

  The Euro sign character is correctly supported as a Windows 1252 character.

CMEW 225

• Problem description:

  When executing reports, parameters for the connection to a database must be supplied. For Oracle, the net service name is needed. The net service name is obtained from the JDBC URL specified in the EnterpriseDB configuration file from the name of the server. The user cannot specify a different net service name.

• Correction:

  The field Reporting.NetServiceName is included in the ew config file. You can use this field to change the net service name from the one specified in the EnterpriseDB config file.

CMEW 229

• Problem description:

  When using the Package Create function of CA CMEW to create an Endevor package, all 16 characters of the package name are not displayed. Although up to 16 characters can be entered and are used, the entire package name is not visible.

• Correction:

  The field for the Endevor package name can display up to 16 characters.

CMEW 231

• Problem description:

  The following new options introduced by corrections are not present in the Define Data Source & Deployment tool:

  • Ew.Debug option
  • WebUI.EndevorPasswordUppercased option
  • Reporting.NetServiceName option
• Correction:

  New fields are included in the Define Data Source & Deployment tool for these options.

5.0 Installation Considerations

The following sections contain prerequisite information and installation instructions for the patch.

5.1 Prerequisites

Verify that CA CMEW r12 is installed before you install Patch P002.

In addition, we strongly recommend that you complete the following before deploying this patch:

• Schedule deployment of this patch during the web services maintenance cycle. The web services application must be shut down to deploy this fix.
• Notify users of CA CMEW of the impending upgrade before deploying the patch.
• Read this document completely through before attempting installation and deployment of the patch.
• For WebSphere users only – Know the WebSphere user ID and password before starting the installation, because they are required to deploy the application.

5.2 How to Install Patch P002

The patch installation replaces existing CA CMEW files with new files delivered with this patch. You install the patch by running the installation executable (eFix101013.exe). To install the patch, complete these steps:

1. Stop the web application server that is executing CA CMEW.
2. Execute the delivered eFix101013.exe.
3. Follow the instructions in the installation wizard. Make the following selections or changes, during installation:

   1. On the Choose Components screen, select the components you want installed with the eFix installation files.
   2. On the Choose Install Location screen, if needed, you can change the default installation location (which is obtained from the %EW_HOME% environment variable) to a different location.
   3. During the installation, the following message may appear: "Cannot overwrite DLL files!". This is usually because the DDL files are locked by the Web application server. In this case, stop the web application server and click OK to retry the operation. If the message reappears, make sure there are no other processes locking the DLL files, which are located in the bin folder of the CMEW installation directory.
   4. On the last screen, make your selections for the following fields:

      • Run Define Data Source & Deployment tool – Specifies whether to run the tool at this time.

        - If you want to run the tool now, no changes are needed on this screen. The option Run the Define Data Source & Deployment tool, which specifies whether to deploy the application with this patch applied, is selected by default.

        - If you want to run the tool later, deselect the option Run the Define Data Source & Deployment tool or cancel (Close) the utility after it is started.

        Note: You can navigate to the utility at a later time from the Windows Start, Programs, CA menu.

        - For WebSphere users only – Start the WebSphere web application server before deploying the application.

      • Show Readme – Specifies whether to display the readme. This option is deselected by default. If selected, the readme displays after the installation is finished.
4. Restart the applicable web application server associated with the CA CMEW application. This step is not necessary for WebSphere web application server users.
5. (Optional) After the patch is installed and the Define Data Source & Deployment tool has been run, we recommend the following steps:

   1. Clear the web application server's cache containing precompiled jsp pages.
   2. Advise your users to clear the Java temporary internet files, using the Java Control Panel, on their client machines.

5.3 How to Uninstall the Patch

To uninstall the patch, complete the following steps:

1. Stop the web application server that is executing CA CMEW.
2. Navigate to %EW_HOME%\efix\efix101013 and execute the uninstall.exe file. If you selected the option Create shortcuts during installation, go to Start, Programs, CA, CM Enterprise Workbench, Maintenance, efix101013, and then click Uninstall.
3. Follow the instructions on the screens that guide you through the uninstall process.
4. On the last screen, specify whether you want to run the Define Data Source & Deployment tool at this time.

   • If you want to run the tool now, no changes are needed on this screen. The option Run the Define Data Source & Deployment tool, which specifies whether to deploy the application with this patch applied, is selected by default.
   • If you want to run the toll later, deselect the option Run the Define Data Source & Deployment tool or cancel (Close) the utility after it is started.

     Note: You can navigate to the utility at a later time from the Windows Start, Programs, CA menu.

   • For WebSphere users only – Start the WebSphere web application server before deploying the application.
5. Restart the applicable web application server associated with the CA CMEW application. This step is not necessary for WebSphere web application server users.

6.0 Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following:

• Online and telephone contact information for technical assistance and customer services
• Information about user communities and forums
• Product and documentation downloads
• CA Support policies and guidelines
• Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com.

If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is available on the CA Support website at http://ca.com/docs.

Copyright © 2010 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.