CS 6.2
Release Notes


        May13, 2005

Welcome to the release notes for Content Server V6.2. For the latest release notes, check the FatWire e-docs web site. The release notes contain descriptions of new features, changes in functionality, known problems, and other last-minute information about Content Server 6.2.

For additional information, contact FatWire technical support.

Table of Contents 

Getting Started

The Content Server product CD includes a zip file (named DOC620.zip or DOC620.tar) of all the CS 6.2 documentation, including the installation guides. Unzip this file and begin reading the installation guide appropriate for your configuration. These guides explain how to install Content Server and the underlying DBMS, application server, portal server (optional), and JDBC driver.

If you are installing Satellite Server, read Installing Satellite Server.

TOP

 

New Features

What’s New in Content Server 6.2?

 

Provides ability to create and use Content Server URLs in a way that can be easily indexed by search engines such as Google

 

Supports upgrade from ContentServer 5.x, and ContentServer 6.1.  Please refer to the document Guidelines for Upgrading ContentServer to ver 6.2 for details.  For upgrading from Beta version of CS6.2, you need to follow this additional step:

- Finish off all the assignments in the FirstSite workflow

- Delete the FirstSite workflow

- Follow the instructions to upgrade from CS 6.1 in the upgrade guide.

 

CS interface now display's the full user name.  Earlier it used to display the login name. The property xcelerate.displayablenameattr can be set to specify the name of the user attribute in which complete name is stored. By default this property is empty, and the pretty name defaults to the user name. Note that:

- Existing entries in the database that have the database name will not be updated.
- CSE continues to display the database username.

 

Support for localized CSS stylesheet based on user’s preferred locale has been added. The default location of the stylesheet for en_US locale is  /futuretense_cs/Xcelerate/data/css/en_US/. However, Insite still doesnt support localized stylesheets.

 

This version of ContentServer now includes Keyview 8.2.

 

What’s New in Content Server 6.1?

Portal Interface – Content Server allows your business to take advantage of existing portal infrastructure by providing a standards-based (JSR-168) portal integration.  This interface allows users to create, edit, approve and publish content to portal site, web sites and other media entirely within the portal.

 

Site Launcher – In recent times, many enterprises are rationalizing their web infrastructure.  This means consolidation of hardware, reduction in software maintenance costs and redeployment of technical staff.  Content Server is designed to support multiple sites.  Often sites within an enterprise will have similar data and code structures.  Site Launcher allows administrators to configure a prototype or template site to be duplicated.  Once configured, a site can be duplicated with only a few clicks.  This feature also allows your business to create a duplicate of an existing site to develop a new version while maintaining the current one.

 

SAFE (Secure Authorization For Enterprise) – Security is a concern for every business.  Content Server 6 provides an enterprise model for access control.  SAFE allows authorized users to control access to content at any level of the repository hierarchy, from broad category, down to an individual asset. Moreover, specific functions such as edit or approve, can be granted or denied at any level.

 

InSite Editor 2 – Making content contributors comfortable by allowing them to work in familiar environments has always been a priority for Content Server. New additions to the InSite Editor improve upon the existing capability of editing content from within the site by adding the ability to create and add assets to a list, reorder of lists of assets, make multiple edits per save, edit asset associations, and perform additional workflow functions.

Features Removed in Release 6.x

·        Integration of Content Server with the AltaVista search engine is no longer supported.

·        The FileServer functionality is replaced by Satellite Server. The functionality of EvalServer has been disabled.

·        Some CS tags have been deprecated. These include CONTENTSERVER.*, EVALSERVER.*, CALLAPPLOGIC, satellite.tag, satellite:tag, CATALOGMANAGER.EXPORTFORM, ics:catalogmanager.exportform. For a full listing of deprecated tags, please refer to the Content Server Tag Reference (look in the XML Index under Deprecated Tags).

Major Bugs Fixed in Release 6.2

(#11921) PDF file conversion by Verity KeyView has been fixed.

In 6.1 dropping a PDF file onto a CS-DocLink folder, would send Keyview into an infinite loop.

 

(#10312) Updating non-ASCII characters through CS-Doclink when the encoding of the application server is not UTF-8 will not corrupt data anymore.

 

(#12176) From CS-Desktop, a revision-tracked flex asset now saves changes to parents.

If a flex asset is revision-tracked and changes are made to the parents of the asset in a new revision, the parents are now displayed correctly in the CS-Direct UI.

 

(#12196) In the CM Portlet, now you can edit and delete related items for a Page asset.

In 6.1 this was not possible to do using the CS portal interface.

 

(#12182) In the Search Portlet, simple search now works for AssetMaker made assets

 

(#12194) The Portal Interface now allows sharing of assets.

 

(#12129) Publish Target can contain non-ASCII characters now

 

(#12994) Simple search from portal interface now uses verity search engine if verity is enabled for that asset type

 

(#3407) PropertyEditor:  Flush Server command  works even if logging.cs and logging.cs.db options are set to DEBUG in commons-logging.properties file.

 

(#3020) In email created using Content Server's email APIs, header values containing characters other than US-ASCII are now properly encoded.

 

(#3451) CS now reads from HTTP posts without corrupting data even if there are multi byte characters on the boundary of each 1024 bytes.  CS read HTTP post in blocks of 1024 bytes.  Earlier if there were multi byte characters on the boundary, it could lead to possible corruption of data.

 

(#2374) When the getFileData method from the IList class references the defdir column in the SystemInfo table, and the defdir column is empty, the method returns null bytes.  Earlier it would throw a java.lang.illegalArgumentException error.

 

(#1872) The POST method works with USERNAME and PASSWORD arguments.

 

(#11524) When you click on  “Pick from Tree” in Recommendations with no asset in tree highlighted, now you will get an alert message asking you to select an asset in the tree.

 

(#11773) The scatter/gather/inspect variables for the Template asset has changed to better reflect the relationship between a templates elements and sitecatalog entries.
Templates can have associated multiple site catalog entries 1) if it is shared to multiple sites or 2) if it is a template with variants (i.e., has multiple element catalog entries, a feature which will be available sometime in the future). Some sitecatalog values should be set once for the template, regardless of how many element catalog entries (variants) are in the template, while others are more closely tied to the element.

Pagename (not editable, one per element+site)
Rootelement (not editable, one per element)
Pagelet parameters” (a.k.a., default arguments, resargs ) – one per sitecatalog entry (because site is one of these)
“Cache criteria” (a.k.a, pagecriteria) – per template (by definition, variants should all use the same page criteria )
ACL – per template
“Cache rules” (a.k.a., cscacheinfo + sscacheinfo) – per rootelement


(#11796) Verity: Significant performance improvements for editing a flex asset with multiple attributes enabled for verity indexing.

 

(#12112) Workflow components can be created with all non-ASCII characters in the name.

Earlier it wais not possible to create Workflow Step Actions, Workflow Email, or a Workflow State in which all characters of the name are non-ASCII. A javascript error window would pop up and prevent completion of the action. If the name contained both ASCII and non-ASCII characters, the item was saved correctly.

 

(#12186) Site parameter is automatically added for new templates.

Earlier while creating a Template the site parameter on the SiteEntry page would not be filled in automatically. The workaround was to manually add the name of the site as a pagelet parameter.

 

(#12132) Copying template with unspecified usage sets a default usage

 

(#11981) Copy of a typeless template now makes the new copied template also a typeless template

 

(#11556) Site replicator now uses the same kind of replication (Copy or Share) for asset types that have the same Parent/Child relationship.

 

(#12179) Assets not being published can be edited while a publish operation is publishing other assets.  Earlier it would give an error message and prevent users from editing the asset.

 

(#12187, 12188) InSite button to edit a list item now works correctly.  Earlier it would add an item instead of editing the list.

 

(#11403) In Spark, deleted folders cannot be accessed anymore.  Earlier a user was able to inspect and edit the deleted folder.

 

Major Bugs Fixed in Release 6.1

·        In CS 6.1 Satellite Server and Content Server generate cache keys using the same algorithm. Previously it was possible for a pagelet to be cached in Satellite Server but not in Content Server because different cache keys were used.  In this situation the pagelet could not be flushed from Satellite Server. This has been resolved.

·        Satellite Server will allow caching of wrapper pages around non-cacheable pagelets such as forms.

·        (#11652) Export publishing now supports NTFS file path length restrictions. Added a new futuretense_xcel.ini property under the publishing tab, xcelerate.exportmaxfilename, to give the client the ability to limit file path+name length to a predetermined maximum during export. Its default value is 4096. If you are using NTFS (Windows systems starting with Windows 2000 Pro), set this property to 255. 

·        In CS 6.2, asset types which require unique names are: CSElement, Template, SiteEntry, flex attributes, flex definitions, flex filters, and Recommendations. All others do not.  However, the uniqueness constraint is not changed for existing asset types on upgrade.

TOP

 

Kit Contents

This kit includes the following items:

TOP

 

 Documentation Set

The CS 6.2 document set provides documentation for different kinds of users. Updates to product documentation, as they are made, are posted to the following URL: http://e-docs.fatwire.com/CSEE/6.2.0.  For a description of the documents please refer to the Documentation Notes link on the site.  Check the site regularly for the latest set.

 

TOP

 

 System Requirements

See the SPD on FatWire e-docs web site for the list of J2EE components (web servers, application servers, DBMSs, JDBC drivers, and so on) that CS version 6.2 supports.

In order to run Satellite Server in a configuration that is not listed at the link above you may need to compile your own resin plug-in. Details for compiling your own are available at the Caucho website in the references section. You may also want to check with support to see if there are any known issues with the configuration you wish to use.

Also, refer to the Sun and IBM release notes for all J2EE components to find the latest e-fixes, patches, and service packs required to run your component.

JRE 1.4.1 or higher required by Content Server

Content Server 6.2 works in application servers running J2SDK/J2RE (i.e. JRE) 1.4.1 and above. Please make sure that appropriate version of JRE in installed and configured before installing Content Server.

Please also make sure that older versions of the JDK or JRE are not present in the PATH or CLASSPATH environment variables, especially if you plan to run Content Server in an environment that relies on these entries to be correct (resin, for example).

As of JRE 1.4.1, Sun has moved certain netscape.* classes from jaws.jar to plugin.jar. If you encounter a java.lang.NoClassDefFound  (or related) exception, make sure that JRE is properly installed on the client machine. This error is usually seen on the client machine while loading the Tree applet.

Another common problem encountered is a type of JSPException with a message like the following: "The major.minor version '48.0' is too recent for this tool to understand"

This error is related to the incorrect version of tools.jar in the class path. Make sure tools.jar loaded belongs to the correct JRE by launching JVM with a -verbose option.

TOP

 

 Installation Notes

This section describes additional steps that are necessary when installing Content Server 6.2.

General Notes

Content Server contains a modified version of the Microsoft XML Parser in the MSXML.jar file, which can cause conflicts if another version is in use. If you have Microsoft's version of MSXML.jar installed on your machine and this file is referenced in the CLASSPATH environment variable, you must change the path to the Content Server version; otherwise, Content Server fails when parsing XML.

CS Installer doesn't work in JVM1.3. JVM 1.4 should be used while installing CS (#13243)

In Application/Portal server jvm options include the settting -Djava.awt.headless=true

Additional Steps to Configure System for CS-Desktop and Document Transformation Filter

In addition, there are extra installation steps if you are using CS-Desktop, or the document transformation filter (#9760). When using CS-Desktop, the locale of the operating system, the application server, the installation of Microsoft Word, and the Internet Explorer on the client system must all be set to U.S. English with UTF-8 characters. Complete the steps appropriate for your system:

Browser Encoding

To change the character set for Internet Explorer 5.5, click View > Encoding > Unicode (UTF-8).

Server-Side Locale and Character Set

Make sure that your application server is also set for U.S. English using UTF-8 characters.

For Weblogic, follow these steps:

  1. Set up the following at the beginning of the startWebLogic.sh and startManagedWebLogic.sh scripts:
  2. On the startManagedWebLogic script, in the JAVA_OPTIONS section, add the parameter -Dfile.encoding=UTF-8.
  3. Change futuretense.ini to set cs.contenttype=text/html;\ charset\=UTF-8.
  4. Change futuretense_xcel.ini to set xcelerate.charset=UTF-8.

 

For WebSphere, be sure that the default client encoding and file encoding values in the System Properties section of the JVM Settings tab are set as follows:

Solaris/WebLogic/Oracle

  1. Open the startManagedWebLogic.sh script in a text editor.
  2. Scroll down to the LD_LIBRARY_PATH setting and append the following string to the value:
    :/$WL_HOME/server/lib/solaris
  3. Save the file.

Windows 2000/WebLogic/Oracle

  1. Open the startManagedWebLogic.cmd script.
  2. Scroll down to the PATH setting and append the following string to the value:
    drive letter:\application-server-install-dir\server\bin
  3. Save the file.

Solaris/WebSphere/Oracle

  1. Open the WebSphere Console.
  2. In the tree on the left, select the application server that represents Content Server.
  3. Select the General tab.
  4. Click the Environment button.
  5. Enter the following Name/Value pair:
  6. Save your changes.

Windows 2000/WebSphere/Oracle

  1. Open the WebSphere console.
  2. In the tree on the left, select the application server that represents Content Server.
  3. Select the General tab.
  4. Click the Environment button.
  5. Enter the following Name/Value pair:
  6. Save your changes.

AIX/WebSphere/DB2

  1. Open the startupServer.sh file in a text editor.
  2. Scroll down to the DB2 section, which is in the else clause of the if DB_TYPE condition statement.
  3. Append the following path to the LIBPATH=$LIBPATH setting, separated with a colon (:) from the other path strings for the setting: /Content-Server-install-dir/bin
  4. Save your changes.

Database and JNDI Connection Pooling

·         Increase the value of the maximum number of WebLogic JDBC Connection Pools to at least 100 on both publish source and target machines.

eWebEditPro License

Within Content Server, Ektron eWebEditPro ships with a 30-day evaluation license. At the end of the evaluation period, customers interested in purchasing a license for eWebEditPro should contact their FatWire sales representative.

JNDI Authentication Plug-In Configuration

If upgrading from the old LDAP plugin (CS v4.0 and earlier, based on LDAP authentication) to new LDAP plugin (CS v5 and later, based on JNDI authentication), set the following properties in futuretense.ini under the Authentication tab:

Set the following properties in dir.ini:

The "loginattribute" property is the name of the attribute that a user logs in with. This is analogous to the "username" property in ldap.ini. If you're upgrading from LDAP authentication to JNDI authentication, copy the value of "username" from LDAP.ini to the value of "loginattribute" in dir.ini. Also, copy the values of the "LDAP.PrivUser" and "LDAP.PrivPassword" properties in ldap.ini, to the jndi.login and jndi.password properties of dir.ini. You need to do this even if jndiConnectAsUser is set to true. If jndiConnectAsUser is set to true, Directory Services will still connect to LDAP as the currently logged in user, but the authentication plug-in still needs these values.

Sun ONE Application Server

To avoid potential publishing problems, edit the server.policy file corresponding to the Content Server "server." In the server.policy file, add the following grant directive:

 
grant {
permission java.lang.RuntimePermission "createClassLoader";
}

Sample Code

The installation media of Content Server  includes a folder (named Samples) with sample code for AssetMaker, XMLPost, and BulkLoader. Please refer to the readme file in the Samples folder for details of the sample code. The folder is not installed on the customer's system but is available on the installation media for reference. 

TOP

 

Known Issues

Known Issues 6.2

The known issues discovered in release 6.2 are described in this section and are sorted by product.

Content Server

Application Servers

 (#11461) Need patch from BEA to enable javascript in portlets.

Javascript doesn't work on BEA managed server set up in Production mode. To use the portal defined from Weblogic Administration Tools Portal (the WebUI, not the WorkShop), contact BEA to obtain patch CR 131778. Install the patch.

(#1700) For Microsoft SQL Server databases, Content Server recommends maximum length of 4000 characters for Varchar columns.

Microsoft SQL Server 2000 database allows a maximum size of 8000 characters in a varchar type column. Using JDBC, however, it is possible to insert/update data of only 4000 characters or less using prepared statement technique (Content Server users this technique). Attempts to insert/update data larger than that size fail with an error. As a result of this anomaly, Content Server’s insert/updates fail with the following message in the logs “Disallowed implicit conversion from data type ntext to data type varchar”.

It is therefore advised that that the varchar column be created with capacity less than 4000. If size requirement for this column is greater than 4000, please consider using a ‘URL type’ field.

TOP

 

CatalogManager

(#605) Deleting tables using CatalogManager.

If you have enabled revision tracking for an object table, and then you delete the table using CatalogManager, Content Server still thinks that the table is being revision tracked.

(#2037) SystemSQL column tablename is allowed to be null.

Content Server allows the value in the tablename column in the SystemSQL table to be null. However, for result set caching to work properly, this value must be specified.

(#2534) Cannot log in to Content Server if username is the same as "id" value in SystemUsers.

You cannot log into Content Server if the username you are using to log in has the same "id" value of a different user in the SystemUsers table. For example, DefaultReader has an ID value of 2. If you create a user with the username "2," that user cannot log in.

TOP

 

CatalogMover

(#2272) Selecting a specific HTML file for import does not work properly if more than one file exists in the directory location.

(#2548) CatalogMover does not export from columns that hold blobs.

For example, a table is created with a column using the data type specified by the property cc.blob. An image is uploaded to the table. When CatalogMover exports the row, the image is not written out to the export data.

TOP

 

Cache

(#3440) Content Server and Blob Server cache properties use inconsistent units of measurement.

The properties that control default cache expiration use different measures.

·        In futuretense.ini: cs.pgCacheTimeout is measured in minutes. The default value is1440 (i.e. 24 hours.) This property specifies how long page cache live in CS. It also specifies how long pages live in the SS cache if not otherwise specified.

·        In futuretense.ini: bs.bCacheTimeout is measured in seconds. The default value is 300 (i.e. 5 minutes.) This property specifies how long blob cache lives in CS cache if not otherwise specified.

·        In Satellite.properties: expiration is stored as a timepattern and controls when blob cache in SS would be flushed. The default value is 5:0:0 */*/* which means that the blob cache will be flushed at 5:00am every morning from Satellite Server.

TOP

 

Databases

(#1131) LONG and LONG RAW columns cannot be mirrored.

When using Oracle, LONG and LONG RAW columns cannot be mirrored. Use a URL column rather than a LONG or LONG RAW.

(#13399)  Oracle 10 thin driver limits creating AssetMaker Asset Types with 2 or more binary fields.

While using Oracle 10.1.0.2.0 thin driver for CS, if you create an AssetMaker asset type with 2 or more BINARY fields, Content Server mixes the columns. The workaround is to use the 9.2.0.4 OCI driver.

TOP

 

Java API

(#1513) Content Server requires column names returned in length order.

When implementing an IList, Content Server requires that column names be returned in length order, especially when one column name is a prefix of another column name (i.e., order and order_id). This can affect performance if the implementing IList class wants to maintain a column order.

(#2046) ics.CommitBatchedCommands() does not return the correct status.

ics.CommitBatchedCommands() does not return the correct status or set the errno variable properly in every situation.

TOP

 

Miscellaneous

 (#1597) Content Server Events (APPEVENT) are ignored if the previous event took too long.

For example, if you have a Content Server event that is scheduled to occur every minute and one of the events took 70 seconds to execute, the next event is ignored.

(#2035) Changing cc.contentkey causes problems.

Changing the value of the cc.contentkey property to something other than the default value causes problems with CS tables that depend on this property. FatWire recommends that you do not change this property.

(#2775) Mirroring sets errno incorrectly.

Mirroring fails to set errno if it fails to write a file to the folder specified by defdir in the SystemInfo table.

(#3209) Page Debugger doesn't work for JSP pages.

Page debugger fails when trying to debug JSP pages.

(#13212) When ContentServer is installed on Websphere 5.1 and higher futuretense.txt does not get created at all.

By default Content Server (futuretense.txt) logs on WebSphere 5.1 goes to WebShpere (SystemOut.log) log directory. So User don't see futuretense.txt file at all. Solution for this is WebSphere uses commons-logging and so it's in the root classloader. This may cause difficulties when trying to find a configuration resource. The solution is to ensure that the right classloader policy is set: Set EAR classloader mode as PARENT_LAST and WAR classloader policy as Application

(#13128) If a user has an asset checked out, and admin removes access permission for the user, the item is still checked out to the user. It should automatically get checked in.

(#13210) During Installation if FirstSite is selected no other sample sites should be selected, else it would cause a number of issues in the CS Application.

TOP

 

Revision Tracking

(#145) Tracker table is wider than the source table.

The tracker table created by the revision tracking feature for a tracked table is always wider than the source table. This means that you cannot track tables that are close to the maximum row size supported by the database.

TOP

 

Tag Issues

(#2458) SQLEXP adds a percent sign (%) to the front and back of the literal when LIKE is used.

(#) POST tag sends login and logout requests to the URL being posted.

The POST tag works incorrectly when USERNAME, PASSWORD or LOGOUT attributes are passed to it. Login and logout requests are sent to the URL being posted to instead of CatalogManager. One workaround is to perform login before this tag is executed. Alternatively, FormPoster API can be directly used to perform the post operation.

 

TOP

 

User Management

(#3267) CS supports only Reads (not Writes) from the Active Directory implementation of LDAP.

For an installation of Content Server that uses Active Directory for User Management, the jndi user specified should only have read permissions. We do not guarantee what will happen if he has write permission.

(#2153) The dir:replaceattrs tag does not give an error when an attribute or user does not exist.

The dir:replaceattrs tag, which is part of the CS-Direct application that Content Server uses for user management, does not throw an exception when it is trying to replace the user attribute value of a nonexistent user attribute or for a nonexistent user.

TOP

 

Utilities

 (#1570) Page Debugger: Port conflict on Windows 2000.

The default debug listener port of 1025 for the Page Debugger may have a conflict on Windows 2000. This can be changed so some other port number.

TOP

 

XML

(#1558) XML namespaces are stripped from XML elements during evaluation.

TOP

 

Satellite Server

 (#3446) Satellite Server default url is http://host:port/Satellite

By default, remote Satellite Server is installed under http://host:port/Satellite, i.e. the default url for servlets is http://host:port/Satellite. Note that this URL does not contains /servlet/. The customer may alter the default URL by editing web.xml in the Satellite Server kit.

(#2525) Satellite Server does not preserve the IP address of site visitors.

If you use the Content Server REMOTE_ADDR variable to return the IP address of a site visitor, the value returned contains the IP address of the Satellite Server machine instead of the IP address of the visitor. For this release, it is not possible to return visitor IP addresses through Satellite Server.

(#13506) IIS6 plugin for resin does not work.  So IIS WebServer plugged in to Resin App Server is not supported for Remote Satellite Server installs

TOP

 

CS-Direct

Attribute Editors

(#8220) The XML code for attribute editors can have no extra white space in the text entry field in the New or Edit Attribute Editor form.

This includes hard spaces between lines of code and indenting. When there are additional white spaces, the attribute editor does not work properly when a user attempts to add a value for the flex attribute that uses the editor.

TOP

 

BulkLoader Utility - Flex Assets Only

(#1756) BulkLoader does not handle attributes of type blob or URL field.

TOP

 

Embedded Links

(#6623) It is possible to embed an embedded link inside another embedded link.

CS-Direct does not stop users from embedding links inside other embedded links. If this happens, the links may not be resolved on the page that displays the asset (that is, they are broken links).

(#10323) Embedded pagelets, using the 'Include' link, can not be rendered in the InSite Editor if ewebeditpro is true.

The Insite.Edit tag should have the ewebeditpro=true attribute removed when displaying an embedded pagelet.

TOP

 

Flex Families

(#9442) Asset types other than flex assets may show in the Admin when tree is not displayed.

When the treeview is toggled off and you click "List All Flex Family Asset Types," the list returned are not all flex assets.

(#6479)  If a user disables an asset for a particular site, that asset type still appears on the New and/or Search menus.

(#13000) FlexFilters: Input data not converted to output attribute.

Data selected as an input attribute is not converted to the output attribute as specified in the Flex Filter.

TOP

 

InSite Editor

 (#11890) Selecting a workflow assignment may close InSite Editor.

If an assignment link is selected from InSite Editor and the link points to an asset that is unsupported for editing by ISE, then ISE will close.

 (#4471) Display and data entry issues.

The Internet Explorer browser sometimes exhibits unexpected behavior when you are editing the value of a field with the InSite Editor. For example, pressing the spacebar can toggle the eyeball and pencil icons or cause you to lose focus on the field. You can usually prevent this behavior by clicking in the dotted-outline field immediately after clicking the pencil icon. If you lose focus, click once outside the field and again inside the field.

(#7316) InSite Editor needs to perform an additional check when revision tracking is on.

When a user views an asset in the InSite Editor, the InSite Editor checks to make sure the asset is not locked and it displays the most recent version. However, it does not lock the asset until the user clicks the pencil icon.

At that point, when it does lock the asset, the InSite Editor should check the version one more time. It does not. Because the asset was not locked, it is possible that another user could have opened, edited, and saved it while the first user was viewing it. This means that the original user could now be working on an out-of-date version of the asset.

(#13061) InSiteEditor does not refresh to show the pencil icons for editing after the deny permission to edit is removed for author user.

To keep up with the performance, insite content is designed to be cached with other part of the pagelet. The current implementation keeps track of all direct dependencies, including access permission and workflow state, which are all direct related to the asset instance.  The workaround is to flush CS and SS cache and the pencil icons will start showing correctly.

TOP

 

Publishing

 (#1752) The publishing process cannot mirror query assets that are referenced in the code in an attribute editor asset.

Because the publish process does not parse the code in attribute editors, it cannot determine whether an attribute editor uses a query asset. To work around this problem, explicitly publish the query assets that you are using with your attribute editors.

(#5493) Multiple users cannot perform bulk approvals at the same time.

It is recommended that only 1 user runs bulk approval at any given time. If you do need multiple users to run bulk approvals, please schedule accordingly.

TOP

 

Search

 (#8543) Cannot search on subtype field for assets with their subtypes set to "no subtype."

When upgrading from a Content Server version that does not support subtypes to CS 6.2, all legacy assets have their subtype value set to "no subtype."

Because the "no subtype" option does not appear in the subtype drop-down menu on the Advanced Search screen, you cannot run an advanced search based on the subtype field for assets with their subtype set to "no subtype."

 

(#13437) Cannot search with simple operators on a flex attribute that have verity enabled

When searching flex assets using the simple parser and the operators MATCHES, STARTS, ENDS, CONTAINS and SUBSTRING you need to specify a field. Example: keyword <MATCHES> Yaser Arafat. In BASIC assets it works because in the index there are fields with the same name as the fields in the asset, so you can query: keyword <MATCHES> Yaser Arafat. And it works. With Flex Attributes, the internal name of field used in verity index is different from the field used in the CS Database.

TOP

 

Site Launcher

Need to reapprove assets shared by Site Launcher.

Any approved assets which are shared when a site is replicated with Site Launcher will need to be reapproved in the source site after the site replication.

TOP

 

Tag Issues

(#5763) SEARCHSTATE.ADDRICHTEXTCONSTRAINT fails when the resultset returns more than 1000 rows.

TOP

 

Templates and Elements

 (#8014) Do not use <throwexception> in template code.

Do not use the tag <throwexception> in the code of a template asset. <throwexception> effectively kills execution in CS for itself and any nested or parent CS engine. This breaks template execution and streaming of data to the client. In addition, when a user approves a template for export publish, a <throwexception> terminates the execution of the approval page and the user gets no feedback.

(#12055) Approval may display an error (-10004) if template logic expects an argument that is not supplied by the Approval process.

Element logic which expects to be passed an argument may generate an error (-10004) when called during approval for export publish if that argument is not present. The error code is displayed in an information box after approval. The template writer should decide whether the error can be safely ignored, i.e. if the error occurs because the template or element is being called out of context and does not affect the approval dependencies.

 

TOP

 

Users

(#9647) To remove a user from LDAP, first remove the user’s roles in CS

If a CS Administrator wants to remove a user from the LDAP, he should first remove all the user’s roles in the CS-Direct interface. If this step is not completed, the user can have dangling rows in UserPublication table when LDAP is used to store users (& ACLs) and CS database (UserPublication table) is used to store user roles.

(#8455) Deleting a user at the Content Server level does not delete that user at the CS-Direct level.

When a user is deleted at the Content Server level through Content Server Management Tools, that user is not deleted from CS-Direct sites.

(#13432) If a user without any ACL logs in to CS, CS allows user to perform only those operations that a user with Browser ACL can perform.

 Updates made to ACLs using CS User Admin Screen, are reflected immediately. However, if ACLs are updated directly in LDAP server, then we recommend that you a) Restart your portal/Application server for the changes to take effect or b) Flush ACL cache using the url http://localhost:7001/spark/CatalogManager?ftcmd=flushcatalog&tablename=SystemUsers&authusername=admin&authpassword=xceladmin

(#13312) CS Installer fails on Sun JES platform if there is a preexisting "admin" user If your Sun JES platform has an admin user, and you try to install CS with LDAP integration enabled, the CS Installer fails because it tries to create an admin user too.

(#13481) Advance Search UI screen stops rendering if you delete a user from CS Management Tools or CS Explorer

 If a user is enabled for a site and you delete the user from ContentServer Management Tools interface or from SystemUsers in Content Server Explorer, AdvanceSearch UI screen will not render. The workaround is to delete the corresponding user entry from UserPublication table

(Unnumbered) The RolesAdmin portlet doesn't work properly. If you want to modify/add a role you can use this portlet but the changes will be visible only after you log back in. The alternative is to use the identity server interface

TOP

 

Workflow

(#9651) When a user takes a Retained Assignment workflow step, an entry in the workflow history is not created.

On a retained assignment, entering content into the "Action Taken" text box produces the following message: “This step retains the current assignment. Content entered into the “Action Taken” field will not be recorded.”

(#9654) After doing "Finish My Assignment" the "Abstain" function is missing.

When a user has finished their assignment and the assignment is 'queued' (in an all-voting step) the Abstain function is incorrectly missing from the workflow actions dropdown. If this occurs when the asset is in workflow deadlock, the user may change his vote to fix the deadlock.

(#8211) Canceling Set Participants causes the workflow to be set to all participants.

If you select a workflow for an asset, then go to the Set Participants form, then click the Cancel button, the workflow is set to all participants, as if you had selected the Select All button.

TOP

 

Internationalization

(#12096) The ConentServer Management Forms are not internationalized.

Within the CS Admin tab, there is a node titled “Content Server Management Tools”. The forms under this node are not internationalized. That is, they do not accept non-ASCII characters.

(#13471) CS does not support table names and column names with multibyte UTF-8 characters.

We have seen issues with creating tablenames and column names in multibyte UTF-8 characters in Oracle 9i, MS SQL Server, and DB2.  We also recommend that you do not use multi-byte characters in the following

                   UserName’s

                   ACLName’s

                   RoleNames

                   Template Names

                   AssetType Names and FieldNames

TOP

 

Upgrades

(#13474) Before upgrade, set the Following property in futuretense.ini: secure.CatalogManager=false

If this property is set to true, you will get unknown username/password error while running pingdb. Once the upgrade process is complete, you can set this property back to true.

(#13292)The History and Vistor Attributes do not upgrade automatically from previous versions of Content Server to CS 6.2.

 Error during deserialization of history attribute on an upgrade from 5.5.1 to 6.2 The user to edit all visitor attributes and history attributes that have constraints, and basically respecify the constraints in the UI.

(#13079) DB differences between 5.5 and 6.2

Differences between 5.5.1 upgraded to 6.2 and pure 6.2 install.

TABLE Differences

 

Unique Tables, that still existed in the upgraded version – These tables are not used by 6.2 code anymore.  However, we do not recommend that you delete these tables.

DTDCATALOG

INBOUNDCATALOG

OUTBOUNDCATALOG

PARTNERCATALOG

SITEENTRY_ARGS

TXSITECATALOG

TXSYSTEMITEMCACHE

 

 

CONSTRAINT Differences

Constraints that are not removed from 5.5.1 upgraded to 6.2. These constraints should be removed manually after upgrade to achieve full functionality, and to avoid any problems on future upgrades.

Table Name

Constraint Name

AARTICLES

UNIQUE NAME

AIMAGES

UNIQUE NAME

ARTICLE

UNIQUE NAME

ATTRTYPES

UNIQUE NAME

COLLECTION

UNIQUE NAME

CONTENTGROUPS

UNIQUE NAME

DRILLHIERARCHY

UNIQUE NAME

DTDCATALOG

PRIMARY KEY ID

IMAGE

UNIQUE NAME

INBOUNDCATALOG

PRIMARY KEY ID

LINK

UNIQUE NAME

LINKSET

UNIQUE NAME

OUTBOUNDCATALOG

PRIMARY KEY ID

PAGE

UNIQUE NAME

PARTNERCATALOG

PRIMARY KEY ID

PDF

UNIQUE NAME

PRODUCTGROUPS

UNIQUE NAME

PRODUCTS

UNIQUE NAME

PROMOTIONS

UNIQUE NAME

QUERY

UNIQUE NAME

SEGMENTS

UNIQUE NAME

TXSITECATALOG

PRIMARY KEY PAGENAME

SITEENTRY_ARGS

PRIMARY KEY ID

WORKFLOWOBJSACTIONS

PRIMARY KEY ID


 

COLUMN Differences:

The table below lists the column difference after upgrading from 5.5.1 to 6.2  You can change the length of those columns after upgrade. 

Tablename

Column Name in

CS 5.x

Column Definition in

CS 5.x upgraded to 6.2

Column Definition in brand new
CS 6.2 install

AARTICLES

subtype

Varchar2(24)

varchar2(32)

AIMAGES

subtype

Varchar2(24)

varchar2(32)

ARTICLE

subtype

Varchar2(24)

varchar2(32)

ATTRTYPES

subtype

Varchar2(24)

varchar2(32)

CATTRIBUTES

subtype

Varchar2(24)

varchar2(32)

CGROUPTMPLS

subtype

Varchar2(24)

varchar2(32)

COLLECTION

subtype

Varchar2(24)

varchar2(32)

CONTENTGROUPS

subtype

Varchar2(24)

varchar2(32)

CONTENTTMPLS

subtype

Varchar2(24)

varchar2(32)

DRILLHIERARCHY

subtype

Varchar2(24)

varchar2(32)

HELLOARTICLE

subtype

Varchar2(24)

varchar2(32)

HELLOIMAGE

subtype

Varchar2(24)

varchar2(32)

HFIELDS

subtype

Varchar2(24)

varchar2(32)

HISTORYVALS

subtype

Varchar2(24)

varchar2(32)

IMAGE

subtype

Varchar2(24)

varchar2(32)

IMAGEFILE

subtype

Varchar2(24)

varchar2(32)

IMAGEFILE

template

Varchar2(32)

varchar2(64)

LINK

subtype

Varchar2(24)

varchar2(32)

LINKSET

subtype

Varchar2(24)

varchar2(32)

PAGE

subtype

Varchar2(24)

varchar2(32)

PATTRIBUTES

subtype

Varchar2(24)

varchar2(32)

PDF

subtype

Varchar2(24)

varchar2(32)

PGROUPTMPLS

subtype

Varchar2(24)

varchar2(32)

PRODUCTGROUPS

subtype

Varchar2(24)

varchar2(32)

PRODUCTS

subtype

Varchar2(24)

varchar2(32)

PRODUCTTMPLS

subtype

Varchar2(24)

varchar2(32)

PROMOTIONS

subtype

Varchar2(24)

varchar2(32)

QUERY

subtype

Varchar2(24)

varchar2(32)

SCALARVALS

subtype

Varchar2(24)

varchar2(32)

SEGMENTS

subtype

Varchar2(24)

varchar2(32)

STYLESHEET

template

Varchar2(32)

varchar2(64)

VMHISTORYATTRIBUTEFIELDDEF

defaultvalue

Clob

varchar2(2000)

VMSCALARATTRIBUTEDEF

defaultvalue

Clob

varchar2(2000)

VMVISITORSCALARVALUE

attributevalue

Clob

varchar2(2000)

WORKFLOWOBJECTS

cs_status

Varchar2(1)  NOT NULL

char2(1)  NOT NULL

WORKFLOWSUBJECT

body

clob NOT NULL

varchar2(2000) NOT NULL

 

TOP

 

CSExpress

(#13275) CS Express cannot be installed on an existing CS Express install

(#13156) On uninstalling the BEA that came with CSExpress, the Start Menu folder is not deleted.

(#13157) On uninstallation of CSExpress, Fatwire directory and some of its files are not deleted.

TOP

 

CS Portal Interface

No.

Summary

Description

10719

Undoing asset checkout displays errant message.

After undoing an asset checkout, the message " Deleted Catalog record" may appear on the bottom of the screen

10817

DM Portlet: Identical folder/document names under the same parent folder.

Under the same parent folder, the DM Portlet allows both folders and documents to have identical names.

10823

Message requests user to provide a unique name.

Trying to save a Spark asset without a name produces the following dialog: "You must specify a unique name for this Spark <asset type>". Note that the name does not have to be unique.

10829

DM Portlet: Cannot delete a folder if the folder is not empty.

Cannot delete a folder if the folder contains documents or sub-folders. User must delete documents and sub-folders first.

10868

DM Portlet: Copying a folder does not do a deep copy.

Copying a Spark folder does not perform a deep copy; i.e., it does not copy the contained sub-folders and/or documents.

10884

DM Portlet: No confirmation when a file with the same name is to be replaced.

Uploading a file with the same name as an existing file does not prompt the user to confirm the replacement of the existing file.

10944

Assigning a workflow process to an asset does not refresh portlets.

Assigning a workflow to an asset does not update portlets with new information.

10959

DM Portlet: Lack of permission yet still can create document or folder.

A user lacking "Check Out" and "Edit" permissions on a folder can still create a document or folder under that folder.

10965

DM Portlet: Navigation without permission.

A user can navigate the folders/documents in the DM Portlet even if the user lacks Inspect/View permission on the parent folder.

10967

DM Portlet: A folder can be moved when an underlying document is unavailable.

A folder can be moved when one of its assets is checked out or opened for editing by another user.

10968

DM Portlet: Folder can be moved when user lacks permission to edit its underlying content.

A folder can be moved when user lacks permission to move(edit) its underlying folders or documents. (Folder can be moved when its content can't.)

10976

Search results cannot be reordered.

Clicking a column title does not reorder the search results.

11106

Illegal participant entries in "Workflow commands" drop-down list.

On an asset's "Status" screen, the entries "Set Participants" and "Show Participants" may be displayed in the "Workflow commands" drop-down list . These entries are nonfunctional within Spark.

11208

DM Portlet: Document can be downloaded after session timeout.

After session timeout, document downloading is still enabled.

11220

DM Portlet: Document and folder name changed on rollback.

When a document's name and/or its parent folder is changed, rolling back the document also rolls back the document's name and/or the parent folder.

11221

Reference portlet for Spark Ad throws a stack trace.

Reference portlet for Spark Ad throws a stack trace if nothing has been published to the production server.

11458

DM portlet fails when running on JRocket.

DM portlet fails when running on JRocket. Workaround is to use the Sun JVM which ships with BEA portal.

12082

Clicking on Simple Search from Advanced Search in the Search Documents portlet brings up a blank window.

When accessed from the Search Documents portlet, the Advanced Search popup contains a link for simple search. Clicking on this link brings up a blank window.

10979

In DM portlets, clicking on some links take you to search screen

After Searching for assets in the portal interface, when you click on some links in My Document portlet you may see the search screen again.

13467

Delete of Page Asset doesn't fully remove it from the system in CS Portal

Interface From CS portal interface when a Page asset is deleted, it seems to be successful. However, when the user tries to delete a query or collection associated with the deleted Page asset, it shows the ID of the deleted Page asset. Note that this deleted Page cannot be searched for, but is seen only when user tries to delete a related Asset.

12910

TimeZone mismatch error happens and Assignment Due date changes by 1 day in Portlet display

In workflows the times are set based on GMT. So this causes some confusion for users using the system in other time zones

12911

In Spark Portal Interface, the deadline time is not set correctly

In the set assignment deadline screen in Spark Portal interface, if the Time field is set to 09:30 it actually saves as 0:30 and removes the 9.

 

The RolesAdmin portlet doesn't work properly in Spark installs on SunOne Portal Server.

If you want to modify/add a role you can use this portlet but the changes will be visible only after you log back in. The alternative is to use the identity server interface.

 

TOP

CS Clients

CS-Desktop

(#12172) Delete of multi-valued attribute throws exception.

Within CS-Desktop, deleting one or more values of a multi-valued attribute causes CS to throw the following exception on save "Error 0, Exception in AssetImportSeed null" error. Adding a new attribute will correct the issue

            (#12174) Workflow menu for Delegate Assignment is not enabled correctly.

Within CS-Desktop, delegate an assignment and then delegate it back.  Even though the delegation is successful, workflow menu is still not grayed out and delegate and finish are available but fail.

(#12177) Revision-tracked flex asset stays locked after closing CS-Desktop if the asset existed before revision-tracking was turned on or if the version number was updated from CS-Desktop.

(#11741) CS-Desktop Images are not saved if folder does not exist.

During file conversion by CS-Desktop (implemented by Verity KeyView), CS-Desktop writes image files to the folder specified by property keyview.imagedir in futuretense_xcel.ini. There are two requirements for the folder keyview.imagedir:

1.      It must be a web-accessible folder that matches the URL prefix specified in keyview.imgurl. This ensures that CS can preview the CS-Desktop images.

2.      The folder must exist before CS-Desktop is used. This ensures that the KeyView file conversion completes successfully and saves the images.

Note that after installing CS, keyview.imagedir is set to $SHARE-directory/remoteimages and keyview.imgurl is set to /futuretense_cs/remoteimages/. You may edit these value to point to an appropriate folder, or you may keep these values and create a folder named remoteimages.

(#9414) CS-Desktop toolbar does not show up when Word is used as email editor in Outlook.

If Outlook is already open, CS-Desktop toolbar will not be displayed when MSWord is opened to connect with ContentServer.  This only occurs if MSWord is configured to be the default email editor for Outlook and Outlook has been opened first.  Outlook maybe closed and MSWord reopened as a workaround.

 (#5928) Undocumented limitation: You cannot specify named associations for an asset with CS-Desktop.

(#7688) You cannot specify values for flex attributes of type asset with CS-Desktop.

This means that flex assets that have a required attribute of type asset should not be enabled for CS-Desktop.

(#8105) CS-Desktop is unable to save UTF-8 encoded characters in the name field and other fields populated via document properties (not bookmarks) due to problems with Keyview transformation of the word document into XML.

 (#8504) When you edit a flex definition and change the number of parents that flex assets using that definition can have from single to multiple, there are problems with existing flex assets of that definition.

In such a case, when a CS-Desktop user opens a flex asset that was created with the original definition, there are no parents marked for the asset. To work around this issue, be sure that you do not enable flex asset types for CS-Desktop until you are completely finished configuring their definitions.

(#10337) CS-Desktop does not support connection via a proxy server.

(#13371) Using CS-Desktop the saved contents from word are not shown fully in the preview.

When data is saved using CS-Desktop in the form of table content then entire data is not saved hence not previewed.

(#13366)  Need to add LD_LIBRARY_PATH for CS-Desktop to function properly

 When installing ContentServer on Solaris/ SUN application server or SUN webserver, you need to set the environment variable LD_LIBRARY_PATH to the location where keyview files get copied. This is typically /var/opt/SUNWappserver7/lib. This environment variable must be set for the user who is starting/restarting the SUN application/ SUN web server.

TOP

 

CS-DocLink

 (#10337) CS-DocLink does not support connection via a proxy server.

TOP

 

Content Server Explorer

(#3439) Content Server Explorer (CSE) issue with Export to Zip format

If your Content Server system is using the UTF-8 or Shift-JIS character sets, please be aware of the following problem with exporting tables in the ZIP format from CSE. File names (such as an element's url file) containing non-English characters will cause the export to fail. As a workaround you can export those
records or the table using the CSE format. There is no problem with the content of the files (any valid UTF-8 or Shift-JIS characters will work), only the file names are an issue.

TOP

 

CS-Engage

 (#5508) Problem with multiple-value history attributes

If a history attribute has multiple values (for example, a history attribute of type date), you cannot remove one value without removing all values while editing the attribute.

TOP

 

 Contacting FatWire 

To contact FatWire Corporation about technical support for your product:

Web: http://www.fatwire.com/support

TOP

 

.


FatWire documentation

Copyright © 2002 2003 2004 2005, FatWire Corporation All rights reserved.