Getting Started

The Content Server 6.3 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  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

Kit Contents

This kit includes the following items:

• Content Server
• Java components that provide application services
• Samples that demonstrate the use of Content Server pages, elements, dynamic tags and Java APIs
• Content Server User Interfaces
• CS-Engage
• CS-DocLink
• CS-Desktop
• Content Server Utilities
• Content Server Explorer - Windows-based utility to browse and modify content stored using CS
• CatalogMover - Java utility for importing and exporting tables
• Property Editor - Java utility for modifying Content Server properties
• XMLPost - Java utility that for loading in batch mode content into the Content Server database
• Co-Resident Satellite Server (see Installing Satellite Server for more information)

 

TOP

 Deprecated functionality in Content Server 6.3 Patch 10

The following items are no longer shipped or supported in Content Server 6.3 Patch 10:

• KeyView
• Ektron eWebEditPro

 

TOP

General release note updates post GA

Miscellaneous updates to the release notes

• New tables - Two new tables have been added in this release. The two tables - Template_Map and CSElement_Map - are used to store mapping related data. See the developer's guide for more details.
• Support was added to allow recommendations as unnamed associations.
• The following variables - c, cid and p - are not included in the packed arguments when render.getpageurl tag is used with wrapperpage argument.
• If you install Spark as production then the users need to be created manually in the LDAP server.
• If upgrading from Spark to CS - change following property in futuretense_xcel.ini to enable preview icon on the UI. Change the property from
   xcelerate.defaultpreviewurlgenerator=None
     to
   xcelerate.defaultpreviewurlgenerator=Standard
  Restart application/portal server for the change to take effect.

Issues fixed post GA

This rollup patch incorporates all fixes and changes added to the product since the 6.3 GA release. This patch requires that you are at least on the GA 6.3 version of software. It is not intended for use with any previous version
 

Patch Release Name and version	Patch Release date
CS 6.3 patch 1 build   cs.jar - ContentServer-bld-216   xcelerate.jar - xclF-bld-474	Feb 21, 2006
CS 6.3 patch 2 build   cs.jar - ContentServer-bld-226     xcelerate.jar - xclF-bld-484	Mar 29, 2006
CS 6.3 patch 3 build   cs.jar - ContentServer-bld-248   xcelerate.jar - xclF-bld-509	Aug 28, 2006
CS 6.3 patch 4 build   cs.jar - ContentServer-bld-259   xcelerate.jar - xclF-bld-521	September 29, 2006
CS 6.3 patch 5 build   cs.jar - ContentServer-bld-277   xcelerate.jar - xclF-bld-539	December 18, 2006
CS 6.3 patch 6 build   cs.jar - ContentServer-bld-304   xcelerate.jar - xclF-bld-566	May 1, 2007
CS 6.3 patch 7 build   cs.jar - ContentServer-bld-326   xcelerate.jar - xclF-bld-588	August 31, 2007
CS 6.3 patch 8 build   cs.jar - ContentServer-bld-346   xcelerate.jar - xclF-bld-607	December 28, 2007
CS 6.3 patch 9 build   cs.jar - ContentServer-bld-365   xcelerate.jar - xclF-bld-624	August 29, 2008
CS 6.3 patch 10 build   cs.jar - ContentServer-bld-490   xcelerate.jar - xclF-bld-738	June 15, 2011
CS 6.3 patch 11 build   cs.jar - ContentServer-bld-498   xcelerate.jar - xclF-bld-742	August 24, 2011

This section is to report the important customer impacting bugs that were fixed. A full listing of the elements and data that has been changed since GA can be found by referring to the html files located in the Populate directory.

Notes:

• When installing a rollup patch - please make sure that any unique indexes added post install of CS 6.3 are removed. Reapply them after the rollup patch install completes successfully
• If any sample content installed was edited (e.g. Templates, CSElement, Attributes etc) you may see a Unique Key Violation exception. The workaround is to remove the system defined unique keys on that table and restart the installation. Reapply the unique index after the rollup patch install completes successfully.
• To patch remote satellite servers to this level, please apply cs.jar, sserve.jar and cs-core.jar from the CS kit to all Remote SS.
• If you are installing on a cluster, ft.sync must be turned off during installation
• PRs that are marked as * are only available in the complete 6.3 patch 1 kit and not as part of the rollup patch.

New platforms:

• FCKEditor is added in replacement of eWebEditPro - since patch 10
• Websphere 6.0 - since patch 3
• IE 7.0 - since patch 5
• Update on supported IBM JDKs and Websphere versions:

IBM JDK had a bug on x86 platforms that caused CS to fail under certain situations. It was fixed in IBM SDK 1.4.2 SR5 and was released as part of the WebSphere  6.0.2.11. 

 

The issues fixed in release 6.3 patch 11 are listed below.

PR	Summary	Component
26630	Unable to save AssetMaker Assets using FCKEditor	FCKEditor

The issues fixed in release 6.3 patch 10 are listed below.

PR	Summary	Component
16641	Tags - getattributevalues or listget not working after upgrade to patch 8	Tags
18668	Digital signature for CS Tree applet has expired in CS 6.3	Advanced UI - Tree Applet
19140	If you flush all Satellite Servers, Satellite Server was returning result of only first Satellite Server listed in the SystemSatellite table instead of all Satellite Servers	Caching - Satellite Server
19325	DatabaseLoader utility loads columns in random order	Database
19945	XMLPost operation was partially failing to add multiple parents to a child asset when there is a 'S' parent child relationship between the two parents.	XMLPost
20313	Recursive approval process for static publishing does not automatically approve all dependencies	Publishing - Export to Disk
20815	Satellite does not render com.fatwire.satellite.blob tags correctly	API - JSP Tags
22300	Asset import fails with multiple ordered attributes.	Flex Assets
22825	Applet warnings on JRE 1.6 if all the components of applet are not signed	Advanced UI - Tree Applet
24960	First time edit of a parent asset and save throws a -13700 error	Advanced UI

The issues fixed in release 6.3 patch 9 are listed below.

PR	Summary	Component
14519	Attempted save of Flex Asset locked by Mirror Publishing reports Errno 0	Publishing - Mirror
14708	Workflow not storing all files in subdirectories on a shared file system	Workflow
16094	XMLPost: Unable to delete blob attributes using modifyData	Utility - XMLPost
16116	Unable to pick asset when using PickOrderAsset attribute editor in insite:editasset	InSite - Editing
16199	Changes to parent cs_ordinal not changing child's asset_cs_ordinal	Flex - Attribute Editor
16377	Performance issues when too many files are stored in shared directory	Basic Asset - ADF based
16426	Folderize storage for Revision Tracking (_t) tables: Revision tracking tables for basic or AssetMaker Assets did not folderize the storage of the URL columns. This lead to a large number of files being stored in single directories which impacts performance. Now URL, Text and Binary type columns are folderized. URL columns are folderized based on the filename and text / binary columns are folderized based on the column name and revision number.	Revision Tracking
16451	JavaScript error when use "include" with TextArea	Editor - RealObjects
16468	Copying of segment fails with message that there is duplicate data	Engage
16470	Cart-based segments do not restrict based on products	Engage
16629	Shared assets are not showing up properly in the tree	Advanced UI - Tree Applet
17032	Non-static logger members cause performance issues	Performance
17260	Duplicate entries in page cache	Caching - Page Cache
17287	Possible 404 error when using PREFERREDDIR and PREFERREDFILE in static publishing	Publishing - Export to Disk
17434	asset:import error reporting missing "Attributes" section in XML file when trying to import XML representing a flex definition possessing no attributes	API - JSP Tags

 

The issues fixed in release 6.3 patch 8 are listed below.

PR	Summary	Component
14322	Searches for FlexParent Asset from "Advanced Search Form" with custom parent flex attribute specified as a constraint, resulted in the assetid of not only FlexParents but also FlexAssets which inherited the FlexParents	Search
15142	Embedded link ampersands should be encoded	Embedded Link
15820	Expanding tree node which contains more than the value of treemaxnodes resulted in the "Select more item" option not working in languages other than English	TreeView
15867	No option is shown to select assets when add selected button chosen for page assets when using insite:editasset tag.	InSite Editor
15963	Unable to clear attribute via XMLPost / modifyData	XMLPost
15969	Getting approved asset dependencies query is slow on large tables	Publishing Approval
15997	Allow for characters " / \ ^ " in the name field for Template, Site Entry and CSElement asset types	User Interface
16090	Revision tracked assets do not get automatically checked in after selecting the parent asset on edit and save	Revision Tracking
16148	ORA-01795 exception is thrown by attribute level search in Oracle when there are more than 1000 results	Search - standard
16152	Related Items block is displayed multiple times in the inspect screen	User Interface
16228	CSExplorer login and password are shown in plain text in web server's access logs.	Content Server
16252	Content Server 6.3 Patch 7 install breaks WebSphere futuretense logging	Content Server
16263	In WYSIWYG mode, if text is selected which includes paragraph tags, eWebEditPro will strip out the entire content of the paragraph tag or move it outside of the anchor tag.	eWebEditPro
16264	Pagination links for searching assets are not functioning in  insite editing	InSite Editor
16266	If a site is visited while a publish is running, accessing an uncached page can cause Content Server to cache a blank page	Publishing - Mirror
16268	Typeless templates cause double entries in the SiteCatalog	SiteEntry
16270	CS does not flush Satellite Server cache cleanly if cache key for the page contains HTML encoded characters.	Cache Management
16280	Revision Tracked assets race condition can cause database corruption	Revision Tracking
16288	<assetset:getattributevalues> no longer returns distinct values	Tags
16302	Error number 500 received instead of 404 when page is retrieved via remote Satellite Server	Satellite Server
16330	Content loads outside the body in a Basic Asset if there is a " character	AssetMaker
16361	Exception seen on Satellite Server only on Oracle Application Server when a cookie is prefixed with a '$' or is null.	Satellite Server
16396	If a BLOB is loaded in Content Server's cache but not in Satellite Server's cache (due to a restart or flush); the BLOB cannot be reloaded in Satellite Server cache	Satellite Server

Note for bug fixes:

15963:

Unable to clear attribute via XMLPost.

In XMLPost a new constant, '_EMPTY_' has been introduced to resolve this issue.

Basic assets:
Use a constant '_EMPTY_' in the value field of an attribute whose value is to be cleared. 

Flex assets:
- Single Value: Use  _EMPTY_ to clear out values
- Multi Valued attributes: In the value field, a ';' should be specified.
- BLOBs: Use  _EMPTY_ to clear out values. 

Example:

If we plan to clear BLOBs, then there is no need to send BLOB as an attachment. There are two ways to send BLOBs via XMLPost:

1. Contents of the BLOB are in the form of an external file

    To send BLOB via XMLPost

    Example: if we want to send foo.txt which is an external file

    <testBlob>foo.txt</testBlob>

    posttestBlob: y
    filetestBlob: y

    If filetestBlob is set to 'y', that means that we are passing an external file via xmlpost and the filename is 'foo.txt'

    To remove/clear value of an attribute of blob type

    <testBlob>_EMPTY_</testBlob>

    posttestBlob: y

    (no need to set parameter 'filetestBlob')

 

2. Contents of the blob are part of the XML file itself

    To send BLOB via XMLPost

    <testBlob>all the contents of fooo.txt file</testBlob>
    <testBlob_file>fooo.txt</testBlob_file>

    posttestBlob: y
    posttestBlob_file: y

    To remove/clear value of an attribute of blob type

    <testBlob>_EMPTY_</testBlob>
   
    posttestBlob: y

 

3. For single valued attribute in flex assets
   <?xml version="1.0" encoding="UTF-8" ?>
    <document>
          <_ASSET_>Content_C</_ASSET_>
          <_DEFINITION_>test1</_DEFINITION_>
          <_TYPE_>test1</_TYPE_>
          <_ITEMNAME_>abc</_ITEMNAME_>
          <_ITEMDESCRIPTION_>abcd</_ITEMDESCRIPTION_>
          <testAttribute>_EMPTY_</testAttribute>
          <age>_EMPTY_</age>
          <publication>FirstSiteII</publication>
     </document>
 
 
 

4. For multi valued attribute in flex assets
     <?xml version="1.0" encoding="UTF-8" ?>
     <document>
          <_ASSET_>Content_C</_ASSET_>
          <_DEFINITION_>testMvalueDef</_DEFINITION_>
          <_TYPE_>testMvalueDef</_TYPE_>
          <_ITEMNAME_>mvalue1</_ITEMNAME_>
          <_ITEMDESCRIPTION_>mvalue1</_ITEMDESCRIPTION_>
          <testmvalue>;</testmvalue>
          <publication>FirstSiteII</publication>
     </document>

16270:

Content Server does not flush Satellite Servers cache cleanly if the cache key for the page contains HTML encoded characters. The characters in the cache key get encoded due to fix made in PR 15359. It happens for both Remote and Co-Resident Satellite Server.

For example, using a FirstSite II install, if render the following Satellite Server URL is rendered:
http://<server>:<port>/ss/Satellite?pagename=FirstSiteII/Product_C/FSIISummary&c=Product_C&cid=1114083739851&context=Product_C:1114083739851:FSIISummary&locale=1154551493541&p=1118867611403&rendermode=previewnoinsite&site=FirstSiteII&sitepfx=FSII&ft_ss=true

After the Product_C is edited with ID 1114083739851, Content Server needs to flush items from the cache. The relevant items are removed from SystemPageCache table but Satellite Server cache is not cleaned.

The following rules apply for encoding and decoding of URLs:

* The alphanumeric characters "a" through "z", "A" through "Z" and "0" through "9" remain the same.
* The special characters ".", "-", "*", and "_" remain the same.
* The space character " " is converted into a plus sign "+".
* All other characters are unsafe and are first converted into one or more bytes using some encoding scheme. Each byte is then represented by the 3-character string "%xy", where xy is the two-digit hexadecimal representation of the byte. The recommended encoding scheme to use is UTF-8. For compatibility reasons; if an encoding is not specified, then the default encoding of the platform is used.

For more information about HTML form encoding, consult the HTML specification at http://www.w3.org/TR/html4/

The issues fixed in release 6.3 patch 7 are listed below.

PR	Summary	Component
14346	SS shouldn't transmit host service header to browser	Satellite Server
14678	XMLPost: problem adding flex assets with 2 or more parents with the same name	XMLPost
14740	XMLPost with httpclient reports failure but actually succeeds	XMLPost
15045	Tag asset:deletevoids does not work, and it corrupts the approval subsystem	API
15183	RemoteContentPost does not work for Revision Tracked assets	Other
15184	Basic attributes are URL encoded on out of the box basic assets but not on custom ones	User Interface
15302	Configuration for some properties in KeyView ini file are still hardcoded	Other
15304	Asset saves are slow due to large number of unknown dependencies	Other
15305	Rollup.zip File does not contain the file csrollupinstall.sh file to run on Unix/Linux	Installation
15308	Performance issues related to logging	Other
15331	Static approval works incorrectly when templates are shared	Publishing (common)
15347	Date Picker images not being displayed in CS6.3 Patch 5	UI / usability
15349	NumberFormatException thrown when doing Export To Disk publish	Publishing Export to Disk
15355	NumberFormatException thrown when doing Export To Disk publish	Publishing Export to Disk
15359	SS does not correctly pass parameters when they contain a doublequote mark	Satellite Server
15467	CS: xcelerate.displayablenameattr causes "Variables.useraclname" to be displayed	Content Server
15481	RSS does not pass some headers to CS	Satellite Server
15493	CS 6.3 patch 6 breaks embedded links for basic assets	Embedded Link
15500	PREFERREDFILE and PREFERREDDIR parameters missing from jsp tags	Publishing Export to Disk
15523	Gross system.exit in com.openmarket.commercedata.seed.DataWriteManager	Analysis Connector
15534	Order of columns in bkt files (commerceconnector)	Commerce Connector
15566	Ektron 5 needed for CS 6.3 Patch 7	User Interface
15567	CS-Direct: Character Encoding is different when page is called from Tree applet	User Interface
15639	Unable to delete parent pointers in an asset using "pick from tree"	User Interface
15698	Flush SS in multiple threads	Cache Management
15700	brackets in cs.jsproot cause exception	JSP
15711	Template save enforces SiteCatalog naming format <site>/<assettype>/<tname>	Template Asset
15713	XMLPost not working with : char	XMLPost
15716	application/rss+xml	Satellite Server
15737	XML debug breaks 'new' start menu	Start Menu
15739	Document_C/FSIILink uses satellite:blob instead of render:getbloburl	FirstSite II
15741	XSS vulnerability: additional places of XSS problems	Security
15742	CS-Direct: Character Encoding is different when page is called from Tree applet	User Interface
15746	tree localization issues	Localization
15749	Unable to mirror AssetTypes	Publishing Mirror
15764	Exported page effectively rendered with wrong template when using SIMPLENAME	Publishing Export to Disk

Note for bug fixes

15304:

Expire cached pages instead of expunging by marking their expiration date to a past date. Expired pages are cleaned up asynchronously by CacheServer. This makes asset saves and publishing much faster. A property has been added.

Set cs.expireonly=true in futuretense.ini to switch to this new behavior

15308

The real issue is that JCL's implementation of the factory is just too slow to run in concurrent code. The fix is to hold the loggers statically instead of dynamically. This change causes us to no longer be able to theoretically change the logging levels without restarting CS. Users can use Log4J and still change log levels on the fly.

15534

The columns are now sent into the queue manager in ordered form, rather than in hash-table form.

15566

eWebEditPro 5.1 is certified on CS 6.3 patch 7 but it is a manual configuration. Get 'ewebeditpro51.zip' from the patch and follow ReadMe_eWebEditPro.txt to configure it.

15698

Satellite Servers were flushed in series using a single thread. With many satellite servers, this can cause significant delays. Now we flush each SS in a separate thread to bring that under control. We now have two ways to flush satellite servers - do a complete flush (set ss.flushall=true in futuretense.ini), or flush affected pagelets only (default).

15713

Introduced three XMLPost parameters that user could use to identify their data delimiters when they use flex XMLPost (add/modify/deletedata elements). The default values for the three delimiters are : = ; if user does not post them. To change them, do the following:

in xmlpost.ini, add

post_xmlnamevaldelim_: y
post_xmlpostequaldelim_: y
post_xmlpostmulvaldelim_: y

in .xml data file, add (suppose you want to use @ to separate name/value pair(default is : if not posted), == instead of = for name=value(default is =), and - to separate multi-valued attributes(default is ;))


<_xmlnamevaldelim_>@</_xmlnamevaldelim_>
<_xmlpostequaldelim_>==</_xmlpostequaldelim_>
<_xmlpostmulvaldelim_>-</_xmlpostmulvaldelim_>
 

15716

For the Elements where you plan to support rss object, set resdetails2 property to "cs.contenttype=application/rss+xml

15746

Fixed the localization issue but opened a new PR (15820) for tree related pop up issue.

15764

This issue was resolved using a support tool written by US support.

 

The issues fixed in release 6.3 patch 6 are listed below.

PR	Summary	Component
12146	In Scheduled Publish, if there is nothing to publish (for a mirror target), sometimes the status of publish is listed as 'Failed' and sometimes it is 'Done'.	Publishing
14257	Insite template throws javascript error when template has many slots	InSite Editor
14476	CS throws an incorrect error messages when a Blob is viewed through Satellite Server with invalid data.	Content Server
14496	CDATA section ignored by asset:import	Import/Export
14533	Advanced Search: Using "Select Attribute" returns all assets	Search
14574	"distinctonly" attribute added as an optional parameter in AssetSet.getassetlist and AssetSet.getassetcount tags to select first combination of sorted values when sorting on a multi value attribute.	Tags
14575	Tempobjects table and directory is not cleaned up after using  RemoteContentPost.	API
14609	Web services not working properly for processing application/xml SOAP responses	Web Services
14617	Mimedecoder - throws exception if "\r\n" occur at 1025 characters	Other
14667	Insite editor with eWebEditPro fiddles with the content	InSite
14678	XMLPost: problem adding flex assets with 2 or more parents with the same name	XMLPost
14693	Deleting a site that contains shared AND revision tracked assets causes those assets to be deleted from all sites	Sites
14720	Publishing status is not reported in a consistent manner when no assets need to be published	Publishing
14726	Pulldown attribute default to the same value when used twice on the form.	User Interface
14733	setsearchedassets with fixedlist set to true throws a SQL Exception	Tags
14738	Blob server cache is not being refreshed correctly for basic asset blobs.	Cache
14745	Unable to install patch 5 on secondary cluster	Installation
14746	asset:save tag does not work correctly when updating parents	API
14748	Multiple money attributes throw exceptions when screen refreshes	FlexAssets
14777	"My Work" screen renders very slowly depending on the number of Workflow groups   After applying this patch, create indexex on the following tables/fields manually:        (tablename) | (fieldname) - GroupParticipants | ownerid - WorkflowGroups_DRoles | cs_ownerid - WorkflowGroups_ERoles | cs_ownerid	Workflow
14778	Workflow Functional Privileges screen is very slow	Workflow
14811	CS-Direct: Multiple (ordered) values of "asset" type using "PickAsset" sorts the list randomly	User Interface
14820	Static publish (export to disk) doesn't update asset date correctly. This causes assets to be stuck in the publish queue even after a successful publish.   (Contact support to cleanup existing data conditions if you face this issue)	Static Publishing
14859	Multiple ordered attributes do not work correctly with Blobs	Flex Assets
14884	404 error not forwarded to error page in WebLogic	Content Server
14909	Deserialization errors during mirror publish do not log assets that caused the failure.	Publishing Mirror
14970	Memory leak in asset manager's dependency logger. Loading a lot of flex assets as part of the same request (such as publishing) causes significant memory leaks, particularly with assets that have a lot of attributes.	Flex Assets
15042	Revision History links not pointing to correct revision media (Doc, Images)	Revision Tracking
15045	Tag asset:deletevoids does not work, and it corrupts the approval subsystem	API
15181	Advanced search for INT attributes do not work	Search
15209	Satellite Server does not parse the responses correctly for a binary response (e.g. application/rss+xml)	Satellite Server
15258	Recommendations get loaded in the asset edit screen even if they do not apply to the asset	CS-Engage Assets
15267	Race condition during approval leads to duplicates in PubKey table. This causes assets to be stuck in the publish queue even after a successful publish. (Contact support to cleanup existing data conditions if you face this issue)	Publishing
15290	Publish sessions created when there's nothing to publish	Publishing Console
	Two new insite tags have been added - insite:editasset and insite:createasset. See below for details	InSite
	Add argument for specifying page output directory and file name. This fix added two optional arguments to render:getpageurl tag - PREFERREDFILE and PREFERREDDIR   e.g. <render:getpageurl outstr="myURL" pagename='test' cid='<%=ics.GetVar("cid")%>' c='Page'>           <render:argument name="PREFERREDDIR" value="MyDirName/"/>           <render:argument name="PREFERREDFILE" value='<%="MyFileName.html"%>' /> </render:getpageurl>	Static Publishing

 

Insite:editasset : For editing assets using the full edit screen or the document management view screen.

<insite:editasset       

      assettype="type of the asset to be edited"

      assetid="asset id of the asset to be edited"      

      [displayname="display_name"]

      [dmv="whether to display the create screen in dmv (Document Management View)"] />

• assettype (required) : Asset type of the asset to be edited.
• assetid (required): Asset ID of the asset to be edited
• displayname (optional): The desired display text for the InSite button 
• dmv (optional): Whether to display the create screen in dmv (Document Management View) by default if it is available.
   

Insite:createasset : For creating new assets using the full edit screen or the document management view screen.

<insite:createasset       

      [assettypes="one or more assettypes to be displayed in the create screen"]

      [startmenu="A specific startmenu item to be used for creating assets"]

      [displayname="display_name"]

      [dmv="whether to display the create screen in dmv (Document Management View)"] />

• assettype (optional) : one or more assettype to be displayed in the create screen. If there are more than one assettype, they need to be separated by commas. If this attribute is not specified, then all assettype will be shown.
• startmenu (optional): A specific startmenu item to be used for creating assets. If this is specified, then InSite will bring up the create screen as if one clicks on the specified startmenu item.
• displayname (optional): the desired display text for the InSite button
• dmv (optional): whether to display the create screen in dmv (Document Management View) by default if it is available.
   

The issues fixed in release 6.3 patch 5 are listed below.

PR	Summary	Component
13931	Safari browser can't handle upload files in CS Direct	UI
14219	Embedded link code on the fly is not XHTML strict compliant. CS will remove the custom parameters when rendering the link for a live site or in static publishing.	Embedded link
14270	RemoteContentPost adds assets to flex parents in the wrong site.	XMLPost
14309	asset.export does not close output writer on exception	API
14331	Assets with an "Include" link become corrupted after using Site Launcher	Site Launcher
14395	Remote Satellite Server cannot render blobs with expiration=never/immediate	Satellite Server
14420	Rollup patch - doesn't install RealObjects attribute editor	Rollup
14441	ISO8859_1 is not charset for internet (says iana.org)	Misc
14445	CS-DocLink Document and Media asset types in FirstSite II not previewing correctly.	CS DocLink
14451	'parentid' in render:getbloburl is not documented	Tags
14484	Satellite server shows a 500 error and a stack trace for a NullPointerException when passed a pagename that does not exist. Property cs.wrapper need to be set to false for this fix.	Satellite Server
14511	CacheManager throws Out Of Memory Exception if large number of dependent assets have to be cleared	Cache
14520	db2 obtains read locks for each row on select queries which are never released causing update to wait indefinitely or timeout based on locktimeout.	Database
14524	Error 500 Internal Server Error page when accessed from a unlicensed URL	Satellite Server
14531	Remote satellite server is echoing the version number Property cs.wrapper need to be set to false for this fix.	Satellite Server
14536	com.openmarket.assetframework.complexasset.AssetManager, method savePublishedObjects() takes a lot of memory. In publishing, CS first identifies all asset types that have publishable assets. For each such asset type, we first load *all* publishable assets and serialize them. On the target, we deserialize *all* published assets of that type before we save them. If there are many assets of a particular asset type, we can run out of heap. With this change, the default behavior remains the same. However, clients can set xcelerate.batchloadsizeonpublish (source) and xcelerate.batchsavesizeonpublish (target) to specify the maximum number of assets to be loaded/saved at a time.	Publishing
14553	render:gettemplateurl generates incorrect URL	API
14557	CS6.3 Patch 4 Installer, Installs FSII Files when FSII is not installed	Rollup
14570	Update the certificate for the tree applet	Tree Applet
14572	Setting com.fatwire.logging.cs.visitor.ruleset=DEBUG breaks saving recommendations on JDK1.4	Engage
14612	Field Copier can't copy updatedby or createdby on asset creation	Flex Filter
14615	Add better portlet support to Satellite Server Deploy a JSR-168 portlet t that extends the com.openmarket.Satellite.portlet.Satellite Ability to pass other page parameters. This means that both the page, as well as the specified page parameters, need to be communicated to the CS through the satellite server. See below for a code snippet	Portal
14616	Add argument for specifying blob output directory. This fix added two optional arguments to render:bloburl tag - PREFERREDFILE and PREFERREDDIR e.g. <render:getbloburl blobtable='MungoBlobs' blobcol='urldata' blobkey='id' blobwhere='1088466917821' outstr='pagelogoURL' csblobid='1088466917821'>    <render:argument name='PREFERREDFILE' value='myfile.ext'/>    <render:argument name='PREFERREDDIR' value='mydir'/> </render:getbloburl>	Publishing
14617	Mimedecode - throws exception if "\r\n" occur at 1025 characters	Misc
14618	Satellite Server: Clean up error reporting in satellite server while deleting files	Satellite Server
14619	Publishing uses a lot of database connections	Publishing
14629	Java script error occurs while editing eWebEditPro in Preview Mode.	Insite Editing
14630	Document Management View screen remains blank when opted for view for the first time.	Document Management
14642	Satellite Server cannot handle mixed-case default arguments	Satellite Server
	IE 7 support

Note for bug fixes 14531, 14440, 14484

Content Server will do the following:

- <appserver>/cs/ContentServer?  - Will generate blank page

- <appserver>/cs/ContentServer?pagename  Will generate blank page

- <appserver>/cs/ContentServer?pagename=  - Will generate blank page

- <appserver>/cs/ContentServer?pagename=InvalidName  - Will generate 404 status code

 

Satellite Server will do the following:

- <appserver>/cs/Satellite?pagename=InvalidName --> will return a 404.

- <appserver>/cs/Satellite?pagename= --> will return a 500 error

- <appserver>/cs/Satellite? --> will return a 500 error

- <appserver>/cs/Satellite --> will return a 500 error

 

Code snippet for 14615

1. Create a java class using the sample code below. To compile this class you would need to include at least sserve.jar and portlet.jar in the classpath

package com.fatwire.sparksample;
import com.openmarket.Satellite.portlet.Satellite;
import com.openmarket.Satellite.portlet.SSRenderParams;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
public class SatelliteYKPortlet extends Satellite
{
     public final void doView(RenderRequest request, RenderResponse response)
     {
          SSRenderParams params = getSSRenderParams(request);
          String s = getInitParameter("PortletParam");
          params.addParameter("PortletParamToCS", s);
          super.doView(request, response);
     }
}
 

2. Create templates or SiteEntry+Elements that you wish to render from within a portlet

Sample code for atf/outer.jsp

<%@ taglib prefix="cs" uri="futuretense_cs/ftcs1_0.tld" %>
<%@ taglib prefix="ics" uri="futuretense_cs/ics.tld" %>
<%@ taglib prefix="satellite" uri="futuretense_cs/satellite.tld" %>
<%@ taglib prefix="render" uri="futuretense_cs/render.tld" %>
<%//
// atf/outer
//%>
<%@ page import="COM.FutureTense.Interfaces.FTValList" %>
<%@ page import="COM.FutureTense.Interfaces.ICS" %>
<%@ page import="COM.FutureTense.Interfaces.IList" %>
<%@ page import="COM.FutureTense.Interfaces.Utilities" %>
<%@ page import="COM.FutureTense.Util.ftErrors" %>
<%@ page import="COM.FutureTense.Util.ftMessage"%>
<cs:ftcs>

<h1>Hello world from outer. <em>PortletParamToCS=<ics:getvar name="PortletParamToCS" /> date=<ics:resolvevariables name="CS.SQLDate" /></em> </h1>
<ics:setvar name="myVar" value="Fred"/>

<satellite:page pagename="atf/inner" >
<satellite:parameter name="myVar" value='<%=ics.GetVar("myVar")%>'/>
</satellite:page>

<h1>Goodbye after outer <em>date=<ics:resolvevariables name="CS.SQLDate" /></em></h1>

<render:satellitepage pagename="atf/inner">
<render:argument name="myVar" value='<%=ics.GetVar("myVar")%>'/>
</render:satellitepage>

<h1>Goodbye after render:satellite <em>date=<ics:resolvevariables name="CS.SQLDate" /></em></h1>

</cs:ftcs>

 

Sample code for atf/inner.jsp

<%@ taglib prefix="cs" uri="futuretense_cs/ftcs1_0.tld" %>
<%@ taglib prefix="ics" uri="futuretense_cs/ics.tld" %>
<%@ taglib prefix="satellite" uri="futuretense_cs/satellite.tld" %>
<%//
// atf/inner
//%>
<%@ page import="COM.FutureTense.Interfaces.FTValList" %>
<%@ page import="COM.FutureTense.Interfaces.ICS" %>
<%@ page import="COM.FutureTense.Interfaces.IList" %>
<%@ page import="COM.FutureTense.Interfaces.Utilities" %>
<%@ page import="COM.FutureTense.Util.ftErrors" %>
<%@ page import="COM.FutureTense.Util.ftMessage"%>
<cs:ftcs>

<h2>Hello world from inner <em>myVar=<ics:getvar name="myVar" /> date=<ics:resolvevariables name="CS.SQLDate" /></em></h2>

</cs:ftcs>

3. Define a portlet in your portal server.

4. For the portlet you defined, add the following section to your portlet.xml.  Modify the following section to match your specific portlet-name, portlet-class, and init-param's with their name and value combinations.

<portlet>
<portlet-name>Test_Flex_Assets</portlet-name>
<portlet-class>com.fatwire.sparksample.SatelliteYKPortlet</portlet-class>
<init-param>
<name>detailsjsp</name>
<value>OpenMarket/Flame/SparkSample/TESTFLEX</value>
</init-param>
<init-param>
<name>com.fatwire.cs.portals.portlet.CSPortlet.config.renderpage</name>
<value>atf/outer</value>
</init-param>
<init-param>
<name>PortletParam</name>
<value>PortletParam_value happy 1234567</value>
</init-param>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>view</portlet-mode>
</supports>
<portlet-info>
<title>Test_Flex_Assets</title>
</portlet-info>
</portlet>

 

 

The issues fixed in release 6.3 patch 4 are listed below.

PR	Summary	Component
14085	Field copier doesn't get copied correctly in Site Replication. This leads to replicated site not being able to run field copier filter correctly when an asset is edited. There is a known design issue where the field copier is not fired during site replication. It is only fired when you edit the asset	Site Replication
14384	Static publish (export to disk) doesn't list the publish queue correctly. This happens when using using <render:getpageurl> tag	Static Publishing
14403	When you delete a page that has been exported to disk, the deleted page stays in the publish queue	Static Publishing
14407	Fix for having & in your URL causes problems with static publish. This will still cause problems in the publish queue when republishing which is a  known issue. So its recommended not to have '&' and other special characters in the URL or generated filename when using Static Publishing	Static Publishing
14411	Multiple (ordered) attribute type not working properly	Flex Assets
14435	Mirror publishing basic assets that contain a file with extended characters in the filename fails.	Mirror Publishing
14436	When the condition enumerated in 14435 occur - publishing fails silently	Mirror Publishing
14437	Publish fails with wrong message (-609) when a element body is missing from an element that is mirrored on every publish	Mirror Publishing
14439	There was a locking on COM.FutureTense.Servlet.ServletRequest.init() which was not needed	Misc

* Due to the addition of RealObjects support - replicating FirstSite II with Copy All option will throw the following error which can be ignored:

        [pagename=OpenMarket/Xcelerate/Admin/SiteBuilder/SiteLauncherPost]

        Error: com.openmarket.xcelerate.commands.ReplicateManagerDispatcher:

        Commence: com.openmarket.basic.interfaces.AssetException:

        Errors sharing or copying assets: <br/>AttrTypes:1148294189528(-101)

        com.openmarket.basic.interfaces.AssetException: source asset not loaded - error -101(number-101 (No description provided))

 

 

The issues fixed in release 6.3 patch 3 are listed below.

PR	Summary	Component
14148	Blobserver now synchronizes caches across a cluster. this can be disabled (to revert to the original behaviour) by setting cc.BlobServerCSync=false. All resultset caches have a default value of cc.TABLENAMECSync=true and you can override it to false. BlobServer instead used to ignore the property and assume a value of false - which meant that it would not synchronize changes across VMs - for performance. The change that was made was to make BlobServer like all of the other resultset caches. This is a change in behaviour, but it can be configured for backward-compatibility by setting the property cc.BlobServerCSync=false. Users not using SS should set this new property to retain the previous behaviour and performance. Users using SS should proceed with the new world default because Satellite Server will be serving the blobs anyway.	Blob Server
14163	Poor publishing query performance.   Added a new query style. A client on their system discovered that running a 'join' style instead of the existing 'subquery' style publishing query improved the performance quite significantly.   Typically which of them performs best in a given installation depends on a number of customer-installation-specific parameters. In order to provide users with flexibility to achieve optimal performance, this solution allows selecting either one of the two styles by changing the value of a new property, xcelerate.publishquerystyle, added to the futuretense_xcel.ini file. This property allows users to select either the join (xcelerate.publishquerystyle = join) or the subquery (xcelerate.publishquerystyle = subquery) syntax for the publishing query SQL generated by CS.	Publishing
14166	No users defined for Workflow error	Start Menu
14167	Adding from tree into an association and attribute together looses the association	Misc
14168	Comment in soap response	Web Services
14171	Revision Tracking Inspect screen shows path instead of contents for URL fields	Revision Tracking
14184	Issue with eWebEditPro preserving original link	Web Editor
14187	CS-DocLink: UTF-8 or double byte characters get corrupted when submitting a new asset with required fields.	CS DocLink
14196	CS63 patch install gives bad instructions on JBoss and does not deploy war	Installer
14199	CS-Desktop errors for no apparent reason: Run-time error '5941'	CS Desktop
14200	CS-Desktop prompts for save even if already saved.	CS Desktop
14211	CS-Desktop allows all subtypes even if there is no start menu for them	CS Desktop
14212	CS-Doclink allows all subtypes even if there is no start menu for them	CS Doclink
14214	Bug with current resin build used for Satellite Server	Satellite Server
14240	commercecontext:getrecommendations: issue with maxcount parameter	Tags
14242	When asset data changes in one cluster member that change is not picked up in the other cluster member's cached pages	Cluster
14245	Can't create start menu with DB2, SQL error	Start Menu
14246	Site Launcher doesn't check license for maximum number of sites	Site Launcher
14250	While installing 632 Rollup Patch on 63 GA on JBoss a dialog related to WebLogic is displayed which is unnecessary	Installer
14257	Insite template has js error when template has many slots	Insite Templating
14287	Posting a file through Remote Satellite Server makes the variable non-binary	Satellite Server
14310	MimeDecoder throws an exception if the first character is a new line character	Mime Decoder
14312	NumberFormatExceptions thrown by <ASSET.GETPUBDEPS>	Tags
14313	Template select based on subtype of flex family doesn't work upon asset creation	Template
14319	Assets that refer only to themselves cannot be deleted	Assets
14320	Field copier flex filter doesn't copy the ID field of the asset. Fixed the inability to properly save a new asset with self references.	Assets
14323	$WSPR not allowed as cookie name	Cookie
	User can exist either under people parent or under any sub node of people parent. The user name has to be unique or it will pick up the name in the order returned.	LDAP
3681	Fix an issue with HttpClient integration where Remote Satellite Server was notified incorrectly about cookies set by the Content Server. This meant that the cache in Satellite server contained an incorrect set of cookies, headers were also not correctly logged, now they are.	HTTP Client
	Support for new web editor - RealObjects webeditor (see the RealObjects readme file for installation details)	WebEditor

 

 

The issues fixed in release 6.3 patch 2 are listed below.

PR	Summary	Component
14089	No possibility to generate forward slash when publishing Blobs	API
14091	RENDER.SATELLITEBLOB called from a JSP was including the rendermode field in the BLOB URL during export	API
14173	Remote SS on WebLogic with httpclient=true causes large numbers of file handles to be produced.	HTTP Client
14180	Added a new property cs.manage.expired.blob.inventory that allows users to force the blob cache to retain the inventory of asset-blobkey mappings so that blobs can always be flushed on SS even if the blob cache is incorrectly configured so that blobs expire on CS before they expire on SS.	Blob Server
14182	Add Link and Include buttons do not show up on Firefox	UI
14183	WSL changes ported over from the 5.x branch	Content Server

 

The issues fixed in release 6.3 patch 1 are listed below.

PR	Summary	Component
3644	CSE crashes when importing projects with blank catalogs. The actual problem was occurring in cases where namespaces were used which caused some folder in the projects to be empty, and this wasn't accounted for in the code. When a file input stream was null and getSizeofFile() was called, it crashed CSE. This has now been fixed. Note: CSE is not fully capable of locking and committing records on import if revision tracking is turned on. If you want to import a project from a zip, you will need to lock the records stored in the zip manually before they can be saved. If you do not do this, you will get a warning stating: no access allowed from revision tracking for each record that inside the zip file. This behavior has always existed and will probably be fixed in future releases.	CSE
13428	Clicking on the Document in MyDocuments portlet pops up a save file window that always specifies Blob Server as filename	Blob Server
13434	Uploading binary files to flex assets with XMLPost does not work	XMLPost
13843	Invalid SQL with StartProcessChoice query on DB2	Workflow
13978	Exception thrown if trying to mirror publish site : java.sql.SQLException: ORA-01795: maximum number of expressions in a list is 1000	Mirror Publish
13982	render:satelliteblob does not work when using c/cid/fieldname set of attributes	Tags
13993	Insite Templating - Save does not work on Tomcat	Insite Templating
13995	Insite Templating control panel throws a JavaScript error on Oracle App Server	Insite Templating
*13998	Language Pack Install fails on Spark, if CS installer was run on the Spark installation and then cancelled	Installer
14005	FirstSite II: Exception thrown when viewing the products page	FirstSite II
*14006	SS packed with Resin not available	Remote Satellite Server
*14007	servletrequest.properties gets corrupted during a reinstall	Installer
14031	FirstSite II - Date Picker attribute editor throws a JavaScript error.	FirstSite II
14036	FirstSite II - Parent is not set for the content asset instances - FSIIAbout and FSIIHomePageText	FirstSite II
*14037	Installer: Need to set jspresponsewrapper=false in Tomcat	Installer
14038	FirstSite II: Attributes not allowed with spaces in names	FirstSite II
14040	PickOrderAsset attribute editor added	Attribute Editor
14047	AssetMaker: Data not saved in optional eWebEditPro field	Basic Asset
14054	Associating asset types with templates in the template screen does not reflect in the template dropdown box when creating assets using these definitions.	UI
14055	Incorrect association fields appear when creating an asset. If the asset types association is set to a particular subtype (asset definition); the asset association still appears in the creation screen for other definitions of the asset type.	UI
*14060	Upgrade on cluster doesn't work. Fix is available as a workaround from support if you are still on CS 6.3 GA build.	Upgrade
14061	Related items don't appear on the edit screen for Products in FirstSite II	UI
14062	eWebEditPro field disappears if you click save too soon	eWebEditor
14063	Thumbnail image doesn't appear on the revision tracking screen	Revision Tracking
14066	Element storage filename is incorrect when you create a template/CSElement	Template
14077	Filetype not displaying for PDF files on the inspect screen	UI
14079	Satellite Server gives an incorrect  message in case of invalid license at CS	Satellite Server
14081	XMLPost/modifyData fails to change the parent of an asset if the parent has attributes.	XMLPost
	Insite Templating - Modified control panel to float on the design palette Edit Template opens design screen in the same window Scrolling beyond the screen is supported Modifications made in design screen to prevent overlap of slots	Insite Templating
	Added a high performance asynchronous logger to complement Traditional Log. Setting org.apache.commons.logging.Log=com.fatwire.cs.core.logging.AsyncLog enables this log. Log messages are written to the file in an asynchronous fashion instead writing at each log request (the time interval can be configured). As the logging subsystem is based on commons logging, users can set any valid logger they prefer (preferably log4j) to get the desired feature and performance benefits. AsyncLog simply provides an easy switch to obtain improved performance when logging and performance are both critical. AsyhcLog performs significantly better, but consumes one additional thread dedicated just for logging.	Logging
	Added support for configuring Satellite Server using system properties in addition to the regular property file, as loaded in the classpath. You can now specify system properties, with the names the same as the regular Satellite Server properties, and Satellite Server will use those values as overrides for the properties found in the satellite.properties file.	Satellite Server
	Performance improvement in CS-CMSPI. Previous release used an Axis library and axis auto-generated code to connect to Content Server, however, the hashcode functions generated by Axis were very inefficient.  These functions were rewritten which resulted in a significant improvement in hashcode performance and the whole system.  Users should upgrade to the latest version of CS-CMSPI to benefit from these changes.	CS-CMSPI
14097	There was a problem in version 6.2 and later of CS-CMSPI (related to the new caching architecture) wherein reading assets could fail to retrieve the proper list of children when under load. This has been fixed.	CS-CMSPI

New Features

What's New in Content Server 6.3?

• InSite Templating enables non-technical users to change the layout and design of Web pages with easy-to-use drag-and-drop tools. These capabilities extend Content Server’s InSite Editing features that allow users edit content from within the context of a Web page to include layout and design changes. IT retains control to ensure overall quality and brand consistency and is able to designate which specific pages and “pagelets,” or page components, are available for editing. As allowed, business users can add, remove, resize, relocate, and reuse pagelets from within the context of Web pages.
• FirstSite II - Additional examples of FatWire best practices under FirstSite II. This allows developers to quickly learn and implement enterprise sites that are robust and scalable.
• HTTP 1.1 - HTTP communication framework enhanced. Native support for HTTP1.1 added. Legacy HTTP 1.0 support has been deprecated. A new API for HTTP communication in Content Server has been provided (see javadocs). Also support for HTTPS communication has been enhanced.
• New functionality and tags added to provide better support for replication of templates and assets. Templates and CSElements support "mapped variables" which associate values to user defined keys. The key is then used in the template logic to look up the value, so that the value is always retrieved dynamically. The render:lookup tag allows map values to be retrieved for the specified template. View the FirstSite II documentation for examples of this technique. Also see the Tag Reference changes section for details on the modified tags.
• Supports upgrade from CS 6.2 and CS 5.x
• Content Server 6.3 also extends Satellite Server’s caching capabilities to include portals.
• This release adds support for Oracle Application Server and the latest version of Java Enterprise Server. Content Server 6.3 is also supported on Solaris 10.
• Enhanced portal integration by extending support for the IBM WebSphere Portal. These portlets support the JSR-168 portlet standard that defines how portals interface with other systems. Included portlets allow users to create, edit, approve, and publish content to a portal site, Web sites, and other media all from within the portal environment.
• Abstract helper class to assist with writing custom URL assemblers. See Javadoc for details.

New in Content Server 6.2?

• Provides the 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 Content Server 5.x, and Content Server 6.1.  Please refer to the document Guidelines for Upgrading ContentServer to v6.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.

            - Also ft.sync needs to be unset during upgrades

• CS interface now displays 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 doesn't support localized stylesheets. 
• This version of Content Server 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 File Server functionality is replaced by Satellite Server. The functionality of Eval Server 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 Bug Fixes in 6.3

Asset

• (#13820) asset:load with invalid object id loads more data than necessary
• (#13572, 13594) Deleting a flex or basic asset does not delete its child relationships

Blob Server

• (#3525) Fixed race condition in cache page and blob rendering. Blob Server's throttle is replaced with KeyThrottle for race condition free throttling. When concurrent requests for the same blob arrive at Blob Server, requests are throttled while one of the requests loads the blob and caches it at the same time. Once loaded, all threads proceed to render it concurrently.

Cache

• (#3610) SysPage is static syncing the access to the DB to get cached pages
• (#3621) Incorrect expiration times set when using timepattern in cscacheinfo.
• (#13613) Cache invalidation. unknowndeps:assettype does not work. The publish operation was not flushing the last asset it published because of bad loop control.
• (#13868) Synchronization causes performance issues on heavily accessed cached table definitions. It is resolved by introducing an immutable instance to be held in cache making synchronization unnecessary.

CS Desktop

• (#13682)  BLOBs not working on CS Desktop

CS Engage

• (#13562) <commercecontext:getrecommendation> does not return assets with Confidence = 1%

Miscellaneous

• (#13571) Unable to create flex filters on DB2
• (#13551) Editing a role's description in CS removes all users assigned to that role
• (#13556) XMLPost does not work on Revision Tracked flex assets.

Publish

• (#13910) Textfield in basic asset starting with CRLF can't be published
• (#13591) Cannot publish from a environment which is running WebServer with https only
• (#13606) ScalarVals of type Enum can't be published

Satellite Server

• Satellite Server ignores blobnocache=true
• (#3623) Co-resident satellite server was failing to initialize properly if it was initialized before Content Server was initialized. This has been fixed in the code and also there is a property change. The property has been renamed from
  
  path.to.futuretense.ini
  to
  contentserver.installation.folder
  
  The new value of the property is the path to the CS install, namely, where FWLicense.xml and futuretense.ini are put. ex. c:\FutureTense.
• Sendmail tag sends corrupt satellite server URLs (refer to satellite.normalizeurl and satellite:normalizeurl tag for detail)

Template

• (#13625) Changing the root element when creating a template fails on preview. Base Site Catalog names are now ALWAYS:       <site>/<assettype>/<tname>, and never include the rootelement name.
• (#13823) Cannot preview a template if root element is saved to a different folder than the default.

Workflow

• (#4359) Workflow graph does not show the last state.

Major Bug Fixes in 6.2

Clients

• (#11921) PDF file conversion by Verity KeyView has been fixed.
• (#10312) Updating non-ASCII characters through CS-DocLink when the encoding of the application server is not UTF-8 will no longer corrupt data.
• (#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.

InSite

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

Miscellaneous

• (#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.

Portal

• (#12196) In the CM Portlet, now you can edit and delete related items for a Page asset.
• (#12182) In the Search Portlet, simple search now works for AssetMaker created assets
• (#12194) The Portal Interface now allows sharing of assets.
• (#12994) Simple search from portal interface now uses verity search engine if verity is enabled for that asset type
• (#11403) In document management portal interface, deleted folders cannot be accessed anymore. Earlier a user was able to inspect and edit the deleted folder.
• (#12129) Publish Target can now contain non-ASCII characters

Publish

• (#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.

Search Engine

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

Site Replication

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

Templates

• (#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 templates with unspecified usage sets a default usage
• (#11981) Copy of a typeless template now makes the new copied template also a typeless template
• (#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

Workflow

• (#12112) Workflow components can be created with all non-ASCII characters in the name. Earlier it was 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.
   

Major Bug Fixes in 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.
• 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 allow users 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.1, 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

 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 6.3 supports. You should also check with FatWire Support to see if there are any known issues with the configuration you wish to use.

Also, refer to the vendor 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.3 works in application servers running J2SDK/J2RE  1.4.1 and above. Make sure that appropriate version of JRE in installed and configured before installing Content Server.

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.

In Internet Explorer, the Tools > Internet Options > Settings > Every Visit to the page must be set to true.

 

TOP

 Installation and Upgrade Notes

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

General Notes

CS Installer needs JVM 1.4.x to work properly. It will not work with previous versions. (#13243)

Windows install fails if there is a space in the path to CS home directory (#13876)

In Application/Portal server JVM options, include the setting -Djava.awt.headless=true

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.

If an installation of CS fails then do the following before retrying the installation:

• Drop the database tables
• Undeploy the .ear/.war file
• Delete the CS installation folder
• Restart the application/web server

Running the installer on top of a failed install corrupts SatelliteServer.properties file. The workaround is to manually set the properties correctly or run the installation after cleaning up the failed install.

ft.sync needs to be unset during upgrades/new setups

In Internet Explorer, the Tools > Internet Options > Settings > Every Visit to the page must be set to true.

 

BEA Application and Portal Server

• For BEA application and portal servers, select the Sun JDK while creating the domains. CS will not work if JRockit JDK is selected.
• When installing CS WebLogic must be in Development mode. After installation, server can be reconfigured to production mode if needed.
• Increase the value of the maximum number of WebLogic JDBC Connection Pools to at least 100 on both publish source and target machines.
• If you are configured with BEA portal or BEA application server and using LDAP for user or site management, to avoid a memory leak contact BEA to obtain patch CR 185315. Install CR 185315 as instructed by BEA.
• In dir.ini, set property jndi.poolConnections=true.
  JNDI connections can now be "pooled." Two properties must be configured in dir.ini: (1) jndi.poolConnections=true. (2) jndi.poolsize (size of the pool). This setting defaults to 20 connections.

IBM WebSphere Application and Portal Server

• IBM JDK has a bug on x86 platforms that causes CS to fail under certain situations. IBM will fix this in the upcoming JDK releases. In the meanwhile they recommend to set the following option:
  
  JITC_COMPILEOPT NQDEADSTORE{class}{method}
   
• This issue has been fixed in IBM SDK 1.4.2 SR5 and was released as part of WebSphere 6.0.2.11.

Sun ONE Application and Portal Server

·                Sun JES 2005Q1 has an issue with loading the CS loggers hence futuretense.txt is not created. This has been fixed by Sun in JES 2005 Q4.

·               SUN JES Portal - Portlets will not be correctly installed if context is changed from 'cs' or 'servlet' (#13722)

JBoss Application Server

• JBoss application server is unable to load the Verity DLL's correctly.

Tomcat

• Set cs.jspresponsewrapper=false in futuretense.ini

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

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:
• LANG=en_US.UTF-8
• LC_ALL=en_US.UTF-8
• export LANG
• export LC_ALL
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:

• Name= default.client.encoding Value=UTF-8
• Name=file.encoding Value=UTF-8

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:
• Name: LD_LIBRARY_PATH
• Value = $LD_LIBRARY_PATH:/Content-Server-install-dir/bin
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:
• Name: PATH
• Value = drive letter:\Content-Server-install-dir\bin
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.

Upgrade Notes

Backup the database, application server and the installation folder before an upgrade

If the CS installation being upgraded has LDAP integrated, then there is no need to disable LDAP. Before upgrading such an installation make sure that all the properties in dir.ini are set correctly.  Also set jndi.poolConnections=true and set jndi.poolsize in dir.ini. This will pool the LDAP connections.

While upgrading, do not select a new sample site to be installed.

Turn off revision tracking for the following assets and tables before running the upgrade process:

• Link
• Page
• CSElement
• Template
• SiteEntry
• SiteCatalog
• Query
• ElementCatalog
• System* (all Content Server tables in the database starting with System)

If an upgrade process fails in between, restore the system to the original state (for all components - database, application server and CS installation folder) before restarting the upgrade process again.

Set  cs.privuser and cs.password to blank in futuretense.ini for better performance. Currently the installer sets it which in itself is correct but reduces performance (#3608)

Before upgrade, set the following property in futuretense.ini: secure.CatalogManager=false

Attribute Editor Elements variables name have been changed in 6.x. To upgrade a custom attribute editor from version 5.5.2 and below, the following steps are needed:

1. Open the element files under $CS_SharedDirectory/elements/OpenMarket/Gator/AttributeTypes
2. Replace all Variables.AttrName with Variables.cs_SingleInputName if it is not preceded with Counters.TCounter (for single valued attribute)
3. Replace Counters.TCounterVariables.AttrName with Variables.cs_MultipleInputName (for multiple valued attribute)

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 system but is available on the installation media for reference. 

TOP

Clustering Notes

The file ftFileLock.dll/libFTFileLock.so must exist in the path for clustering to work properly.

Content Server uses the java.io.tmpdir specified by the JVM and creates temporary files and sub-folders within. In some instances, if Content Server is configured to use multiple JVMs (a.k.a. vertical cluster) or if the box is configured with multiple Content Server environments (i.e authoring and staging on the same box), there is a risk that all JVM or environments will use the same temporary directory specified by java.io.tmpdir. It is advisable to configure each JVM to use its own java.io.tmpdir (#13684).

Application Servers:

Copy ftFileLock.dll/libFTFileLock.so file into the lib directory of the Application server or add the location to the path statement for the server. Restart the server. e.g., In WebSphere - add to the "PATH" using the WAS admin console in "Process Definition-Environment Entries".

Operating System:

The ftFileLock.dll/libFTFileLock.so should be in the library path.

·                On Solaris:    LD_LIBRARY_PATH

·                On AIX:        LIBPATH

·                On Linux: Add this to the ldconfig’s database on Linux.
1. Edit the file /etc/ld.so.conf and add the location of libFTFileLock.so on a new line then save and run ldconfig
2. You can test that this was successful by running ldconfig –p | grep libFTFileLock.so if nothing comes up then it was not found, confirm that you have the correct path.
3. Add the path to libFTFileLock.so into shell environment from which you execute the WebSphere Deployment Manager and Application servers (startServer.sh and startNode.sh)
 

TOP

Known Issues in CS 6.3

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

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.

(#13719) Log file futuretense.txt is not created when using Sun JES 2005 Q1.

This is fixed by Sun in JES 2005 Q4 release

(#3651) In BEA LDAP integration, CS does not ask realm name from user and assumes default of 'myrealm'.

TOP

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

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.

Login to Content Server will fail 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

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.

(#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.

(#3617)  Content Server doesn't handle field length correctly when using UTF-8.

e.g. The maximum length of asset's name is 64 characters in html form (input type="text" maxlength="64"). If I enter 64 ä-letters into the text field, SQLException occurs. That happens because the name field is VARCHAR(64), which is 64 bytes which is incorrect for UTF-8.

(#13270) Case sensitive database causes error on call to CatalogList for catalog template

(#13765) CatalogManager doesn't support Oracle users with access to multiple schemas

When an Oracle database user has access to multiple schemas, all these schemas are read when CatalogManager tries to find the table structure of tables.

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

eWebEditPro

(#13626) Editing fails if MAXLENGTH is specified for an eWebEditPro field.

Setting the MAXLENGTH attribute in eWebEditPro does not allow an asset to be saved. This requires a manual edit in an eWebEditPro file. Edit ewep.js and search for "var editorEstimateContentSize=". Change whole to body e.g.
    var editorEstimateContentSize="whole";
        to
    var editorEstimateContentSize="body";

(#13833) Attributes with eWebEditPro support do not work if they are placed right below any other attribute that has a button

(#13865) Links to anchor tags created with eWebEditPro within InSite editing have the complete URL encoded which causes problems when content is published.

TOP

FirstSite II

(#13963) Site Replication throws exceptions when replicating FirstSite II with only Core and Document Schema installed.

(#13964) Cannot create a media asset when only the following FirstSite II components are installed - FSII Core, FSII Store Schema and FSII Store Demo Data

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.

TOP

InSite Editor

(#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.

 (#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 InSite Editor, then InSite Editor will close.

(#13061) InSite Editor 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 parts of the pagelet. The current implementation keeps track of all direct dependencies, including access permission and workflow state, which are all directly related to the asset instance.  The workaround is to flush CS and SS cache and the pencil icons will start showing correctly.

TOP

InSite Templating

(#13993) Save does not work on Tomcat

(#13995) InSite Templating control panel throws a JavaScript error on Oracle application server

TOP

Installer

(#13100) Error messages in futuretense.txt while installing CS

e.g. Exception checking for url http://<machinename>:<port>/futuretense_cs/formerror.html

(#13876) Windows install fails if there is a space in the path to CS home directory

TOP

Internationalization

(#13471) CS does not support table names and column names with multi-byte UTF-8 characters in Oracle 9i, MS- SQL Server, and DB2. 

It's recommended not to use multi-byte characters in the following:

·                      UserNames

·                      ACLNames

·                      RoleNames

·                      Template Names

·                      AssetType Names and FieldNames

TOP

Java API

(#1513) Content Server requires column names to be 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

KeyView

(#13974) KeyView doesn't work correctly for translating Microsoft Excel to HTML on Linux

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.

(#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 does not automatically get checked in.

(#13870) ics.sendmail does not work when using authenticating SMTP server

(#13987) Preview operation picks up incorrect Satellite Server URL if multiple Remote Satellite Servers are registered

(#16400) RealObject is does not load on IE7, but does on IE6

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

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.

(#13915) Revision history links do not point to the correct revision media (Doc, Images)

The data stored in revision history is correct but links in the inspect screen of the revisions are not pointing to the correct, uploaded revision files. The data links are all pointing to the latest uploaded revision file which is incorrect.

 

TOP

Satellite Server

(#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. Workaround is to use a cookie to set the remote IP address.

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.

(#13881) JBoss cannot load Verity DLLs

(#13855) Verity indexes get corrupted during publishing if set up in asynchronous mode.

Verity indexes get corrupted during publishing if set up in asynchronous mode but work correctly if set up in synchronous mode.

(#13873) Editing assets in clustered environment with Verity in asynchronous mode crashes Verity.

(#13994) Verity indexing operations crash the JVM on Linux after installing a Verity Locale kit.

Using any Verity function after installing the Verity locale kit causes the JVM (running the application/portal server) to crash.  This happens only on Linux environments; Verity works correctly before the locale kit is installed.

TOP

Site Launcher

(#unknown) 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 re-approved in the source site after site replication.

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.

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

(#13768) asset:loadrevision does not work and throws an exception.

(#13982) render:satelliteblob does not work when using c/cid/fieldname set of attributes

Workaround is to use the satellite:blob tag and specify the parentid attribute with a value set to "asset-cid:c" where c and cid are replaced with the actual values.

TOP

Templates and Elements

(#3210, #13653) JSP pages rendered have too much white-space

(#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.

(#13942) JSP is not always regenerated after a publishing to a cluster.

Workaround is to restart the cluster members once the publish is complete

 

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 an 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 Visitor 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.

(#13097) 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 these 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

Users and 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 the user 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 non-existent user attribute or for a non-existent user.

(#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.

(#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.

(#13432) Updates made to ACLs are not reflected consistently

If updates are made using CS User Admin Screen, they are reflected immediately. However, if ACLs are updated directly in LDAP server, then we recommend that you

1.                   Restart your portal/Application server for the changes to take effect or

2.                   Flush ACL cache using the URL
http://localhost:7001/spark/CatalogManager?ftcmd=flushcatalog&tablename=SystemUsers&authusername=admin&authpassword=xceladmin

If a user without any ACL logs into CS; CS allows the user to perform only those operations that a user with Browser ACL can perform.

(#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 Content Server Management Tools interface or from SystemUsers in Content Server Explorer, the Advanced Search UI screen will not render. The workaround is to delete the corresponding user entry from the UserPublication table

(13560) Call Stack is printed in futuretense.txt whenever a role is updated or deleted in LDAP

A call stack is seen in futuretense.txt on WebLogic 81 portal installations (See below). This is a debug message and does not indicate any problem with the LDAP integration.

May 13, 2005 3:30:05 PM][CS.AUTH][INFO] Print Call stack. Delete Role WorkflowAdmin from database and from ldap. Page name is OpenMarket/Xcelerate/Installation/AddRole
java.lang.Exception: Inside delete method of FlatLDAPRoleManager.
at com.openmarket.xcelerate.roles.FlatLDAPRoleManager.delete(DashoA14174)
at com.openmarket.xcelerate.roles.RoleManager.save(DashoA14174)
at com.openmarket.xcelerate.roles.FlatLDAPRoleManager.save(DashoA14174)
at com.openmarket.xcelerate.commands.RoleManagerDispatcher.Save(DashoA14174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.openmarket.framework.commands.Dispatcher.Execute(DashoA14174)
....

(#13599) DefaultReader is not needed in CS if integrated with an external LDAP

This is an inconsistency between database and LDAP user management. DefaultReader is needed in database (SystemUsers) in case of native user management but you don't need this user in any system in case of external/LDAP user management.
 

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 to another port number.

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

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

Page debugger fails when trying to debug JSP pages.

TOP

Workflow

(#8211) Cancelling 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.

(#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.

(#16394) "Error finishing assignment: -12062 reason: Exception in CompleteAssignmentSeed Workflow step requires assignees" is received in Desktop

When an asset that was created in CS-Desktop is assigned users to the workflow in CS-Direct and then the asset is accessed via CS-Desktop to complete the remaining workflow fields, the message above will appear. The workflow status changes to completed following this message in CS-Direct, the link is disabled in CS-Desktop.

 

TOP

XML

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

(#13735) XMLPost can malfunction when reading files from dir with mixed extension names

(#13434) Uploading binary files to flex asset with XMLPost does not work

(#13990) XML Post fails to import UTF-8 characters correctly if encoding is specified

Import is successful if you remove the encoding <?xml version="1.0" encoding="UTF-8" ?> and run XML Post

TOP

 

CS Express

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

(#13156) Uninstalling the BEA that came with CSExpress, does not delete the Start Menu folder

(#13157) Uninstalling CSExpress does not remove the FatWire directory and some of its files

TOP

CS Portal Interface

 

TOP

CS Clients

CS-Desktop

(#13648) 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 the 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, #12962) CS-Desktop toolbar does not show up when Word is used as email editor in Outlook. Also on Windows XP, it does not load correctly

If Outlook is already open, CS-Desktop toolbar will not be displayed when MSWord is opened to connect with Content Server.  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.

Workaround: CS-Desktop is a word Add-in and not just a template. There is a very subtle difference between the two of them especially in the way they are loaded and run. The workaround for this bug is to move the CS-Desktop.dot from Word's startup folder to somewhere safe for example in c:\Program Files\FatWire\.
After the move, when you start Word or Outlook, the Content Server toolbar add-in won't be loaded. If you need to load it, Click on Tools --> Templates and Add-Ins -> Click Add and browse to the CS-Desktop.dot, add it and click okay, it will then load our CS-Desktop add-in.

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

(#8125) 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.

(#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, 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 Content Server 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 WebServer.

(#13413) Unable to login to CS from CS Desktop using HTTPS as the validation for URL fails.

TOP

CS-DocLink

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

(#13934) Help link on CS DocLink does not work.

The help file is present in the installed folder but not registered correctly.

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.

(#3644) CSE crashes when importing project with an empty catalog

Workaround is to make sure that all the catalogs in a project have at least one record.

TOP

 Contacting FatWire 

To contact FatWire Corporation about technical support for your product:

Web: http://support.fatwire.com

TOP

 

FatWire	Copyright © 2002 2003 2004 2005, 2006, 2007,2008, 2011 FatWire Corporation All rights reserved.