DCA 2.01 is not simply an update to DCA 1.0 -- it is a separate application based on a different architecture. DCA 2.01 uses different mechanisms for session creation, page sharing, and other core functionality.
Due to DCA 2.01's more advanced feature set, its hardware requirements and performance specifications are different than those for DCA 1.0. You cannot install DCA 2.01 over DCA 1.0.
If you are a DCA 1.0 user upgrading DCA 2.01, perform these steps prior to installing DCA 2.01:
1. |
Inventory DCA 1.0 settings and customization There is no automated way to port settings and customization from your DCA 1.0 server to DCA 2.01. Therefore, you should take an inventory of settings and customization you introduced to DCA 1.0, and decide which, if any, you will want to re-create on your DCA 2.01 server. Under no circumstances should DCA 2.01 properties files simply be overwritten with files from 1.0. Note that the following DCA 1.0 customization features have been deprecated in DCA 2.01. In 2.01, the behaviors available through these features can be achieved through parser customization.
|
2. |
Uninstall DCA 1.0 DCA 2.01 cannot be installed over DCA 1.0. If you plan to install DCA 2.01 on a machine on which DCA 1.0 was previously installed, you must first uninstall DCA 1.0. To ensure that DCA 1.0 uninstalls cleanly, be careful to follow the uninstall instructions included in your DCA 1.0 documentation. You should also delete the DCA 1.0 alias for the DCA Admin Tool defined in your Web Server software. |
3. |
Remove DCA 1.0 URL formatting from CCS scripts For DCA 1.0, your company may have modified URLs in the Collaboration Server Agent Desktop Script area to point to the DCA. Because the DCA 2.01 uses a different, automatically imposed, URL format, DCA modifications made to URLs in the CCS Script area must be removed. (URLs modified for DCA 1.0 used this format: http://<DCAservername>/DCA?url=http://<URL>&WLSession=<sessionID>.) |
4. |
Remove DCA 1.0 code from the CCS Screen Pop configuration For DCA 1.0, your company may have added code to the Collaboration Server Screen Pop file (screenpop.jhtml) that served to create DCA sessions at the start of a CCS session. This code is not needed for DCA 2.01 and should be removed if it exists. |
See Also
For related information, see:
About DCA Hardware Requirements
The DCA 2.01 Administration and Configuration Guide
The DCA 1.0 Installation and Configuration Guide