| CA |
3.0 Upgrading from CA CM Enterprise Workbench r7.1 with Shared Tomcat
3.1 Prerequisite for Upgrade from CA CM Enterprise Workbench r7.1 with Shared Tomcat
3.2 Post-Upgrade Actions for CA CM Enterpise Workbench r7.1 with Shared Tomcat
4.0 Interactive Tomcat 6.0.16 Installation
5.0 Setting Up SSL for Your Web Server
7.0 Define Data Sources and Deployment Tool
8.0 Database Creation, Upgrade, and Ingres Migration
9.0 Reading the Enterprise DB Setup Tool Log
10.0 Oracle Client/Server Network Connectivity
11.0 Installing the CD-Image Media From a Local or Network Drive
12.0 Performing a Command Line Deployment of WAR Files
13.0 Contact Technical Support
Welcome to the CA Change Manager Enterprise Workbench r12 (CA CM Enterprise Workbench). This readme contains issues and other information discovered after publication of the Release Notes. For details about how the features and enhancements for this release might affect you, see the Release Notes. For the latest information including any updates that may have occurred after publication of this readme, see http://ca.com/support.
Before you can access CA Endevor SCM r12 SP2 from CA CM Enterprise Workbench, the following PTF must be in applied to CA Endevor SCM r12 SP2: RO04407
If you are upgrading from CA CM Enterprise Workbench r7.1 and using a shared Tomcat, the following prerequisite and post-upgrade actions are required.
If you are upgrading from CA CM Enterprise Workbench r7.1 and using a shared Tomcat, perform the following prior to upgrading to CA CM Enterprise Workbench r12:
Post-upgrade actions are required, if you are upgrading from CA CM Enterprise Workbench r7.1 and using a shared Tomcat located in folder: C:\Program Files\CA\SharedComponents\
When CA CM Enterprise Workbench r7.1 is uninstalled from the server during the upgrade process, the default behavior of the shared Tomcat is returned. This affects the Tomcat port number, which is returned to 8080, and the password of the Tomcat Manager, which is removed. You can change the port number and add the manager access password by editing the following Tomcat files respectively: server.xml and tomcat-users.xml.
The Zip file for shared Tomcat installation has been discontinued for CA CM Enterprise Workbench r12.
Tomcat 6.0.16 is now installed interactively, giving you full access to all of Tomcat's installation features. Consider the following when installing Tomcat interactively through Tomcat's installation program:
If you choose to run https: (secure) instead of http: (non-secure), you need to set up Secure Sockets Layers (SSL) for your web server. Details on how to setup SSL for the web servers that CA CM Enterprise Workbench supports are provided on the software manufacturers' websites. Go to the website for your web server and navigate to the appropriate document. Links to each manufacturer's main site are listed next:
Previous versions of CA CM Enterprise Workbench need to be removed from your web server before performing an upgrade of the product. Recommendations for supported web servers follow.
Tomcat: We recommend that you take a copy of the most recently used *.cfg files prior to undeploying the EW application from Tomcat. The *.cfg files are located in the Tomcat folder tree at: <Tomcat Root Folder>\webapps\ew\WEB-INF\classes\
Undeploying of the previous version of CA CM Enterprise Workbench (ew.war) can be done through the Tomcat manager application.
Additionally the following files must be removed (deleted) from the Tomcat folder location: <Tomcat Root Folder >\shared\lib\
Also, the Tomcat working cache folder for \ew should be manually deleted if it exists. The location of the working Tomcat cache is: <Tomcat Root Folder>\work\Catalina\localhost\ew
JBoss: Removing the previous version of CA CM Enterprise Workbench from under JBoss requires the following steps:
IBM WebSphere Application Server: Use the WebSphere Administrative Console to stop and uninstall the Enterprise Change Manager Application prior to upgrading to r12. Remember to save the master configuration after installating CA CM Enterprise Workbench. You may need to recycle WebSphere prior to deploying r12 version of CA CM Enterprise Workbench.
The Define Data Sources and Deployment Tool (hereafter referred to as the Admin Tool) has the following known error conditions:
CA SCM Brokers Page: If you are creating a CA Software Change Manager (Harvest) configuration for the first time, the CA SCM Brokers page will display one‑character text fields. The following actions must be performed to work around this condition:
The one-character fields are now displayed as multi-character fields and can be filled in with data values.
Removing Existing Configurations: The following actions affect the CA SCM Brokers and CA Endevor SCM Hosts pages. Existing configurations can be removed by selecting the configuration file name and pressing the Remove button. If you want to remove all configuration files (for example, if you want to remove Harvest functionality from CA CM Enterprise Workbench) removing the last configuration file requires an extra step. To remove all the configurations, perform the following actions:
All configuration files up to the last configuration file are removed.
The final configuration file is removed.
The CA CM Enterprise Workbench DB Setup Tool creates a set of database tables, indexes, users, and required tablespace –collectively known as the CA CM Enterprise Workbench starter database. For users of Microsoft SQL Server, the DB Setup Tool installs the CA-MDB, a set of application database tables supplied by CA, which is invoked as required by the installation of the supported application.
For Ingres users, the tool offers a migration utility to export CA CM Enterprise Workbench data from Ingres to either Oracle or Microsoft SQL Server databases. For CA CM Enterprise Workbench r12, there are a couple of different ways to perform a database upgrade with Ingres migration; however, because of the variability of database installations we recommend the following process:
Install DB support for the target database (Oracle or SQL Server):
Migrate Data from Ingres:
The database migration process should have completed successfully. For more information about upgrade installations, see the Release Notes and the CA CM Enterprise Workbench Implementation Guide . After database migration has completed successfully, you can continue with upgrading CA CM Enterprise Workbench from r7.1 to r12.
Certain conditions reported as errors in the DB Setup Tool's log file are not necessarily fatal conditions. During the various operations performed by the DB Setup Tool error logs are created, displayed, and optionally saved. Occasionally, an error condition reported by the DB Setup Tool is not a true error, but merely the result of 'top-down execution' of the SQL language. The language does not contain procedural constructs, or flow-of-control statements, so false error reports are possible.
Example: DB Setup Tool Error Log - False Error
This error log displays the SQL language action and the result generated. The tablespace 'DBO' already exists, so it cannot be created again. This is not an error.
CREATE TABLESPACE DBO DATAFILE 'DBO.ORA' SIZE 8M AUTOEXTEND ON ERROR at line 1: ORA-01543: tablespace 'DBO' already exists
When reviewing the DB Setup Tool log file, you may want to consult your site DBA or CA CM Enterprise Workbench technical support, if you encounter error outputs that are questionable.
Sites using the Oracle database as a back end to CA CM Enterprise Workbench require Oracle client software to be installed on the CA CM Enterprise Workbench server. The Oracle client software supports both the DB Setup Tool and Enterprise Reporting.
The Oracle tnsnames.ora file contains client side network configuration parameters. It can be found in the ORACLE_HOME/network/admin/ folder on the client. This file is also present on the server if client style connections are used on the Oracle server.
In a tnsnames.ora file, connection information for an Oracle service is associated with an alias, or Oracle net service name. This alias (Oracle net service name) is a required input during database setup activities and during Installshield installation of Enterprise Reporting.
See the tnsnames.ora file (which can be read by a text editor) to determine the correct Oracle net service name syntax when installing Enterprise Reporting or using the DB Setup Tool.
Sites that electronically download the product receive the electronic download as an ISO file. This file can be burned onto a CD, mounted onto a network file system or de-archived onto a local or network drive. Additionally, the physical CD-image can also be copied to a local or network drive and the install.exe program invoked from the Windows Explorer.
In each of these cases, the site must mount or copy the installation image onto a root drive letter or short folder name path. The folder name path cannot have any 'white space' between the folder names.
Example: Copy CD Command
This is a valid Copy CD command to copy the contents from a physical CD to a folder path:
Copy CD *.* <drive-letter>:\CMEWr12\*.*
Example: Mounting points
This is a valid example of Mount drive command:
Mount drive: <drive-letter>:\ CA Change Manager Enterprise Workbench r12 GA Candidate.iso
The Define Data Sources and Deployment Tool (referred to as the Admin Tool) can operate in a command line mode to create and deploy WAR files.
To perform a command line deployment using the Admin Tool the following must occur:
Note: The comment, denoted by ! and shown in (), is not part of the file contents.
Type=DeployFile name=deploy ServerType=Tomcat ServerHomeDirectory=C:\\Program Files\\Apache Software Foundation\\Tomcat 5.5 !(This is the explicit path to the root of the web-container) EwContextRoot=ew SharedFilesRequired=Y EWwebapps=Y EclipseService=N CmewService=N
Note: The Y or N character in the last three tags indicate the WAR files to deploy. (EWwebapps is the CMEW WAR file.)
Note: Comments, denoted by ! and shown in (), are not part of the file contents.
#/n #Mon Jun 15 13:03:38 EDT 2009 CONFIG_PATH=C\:\\Program Files\\CA\\CA CM Enterprise Workbench\\ew\\WEB-INF\\classes !(This is the installation path [%EW_HOME%\ew\WEB-INF\classes]) DBUSER= EwContextRoot=ew ServerHomeDirectory=C\:\\\\Program Files\\\\Apache Software Foundation\\\\Tomcat 5.5 !(This is the root of the web-container) EWwebapps=Y CMEW_HOME=C\:\\Program Files\\CA\\CA CM Enterprise Workbench !(This is %EW_HOME%) ServerType=Tomcat EclipseService=N PRODUCT_WORKING_PATH=C\:\\\\Program Files\\\\CA\\\\CA CM Enterprise Workbench\\\\Files !(This is %EW_HOME%\files\) SharedFilesRequired=Y DBPASSWORD= CmewService=N
Contact Technical Support
For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At http://ca.com/support, you can access the following:
Provide Feedback
If you have comments or questions about CA product documentation, you can send a message to techpubs@ca.com.
If you would like to provide feedback about CA product documentation, complete our short customer survey, which is also available on the CA Support website, found at http://ca.com/docs.