Tuesday, November 27, 2012

Composer v6.7 getting crashed after adding few plug-ins

Composer v6.7 is getting crashed while launching it. Here is the exception log.

!SESSION 2012-11-27 09:36:27.501 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_35
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.equinox.p2.reconciler.dropins 4 0 2012-11-27 09:36:32.550
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: org.eclipse.equinox.internal.provisional.configurator; version="0.0.0"
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
    at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
    at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
    at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)

!ENTRY org.eclipse.osgi 4 0 2012-11-27 09:36:32.580
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: No application id has been found.
    at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:236)
    at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

!ENTRY org.eclipse.osgi 2 0 2012-11-27 09:36:32.642
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.642
!MESSAGE Bundle reference:file:plugins\org.eclipse.equinox.p2.reconciler.dropins_1.0.0.v20080611.jar was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.reconciler.dropins 2 0 2012-11-27 09:36:32.642
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.configurator_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.642
!MESSAGE Bundle reference:file:plugins\org.eclipse.equinox.p2.ui_1.0.0.v20080530-1237.jar was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.ui 2 0 2012-11-27 09:36:32.642
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.configurator_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.642
!MESSAGE Bundle reference:file:plugins\org.eclipse.equinox.p2.console_1.0.0.v20080514-1900.jar was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.console 2 0 2012-11-27 09:36:32.642
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.configurator_0.0.0.

!ENTRY org.eclipse.osgi 2 0 2012-11-27 09:36:32.671
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.672
!MESSAGE Bundle reference:file:plugins\org.eclipse.equinox.p2.console_1.0.0.v20080514-1900.jar [204] was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.console 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.configurator_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.672
!MESSAGE Bundle reference:file:plugins\org.eclipse.equinox.p2.director.app_1.0.0.v20080604.jar [207] was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.director.app 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.p2.console_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.672
!MESSAGE Bundle reference:file:plugins\org.eclipse.equinox.p2.reconciler.dropins_1.0.0.v20080611.jar [217] was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.reconciler.dropins 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.configurator_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.672
!MESSAGE Bundle reference:file:plugins\org.eclipse.equinox.p2.ui_1.0.0.v20080530-1237.jar [220] was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.ui 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.configurator_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.672
!MESSAGE Bundle reference:file:plugins\org.eclipse.equinox.p2.ui.sdk_1.0.0.v20080605-1731.jar [221] was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.ui.sdk 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.p2.ui_0.0.0.
!SUBENTRY 2 org.eclipse.equinox.p2.ui.sdk 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.p2.ui.actions_0.0.0.
!SUBENTRY 2 org.eclipse.equinox.p2.ui.sdk 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.p2.ui.dialogs_0.0.0.
!SUBENTRY 2 org.eclipse.equinox.p2.ui.sdk 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.p2.ui.model_0.0.0.
!SUBENTRY 2 org.eclipse.equinox.p2.ui.sdk 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.p2.ui.operations_0.0.0.
!SUBENTRY 2 org.eclipse.equinox.p2.ui.sdk 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.p2.ui.policy_0.0.0.
!SUBENTRY 2 org.eclipse.equinox.p2.ui.sdk 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.p2.ui.query_0.0.0.
!SUBENTRY 2 org.eclipse.equinox.p2.ui.sdk 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing imported package org.eclipse.equinox.internal.provisional.p2.ui.viewers_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-11-27 09:36:32.672
!MESSAGE Bundle reference:file:plugins\org.eclipse.pde.p2.ui_1.0.0.v20080604-2000.jar [269] was not resolved.
!SUBENTRY 2 org.eclipse.pde.p2.ui 2 0 2012-11-27 09:36:32.672
!MESSAGE Missing Constraint: Require-Bundle: org.eclipse.equinox.p2.ui; bundle-version="[1.0.0,2.0.0)"

Wednesday, November 14, 2012

EMC Delivers Documentum Platform 7.0

  • Announces EMC Documentum Platform 7.0
  • New xMS technology accelerates deployment from weeks to hours
  • Enhances Documentum xPlore for better, faster, integrated search
  • Lowers TCO by significantly improving performance and reduces investment required in IT infrastructure
  • Further improves security through FIPS 140-2 Level 1 compliance and 128-bit AES encryption
  • Available via EMC OnDemand, a hosted deployment model

Wednesday, March 28, 2012

Tuesday, March 27, 2012

Documentum Distributed Models



  1. Single Repository distributed environments (Content is distributed across sites)
    • A Single Repository, with content stored at the primary site and accessed from remote sites  using ACS Server. Optionally, BOCS servers can be used.
    • A Single Repository, with content stored in a distributed storage area and accessed from remote sites using Remote Content Servers, ACS Servers, and optionally BOCS Servers.
  2. Multi-Repository distributed environments (Objects, content & metadata, are distributed across sites)
    • Multiple Repositories that replicate objects among themselves.
    • Multiple Repositories organized as a federation.
 
Single Repository - Distributed Model-1

Single Repository - Distributed Model-2

Monday, March 26, 2012

tidbits about xPlore

 Documentum xPlore is the next-generation search engine for Documentum.It is built on technology foundation of EMC xDB (native XML database) and Lucene. This combination of custom schema handling provided by xDB and index lookup by lucene is optimized by custom document type capabilities of Documentum.

 xPlore is a D6.5 SP2 (or later) compatible indexing system. xPlore v1.2 is the latest version released in November 2011.

Documentum xPlore vs FAST:

  • VMWare Support
  • Integrated Documentum security
  • Native Facet Computation
  • Improved performance and scaling
  • Query and Ingestion analytics
  • Multi-node
  • Improved HA/DR Support
xPlore features at a glance:

  • Next-generation search engine
    1. Combined meta data and content search
    2.  Zero-day tuning of the indexing schema
    3. Leverage XML and XQuery standards
    4. Integrated Documentum Security
  • Infrastructure
    1. Vmware Support
    2. SAN/NAS ready
    3. Improved HA/DR Support
    4. Hot backups
  • Performance and Scaling
  • Quality of Search
  • Query-based subscriptions
  • Support Languages
    1. English, German, Chinese
    2. French, Italian, Spanish, Japanese and Korean
    3. Russian, Arabic, Hebrew and Brazilian Portuguese
  • Indexing
  • Customizable Natural Language Processing Pipeline (NLP)
  • Administration
  • Data Management

More information on xPlore is available at:

Friday, March 16, 2012

Notes on DFS

DFS will be installed on documentum server at port 9080 by default and can be tested using below url.
We can also install DFS on web/App server as per below steps

Deploying on Apache Tomcat
Apache Tomcat does not support EAR archives. Therefore, to deploy on Tomcat, download emc-dfs.war for DFS (or the provided WAR file for a separate ECS deployment), using any of the various methods supported by Tomcat.

Note:
If the default maximum heap size of Tomcat is not large enough to run DFS and ECS services, increase it to 256 MB.

When deploying to Tomcat, we recommend making DFS the default application for the virtual host by setting its context path to a zero-length string. This step gives DFS the expected context root of http://<host_name>:<port>/services.

You can use the following procedure to perform a simple war file deployment.
1. Stop the Apache Tomcat server.
2. If the Tomcat JVM maximum heap size (also called Maximum Memory Pool) is less than 256 MB, increase it to 256 MB.
3. Copy the WAR file to the <TomcatHome>/webapps directory.
4. Modify the <TomcatHome>/conf/server.xml file and add an element like the following inside the <host> element.
<Context path="" docBase="emc-dfs" debug="0" reloadable="true"/>
This modification makes DFS the default application on the virtual host.
5. Start the Apache Tomcat server.

On startup, Tomcat unpacks the WAR file to a <TomcatHome>/webapps/<application_name> directory, where <application_name> is the name of the WAR file without the file extension

Wednesday, March 7, 2012

One-stop-shop for Documentum Performance

EMC has created performance corner on EDN for everything related to Documentum performance. Here is the landing page. It has lot of useful information and ideas related to performance. please do visit this page often for performance related tidbits / documentation.

https://community.emc.com/docs/DOC-12038


Documentum D2 : Overview and useful links

Useful link for DQL queries

Please refer below site for DQL queries.

http://www.dctmcontent.com/Lists/DQL/Category.aspx

Headlines Today