Last updated March 6, 2007
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 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.
Collage is now available on DVD, not CD-ROM. It is also available for download.
All new (and upgraded) projects now include a file (AllowedFilterHTMLTags.xml) that specifies the specific HTML elements and attributes that contributors can enter when editing a document for which the Filter HTML setting is enabled. Contributors can save documents with any HTML elements and attributes that are explicitly listed in the AllowedFilterHTMLTags.xml file. Any elements and attributes that are not listed here are stripped out of documents, with the exception of HTML syntax that is allowed by the document definition file (DDF) for the document type.
For example, if <div> tags are not listed in the AllowedFilterHTMLTags.xml file, then they will be filtered out of all documents, by default. However, if the DDF for a particular document type is set to allow <div> tags, then contributors can add <div> tags to that type of document.
By default, the AllowedFilterHTMLTags.xml file is set up to filter exactly as previous versions had filtered. To customize the set of HTML elements and attributes allowed by default for documents for which Filter HTML is enabled:
/System /Internal Editor Setup
You can edit this file in any XML or text editor.
To identify HTML attributes that should always be allowed, add the attributes to the following element:
<AttributesAlwaysIncluded attributes="attribute1,attribute2"/>
Add the following element for each HTML tag (and attributes within those tags) you want to allow, under the <AllowedTags> element:
<AllowedTag name="name" attributes="attribute1,attribute2"/>
For example:
<AllowedTag name="img" attributes="src"/>
For more information, see Knowledgebase article 5005142, available from the Serena Support Website:
http://sos.serena.com/eSupport/Solutionshow.asp?solution_id=5005142
Collage is now available in French and German language editions.
Collage now supports the following:
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:
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 2000 Server, Advanced
Microsoft Windows 2000 Server
Sun Solaris 10 (64bit)
Sun Solaris 9 (64bit)
Red Hat Linux AS 4.0 (64bit)
Red Hat Linux 8
Processor
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
Temporary hard drive space: 100 MB
IMPORTANT! Over time, as your projects grow, your database server (any platform) will likely require much more hard drive space than the minimum listed here. We therefore recommend starting with as much free space as possible, to alleviate maintenance issues later on.
Windows:
Pentium III
32 MB of RAM (64 MB recommended)
Monitor screen resolution of 1024x768 with 256 colors
100 MB hard disk
Macintosh:
For Collage Classic, use one of the following browsers on Windows or Macintosh.
NOTE: You must enable ActiveX to using the Collage clients.
For Collage Contributor, use one of the following browsers on Windows and Macintosh.
NOTE: You must enable ActiveX to using the Collage clients.
NOTE: You will need the MSXML 4.0 SP2 plug-in.
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.
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 (64bit)
Microsoft Windows 2003 Server, Enterprise Edition
Microsoft Windows 2003 Server, Standard Edition
Microsoft Windows 2000 Server, Advanced
Microsoft Windows 2000 Server
Sun Solaris 10 (64bit)
Sun Solaris 9 (64bit)
Red Hat Linux 8 (Installation must include the following package: compat-libstdc++-7.3-2.96.110)
Red Hat Linux AS 4.0 (64bit)
Hewlett Packard HP-UX 11.11 and 11.23 (64bit)
IBM AIX 5.2L (64bit)
IBM AIX 5.3L (64bit)
Windows: Pentium III, 500 MHz
Solaris: Sparc, 333 MHz
Red Hat Linux: Pentium III, 500 MHz
HP-UX: PA-RISC
AIX: PowerPC POWER3
512 MB minimum total RAM, 1 GB recommended. Total RAM requirement for the system depends on the demands of the application or Web server installed to it.
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.3 (Not supported on Solaris 10)
Oracle 9.2.0.7
Oracle 10.2.0.2
Microsoft SQL Server 2000
Microsoft SQL Server 2005
IMPORTANT!
Case-sensitive collation of databases is not supported.
The following Web servers are supported with Collage:
NOTE: For details on setting up Collage with IIS, see KB article KB 5002288 at http://support.serena.com.
The following Application servers are supported with Collage:
IMPORTANT! In order to support changes to Daylight Savings Time (DST) in 2007, you must apply a patch to WebSphere 5.1. Please consult the following for more information:
http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21219396
IMPORTANT! In order to successfully install Collage to WebLogic, WebLogic must be running during installation.
IMPORTANT! In order to support changes to Daylight Savings Time (DST) in 2007, you must upgrade the Java installation on the WebLogic server. For critical information on this upgrade, please consult the following:
http://support.bea.com//support_news/Patch_for_2007_Daylight_Savings_Time_Changes.jsp
The following FTP servers are supported for use with Collage:
WU-FTP 2.6.2 on Linux
IIS 5.0, 6.0 FTP service alias Windows FTP service
Built-in FTP server on supported Solaris platforms
ServU FTP 6.3.0 over SSL
Open SSH 4.3 FTP
VSFTPD (SSH) 2.0.4
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:
Serena TeamTrack 6.6 (requires XML Bridge 2.0 and Serena License Manager 2.1.1)
Serena Version Manager 8.1.2, 8.1.3
Serena Dimensions 9.1.3
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.x, perform a full installation of the 4.6 release of Collage and load your projects to the new installation, Then, perform an upgrade installation.
For Collage 4.6 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.
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 database owner usernames or passwords.
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.
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.
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 Collage Classic, displaying a contribution folder that includes HTML elements in the description may result in a stack-trace error. This occurs when you log in as a different user than the user who created the the folder. You are then unable to access the contents of the contribution folder.
To avoid this issue, remove any HTML elements from the description field for contribution folders. From the Content | Search view, you can quickly find any contribution folders with descriptions that include HTML. Choose Description contains and enter an angle bracket character "<." Then, from the Type list, choose Contribution Folders.
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.
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:
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.
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:
To preview the page without these permissions, you can preview from Contribute's built-in browser.
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:
One or more assets being deleted are currently being used/referenced by other assets. Delete anyway?
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:
./myfile.htm
./myfolder/myfile.htm
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:
HTTP Status 500 Internal Error. Unknown Error Occurred.
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.
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.
Give the empty file the same name that you specified for the Web Application's Context Name property, in the component property settings (in the Project | Components view). The file must have the .war file extension.
Add or upload the empty file to the \WarContents deploy folder.
Approve the file.
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:
The correct example is:
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.
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.
Shut down Collage. For information on starting and stopping Collage, refer to the Serena Collage Installation and Setup Guide.
Do one of the following:
Restart Collage.
Next, you can load the project into Collage. For information on loading projects, see the Collage Installation and Setup Guide.
The Collage Installation and Setup Guide does not explain how to install the Collage Agent on AIX.
To do this:
Copy the appropriate file from the following directory on the DVD to an empty directory on your system: /DeployAgent/agentSetupAIX
Go to the directory to which you copied the file from the DVD and enter the following command to run the installer:
GUI installer: ./agentSetupAIX
Text-based installer: ./agentSetupAIX -console
Follow the onscreen prompts to complete the install. With the exception of the Windows Service option and the default install directory (/opt/serena/agent on UNIX or Linux), the install options are identical to the install options for Windows platforms.
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:
These have been superceded by two new server properties, MaxInactivityTimeout and BrowserKeepAliveInterval. These properties are described in "(DEF06046) Undocumented Properties from nas.properties File" on page 17.
The Collage Installation and Setup Guide incorrectly states that when importing an LDAP certificate, the file must be in pk7 format. The certificate should in fact be X.509 format. An error appears if you attempt to import a pk7 certificate.
In order to successfully install Collage to BEA WebLogic, WebLogic must be running during installation.
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.
The characters listed below cannot be used in project names:
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.
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: $
Accents
Non-ASCII characters, such as Cyrillic and Greek characters, are not supported for asset names in Collage.
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.
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.
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.
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.
For more information, see the KnowledgeBase article number 5000940 from the Serena Support Web-site.
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_.
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.
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.
Go to Tools | Internet Options.
Click the Advanced tab.
Scroll down to the Security section.
Select the Allow active content to run in files on My Computer check box.
Click OK.
With Windows XP SP2, the following security warning may appear when working in Collage:
Windows has blocked this software because it can't verify the Publisher
Name: PopupMenu.dll
Publisher Unknown Publisher
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).
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.
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:
Scroll to the following value: dom.max_script_run_time
Set the value to something higher than the default, which is just 5 seconds.
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.
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).
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-2007 Serena Software, Inc. All rights reserved.