Jivespace : Document List - Support

How to clear specific document from DocumentCache

communities@jivesoftware.com — Fri, 20 Nov 2009 08:36:24 GMT

Today, After I updated the workflowid of a document, I didn't get the workflowid of the document because after update, the doucment I got from

documentManager is cached, not searched from the database. In this situation, how to get the latest document information? Before get the doucment

from the documentManagement, remove the doucment cache form the documentCache.

Here is the Java Code.

DbDocumentManager documentManager = (DbDocumentManager) JiveApplication.getContext().getDocumentManager();
documentManager.getDocumentCache().remove(caseLink.getDocID());

DocumentManager is an interface and class DocumentManagerProxy implements it.

ExtendedDocumentManager is an interface and extends DocumentManager. The DbDocumentManager implements ExtendedDocumentManager interface.

About Cache, please refer to http://www.jivesoftware.com/jivespace/docs/DOC-4060

documentManager and documentManagerImpl

communities@jivesoftware.com — Thu, 12 Nov 2009 09:19:54 GMT

Today, I always got DocumentProxy from documentManager.getDocument(docID), the DbDocument should be returned.

DocumentManager is a interface, that is extened by ExtendedDocumentManager and implemented by DocumentManagerProxy
Document is a interface, that is implmented by both DbDocument DocumentProxy.In DocumentManagerProxy,
the getDocument(docID) returms Document. I don't know whether the Document is DbDocument or DocumentProxy. In my bean definition file,
the documentManager is referenced to documentManager, but in clearspace bean definition files, the documentManager is always refered to
documentManagerImpl. In the clearspace bean definition files, the documentManager is the name of DocumentManagerProxy, while
DbDocumentManager is the name of DbDocumentManager.

Then I found that the DbDocumentManager is implementation of ExtendedDocumentManager. Exactly ,the getDocument(docID) of DbDocumentManger
returns DbDocument. so im my bean definition file, the documentManager should reference to documentManagerImpl, not the docuementManager.

Testing Links

russellstephens@gmail.com — Mon, 09 Nov 2009 03:27:43 GMT

http://www.google.com

Updating Lucene libraries

communities@jivesoftware.com — Thu, 22 Oct 2009 17:46:56 GMT

Apache Lucene is the library we use for performing search indexing and retrieval in all of Jive's products. We have found that in older versions of Clearspace (2.5.x and earlier), some users run into problems with corrupt search indices. This is often accompanied by strange errors in the logs and problems with content not showing up in the index as expected. If you do encounter these problems, you may need to update the version of Lucene your instance is using to address several known bugs. To determine whether or not your error warrants these changes, please contact Jive Support.

Updating to Lucene 2.4:

Replace the following jars from the <webapps>/clearspace/WEB-INF/lib directory with the attached jars:

lucene-core.jar
lucene-highlighter.jar
lucene-memory.jar
lucene-queries.jar

Once the new jars are in place:

Stop Clearspace
Back up your jiveHome/search/ folder, then remove the index directories from the jiveHome/search/ folder (keep the xml files)
Start Clearspace
Do a full rebuild of both the search index and user search index. This is necessary because the format of the indexes changes with the 2.4 release of Lucene.
Restart Clearspace again just to ensure that everything is starting with a clean slate.

After this, any issues with corrupt indices should be resolved. Note that these updated libraries have been included with the SBS 3.0 release, so these instructions apply only to Clearspace releases.

Connecting to the default SBS database

communities@jivesoftware.com — Fri, 09 Oct 2009 13:12:17 GMT

If you install the SBS platform with the default Postgres database, you may find your self wondering how to connect directly to the database. This information is a little bit hidden but we do supply some convenience scripts to facilitate the task.

The default database username is sbs.
The password can be found in the file /usr/local/jive/etc/postgres/.cs-password
To enable remote connections to the database, run the script: /usr/local/jive/bin/dblocal, then restart the application with ./appstop && appstart
Now use DbVisualizer, psql, or any other database browsing tool to connect to your db!

More information on these scripts can be found in the Operations Cookbook.

Repeated task reminder emails after task is complete

communities@jivesoftware.com — Thu, 08 Oct 2009 20:53:05 GMT

Problem:

Users receive duplicate email notifications for the same task, or receive email notifications for tasks which have already been marked as completed.

Type of Problem:

Server misconfiguration.

Cause:

Either there are multiple Clearspace/SBS instances running on the same application server or a development instance is running with a copy of the same database as the production server.

Task reminders are processed and delivered from a nightly batch process that runs individually on each cluster. If you have multiple instances of Clearspace/SBS pointing to the same database running on the same machine, your users will receive one notification per instance.

Another problem can arise if you restore a copy of the production server's database to a development environment. Notifications will be triggered from each instance, and users may continue to receive notifications for overdue tasks from one server if the tasks are not marked as complete on both instances.

Solution:

Ensure that only one Clearspace/SBS application is running per instance. You can do this by either checking the list of running processes or examining Tomcat's webapps folder. Also, ensure that when you restore a database backup you change the email server settings (System > Settings > Email) to disable outgoing emails.

Using JPDA Remote Debugging with SBS & Linux Setup

communities@jivesoftware.com — Tue, 22 Sep 2009 21:08:04 GMT

This was not as easy as I'd like, but this could be a feature add for management.

As the jive user, visit the following file:

~/applications/sbs/bin/manage

Around line 115, make the following update:

echolog "Starting application $JIVE_NAME" $LOG_FILE

COMMAND="$JAVA_BIN $JAVA_OPTS $JPDA_OPTS $CONF_OPTS -D catalina....

~/applications/sbs/bin/instance

Append the following line:

export JPDA_OPTS="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9113"

After this, do a simple

~/bin/apprestart

At this point, simply point your remote debugger (Eclipse or what not) at port 9113 on your server, and you should be able to attach to the JVM like a champ.

Note: If you pick a separate port number, just make sure that it doesn't conflict with an OOTB port number (i.e. 9000 not a good idea).

Jivers?

Is there a better way to do this and/or can you work this into the script as an option for us developers. =)

Hope this helps someone.

no pagination for resources or discussions tab for a community

communities@jivesoftware.com — Mon, 14 Sep 2009 17:00:09 GMT

Currently, there is a filter on the discussions or resources tab for a community that lets the user pick how many to display (15, 30, or 50). However, if there are 51 or more resources or discussions, there isn't a way for the user to get to the 51st+ discussion or resource.

Installation of Jive on redhat Linux

communities@jivesoftware.com — Thu, 27 Aug 2009 10:57:29 GMT

Hi,

Have installed demo of Jive SBS on Redhat linux platform via a stumbling route as I'm not that familar with Linux (well this is my first time).

Managed to get all pre-requisites installed.
Now logged onto localhost.localhost.com/admin/setup. and going through the Database settings - Standard Connection screen.
- I've created a blank database on a windows server called SQL2K5Tst.
- setup user sbs and password
- tested the server is pingable from the linux server.
When I try to connect to the SQL server I get this error: Unable to find jdbc driver class: net.souceforge.jtds.jdbc.Driver

Your help would be greatly appreciated.

Thanks

dan

Clearspace community API about Document

communities@jivesoftware.com — Tue, 25 Aug 2009 05:45:48 GMT

1. How to get a document

2. How to create a document

3. How to publish a document

     /**
      * @throws UnauthorizedException 
      * @throws CommunityNotFoundException 
      * 
      */
     public com.landesk.miner.bean.Document createDocument(
               com.landesk.miner.bean.Document document) throws Exception {
 
          DocumentManager documentManager = JiveApplication.getContext().getDocumentManager();
          CommunityManager communityManager = JiveApplication.getContext().getCommunityManager();
          
          Community community = null;
 
         community = communityManager.getCommunity(document.getCommunityID());
     
          DocumentBean documentBean = new DocumentBean();
          documentBean.setUserID(document.getUserID());
          documentBean.setDocumentTypeID(1L);
          documentBean.setContainerID(document.getCommunityID());
          documentBean.setContainerType(JiveConstants.COMMUNITY);
          //Case title can be null
          documentBean.setTitle(document.getSubject()== null ? "Case:" + document.getIDInSource() + " Subject" : document.getSubject());
//          documentBean.setBodyText("abc");
          documentBean.setBodyText(document.getBody());
          
          Document communityDocument = documentProvider.getDocument(documentBean);
 
          Log.debug("documentManager:" + documentManager);
          Log.debug("documentProvider:" + documentProvider);
          Log.debug("community:" + community);
          Log.debug("communityDocument:" + communityDocument);
          Log.debug("Case:" + document.getIDInSource());
          
          documentManager.addDocument(community, communityDocument, Collections.emptyMap());
          
          communityDocument.setDocumentState(DocumentState.PUBLISHED);
          
          communityDocument.save();
          
          document.setIDInTarget(String.valueOf(communityDocument.getID()));
          
          Log.info("Case:" + document.getIDInSource() + " in Salesforce export successed." + "Document:" + document.getIDInTarget() + " creation  succeedeed.");
          
          return document;
     }

4. Plain Text to Community Document Body

            String myDocumentBody = "Hello\n\n";
            String doc = WikiContentHelper.wikiToEditorHtml(myDocumentBody);
            logger.info(doc);

When myDocumentBody="Hello\n\n" the Reuslt is <body>Hello </body>

When myDocumentBody = "<a href=\"abc\">Cause:</a>", the result is <body><a href="abc">Cause: </a></body>

When myDocumentBody ="<company>landesk</company>" the result is <body><company>landesk</company></body>

When myDocumentBody ="Cause:" + case.getCause() and the case.getCause() return null, the result is <body>Cause:null</body>

5. Wiki Text to Document

communityDocument.setBody(WikiContentHelper.unknownContentToJiveDoc(WikiContentHelper.wikiToEditorHtml(document.getBody())));

WikiContentHelper.wikiToJiveDocument(textBody);