Documentation Changes
The following documentation updates have been made since the eighth edition of this documentation:
The following documentation updates have been made since the seventh edition of this documentation:
The following documentation updates have been made since the sixth edition of this documentation:
The following documentation updates have been made since the fifth edition of this documentation:
The following documentation updates have been made since the fourth edition of this documentation:
The following documentation updates have been made since the third edition of this documentation:
Legal Notices—Updated to reflect public documentation legal disclaimer.
How the Installation Process Works:
Install CA Chorus and Java Home Directory—Noted a change in Service Release support. Version 3.0 now supports IBM 64-bit SDK for z/OS, Java Technology Edition, Version 7 Release 0 Modification 0 Service Release 2 or 5 (5655-W44), including optional JZOS batch launcher. Support for Service Release 5 is new.
Install CA Chorus and Install CA Chorus Disciplines—Added a stop sign warning to remind you to read the Site Preparation Guide before starting the installation.
Deploying Your Product—Clarified that you must configure all installed disciplines. Deployment is recommended but optional.
Deploy CA Chorus and Disciplines with CA Chorus Software Manager
Deploy CA Chorus and Disciplines Manually—Simplified the procedure such that two jobs manage the majority of the deployment tasks. (Requires RO63417)
Configuring Your Product—Clarified that you must configure all installed disciplines. Deployment is recommended but optional.
Configuring Your Product Using CA CSM—Clarified the reconfiguration options in step 2.
Submit CA Chorus and Discipline Jobs (Auto Config)
Seeding Data to Multiple TSF Regions—Removed incorrect reference to TSFSUFFIX default in step 2.
The following documentation updates have been made since the second edition of this documentation:
Configure Your Product Automatically (Auto Config)—Clarified the outcome of step 4. The first paragraph more clearly explains where the new customized data sets reside.
The following documentation updates have been made since the first edition of this documentation:
Installation Use Cases—Clarified the upgrade case.
Deploy CA Chorus and Disciplines Manually—Deleted repetitive mount information from the note in the CA Chorus for Security and Compliance Management steps.
Submit CA Chorus and Discipline Jobs—Updated the CA Chorus for DB2 Database Management job submission information to add an optional step for overriding the DB2 execution mode and to add a warning about starting JBoss during an upgrade.
Verify the Installation and Configuration—Clarified the URL so it includes /Chorus and streamlined the steps to make the URL a trusted site.
Override the DB2 Execution Mode—Added this optional step to the CA Chorus for DB2 Database Management manual configuration tasks.
The following documentation updates have been made since the last release of this documentation:
Global—Changed the following references:
Prerequisites and security procedures—Moved this information to the Site Preparation Guide because the work must or can be completed prior to the day of the installation.
How the Installation Process Works
Launch CA Chorus Software Manager—Added this new section.
Installation Use Cases—Added this new section.
Install CA Chorus Disciplines—Added this new section.
Install CA Chorus Maintenance—Clarified the steps, listed the FMIDs, and updated the reference information.
Upgrading Your Product—Moved this scenario to a standalone Upgrade Guide.
Deploy CA Chorus and Disciplines with CA Chorus Software Manager
Deploy CA Chorus and Disciplines Manually
Configure Your Product Using CA Chorus Software Manager—Added this new section.
Configure Your Product Automatically—Added this new section.
Post-Installation Considerations—Updated this section for discipline activities.
Verify the Installation and Configuration—Clarified the httpconnectorport definition.
USS Directories—Removed tpv as an option.
Set Port Assignments Manually—Removed ports that apply to Release 2.5 or sooner.
Not Enough Sort Space for CA Datacom/AD—Removed reference to CHDB002, which is no longer valid.
Not Enough Heap Memory—Updated the -Xms and -Xmx values in the workaround steps.
Cannot find a free port JBoss usage—Removed this topic because it does not apply to Version 3.0.
Djboss.remoting.start.portrange—Removed this option because it does not apply to Version 3.0.
CA Chorus Installation Worksheet—Moved this chapter to this guide.
JBoss Environment Variables (ENVETJ) and Ports
Java Home Directory—Updated the Java version requirement for 3.0.
JAVALIB—Added a description and the default for this installation directory.
Additional CA Chorus for DB2 Database Management Configuration—Added this new section.
Additional CA Chorus for Storage Management Configuration—Added this new section.
Not Enough Sort Space for CA Datacom/AD—Removed this topic because it does not apply to Version 3.0.
JBoss Startup Fails Due to Missing File—Added this new section, which explains how to use the FIXLINK job.
Added the topic to use FIXLINKS in JBoss Startup Fails Due to Missing File.
Additional CA Chorus for DB2 Database Management Configuration—Added this new section.
Additional CA Chorus for Storage Management Configuration—Added this new section.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|