This file contains information on installing and using the current release of Serena® Collage®. For a list of the defects fixed since the last release of Collage, see release_notes.enUS.html.
To view the Master License Agreement, see MasterLicenseAgreement.pdf.
To contact Serena Online Services, go to support.serena.com.
IMPORTANT:
If you are upgrading from a previous version, review the Supported Platforms section to verify support of your existing environment.
The following changes should be noted by all customers:
AIX is no longer supported as an operating system for the Collage server.
The Microsoft Java Virtual Machine is no longer supported. The Sun Java Virtual Machine plug-in is used instead.
Netscape Navigator is no longer supported.
The Firefox browser is supported only for the Collage Contributor client, not the Collage Classic client. The Collage Classic client is supported only on Windows platforms with Internet Explorer. Administration tasks can be performed only in Collage Classic.
Collage is now available on DVD, not CD-ROM. It is also available for download.
Collage Contributor is a simplified Web-based interface that allows you to easily contribute files to a Web site. The Collage Contributor Home Page provides easy access to all the tasks and files you are working on as well as assistants that simplify tasks through the use of customizable workflows.
Performance during the loading of folder trees in Collage has been improved using AJAX technology. Tree nodes are loaded on demand, drastically reducing initial render time.
The following changes were made in order to reduce the amount of time it takes to run a deployment:
Improved binary data cache that retains contents across server restarts.
Document conversions upon check-in rather than during the deploy operation. Converted documents are stored in binary data cache.
Caching of commonly used information to decrease page generation time.
When you set up a deploy web server, you can now choose to transfer files using any of the following options:
Local file system
FTP server
FTP over SSL server
Secure FTP server (SSH/Secure Copy)
Fixed UI performance problems that occurred when editing large deploy maps.
Improved reporting of errors in the activity and server logs.
Enhanced deploy activity log that summarizes deploy settings, generation times, and transfer times.
In the Preferences dialog box, you can now set up text files such as HTML, ASP, JSP, or plain text files to be editable using the Collage contribution editor.
In the content contribution DDF file, you can now choose to make all code generated by the Collage Editor XHTML-compliant.
The spell checker in the Collage contribution editor is now a server side function. As a result, Microsoft Word is no longer required for spell checking, and spell checking is supported for all supported browsers.
The Content Contribution screen now allows you to edit a global DDF file that can be used by other DDF files. This allows you to set up reusable content, styles, fonts, font colors, font sizes, and accessibility options in one place.
The DDF file can now be configured to use CSS styles.
Image fields can now be configured to require an ALT attribute.
Rich text fields can be configured to require the Summary attribute and relative sizing on tables.
Other accessibility tags can be defined, such as Abbreviation, Acronym, and Citation.
Contribution fields can now be flagged as required.
New formatting options include:
Merging cells
Applying formatting across multiple cells
Ability to add and delete multiple rows and columns
The Collage contribution editor now allows you to edit existing external links.
E-mail messages sent after a deploy has finished or when a task is transitioned can now be customized. For details, see KnowledgeBase article KB5002120 for deploy e-mail and KB5002121 for task e-mail messages on Serena Online Services.
You can now set up a simplified masterpage to enable previews to load faster. Once you've created the simplified masterpage, you can assign it to the original masterpage. Preview operations for pages that use the original masterpage will then use the simplified masterpage, while deploys will continue to use the original masterpage. For details on setting up the preview masterpage, see KnowledgeBase article KB5002115 on Serena Online Services.
For single sign-on environments, Collage can be configured to authenticate against a Windows NT domain. For details, see KnowledgeBase article KB5001032 on Serena Online Services.
The integration with Collage allows for the following functionality:
Kick off Collage Task from within TeamTrack.
Monitor the progress of the Collage Task from TeamTrack.
Serena Collage 5.1 provides support for updated versions of several platforms. For details, refer to the section on Supported Platforms for more information.
The components of this Collage release are supported on the platforms listed below.
Microsoft Windows 2003 Server, Enterprise Edition (64bit)
Microsoft Windows 2003 Server, Enterprise Edition
Microsoft Windows 2003 Server, Standard Edition
Microsoft Windows XP Professional
Microsoft Windows 2000 Server, Advanced
Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional
Sun Solaris 9 (64bit)
Sun Solaris 9
Sun Solaris 8 (64bit)
Sun Solaris 8
108652-40
108921-13
108940-33
Red Hat Linux 8
Install must include the following package: compat-libstdc++-7.3-2.96.110
Red Hat Linux AS4 for use with Oracle and Microsoft SQL databases only
Processor
Windows: Pentium III, 500 MHz
Solaris: Sparc, 333 MHz
Red Hat Linux: Pentium III, 500 MHz
RAM (All platforms)
Single server installation: 1 GB minimum (2 GB recommended)
Collage Server only: 500 MB minimum (1 GB recommended)
Bundled Sybase database server only: 500 MB minimum (1 GB recommended)
Collage Server and bundled Sybase server: 1 GB minimum (2 GB recommended)
Disk Space (All platforms)
Collage Server only: 150 MB
Bundled Sybase database server only: 100 MB
Collage Server and bundled Sybase server: 200 MB
DVD-ROM Drive (All platforms)
Monitor Screen Resolution
Windows: 1024x768 with 256 colors
Solaris: X virtual frame buffer (Xvfb)
Temporary hard drive space: 100 MB
Collage Classic is supported on:
Windows 2000
Windows XP
Collage Contributor is supported on:
Windows 2000
Windows XP
Apple Macintosh OS X Tiger 10.4
Windows:
Pentium III
32 MB of RAM (64 MB recommended)
Monitor screen resolution of 1024x768 with 256 colors
100 MB hard disk
Macintosh:
Monitor screen resolution of 1024x768 with 256 colors
For Collage Classic, use the following browser on Windows and Macintosh:
Microsoft Internet Explorer 6.0
Firefox 1.5.0.x
For Collage Contributor, use one of the following browsers on Windows and Macintosh:
Microsoft Internet Explorer 6.0
Firefox 1.0.6 and 1.5.0.x
IMPORTANT! Pop-up blocker browser plug-ins may cause issues with the Collage Web clients. For best results, disable any pop-up blockers before using the Web clients.
Sun 1.5.0_04
Sun 1.4.2_07
Sun 1.4.2_06
Sun 1.4.2_05
The Serena Collage DVD includes version 1.5.0_04 of the Sun Java Runtime Environment (JRE). Install this version of the Sun JRE if you want to use the Sun JVM plug-in with Microsoft Internet Explorer.
You can find the installer under the JRE directory on the Collage DVD.
With Collage Enterprise edition, the Deploy Agent is supported on the following platforms:
Microsoft Windows 2003 Server, Enterprise Edition
Microsoft Windows 2003 Server, Standard Edition
Microsoft Windows XP Professional
Microsoft Windows 2000 Server, Advanced
Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional
Sun Solaris 9 (64bit)
Sun Solaris 9
Sun Solaris 8 (64bit)
Sun Solaris 8
Red Hat Linux 8
compat-libstdc++-7.3-2.96.110
Hewlett Packard HP-UX 11.11 (64bit)
Hewlett Packard HP-UX 11.11
IBM AIX 5.2
IBM AIX 5.1 (maintenance level 3, 5100-03)
Processor
Windows: Pentium III, 500 MHz
Solaris: Sparc, 333 MHz
Red Hat Linux: Pentium III, 500 MHz
HP-UX: PA-RISC
AIX: PowerPC POWER3
RAM
DVD drive
100 MB hard drive space
You can use any of the following database servers with Collage to host your Admin database and project databases.
Sybase Adaptive Anywhere Server 8.0.2
Oracle 9i Release 2
Oracle 10g Release 2
Microsoft SQL Server 2000
IMPORTANT!
Case-sensitive collation of databases is not supported.
The use of Web servers with Collage are supported as follows:
The following Application servers are supported with Collage:
The following FTP servers are supported for use with Collage:
WU-FTP 2.6.2 on Linux
IIS FTP service alias Windows FTP service
Built-in FTP server on supported Solaris platforms
ServU FTP over SSL 5.x
Open SSH
VSFTPD (SSH)
Collage supports SMTP as its mail server.
Collage supports the following directory servers:
Microsoft Active Directory (2003)
Microsoft Active Directory (2000)
Sun Java System Directory Server 5.2
Novell e-Directory 8.7.3
Collage integrates with the following products:
Contribute 3
Dreamweaver MX
Dreamweaver 4.0
Microsoft Word
Microsoft Excel
Microsoft PowerPoint
Dreamweaver
Windows Web Folders
Dreamweaver
Serena TeamTrack 6.3 (requires XML Bridge 2.0 and Serena License Manager 2.1.1)
Serena Version Manager 8.1
Serena Dimensions 9.1.2
NOTE:
For information on the integration with TeamTrack, see the Serena Collage Integration with Serena TeamTrack document that accompanies Collage.
For information on the integration with Version Manager, see the Serena ChangeMan Version Manager Administrator's Guide on the Version Manager CD-ROM.
For information on the integration with Dimensions, see the Serena ChangeMan Dimensions/Serena Collage Integration Guide on the Dimensions Documentation CD-ROM.
Consider the following important information about upgrading previous versions of Collage:
For Collage 3.0 or 3.1, perform a full installation of the 4.0 release of Collage and load your projects in the new installation. Then complete the steps in the next bullet.
For Collage 4.0, 4.0.1, or 4.5.0.x, perform a full installation of the 4.5.1 release of Collage and load your projects in the new installation. Then complete the steps in the next bullet.
For Collage 4.5.1 and later, you can perform an upgrade installation.
For detailed information on installing Collage, see the Serena Collage Installation and Setup Guide.
For instructions on upgrading Collage installations running on BEA WebLogic or IBM WebSphere, see Upgrading Collage on IBM WebSphere and BEA WebLogic (Collage WS BEA Upgrade.pdf) located in the documentation installation directory on the Collage server, and downloadable from the Serena Support Website.
If you initially install an evaluation copy of Collage and then enter a license key to update it to a full version, you must restart the Collage server after you enter the new license key. If you do not restart the Collage server, the FTP integration to Collage will not be properly updated to allow the correct number of users, as determined by your license.
The Sybase database icon may remain in the Windows system tray after installation is complete. In this case, Sybase has actually shut down, but the icon remains visible. To remove the icon from the system tray, simply pass your mouse over the top of it.
With UNIX installations of Collage, if you upgraded from version 4.0.1 and chose the French or German option from the login screen, you may see a mix of English and localized text in the UI. To fix this problem, do the following:
clientres_de.properties
clientres_fr.properties
When you upgrade an installation of Collage on Linux using the bundled Sybase DB platform, the port number that was previously assigned to Tomcat is lost. The Collage server therefore will not start correctly.
To fix this issue:
Do not add files to Collage that include commas (,) or plus signs (+) in their names. Errors may occur when you attempt to check in, check out, preview, or display source code for assets with commas or plus signs in their names.
Do not create asset type names that include commas (,). This causes problems when you create new files using an assistant in Collage Contributor.
When creating contribution document types, use Western European characters only (ISO 8859-1 character encoding) to name them. Though Collage may appear to successfully create document types that are named using other characters, such as Asian characters, errors may result.
By default, layout and master pages use the ISO-8859-1 character set. If you want to use a different character set, add the correct <META> tag to the <head> section of the master page:
Where character set is the correct character set.
NOTE The suggested character set is "UTF-8", which supports all languages at the same time.
The characters listed below cannot be used in group or user names. Even when using LDAP security, these characters may cause problems:
Slashes: \ /
Asterisk: *
Double quote: "
Single quote: '
Question mark: ?
Pipe: |
Angle brackets: < >
Dollar sign: $
Non-ASCII characters, such as Cyrillic and Greek characters, are not supported for asset names in Collage.
Collage allows you to use non-ASCII characters when naming projects and folders. However, because browsers do not universally support non-ASCII characters in URLs, Collage converts any non-ASCII characters in file references to ASCII escape characters. For example, you can create a folder with the following characters in its name:
öä
If you then create references to files in the folder, Collage will convert these characters to encoded ASCII characters, such as: %F6%E4. For example, <img src="öä/image.gif"> will be encoded to be <img src="%F6%E4/image.gif">. To avoid such URL and path conversion, do not include non-ASCII characters in folder or project names.
If you attempt to copy a project that includes metadata fields with non-Western European characters (such as Asian characters) in their names, the copy may fail. To ensure that you can successfully copy projects with non-Western European metadata field names, first rename the metadata fields using Western European characters, copy the project, then restore the characters in the new, copied project.
Dynamic Web pages, such as Java Server Pages (JSPs), may not preview correctly with the Tomcat application server, which is the default application server. Tomcat generates URLs for dynamic pages when it compiles them. If the URL exceeds 255 characters, preview will fail and a File Download dialog box will appear instead.
Backing up the Admin database or projects running on a Windows Oracle server causes resource leaks. These leaks can eventually cause Oracle to run out of resources and crash. Use Oracle's backup facilities instead.
From a Macintosh OS X client, you can establish an FTP connection to a Collage Server, which allows you to check out and edit assets from editor applications that support FTP. To do this, simply enter ftp://machine name:port in your browser.
However, note that once you have established an FTP connection, the connection is not closed until you restart the Macintosh client.
If you purchased the bundled Sybase database server, do not use the words "date" or "time" as your project name, database owner usernames or passwords.
Collage includes a system group called Administrators, to which all system permissions are granted. If you use LDAP to supply user information to Collage, and your LDAP server also includes a group called Administrators, any user who belongs to the LDAP Administrators group is granted all system permissions in Collage, by default. You can modify system permissions for each user, as needed, if you do not want to grant all system permissions to all members of the LDAP Administrators group.
If you use LDAP to manage your users and groups, users must log into Collage at least once before they can successfully receive task notifications via email. Once they have logged into Collage the first time, using their LDAP usernames, their email addresses are registered in Collage and they will always receive their task notifications.
You cannot currently export audit logs from the System | Audit Log view when Collage is running on the IBM WebSphere server platform.
In the Collage contribution editor, creating links from text that contains French accents changes the accents to invalid double-byte characters. This occurs when Collage is running on WebSphere and Solaris.
You can apply master pages to most types of Microsoft Office files, including Microsoft Word and Excel files. When you deploy the files, if Office and GhostScript are installed to the Server, Collage will convert the files to HTML and apply the master pages to them.
However, because Microsoft PowerPoint files (.PPT) are saved to multiple HTML files when they are converted, you cannot apply master pages to them.
An error may appear if you attempt to preview a page while working in context of an open task, if that page has a master page associated with it that is not approved. If this error occurs, approve the associated master page.
Note that all users, while working in context of an open task, can delete assets that are associated with that task, so long as the assets are not yet approved. To prevent contributors from accidentally deleting assets, you can set asset permissions appropriately.
When you delete a project, Collage does not automatically delete the associated project cache. This may cause cache issues if you try to restore the project or migrate the project to a different server. To avoid these issues, delete the project cache (/cmsessions/blobcache/project_name).
In the Collage contribution editor, when you use the table cell merge above/below functionality, the visual results can look different than expected. This can happen if you merge cells that span one or more columns. This occurs because the position of the cell in the row where the merge is started is different from the position of the cells that appear to be located above or below this cell.
In the Source view of the Collage contribution editor, links that contain "&" get replaced by "&" each time that you save the file. This can cause the links to be invalid.
This issue only occurs if the Convert to XHTML option is set in the DDF.
In the Source view of the Collage contribution editor, ASP and JSP code gets changed when you save the file. The opening script tag (<% or <?) gets stripped out, or is replaced by <% or <?.
This issue occurs only if the Convert to XHTML option is set in the DDF file.
The Collage spell checker includes a Locale2LexiconMapping.xml file, located in install directory/sql/lex, that maps locales to the appropriate language dictionary. If the country code for a locale doesn't exist in the mapping file, the first entry that contains the appropriate language is used. For example, if you are spell checking Australian English (enAU), the UK dictionary is used, as this is the first entry in the mapping file that contains the English language.
You can move the entries in this mapping file so that your desired language dictionary is used for country codes that aren't in the file. For example, you can move the enUS entry to the top of the "en" languages. In this case, if spell checking Australian English, the American English dictionary would be used.
When you access Solaris or Red Hat Linux installations of Collage with Microsoft Internet Explorer on Windows, Internet Explorer may hang. This occurs because, by default, Internet Explorer does not support more than two connections at a time to any server that uses HTTP version 1.1. Solaris and Red Hat Linux installations of the Collage Server use HTTP version 1.1, and the Collage client uses multiple frames, each of which may connect concurrently to the Collage Server.
To resolve this issue, update the Windows registry setting on each client machine to allow Internet Explorer to use more than two HTTP 1.1 connections at a time. To make this change, add a registry key in HKEY_CURRENT_USER\Software\Microsoft\Windows\ CurrentVersion\Internet Settings called MaxConnectionsPerServer and give it a value of 00000004.
A .reg file to help automate this process is available in KnowledgeBase article KB70176, accessible on Serena Online Services.
For more information on this Internet Explorer limitation, see http://support.microsoft.com/default.aspx?scid=kb;en-us;279745.
On Windows 2000 client machines, new HTML files created in Collage Contributor are opened with Internet Explorer if IE is set as your default browser. To open new HTML files with a different application, you must explicitly specify the application as the content editor for the HTML file type, under Collage preferences. Setting the content editor to "default application" still results in new HTML files opening in IE.
With Windows XP SP2, the following security warning may appear when working in Collage:
To allow access to popup menus, add the Collage host name to the list of trusted sites in Internet Explorer (Tools | Internet Options | Security | Trusted Sites).
When you upgrade to Windows XP Service Pack 2, default security settings are changed. These changes can cause messages to appear that prompt you to explicitly allow the Help system to be viewed.
To allow the Help system to be viewed without seeing warnings, perform the following steps.
There is a defect in the implementation of the Java Runtime Environment on Macintosh clients that can cause editing, checking in, and checking out assets to fail intermittently. When this problem occurs, close the Firefox browser and reopen it.
When you deploy contribution documents to a database, the contents from those documents are typically stored in a database column that is named after the content field. For example, if a content field called Body is deployed to a database, content from this field is stored in a database column called Body.
However, if any of the content field names are reserved SQL words (such as Date or Time), an underscore is appended to the end of the field name, when creating the corresponding database column. For example, content from a content field called Date will be stored in a database column called Date_.
The incremental deployment feature, which allows you to deploy only changed files, attempts to remove any files from the target servers that have been deleted or moved from the corresponding deploy folder in Collage, including files that are only deployed if referenced by another file. However, this may fail on Solaris if the Timezone environment variable for the Tomcat server is not set to a valid value.
The Timezone environment variable for the Tomcat server is set to a null value, by default, in UNIX installations of Collage. This may result in incorrect timestamps resulting from shifts in time that the server is unaware of, such as Daylight Savings.
For details on how to set the correct timezone, including a complete list of possible timezone values, see the Serena Online Services KnowledgeBase article KB54463.
If a Microsoft Office document is converted to either HTML, PDF, or PS, the converted documents are deployed successfully using incremental deploy, but the source document is not deployed. In this situation, the source documents can be deployed using single asset, folder, or full deployments. If the Microsoft Office document is not converted, the source document will deploy successfully during an incremental deploy.
This issue occurs when you have an AssetQuery page with a link to a Microsoft Office document. If you change the convert option for a Microsoft Office document, and then perform an incremental deploy, the AssetQuery page is not redeployed, causing the link to the document to be incorrect. To fix the issue, you must deploy the AssetQuery page or do a full deployment. After that, you can perform incremental deploys.
On Windows, files are not deployed to the backup directory specified in the deploy map. The folders are created in the backup directory but the files are not created.
Deployment to SFTP servers is not supported when deploying in ASCII text mode from Windows Collage servers to UNIX targets, or from UNIX Collage servers to Windows targets.
The Language and Regional Display and Automatically Open Project options in the Preferences dialog box do not work as intended. You can set these preferences in the following places instead:
Language and Regional Display: Login page
Automatically Open Project: Select Your Project page
When you set the date and time fields throughout Collage Contributor, the order of the fields (month, day, and year) may not reflect the locale that you selected on the Login page. Additionally, the calendar control may not display the correct day for the beginning of the week for your locale.
If a dollar sign ($) is present in the description of a file, the Edit File dialog box does not appear when you click the file name beneath Files I'm Working On. To edit the file, click the Browse Files button, locate and select the file, and click the Edit link.
When you add a file using the Existing File option, Collage should choose the appropriate assistant based on the file type. Instead, the default assistant is used. This can cause an error when uploading the file, as Collage attempts to create a new task for the file.
When you start an advanced search in Collage Contributor, using the Firefox browser, you may encounter the following error message:
A script on this page may be busy, it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
Firefox displays this error when a script takes longer to load than is allowed by a specific browser setting. To avoid seeing this error:
about:config in the Firefox address bar.
dom.max_script_run_time
Macromedia Dreamweaver 4 does not support the UTF-8 character set, which is the recommended character set for contribution layout pages. If you check in layout files that are not correctly UTF-8 encoded, the layout files may be truncated, which can result in data loss. If you are using Dreamweaver 4 to edit CCS layout pages, you must convert the html file to UTF-8 before checking it in to Collage. You can use Windows Notepad to convert files to UTF-8 by choosing File | Save As and specifying the UTF-8 character set.
To edit Collage assets via the Web Development and Versioning (WebDAV) interface, Macromedia Dreamweaver MX and UltraDev must connect to the Collage Server using an HTTP version 1.0 port. Because the Tomcat application server that is included with Collage no longer uses HTTP version 1.0 for Solaris or Linux, the HTTP 1.0 connection is provided via a separate port rather than the main Tomcat port. For Windows this is not an issue since the HTTP 1.0 port is enabled by default.
By default, this port number is 8083. This port is automatically activated when you start the Collage Server on Solaris or Linux. You may need to update your Dreamweaver WebDAV connection settings to specify this port number. For example, set it to: http://Collage:8083/servlet/nexus/dav.
If for any reason you need to change the port number that Collage uses for the HTTP 1.0 connection, complete the following steps, in addition to setting the correct port number in Dreamweaver:
NOTE: WebSphere does not provide an HTTP 1.0 port. To use Dreamweaver/UltraDev and WebDAV with Collage in one a WebSphere installation, you need to set up a Tomcat server as described above.
When you access Contribute's Preview in Browser feature, you may see the following error:
An error occurred. Please contact your administrator.
This error will occur if you do not have the following asset permissions granted on the folder that contains the page:
Modify
Create Folder
Create Asset
Delete Folder
Delete Asset
To preview the page without these permissions, you can preview from Contribute's built-in browser.
When you delete a file from Contribute, Contribute attempts to create a copy of the deleted file and a design notes file (.mno). This causes errors in the Collage server log. To prevent this from happening, make sure that the Contribute option Remove rollback versions on delete is selected on the Edit Role Name Settings dialog box (Folder/File Access category).
When you try to delete a file from Contribute that is referenced by other files, the deletion fails, and no error is displayed in Contribute. The Collage server log displays the error:
To delete the file, use Collage instead.
In the Contribute Insert Link dialog box, when you manually type the file name of an asset located in the same folder (or a lower folder) as the page you are editing, the link is automatically prefixed with http:// If you want to manually type the file name, prefix it with ./ For example:
Alternatively, you can browse to the file to which you want to create a link.
When you preview a page using Contribute's Preview in Browser feature, any links generated by the AssetQuery component will fail when you click them. You can preview the links using Contribute's built-in browser.
On Macintosh, any auto-generated images are not displayed when you edit a page. The images are displayed when you preview the page in Contribute's built-in browser.
In the Contribute File Placement Rule dialog box, do not select the Write links relative to the root of the website option. If this option is selected and new images are added to an HTML document, the paths to the new images are incorrect, resulting in broken images when deployed.
When working on a contribution document in Contribute, any new images that you create are not placed in the folder defined by the document definition file by default. The new images are placed in a folder called "images", which is created in the same folder as the contribution document you are editing. This default can be changed by updating the File Placement options for the Contribute user's role.
Contribute does not adhere to the Exposed folders setting for link and image fields in the document definition file. Contribute allows you to add links or images to or from any folders, even if the Exposed folders setting is restricted to contribution folders only.
If you have multiple connections enabled, and you switch home pages using the Home Page button in the Contribute toolbar, you may receive the following error:
To correct this problem, click the Refresh button in the Contribute toolbar.
You can preview pages using the Preview in Browser feature in Contribute. If you do this on a machine on which the Collage UI is currently open, Collage will switch to display the project to which the page belongs. To prevent this from happening, use a different browser to preview pages in Contribute than the browser that you use for Collage.
Enabling the Contribute integration changes the extension of existing contribution documents from .xml to .ccd. The extension of any contribution documents in the Recycle Bin does not change. If you restore the contribution documents from the Recycle Bin, you will not be able to work with them in Contribute.
In this situation, the restored assets will have to be manually updated to use the .ccd file extension. After changing the file extension, verify that the Asset Type and Mime-Type are correct for this contribution asset. After this change, the documents can be modified through Contribute.
On Solaris or Linux, if you will use any image effects or image generation features, such as the Navigation Bar component to generate image-based navigation buttons, see KnowledgeBase article KB70344, accessible on Serena Online Services.
The $node.url data field macro allows you to automatically generate a link from a Collage Component, such as the AssetQuery Component, to another asset. If the target asset is set to deploy as a PDF, using GhostScript, then the $node.url macro will refer to the PDF version. However, if the target asset has a period somewhere in the name and will be converted to PDF, then the link generated from $node.url may be incorrect. This may result in broken links in content that is generated from the Collage Components.
To ensure that no links to assets converted to PDF are broken, make sure that the target assets' filenames do not include periods. You can also replace the $node.url macro with $node.pdfurl, if you are certain that the links will be to converted PDF versions of the assets.
The WAR Filer Component, which you can use to automate the packaging and deployment of WebARchive (WAR) files, may fail to deploy the compiled WAR files. This failure occurs due to changes in the deployment features.
To ensure that WAR files successfully deploy, complete the following steps, in addition to the instructions provided in the collage_warfiler_component.pdf file. This file is available from Serena Online Services in KnowledgeBase article #70204.
The WAR file should now successfully deploy.
In the Components User's Guide, the AssetQuery section displays an incorrect example for the metafilter property. The guide states:
Greater than/less than or equal to statements (<= =>)
The correct example is:
Greater than/less than or equal to statements (<= >=)
The Web Services Getting Started Guide has not been updated for this release. The following corrections should be noted:
In the section "Importing the WSE", replace Microsoft.Web.Services.dll with Microsoft.Web.Services2.dll.
In step 5 of section "Setting Up Web Service Stub Files", replace Microsoft.Web.Services.WebServicesClientProtocol with Microsoft.Web.Services2.WebServicesClientProtocol.
The help link for the Select Your Project Page does not work. To access the help for this page, log in and click the Help link. On the Contents tab, navigate to Getting Started | How to Log Into a Project.
The TeamTrack Integration Guide incorrectly states that you should import the database schema from the file ttintegr_schema.xml. However, doing so results in the following error: "Wizard Error: Cannot import a TeamTrack solution."
To correct this issue, you should instead import the following file: ttintegr_schema_aux.xml.
The Components User's Guide incorrectly states that the AssetQuery component will only return assets that will be deployed. The AssetQuery component does not actually have this limitation.
The Components User's Guide lists invalid examples of data field macros. For example, for $type.assetid macros, the included usage examples are:
The asset that contains the component ($node.name)
The deploy map that was used to publish the asset ($publishmap.name)
The deploy folder that contains the asset ($parent.name)
Each of the above example macros is incorrect. They should be: $node.assetid, $publishmap.assetid, and $parent.assetid. The same errors appear in subsequent examples of other types of macro.
creator Macro Type
The Components User's Guide includes the following incorrect example usage of the creator data field macro type:
For example, to display the ID of the user who created the asset's deploy map:
$parent.creator
This example is incorrect. The macro should actually be:
$publishmap.creator
The Collage Installation and Setup Guide contains information on how to update properties in the nas.properties file. However, the following properties are missing from the nas.properties appendix:
The Project Manager's Guide does not explain how to restore a backup of a project database with Sybase or MS SQL database servers. You must complete these steps before you can load the database back into Collage.
The Collage Installation and Setup Guide does not explain how to install the Collage Agent on AIX.
To do this:
./agentSetupAIX
./agentSetupAIX -console
NOTE Unless you logged in as root, you must set the port number to a value greater than 1024. By default, the port number is 9999.
The following obsolete server properties are documented in Appendix A of the Collage Installation and Setup Guide:
clientTimerInterval
missedtimerKillFactor
These have been superceded by two new server properties, MaxInactivityTimeout and BrowserKeepAliveInterval. These properties are described in "Undocumented Properties from nas.properties File" on page 24.
Sun Technology Licensing Information
This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/.
Solaris: Collage Uses Public GNU Tool
Collage uses the GNU Ghostscript tool, which is protected under the GNU Public License. This license agreement states that you have the right to access the source code for this tool. The source code can be found online at the following location:
ftp://ftp.gnu.org/gnu/ghostscript/
End Readme
Copyright © 2005 Serena Software, Inc. All rights reserved.
$Revision: 1.1 $