|
|
|
|
FatWire
documentation |
CS 6.3 |
|
|
|
|
Dec 2, 2005 |
Copyright © 2002, 2003, 2004, 2005 FatWire Corporation All rights reserved. |
Welcome to the release notes for Content Server V6.3. For the latest release notes, check the FatWire e-docs web site. The release notes contain descriptions of new features, changes in functionality, known problems, and other last-minute information about Content Server 6.3.
For additional information, contact FatWire technical support.
Document history:
The Content Server product CD includes a zip file (named DOC630.zip or DOC630.tar) of all the CS 6.3 documentation, including the installation guides. Unzip this file and begin reading the installation guide appropriate for your configuration. These guides explain how to install Content Server and the underlying DBMS, application server, portal server (optional), and JDBC driver.
If you are installing Satellite Server, read the Installing Satellite Server guide.
|
|
|
This kit includes the following items:
|
|
|
The CS 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/CSEE/6.3.0. For a description of the documents please
refer to the Documentation Notes link on the site. Check the site regularly for the latest set.
|
|
|
Provides ability to create and use Content Server URLs in a way that can be easily indexed by search engines such as Google
Supports upgrade from ContentServer 5.x, and ContentServer 6.1. Please refer to the document Guidelines for Upgrading ContentServer to ver 6.2 for details. For upgrading from Beta version of CS6.2, you need to follow this additional step:
- Finish off all the assignments in the FirstSite workflow
- Delete the FirstSite workflow
- Follow the instructions to upgrade from CS 6.1 in the upgrade guide.
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 doesnt support localized stylesheets.
This version of ContentServer now includes Keyview 8.2.
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.
· Integration of Content Server with the AltaVista search engine is no longer supported.
· The FileServer functionality is replaced by Satellite Server. The functionality of EvalServer has been disabled.
· Some CS tags have been deprecated. These include CONTENTSERVER.*, EVALSERVER.*, CALLAPPLOGIC, satellite.tag, satellite:tag, CATALOGMANAGER.EXPORTFORM, ics:catalogmanager.exportform. For a full listing of deprecated tags, please refer to the Content Server Tag Reference (look in the XML Index under Deprecated Tags).
|
|
|
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.
Content Server 6.3 works in application servers running J2SDK/J2RE 1.4.1 and above. Please make sure that appropriate version of JRE in installed and configured before installing Content Server.
Please also make sure that older versions of the JDK or JRE are not present in the PATH or CLASSPATH environment variables, especially if you plan to run Content Server in an environment that relies on these entries to be correct (resin, for example).
As of JRE 1.4.1, Sun has moved certain netscape.* classes from jaws.jar to plugin.jar. If you encounter a java.lang.NoClassDefFound (or related) exception, make sure that JRE is properly installed on the client machine. This error is usually seen on the client machine while loading the Tree applet.
Another common problem encountered is a type of JSPException with a message like the following: "The major.minor version '48.0' is too recent for this tool to understand". This error is related to the incorrect version of tools.jar in the class path. Make sure tools.jar loaded belongs to the correct JRE by launching JVM with a -verbose option.
|
|
|
This section describes additional steps that are necessary when installing Content Server 6.3.
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 settting -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:
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
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)
In addition, there are extra installation steps if you are using CS-Desktop, or the document transformation filter (#9760). When using CS-Desktop, the locale of the operating system, the application server, the installation of Microsoft Word, and the Internet Explorer on the client system must all be set to U.S. English with UTF-8 characters. Complete the steps appropriate for your system:
To change the character set for Internet Explorer 5.5, click View > Encoding > Unicode (UTF-8).
Make sure that your application server is also set for U.S. English using UTF-8 characters.
For Weblogic, follow these steps:
For WebSphere, be sure that the default client encoding and file encoding values in the System Properties section of the JVM Settings tab are set as follows:
Solaris/WebLogic/Oracle
Windows 2000/WebLogic/Oracle
Solaris/WebSphere/Oracle
Windows 2000/WebSphere/Oracle
AIX/WebSphere/DB2
Within Content Server, Ektron eWebEditPro ships with a
30-day evaluation license. At the end of the evaluation period, customers
interested in purchasing a license for eWebEditPro
should contact their FatWire sales representative. Once the
license arrives, it must be placed in the file ewebeditprolicensekey.txt, normally located in the
eWebEditPro directory under web server.
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:
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)
Also 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.
The installation media of Content Server includes a folder (named Samples) with sample code for AssetMaker, XMLPost, and BulkLoader. Please refer to the readme file in the Samples folder for details of the sample code. The folder is not installed on the customer's system but is available on the installation media for reference.
|
|
|
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 file 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 would be best to configure each jvm to use its own java.io.tmpdir (#13684).
Copy ftFileLock.dll/libFTFileLock.so file into the lib directory of the Application server or else 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".
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 worked by running ldconfig –p | grep libFTFileLock.so
if nothing comes up then it was not found confirm that you have the correct
path.
3. Also 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)
|
|
|
The known issues in release 6.3 are described in this section and are sorted by product.
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.
This is fixed by Sun in JES 2005 Q4 release
|
|
|
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.
|
|
|
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.
|
|
|
When using Oracle, LONG and LONG RAW columns cannot be mirrored. Use a URL column rather than a LONG or LONG RAW.
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.
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.
When the oracle database user has access to multiple schemas, all these schemas are read when CatalogManager tries to find the table structure of tables.
|
|
|
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).
The Insite.Edit tag should have the ewebeditpro=true attribute removed when displaying an embedded pagelet.
|
|
|
Setting the MAXLENGTH attribute in the 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";
|
|
|
|
|
|
When the treeview is toggled off and you click "List All Flex Family Asset Types," the list returned are not all flex assets.
|
|
|
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.
If an
assignment link is selected from InSite Editor and
the link points to an asset that is unsupported for editing by ISE, then ISE
will close.
To keep up with the performance, insite content is designed to be cached with other part of the pagelet. The current implementation keeps track of all direct dependencies, including access permission and workflow state, which are all direct related to the asset instance. The workaround is to flush CS and SS cache and the pencil icons will start showing correctly.
|
|
|
|
|
|
e.g. Exception checking for url http://<machinename>:<port>/futuretense_cs/formerror.html
|
|
|
Its recommended not to use muti-byte characters in the following:
UserNames
ACLNames
RoleNames
Template Names
AssetType Names and FieldNames
|
|
|
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.
|
|
|
|
|
|
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.
Mirroring fails to set errno if it fails to write a file to the folder specified by defdir in the SystemInfo table.
|
|
|
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.
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.
|
|
|
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.
The data stored in revision history is correct but links in 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 is wrong.
|
|
|
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 using a cookie to set the remote IP address.
|
|
|
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."
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.
Verity indexes get corrupted during publishing if set up in asynchronous mode but work correctly if set up in synchronous mode.
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 environment and Verity works correctly before the locale kit is installed.
|
|
|
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.
|
|
|
(#) 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.
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.
|
|
|
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.
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.
Workaround is to restart the cluster members once publish is complete
|
|
|
If
this property is set to true, you will get unknown username/password error
while running pingdb. Once the upgrade process is
complete, you can set this property back to true.
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.
Differences between 5.5.1 upgraded to 6.2 and pure 6.2 install.
TABLE
Differences
|
Unique Tables, that still existed in the upgraded
version – These tables are not used by 6.2 code
anymore. However, we do not recommend
that you delete these tables. |
|
DTDCATALOG INBOUNDCATALOG OUTBOUNDCATALOG PARTNERCATALOG SITEENTRY_ARGS TXSITECATALOG TXSYSTEMITEMCACHE |
CONSTRAINT
Differences
Constraints that are not removed from 5.5.1 upgraded to 6.2. These constraints should be removed manually after upgrade to achieve full functionality, and to avoid any problems on future upgrades.
|
Table Name |
Constraint Name |
|
AARTICLES |
UNIQUE NAME |
|
AIMAGES |
UNIQUE NAME |
|
ARTICLE |
UNIQUE NAME |
|
ATTRTYPES |
UNIQUE NAME |
|
COLLECTION |
UNIQUE NAME |
|
CONTENTGROUPS |
UNIQUE NAME |
|
DRILLHIERARCHY |
UNIQUE NAME |
|
DTDCATALOG |
PRIMARY KEY ID |
|
IMAGE |
UNIQUE NAME |
|
INBOUNDCATALOG |
PRIMARY KEY ID |
|
LINK |
UNIQUE NAME |
|
LINKSET |
UNIQUE NAME |
|
OUTBOUNDCATALOG |
PRIMARY KEY ID |
|
PAGE |
UNIQUE NAME |
|
PARTNERCATALOG |
PRIMARY KEY ID |
|
PDF |
UNIQUE NAME |
|
PRODUCTGROUPS |
UNIQUE NAME |
|
PRODUCTS |
UNIQUE NAME |
|
PROMOTIONS |
UNIQUE NAME |
|
QUERY |
UNIQUE NAME |
|
SEGMENTS |
UNIQUE NAME |
|
TXSITECATALOG |
PRIMARY KEY PAGENAME |
|
SITEENTRY_ARGS |
PRIMARY KEY ID |
|
WORKFLOWOBJSACTIONS |
PRIMARY KEY ID |
COLUMN
Differences:
The table below lists the column difference after upgrading from 5.5.1 to 6.2 You can change the length of those columns after upgrade.
|
Tablename |
Column Name in CS 5.x |
Column Definition in CS 5.x upgraded to 6.2 |
Column Definition in brand new |
|
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 |
|
|
|
For
an installation of Content Server that uses Active Directory for User
Management, the jndi user specified should only have read
permissions. We do not guarantee what will happen if he has write permission.
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.
When a user is deleted at the Content Server level through Content Server Management Tools, that user is not deleted from CS-Direct sites.
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.
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
Restart your portal/Application server for the changes to take effect or
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 in to CS, CS allows user to perform only those operations that a user with Browser ACL can perform.
If a user is enabled for a site and you delete the user from ContentServer Management Tools interface or from SystemUsers in Content Server Explorer, AdvanceSearch UI screen will not render. The workaround is to delete the corresponding user entry from UserPublication table
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)
....
This is an inconsistency between database and LDAP user
management. You need DefaultReader 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.
|
|
|
The default debug listener port of 1025 for the Page Debugger may have a conflict on Windows 2000. This can be changed to some other port number.
Page debugger fails when trying to debug JSP pages.
|
|
|
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.
|
|
|
Import is successful if you remove the encoding <?xml version="1.0" encoding="UTF-8" ?> and run XML Post
|
|
|
|
|
|
|
No. |
Summary |
Description |
|
10719 |
Undoing asset checkout displays errant message. |
After undoing an asset checkout, the message " Deleted Catalog record" may appear on the bottom of the screen |
|
10817 |
DM Portlet: Identical folder/document names under the same parent folder. |
Under the same parent folder, the DM Portlet allows both folders and documents to have identical names. |
|
10823 |
Message requests user to provide a unique name. |
Trying to save a Spark asset without a name produces the following dialog: "You must specify a unique name for this Spark <asset type>". Note that the name does not have to be unique. |
|
10829 |
DM Portlet: Cannot delete a folder if the folder is not empty. |
Cannot delete a folder if the folder contains documents or sub-folders. User must delete documents and sub-folders first. |
|
10868 |
DM Portlet: Copying a folder does not do a deep copy. |
Copying a Spark folder does not perform a deep copy; i.e., it does not copy the contained sub-folders and/or documents. |
|
10884 |
DM Portlet: No confirmation when a file with the same name is to be replaced. |
Uploading a file with the same name as an existing file does not prompt the user to confirm the replacement of the existing file. |
|
10944 |
Assigning a workflow process to an asset does not refresh portlets. |
Assigning a workflow to an asset does not update portlets with new information. |
|
10959 |
DM Portlet: Lack of permission yet still can create document or folder. |
A user lacking "Check Out" and "Edit" permissions on a folder can still create a document or folder under that folder. |
|
10965 |
DM Portlet: Navigation without permission. |
A user can navigate the folders/documents in the DM Portlet even if the user lacks Inspect/View permission on the parent folder. |
|
10967 |
DM Portlet: A folder can be moved when an underlying document is unavailable. |
A folder can be moved when one of its assets is checked out or opened for editing by another user. |
|
10968 |
DM Portlet: Folder can be moved when user lacks permission to edit its underlying content. |
A folder can be moved when user lacks permission to move(edit) its underlying folders or documents. (Folder can be moved when its content can't.) |
|
10976 |
Search results cannot be reordered. |
Clicking a column title does not reorder the search results. |
|
11106 |
Illegal participant entries in "Workflow commands" drop-down list. |
On an asset's "Status" screen, the entries "Set Participants" and "Show Participants" may be displayed in the "Workflow commands" drop-down list . These entries are nonfunctional within Spark. |
|
11208 |
DM Portlet: Document can be downloaded after session timeout. |
After session timeout, document downloading is still enabled. |
|
11220 |
DM Portlet: Document and folder name changed on rollback. |
When a document's name and/or its parent folder is changed, rolling back the document also rolls back the document's name and/or the parent folder. |
|
11221 |
Reference portlet for Spark Ad throws a stack trace. |
Reference portlet for Spark Ad throws a stack trace if nothing has been published to the production server. |
|
11458 |
DM portlet fails when running on JRockit. |
DM portlet fails when running on JRockit. Workaround is to use the Sun JVM which ships with BEA portal. |
|
10979 |
In DM portlets, clicking on some links take you to search screen |
After Searching for assets in the portal interface, when you click on some links in My Document portlet you may see the search screen again. |
|
12910 |
TimeZone mismatch error happens and Assignment Due date changes by 1 day in Portlet display |
In workflows the times are set based on GMT. So this causes some confusion for users using the system in other time zones |
| 13722 | SUN JES Portal - Portlets will not be correctly installed if context is changed from 'cs' or 'servlet' |
If you change the context root to anything other
than 'cs' or 'servlet', in JES3 admin console after the install then the portlets fail to load.
The error seen in the logs is:
Servlet.service() for servlet desktopServlet threw
exception |
|
|
During file conversion by CS-Desktop (implemented by Verity KeyView), CS-Desktop writes image files to the folder specified by property keyview.imagedir in futuretense_xcel.ini. There are two requirements for the folder keyview.imagedir:
1. It must be a web-accessible folder that matches the URL prefix specified in keyview.imgurl. This ensures that CS can preview the CS-Desktop images.
2. The folder must exist before CS-Desktop is used. This ensures that the KeyView file conversion completes successfully and saves the images.
Note that after installing CS, keyview.imagedir is set to $SHARE-directory/remoteimages and keyview.imgurl is set to /futuretense_cs/remoteimages/. You may edit these value to point to an appropriate folder, or you may keep these values and create a folder named remoteimages.
If Outlook is already open, CS-Desktop toolbar will not be displayed when MSWord is opened to connect with ContentServer. This only occurs if MSWord is configured to be the default email editor for Outlook and Outlook has been opened first. Outlook maybe closed and MSWord reopened as a workaround.
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 the word's startup folder out to somewhere safe for example in c:\Program Files\FatWire\. Now 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, when you add it and click okay, it will load our CS-Desktop add-in.
This means that flex assets that have a required attribute of type asset should not be enabled for CS-Desktop.
In such a case, when a CS-Desktop user opens a flex asset that was created with the original definition, there are no parents marked for the asset. To work around this issue, be sure that you do not enable flex asset types for CS-Desktop until you are completely finished configuring their definitions.
When data is saved using CS-Desktop in the form of table content then entire data is not saved hence not previewed.
When installing ContentServer on Solaris/ SUN application server or SUN webserver, you need to set the environment variable LD_LIBRARY_PATH to the location where keyview files get copied. This is typically /var/opt/SUNWappserver7/lib. This environment variable must be set for the user who is starting/restarting the SUN application/ SUN web server.
|
|
|
The help file is present in the installed folder but not registered correctly.
|
|
|
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.
Workaround is to make sure that all the catalogs in a project have at least one record
|
|
|
To contact FatWire Corporation about technical support for your product:
|
|
|
|
|
|
|
FatWire documentation |
Copyright © 2002 2003 2004 2005, FatWire Corporation All rights reserved. |