June 15, 2011
Copyright 2002-2011 FatWire Corporation All rights reserved.
Welcome to the release notes for Content Server v7.6. For the latest release notes, check the FatWire e-docs web site. The release notes contain descriptions of new features, changes in functionality, known issues or limitations, and other last-minute information about Content Server 7.6.
For additional information, contact FatWire technical support.
Patch Release Name and version
Patch Release date
CS 7.6 Patch 1
ContentServer-bld-32 Revision: 137153
|June 15, 2011|
ContentServer-bld-675 Revision: 134577
|March 31, 2011|
The Content Server 7.6 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.
Content Server 7.6 Patch 1 has important changes as noted below:
eWebEditPro is no longer shipped or supported
Content Server 7.6 introduces new features to help developers and system administrators streamline the process of building and maintaining Content Server (CS) web sites. The CS 7.6 package also includes HF1 which contains important updates and should be applied immediately following rollup to 7.6.
Allows system administrators to gather, review and download the information about the Content Server environment directly from the Advanced Interface. The information includes:
- Configuration and property file contents, jar versions, system variables
- Database table design, row counts, and query times for specified tables
- Thread information
- Content Server’s log file
- Results of the file system test
- System Tools allow administrators to configure log4j loggers from the Advanced Interface if log4j is enabled.
CSSO facility is a new customization layer included in the FatWire WEM Framework authentication system, which is built over the Central Authentication Service (CAS). The CSSO facility contains authentication extensions that you can use to create a custom SSO solution, without modifying the CAS configuration. A Spring configuration directs the injection of these extensions into the CAS configuration to implement the desired login behavior.
AssetCache is a new component introduced into the inCache framework. It is a memory-based system, built to improve Content Server’s performance by absorbing load that would otherwise impact the database. AssetCache is available on Content Server nodes.
Flex Filters API is a formalized API that is now available to build filters associated with asset types. When assets of those types are saved, the filters perform operations on the assets.
Rollup Installer enhancements in CS 7.6 provide options to:
- Migrate to log4j automatically during rollup
- Cluster CAS during deployment
(#24292) A new property is added to control how FCKEditor behaves when you include assets within text. When you include assets that use <div> tags, FCKEditor does not change them to <span> tags. If you want FCKEditor to retain the earlier behavior of change <div> tags to <span> tags, add this property and set it to true. For further information please refer to the Property Reference Guide.
The database performance utility has been updated with CS 7.6 to include Mungo and AMap tables.
Workflow locking mechanism has been improved by eliminating a workflow engine lock for all workflow operations
The REST interface now includes an additional API to return site plan navigation.
See the SPD on FatWire e-docs web site for the list of J2EE components (web servers, application servers, DBMSs, JDBC drivers, etc.) that Content Server 7.5 supports. You should also check with FatWire Support to see if there are any known issues with the configuration you wish to use.
Refer to the vendor release notes for all J2EE components to obtain the latest e-fixes, patches, and service packs required to run your components.
A common problem encountered is a type of JSP Exception such as: "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 the JVM with a -verbose option.
Windows install will fail if there is a space in the path to CS home directory
If your installation of Content Server fails, take the following steps before rerunning the installation:
Drop the database tables
Undeploy the .ear/.war file
Delete the CS installation folder
Restart the application/webservers
Installing a WebServer between Remote Satellite Server and Content Server, you must set the cookie header property http.protocol.single-cookie-header=true in the httpaccess.properties file and place it in the Remote Satellite Server Install Directory /WEB-INF/Classes
Ensure that the maximum number of open files handles for your publish destination Operating System is set to 65000, the source should be at least 32000. These numbers are only a guideline and may need to be adjusted depending on the type of data and the size of the publish operation.
To install CS75 GA package on Windows 2008R2, add -Dos.name="Windows Server 2008" in the JVM startup
If using MSSQL2008 and MSSQL2008R2, the following changes to AdvPub.xml are required for publishing:
1. Set "numParallelTasks" value="1"
2. Replace this line:
<bean id="ApprovalGroupingStrategy" class="com.fatwire.realtime.ApprovalAggregatingGroupingStrategy" singleton="false"></bean>
<bean id="ApprovalGroupingStrategy" class="com.fatwire.realtime.ApprovalGroupingStrategy" singleton="false"></bean>
Be sure to review the known issues listed in the Installer - Upgrades section before you begin your upgrade.
Asset Type Name Restrictions
The following lists display the asset type names used by Content Server.
Beginning with the release of Content Server 7.5, all administrative database tables created by FatWire in Content Server will be prefixed with “FW_”. Asset types should not be created with a prefix of “FW_”.
If you have created asset types using names in our Standard Asset list, upgrade scripts will encounter errors. Manually back up their data and elements before starting the upgrade process to preserve these assets. If you install the sample sites, do not use the Sample Site asset type names listed below when creating custom asset types.
Standard assets - These asset types are created by default:
Asset Types installed by the FirstSite II Sample Site:
Asset Types installed by the Burlington Financial Sample Site:
Asset Types installed by the GE Lighting Sample Site:
Asset Types installed by the Hello Asset World Sample Site:
Asset Types installed by the Spark Sample Site:
Restricted Names for Asset Types:
The following names (in alphabetical order) are reserved for Content Server's use and must not be assigned to custom asset types:
ActiveList, AdvCols, AdvCols_Dim, AdvCols_DimP, AdvCols_Extension, AdvCols_ManRec, AdvCols_Publish, AdvCols_SSpec, AdvCols_Types, ApprovalQueue, ApprovedAssetDeps, ApprovedAssets, AssetDefaultTemplate, AssetEditPane, AssetExportData, AssetIndexSourceConfig, AssetListener_reg, AssetPublication, AssetPublishList, AssetQueues, AssetRelationTree, AssetStubElementCatalog, AssetSubtypes, AssetType, Assignment, AssocNamed, AssocNamed_Subtypes
CARTSET, Category, CCFunction, CCRoles, CheckOutInfo, Collection, Collection_Dim, Collection_DimP, Comparators, ComplexAssets, CSElement, CSElement_Arg, CSElement_ArgVals, CSElement_CArgs, CSElement_Composition, CSElement_Dim, CSElement_DimP, CSElement_Map, CSElement_Publish, CSEvents
DeliveryType, Dimension, Dimension_Dim, Dimension_DimP, DimensionSet, DimensionSet_Dim, DimensionSet_DimP, DimensionSet_EDim, DistributionList, dtproperties,
ElementCatalog, EmbeddedReference, externalclients, externalclientsconfig
Filters, FlexAssetDef_reg, FlexAssetTypes, FlexFilterTypes, FlexGroupTypes, FlexGrpTmplTypes, FlexTmplTypes, FunctionPrivs
HFields, HFields_Dim, HFields_DimP, HFields_Extension, HFields_Publish, HistoryVals, HistoryVals_Dim, HistoryVals_DimP, HistoryVals_Extension, HistoryVals_Publish ,
Link, Link_Dim, Link_DimP, Linkset, Linkset_Dim, Linkset_DimP, Locale, LocaleMap, LocaleTree
MenuArgs, MenuLegalArgs, MimeType, MungoBlobs
ObjectPrivs, ObjectPublish, ObjectRegistry
Page, Page_Dim, Page_DimP, Previewgen, Promotions, Promotions_Dim, Promotions_DimP, Promotions_Extension, Promotions_Goals, Promotions_ManRec, Promotions_Publish, PubContext, PubKeyTable, Publication, Publication_Replicate, PublicationTree, PublishedAssets, PubMessage, PubSession, PubTarget, PubTarget_Distribution, PubTarget_Satellites, PubTarget_Sites
Query, Query_Dim, Query_DimP
Rank, Remove, Replicate, Replicate_Assets, Replicate_AssetTypes, RTInfo, RuleMap, RuleSetDef
SaveSearch, SaveSearch_Roles, SaveSearch_Sites, ScalarVals, ScalarVals_Dim, ScalarVals_DimP, ScalarVals_Extension, ScalarVals_Publish, scratch, SearchEngineMetaDataConfig, Segments, Segments_Dim, Segments_DimP, Segments_Extension, Segments_Publish, SiteCatalog, SiteEntry, SiteEntry_Dim, SiteEntry_DimP, SiteEntry_Publish, SitePlanTree, Source, StartMenu, StartMenu_Roles, StartMenu_SChoices, StartMenu_Sites, StartParticipantChoice, StartProcessChoice, StatusCode , SystemACL, SystemEvents, SystemIdGenerator, SystemInfo, SystemItemCache, SystemLocalAlias, SystemLocaleString, SystemPageCache, SystemRemoteAlias, SystemSatellite, SystemSeedAccess, SystemSQL, SystemTransforms, SystemUserAttr, SystemUsers
TempBlobs, Template, Template_Arg, Template_ArgVals, Template_CArgs, Template_Composition, Template_Dim, Template_DimP, Template_Map, Template_Publish, Template_Subtypes, Template_Thumb, Template_TName, TempObjects, TNames, TreeTabs, TreeTabs_Items, TreeTabs_Roles, TreeTabs_Sect, TreeTabs_Sect_Roles, TreeTabs_Sect_Sites, TreeTabs_Sites, Type
UITag, UITagItem, UIUserLoggedInDetails, UnassignedObjects, UserPublication
VMACCESSKEY, VMACCESSMETHOD, VMATTRIBUTECATEGORY, VMHISTORYATTRIBUTEDEF, VMHISTORYATTRIBUTEFIELD, VMHISTORYATTRIBUTEFIELDDEF, VMSCALARATTRIBUTEDEF, VMVISITOR, VMVISITORALIAS, VMVISITORSCALARBLOB, VMVISITORSCALARVALUE, Any name that starts with VMz
Workflow, Workflow_ARols, Workflow_Assets, Workflow_DlgA, Workflow_Roles, Workflow_Sites, Workflow_TActs, WorkflowAsgActions, WorkflowAsgsAction, WorkflowConditions, WorkflowDlgActions, WorkflowDlkActions, WorkflowGroups, WorkflowGroups_Dlock, WorkflowGroups_DRoles, WorkflowGroups_ERoles, WorkflowGroups_Sites, WorkflowGrpActions, WorkflowObjects, WorkflowObjsAction, WorkflowParticipants, WorkflowProActions, WorkflowRoutes, WorkflowRoutes_Comp, WorkflowRoutes_Cond, WorkflowRoutes_Dead, WorkflowStatusCode, WorkflowStatusCode_TActs, WorkflowStpActions, WorkflowSubject
For a given database, the name of a flex asset type must have eight characters less than the maximum number of characters that are allowed for database table names.
For a given database, the name of a basic asset type must have five characters less than the maximum number of characters that are allowed for database table names.
For security reasons, we recommend that you allow only internal access to the following servlets:
In Internet Explorer, the Tools > Internet Options > Settings > Every Visit to the page must be set to true.
To change the character set for Internet Explorer 6.0, click View > Encoding > Unicode (UTF-8).
Tree applet conflicts will exist if you have both CS 6.3 and 7.x running on the same machine on the same port. To resolve a Java applet issue:
1) Right-click the JVM icon in the system tray.
2) Select 'Open Control Panel'.
3) In the JVM Control Panel...
a. Navigate to the General tab.
b. Click the 'Delete Files...' button in the Temporary Internet Files section.
c. Click OK to delete the temporary Java internet files.
4) Right-click the JVM icon in the system tray again.
5) Select 'Open Console'.
6) Within the Console, type 'x'. This will clear the classloader cache.
7) Restart your browser.
For WebLogic installs, the following changes need to be made to the bea_omii.ini file:
1. Set CSInstallbManual=true
2. Uncomment CSManualDeployPath=C\:/bea/weblogic10/user_projects/domains/mydomain/applications and set to the path for the installer to explode the war for deployment
FCKEditor and Online Image Editor ship free with Content Server
CS 7.6 Patch 1 Installs
If you are rolling up from CS 7.5 Patch 5, and were using inCache earlier, you must flush your cache after rollup as the caching mechanism has been changed
CS 7.6 Patch 1 contains all publicly available Hot Fixes released for CS 7.5 patch 5 up to and including HF26 as well as CS 7.6 HF1 and HF2
CS 7.5 Language Pack:
The Language Pack release is a rollup installer which can be installed on CS 7.6 Patch 1. There are two means of installation for the Language Pack:
a. GUI Install which is initiated by executing csrollupinstall.bat or csrollupinstall.sh
b. Silent install by following the directions below:
Note - these steps are required even if you have run an installation of Content Server previously as the most updated files must be used
1. In the CS Install folder\ominstallinfo locate omii.ini
2. Place this ini file in a folder other then <installation_folder> and rename it
3. Edit the renamed omii.ini, add the following property:
To install the Italian Language Pack - it_IT=true
To install the Japanese Language Pack - ja_JP=true
To install the German Language Pack - de_DE=true
To install the French Language Pack - fr_FR=true
To install the Spanish Language Pack - es_ES=true
To install multiple Language Packs at the same time, each property must be on its own line - for example, to install French and German Language Packs:
4. Go to the directory where you extracted the rollup package, edit the install.ini
4. Set nodisplay=true
5. Uncomment the loadfile property and set it as loadfile=<path and name of renamed omii.ini from step 1>
Note: While editing the ini file make sure you specify the file system path correctly for example, for windows:
CSInstallDirectory=C\:/csinstall or c\:\\install
6. Edit csCombinedLangPackInstall.bat or csCombinedLangPackInstall.sh:
Locate COM.FutureTense.Apps.CSSetup –files CombinedLanguageInstall.xml
Change this line to COM.FutureTense.Apps.CSSetup –silent –files CombinedLanguageInstall.xml
When deploying inCache, the default RMI setting will discover any other inCache systems deployed on the same subnet. To avoid multicast issues, configure RMI to connect only to localhost or eliminate lookup and provide a list of servers to be communicated with. For further information please refer to the Developers Guide inCache section, the RMI settings are specified in the cs_cache.xml and ss_cache.xml files.
This process is enabled when stalePages is set to true
Resolved an issue where it was possible to flush the blob server cache without proper authentication
Resolved an issue where it was possible to overwrite the JSESSIONID value using CookieServer
NOTE - this is fixed for new basic assets, to apply the change to existing basic assets, the following strings need to be replaced in the element "OpenMarket\Xcelerate\AssetType\<BasicAssetName>\SearchForm.xml":
<setvar NAME="name" VALUE="Name"/>
<setvar NAME="category" VALUE="Category"/>
<setvar NAME="updatedby" VALUE="Modified By"/>
<setvar NAME="createddate" VALUE="Created Date"/>
<setvar NAME="createdby" VALUE="Created By"/>
<setvar NAME="updateddate" VALUE="Modified Date"/>
Replace above lines with the following lines:
<XLAT.LOOKUP KEY="dvin/AT/Common/Name" VARNAME="name"/>
<XLAT.LOOKUP KEY="dvin/UI/Admin/Category" VARNAME="category"/>
<XLAT.LOOKUP KEY="dvin/UI/Search/Modifiedby" VARNAME="updatedby"/>
<XLAT.LOOKUP KEY="dvin/UI/Search/CreatedDate" VARNAME="createddate"/>
<XLAT.LOOKUP KEY="dvin/Common/CreatedBy" VARNAME="createdby"/>
<XLAT.LOOKUP KEY="dvin/UI/Search/ModifiedDate" VARNAME="updateddate"/>
We have introduced 2 new properties in futuretense.ini to override the current limit of 1024: Refer to the Property file reference for further information
A button "Delete this <attribute>" has been added to enable the ability to delete additional multi-valued string attributes in Advanced UI
Clients not using locale can eliminate these queries by following the directions in the Property Reference to turn these off
Reduced the frequency of the log messages to one
Other Important Issues fixed prior to CS 7.6 which are also applicable to CS 7.6
Effective September 2009, Content Server no longer ships with KeyView. In place it ships with other document transformation open source libraries
The patch 2 or higher rollup installer will:
Both full text search and Desktop will use the new transformation libraries.
This enhancement provides the ability to specify URLs to be regenerated. An additional module is required to enable this functionality which can be requested from FatWire Support
To enable new behavior, please make following configuration changes:
On the editorial system
1. Make sure that ft.usedisksync & ft.sync of futuretense.ini are set correctly; ft.sync and ft.usedisksync should not be empty and should be the same value on all cluster members.
2. xcelerate.lockdir property in futuretense_xcel.ini must not be empty and must have the same value on all cluster members
3. Specify switch -Dinsite.saveslotsonly=true and -Dinsite.usemarkerassets=true in VM options (for all clustered members)
4. Create Page associations - these must be created as specified below for this functionality to work correctly:
1. Create CompositionSlot_C flex asset type:
a. create a flex family whose Flex Asset type is called CompositionSlot_C.
b. create the following attributes:
•ownerid (Value Type:asset, Asset Type: Template, Mirror Dependency Type: exists)
•slotname (Value Type:string)
•site (Value Type:string)
•context (Value Type:string)
•template (Value Type:string)
•variant (Value Type:string)
•arguments (Value Type:text)
•state (Value Type:string)
c. create a flex definition named CompositionSlotDef which contains all above attributes as optional
d. add the following Named Association to the CompositionSlot_C asset type
Child Asset: Any
CompositionSlot_C Subtypes: Any
Mirror Dependency Type: Exact
Multivalued Association: Single Valued
2.Add the following association to the Page asset:
Child Asset: Any
Page Subtypes: Any
Mirror Dependency Type Exact
Multivalued Association: "Multivalued"
5. If publishing from development to editorial will overwrite the template composition table - to avoid this overwrite use the Template Composition Preserver
Module available from FatWire Support
On the delivery system:
1. Run the following query to install the asset event listener (NOTE: Do not register this event on editorial system where pages are being built using
insert into AssetListener_reg values (1234567, ‘com.openmarket.xcelerate.controlpanel.CompositionSlotEventListener’, ‘Y’
Limitations of this implementation:
1. CompositionSlot_C Assets’ Lifecycle
a. CompositionSlot_C assets; which act as proxies for publishing composition information; do not have a
well-defined lifecycle because they are not deleted by the system when they are obsolete.
b. The maximum number of CompositionSlot_C assets is (number of pages in all sites) x (number of slots
c. If an existing slot is modified, the corresponding CompositionSlot_C assets is updated and no new
assets are created.
d. It is possible to remove CompositionSlot_C assets
2. Impact of Empty Slot Contexts
It is recommended to ensure that context values are non-null for all slots. The system does not handle null context
correctly in some cases, which can lead to duplicate CompositionSlot_C assets created for the same slot and
other unexpected behavior.
3. Impact of Not Using Wrapper Pages
If the template that renders the slots is not rendered through a wrapper, the context values for all of its slots will be
empty. All templates that contain slots must be rendered through wrapper pages.
4. Customized Context Values
When setting custom context values, ensure that each unique slot has a distinct context value. Colliding context
values could lead to inadvertently overlapping slots across different pages (if Ownerid, Site, and Slotname are
the same) and could cause content to be overwritten and/or repeated across unrelated pages that happen to use
the same slots.
As of patch 4, values of date fields are stored to millisecond accuracy in Content Server’s database, in the format hh:mm:ss.SSS. The JVM flag -Dcs.useMilliseconds determines whether the millisecond portion of the timestamp can be read and how entries in the Lucene search index are affected. The use of -Dcs.userMilliseconds=true is only supported for use in CS systems that are integrated with Community Server.
If -Dcs.useMilliseconds=false (or not set), dates are written to the database to millisecond accuracy, but the millisecond portion of the timestamp cannot be read. As a result, when the Lucene search engine reads Content Server’s database while indexing, it leaves the timestamps of index entries in their existing format.
Milliseconds can be read only by APIs and tags, as long as the following conditions hold:
• The JVM flag -Dcs.useMilliseconds is set to true.
• After patch 4 is installed, the Lucene Index Conversion Tool was run to include milliseconds in timestamps (http://<hostname:port>/context/ContentServer?pagename=OpenMarket/Xcelerate/Search/IndexDateChangeUtil).
All timestamps for Lucene index entries are then assigned the value 000 in the millisecond position, which is updated to actual time when the entries are updated.
Switching back to -Dcs.useMilliseconds=false after a Lucene index has been updated with millisecond information does not require re-indexing or reversing the conversion in any way. Setting the -Dcs.useMilliseconds flag to true always requires running the Lucene Index Conversion Tool.
com.fatwire.logging.cs.file to monitor file path, file content size, and operation time if it is great than 300 ms.
If an editorial user is added to the UI and that user is not given SiteGod privileges, the user cannot edit Recommendation assets if they are more than static list recommendations. The following error appears on the screen: Error -3 encountered while saving. Error: errno=-3 on call to catalog manager for table 'RuleSetDef'
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.
ics.CommitBatchedCommands() does not return the correct status or set the errno variable properly in every situation.
Take an xml page that wraps code that streams a document back to the user -- this allows for checking the user credentials before the doc is streamed. If we try to call out the a JSP to do the validation the stream fails - it actually spits the bytes into the browser since something IS coming before the header. The JSP the I called was completely on 1 line so it should not have 'preserved' any white space
When using asset:export / asset.export tags on an asset that isn't a page or collection, the output XML doesn't contain info about the unnamed associations.
In flex Asset, getCompleAttribute method always assumes that there is a parent for the passing in asset type + definition, if there is none, a CS.DB exception would be thrown relating to getting "assetid" from ResultSet while the resultset is empty.
Instead of byte d = fileObj.getBinary() , the example should be changed to
byte d = newbyte[fileObj.getBinaryStream().available()];
The parser for ASSET.DELETEREVISION is in com.openmarket.xcelerate.commands.AssetDispatcher. It does call through to OBJECT.DELETEREVISION, so if the ObjectDispatcher.tag file is incorrect then an error will result.
This is a browser limitation
To resolve this issue, you can modify your web.xml file by adding the following:
Without validation, the utility ignores versioning on content. With validation, if the content type is under versioning, it will not update the content.
Page cache is not flushed by BulkLoader. as page cache is persistent, the cache should be cleared prior to running BulkApprover
BulkApprover requires running Content Server as it is implemented via CS tags
Flex filters are not fired (for example, FieldCopier)
BulkLoader does not support Blobs; for this you should use XMLPost
BulkLoader should not be executed while Content Server is running
When assets are added using BulkLoader, the assets will not be indexed in Lucence. You will need to re-indexed after import.
BulkApprover will not update the PubAsset Table to reflect the publish status after running Approve and Mark_Publish
Any blob which is not supposed to be cached by the Satellite Server will be added under <sscacedir>/uncachedblob. This directory can grow if blobs are not being cached on the satellite server. The content of this directory can be safely deleted at any time. It can be deleted manually or by using the FlushServer reset call. Note: FlushServer reset call will also clear all the cache from the Satellite Server
(#18534) Undesired headers are being passed from client to Remote Satellite Server when a WebServer (Sun Web Server 6.1) is in the middle of Content Server and Remote Satellite Server
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.
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.
You cannot log into Content Server if the username you are using to log in has the same "id" value of a different user in the SystemUsers table. For example, DefaultReader has an ID value of 2. If you create a user with the username "2," that user cannot log in.
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.
After the Document Type is changed in CS, refreshing DocLink does not make this change active - the user must logout and log back in for the change to be effective.
Required fields are not marked as "Required" in DocLink Edit Configuration screen. But From CS-DocLink Client interface its prompting properly for all required fields problem only with Edit Configuration field.
ANY template or site entry cannot have a "." in its name. should not allow prefix extension for SiteLauncher with periods in them
Dash UI - Copy keeps referenced by incorrectly 1). Create a product asset - say A - (this is the master) 2). Create a translation - say B 3). Go back to asset 'A' and click on copy (don't click on save) Observe - In the Relation tab - the Referenced by shows 'B'. (this is because its copying everything from A - which is incorrect) On saving - the referenced by is refreshed correctly
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.
Use multiple named associations for collection purposes rather than recommendations.
To workaround this issue, place the <p> and </p> inside a div tag
They will be deployed without the .jsp extension so the AppServer won't know how to run them. To work around this, clients who use dots in their jsp element names should set cs.use.short.jsp.names=true.
To set the password for a silent production install
1. Open the cs-core.xml file
2. Search for this block of text
<SETVARIABLE NAME="passwordVar" VALUE=" "/>
<SETVARIABLE NAME="passwordAdminVar" VALUE=" "/>
3. Set the ContentServer/SatelliteServer user password with <SETVARIABLE NAME="passwordVar" VALUE=" "/> .. specify the password in the value filed
4. Set the fwadmin user password with <SETVARIABLE NAME="passwordAdminVar" VALUE=" "/> .. specify the password in the value filed
5. Save the file and run the silent install as specified in the install guide. During the delivery install make sure Development is set to FALSE in omii.ini file - NOTE - this is case sensitive and should be typed in all UPPERCASE
(#18198) Lock escalations may occur when Real Time Publishing is running in multi-threaded mode using MSSQL Database.
The resolution to this is to make the following change to adv.pub.xml:
<bean id="DataUnpacker" class="com.fatwire.realtime.ParallelUnpacker" singleton="false">
<ref local="DataDeserializer" />
<ref local="EmbeddedMessenger_unpacker" />
<property name="numParallelTasks" value="3" />
<bean id="DataUnpacker" class="com.fatwire.realtime.ParallelUnpacker" singleton="false">
<ref local="DataDeserializer" />
<ref local="EmbeddedMessenger_unpacker" />
<property name="numParallelTasks" value="1" />
To take advantage of the newly added search functionality, a re-index is required after upgrade.
Log into the site
In the tree, pick the "Admin" tab
Open the "Asset Types" node
Double-click on ImageFile
On the right pane, click the "Register Asset Elements..." button
On the confirmation screen, click "Register Asset Elements" again
The workaround is to check in the asset in Advanced UI before checking it out in DASH
Ensure that the futuretense.ini property cs.dbtype is set to cs.dbtype=Oracle10 prior to upgrade to Content Server 7.5
Client shouldn't have system or hidden files in there war or exploded folder. The reason is that the installer won't be able to overwrite such files when it is auto deploying files/folders.
In earlier versions of Content Server it was possible to share elements between different templates. Content Server 7.x no longer supports this.
For a site that uses static publishing when you change the template on an asset and save it, and publish, then the asset remains in the publish list with the old template and also shows in the new one. Changing to a 3rd template on the asset and publishing added it to the publish list 3 times (one for each template it had been saved and published with). This is a problem because the template the user want is higher in the list than the other ones, and so the html output is overwritten with one of the template choices the user doesn't want.
Tree tabs are NOT mirrored to the Destination system when user use the mirror site configuration option in source system.
In order to mirror the tree tabs you need to do the following:
Login and go to the admin tab in the tree applet
Go to Sites and select a site..sat FSII
Scroll down and click on 'Mirror site configuration for FSII Destination (dynamic)'
Templates should be published first
If Mirror publish fails with an error "Address already in use: connect" then you can set the property http.protocol.version=1.0 in the file httpaccess.properties and try the publish again. You can create the file httpaccess.properties in the same folder that stores the commons-logging.properties.
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server
ABC-DEF-HIJ is sometimes indexed as one word and sometimes indexed separately as "ABC" and "DEF-HIJ", when this occurs, searching for "ABC-DEF-HIJ" will not always return the proper results.
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.
Workaround is to set the pubid in the session to "0", then remove it again after voiding.
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.
The dir:replaceattrs tag, which is part of the CS-Direct application that Content Server uses for user management, does not throw an exception when it is trying to replace the user attribute value of a nonexistent user attribute or for a nonexistent user.
If the 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
Flush ACL cache using the URL
If a user without any ACL logs in to CS, CS allows user to perform only those operations that a user with Browser ACL can perform.
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.
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.
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.
If there is a un-recognized rendermode passed, the system will cache the page and not log the dependencies. This will cause the page not being flushed in anyway since there dependencies are not there. The correct behavior should be:
1. Cache the page and log the dependencies anyway or
2. If the dependencies are not logged, do not cache the page.
When opening documents from a URL location in Microsoft Office 2007, the Office library makes an HTTP HEAD request to the web server for the opening URL. Content Server does not support HEAD requests which causes this exception to appear in the log file.
[CS.DB][ERROR] No where clause value for column category in table Category
[CS.DB][ERROR] Unable to build a where clause from columns category,assettype for query CategoryDescription
The INPUTFORM tag support is limited in ASSET API when creating basic asset types via REST. As a result, unsupported INPUTFORM TYPES are interpreted as <INPUTFORM TYPE="TEXT" WIDTH="48" REQUIRED="YES"/>. In order for users to see proper asset type attributes in Content Server UI's, the INPUTFORM tags need to be updated in the asset descriptor file through the database (AssetType table in CSE).
Use WEM Admin UI to delete a role or manually clean up the UserPublication table to remove the dependencies
The group can be manually deleted by removing the entries from the FW_CSSecurityConfig table.
SEVERE: Internal server error
Delete the site using Advanced UI in this case
To resolve this, manually remove the site entries from the urlaccessroles column in FW_Applications table using CSE
The workaround for this is to edit and save the user in the WEM Admin UI
The user needs to clear the browser cookie to continue should this occur
To avoid this issue, wait for the current operation to complete before changing to another application through WEM
If this occurs, continue to click on the next selection and it should resolve the issue
To contact FatWire Corporation about technical support for your product: