tag:blogger.com,1999:blog-78712015958095251982011-10-17T06:42:29.819-07:00Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.comBlogger951100tag:blogger.com,1999:blog-7871201595809525198.post-38600416654110264382010-01-11T12:55:00.000-08:002010-01-11T12:57:01.368-08:00Introduction <br />In Documentum applications, the speed at which users can retrieve or add content to the system plays a big part in the overall end user experience. Network latency and bandwidth restrictions, physical architecture and client configuration all have an impact on the time it takes between initiating a content transfer, performing the upload or download, and returning control back to the user. <br /> <br /> <br /> <br />This document will discuss various tuning options available to achieve the best possible performance for UCF content transfer in your network environment. <br /> <br /> <br /> <br />Overview of UCF <br />UCF (Unified Client Facilities) is the EMC Documentum framework for performing content transfer between the client and content servers over HTTP. It provides many features that extend beyond simple file transfer protocol, such as: <br /> <br />Content compression to optimize transfers of larger files over the network <br />Support for complex documents, such as XML files <br />Support for compound document types, such as OLE objects inside a Microsoft Office document <br />Awareness of locally downloaded files, and the ability to avoid downloading the same content twice <br />Registry support, to allow checkout from one application and check in from another <br />Recoverability in the case of a brief network interruption <br />Location aware, to allow users to transfer content from the closest ACS or BOCS server <br />High-Level UCF Operations <br />When a content transfer is initiated, the UCF client running on the end user machine is initiated if it is not already running. The applet loads the UCF client jars and initiates contact with the UCF server, running on the application server. <br /> <br /> <br /> <br />The UCF client and server pass information back and forth about the environment and requested action before content is transferred between the two machines. Depending on the architecture and configuration, content may be transferred through the application server, directly to or from an ACS server on the content server, or a BOCS server located near the user. <br /> <br /> <br /> <br />After the content transfer is complete, there will be some additional communication from server to client to provide instructions on registry entries to be added or modified, directions on how to launch the appropriate application for view or edit operations, or instructions on how to delete the local file on check in. <br /> <br /> <br /> <br /> <br /> <br />Optimizing UCF for Best Performance <br /> <br /> <br /> <br />Tip #1 - Use ACS and BOCS for Content Transfer Whenever Possible <br /> <br /> <br /> <br />The introduction of ACS and BOCS servers in 5.3 SP1 have allowed content transfer to be performed directly from the content server, rather than requiring that the content always pass through the application server. This not only removes the double-hop that is required (which is very costly for small files) but also reduces the load on the application server. <br /> <br /> <br /> <br />In the 5.3 timeframe, ACS and BOCS could only be used for download operations such as checkout, export and view. All upload operations still passed through the application server. <br /> <br /> <br /> <br />From D6 onward, ACS and BOCS servers can also be used for upload operations. <br /> <br /> <br /> <br />Note that not all applications are network location aware and able to take advantage of remote ACS and BOCS servers. <br /> <br /> <br /> <br />Tip #2 - Optimize UCF Client Initialization <br /> <br /> <br /> <br />In 5.3 SP1 through SP5, D6 and D6SP1, the UCF client engine will time out after one minute of inactivity, and the javaw.exe process would be terminated. This means that if a user initiates another content transfer request after the timeout has occurred, the browser must re-initialize the UCF client and restart javaw.exe. <br /> <br /> <br /> <br />This value can be increased in the ucf.client.config.xml file as follows: <br /> <br /> <br /> <br />Edit the ucf.client.config.xml file (located at C:\Documents and Settings\<username>\Documentum\ucf\<hostname>\shared\config\ucf.client.config.xml) and add the following option to extend the UCF Client Timeout. <br /> <br /><option name="client.engine.timeout> <br /> <br /> <value>30</value> <br /> <br /></option> <br /> <br />Close all browser windows and log back into the application. The next content transfer operation will cause these new settings to take effect. <br /> <br /> <br /> <br />With these new settings, the UCF client will remain alive for at least 30 minutes of inactivity before terminating itself. <br /> <br /> <br /> <br />Note that the default value has been increased in 5.3 SP6 and D6.5. <br /> <br /> <br /> <br /> <br /> <br />Tip #3 - Configure On-Demand Virus Scanners to exclude unnecessary files <br /> <br /> <br /> <br />The first time the UCF client is initialized after restart, the on-demand scanner will need to scan all jars and DLLs prior to launching them. In addition, if it is the first time java has been used since reboot, the scanner will scan all of the Java jars and DLLs. This slows initialization down tremendously. <br /> <br /> <br /> <br />With some small changes to the configuration of the virus scanner, it is possible to see much faster UCF client initialization without sacrificing the security of the system. Please see Appendix A for more detailed instructions on how to implement this recommendation when using McAfee. <br /> <br /> <br /> <br />Tip #4 - Reduce UCF Client Communications over High Latency <br /> <br /> <br /> <br />When the UCF client is remote from the UCF server, the time it takes for each request/response is greatly increased. As there can be many such roundtrips, it can add significant time to the end-to-end operation, which is especially noticeable for small files. <br /> <br /> <br /> <br />In order to reduce the chattiness of the UCF communication, handshake and request optimizations were introduced in D6 SP1 and 5.3 SP6. <br /> <br /> <br /> <br />Note: These optimizations were also back ported to 5.3 SP5 and can be found at ftp://dev_pre:qa5.grN6@ftp2.documentum.com/UCF/5.3SP5/SP5_HF_GW2. However, EMC strongly recommends that customers upgrade to 5.3 SP6 instead of applying the hotfix as 5.3 SP6 includes a number of other performance and stability enhancements. <br /> <br /> <br /> <br />Tip #5 - Tune the Buffer or Chunk Size to Improve Download over High Latency <br /> <br /> <br /> <br />Each application server has a default sized buffer that it uses when transferring data across the network to clients. In most cases, this buffer is sized much too small, resulting in slower transfers over the WAN as more roundtrips are necessary. <br /> <br /> <br /> <br />Tomcat and Jboss <br /> <br />If you are using Tomcat or Jboss as the application server and you are not using ACS, you can add the socketBuffer parameter to the HTTP Connector as shown below: <br /> <br /><!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> <br /> <br /> <Connector port="8080" maxHttpHeaderSize="8192" <br /> <br /> maxThreads="150" minSpareThreads="25" maxSpareThreads="75" <br /> <br /> enableLookups="false" redirectPort="8443" acceptCount="100" <br /> <br /> connectionTimeout="20000" disableUploadTimeout="true" <br /> socketBuffer="64000"/> <br /> <br />If you are using 5.3 ACS and BOCS the application server is Tomcat 5.0.28. In versions 5.3 SP1 or SP2, you will need to add the socketBuffer parameter. In 5.3 SP3 through SP6, this parameter should already have been added by the installer. <br /> <br /> <br /> <br />In 6.5 and beyond, Jboss is the container for ACS and BOCS. In 6.5 SP1, enhancements were added to the embedded Jboss server to enable it to recognize and use the socketBuffer parameter. <br /> <br /> <br /> <br />BEA Weblogic <br /> <br />If you are using BEA Weblogic as your application server and you are not using ACS, be sure to add the -Dweblogic.ChunkSize parameter. By default, the ChunkSize is 4k which is much too small. <br /> <br /> <br /> <br />It can be set in the config.xml for the domain: <br /> <br /><server> <br /> <br /><name>server1</name> <br /> <br /><ssl> <br /> <br /><enabled>false</enabled> <br /> <br /></ssl> <br /> <br /><machine>localhost</machine> <br /> <br /><listen-port>17001</listen-port> <br /> <br /><cluster xsi:nil="true"></cluster> <br /> <br /><listen-address></listen-address> <br /> <br /><server-start> <br /> <br /><arguments>-Dweblogic.Chunksize=64000</arguments> <br /> <br /><username>weblogic</username> <br /> <br /><password-encrypted>{3DES}wmzrpHOymvTy3q8TOeF1qQ==</password-encrypted> <br /> <br /></server-start> <br /> <br /></server> <br /> <br /> <br />It can also be defined in the set_domain_env batch file with the other JAVA_PROPERTIES values: <br /> <br />set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% \ <br /> <br />-Dwls.home=%WLS_HOME% -Dwli.home=%WLI_HOME% \ <br /> <br />-Dweblogic.Chunksize=64000 <br /> <br />In D6 and D6 SP1, the application server that hosts ACS and BOCS is BEA Weblogic, and the installer has automatically added those options to the script that starts the embedded Weblogic server (startMethodServer.cmd for example). <br /> <br /> <br /> <br />IBM Websphere <br /> <br />If you are not using ACS and content is being transferred through WAS, then you may see improvements in content download performance for large files by modifying the ResponseChunkSize configuration parameter in the plugin-cfg.xml. <br /> <br /><Config ResponseChunkSize="N"> <br /> <br />where N equal the chunk size in kilobytes. The default value is 64 (kilobytes). <br /> <br /> <br /> <br /> <br />Tip #6 - Improve Upload Performance in D6 and Above <br /> <br /> <br /> <br />In D6, a parameter was added to the ucf.client.config.xml file that allowed the users to specify a chunk size to be used when uploading content. <br /> <br /> <br /> <br />Internal testing showed that a value of 49152 worked best with ACS on BEA when simulating various WAN conditions. However, in environments where customers are not using ACS write, or whose network conditions are different from that which was tested, this value may not be optimal. Increasing or decreasing the optimal.chunk.size parameter based on your specific network conditions can be beneficial. <br /> <br /><option name="optimal.chunk.size"> <br /> <br /> <value>49152</value> <br /> <br /></option> <br /> <br />Note that this setting is ignored if the client is using Sun Java version 1.6 due to a Java bug (http://bugs.sun.com/bugdatabase/view_bug.do"bug_id=6631048). <br /> <br /> <br /> <br />Tip #7 - Use Adaptive Parallel Content Transfer to Consume More Available Bandwidth <br /> <br /> <br /> <br />By default in most versions of UCF, content download operations will be done in a single thread. If sufficient network bandwidth is available, the download operations could perform significantly faster if the file was broken up into smaller pieces and transferred by multiple concurrent threads. <br /> <br /> <br /> <br />In 5.3 SP6 and D6.5 the UCF client can be configured to use multiple threads when downloading files. This is controlled in the ucf.client.config.xml file using the following parameters: <br /> <br /><option name="max.parallel.download.streams"> <br /> <br /> <value>5</value> <br /> <br /></option> <br /> <br /><option name="min.parallel.segment.size"> <br /> <br /> <value>131072</value> <br /> <br /></option> <br /> <br /><option name="measurement.time.interval"> <br /> <br /> <value>300</value> <br /> <br /></option> <br /> <br /><option name="single.thread.throughput "> <br /> <br /> <value>131072</value> <br /> <br /></option> <br /> <br />The "max.parallel.download.streams" parameter limits the number of threads that can be run concurrently when performing a parallel download. In this example, 5 separate streams could potentially be initialized. If one of the streams finishes their assigned task ahead of the others, it is then free to request a new range of bytes to be downloaded. <br /> <br /> <br /> <br />The "min.parallel.segment.size" parameter specifies that if the remaining portion of a document after a byte range is assigned is smaller than a specified value, it should not be assigned to a new thread. Rather the original thread's byte range should be extended to include those additional bytes. For example, if a thread is supposed to download 500Kb of a 600Kb file, as the remaining number of bytes is less than 128k, no new thread will be started and the original thread will assume ownership of those additional bytes. <br /> <br /> <br /> <br />The "Adaptive" part of parallel content transfer is controlled by the remaining two parameters. As tests have shown that disk I/O actually becomes a bottleneck and degrades performance if the content is transferred in parallel over LAN conditions, it is important to be able to control when the parallel content transfer is actually turned on. In this case, the UCF client will measure how many bytes were transferred initially by a single thread within a specified timeframe. If the number of bytes is less than what it expected, parallel content transfer will be turned on. If it is more than was expected, then it is assumed that bandwidth and latency are sufficient for a single thread to transfer the content most efficiently. <br /> <br /> <br /> <br />In the example above, the UCF client will measure the number of bytes that have been downloaded in the first 300ms of transfer (or as close to that time as possible). It will enable parallel content transfer if less than 131072 bytes (128k) have been downloaded, and disable it if more than 128k has been downloaded. <br /> <br /> <br /> <br />If your remote users have very high latency, it is likely that you will want to increase the "measurement.time.interval" to match the round trip time plus time to download a small portion of the file. For example, if you have 200ms round-trip latency, you might consider increasing the measurement.time.interval to 500ms to compensate for the time it takes for the request to reach the ACS server and start the content transfer. <br /> <br /> <br /> <br />In order to permanently disable parallel content transfer, all that must be done is changing the "max.parallel.download.streams" to 1, or decreasing the "single.thread.throughput" to a very small number, such as 1. In this case, regardless of the actual throughput, parallel content transfer will not be used. This is especially important in load testing scenarios, where many clients are being simulated from the same client machine. <br /> <br /> <br /> <br />Tip #8 - Tuning Content Download when Documentum User Directory is on a Network Drive <br /> <br /> <br /> <br />If the location of the Viewed and Checkout directories are on a network drive, or users regularly export content to a network drive, performance can be improved by setting the value of "ucf.file.buffer.size" to a larger number. The default value is 32768. <br /> <br /> <br /> <br />To set it for a single user, simply add the following to the ucf.client.config.xml on the client machine: <br /> <br /><option name="ucf.file.buffer.size"> <br /> <br /><value>61440</value> <br /> <br /></option> <br /> <br />To set the default for all users, add the same option to the ucf.installer.config.xml file on the application server and force a new version of UCF on the server side using the steps in Appendix B. <br /> <br /> <br /> <br />Tip #9 - Use UCF Client Logging to Measure performance <br /> <br /> <br /> <br />UCF Client logs are extremely useful when diagnosing UCF performance. <br /> <br /> <br /> <br />UCF client logging is enabled on the end user's machine. <br /> <br /> <br /> <br />Edit the ucf.client.logging.properties file, located at: <br />C:\Documents and Settings\<username>\Documentum\ucf\<hostname>\shared\config <br /> <br /> <br /> <br />For best results, set the log level to FINEST, as shown below: <br /> <br />handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler <br /> <br />.level=FINEST <br /> <br />#------------------- <br /> <br />java.util.logging.FileHandler.pattern=C:/Documentum/logs/ucf.client%u.log <br /> <br />java.util.logging.FileHandler.limit=10485760 <br /> <br />java.util.logging.FileHandler.count=10 <br /> <br />java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter <br /> <br />java.util.logging.FileHandler.encoding=UTF-8 <br /> <br />#------------------- <br /> <br />java.util.logging.ConsoleHandler.level=OFF <br /> <br />java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter <br /> <br />In addition, to prevent the UCF client log from overwriting itself each time, change the value of java.util.logging.FileHandler.count to a number greater than 1. As each new client initializes, the old logs will be renamed and preserved for further analysis. <br /> <br /> <br /> <br />In the UCF client logs you will see entries such as "Logging request: getFile" and "Handled request: getFile" with timestamps. This can be used to better measure the time taken in the UCF pre-processing, content transfer and post-processing phases. <br /> <br /> <br /> <br />Appendix A: <br /> <br /> <br /> <br />Reduce the Effect of On-Access Scanning on UCF Initialization and Other Java Applets After Reboot <br /> <br />Right-click on the VirusScan icon in the system tray and choose "On Access Scan Properties. <br />Click on All Processes. <br />Click on Advanced. <br />Ensure "Scan inside archives" is NOT selected. <br />Click on the Detection tab. <br />Click on the Exclusions button. <br />Click on Add. <br />Add C:\Documents and Settings\s38737\Documentum\ucf , with "Also exclude subfolders", "On Read" and "On Write". <br />Click on OK to save. <br />Click Add to add another path. <br />Add C:\Program Files\Java with "Also exclude subfolders" and "On Read". <br />Click OK to save. <br />Appendix B: <br /> <br /> <br /> <br />Changing UCF Client Settings for All Users <br /> <br /> <br /> <br />1. Edit the <app>\webtop\wdk\contentXfer\ucf.installer.config.xml file. <br /> <br />2. In this file, you will find the following line, <br /> <br /><"xml version="1.0" encoding="UTF-8""> <br /><"dctm fileVersion="5.3.0.1" compatibilityVersion="5.3.0.1""> <br /><ucfInstaller codebase="" loggerLevel="INFO"> <br /><app id="shared" version="5.3.0.XXX" compatibilityVersion="5.3.0" /> <br /> <br />3. Change the highlighted text above from 5.3.0.XXX to 5.3.0.XXXa <br /> <br />4. Under the configurations tag, change or add the desired option. <br /> <br /><option name="name_of_option"> <br /> <br /><value>value</value> <br /> <br /></option> <br /> <br />The next time the UCF client engine is initialized on the client side, the new UCF settings will be downloaded and added to the ucf.client.config.xml file. <br /> <br /> <br /> <br />There may be cases where the "default" values in the ucf.installer.config.xml should not be applied to the client side. In this case, the "persistent" attribute can be added to the option on the client side. This will prevent any changes on the server side from being applied to that particular client. <br /> <br /><option name="name_of_option" persistent="true"> <br /> <br /><value>value</value> <br /> <br /></option> <br /> <br />If not specified, then persistent is set to false. <br /> <br /> <br /> <br />The persistent property can be specified on the ucf.installer.config.xml and in the ucf.client.config.xml. The following chart outlines the expected behavior: <br /> <br /> <br /> <br />Server Client Description <br /> <br />false false Server value will override client value. <br /> <br />true true Server value will override client value. <br /> <br />true true Server value will override client value. <br /> <br />false true Client value will not be overridden. <br /><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3860041665411026438?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-21623790916415618522009-10-01T17:15:00.000-07:002009-10-01T17:22:29.864-07:00This is a bug in D6.0 Sp1 <br /><br />Clear the cache files under App server <br /><br />for e.g : bea/user_projects/domains/dev/documentum/presets <br /><br />Restart the DA managed server.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2162379091641561852?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-7920025567818160342009-04-24T14:05:00.000-07:002009-04-24T14:07:22.423-07:00Issue:<br />Unable to view all cabinets or permmitted folders/cabinets in documentum<br /><br />Resolution:<br /><br />We need to create profile and browse the specific cabinet or select all cabinets and enable few check boxes in the properties window<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-792002556781816034?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-73476532843396101622009-04-24T14:04:00.002-07:002009-04-24T14:05:21.261-07:00Symptoms<br />Client seeing new folder created in Outlook called "Documentum Lost & Found".<br /> <br />Cause<br />The folder is created only if an import operation fails. This means that an object you intended to import into a repositiry through DCO failed to import correctly.<br /> <br />Resolution<br />The way the Lost & Found is used is as follows:<br /> <br />Managing failed move/copy operations:<br /><br />1. If DCO does not respond properly when you try to drag-and-drop an item from the right pane to your profile, you might see the following error message: Documentum Client for Outlook has found some messages that failed to be imported, and moved them to the "Documentum Lost & Found" folder.<br />2. The first time such an operation fails, DCO creates a new folder called Documentum Lost and Found in your Outlook Personal Folders. The next time you log in to Outlook (that is, once you exit Outlook and start it up again) items that failed to move or copy appear in the Documentum Lost and Found folder as unread items.<br />3. In the Documentum Lost and Found folder, you can perform any task normally available to you, such as moving, deleting, forwarding, replying, and so on.<br />4. DCO never automatically deletes messages in the Documentum Lost and Found folder; they remain there until you perform some action on them<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7347653284339610162?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-46761050727441359562009-04-24T14:04:00.001-07:002009-04-24T14:04:52.812-07:00Documentum Folders doesn't show in Outlook Tree Viewer after installing DCO Client. <br />When opening Outlook, you will get an error that says, <br /><br />The file C:\Documents and Settings\<user>\Application Data\Documentum\DCO\Documentum.pst could not be found. <br /><br />If this occurs, there is a problem with the PST file that is create. To create this file again <br /><br />1.Close Documentum Folders in Outlook <br />2.Close Outlook. <br />3. Verify that Outlook and the DCOAddin process is closed in the Task Manager. <br />4. Restart Outlook. <br /><br />When Outlook is restarted the DCOAddin will recreate the PST file. <br /><br />If there error continues and the PST file is not created. Then something is preventing the DCOAddin from creating the PST file. Make sure that the directory is not mapped and that the user has rights to add to that directory.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4676105072744135956?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-33496432618492474062009-04-24T13:57:00.000-07:002009-04-24T14:04:20.816-07:00Error:<br />There is no valid docbases specified on the DCO server.<br />The docbase can be down. Please contact the administrator.<br /><br />Resolution:<br /><br />It seems you do not have valid docbase in custom/app.xml<br /><br /><config><br /><scope><br /><application extends="dco/app.xml"><br /><!-- default repositories - the default list of 'visible/favorite' repositories, which is used to constrain projected profiles for DCO clients --><br /><default_repositories><br /><!-- NOTE: The repository name is case sensitive. --><br /><!-- <repository_name>add_your_repository_here</repository_name> --><br /><!-- . . . --><br /><repository_name>XXXXX</repository_name><br /><repository_name>YYYYY</repository_name><br /></default_repositories><br />....<br /><br />The login component used by dco/outlook is not the same as the one used when you login through the browser!<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3349643261849247406?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-75453803011562301912009-04-01T15:39:00.000-07:002009-04-01T15:42:40.843-07:00Error: UcfSesionManager$ClientException<br />in DA 6.5 or Webtop 6.5 with Weblogic 9.2 Sp3 and Sql Server 2005<br /><br />Check the exact version in ucf.installer.config.xml located at D:\bea\weblogic92\server\da.war\wdk\contentXfer and install the respective version or update the version here!!!<br /><br />Download it from http://java.sun.com/products/archive/<br /><br />here is what I have in my ucf.installer.config.xml:<br /> <platform os="windows" arch="x86"><br /> <runtime type="java" version="1.5.0" href="win-jre1.5.0_06.zip"<br /> exePath="jre1.5.0_06\bin\java.exe"><br /><br />- Intall jdk-1_5_0_06-windows-i586-p.exe in the Application Server or the system where u have UCF Errors<br /><br />- Set JAVA_HOME in System Variables<br />JAVA_HOME --> D:\Program Files\Java\jdk1.5.0_06\bin<br /><br />- Clear the cache<br /><br />- Restart the Application Server<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7545380301156230191?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-17175333801376086172009-03-12T12:25:00.000-07:002009-03-12T12:30:34.337-07:00How to resolve the error in Queue Manager log? [DM_DFC_E_CLASS_NOT_FOUND] <br /><br />How to resolve the error in Queue Manager log" [DM_DFC_E_CLASS_NOT_FOUND] Unable to instantiate the necessary java class: com.documentum.compliance.type.DmiRegistry; ERRORCODE: 202; NEXT: null<br /><br />Symptoms<br /><br />You will not able to promote document or send TBR. This is what you will see in the queue manager log:<br /><br />10:12:11,812 DEBUG [ Thread-12] DcmCustomTaskProcessor - Calling execute() on DcmQueueManager<br />10:12:16,164 ERROR [ Thread-12] DcmAuditManager - unable to create audit, action - object<br />DfException:: THREAD: Thread-12; MSG: [DM_DFC_E_CLASS_NOT_FOUND] Unable to instantiate the necessary java class: com.documentum.compliance.type.DmiRegistry; ERRORCODE: 202; NEXT: null<br /> at com.documentum.fc.bof.compoundclass.CompoundClassMgr.getTboClass(CompoundClassMgr.java:321)<br /> at com.documentum.fc.bof.compoundclass.CompoundClassMgr.getImpClass(CompoundClassMgr.java:94)<br /> at com.documentum.fc.bof.compoundclass.CompoundClassMgr.getInterfaceExtClass(CompoundClassMgr.java:156)<br /> at com.documentum.fc.client.DfPersObjFactoryWithAspects.makeObjectWithInterface(DfPersObjFactoryWithAspects.java:55)<br /> at com.documentum.fc.client.DfSession.getObjectWithInterface(DfSession.java:1645)<br /> at com.documentum.dcm.app.AuditHelper.findDmiRegistry(AuditHelper.java:493)<br /> at com.documentum.dcm.app.AuditHelper.getDmiRegistryForEvent(AuditHelper.java:49)<br /> at com.documentum.dcm.app.AuditHelper.createAuditTrail(AuditHelper.java:279)<br /> at com.documentum.dcm.app.security.DcmAuditManager.createObjAuditTrail(DcmAuditManager.java:608)<br /> at com.documentum.dcm.app.security.DcmAuditManager.createAudit(DcmAuditManager.java:224)<br /> at com.documentum.dcm.app.security.DcmAuditManager.postExecute(DcmAuditManager.java:210)<br /> at com.documentum.dcm.services.DcmManagerImpl.createAudit(DcmManagerImpl.java:747)<br /> at com.documentum.dcm.app.signoff.TBRHelper.sendTbrEventToUser(TBRHelper.java:576)<br /> at com.documentum.dcm.app.signoff.TBRHelper.sendTbrEventToPerformers(TBRHelper.java:395)<br /> at com.documentum.dcm.app.signoff.TBRHelper.sendTBRNotification(TBRHelper.java:165)<br /> at com.documentum.dcm.queue.impl.SendTBRCmd.sendTBR(SendTBRCmd.java:57)<br /> at com.documentum.dcm.queue.impl.SendTBRCmd.process(SendTBRCmd.java:41)<br /> at com.documentum.dcm.queue.impl.DcmQueueManagerImpl.execute(DcmQueueManagerImpl.java:164)<br /> at com.documentum.impl.services.task.dcm.DcmCustomTaskProcessor.processCommand(DcmCustomTaskProcessor.java:121)<br /> at com.documentum.impl.services.task.dcm.DcmCustomTaskProcessor.execute(DcmCustomTaskProcessor.java:266)<br /> at com.documentum.impl.services.task.TaskBase.doExecute(TaskBase.java:416)<br /> at com.documentum.impl.services.task.TaskBase.run(TaskBase.java:393)<br /> at com.documentum.impl.services.thread.ThreadPoolManagerImpl$TaskThread.run(ThreadPoolManagerImpl.java:272)<br /> at java.lang.Thread.run(Thread.java:534)<br />Caused by: java.lang.ClassNotFoundException: Unable to load class<br /> at com.documentum.fc.bof.classmgmt.InheritanceManagingClassLoader.loadClass(InheritanceManagingClassLoader.java:95)<br /> at com.documentum.fc.bof.compoundclass.CompoundClassMgr.getTboClass(CompoundClassMgr.java:317)<br /> ... 23 more<br />Caused by: DfException:: THREAD: Thread-12; MSG: ; ERRORCODE: ff; NEXT: null<br /> at com.documentum.fc.bof.classmgmt.BaseClassModifier.replaceSuperClass(BaseClassModifier.java:57)<br /> at com.documentum.fc.bof.classmgmt.InheritanceManagingClassLoader.loadClass(InheritanceManagingClassLoader.java:72)<br /> ... 24 more<br />Caused by: com.documentum.thirdparty.javassist.NotFoundException: com.documentum.compliance.type.DmiRegistry<br /> at com.documentum.thirdparty.javassist.ClassPool.get(ClassPool.java:301)<br /> at com.documentum.fc.bof.classmgmt.BaseClassModifier.replaceSuperClass(BaseClassModifier.java:45)<br /> ... 25 more<br />10:12:17,508 DEBUG [ Thread-12] DcmCustomTaskProcessor - DcmQueueManager execute() returned<br /><br />Cause<br />The reference is to DmiRegistry. In this particular case it is old version dbor.properties, com.documentum.compliance. It should be com.documentum.dcm.<br /><br />Resolution<br /><br />The correct mapping should be: com.documentum.dcm.type.IDmiRegistry=type,com.documentum.dcm.type.DmiRegistry,5.0<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1717533380137608617?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-79584315986612274202009-03-12T12:24:00.000-07:002009-03-12T12:29:59.057-07:00Why do I get error when installing DCM Queue Manager?<br /><br />Symptoms<br /><br />While installing DCM Queue Manager you get - Access denied when trying to execute the service script failed to execute: "D:\PROGRA~1\DOCUME~1\DCMQUE~1\smaster\srunner.exe" "D:\PROGRA~1\DOCUME~1\DCMQUE~1\scripts\svcStartMediaServer_NCGMP_QAS.txt" - Access is denied.<br /><br />Resolution<br /><br />To install DCM Queue Manager, <br /><br />1. Disable Antivirus software.<br />2. Install the application<br />3. Start the service<br />4. Enable Antivirus software.<br /><br />The DCM Queue Manager service is enabled using the srunner.exe utility. This utility allows java programs to be installed as a windows services.<br />Antivirus application can see this executable as a threat and if so, will deny access to starting the service.<br /><br />Stopping the antivirus software and installing and starting the service enables the service to be installed and started.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7958431598661227420?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-9328066204812035912009-03-12T12:19:00.000-07:002009-03-12T12:40:15.835-07:00Unexpected error: [DM_DFC_E_CLASS_NOT_FOUND] Unable to instantiate the necessary java class: com.documentum.dcm.aspect.impl.DcmControlledDocAspect<br /><br />This also explains how to Configure DTS for DCM Applications<br /><br />If you see the above error in ur DTS log file, please check the below: <br /><br />1) Copy the jars from the Application Server box to DTS/MTS box<br /><br />dcm.jar,dcmSupport.jar,dcmSupportImpl.jar,dcmQueue.jar,dcmQueueImpl.jar<br /><br />2) In My Computer --> Environmental Variables .. set the classpath (add Jars: D:\Program Files\Documentum\Shared\dcm.jar;D:\Program Files\Documentum\Shared\dcmSupport.jar;)<br /><br /> ClassPath : - D:\Program Files\Documentum\dctm.jar;D:\Documentum\config;D:\Program Files\Documentum\Shared\dcm.jar;D:\Program Files\Documentum\Shared\dcmSupport.jar;<br /><br /> JAVA_HOME : -> D:\j2sdk1.4.2_11<br /><br /> Path : -> D:\PROGRA~1\DOCUME~1\CTS\lib;D:\Program Files\Documentum\CTS\lib;D:\Program Files\Documentum\Shared;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem<br /><br />3) Regedit (Add the jars: D:\PROGRA~1\DOCUME~1\Shared\dcm.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmSupport.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmSupportImpl.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmQueue.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmQueueImpl.jar)<br /><br />My Computer\Hkey_Local_machine\System\CurrentControlSet\Services\DocumentumCTS\Parameters<br /><br />-Xbootclasspath:D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\lib\rt.jar -Xms64m -Xmx256m -Djava.protocol.handler.pkgs=sun.net.www.protocol -Djava.ext.dirs=D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\lib -Djava.library.path=D:\PROGRA~1\DOCUME~1\Shared;D:\PROGRA~1\DOCUME~1\CTS\lib -XJVMDir:D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\bin\server\jvm.dll -DCTS_CONFIG_DIR=D:\PROGRA~1\DOCUME~1\CTS\config -Dlog4j.configuration=file:D:\DOCUME~1\config\log4j.properties -DOUTPUT_DIR=D:\PROGRA~1\DOCUME~1\CTS\logs -DOUTPUT_TEST_FILES=true -DCLEAN_TEST_FILES=false -DMAX_WAIT_INTERVALS=5 -Djava.class.path=D:\PROGRA~1\DOCUME~1\CTS\lib\cts.jar;D:\PROGRA~1\DOCUME~1\dctm.jar;D:\PROGRA~1\DOCUME~1\Shared\dcm.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmSupport.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmSupportImpl.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmQueue.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmQueueImpl.jar;D:\DOCUME~1\config;D:\PROGRA~1\DOCUME~1\CTS\lib;D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\lib\jce.jar;D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\lib\ext\sunjce_provider.jar -mainclass=com/documentum/cts/services/ctsserver/CTSServerStartup -servicename=DocumentumCTS -displayname=Documentum Content Transformation Services -wrkdir=D:\PROGRA~1\DOCUME~1\CTS\lib<br /><br />4) Edit startCTS.bat (location : D:\Program Files\Documentum\CTS\server_install\CTSService ) - add the jars<br /><br />cd D:\PROGRA~1\DOCUME~1\CTS\lib<br /><br />"D:\PROGRA~1\DOCUME~1\java\1.4.2_11\bin\java.exe" -server -Xrs -Xms64m -Xmx256m -Dlog4j.configuration="file:D:\DOCUME~1\config\log4j.properties" -DCTS_CONFIG_DIR="D:\PROGRA~1\DOCUME~1\CTS\config" -DOUTPUT_DIR="D:\PROGRA~1\DOCUME~1\CTS\logs" -DOUTPUT_TEST_FILES=true -DCLEAN_TEST_FILES=false -DMAX_WAIT_INTERVALS=5 -Djava.library.path=D:\PROGRA~1\DOCUME~1\Shared;D:\PROGRA~1\DOCUME~1\CTS\lib -Djava.class.path="D:\PROGRA~1\DOCUME~1\CTS\lib\cts.jar;D:\PROGRA~1\DOCUME~1\dctm.jar;D:\PROGRA~1\DOCUME~1\Shared\dcm.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmSupport.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmSupportImpl.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmQueue.jar;D:\PROGRA~1\DOCUME~1\Shared\dcmQueueImpl.jar;D:\DOCUME~1\config;D:\PROGRA~1\DOCUME~1\CTS\lib;D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\lib\jce.jar" com.documentum.cts.services.ctsserver.CTSServerStartup -servicename="DocumentumCTS" -displayname="Documentum Content Transformation Services" -wrkdir="D:\PROGRA~1\DOCUME~1\CTS\lib"<br /><br />==><br /><br />Stop the Services in the order<br /><br />Documentum Content Transformation Services<br />Documentum Content Transformation Monitor Services<br />Documentum CTS Admin.Agent<br /> <br />Delete the log content in D:\Documentum\logs log4j.log<br /><br />- Start the 'startCTS.bat'<br />- Documentum CTS Admin.Agent<br />- Documentum Content Transformation Services<br />- Documentum Content Transformation Monitor Services<br /><br />From Next time onwards... its only required to start the below 3 services<br />- Start the 'startCTS.bat'<br />- Documentum CTS Admin.Agent<br />- Documentum Content Transformation Services<br />- Documentum Content Transformation Monitor Services<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-932806620481203591?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-5996844524511336372009-03-12T12:17:00.000-07:002009-03-12T12:39:03.215-07:00Unexpected error: [DM_DFC_E_CLASS_NOT_FOUND] Unable to instantiate the necessary java class: com.documentum.dcm.aspect.impl.DcmControlledDocAspect <br /><br />Resolution : dcmsupport.jar is not copied or has mismatch in classpath or may be duplicated.<br /><br />Make sure the following for no duplications:<br /><br />1) dcmSupport.jar and dmcSupportImpl.jar should be in only 1 location when u do a simple search in DCM application and the path should be <br /><br /> Cabinets/System/Applications/DCM/com.documentum.dcm.aspect.IDcmControlledDocAspect<br /> - dcmSupport.jar<br /> - dcmSupportImpl.jar<br /> - RuntimeEnvironment.xml<br /><br /><br />2) Classpath Settings in My computer --> Environmental variables<br /><br />UserVariables for dmadmin<br /> CLASSPATH - > D:\Program Files\Documentum\dctm.jar;D:\Documentum\config;C:\Program Files\Altova\xmlspy\XMLSpyInterface.jar;D:\bea\user_projects\domains\abraxis\myserver\upload\dcm\dcm\WEB-INF\lib\mail.jar;D:\Program Files\Documentum\Shared\dcm.jar;D:\Program Files\Documentum\Shared\dcmSupport.jar<br /><br />System Variables<br /> ClassPath - > D:\Program Files\Documentum\dctm.jar;D:\Documentum\config;D:\Program Files\Documentum\Shared\dcm.jar;D:\Program Files\Documentum\Shared\dcmSupport.jar;D:\bea\user_projects\domains\abraxis\myserver\upload\dcm\dcm\WEB-INF\lib\mail.jar;D:\Program Files\Documentum\Shared\dfc.jar;D:\Program Files\Documentum\Shared\admin.jar<br /><br /> DFC_DATA -> D:\Documentum<br /><br /> JAVA_HOME -> D:\j2sdk1.4.2_11\bin<br /><br /> Path -> D:\Program Files\Documentum\Shared;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem<br /><br />3) No changes for StartManagedWeblogic.cmd<br /><br />4) StartWeblogic.cmd (Make sure the paths are matching or change accdly)<br /> <br />set CLASSPATH=%CLASSPATH%;D:\bea\user_projects\domains\Abraxis\AdminServer\upload\dcm\dcm\dcm\strings;D:\Program Files\Documentum\shared\PDFsignClient.jar;D:\Program Files\Documentum\shared\jbossall-client.jar;D:\Program Files\Documentum\shared\jnet.jar;D:\Program Files\Documentum\shared\DmcRecords.jar;D:\Program Files\Documentum\shared\messageArchive.jar;D:\Program Files\Documentum\shared\messageService.jar;D:\Program Files\Documentum\shared\dcmQueueImpl.jar;D:\Program Files\Documentum\shared\dcmQueue.jar;D:\Program Files\Documentum\shared\bpmutil.jar;D:\Program Files\Documentum\shared\dcm.jar;D:\Program Files\Documentum\shared\dcmSupport.jar;D:\Program Files\Documentum\shared\dcmSupportImpl.jar;D:\Program Files\Documentum\shared\ctsTransformImpl.jar;D:\Program Files\Documentum\shared\ctsTransform.jar;D:\Program Files\Documentum\shared\collaboration.jar;D:\Program Files\Documentum\shared\ci.jar;D:\Program Files\Documentum\shared\castor-0.9.5.2.jar;D:\Program Files\Documentum\shared\commons-jxpath-1.1.jar;D:\Program Files\Documentum\shared\XformsCommon.jar;D:\Program Files\Documentum\shared\xforms.jar;D:\Program Files\Documentum\shared\subscription.jar;D:\Program Files\Documentum\shared\workflow.jar;D:\Program Files\Documentum\shared\xml-apis.jar;D:\Program Files\Documentum\shared\xalan.jar;D:\Program Files\Documentum\shared\log4j.jar;D:\Program Files\Documentum\shared\All-MB.jar;D:\Program Files\Documentum\shared\xtrim-api.jar;D:\Program Files\Documentum\shared\bsf.jar;D:\Program Files\Documentum\shared\dfcbase.jar;D:\Program Files\Documentum\shared\dfc.jar;D:\Documentum\config;D:\Program Files\Documentum\shared\admin.jar;D:\Documentum\config\dfc.properties;%CLASSPATH%;<br /><br />5) StartDocumentum.cmd<br />set CLASSPATH=%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%;D:\bea\user_projects\domains\abraxis\myserver\upload\dcm\dcm\dcm\strings;D:\Program Files\Documentum\shared\PDFsignClient.jar;D:\Program Files\Documentum\shared\jbossall-client.jar;D:\Program Files\Documentum\shared\jnet.jar;D:\Program Files\Documentum\shared\DmcRecords.jar;D:\Program Files\Documentum\shared\messageArchive.jar;D:\Program Files\Documentum\shared\messageService.jar;D:\Program Files\Documentum\shared\dcmQueueImpl.jar;D:\Program Files\Documentum\shared\dcmQueue.jar;D:\Program Files\Documentum\shared\bpmutil.jar;D:\Program Files\Documentum\shared\dcm.jar;D:\Program Files\Documentum\shared\dcmSupport.jar;D:\Program Files\Documentum\shared\dcmSupportImpl.jar;D:\Program Files\Documentum\shared\ctsTransformImpl.jar;D:\Program Files\Documentum\shared\ctsTransform.jar;D:\Program Files\Documentum\shared\collaboration.jar;D:\Program Files\Documentum\shared\ci.jar;D:\Program Files\Documentum\shared\castor-0.9.5.2.jar;D:\Program Files\Documentum\shared\commons-jxpath-1.1.jar;D:\Program Files\Documentum\shared\XformsCommon.jar;D:\Program Files\Documentum\shared\xforms.jar;D:\Program Files\Documentum\shared\subscription.jar;D:\Program Files\Documentum\shared\workflow.jar;D:\Program Files\Documentum\shared\xml-apis.jar;D:\Program Files\Documentum\shared\xalan.jar;D:\Program Files\Documentum\shared\log4j.jar;D:\Program Files\Documentum\shared\All-MB.jar;D:\Program Files\Documentum\shared\xtrim-api.jar;D:\Program Files\Documentum\shared\bsf.jar;D:\Program Files\Documentum\shared\dfcbase.jar;D:\Program Files\Documentum\shared\dfc.jar;D:\Program Files\Documentum\shared\ctsTransformImpl.jar;D:\Program Files\Documentum\shared\ctsTransform.jar;D:\Program Files\Documentum\shared\collaboration.jar;D:\Program Files\Documentum\shared\ci.jar;D:\Program Files\Documentum\shared\castor-0.9.5.2.jar;D:\Program Files\Documentum\shared\commons-jxpath-1.1.jar;D:\Program Files\Documentum\shared\XformsCommon.jar;D:\Program Files\Documentum\shared\xforms.jar;D:\Program Files\Documentum\shared\subscription.jar;D:\Program Files\Documentum\shared\workflow.jar;D:\Program Files\Documentum\shared\xml-apis.jar;D:\Program Files\Documentum\shared\xalan.jar;D:\Program Files\Documentum\shared\log4j.jar;D:\Program Files\Documentum\shared\All-MB.jar;D:\Program Files\Documentum\shared\xtrim-api.jar;D:\Program Files\Documentum\shared\bsf.jar;D:\Program Files\Documentum\shared\dfcbase.jar;D:\Program Files\Documentum\shared\dfc.jar;D:\Documentum\config;D:\Program Files\Documentum\shared\admin.jar;<br /><br />6) In dbor.properties<br /><br />com.documentum.services.workflow.inbox.IInbox=service,com.documentum.services.workflow.inbox.Inbox,1.0<br />com.documentum.services.workflow.startworkflow.IStartWorkflow=service,com.documentum.services.workflow.startworkflow.StartWorkflow,1.0<br />com.documentum.services.workflow.report.IWorkflowReportBuilder=service,com.documentum.services.workflow.report.WorkflowReportBuilder,1.0<br /><br />com.documentum.services.subscriptions.ISyncList=service,com.documentum.services.subscriptions.Subscriptions,1.1<br />com.documentum.services.subscriptions.ISubscriptions=service,com.documentum.services.subscriptions.Subscriptions,1.0<br /><br />dm_docset=type,com.documentum.ci.imp.Docset,1.0<br />dm_docset_run=type,com.documentum.ci.imp.DocsetRun,1.0<br />com.documentum.ci.ICiService=service,com.documentum.ci.imp.CiService,1.0<br />dm_category_assign=type,com.documentum.ci.imp.CategoryAssign,1.0<br />dm_ci_config=type,com.documentum.ci.imp.CiConfig,1.0<br />ci_config=type,com.documentum.ci.imp.CiConfig,1.0<br />dm_category=type,com.documentum.ci.imp.Category,1.0<br />dm_category_class=type,com.documentum.ci.imp.CategoryClass,1.0<br />dm_taxonomy=type,com.documentum.ci.imp.Taxonomy,1.0<br /><br />dm_xfm_form=type,com.documentum.xforms.docbase.DctmForm,1.0<br />dm_xfm_instance=type,com.documentum.xforms.docbase.XMLInstance,1.0<br />dm_xfm_schema=type,com.documentum.xforms.docbase.XMLSchema,1.0<br />com.documentum.xforms.docbase.IDctmFormService=service,com.documentum.xforms.docbase.DctmFormService,1.0<br />com.documentum.tools.docbase.IDctmDataModelService=service,com.documentum.tools.docbase.DctmDataModelService,1.0<br /><br />dmc_comment=type,com.documentum.services.collaboration.Comment,1.0<br />dmc_topic=type,com.documentum.services.collaboration.Topic,1.0<br />dmc_notepage=type,com.documentum.services.collaboration.NotePage,1.0<br />dmc_room=type,com.documentum.services.collaboration.Room,1.0<br />com.documentum.services.richtext.IRichTextManager=service,com.documentum.services.richtext.RichTextManager,1.0<br />com.documentum.services.collaboration.ICommentManager=service,com.documentum.services.collaboration.CommentManager,1.0<br /><br />dm_media_profile=type,com.documentum.services.dam.impl.transform.MediaProfile,1.1<br />dm_transform_request=type,com.documentum.services.dam.impl.transform.TransformRequest,1.1<br />com.documentum.services.dam.df.transform.IProfileService=service,com.documentum.services.dam.impl.transform.ProfileService,1.1<br />com.documentum.services.dam.df.transform.ICTSService=service,com.documentum.services.dam.impl.transform.CTSService,1.1<br /><br />com.documentum.dcm.services.DcmManager=service,com.documentum.dcm.services.DcmManagerImpl,5.0<br />com.documentum.dcm.services.IDcmReportService=service,com.documentum.dcm.services.DcmReportService,5.0<br />com.documentum.dcm.services.DcmConfigManager=service,com.documentum.dcm.services.DcmConfigManagerImpl,5.0<br />com.documentum.dcm.queue.DcmQueueManager=service,com.documentum.dcm.queue.impl.DcmQueueManagerImpl,5.0<br />com.documentum.dcm.services.IPDFsignAdapter=service,com.documentum.dcm.services.PDFsignAdapterImpl,5.0<br />com.documentum.dcm.type.IDcmDocumentClass=type,com.documentum.dcm.type.DcmDocumentClass,5.0<br />com.documentum.dcm.type.IDcmStateExtension=type,com.documentum.dcm.type.DcmStateExtension,5.0<br />com.documentum.dcm.type.IDcmPerformerCriteria=type,com.documentum.dcm.type.DcmPerformerCriteria,5.0<br />com.documentum.dcm.type.IDcmAutoProcess=type,com.documentum.dcm.type.DcmAutoProcess,5.0<br />com.documentum.dcm.type.IDmiRegistry=type,com.documentum.dcm.type.DmiRegistry,5.0<br />com.documentum.dcm.type.IAuditTrail=type,com.documentum.dcm.type.AuditTrail,5.0<br />com.documentum.dcm.type.IDcmStateProcessRule=type,com.documentum.dcm.type.DcmStateProcessRule,5.0<br />com.documentum.dcm.type.IDcmSignoffRelation=type,com.documentum.dcm.type.DcmSignoffRelation,5.0<br />dcm_extended_relation=type,com.documentum.dcm.type.DcmExtendedRelation,5.0<br />dcm_extended_relation_type=type,com.documentum.dcm.type.DcmExtendedRelationType,5.0<br />dcm_autoname=type,com.documentum.dcm.type.DcmAutoName,5.0<br />dcm_state_extension=type,com.documentum.dcm.type.DcmStateExtension,5.0<br />dcm_document_class=type,com.documentum.dcm.type.DcmDocumentClass,5.0<br />dcm_performer_extension=type,com.documentum.dcm.type.DcmPerformerCriteria,5.0<br />dcm_auto_process=type,com.documentum.dcm.type.DcmAutoProcess,5.0<br />dcm_state_process_rule=type,com.documentum.dcm.type.DcmStateProcessRule,5.0<br />dcm_extended_sysobject=type,com.documentum.dcm.type.DcmExtendedSysobject,5.0<br />dcm_signoff_relation=type,com.documentum.dcm.type.DcmSignoffRelation,5.0<br /><br />com.documentum.admin.object.IDfRemoveExpiredObjectsJob=type,com.documentum.admin.object.DfRemoveExpiredObjectsJob,1.0<br />dm_job_sequence=type,com.documentum.admin.object.DfJobSequence,1.0<br /><br /># DCM5 services<br /><br /># DCM5 types<br />com.documentum.dcm.type.IDcmControlledDoc=type,com.documentum.dcm.type.DcmControlledDoc,5.0<br />com.documentum.dcm.type.IDcmReviewPeriod=type,com.documentum.dcm.type.DcmReviewPeriod,5.0<br />dm_audittrail=type,com.documentum.dcm.type.AuditTrail,5.0<br />dmi_registry=type,com.documentum.dcm.type.DmiRegistry,5.0<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-599684452451133637?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-11549586557438972852009-03-03T10:39:00.000-08:002009-03-03T10:40:15.023-08:00Turn off Full-Text Indexing: <br />1. Shut down application server. <br />2. Shut down Index Agent. <br />3. In the applications config directory create/edit a file named dfc-dqlhints.xml. <br />That file should contain the following information: <br /><?xml version="1.0"?> <br /><!DOCTYPE RuleSet PUBLIC "dfc-dqlhints.dtd" "dfc-dqlhints.dtd"> <br /><RuleSet> <br /><Rule> <br /><Condition> <br /><Where condition="any"> <br /><Attribute operator="like">object_name</Attribute> <br /></Where> <br /></Condition> <br /><DisableFTDQL/> <br /></Rule> <br /></RuleSet> <br />4. Save and Close the file. <br />5. In dfc.properties and dfcfull.properties edit it to contain the following information: <br />dfc.dqlhits.file=<path to dfc-dqlhints.xml file> <br />6. Clear the application server cache and dmcl folders. <br />7. Start Application Server.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1154958655743897285?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-64418401249743652812009-02-13T19:56:00.000-08:002009-02-13T19:57:30.217-08:00You may see the following message,<br /><br />"Unable to initialize admin dll (OSEnv)" or "Unable to gather user rights"<br /><br />when starting Server Manager if a change has been made to any domain the user is a member of or if one of them has been deleted.<br /><br />It may also be the result of connectivity problems where a domain is unavailable and the error can be caused by varying problems with the domain.<br /><br />Check the possible domains the user is a member of has been modified, deleted or is unavailable.<br /><br />Our code calls the Microsoft function GetComputerName() which is supposed to return the NetBIOS name of the local computer. See: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/getcomputername.asp.<br /><br />Once it has the name, it uses it to call NetServerEnum() (another Microsoft call) to get the domain controllers for the computer's domain. See: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netmgmt/netmgmt/netserverenum.asp.<br /><br />If these functions fail, then an error is returned and the unable to gather user rights message is displayed.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6441840124974365281?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-73787519352637190092008-11-20T14:23:00.001-08:002008-11-20T14:23:58.089-08:00Symptoms<br /><br />UCF component unable to upload any files to Documentum. Enabling UCF trace shows no UCF server log.<br /><br /> <br /><br />An error has occurred when invoking the UCF runtime. Details:<br />Failed to connect to server - refer ucf client logs for details<br />An error has occurred when invoking the UCF runtime. Details:<br />Failed to connect to server - refer ucf client logs for details <br /><br />After closing this window, press the Refresh or Reload button on your browser to continue. <br /><br />Hide Details <br /><br />Stack Trace: <br /><br />An error has occurred when invoking the UCF runtime. Details:<br />Failed to connect to server - refer ucf client logs for details<br />com.documentum.ucf.client.install.launcher.InvocationException: An error has occurred when invoking the UCF runtime. Details:<br />Failed to connect to server - refer ucf client logs for details<br />at com.documentum.ucf.client.install.launcher.impl.RuntimeInvoker.retrieveContent(RuntimeInvoker.java:433)<br />at com.documentum.ucf.client.install.launcher.impl.RuntimeInvoker.initConnectionForSharedProcess(RuntimeInvoker.java:287)<br />at com.documentum.ucf.client.install.launcher.impl.RuntimeInvoker.initConnection(RuntimeInvoker.java:59)<br />at com.documentum.web.applet.ucfinvoker.LaunchRuntimeDelegate.connectRuntime(Unknown Source)<br />at com.documentum.web.applet.ucfinvoker.Java2DelegateImpl.access$201(Unknown Source)<br />at com.documentum.web.applet.ucfinvoker.Java2DelegateImpl$3.run(Unknown Source)<br />at java.security.AccessController.doPrivileged(Native Method)<br />at com.documentum.web.applet.ucfinvoker.Java2DelegateImpl.connectRuntime(Unknown Source)<br />at com.documentum.web.applet.ucfinvoker.LaunchRuntimeDelegate.safeConnectRuntime(Unknown Source)<br />at com.documentum.web.applet.ucfinvoker.LaunchRuntimeDelegate.getUcfSessionId(Unknown Source)<br />at com.documentum.web.applet.ucfinvoker.LaunchRuntimeDelegate.start(Unknown Source)<br />at com.documentum.web.applet.ucfinvoker.LaunchRuntime.start(Unknown Source)<br />at sun.applet.AppletPanel.run(Unknown Source)<br />at java.lang.Thread.run(Unknown Source)<br /><br /> <br /><br />SEVERE: Error during retrieveing Requests: <br /><br />java.io.EOFException<br /><br />at java.io.DataInputStream.readFully(Unknown Source)<br /><br />at java.io.DataInputStream.readUTF(Unknown Source)<br /><br />at java.io.DataInputStream.readUTF(Unknown Source)<br /><br />at com.documentum.ucf.common.transport.spi.StreamHelper.readString(StreamHelper.java:29)<br /><br />at com.documentum.ucf.client.transport.impl.ClientReceiver.getRequests(ClientReceiver.java:44)<br /><br />at com.documentum.ucf.client.transport.impl.ClientSession.handshake(ClientSession.java:510)<br /><br />at com.documentum.ucf.client.transport.impl.ClientSession.handshake(ClientSession.java:485)<br /><br />at com.documentum.ucf.client.transport.impl.ClientSession.run(ClientSession.java:201)<br /><br /> <br /><br />Cause<br /><br />Bug 118836, install dab after Webtop or DA.<br /><br /> <br /><br />If Webtop is installed before DAB, you may experience the ucf-server-api.jar issue referring to different location, the one in DAB. The reason is that, dctm.jar ->manifest.mf has the following:<br /><br />Application%20Builder/devws.jar <br /><br />And devws.jar ->manifest.mf has ucf specified as below. This jar is in C:\Program Files\Documentum\Application Builder, the ucf-server_api.jar is under C:\Program Files\Documentum\Application Builder\lib<br /><br /> <br /><br />Resolution<br /><br />1. Go to DOS prompt.<br /><br />2. Enter:<br /><br />==<br /><br />set classpath=<br /><br />==<br /><br />3. Start WebLogic from that command line prompt and see if that works.<br /><br /> <br /><br />An alternative solution is to get rid of dctm.jar from classpath. Reference all the jar files under Documentum\shared directory in the classpath.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7378751935263719009?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-77619261473181065562008-11-20T14:00:00.001-08:002008-11-20T14:00:53.382-08:00Below are things to check when seeing error "Failed to transfer content due to a transport error com.documentum.ucf.common.UCFException: All remote hosts failed":<br /> <br />Background:<br />When using ACS to retrieve content (the default content transfer mode starting in 5.3 SP1), DFC produces URLs that point to content on the ACS/Content Server machine. UCF on the browser machine tries to use these URLs to retrieve the content. These URLs are produced based on a "base url" in the ACS config attribute. (The ACS config is managed in DA.) This means the browser machines requires connecting to the ACS/Content Server machine. <br /> <br />A URL will not be generated for an ACS that is not running but if ACS goes down AFTER the URL was generated that client will fail with the error but all other content requests will succeed using the pre-ACS content transfer mode (just using Content Server) until ACS is restarted.<br /> <br />1. One possibility for the error is that URLs cannot be DNS-resolved on a client computer. (like http://localhost, or http://servername instead of http://servername.emc.com). If need be, the base URL can be changed using IAPI:<br /> <br />API>retrieve,c,dm_acs_config<br />API>set,c,l,acs_base_url<br /> SET><new value><br />API>save,c,l<br /> <br />In order to check which URL the browser is using to access content, change the UCF log level on a client side (where the browser is) by changing:<br /> <br />.level=FINE<br /> <br />In the file:<br /> <br />C:\Documents and Settings\<user-login-name>\Documentum\ucf\<computer-name>\shared\config\ucf.client.logging.properties<br /> <br />The output goes to file- C:\Documentum\Logs\ucf.trace<….>.log<br /> <br />Another way is to get the same information on a Webtop/DFC side. Enable INFO or DEBUG logging for a category<br /> <br /> com.documentum.acs<br /> <br />Webtop machine in the log4j.properties file. These changes should be picked up dynamically.<br /> <br />2. Check that a firewall does not restrict access to these URLs from the client computer.<br /> <br />3. Check the $DOCUMENTUM/shared/logs/AcsServer.log for errors.<br /> <br />4. If the following error occurs in the Java Method Server log:<br /> <br />FATAL [HttpProcessor[9080][4]] acs.com.documentum.acs.sdi.ACS -<br />java.lang.NoSuchMethodError: org.aspectj.runtime.reflect.Factory.makeJP(Lorg/aspectj/lang/JoinPoint$StaticPart;Ljava/lan<br />g/Object;Ljava/lang/Object;Ljava/lang/Object;Ljava/lang/Object;)Lorg/aspectj/lang/JoinPoint;<br /> <br />and DCM is being used in the Docbase, go to C:\Program Files\Documentum\tcf\lib or the appropriate place on the UNIX system and rename file aspectjrt1.1.0.jar to something like aspectjrt1.1.0.bak<br /> <br />In some cases, you may be getting the "all remote hosts failed" error in a standalone docbase WITHOUT DCM, and in that case, you will need to go find the 1.2.0 version of that jar file, aspectjrt-1.2.0.jar, merged with custom documentum classes in the Documentum\product\5.3\tomcat\webapps\ACS\WEB-INF\lib\ucf-server-impl.jar class.<br />If you copy that the aspectjrt-1.2.0.jar to the lib directory and rename the aspectjrt-1.1.0.jar to something like .bak, then all errors go away.<br /> <br />5. If there is an error like 'java.lang.NoClassDefFoundError: org/aspectj/lang/NoAspectBoundException', the reason for this error is that Application Builder is installed on the same machine as the Content Server. <br /> <br />App Builder and ACS server use common jar file ucf-server-api.jar. In the classpath for ACS Server, the ucf-server-api.jar located in program Files\Application Builder\lib directory has precedence over the same jar file present in ACS server webapp lib directory. Quick test to confirm this would be rename the ucf-server-api.jar in Application Builder lib directory to ucf-server-api.bak and restart the Java Method Server. Note that you have to stop the method server before renaming the jar file as the jar will be in use while the server is running and will not allow you to rename the file. <br /><br /><br />The workaround for this is to install Application Builder on a different machine or modify the classpath of the java method Server so that App Builders ucf-server-api.jar is not in the classpath of the java method server.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7761926147318106556?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-90735138141576906822008-11-20T13:43:00.000-08:002008-11-20T13:48:42.420-08:00How do I enable tracing for UCF<br /><br />With UCF there are two types of logging available for diagnostics. There are client side (browser) and server side (application server) logging available. <br /><br />Client Side Logging:<br /><br />To enable client side logging, 2 files will need to be modified. Both of these files can be found in the folder: <br /><br />C:\Documents and Settings\<USERNAME>\Documentum\ucf\<HOSTNAME>\shared\config\<br /><br />where USERNAME is the windows user ID and HOSTNAME is the machine hostname where the testing is being done. <br /><br />The first file to be edited is ucf.client.config.xml. The following entry should be changed to true: <br /><br /> <option name="tracing.enabled"><br /> <value>true</value><br /> </option><br /><br />The following entry will need to be added as well: <br /><br /> <option name="debug.mode"><br /> <value>true</value><br /> </option><br /><br />The next file to be edited is ucf.client.logging.properties and set the .level entries to ALL (all caps). The debugging levels available are (from least informative to most): <br /><br />SEVERE (highest value) <br />WARNING <br />INFO <br />CONFIG <br />FINE <br />FINER <br />ALL<br />Once these changes are made, UCF will begin logging on the client side starting with the next invocation. All output will be logged to: C:\Documentum\logs\ucf.client.*.log. <br /><br />App Server Logging:<br /><br />To enable UCF tracing, the following file in the WDK application will need to be edited: <br /><br />../WEB-INF/classes/ucf.server.config.xml <br /><br />In this file, the following entry will need to be set to true: <br /><br /> <option name="tracing.enabled"><br /><br /> <value>true</value> <br /> </option><br /><br />UCF will log on the app server to $DOCUMENTUM_SHARED/logs/trace.log and/or wdk.log (depending on how log4j is configured). These changes will require a restart of the app server.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-9073513814157690682?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-60831457591572687262008-11-07T10:11:00.000-08:002008-11-07T10:12:07.469-08:00A simple Hello World example.<br /><br />public class Hello {<br /><br />public static void main(String argv[]) {<br /><br />System.out.println("Hello world !");<br /><br />} <br /><br />}<br /><br />then, when you compile it: <br /><br />> javac Hello.java<br /><br />and want to execute it:<br /><br />> java Hello<br /><br />Exception in thread "main" java.lang.NoClassDefFoundError: Hello<br /><br />We set the CLASSPATH and JAVA_HOME enviroment variable correctly, and the problem was still the same..<br />When we copied the Hello.class into a lib directory of JAVA_HOME, it worked, but not from the current directory !<br /><br />We tried different versions of java.. and do you know where this stupid problem is?<br /><br />in the CLASSPATH there should be:<br />CLASSPATH=.;c:\programme\jboss\lib;c:\programme\<br />j2sdk1.4.2_08\lib;c:\programme\j2sdk1.4.2_08\jre\lib; ...<br /><br />yes.. a dot .. it means, that it will search for classes bytecode in the current directory !<br /><br />you can also tell java to search the current directory with the -classpath parameter<br /><br />> java -classpath . Hello<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6083145759157268726?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-57339967184735485682008-10-23T14:47:00.000-07:002008-10-23T14:48:11.232-07:00Symptoms<br /><br />When configuring the repository with automatic renditions on import, the renditions are not happening.<br /><br />Cause<br /><br />Register.xml is missing an entry for the PDF profile.<br /><br />Resolution<br /><br />Follow the steps given in Pg 26,27 in the DTS Admin Guide for configuring the automatic renditions on import. You could find the renditions are not happening. This is because you need to add one more entry to the register.xml:<br /><br /> <br /><br />1. Stop the CTS Services.<br /><br />2. Edit the register.xml(System/Media Server/System Profiles).<br /><br />Add this to the <Profilesequence>:<br /><br /><InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken="target_format" Literal="true"/><br /><br />3. Back up the log folder.<br /><br />4. Start the CTS. <br /><br />5. Check the logs for any errors.<br /><br />6. Import the document and check the renditions<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-5733996718473548568?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-49471442580310433072008-10-12T21:27:00.000-07:002008-10-14T17:26:57.723-07:00When you try to run the DocApp Installer with the ldap authentication, you may receive the error message below: <br /><br />User "User_name" DOES NOT have Super User privileges. <br /><br />EXPLANATION OF THE PROBLEM: <br /><br />When you connect to the Docbase with the ldap authentications, you DO NOT need to specify an OS Domain Name. However, when you connect to the Docbase via DocApp Installer, you DO need to login with the user_name, Password and OS Domain name (even a dummy Domain name will work). <br /><br /><br />Your login to the Docbase via DocApp Installer with the user_name, Password and OS Domain name successes, but when you run the installer, will be NOT able to install the docapp and receive the error message above even you DO have a Super User privileges. <br /><br /><br /><br />FIXING THE PROBLEM (ERROR): <br /><br />1) Login to the Docbase via DA. <br /><br />2) Select the user try to install the DocApp and go on his Properties. <br /><br />3) In the attribute "Windows Domain" add the Domain name (or a dummy Domain name). <br /><br />4) Save and exit. <br /><br />5) Login and run the DocApp Installer again, it will work. <br /><br /><br />NOTE: You need to use the SAME Domain name to login to the DocApp Installer as the one you specified in the attribute "Windows Domain".<br /><br /><br />----------------------<br /><br />Check the user_os_name: this should not be blank. it should be a valid name like 'dmadmin' then this issue will not occur<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4947144258031043307?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-89095779465191513442008-10-05T12:36:00.000-07:002008-10-05T12:37:26.745-07:00Symptoms<br /><br />Need to troubleshoot the BOF user setup to allow connecting to a Global Repository/ Global Registry.<br /><br />Cause<br /><br />Troubles using BOF (TBOs/SBOs) or using version 6 web clients and be caused due to incomplete or incorrect configuration.<br /><br />Resolution<br /><br />To use BOF (TBO/SBO) requires that at least one of your Repositories be designated as the BOF Global Registry. Each Application Server must identify the BOF Global Registry it will use via the dfc.properties file. <br /><br />There are two parts to setting up the BOF Global Registry: <br /><br />1) making sure the "dm_bof_registry" Repository user is active.<br /><br />2) making sure that the dfc.properties file on your Application Server(s) are correctly referencing the Repository that is acting as the BOF Global Registry and has the listed the correct user information for the dm_bof_registry user. <br /><br />1. Verifying that a Repository is the BOF Global Registry: <br /><br />=================================== <br /><br />-Using Documentum Administrator (DA), log into the Repository that should be the BOF Global Registry, using an administrator account. <br /><br />-In Classic view, in the left navigation tree, click on the Administration node. In the page that appears, under the heading "User Management", click on "Search for Users". <br /><br />-Search for the following user: 'dm_bof_registry" (enter this value next to the User Name label, and click Search). <br /><br />-View the properties of this user "dm_bof_registry" (click the (i) icon). <br /><br />-Make note of the user's 'State' and 'User Login Name'. <br /><br />If the user State is 'Inactive', then this Repository is not the BOF Global Registry. To make this Repository the BOF Global Registry, follow Steps 2-4. <br /><br />If the BOF Global Registry user is 'Active', you need to verify some information in your dfc.properties file on your Application Server(s). <br /><br />From the Application Server machine, locate the dfc.properties file. <br /><br />Open this file in any text editor. Ensure the following three attributes are set in the dfc.properties file: <br /><br /> dfc.bof.registry.repository = <br /><br /> dfc.bof.registry.username = <br /><br /> dfc.bof.registry.password = <br /><br />Without the above three entries, the BOF Global Registry will not be set. <br /><br />If these entries are missing or values are not complete, you will need to add and populate these values. See the following steps for more details.<br /><br />2. Enabling the BOF Global Registry <br /><br />=================================== <br /><br />The following section outlines the steps required to enable the BOF Global Registry using the Documentum Administrator (DA) application. <br /><br />-Log into Documentum Administrator (DA) as an Administrator in the Repository where you want to enable TBO/SBO functionality. <br /><br />-In Classic view, in the tree, click on the Administration node. In the page that appears, under the heading "User Management", click on "Search for Users". <br /><br />-Search for the following user: 'dm_bof_registry" (enter this value next to the User Name label, and click Search). <br /><br />-View the properties of this user 'dm_bof_registry" (click the (i) icon). <br /><br />- The properties page will appear. From the properties page, ensure the following options and values are set to the following: <br /><br /> User State: Active <br /><br /> User Source: Inline Password <br /><br /> Restrict Folder Access: System <br /><br />- For security purposes, change the default password (make a note of the new password). <br /><br />- Click OK on the 'dm_bof_registry' user 'Properties' page. <br /><br />3. Verifying the dfc.properties file <br /><br />==================================== <br /><br />On each Application Server, locate the dfc.properties file. Open this file in any text editor. Ensure the following three attributes are set in the dfc.properties file: <br /><br /> dfc.bof.registry.repository = <br /><br /> dfc.bof.registry.username = <br /><br /> dfc.bof.registry.password = <br /><br />Without the above three entries, the BOF Global Registry will not be set. <br /><br />Note: The password supplied in the entry 'dfc.bof.registry.password' must be consistent with the password provided when setting the 'dm_bof_registry' password via Documentum Administrator (DA). The password must also be encrypted. For information on how to encrypt the password, see the next section in this document, entitled 'Encrypting Passwords for the dfc.properties file'. <br /><br /> <br /><br />4. Encrypting Passwords for the dfc.properties file <br /><br />=================================================== <br /><br />The password provided in the 'dfc.properties' file must be encrypted. A utility is provided to encrypt this password. The following section outlines the steps required to invoke the password utility program to encrypt a password. <br /><br />From a command prompt, execute the following: <br /><br /> java com.documentum.fc.tools.RegistryPasswordUtils <password><br /><br />Note- If you are using java methods that use the TBOs/SBOs then you will need the following entries on the %DM_Home/config/dfc.properties file as well <br /><br /> dfc.bof.registry.repository = <br /><br /> dfc.bof.registry.username = <br /><br /> dfc.bof.registry.password =<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-8909577946519151344?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-4168644563063986612008-10-02T15:15:00.000-07:002008-10-02T15:16:08.551-07:00Cause<br /><br />This can be because you have not configured your docbase yet, or because you have registered the service as an invalid user. <br /><br />Resolution<br /><br />When you first install a Transformation Services product you will only see the Admin listed as a service. This is because you have not configured to a docbase yet. Once you run the configuration utility to add a docbase, you should see three services: <br /><br />Documentum Content Transformation Monitor Service <br />Documentum Content Transformation Services <br />Documentum CTS Admin. Agent<br /> <br /><br />If you do not see three services after configuring you docbase this is most likely because the user that you used when installing the Transformation Services Product was not a local Administrator, or you did not specify the domain if it was a domain user. To resolve the issue you can do one of two things:<br /><br /> <br /><br />Unconfigure and uninstall and then re-install using a local Admin and domain in necessary. <br />Register the service manually by running the following utility:<br /> cmd> C:\Program Files\Documentum\CTS\server_install\CTSService\InstallLocalCTS.bat<br /><br /> <br /><br />This should register the service with the Local System account. You will then need to manually change it to run as the local admin user.<br /><br /> <br /><br />Notes: <br /><br />You can start the CTS service from a bat file to see if there are any problems with the service starting.<br /> cmd> C:\Program Files\Documentum\CTS\server_install\CTSService\startCTS.bat<br /><br /> Make sure you run this from the command console as you will see any error message in the terminal.<br /><br />You can reference the install.log located on the same directory as the installer for more information. <br />You can also run the installer with the following option for more verbose information:<br /> cmd> rptsWinSuiteSetup.exe -is:log "C:\temp\rpts_install_log_txt"<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-416864456306398661?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-48622055406512615362008-10-01T23:28:00.000-07:002008-10-01T23:29:53.808-07:00If after your upgrade to eContent Server 4.2.6f or higher, your attached lifecycle or promote operations fail and see your dm_bp_transition log files contain single line entries such as the one below, you should remove any Print #2 statements from your custom Action or PostProc procedure code. <br /><br />Sample Error: <br />[ErrorCode] 1700 [ServerError] Illegal Procedure Call 'Action'. Dmbasic error: 52 <br /><br /><br />Server patch version 4.2.6f made changes to the dm_bp_transition.ebs file so log files are ONLY created when there is an error. This is to address the large number of dm_bp_transition log files generated on the server (bug 42336). Any "Print #2," statements in you custom procedures that use to print to the dm_bp_transition log file, will now cause the procedure to fail since the file is only opened when an error condition occurs. <br /><br />If you want to print to a custom log file you should open your own log file for output in your custom code and number it something other than #2. For example, in a custom PostProc procedure you could do the following: <br /><br />===================================================== <br />Public Function PostProc(ByVal SessionID As String, _ <br />ByVal ObjectId As String, _ <br />ByVal UserName As String, _ <br />ByVal TargetState As String, _ <br />ByRef ErrorStack As String) As Boolean <br /><br />Dim rci as integer <br />Dim ret as Boolean <br />Dim OutFile as String <br /><br />On Error GoTo PostProc_Error <br /><br />PostProc = False <br /><br />OutFile = "my_debug_" & SessionID & ".txt" <br />ErrorStack = "Opening debug file " & OutFile & "for output:" <br /><br />Open OutFile For Output As #4 <br />Print #4, now() & " In PostProc Procedure..." <br /><br />...<your PostProc processing code>... <br /><br />PostProc = True <br /><br />Print #4, "PostProc Procedure Successful" <br />Close #4 <br /><br />Exit Function <br /><br />PostProc_Error: <br /><br />ErrorStack = "PostProcess Procedure Failed: " & ErrorStack <br />Print #4, ErrorStack <br />Close #4 <br /><br />End Function <br /><br />===================================================== <br /><br />The rest of your processing code would also contain any additional debug Print #4 statements. <br /><br />This debug file will be written to the %DM_HOME%\bin directory on Windows or $DM_HOME/bin directory on Unix, of the server machine.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4862205540651261536?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-61138738542822691642008-09-30T16:06:00.000-07:002008-09-30T16:07:22.016-07:00How to fix the following errors in DAB for DCM docapp? This can happen if the DCM docapp has been installed multiple times. [DM_API_E_EXIST]error: "Document/object specified by 4b0027ed800f26a9 does not exist." [DM_SYSOBJECT_E_CANT_FETCH_INVALID_ID]error: "Cannot fetch a sysobject - Invalid object ID 4b0027ed800f26a9" <br /><br />Here are the step to clear out the DAB errors: <br /><br /><br />1. Clean up the dmcl cache on the DAB box, delete the content under these subfolders located in c:\documentum\dmcl and c:\documentum\[docbase_name] <br /><br />2. Re-run the DAB to open up dcm docapp. Write down the object_id of the orphaned objects <br /><br />3. Once you got the list of errored object ids, log into DA, navigate to <br /><br />* /system/Application/dcm, select 'how all object on the filter' on the upper right hand side <br /><br />* open up the dcm docapp(the virtual document one) by clicking on it <br /><br />* then select all _ref_4Bxxxxx that got from step2. <br /><br />* from the pull down menu, Document->Virutal Document->remove child from dcm docapp, repeat this for all the orphaned object ids <br /><br />4. Checkin the dcm docapp as the same version. <br /><br />Now you should be able to open DCM docapp from DAB without errors.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6113873854282269164?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-15671404595294109572008-09-29T20:24:00.000-07:002008-09-29T20:26:52.812-07:00Use the following steps:<br /><br /> <br /><br />1. Get the object id of the controlled document that failed with promotion. Make sure you have the correct ID if the Controlled Document is a non-current version. <br /><br />2. In DQL run the following query to find the status of the promotion: <br /><br /><br />select status from dcm_process_relation where relation_name = 'dcm_promote' and parent_id = '{OBJECT ID From step1}' <br /><br />The status should be "Pending', if this is the case, run the following DQL to update the status: <br /><br />update dcm_process_relation object set status = 'success' where relation_name = 'dcm_promote' and parent_id = '{OBJECT ID From step1}' <br /><br />3. Retry promote.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1567140459529410957?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-63575635339940676952008-09-29T20:00:00.000-07:002008-09-29T20:20:21.570-07:001. Set the Classpath for following: <br /><br />C:\Program Files\Documentum\Shared\dcm.jar <br />C:\Program Files\Documentum\Shared\dcmSupport.jar <br />C:\Program Files\Documentum\Shared\dcmQueue.jar <br />C:\Program Files\Documentum\dctm.jar<br /><br />2.Where are queue manager Logs <br /><br />C:\Program Files\Documentum\dcmQueueManager\docbases\<docbase_name>\config\logs <br /><br />3. Login into Documentum Administrator (DA) <br /><br />Go to locations and locate the files listed. <br />Cabinets/System/Media Server/Command Line Files <br />dcmCustomProfile.xml <br />ProfileSchema.dtd <br />Cabinets/System/Media Server/Profiles <br />ProfileSchema.dtd <br />Cabinets/System/Media Server/System Profile <br />dcmCustomProfile.xml <br />ProfileSchema.dtd <br />register.xml <br /><br />If the Profiles are missing copy the xml files from Content Server from: <br /><br />C:\Program Files\Documentum\dcmQueueManager\docbases\dcm53sp1_o9i\config\profiles <br /><br />4. Queue manager needs to be installed for every instance of the Docbase in case there are mutilple Docbases <br /><br />5. Stop the Queue manager service and execute the following Query for DCM 5.3 spx <br /><br />DQL> select * from dmi_queue_item where name='dcm_custom_job' <br /><br />If there is no result set, then the request is not being sent to the Queue manager, and there is no Docbase instance against the Queue manager <br /><br />- Install DCM Queue manager Instance Add or Remove select the Docbase for the Installation ( Start - Programs - Documentum- DCM Queue Manager Instance Add or Remove) <br /><br />6. User needs to have Write Permission to Promote the Controlled Document or Should be a Coordinator to Promote CD. <br /><br />7. If the QM is installed on D:\ drive, need to check if dctm.jar is being set correctly in the classpath. <br /><br />8. Check if the Queue items are visible by running the following Query. <br /><br />For DCM 5.2.5 spx:<br /><br />DQL> Select * from dmi_queue_item where name = 'dm_mediaserver' (DCM 5.2.5 SPx) <br /><br />DQL> Delete dmi_queue_item objects where name='dm_mediaserver' <br /> <br />For DCM 5.3 spx:<br />DQL> Select * from dmi_queue_item where name = 'dcm_custom_job' (DCM 5.3 SPx) <br />DQL> Delete dmi_queue_item objects where name='dcm_custom_job'<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6357563533994067695?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-44922099440882196302008-09-27T22:19:00.001-07:002008-09-27T22:19:27.707-07:00Yes, you can reinstall a docapp on a docbase more than once. <br /><br /><br />Reinstalling a docapp after some modifications will not cause any problems on the target docbase. Basically, a docapp is just a virtual document, and all properties of a virtual document apply to a docapp. <br /><br /><br />To clarify further, all objects in the docapp such as lifecycle and alias set will be versioned after you reinstalled the docapp. Certain objects, such as custom object types and custom attributes are not versioned. Instead these objects are replaced by the newer version that are installed with the new docapp. <br /><br /><br />If for some reasons, the modifications that were made on the objects in the docapp was not satisfactory, then you can delete the newer version of the objects. <br /><br /><br />For example: <br /><br /><br />- You created a lifecycle on the development docbase, archived, and installed it on the production docbase. <br /><br />- Then you made some modifications on the lifecycle in the same docapp, and you reinstalled the docapp to the production docbase. <br /><br />- However, the changes that you made were not complete. <br /><br />- You can delete the latest version of the lifecycle using Developer Studio inside the docapp on your production docbase. <br /><br />- Or, you can make the necessary changes on your development system and reinstall the docapp again.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4492209944088219630?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-25144771365414755832008-09-27T21:49:00.001-07:002008-09-27T21:54:24.950-07:00When attempting to delete/destroy a lifecycle you may get the following error: <br /><br />[DM_POLICY_E_CANT_DESTROY]error: "Cannot destroy policy identified by <br /><dm_policy_id> since its state is installed or currently referenced by <br />some sysobject." <br /><br />To delete a lifecycle, first make sure that no documents in the docbase are referring to that Lifecycle. Run the following DQL to find out if there are any documents referring to the lifecycle: <br /><br />select * from {object_type} where r_policy_id = '{lifecycle_object_id}' <br /><br />If no documents are using or referring to the Lifecycle, then the most likely cause of this error is that the Lifecycle is still in an "Installed" state in the docbase. To uninstall the Lifecycle and destroy the lifecycle run the following API's: <br /><br />uninstall,c,{lifecycle_id} <br />destroy,c,{lifecycle_id}<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2514477136541475583?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-15986318482329004252008-09-27T19:43:00.000-07:002008-09-27T19:44:29.228-07:00Symptoms<br /><br />When trying to add a DCM queueManager instance, the following error is received in a popup window.<br /><br />DiWAExecuteProcess failed!--DiUtil:ExecuteProcess failed to execute :D:\\Progra~1\DOCUMEN~1\smaster\srunner.exe" "d:\PROGRA~1\DOCUME~1\DCMQUE~1\scripts\svcStartMediaServer_edoctst.txt" -- The system cannot find the file specified; for more detailed information, see the error log:<br /><br />Cause<br /><br />The configurator cannot find srunner.exe. This could be because a virus scanner is deleting the file.<br /><br />Resolution<br /><br />Turn off viruscan temporarily. Replace a copy of rsunner.exe in the install directory (i.e., C:\program files\Documentum\DCMQueueManager\smaster) from another environment, otherwise, reinstall DCM QueueManager.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1598631848232900425?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-9635565016793347752008-09-26T14:04:00.001-07:002008-09-26T14:04:53.975-07:00[DM_API_E_EXIST]error: "Document/object specified by 0b01278f8000bc3b does not exist."<br /><br />[DM_SYSOBJECT_E_CANT_FETCH_INVALID_ID]error: "Cannot fetch a sysobject - Invalid object ID 0b01278f8000bc3b"<br /><br />The error is pointing to a folder that no longer exists. Clear the dmcl cache on the client and CS host. Restart DAB and open the DocApp, this should take care of the problem. <br /><br />Also flush the cache for the folder object<br />API>Flush,c,ddcache,dm_folder<br />API>Flush,c,registrycache,dm_folder<br />API>Flush,c,persistentcache<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-963556501679334775?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-59725038464619708092008-09-26T12:58:00.001-07:002008-09-26T12:58:32.594-07:00This list was updated on April 21, 2005. It includes up to 5.3 object list. <br /><br /><br />NOTE: There is a gap in the sequence due to the fact that composites have <br /><br />been removed. Tag 22 is no longer used. <br /><br />dm_audittrail_attrs = 0; 00 (also dm_auth_config, dmc_completed_workflow, dmc_completed_workitem, dmc_composite_predicate, dmc_module_config, dmc_readcomment, dm_state_type, dmc_transition_condition, dmi_wf_attachment, dmi_wf_timer, dmc_workqueue, dmc_workqueue_doc_profile, dmc_workqueue_policy, dmc_workqueue_user_profile) <br /><br /><br />dmi_session = 1; 01 <br /><br />dm_object = 2; 02 <br /><br />dm_type = 3; 03 <br /><br />dm_collection = 4; 04 <br /><br />dmr_containment = 5; 05 <br /><br />dmr_content = 6; 06 <br /><br />dm_app_ref = 7; 07 <br /><br /><br />dm_sysobject = 8; 08 (also dm_acs_config, dm_application, dm_cache_config, dm_category_class, dm_ci_config, dmc_comment, dm_component, dm_ftindex_agent_config, dm_ftengine_config, dmc_jar, dm_job, dm_job_request, dm_job_sequence, dm_ldap_config, dm_locator, dm_media_profile, dm_network_location_map, dm_procedure, dm_qual_comp, dm_retainer, dmc_richtext, dmc_rps_authority, dmc_rps_base_date, dmc_rps_child_strategy, dmc_rps_condition, dmc_rps_contact, dmc_rps_disposition_method, dmc_rps_event, dmc_rps_hold, dmc_rps_retainer, dmc_rps_retention_policy, dm_script, dm_smart_list, dm_ssa_policy, dm_webc_config, dm_webc_target) <br /><br /><br />dm_document = 9; 09 (also dm_docset, dm_docset_run, dm_email_message, dm_esign_template, dmc_notepage, dmc_tcf_activity, dmc_tcf_activity_template, dm_xfm_form, dm_xfm_instance, dm_xfm_schema, dm_xml_config, dm_xml_custom_code, dm_xml_style_sheet, dm_xml_zone) <br /><br /><br />dm_query = 10; 0a <br /><br />dm_folder = 11; 0b (also dmc_aspect_type, dm_category, dmc_java_library, dmc_module, dmc_room, dm_taxonomy, dmc_topic, dmc_workqueue_category, dm_xml_application) <br /><br /><br />dm_cabinet = 12; 0c <br /><br />dm_assembly = 13; 0d <br /><br />dm_store = 14; 0e <br /><br />dm_fulltext = 15; 0f <br /><br />dm_method = 16; 10 <br /><br />dm_user = 17; 11 <br /><br />dm_group = 18; 12 <br /><br />dm_api = 20; 14 <br /><br />dm_type_manager = 21; 15 <br /><br />dm_composite = 22; 16 <br /><br />dm_outputdevice = 23; 17 <br /><br />dm_router = 24; 18 <br /><br />dm_registered = 25; 19 <br /><br />dmi_queue_item = 27; 1b <br /><br />dm_verity_coll = 28; 1c <br /><br />dm_event = 29; 1d <br /><br />dmi_vstamp = 30; 1e <br /><br />dmi_index = 31; 1f <br /><br />dmi_sequence = 32; 20 <br /><br />dm_transaction_log = 33; 21 <br /><br />dm_file = 34; 22 <br /><br />dmi_otherfile = 35; 23 <br /><br />dm_verity_index = 36; 24 <br /><br />dm_inbox = 37; 25 <br /><br />dmi_registry = 38; 26 <br /><br />dm_format = 39; 27 <br /><br />dm_filestore = 40; 28 <br /><br />dm_netstore = 41; 29 <br /><br />dm_linkstore = 42; 2a <br /><br />dmi_linkrecord = 43; 2b <br /><br />dm_distributedstore = 44; 2c <br /><br />dmi_replica_record = 45; 2d <br /><br />dmi_type_info = 46; 2e <br /><br />dm_dump_record = 47; 2f <br /><br />dmi_dump_object_record = 48; 30 <br /><br />dm_load_record = 49; 31 <br /><br />dmi_load_object_record = 50; 32 <br /><br />dmi_change_record = 51; 33 <br /><br />dm_blob_ticket = 52; 34 <br /><br />dm_staged_document = 53; 35 <br /><br />dm_dist_comp_record = 54; 36 <br /><br />dm_relation = 55; 37 (also dmc_aspect_relation, dm_category_assign, dmc_rps_phase_rel, dmc_rps_retainer_event_rel, dm_state_extension, dm_relation_ssa_policy, dmc_wf_package_schema) <br /><br /><br />dm_relationtype = 56; 38 <br /><br />dm_location = 58; 3a <br /><br />dm_fulltext_index = 59; 3b <br /><br />dm_docbase_config = 60; 3c <br /><br />dm_server_config = 61; 3d <br /><br />dm_mount_point = 62; 3e <br /><br />dm_docbroker = 63; 3f <br /><br />dm_blobstore = 64; 40 <br /><br />dm_note = 65; 41 <br /><br />dm_remotestore = 66; 42 <br /><br />dm_remoteticket = 67; 43 <br /><br />dm_docbaseid_map = 68; 44 <br /><br />dm_acl = 69; 45 <br /><br />dm_policy = 70; 46 <br /><br />dm_reference = 71; 47 <br /><br />dm_recovery = 72; 48 <br /><br />dmi_package = 73; 49 <br /><br />dmi_workitem = 74; 4a <br /><br />dm_process = 75; 4b <br /><br />dm_activity = 76; 4c <br /><br />dm_workflow = 77; 4d <br /><br />dm_dd_info = 78; 4e <br /><br />dm_nls_dd_info = 79; 4f <br /><br />dm_domain = 80; 50 <br /><br />dm_aggr_domain = 81; 51 <br /><br />dm_expression = 82; 52 <br /><br />dm_literal_expr = 83; 53 <br /><br />dm_builtin_expr = 84; 54 <br /><br />dm_func_expr = 85; 55 <br /><br />dm_cond_expr = 86; 56 <br /><br />dm_cond_id_expr = 87; 57 <br /><br />dmi_expr_code = 88; 58 <br /><br />dm_key = 89; 59 <br /><br />dm_value_assist = 90; 5a <br /><br />dm_value_list = 91; 5b <br /><br />dm_value_query = 92; 5c <br /><br />dm_value_func = 93; 5d <br /><br />dm_federation = 94; 5e <br /><br />dm_audit_trail = 95; 5f (also dm_audittrail_acl, dm_audittrail_group) <br /><br /><br />dm_extern_store = 96; 60 <br /><br />dm_extern_file = 97; 61 (also <br /><br />dm_extern_url = 98; 62 <br /><br />dm_extern_free = 99; 63 <br /><br />dmi_subcontent = 100; 64 <br /><br />dm_foreign_key = 101; 65 <br /><br />dm_alias_set = 102; 66 <br /><br />dm_plugin = 103; 67 <br /><br />dmi_dd_common_info = 104; 68 <br /><br />dmi_dd_type_info = 105; 69 <br /><br />dmi_dd_attr_info = 106; 6a <br /><br />dm_display_config = 107; 6b <br /><br />dm_scope_config = 108; 6c <br /><br />dm_ca_store = 109; 6d <br /><br />dm_docuworks = 128; 80<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-5972503846461970809?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-31218220007214762882008-09-25T13:50:00.000-07:002008-09-25T13:51:11.066-07:00http://developer.emc.com/developer/Articles/ConfiguringDFCDevEnv.htm<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3121822000721476288?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-89183552696484936342008-09-25T12:11:00.001-07:002008-09-25T12:11:58.908-07:00Using the Nslookup Command-Line Tool to Find the IP Address of an SMTP Server <br />To connect to a destination SMTP server by using Telnet on port 25, you must have the fully qualified domain name (FQDN) or the IP address of the SMTP server. The easiest way to find this information is to use the Nslookup command-line tool to find the MX record for the destination domain.<br /><br /> To use the Nslookup tool to find the IP address of an SMTP server <br />At a command prompt, type nslookup, and then press ENTER. This command opens the Nslookup session.<br /><br />Type set type=mx and then press ENTER.<br /><br />Type set timeout=20 and then press ENTER. By default, Windows DNS servers have a 15-second recursive DNS query time-out limit.<br /><br />Type the name of the domain for which you want to find the MX record. For example, to find the MX record for the fabrikam.com domain, type fabrikam.com., and then press ENTER.<br /><br />Note: <br />The trailing period ( . ) indicates a FQDN. The use of the trailing period prevents any default DNS suffixes that are configured for your network from being unintentionally added to the domain name. <br /><br />The output of the command will resemble the following:<br /><br /> Copy Code <br />fabrikam.com mx preference=10, mail exchanger = mail1.fabrikam.com<br />fabrikam.com mx preference=20, mail exchanger = mail2.fabrikam.com<br />mail1.fabrikam.com internet address = 192.168.1.10<br />mail2 fabrikam.com internet address = 192.168.1.20 <br /><br />You can use any of the host names or IP addresses that are associated with the MX records as the destination SMTP server. A lower value of preference indicates a preferred SMTP server. You can use multiple MX records and different values of preference for load balancing and fault tolerance.<br /><br />When you are ready to end the Nslookup session, type exit, and then press ENTER.<br /><br />Note: <br />Firewall or Internet proxy restrictions that are imposed on your organization's internal network may prevent you from using the Nslookup tool to query public DNS servers on the Internet.<br />MX records are not strictly required for internal message flow inside an Exchange organization. If you have to find the FQDN of any Hub Transport server or subscribed Edge Transport server in your organization, you can use the following command in the Exchange Management Shell: Get-ExchangeServer | where {$_.isHubTransportServer -eq $true -or $_.isEdgeServer -eq $true} | Format-List Fqdn,ServerRole<br />For more information, see Get-ExchangeServer and Pipelining. <br /><br /> Using Telnet on Port 25 to test SMTP Communication <br />The procedure in this section shows how to use Telnet on port 25 to test SMTP communication. The procedure uses the values that are described in the following list:<br /><br />Destination SMTP server mail1.fabrikam.com<br /><br />Source domain contoso.com<br /><br />Sender's e-mail address chris@contoso.com<br /><br />Recipient's e-mail address kate@fabrikam.com<br /><br />Message subject Test from Contoso<br /><br />Message body This is a test message<br /><br />Note: <br />You should always use a valid sender e-mail address so that any non-delivery report (NDR) messages that are generated by the destination SMTP server are delivered to the sender of the message. <br /><br /> To use Telnet on port 25 to test SMTP communication <br />At a command prompt, type telnet, and then press ENTER. This command opens the Telnet session.<br /><br />Type set localecho and then press ENTER. This optional command lets you view the characters as you type them. This setting may be required for some SMTP servers.<br /><br />Type set logfile <filename>. This optional command enables logging of the Telnet session to the specified log file. If you only specify a file name, the location of the log file is the current working directory. If you specify a path and a file name, the path must be local to the computer. Both the path and the file name that you specify must be entered in the Microsoft DOS 8.3 format. The path that you specify must already exist. If you specify a log file that doesn't exist, it will be created for you.<br /><br />Type open mail1.fabrikam.com 25 and then press ENTER.<br /><br />Type EHLO contoso.com and then press ENTER.<br /><br />Type MAIL FROM:chris@contoso.com and then press ENTER.<br /><br />Type RCPT TO:kate@fabrikam.com NOTIFY=success,failure and then press ENTER. The optional NOTIFY command defines the particular delivery status notification (DSN) messages that the destination SMTP server must provide to the sender. DSN messages are defined in RFC 1891. In this case, you are requesting a DSN message for successful or failed message delivery.<br /><br />Type DATA and then press ENTER. You will receive a response that resembles the following:<br /><br /> Copy Code <br />354 Start mail input; end with <CLRF>.<CLRF> <br /><br />Type Subject: Test from Contoso and then press ENTER.<br /><br />Press ENTER. RFC 2822 requires a blank line between the Subject: header field and the message body.<br /><br />Type This is a test message and then press ENTER.<br /><br />Press ENTER, type a period ( . ) and then press ENTER. You will receive a response that resembles the following:<br /><br /> Copy Code <br />250 2.6.0 <GUID> Queued mail for delivery <br /><br />To disconnect from the destination SMTP server, type QUIT and then press ENTER. You will receive a response that resembles the following:<br /><br /> Copy Code <br />221 2.0.0 Service closing transmission channel <br /><br />To close the Telnet session, type quit and then press ENTER.<br /><br /> Interpreting the Results of a Telnet Session with an SMTP Server <br />This section provides details about the responses that may be provided to the commands that you entered in the previous example.<br /><br />Note: <br />The 3-digit SMTP response codes that are defined in RFC 2821 are the same for all SMTP messaging servers. The text descriptions may differ slightly for some SMTP messaging servers. In this example, the destination computer is running Exchange Server 2007. <br /><br />Open mail1.fabrikam.com 25<br />Successful Response 220 mail1.fabrikam.com Microsoft ESMTP MAIL Service ready at <day-date-time><br /><br />Failure Response Connecting to mail1.fabrikam.com...Could not open connection to the host, on port 25: Connect failed<br /><br />Possible Reasons for Failure <br /><br />The destination SMTP service is unavailable.<br /><br />There are restrictions on the destination firewall.<br /><br />There are restrictions on the source firewall.<br /><br />An incorrect FQDN or IP address for the destination SMTP server was specified.<br /><br />An incorrect port number was specified.<br /><br />EHLO contoso.com<br />Successful Response 250 mail1.fabrikam.com Hello [<sourceIPaddress>]<br /><br />Failure Response 501 5.5.4 Invalid domain name<br /><br />Possible Reasons for Failure There are invalid characters in the domain name. Alternatively, there are connection restrictions on the destination SMTP server.<br /><br />Note: <br />EHLO is the Extended Simple Message Transfer Protocol (ESMTP) verb that is defined in RFC 2821. ESMTP servers can advertise their capabilities during the initial connection. These capabilities include their maximum accepted message size and their supported authentication methods. HELO is the older SMTP verb that is defined in RFC 821. Most SMTP messaging servers support ESMTP and EHLO. <br /><br />MAIL FROM:chris@contoso.com<br />Successful Response 250 2.1.0 Sender OK<br /><br />Failure Response 550 5.1.7 Invalid address<br /><br />Possible Reasons for Failure There is a syntax error in the sender's e-mail address.<br /><br />Failure Response 530 5.7.1 Client was not authenticated<br /><br />Possible Reasons for Failure The destination server does not accept anonymous message submissions. You receive this error if you try to use Telnet to submit a message directly to a Hub Transport server.<br /><br />RCPT TO:kate@fabrikam.com NOTIFY=success,failure<br />Successful Response 250 2.1.5 Recipient OK<br /><br />Failure Response 550 5.1.1 User unknown<br /><br />Possible Reasons for Failure The specified recipient does exist in the organization.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-8918355269648493634?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-47282806299273633132008-09-24T19:58:00.001-07:002008-09-24T19:58:45.926-07:00Symptoms<br /><br />Need to change SMTP server after install.<br /><br />Cause<br /><br />Content Server Installation Guide 5.3 SP1 page 43 has the following details on SMTP Server setting:<br />-----------------------------------<br />SMTP server on Windows<br /> <br />On Windows hosts, Content Server must be able to connect to an SMTP mail server. The<br />SMTP server can be an SMTP server located on your network or it can be the SMTP<br />server provided with Windows 2000. During the installation or upgrade procedure, you<br />must provide the name or IP address of the computer hosting the SMTP server.<br /> <br />If a valid SMTP server host name is not available during installation, supply an invalid<br />host name and the installation will finish. Do not leave the field blank. After installation,<br />add a valid SMTP server host name to the smtp_server attribute of the server config<br />object. Reinitialize the server after you update the server config object.<br />-----------------------------------<br /><br /> <br /><br />Resolution<br /><br />You can change smtp_server attribute in one of the following ways: <br /> <br />1. DA<br />Navigate to DA > Administration > Configuration > Server<br /> Click "i" icon<br /> Change the SMTP Server<br /> Click OK<br />Restart docbase<br /> <br /><br />2. API<br />API> retrieve,c,dm_server_config<br />API> set,c,l,smtp_server<br />SET> <new smtp server><br />API>save,c,l<br />Then restart docbase<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4728280629927363313?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-76131356006944832772008-09-24T14:33:00.000-07:002008-09-24T14:39:27.685-07:00Symptoms<br /><br />PDFAqua Installer fails on Windows 2003 R2, with Error Resource file not found. C...\PDFaquaDocbaseInstaller.int<br /><br />Resolution<br /><br />Right Click on My Computer- Properties<br /><br />Click Advanced Tab<br /><br />On Performance Section Click Settings Button<br /><br />Select Data Execution Prevention TAB.<br /><br />Select the Radio Button<br /><br /> Turn on DEP for essential windows programs & services only<br /><br />Click apply to close of My computer Properties<br /><br />- Restart the computer.<br /><br />- Run the PDFaqua installer.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7613135600694483277?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-85910098867109654022008-09-23T12:00:00.000-07:002008-09-23T12:01:12.476-07:00The following error is returned when I log onto DA. A popup windows open: <br /><br /><br />java.lang.NoClassDefFoundError: com/documentum/admin/commands/DaDocbaseMapStatistics <br /><br />at com.documentum.webcomponent.admin.favorites.AdministrationFavorites.setDoc baseMap(Unknown Source) <br /><br /><br />Check the classpath environment variable. <br /><br /><br />Make sure that you add the following path: <br /><br /><br />C:\Program Files\Documentum\Shared\admin.jar;<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-8591009886710965402?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-71910818098343031752008-09-22T15:37:00.000-07:002008-09-22T15:39:17.478-07:00Before starting this process, go into the Desktop Client and ensure there are no documents of the custom type to be deleted. If there are documents of this custom type then you cannot delete the type. <br /><br />- Start Documentum Developer Studio (DDS) <br /><br />- Open and check out the DocApp <br /><br />- Delete the object type <br /><br />- Check in the DocApp <br /><br />- Close DDS <br /><br />Then, <br />- Start the Documentum Administrator (DA) <br />- Go to Types <br />- Drill down to get to the object type deleted in DDS <br />- Edit the object type <br />- Scroll to the bottom, there will be a DROP option <br />- Select DROP <br />- Close DA <br />- Kill the Desktop Client processes using the Task Manager (Processes Tab), ending the following processes: <br /><br />dcathmgr.exe <br />dcevtsrv.exe <br />explorer.exe <br /><br />Then go File > New Task (Run..) and enter: explorer <br /><br />- Start up the Desktop Client again and ensure that the object type isn't available for use when creating a new document <br /><br />- Open DDS and add the object type again.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7191081809834303175?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-12401607828457569122008-09-22T14:16:00.001-07:002008-09-22T14:16:37.934-07:00You can delete a workflow instance by using the destroy method. However, you can only destroy a workflow instance that is in the dormant, finished, or terminated state. The steps are as follows: <br /><br />1) Halt the workflow instance. To halt a running workflow use the Halt method: <br />dmAPIexec ("halt, <session>, <workflow_ID>") This sets the r_runtime_state attribute to halted. <br /><br />2) Abort the workflow instance. To abort the workflow use the Abort method: <br />dmAPIexec ("abort, <session>, <workflow_ID>"). This sets the r_runtime_state attribute to terminated. <br /><br />3) Destroy the workflow instance. To destroy the workflow use the Destroy method: <br />dmAPIexec ("destroy ,<session> ,<workflow_ID>"). <br /><br />Destroying a workflow instance removes its packages and workitems permanently. <br />When a workflow is aborted, notification will be sent to supervisor, and the inbox task will disappear from the performer's inbox. <br /><br />Note: This does not remove the Workflow Template and the corresponding workflow activities.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1240160782845756912?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-90261109916255321422008-09-19T15:45:00.001-07:002008-09-19T15:45:59.046-07:00Why is the DBWarning job missing from the toolset for 3.1.7 and SQL7.0? <br /> <br />SOLUTION <br /><br />The DBWarning job has been removed from 3.1.7 for SQL 7.0. This release performs the operations automaticaly and handles the conditions that the DBWarning job used to report, therefore, it is no longer required for SQL 7.0 and was removed.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-9026110991625532142?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-11674613296903990842008-09-10T11:02:00.001-07:002008-09-10T11:02:57.201-07:00promote a document manually from Request to In Progress state.<br />This is the message i get.<br /><br />Document class prohibits manual promotion in this state<br /><br />Solution:<br />Change the lifecycle extensions to enable manual promotion.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1167461329690399084?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-15277391879745707792008-09-10T10:59:00.000-07:002008-09-10T11:01:57.874-07:00ID: esg12595 <br />SOLUTION<br /> <br />If a procedure object has been deleted from a lifecycle you may encounter the error. <br /><br />Unable to open the actions for this state: <br /><br />DfException@71a:: THREAD: main; MSG: [DM_API_E_EXIST]error: "Document/object specified by 0800a75a80000d48 does not exist." <br /><br />[DM_SYSOBJECT_E_CANT_FETCH_INVALID_ID]error: "Cannot fetch a sysobject - Invalid object ID 0800a75a80000d48"; ERRORCODE: 100; NEXT: null <br /><br />The way to solve this problem is as follows: <br /><br />1. Remove the reference to the missing procedure. <br />- Uninstall the lifecycle (Example: WebPublisher will not function in this state so they have to inform their users that WebPublisher will be unavailable until the problem is fixed.) <br />- Dump the dm_policy object in IAPI <br />- Locate the offending id in the action_object_id repeating attribute <br />- Set the value to nullid (0000000000000000) at that index. <br />- Save the lifecycle <br /><br />2. Recreate the actions for the state (Assuming they know what actions they want in the state) <br />- Open the fixed dm_policy object in the Lifecycle Editor of DDS. <br />- Open the state and add the actions <br /><br />In the initial case for this SN while in DDS the default WebPublisher Engineering Lifecycle produced the error above. Customer deleted procedure objects. <br /><br />This same process should apply to other Lifecycle applications. <br /><br />Other complaints and/or error messages may include: <br /><br />- I cannot view or edit any Actions in a lifecycle. <br />- I have created a new lifecycle from scratch and the same problem and error message appear. <br />- DfException@5aa:: THREAD: main; MSG: [DM_POLICY_E_BAD_ACTION]error: "The policy identified by 4600a75a80000d46 has an invalid action object id 0800a7580000d47 specified for start Start."; ERRORCODE : 100; NEXT: null<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1527739187974570779?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-86108897885067728362008-09-10T10:58:00.000-07:002008-09-10T10:59:39.121-07:00How do I configure DTS to work with DCM docbases so that controlled documents can have renditions created on demand ? <br /><br />Solution:<br />CTS server does not work unless the classpath for the DTS service <br /><br />is updated to include dcm.jar and dcmSupport.jar . <br /><br />In addition the Business Objects that DCM uses and any additional objects the customers wants to be use must be added to the dbor.properties file on the CTS server where DTS and or ADTS is running. This is described in the DCM 5.3 sp1 release notes. For example the following objects at minumum must be added. <br /><br />dcm_extended_sysobject=type,com.documentum.dcm.type.DcmExtendedSysobject,5.0 <br /><br />See the Doc Control Manager 5.3 sp1 release notes and bug # 107480.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-8610889788506772836?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-28974349019729662872008-09-10T10:56:00.000-07:002008-09-10T10:58:07.344-07:00select * from dm_queue where name='dm_autorender_win31' - if it retruns something .. lets clean this up <br /><br />delete dm_queue objects where name='dm_autorender_win31' <br /><br />Restart CTS Service .. Queue the item again .. check there must be only 1 item in the queue ..<br /><br />Note:<br />We found that controlled documents were getting stuck in the queue which would lead to uncontrolled documents not being rendered. After clearing the queue, we sent an uncontrolled document for transformation and it was rendered successfully. We then tried sending a controlled document and found that it would not render.<br /><br />Verified that steps were followed to allow for controlled documents to be rendered:<br />1. dcm.jar and dcmSupport.jar to C:\Program Files\Documentum\Shared on were added to DTS server (also added dcmQueue.jar and dcmQueueImpl.jar)<br />2. the classpath entry was added<br />3. Verified that the dbor.properties file had the correct entries.<br /><br />We are still unable to render controlled documents. I found this thread, http://forums.emc.com/nsepn/webapps/xpsgggfs31465mnldcpq14543562/forums/thread.jspa?threadID=47974, and attempted to correct the syntax of the classpath entry. After following the instructions we were still unable to render controlled documents.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2897434901972966287?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-70602092908405624612008-09-10T10:54:00.000-07:002008-09-10T10:55:52.861-07:00The queue item with ID (1b018a8c8000b3aa) and message 'rendition_req_ps_pdf' was signed off as it reached its expiry age.".<br /><br />There is one xml file CTSServerService.xml or mediaserverservice.xml with a configuration of maxQueueItemAge in 1m (one minute). <br /><br />Change this to 5m and check again.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7060209290840562461?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-68054544116367689212008-09-10T10:53:00.000-07:002009-03-09T11:47:21.281-07:00msw6template and msw6 files not rendered to PDF <br />ID: esg83952 <br />SOLUTION <br />Symptoms<br /><br />If you are trying to render the following formats to PDF you may not be able to get the PDFs: <br /><br />- msw Word 4.x, 5.x (DOS)<br />- msw3 Word 3.0-4.x (MacOS, Windows) <br />- msw6 Word 6.0 (MacOS), 6.0-7.0 (Windows) <br />- msw6template Word 6.x template (MacOS, Windows) <br />- mswm Word 4.x, 5.x (MacOS) <br />- mswm1 Word 1.x (MacOS) <br />- msww Word 1.x, 2.x (Windows) <br /><br />The rendition will fail and the CTS_log.txt will show the following messages:<br /><br />INFO [ Thread-31] CTSPluginHandlerImpl - The profile legacy_to_pdf does not support msw6 to pdf transformation <br />INFO [ Thread-31] CTSLegacyQueueProcessor - Unable to execute the profile of the queue item (1b010ca380165582)<br /> <br />Cause<br /><br />These formats are not supported in the DTS transformation profiles.<br /><br />Resolution<br /><br />You must add these formats into the profiles by performing the following steps:<br /><br />1) In the repository, navigate to: /System/Media Server/System Profiles.<br /><br />2) Select "Show all objects and versions" from the dropdown list on the top right. <br />3) Check out legacy_to_pdf & document_to_pdf_dts (assuming you are using DTS 5.3 SP4).<br />4) Open the checked out files on your local machine in an editor.<br />5) Add the following to both files, within the formats section:<br /> Format source="msw" target="pdf"<br /> where source is the format you must render.<br />6) Save and close the files.<br />7) Check in both profiles.<br />8) On the DTS server, navigate to %CTS%\config (For example: C:\Program Files\Documentum\CTS\config).<br />9) Open the "FormatMapper.xml" file in an editor.<br />10) Add the following, within the <CTSCustomConfig> section:<br /> FormatMapper CTSFormat="doc" DocumentumFormat="msw"/<br /> where DocumentumFormat is the format you must render.<br />11) Save and close the file.<br />12) Restart the CTS service(s).<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6805454411636768921?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-16316693366173628122008-09-10T10:51:00.000-07:002008-09-10T10:53:06.587-07:00What should you check if the customer cannot transform document in DCM? <br />ID: esg44700 <br />SOLUTION <br /> <br />Symptoms<br /><br />What should you check if the customer cannot transform document in DCM" <br /> <br />Cause<br /><br />When trying to create a PDF rendition of a document in DCM, you may see an error like the following in the cts log: <br /><br />"com.documentum.cts.exceptions.internal.CTSServerTaskException: com/documentum/dcm/aspect/IDcmControlledDocAspect <br /><br />Cause Exception was: <br /><br />java.lang.NoClassDefFoundError: com/documentum/dcm/aspect/IDcmControlledDocAspect" <br /> <br />Resolution<br /><br />Make sure you have gone through all the steps for setting up CTS, DTS, ADTS to work with DCM. <br /><br />First, you need to copy the dcm.jar and dcmsupport.jar file from the DCM machine to the Media Server machine and put them in the following path: <br /><br />\program files\documentum\shared <br /><br />You should add the path and filename to the CLASSPATH for both files. <br /><br />Then, you need to modify the registry to point to the path for those files. <br /><br />In HKEY_LOCAL_MACHINE\system\currentcontrolset\services\documentumcts\parameters you need to modify the app parameters entry and add the full path to the dcm.jar and dcmsupport.jar files.<br /><br />For example: <br /><br />\program files\documentum\shared\dcm.jar;\program files\documentum\shared\dcmsupport.jar <br /> <br />Then you need to edit the startcts.bat file. Edit the file in a text editor. Modify the class.path entry and again add the full path to the dcm.jar and dcmsupport.jar files.<br /><br />For example:<br /><br />\program files\documentum\shared\dcm.jar;\program files\documentum\shared\dcmsupport.jar<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1631669336617362812?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-79943939459535828862008-09-10T10:49:00.000-07:002008-09-10T10:51:41.664-07:00com.documentum.cts.exceptions.internal.CTSProfileServiceException: [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"<br />Cause Exception was: Exception during updating profile cache document_to_pdf_dts<br /> <br />ADTS 6.0 6.0SP1 [DM_VEL_INSTANTIATION_ERROR]error: Cannot instantiate Java class <br /> <br />ID: esg93948 <br />Product(s): Advanced Document Transformation Services <br />Related Bugs: 154355, 150077 <br />SOLUTION <br /><br />Symptoms<br /><br />ADTS 6.0 6.0SP1 [DM_VEL_INSTANTIATION_ERROR]error: Cannot instantiate Java class. ADTS 6SP1 does not rendition documents.<br /><br />The following error is thrown in the CTS log file: <br />com.documentum.cts.exceptions.internal.CTSProfileServiceException: [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"<br />Cause Exception was: Exception during updating profile cache transformEmlToPDF<br />DfException:: THREAD: Thread-10; MSG: [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"; ERRORCODE: 1902; NEXT: null<br /> at com.documentum.services.dam.impl.transform.MediaProfile.initParameters(MediaProfile.java:417)<br /> at com.documentum.services.dam.impl.transform.MediaProfile.getProfileNameAttr(MediaProfile.java:149)<br /> at com.documentum.services.cts.impl.profile.CTSProfile___PROXY.getProfileNameAttr(CTSProfile___PROXY.java)<br /> at com.documentum.cts.impl.services.ctsprofile.CTSProfileManagerImpl.createProfile(CTSProfileManagerImpl.java:1208)<br /> at com.documentum.cts.impl.services.ctsprofile.CTSProfileManagerImpl.addInCache(CTSProfileManagerImpl.java:1060)<br /><br />Caused by: DfServiceInstantiationException:: THREAD: Thread-10; MSG: [DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"; ERRORCODE: 1902; NEXT: null<br /> at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.loadModuleClass(ModuleManager.java:211)<br /> at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.getModuleClass(ModuleManager.java:165)<br /> at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.newModule(ModuleManager.java:120)<br /> at com.documentum.fc.client.impl.bof.classmgmt.ModuleManager.newService(ModuleManager.java:89)<br /> at com.documentum.fc.client.DfClient$ClientImpl.newService(DfClient.java:412)<br /> at com.documentum.services.dam.impl.transform.MediaProfile.initParameters(MediaProfile.java:340)<br /><br />Cause<br /><br />ADTS 6.0/6.0SP1 is installed against the 5.3/5.3SPx repository without any D6 repository. <br /><br />Resolution<br /><br />Customers may tend to assume that D6 ADTS is fully backward compatible with the 5.3/5.3SPx repository and they may be misled due to a lack of accurate and explicit documentation. ADTS 6/6SP1 requires a D6 global registry to successfully get ADTS up and running. This in turn requires installing the D6 Content Server. Even if you follow the instructions in Bug 150077 and deploy Transformation and Rich_Media_Services docapps manually, ADTS will not work unless you have a D6 Global registry.<br /><br />Per Support solution esg92090, this issue could be worked around by manually deploying the ctsTransformImpl.jar file locally in the BOF registry with the CTS host. Although esg92090 is proven to work, this method has not been tested by the CTS QA Team and is therefore not officially supported by CTS/ADTS Engineering.<br /><br />A Documentation bug# 154355 is logged to include these details in the ADTS6/6SP1 Release Notes or Installation Guide. <br /><br />Note: If you already have D6 installed with GR, the steps to resolve the same error are provided in support note esg98200. <br /> <br />SEE THESE SOLUTIONS ALSO:<br /> <br />esg92090 CTS 6.0 users need to have a D6 Global Repository <br />esg98200 DM_VEL_INSTANTIATION_ERROR --CTS docapps Tranformation and Rich media doesn't install properly<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7994393945953582886?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-32059269747382147172008-09-10T10:48:00.000-07:002008-09-10T10:49:03.159-07:00Cannot create/import controlled document with 10022 error. <br />ID: esg76557 <br />SOLUTION <br /><br />ERROR: Failed when creating new controlled document/object. 10022, This is a bug fix in DCM 5.3 SP2 <br />- Trouble shooting steps to resolve 10022, error message <br />1. Check if custom types to the Acceptable types in the Default Lifecycle, using DAB. <br />2. Check if data dictionary population is set to true <br /><data_dictionary_population> <br /><enable>ture</enable> <br />3. Check if the dcm.jar, dcmSupport.jar are set in the Classpath <br />4. Check if the Superuser can check in Controlled Document, if so, refer to support note SN: 44709 . This is a bug fix in DCM 5.3 SP2 <br />5. Check if this is migration of configuration, if so check permission sets have been defaulted to what is OOTB, and not as what designed in DCM 5.3 SP1. Change the permission set to point to the custom permission sets <br />6. you may be hitting this Bug# 108750 <br /><br />----<br />Issue Number: 152099 <br />Severity: 1 - Critical <br />Status: Fixed <br />Problem Summary: Author cannot create controlled document unless unprotect the group_name dm_superusers_dynamic. For DCM 5.3 sp4 and D6 content server. <br />Planned Fix Release: <br />Patch Available/Release: <br />Duplicate of: 153105 <br /><br />---<br />The following errors can occur when creating or importing new controlled documents in DCM without using the repository installation owner account: <br /><br />ERROR: Failed when creating new controlled document/object. 10022 <br /><br />Or <br /><br />Checkin Controlled Document fails. <br /><br />More details from error messages or from JMS logs: <br />.. <br /># [ 2609200048 ] Fri Nov 4 12:11:57 2005 280842 ( 0.000 sec) ( 262 rpc) API> get,s4,sessionconfig,r_user_name <br /><br /># [ 2609200048 ] Fri Nov 4 12:11:57 2005 280884 ( 0.000 sec) ( 262 rpc) Res: 'dmadmin' <br /><br /># [ 2609200048 ] Fri Nov 4 12:11:57 2005 281449 ( 0.000 sec) ( 262 rpc) API> attach,s3,090188b380005fcf,460188b380000983,,dcm52 <br /><br /># [ 2609200048 ] Fri Nov 4 12:11:57 2005 281698 ( 0.000 sec) ( 262 rpc) Server RPC: SysObjAttach (090188b380005fcf) <br /><br /># [ 2609200048 ] Fri Nov 4 12:11:59 2005 710201 ( 2.429 sec) ( 263 rpc) Res: ' ' <br /><br /># [ 2609200048 ] Fri Nov 4 12:11:59 2005 710409 ( 0.000 sec) ( 263 rpc) API> getmessage,s3,3 <br /><br /># [ 2609200048 ] Fri Nov 4 12:11:59 2005 710473 ( 0.000 sec) ( 263 rpc) Server RPC: GET_ERRORS (0000000000000000) <br /><br /># [ 2609200048 ] Fri Nov 4 12:11:59 2005 711840 ( 0.001 sec) ( 264 rpc) Server RPC: MultiNext (29) <br /><br /># [ 2609200048 ] Fri Nov 4 12:11:59 2005 713085 ( 0.003 sec) ( 265 rpc) Res: '[DM_POLICY_E_ERROR_1600]error: "The User Actions Proc failed. Details:Error saving the sysobject: [DM_SYSOBJECT_E_LINK_PERMIT2]error: "Linking or unlinking to the folder '/Controlled Docs/In Progress' failed on sysobject '090188b380005fcf'. WRITE permit is required on the folder, when using folder security." <br /><br />This error occurs when the repository installation owner does not have WRITE permission in the /Controlled Docs/In Progress folder. <br /><br />To fix this problem, please add repository installation owner(aka dmadmin) into administrator role.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3205926974738214717?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-60949410658922546112008-09-10T10:46:00.001-07:002008-09-10T10:48:13.202-07:00Controlled Doc is greyed : <br /><br />Check if the user has co-ordinator access and should be in superuser_dynamic<br /><br />check if there are any doc class in this envr, create one as it requires doc class for a cntrl document.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6094941065892254611?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-60000720611773603872008-09-10T10:44:00.003-07:002008-09-10T10:44:45.995-07:00CTS service crash <br /> <br />ID: esg80644 <br />Product(s): Document Transformation Services, Media Transformation Services <br />Related Bugs: 125676 <br />SOLUTION <br /><br />Symptoms<br /><br />CTS service crashes if machine has several JRE installed by several DCTM products.<br /><br />In the std.log under CTS\lib you see this error:<br /><br />-Djava.class.path=D:\PROGRA~1\DOCUME~1\CTS\lib\cts.jar;D:\PROGRA~1\DOCUME~1\dctm.jar;D:\DOCUME~1\config;D:\PROGRA~1\DOCUME~1\CTS\lib;D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\lib\jce.jar;D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\lib\jce.jar;D:\PROGRA~1\DOCUME~1\java\1.4.2_11\jre\lib\ext\sunjce_provider.jar<br />Mon Nov 13 14:49:49 2006 Exception from the java application<br />java.lang.ExceptionInInitializerError<br /> at javax.crypto.Cipher.a(DashoA12275)<br /> at javax.crypto.Cipher.getInstance(DashoA12275)<br /> at com.documentum.fc.common.impl.PBEUtils.decrypt(PBEUtils.java:97)<br /><br />Cause<br /><br />CTS service crashes if machine has several JRE installed by several DCTM products.<br /><br />Resolution<br /><br />The workaround is to rollback to the 1.4.2.04 JRE by changing all the paths in the AppParamaters registry key for the CTS service as located HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DocumentumCTS\Parameters<br /><br />You should still have the 1.4.2.04 JRE under C:\Program Files\Documentum\java\1.4.2_04. <br /><br />NOTE: Fixed in 5.3 SP4<br /> <br />=========================================================<br /><br />why CTS.exe crashes ? <br /> <br />The symptoms are that cts.exe crashes with JVM errors. But when you start from startCTS.bat it works. This is very similar to the issue that we have when running CTS on the same machine as the Content Server. <br /><br />We have seen this issue mostly when WDK application are running with CTS looks like a issue with sharing JVM?s <br /><br />Here is the resolution. <br /><br />STEP1: Stop CTS and all dependent services. <br /><br />STEP2: Open registry by running regedit. <br /><br />STEP3: Navigate to ?HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DocumentumCTS\Parameters? <br /><br />STEP4: Open AppParameters by Double-clicking. <br /><br />STEP5: Copy and back up the current Value. <br /><br />STEP6: Modify the values to include the following <br /><br /><br />-Djava.ext.dirs=C:\PROGRA~1\DOCUME~1\java\1.4.2_04\jre\lib <br /><br /><br />and make sure following jars are at the end of -Djava.class.path <br /><br />C:\PROGRA~1\DOCUME~1\java\1.4.2_04\jre\lib\jce.jar;C:\PROGRA~1\DOCUME~1\java\1.4.2_04\jre\lib\ext\sunjce_provider.jar <br /><br /><br />Here is a sample from working environment. <br /><br /><br />-Xbootclasspath <br /><br />?. <br /><br />-DMAX_WAIT_INTERVALS=5 <br /><br />?Djava.ext.dirs=C:\PROGRA~1\DOCUME~1\java\1.4.2_04\jre\lib <br /><br />-Djava.class.path=C:\PROGRA~1\DOCUME~1\CTS\lib\cts.jar;C:\PROGRA~1\DOCUME~1\dctm.jar;C:\DOCUME~2\config;C:\PROGRA~1\DOCUME~1\CTS\lib;C:\PROGRA~1\DOCUME~1\java\1.4.2_04\jre\lib\jce.jar;C:\PROGRA~1\DOCUME~1\java\1.4.2_04\jre\lib\ext\sunjce_provider.jar <br /><br />??. <br /><br /><br />STEP7: Save the value. <br /><br />STEP8 Start the CTS service.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6000072061177360387?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-25181068576556883192008-09-10T10:38:00.000-07:002008-09-10T10:42:45.580-07:00How can I change the log level in CTS? <br />ID: esg44235 <br />Product(s): Document Transformation Services, Media Transformation Services <br />SOLUTION <br />By default CTS is set to INFO Level in order to improve the performance. <br />Please refer to support note 25327 for different levels of logging. <br />Steps to change the log level: <br />1. Stop all of the CTS services. <br />2. Go to log4j.properties file under following folder [DFC HOME]\config which is generally C:\documentum\config <br />3. To get debug information for CTS framework, update the following CTS appenders to DEBUG from INFO: <br />FROM: <br /><br />log4j.category.com.documentum.cts.services=INFO, CTSServicesAppender<br /><br />log4j.category.com.documentum.impl=INFO, CTSServicesAppender <br /><br />log4j.category.com.documentum.cts.util=INFO, CTSServicesAppender<br /><br />log4j.category.com.documentum.cts.util.CTSInstanceInfoUtils=INFO, CTSInstanceInfoAppender<br /><br />TO: <br /><br />log4j.category.com.documentum.cts.services=DEBUG, CTSServicesAppender<br /><br />log4j.category.com.documentum.impl= DEBUG, CTSServicesAppender <br />log4j.category.com.documentum.cts.util=DEBUG, CTSServicesAppender<br />log4j.category.com.documentum.cts.util.CTSInstanceInfoUtils=DEBUG, CTSInstanceInfoAppender<br /><br />4. To troubleshoot Plug-in specific issues you will need to add DEBUG to the plugin appender that you would like to trace. Each Plug-In has their own appender so you will need to set this for each one that you are troubleshooting. <br />Here are some example plug-ins and their coresponding appenders.<br /><br />ALTERCAST (MTS)<br /><br />log4j.category.com.documentum.mp.altercast= DEBUG, AltercastAppender <br /><br />IMAGE1<br /><br />log4j.category.com.documentum.cts.plugin.irw=DEBUG, IMAGE1Appender<br /><br />PDF (DTS5.3 SP4 and abobe)<br /><br />log4j.category.com.documentum.cts.plugin.advancedpdf=DEBUG, PDFAPPENDER<br /><br />ADVANCED PDF (RPTS)<br /><br />log4j.category.com.documentum.cts.plugin.advancedpdf=DEBUG, AdvancedPDFAppender<br /><br />ACROBAT (DTS 5.3 -5.3 SP2)<br /><br />log4j.category.com.documentum.cts.plugin.acrobat=INFO, ACROBATAppender<br /><br />WORD (DTS 5.3)<br /><br />log4j.category.com.documentum.cts.plugin.word=DEBUG, WORDAppender<br /><br />PDF Generator (DTS 5.3 SP3 and DTS Legacy)<br /><br />log4j.category.com.documentum.cts.plugin.pdfgen=DEBUG, PDFGenAppender<br /><br />AAES (ADTS)<br /><br />log4j.category.com.documentum.cts.plugin.aaes=DEBUG, AAESAppender<br /><br />5. By switching on separate logging in log4j.properties file by setting "separatelogging" to true, CTS will create a separate log file per repository. This is only needed for a multiple repository configuration.<br /><br />com.documentum.separatelogging.enabled=true.<br /><br />6. Start the CTS service.<br /><br />The logs will now have a higher degree of verbosity which will assist in troubleshooting.<br /><br />7. Logs will be created in two places.<br /><br />a. <CTS_HOME>\logs - This is the default location for logs. If seperate logging is enabled, only non- repository specific information will go here. Like plug-ins loading.<br /><br />b. <CTS home>\docbases\<docbasename>\config\logs - If seperate logging is enabled, docbase specific logging will be placed here.<br /><br />NOTE: Log4j is a open source framework for controlling logging. It is a mechansim for controlling verbosity, logging file creation, and log output format. Please refer to the following support note for more information:<br /><br />http://solutions.emc.com/nsepn/webapps/stqv768481dmts46655278/emcsolutionview.asp"id=esg77976<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2518106857655688319?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-59394605446024378882008-09-10T10:35:00.000-07:002008-09-10T10:38:32.686-07:00Tracing can be enabled using the dmcl32.dll through the dmcl.ini file by including some trace statements in the DMAPI_CONFIGURATION section. <br /><br />There are two keywords used: trace_file and trace_level. <br /><br />The trace_file keyword can be specified as either a file name or a directory name. If you specify a directory name, then a trace file will be generated automatically. The name will appear like dmcl_trace_2658878. The seven digits will be generated as unique numbers. These trace files will be created each time a client application is used that initializes the dmcl32.dll. <br /><br />The trace_level keyword sets the level of trace information put into the trace file. Trace levels are: <br /><br />0 = Informational messages (Note: no trace will be created on Desktop Client if set to "0") <br /><br />1 = Trace messages <br /><br />2 = Warning messages <br /><br />3 = Error messages <br /><br />4 = Fatal error messages <br /><br />10 = Timing information <br /><br />11 = Load operation information <br /><br /><br />For more information on the Trace API Server method, please refer to the Documentum Server Reference Manual. <br /><br />Below is an example of a dmcl.ini file used by a Windows 95 client running WorkSpace 3.1. <br /><br />#Default DMCL.INI. Refer to DMCLFULL.INI for other options <br /><br /># Assuming No Network File System <br /><br /># Assuming No Compression for Content Tunneling <br /><br />[DOCBROKER_PRIMARY] <br /><br />host = barracuda <br />port = 1489<br />#host = shark <br /><br />[DMAPI_CONFIGURATION] <br /><br />cache_query = F <br />trace_file = c:\tracefiles <br />trace_level = 3 <br /><br />Example:<br /><br />[DOCBROKER_PRIMARY]<br /><br />host =10.47.101.119<br />port =1489<br /><br />[DOCBROKER_BACKUP]<br /><br />host =10.47.101.120<br />port =1489<br /><br />[DMAPI_CONFIGURATION]<br />cache_queries = T<br />token_storage_enabled=F<br />token_storage_path=D:\Documentum\apptoken<br />secure_connect_default=try_native_first<br />client_codepage=UTF-8<br />client_os_codepage=UTF-8<br />max_session_count=1000<br />connect_pooling_enabled=T<br />cache_query =F<br />trace_file=c:\trace.log<br />trace_level=10<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-5939460544602437888?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-40684056964009438252008-09-10T10:33:00.000-07:002008-09-10T10:34:31.069-07:001) Create a table in the database<br />2) Register using DA<br /><br />For E.g:<br /><br />DQL> REGISTER TABLE dm_dbo.MLTC_BUSINESS_DOC_TYPE_WEB(BDT_ID INT, BDT_NAME CHAR(255), BDT_DESCRIPTION CHAR(255), CLASS_NAME CHAR(64), HIGHEST_LEVEL_FOLDER CHAR(255), LOWEST_LEVEL_FOLDER CHAR(255)); <br /> <br />new_object_ID <br />============= <br /> <br />190049e0803f9 <br />(1 rows affected)<br /> <br />Update reg table values.<br /> <br />DQL> update dm_registered objects set group_permit= 15 where r_object_id = '190049e0803f96d0';<br /> <br />objects_updated <br />=============== <br /> <br />1 <br />(1 rows affected)<br />DQL> update dm_registered objects set world_permit= 7 where r_object_id = '190049e0803f96d0';<br /> <br />objects_updated <br />=============== <br /> <br />1 <br />(1 rows affected)<br />DQL> update dm_registered objects set owner_table_permit= 7 where r_object_id = '190049e0803f96d0';<br /> <br />objects_updated <br />=============== <br /><br />use this DQL to grant proper permission to your table<br />update dm_registered object<br />set owner_table_permit = 15,<br />set group_table_permit = 15,<br />set world_table_permit = 15<br />set owner_permit =7, <br />set group_permit =5,<br />set world_permit=3<br />where object_name = 'AddressBook'<br />go<br /><br />This should give proper permission to your registered table. if you want you can change the table_permit from 15 to whatever u like.<br /><br />To get the install owner name. use this DQL, sometimes its handy.<br /><br />select user_name from dm_user where user_name = 'dm_dbo'<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4068405696400943825?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-35154589404523289312008-09-10T10:28:00.000-07:002008-09-10T10:31:57.759-07:00Issue:<br />ERROR: Failed when creating new document/object. <br />Error copying template while performing new object operation:Cannot make copy of the document 'Blank Word 97 / 2000 Document'<br /><br />Solution:<br /> check the permissions and give atleast write permissions!<br /> check the permissions in the data directory ie to the specific path<br /><br /> verify the /Templates cabinet, these templates are there and the owner(dmdmin) has delete permissions on these templates<br /><br />Error seen from DMCL trace: <br /><br />[DM_CONTENT_E_LOCK_REQUEST]error: "Error requesting file lock on filename (e:\dctm\Dmcl\00013424\testdocbase\dir.lck) in order to lock the Session Temporary Content Directory for use on the first Getfile request. Lock_wait 1. Operating System error was ( errno: 13, message: Permission denied)."; ERRORCODE: 100; NEXT: null: <br /><br />This error is cause by a permissions issue. <br /><br />The user creating the lock file does not have permission to the DMCL cache location. <br /><br />please check permission to the full path listed. <br /><br />In the error above it would be e:\dctm\Dmcl\00013424\testdocbase\ <br /><br />Your path will differ from the error listed above.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3515458940452328931?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-15238812479119072562008-09-10T10:25:00.000-07:002008-09-10T10:26:38.195-07:00Issue :<br />IN DAB, when am trying to double click.. am getting below error and unable to edit<br />Workflow Manager: There is no unicode font found on the system<br />Unicode data may not be displayed correctly<br /><br />Solution:<br />Install the universal font for Unicode <br />Arial Unicode MS font is a full Unicode font. It contains all of the characters, ideographs, and symbols defined in the Unicode 2.1 standard. It is contained on the Microsoft Office Installation Disk and is not installed by default. <br />Installing the Unicode Font In Microsoft Windows 2000, XP or Millennium Edition <br /><br />1) Quit all programs. <br /><br />2) In Control Panel, double-click the Add/Remove Programs icon. <br /><br />3) Do one of the following: <br /> a) If you installed your Microsoft Office program as part of an Office package, click Microsoft Office in the Currently installed programs box, and then click Change. <br /> b) If you installed your Office program individually, click the name of your program in the Currently installed programs box, and then click Change. <br /><br />4) In the Microsoft Office Setup dialog box, click Add or Remove Features, and then click Next. <br /><br />5) Next to Office Shared Features, click the plus sign (+). <br /><br />6) Next to International Support, click the plus sign (+). <br /><br />7) Click the icon next to Universal Font, and then select the installation option you want. <br /> <br /><br />Installing the Unicode Font In Microsoft Windows 98 or Windows NT 4.0 <br /><br />1) Quit all programs. <br /><br />2) In Control Panel, double-click the Add/Remove Programs icon. <br /><br />3) Do one of the following: <br /> a) If you installed your Microsoft Office program as part of an Office package, click Microsoft Office on the Install/Uninstall tab, and then click Add/Remove. <br /> b) If you installed your Office program individually, click the name of your program on the Install/Uninstall tab, and then click Add/Remove. <br /><br />4) In the Microsoft Office Setup dialog box, click Add or Remove Features, and then click Next. <br /><br />5) Next to Office Shared Features, click the plus sign (+). <br /><br />6) Next to International Support, click the plus sign (+). <br /><br />7) Click the icon next to Universal Font, and then select the installation option you want. <br /><br />Note: Because of its considerable size and the typographic compromises required to make such a font, Arial Unicode MS should be used only when you can't use multiple fonts tuned for different writing systems. For example, if you have multilingual data from many different writing systems in Microsoft Access, you can use Arial Unicode MS as the font to display the data tables, because Access can't accept many different fonts.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1523881247911907256?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-58822629879653459832008-08-21T23:32:00.001-07:002008-08-21T23:32:34.979-07:00Job Description<br />1. DMClean The DMClean job removes deleted and orphaned objects from the<br />Docbase.<br />2. DMFilescan The DMFileScan job removes deleted and orphaned content files from<br />the file system.<br />3. LogPurge The Log Purge job removes server and session logs from the Docbase<br />and file system.<br />4. ConsistencyChecker The Consistency Checker job runs 77 referential integrity checks on<br />the Docbase.<br />5 UpdateStats The Update Stats job updates database table statistics and repairs<br />fragmented tables<br />6. QueueMgt The QueueMgt job deletes dequeued Inbox items from the Docbase.<br />7. StateOfDocbase The State of the Docbase job produces a report of the repository<br />environment and statistics about object types.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-5882262987965345983?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-11941524028646822482008-08-21T23:30:00.000-07:002008-08-21T23:31:18.440-07:00In Webtop the DQL issued by Simple Search and the DQL issued by Advanced Search are different. For example in Simple Search, if I search for a document called "always on" and enter this as such, the simple search text box the following DQL is issued: <br /><br />SELECT ALL r_object_type,r_modify_date,r_object_id,r_lock_owner,i_vstamp,owner_name,r_version_label,i_is_reference,score,a_content_type,object_name,r_is_virtual_doc,r_link_cnt,r_content_size FROM dm_document SEARCH TOPIC ' <ACCRUE>("*always*","*on*")' <br /><br /><br />For the Advanced search, if I carry out the same search the following DQL is issued: <br /><br />SELECT ALL r_object_type,r_lock_owner,r_object_id,owner_name,i_is_reference,a_content_type,object_name,r_is_virtual_doc,r_link_cnt,lower(object_name) AS lowerobjname,r_content_size,r_version_label,r_modify_date FROM dm_document WHERE FOLDER('/Your Folder',DESCEND) AND lower(object_name) = lower('always on') ORDER BY 10 ASC,3 ASC <br /><br /><br />The differences in the two searches is as designed. Simple search matches the words searched against indexed text and properties such as, Filename, Descriptive name, Category and Author. Spaces or commas can be used to separate text / keywords and Webtop will search for all separated chunks of text using Verity queries, such as AND or OR. For more information regarding Simple Search, please refer to the "Using a Simple Search" section of the Webtop 5.2x User Guide. <br /><br />In our example, a client searching for "always on" would be considered to be searching for keywords "always" AND "on". This is a non-issue with Advanced Search as it is a less ambiguous search. <br /><br /><br />Another example: <br />If I have a document called "NEW Vacation Request Form.doc" in my home cabinet. I may carry out the following searches: <br />1) Search for "NEW Vacation Request Form.doc" --> returns the document (full object_name) <br />- SEARCH TOPIC ' ("*NEW Vacation Request Form.doc*")' <br /><br />2) Search for "NEW Vacation Request Form" --> returns the document (partial object_name) <br />- SEARCH TOPIC ' ("*NEW Vacation Request Form*")' <br /><br />3) Search for NEW Vacation Request Form --> did not return as we know <br />- SEARCH TOPIC ' <ACCRUE>("*NEW*","*Vacation*","*Request*","*Form*")' <br /><br />ACCRUE selects documents that include at least one of the search elements you specify. The more search elements that are present, the higher the score will be. e.g. <ACCRUE> (computer, laptop). As you can see, ACCRUE is used to search content not object_name. <br /><br />The workaround suggested is to enclose double quotes around the words in simple search.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1194152402864682248?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-6094039775358245402008-08-21T23:29:00.001-07:002008-08-21T23:29:43.644-07:00“Remove select Object from DocApp/Type” removes object from the docapp not from docbase, if you want to remove objects from docbase the in DAB, checkout docapp <br /> <br />Select the object, Go to Menu item Edit  Delete object(s) from Docbase.<br /> <br />Or<br /> <br />TBO objects reside in the docbase in the location "/System/Modules/TBO" with the object type "dmc_module". You can uninstall the TBO’s by destroying your custom TBO objects from docbase.<br /> <br />select r_object_id, r_object_type from dm_sysobject where folder('/System/Modules/TBO');<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-609403977535824540?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-62285137954596092322008-08-21T23:28:00.000-07:002008-08-21T23:29:07.447-07:00symptoms<br /> <br />User is getting UCF_E_SPECIFY_APPLICATION: A valid application does not exist. when try to view or edit specific file even application exist on the machine.<br />Cause<br />No Registry entries to edit and view with the specific extension.<br /> <br />Resolution<br />The Win32 Native Library used by UCF to identity and launch applications on the client relies on entries in the Windows Registry to discover file-type/application associations. The sequence for identifying which application to use for a given type is as follows:<br />• Look for entries in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts matching the type<br />• For each sub-key found, the program identifier and name are recorded (i.e. HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.asp\OpenWithProgids\aspfile)<br />• For each of the sub-keys, the program identifier is search for in HKEY_CLASSES_ROOT (i.e. HKEY_CLASSES_ROOT\aspfile)<br />• If there is a shell sub-key, then the 'shell\open\command' and 'shell\edit\command' values are used for launching the application. If only one is available, then it will be used for viewing and editing.<br />For an example of a key that works, check HKEY_CLASSES_ROOT\Excel.Sheet.8\shell\Open\command.<br />So, immediate solution user can choose viewer/editor in WDK Client Application, or to provide sub-keys in the Windows registry HKEY_CLASSES_ROOT\aspfile entry to indicate the shell/open/command and shell/edit/command values.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6228513795459609232?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-10477089828550487142008-08-21T23:24:00.000-07:002008-08-21T23:25:23.546-07:00This has nothing to do with folder security, which is a different topic altogether.<br /><br />A permission set, or ACL, on a folder, controls whether that folder is displayed in the Desktop and Intranet clients. It has nothing to do with whether a user can make changes to the documents within the folder. This is determined by the ACLs assigned to each document. Folders are visible to all users with BROWSE permission. A user with NONE cannot see a folder from their client. A folder does not protect documents inside. Users with access to those documents can still search for, find, and change those documents<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1047708982855048714?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-29511770260275372082008-08-21T23:23:00.000-07:002008-08-21T23:24:07.360-07:00Introduction<br /><br />Whether you're a developer new to the Web Development Kit (WDK) or you're a system administrator trying to be efficient in your Documentum user management, you may have wondered why there are both groups and roles. This article explores the differences between them, and provides some guidance on how to decide when to use a group or a role.<br /><br />In the Beginning, there were Groups<br /><br />Groups are a convenient way of aggregating individual users, thereby simplifying the process of managing permissions. Specifically, groups can be used in the following ways:<br /><br />In conjunction with an Access Control List (ACL) to assign object-level permissions to all members of the group<br /><br />As the owner of a document to allow all members of the group to have ownership<br /><br />As the performer of a workflow task to allow that task to be delivered to all members of the group (or optionally the first to receive it)<br /><br />The Content Server Fundamentals manual provides the following example of using groups to control permissions: you might set up a group called engr and assign version permission to the engr group in an ACL applied to all engineering documents. All members of the engr group then have version permission on engineering documents.<br /><br />Groups contain the following properties:<br /><br />Name: the name of the Docbase group<br /><br />Class: the type of group (added in Content Server 5 - more on this later)<br /><br />Email address: the address for the group. If no value is entered, the group email address defaults to the group name.<br /><br />Owner: the name of the Docbase owner who owns this group (most groups are owned by the Docbase owner, but normal users can have their own groups as well, although this feature is rarely used)<br /><br />Administrator: specifies a user or group, in addition to a superuser and the group owner, who can modify the group (this allows a manager to maintain group membership without having system administration privileges to the rest of the system)<br /><br />Alias set: the default alias set for the group (used in certain cases to resolve an Alias Set's scope)<br /><br />Group is Global: indicates that the group is displayed only in the governing Docbase of a federation<br /><br />Description: a user-friendly description of the group<br /><br />Is Private: defines whether the group is private or public. Public groups are visible to all users, while a private group is visible only to the owner of the group.<br /><br />And to make your user management even more flexible, a group can belong to another group, facilitating a hierarchical user structure within which individual users and groups can be combined in the same group.<br /><br />Along Came Roles<br /><br />The release of Content Server 5 ushered in the era of roles. A role is a special type of group. Prior to roles, there was only one type of group, now called a standard group. This type of group is used to assign object-level permissions and participation in workflows as described above.<br /><br />Version 5 added two new types of groups, a role group and a domain group:<br /><br />Role group: this type of group is assigned a particular role within a client application domain. As with standard groups, a role group may contain a set of users, other groups, or both. A role group is created by setting the group_class attribute to role and the group_name attribute to the role name.<br /><br />Domain group: this represents a particular client domain. A domain group contains a set of role groups, corresponding to the roles recognized by the client application. Note that if you create a role as a domain, it is listed in the Groups list page, not the Roles list page.<br /><br />Since a role is a specialized group, roles contain the same nine properties as groups, with restrictions on two of the properties (name and class) as discussed above.<br /><br />Summary of the Differences<br /><br />We've been focusing on the fact that roles are just a special type of group. So let's summarize by highlighting the differences:<br /><br />Groups are used for object permissions; roles are used for application or function permissions.<br /><br />Again we turn to the Content Server Fundamentals manual for an example of using roles and domains to control function permissions. Suppose you write a client application called report_generator that recognizes three roles: readers (users who read reports), writers (users who write and generate reports), and administrators (users who administer the application). To support the roles, you create three role groups, one for each role. The group_class is set to role for these groups, and the group names are the names of the roles: readers, writers, and administrators. Then, create a domain group by creating a group whose group_class is domain and whose group name is the name of the domain. In this case, the domain name is report_generator. The three role groups are the members of the report_generator domain group.<br /><br />When a user starts the report_generator application, the application is responsible for examining its associated domain group and determining the role group to which the user belongs. The application is also responsible for ensuring that the user performs only the actions allowed for members of that role group. Content Server does not enforce client application roles, since this responsibility is delegated to the application via the domain group.<br /><br />Once the roles exist in your Docbase, they can be reused across applications. Just create a new domain group and add any of the existing role groups (readers, writers, and administrators in the example above) to the new domain group.<br /><br />Roles in Web Publisher<br /><br />Web Publisher is already configured with the roles that are defined in the Web Publisher doc app:<br /><br />wcm_content_author_role<br /><br />wcm_content_manager_role<br /><br />wcm_web_developer_role<br /><br />wcm_administrator_role<br /><br />Web publisher uses these roles to determine which features are available to the user. For example, content authors are not allowed to see cabinets and folders, while content managers can. Content managers are not allowed to access administrative features, while administrators can. These out-of-the-box roles are ready to be used within any Web Publisher application, and they can be extended if needed. Plus, you can create new roles as needed.<br /><br />Roles in WebTop<br /><br />Webtop and WDK components can be configured to use any role that is defined in the associated Docbase. If no roles are configured in the Docbase, or if the Docbase is pre-5.1, Webtop defaults to using the client capability model in which four client capability levels can be set as client_capability attributes on the dm_user object in the Docbase:<br /><br />consumer<br /><br />contributor<br /><br />coordinator<br /><br />administrator<br /><br />If you create role groups in the Docbase, you can create roles named consumer, contributor, coordinator, and administrator. Your custom roles can contain these roles (or vice-versa), so that Webtop and WDK components will not need to be reconfigured for your custom roles.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2951177026027537208?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-27717308410267505462008-08-21T23:21:00.000-07:002008-08-21T23:23:12.686-07:00ID: esg5033 <br />SOLUTION <br /><br />You may get the following errors when trying to log into the Docbase even though the Docbase is up, but no client can connect to it. IAPI on the Server machine can also give the following errors: <br /><br />[DM_DOCBROKER_E_NETWORK_ERROR]error: "An error occured performing a network operation: (Unknown error code 112 (_nl_error_ = 10061)). Network specific error: (Winsock error: connection refused; server probably not running)." <br /><br />[DM_DOCBROKER_E_CONNECT_FAILED]error: "Unable to connect to DocBroker. Please check your dmcl.ini file for a correct host. Network address: (INET_ADDR: family: 2, port: 1489, host: 199.82.105.56 (199.82.105.56, c7526938))." <br /><br />[DM_DOCBROKER_E_REQUEST_FAILED_E]error: "The Docbroker request failed." <br /><br />The customer with the problem has the following environment: <br /><br />1. Docpage server is on a Solaris box. <br /><br />2. No DNS service used. <br /><br />3. The server.ini file indicates that the server projects to machine named 'ods_dms' <br /><br />4. Client connects from an NT machine and uses the server machine's IP address instead of the hostname in its dmcl.ini file: <br /><br />[DOCBROKER_PRIMARY] <br /><br />host = 199.82.105.56 (tried both specifying the IP address or hostname but both <br /><br />failed with the same errors) <br /><br />5. From the client machine, telnet and ping using the server machine's IP address 199.82.105.56 both succeed. <br /><br />Upon running 'dmqdocbroker -i' on the server machine and obtaining the docbase map, the following was output : <br /><br />Docbroker network address : INET_ADDR: 02 5d1 ac10490a ods_dms 127.0.0.1 <br /><br />where ods_dms is the host machine name. <br /><br />Checking the /etc/hosts file, the customer only has 1 entry: <br /><br />127.0.0.1 localhost <br /><br />RESOLUTION: <br /><br />1. Add a second entry to the /etc/hosts file for the actual IP address of the host machine since 127.0.0.1 is only the local loop back address. In this case the new entry looks like: <br /><br />199.82.105.56 ods_dms loghost <br /><br />The above entry should exist by default if the OS had been set up properly. But in this case, we suspect the OS had not been properly set up causing the second entry to be missing. <br /><br />2. Kill the docbase server process with Unix kill -9. Shutting down using the standard dm_shutdown_ods_dms script fails because IAPI cannot connect to the docbase at all. <br /><br />3. Run dm_stop_docbroker to shutdown the docbroker process <br /><br />4. Run dm_launch_docbroker to bring up the docbroker <br /><br />5. Run dmqdocbroker to verify that the docbroker picks up the correct entry from the /etc/hosts file. The correct output looks like: <br /><br />Docbroker network address : INET_ADDR: 02 5d1 ac10490a ods_dms 199.82.105.56 <br /><br />6. Run dm_start_ods_dms to start up the docbase. <br /><br />Now all client connections succeed, because the docbroker's docbase map contains the correct network address.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2771730841026750546?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-4445193429595612042008-08-21T23:17:00.001-07:002008-08-21T23:18:36.156-07:00ID: esg29545 <br />Related Bugs: <br />SOLUTION <br /> <br />More specifically the question is what is the impact of the following errors that still exist and how do we clean them up? <br /><br />Here are the steps to clean them up: <br /><br />NOTE: PLEASE ENSURE THAT YOU HAVE A DATABASE BACKUP WHICH YOU CAN USE TO RECOVER THE SYSTEM IN THE UNLIKELY EVENT OF A CORRUPTION <br /><br />You must log on to the database as docbase owner and run the SQL queries; <br /><br />--- QUERY---: select a.r_object_id as p1, a.i_chronicle_id as p2 from dm_sysobject_s a where a.i_chronicle_id <> '0000000000000000' and not exists (select * from dm_sysobject_s b where b.r_object_id = a.i_chronicle_id) <br /><br />WARNING CC-0023: Sysobject with r_object_id '09006e7880082141' references a non-existent i_chronicle_id '09006e788008211f' <br /><br />WARNING CC-0023: Sysobject with r_object_id '09006e788008214b' references a non-existent i_chronicle_id '09006e788008211f' <br /><br />Problem: <br /><br />For some reason the root version doesn't exist anymore. Normally, WE CAN delete this object because it does not have a root document <br /><br />Steps: <br /><br />- Need to get the dump of the objects and check which version are those and check the all tree <br /><br />- Need to change in SQL the i_chronicle_id to the lower version and make it the root <br /><br /><br />In SQL <br /><br />SQL> update dm_sysobject_s set i_chronicle_id='< who ever is the lower version>' where i_chronicle_id='09006e788008211f'; <br /><br />SQL> commit; <br />OR <br /><br />SQL>delete from dm_sysobject_r where r_object_id ='09006e7880082141' <br /><br />SQL>delete from dm_sysobject_s where r_object_id ='09006e7880082141' <br /><br />--- QUERY---: select a.r_object_id as p1, a.i_antecedent_id as p2 from dm_sysobject_s a where a.i_antecedent_id <> '0000000000000000' and not exists (select * from dm_sysobject_s b where b.r_object_id = a.i_antecedent_id) <br /><br />WARNING CC-0024: Sysobject with r_object_id '09006e7880082141' references a non-existent i_antecedent_id '09006e788008211f' <br /><br />Problem: <br /><br />In this particular case the i_chronicle_id which is the i_antecedent_id is gone, OR WILL BE DELETED FROM THE STEP ABOVE. <br /><br />Steps: <br /><br />- Need to update i_antecedent_id to 16 zeros <br /><br /><br />SQL> update dm_sysobject_s set i_antecedent_id='0000000000000000' where i_antecedent_id='09006e788008211f'; <br /><br />SQL> commit; <br /><br />--- QUERY---: select a.r_object_id as p1, a.r_workflow_id as p2 from dmi_workitem_s a where not exists (select b.r_object_id from dm_workflow_s b where b.r_object_id = a.r_workflow_id) <br /><br />WARNING CC-0043: dmi_workitem object with r_object_id '4a006e7880000119' references non-existent dm_workflow object with id '4d006e788000010c' <br /><br />WARNING CC-0043: dmi_workitem object with r_object_id '4a006e788000011e' references non-existent dm_workflow object with id '4d006e788000010e' <br /><br /><br />Problem: <br /><br /><br />The workitem is pointing to a non-existing workflow instance probable related to a bug. <br /><br /><br />Steps: <br /><br /><br />- Dump the dmi_workitem object and set to 16 zeros the r_workflow_id <br /><br />- Get the r_queue_item_id value and set the item_id to 16 zeros and delete_flag to true as solution of Warning CC-0042 <br /><br />- dm_QueueMgt will cleanup the queue_item and destroy the dmi_workitem object <br /><br /><br />Workitem: <br /><br />API> fetch,c,4a006e7880000119 <br /><br /><br />API> set,c,4a006e7880000119,r_workflow_id <br /><br />SET> 0000000000000000 <br /><br /><br />API> save,c,4a006e7880000119 <br /><br /><br />Queue_item <br /><br /><br />API> fetch,c,1b006e788001d911 <br /><br /><br />API> set,c,1b006e788001d911,item_id <br /><br />SET> 0000000000000000 <br /><br /><br />API> set,c,1b006e788001d911,delete_flag <br /><br />SET> 1 <br /><br /><br />API> save,c,1b006e788001d911 <br /><br /><br />Workitem: <br /><br /><br />API> fetch,c,4a006e7880000119 <br /><br /><br />API> destroy,c,4a006e7880000119 <br /><br /><br /><br />--- QUERY---: select a.r_object_id as p1, a.r_workflow_id as p2 from dmi_package_s a where not exists (select b.r_object_id from dm_workflow_s b where b.r_object_id = a.r_workflow_id) <br /><br />WARNING CC-0045: dmi_package object with r_object_id '49006e7880000116' references non-existent dm_workflow object with id '4d006e788000010c' <br /><br />WARNING CC-0045: dmi_package object with r_object_id '49006e7880000118' references non-existent dm_workflow object with id '4d006e788000010e' <br /><br /><br />Problem: <br /><br /><br />dmi_package is pointing to a non-existing workflow <br /><br /><br />Steps: <br /><br /><br />- Set the r_workflow_id to 16 zeros <br /><br />- Destroy the dmi_package object <br /><br /><br />API> fetch,c,49006e7880000116 <br /><br /><br />API> set,c,49006e7880000116,r_workflow_id <br /><br />SET> 0000000000000000 <br /><br /><br />API> save,c,49006e7880000116 <br /><br /><br />API> fetch,c,49006e7880000116 <br /><br /><br />API> destroy,c,49006e7880000116 <br /><br /><br /><br />--- QUERY---: select ws.r_object_id as p1, pr.r_component_id as p2 from dm_workflow_s ws, dm_workflow_r wr, dmi_package_s ps, dmi_package_r pr where ws.r_object_id = wr.r_object_id AND wr.r_act_state != 2 AND pr.r_component_id > '0000000000000000' AND ws.r_runtime_state IN (1,3) AND ws.r_object_id = ps.r_workflow_id AND wr.r_act_seqno = ps.r_act_seqno AND ps.r_object_id = pr.r_object_id AND not exists (select a.r_object_id from dm_sysobject_s a where a.r_object_id = pr.r_component_id) <br /><br />WARNING CC-0046: dm_workflow object with r_object_id '4d006e7880002501' references non-existent sysobject with r_component_id '09006e788000dffd' <br /><br />WARNING CC-0046: dm_workflow object with r_object_id '4d006e7880000d09' references non-existent sysobject with r_component_id '09006e7880006e60' <br /><br /><br />Problem: <br /><br /><br />The r_component_id of the dmi_package and is making reference to a workflow instance doesn't exist anymore <br /><br /><br />Steps: <br /><br /><br />- Set the r_component_id and r_component_chron_id (Chronicle ID of the object identified at the corresponding index position in r_component_id.) to 16 zeros and destroy it. <br /><br />- Or set r_component_id to a existing package with his chronicle_id in r_component_chron_id <br /><br /><br />API> retrieve,c,dmi_package where r_workflow_id='4d006e7880002501' <br /><br />... <br /><br />4d0a636280000900 <br /><br />API> set,c,490a636280000900,r_component_id <br /><br />Set >0000000000000000 <br /><br />... <br /><br />Ok <br /><br />API> set,c,490a636280000900,r_component_chron_id <br /><br />Set >0000000000000000 <br /><br />... <br /><br />Ok <br /><br />API> save,c,490a636280000900 <br /><br />... <br /><br />Ok <br /><br /><br /><br />OR <br /><br /><br /><br />API> set,c,490a636280000900,r_component_id <br /><br />Set >090a636280004c85 <br /><br />... <br /><br />Ok <br /><br />API> set,c,490a636280000900,r_component_chron_id <br /><br />Set >090a636280004655 <br /><br />... <br /><br />Ok <br /><br />API> save,c,490a636280000900 <br /><br />... <br /><br />Ok <br /><br /><br /><br />Check ACLs with non-existent users <br /><br />WARNING CC-0007: ACL object with r_object_id '45006e5880000507' has a non-existent user 'test1' <br /><br />WARNING CC-0007: ACL object with r_object_id '45006e5880000d00' has a non-existent user 'test1' <br /><br /><br />Problem: <br /><br /><br />The ACL contains a non-existing user in r_accessor_name attribute <br /><br /><br />Steps: <br /><br /><br />- Dump the acl <br /><br />- Check the index for the non-existing user <br /><br />- Using remove API call, remove the user per index and also make sure that you remove the same index for r_accessor_permit, r_accessor_xpermit and r_is_group attributes. If CS is 4.2.x this will not have r_accessor_xpermit <br /><br /><br />In API: <br /><br /><br />API> fetch,c,450a636280002512 <br /><br />... <br /><br />Ok <br /><br />API> dump,c,450a636280002512 <br /><br />... <br /><br />USER ATTRIBUTES <br /><br /><br />object_name : peoplesoft_acl <br /><br />description : peoplesoft permission set <br /><br />owner_name : Miguel_Test52 <br /><br />globally_managed : F <br /><br />acl_class : 0 <br /><br /><br />SYSTEM ATTRIBUTES <br /><br /><br />r_object_id : 450a636280002512 <br /><br />r_is_internal : F <br /><br />r_accessor_name [0]: dm_world <br /><br />[1]: dm_owner <br /><br />[2]: dmadmin <br /><br />[3]: test1 <br /><br />r_accessor_permit [0]: 3 <br /><br />[1]: 7 <br /><br />[2]: 7 <br /><br />[3]: 7 <br /><br />r_accessor_xpermit [0]: 0 <br /><br />[1]: 0 <br /><br />[2]: 3 <br /><br />[3]: 3 <br /><br />r_is_group [0]: F <br /><br />[1]: F <br /><br />[2]: F <br /><br />[3]: F <br /><br />r_has_events : F <br /><br /><br />APPLICATION ATTRIBUTES <br /><br /><br /><br />INTERNAL ATTRIBUTES <br /><br /><br />i_is_replica : F <br /><br />i_vstamp : 1 <br /><br /><br />In this case the index 3 contains the user that we need to remove (test1) <br /><br /><br />API> remove,c,450a636280002512,r_accessor_name[3] <br /><br />... <br /><br />Ok <br /><br />API> remove,c,450a636280002512,r_accessor_permit[3] <br /><br />... <br /><br />Ok <br /><br />API> remove,c,450a636280002512,r_accessor_xpermit[3] <br /><br />... <br /><br />Ok <br /><br />API> remove,c,450a636280002512,r_is_group[3] <br /><br />... <br /><br />Ok <br /><br />API> save,c,450a636280002512 <br /><br />... <br /><br />Ok <br /><br />API> dump,c,450a636280002512 <br /><br />... <br /><br />USER ATTRIBUTES <br /><br /><br />object_name : peoplesoft_acl <br /><br />description : peoplesoft permission set <br /><br />owner_name : Miguel_Test52 <br /><br />globally_managed : F <br /><br />acl_class : 0 <br /><br /><br />SYSTEM ATTRIBUTES <br /><br /><br />r_object_id : 450a636280002512 <br /><br />r_is_internal : F <br /><br />r_accessor_name [0]: dm_world <br /><br />[1]: dm_owner <br /><br />[2]: dmadmin <br /><br />r_accessor_permit [0]: 3 <br /><br />[1]: 7 <br /><br />[2]: 7 <br /><br />r_accessor_xpermit [0]: 0 <br /><br />[1]: 0 <br /><br />[2]: 3 <br /><br />r_is_group [0]: F <br /><br />[1]: F <br /><br />[2]: F <br /><br />r_has_events : F <br /><br /><br />APPLICATION ATTRIBUTES <br /><br /><br /><br />INTERNAL ATTRIBUTES <br /><br /><br />i_is_replica : F <br /><br />i_vstamp : 2 <br /><br /><br />API <br /><br /><br /><br />WARNING CC-0059: The dm_sysobject with id '0900f6ae80002980' references a non-existent policy object with id '46004a1a80003dae' <br /><br /><br />Need to update the r_policy_id for this object to 0000000000000000 <br /><br /><br />SQL> insert into dm_policy_s values('46004a1a80003dae',2,NULL,'0000000000000000',NULL); <br /><br /><br />SQL> commit; <br /><br /><br /><br />--- Query --- select a.name,a.s_index_attr from dm_type_s a where not exists(select b.r_object_id from dmi_index_s b where b.r_object_id=a.s_index_attr) <br /><br /><br />WARNING CC-0074: Type object for type 'dm_folder' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br />WARNING CC-0074: Type object for type 'dm_document' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br />WARNING CC-0074: Type object for type 'dm_note' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br />WARNING CC-0074: Type object for type 'dmi_dist_comp_record' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br />WARNING CC-0074: Type object for type 'dm_query' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br />WARNING CC-0074: Type object for type 'dm_script' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br />WARNING CC-0074: Type object for type 'dm_smart_list' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br />WARNING CC-0074: Type object for type 'dm_procedure' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br /><br />Problem: <br /><br /><br />The type is pointing to a non-existing index in dmi_index <br /><br /><br /><br />This is a harmless warning you can ignore. BUG# 65798 is logged on this issue and fixed in Content Server 5.3 OR if you really don't want to see this Warning, you can fix it like this; <br /><br /><br />EXAMPLE; <br /><br /><br />WARNING CC-0074: Type object for type 'dm_folder' references a non-existent dmi_index object for _s table with r_object_id '0000000000000000' <br /><br /><br />Steps: <br /><br /><br />- Confirm the value of the index by doing the following in SQLplus: <br /><br /><br />SQL> select S_INDEX_ATTR from dm_type_s where name='dm_folder'; <br /><br /><br />S_INDEX_ATTR <br /><br />---------------- <br /><br />1f001a9880000142 <br /><br /><br />- Check the indexes for this type: <br /><br /><br />SQL> col index_name format a20 <br /><br />SQL> col column_name format a20 <br /><br />SQL> col column_position format 99999999990 <br /><br />SQL> select index_name,column_name,column_position from user_ind_columns where table_name like 'DM_FOLDER%'; <br /><br /><br />INDEX_NAME COLUMN_NAME COLUMN_POSITION <br /><br />-------------------- -------------------- --------------- <br /><br />D_1F001A9880000143 R_OBJECT_ID 1 <br /><br />D_1F001A9880000143 I_POSITION 2 <br /><br />D_1F001A9880000015 R_FOLDER_PATH 1 <br /><br />D_1F001A9880000016 I_ANCESTOR_ID 1 <br /><br />D_1F001A9880000016 R_OBJECT_ID 2 <br /><br />D_1F001A9880000142 R_OBJECT_ID 1 <br /><br /><br />6 rows selected. <br /><br /><br />SQL> <br /><br /><br />As you can see the the index name + D_ match with the value of S_INDEX_ATTR last row in the example. <br /><br /><br />You need to check if this index exists in dmi_index_s and _r <br /><br /><br />SQL> select count(*) from dmi_index_s where r_object_id='1f001a9880000142'; <br /><br /><br />COUNT(*) <br /><br />---------- <br /><br />1 <br /><br /><br />SQL> select count(*) from dmi_index_r where r_object_id='1f001a9880000142'; <br /><br /><br />COUNT(*) <br /><br />---------- <br /><br />1 <br /><br /><br />SQL> <br /><br /><br />You should not have the object in any of this tables if exists in one of this tables you must delete it. <br /><br /><br />SQL>delete from dmi_index_s where r_object_id='1f001a9880000142'; <br /><br /><br />SQL>delete from dmi_index_r where r_object_id='1f001a9880000142'; <br /><br /><br />OR <br /><br /><br />- Set the S_INDEX_ATTR to 16 zeros and then recreate the index using API with unique attribute "R_OBJECT_ID" as is state it above. update S_INDEX_ATTR from dm_type_s to the correct value without the D_ and that will fix the inconsistency<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-444519342959561204?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-29879968791574190892008-08-21T23:15:00.001-07:002008-08-21T23:15:35.491-07:001. Login into the appropriate Content Server box using telnet.<br /><br />NOTE: since our Application is Load Balancer we need to change for all the three content servers.<br /><br />2. Stop all the process and services (follow the start/stop document).<br />3. Stop the Index Server & Index Agents.<br /><br />NOTE: Stop all the server side Documentum related process/services. E.g.: <br />Docbrokers, docbases, method servers, thumb nail server etc... If 2DAM docbase resides in the same content server its safe that we stop DTS/MTS Boxes).<br /><br />4. On the /lapps/docadm location, type the command “passwd”.<br />5. It will ask for the current password, give it and press enter.<br />6. It will ask for the new password, type the new password and click enter.<br />7. Repeat the steps 1 to 6 for the other content servers.<br />8. Restart all the Documentum server side process as per the start/stop document in all the three content servers.<br />9. Edit the DSCredentials.xml in the location cabinets/gdm/customizations folder by login in through DA.<br />10. Modify with the new installation owner password<br /><br />NOTE: New GDM Env (GDM Clean & GDM_PT docbases does not require to update the DSCredentials.xml since the installation owner account credentials was not hard coded. But safer sides please check when this particular Operation is being performed). <br /><br />11. update the business.xml using DA in the location cabinets/gdm/ (if available)<br /><br />NOTE: New GDM Env (GDM Clean & GDM_PT docbases does not require to update the business.xml since the installation owner account credentials was not hard coded. But safer sides please check when this particular Operation is being performed). <br /><br /><br />12. Repeat the steps 8 and 9 for all the 3 applications.<br /><br /> NOTE: login to each docbase using DA and perform the operations (if applicable).<br /><br />13. Do complete healths check of all the 4 Applications.<br />14. Select any of the default jobs and check its status by running it manually.<br /><br />Note: Consistency Checker Job is the safe option to check the status of the password change as it won’t create/modify/ update/delete any objects. <br /><br />NOTE: As we are unable to test the LDAP job in PSIC, we need to make sure that it is running in production when we perform this operation.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2987996879157419089?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-83444511391739983592008-08-21T23:03:00.000-07:002009-03-19T10:10:19.843-07:00Sequence of Events to Stop the System<br />1. Log into Windows hosts to stop all of the rendition agent services (MTS/DTS)<br />2. Log into Index Agent host, to the Admin console for each agent, and Stop the indexing process for each agent in the console<br />http://<server_name>:9081/IndexAgent1/login.jsp<br />Click on the Agent Status action link named “Stop”.<br />3. From the command line of the primary Index Server host, stop the Index Agent <br />a. $ cd $DOCUMENTUM/share/IndexAgents<br />b. $ ./shutdownAllIndexAgents.sh<br />4. From the command line of the secondary Index Server, stop the FAST index server a. $ cd $DOCUMENTUM/fulltext/IndexServer/bin<br />b. $ ./shutdown.sh<br />c. To verify the shutdown, you can run the “nctrl systatus” command.<br />d. To clear the DMCL cache navigate to “/tmp/dmcl” and perform <br />the “rm –rf *” command<br />5. From the command line of the primary Index Server, stop the FAST index server<br />a. $ cd $DOCUMENTUM/fulltext/IndexServer/bin<br />b. $ ./shutdown.sh<br />c. To verify the shutdown, you can run the “nctrl systatus” command.<br />d. To clear the DMCL cache navigate to “/tmp/dmcl” and perform<br /> the “rm –rf *” command<br />6. From the WebLogic management console, stop all of the running applications<br />a. WebDAV<br />b. DA<br />c. DAM<br />d. Webtop<br />e. To clear the DMCL cache navigate to “/tmp/dmcl” and perform <br />the “rm -rf *” command<br />7. On each of the 3 content servers, stop the following IN THIS ORDER:<br />a. Java Method server<br />i. $ cd $DM_HOME/tomcat/bin/<br />ii. $ ./shutdown.sh<br />b. Thumbnail server<br />i. $ cd $DM_HOME/thumbsrv/bin<br />ii. $ ./dm_thumbsrv_stop.csh<br />c. Repository<br />i. $ cd $DOCUMENTUM/dba<br />ii. $ ./dm_shutdown_<2DAM>.sh<br />iii. $ ./dm_shutdown_<GDM>.sh<br />d. The last thing to stop on each of the 3 content servers are the 3 Docbrokers<br />i. $ cd $DOCUMENTUM/dba<br />ii. $ ./dm_stop_Docbroker<br />1. This stops the Docbroker on port 1489<br />iii. $ ./dm_stop_DocbrokerP1<br />1. This stops the Docbroker on port 1490<br />e. To clear the DMCL cache navigate to “/tmp/dmcl” and perform <br />the “rm –rf *” command<br />8. Log into the SunOne web servers and stop the services for your applications <br />9. With all repository services stopped, the servers and database services can be safely stopped/restarted if necessary.<br /><br /><strong>Sequence of Events to Start the System</strong><br />The process for starting the application is basically to execute the steps above in reverse order<br />1. Ensure database services and all hosts have been restarted and are running<br />a. Try to connect to the database with sqlplus as the repository owner<br />2. Log into the SunOne Web servers and start the services for <Application Name> <br />3. On each of the 3 content servers, start the following IN THIS ORDER<br />a. Docbrokers<br />i. $ cd $DOCUMENTUM/dba<br />ii. $ ./dm_launch_Docbroker<br />1. This starts the Docbroker on port 1489<br />iii. $ ./dm_launch_DocbrokerP1<br />1. This starts the Docbroker on port 1490<br />b. Repositories<br />i. $ cd $DOCUMENTUM/dba<br />ii. $ ./dm_start_<AppName>.sh<br />c. Method Server<br />i. $ cd $DM_HOME/tomcat/bin<br />ii. ./startup.sh<br />iii. Verify this by hitting the method server URL at http://<CONTENT_SERVER_HOST>:9080/DmMethods/servlet/DoMethod<br />d. Thumbnail Server<br />i. $ cd $DM_HOME/thumbsrv/bin<br />ii. $ nohup ./dm_thumbsrv_start.csh &<br />iii. Verify this by hitting the URL for the Thumbnail server at https://<content_server_host>:8443/thumbsrv/getThumbnail?format=msw8<br />1. You can substitute other format values here, such as jpeg or bmp<br />4. On the 3 WebLogic application server hosts, log in and start all of the applications from the command line. (NOTE: If the server itself has been restarted, you will need to log and start the WebLogic admin console as well.)<br />a. $ wls<br />b. $ ./startda.sh<br />c. $ ./start<appname>.sh<br />f. You can verify that all applications have started up correctly on each WLS by logging into the WLS admin console.<br />g. Within the WLS admin console, do first time Garbage Collection on all the managed servers by navigating into “Monitoring” > “Performance” tabs and click on “Force Garbage Collection” button.<br />5. From the command line of the primary Index Server, start the FAST index server<br />a. $ cd $DOCUMENTUM/fulltext/IndexServer/bin<br />b. $ ./startup.sh<br />c. To verify the start, you can run the “nctrl systatus” command and see that all processes are “running”<br />6. From the command line of the secondary Index Server, start the FAST index server a. $ cd $DOCUMENTUM/fulltext/IndexServer/bin<br />b. $ ./startup.sh<br />c. To verify the startup, you can run the “nctrl systatus” command.<br />7. From the command line of the primary Index Server host, start the Index Agent a. $ cd $DOCUMENTUM/share/IndexAgents<br />b. $ ./startupAllIndexAgents.sh<br />8. Log into Index Agent host, to the Admin console for each agent, and Start the indexing process for each agent in the console<br />i. http://<server_name>:9081/IndexAgent1/login.jsp<br />Click on the Agent Status action link named “Start”.<br />9. Log into Windows hosts to start all of the rendition agent services (MTS/DTS)<br />10. From within DA or applications themselves, verify complete environment functionality with the test cases provided.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-8344451139173998359?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-47194145605906663562008-08-11T15:42:00.000-07:002008-08-11T15:43:09.555-07:00Failed to load preferences, Cannot locate file - dfc.properties <br /> <br />ID: esg82728 <br /><br />SOLUTION <br /><br />Symptoms<br /><br />While uninstalling the existing Index Agent on Solaris machine, an error dialog box is displayed:<br /><br />"Failed to load preferences: java.io.FileNotFoundException: Cannot locate file - dfc.properties"<br /><br />Cause<br /><br />Environment variable DFC_DATA set in dmadmin's profile seems to cause this problem. All the other environment variables seemed to be correct.<br /><br />Resolution<br /><br />When DFC_DATA was commented out in the dmadmin's profile, the problem disappeared.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4719414560590666356?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-6751620115736503982008-08-11T15:25:00.000-07:002008-08-11T15:28:21.306-07:00Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid<br />MSCOMCTL.OCX error screenshot:<br /> <br />How to Correct or fix this dependency error: <br />1. First search your local drive for MSCOMCTL.OCX to see if it is missing. The path to the file is typically: C:\WINDOWS\system32 if you are running Windows XP <br />2. If the file is missing you can download it HERE <br />3. Once downloaded, click the MSCOMCTL.exe and extract the file to your C:\WINDOWS\system32 directory<br /><br />Resolution : Install Microsoft ActiveX Control Pad Installation <br /><br />( setuppad.exe )<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-675162011573650398?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-48542757102362082332008-08-11T15:24:00.002-07:002008-08-11T15:25:23.401-07:00You will need to do the following steps: <br /><br />- Stop the Docbase (repository) <br />- Backup file dbpasswd.txt under /Documentum/dba/config/<repository name>/ <br />- Modify dbpasswd.txt file with the new database password in plain text (without encrytion just like abraxis1234) <br />- Re-encrypt the dbpasswd.txt file: <br /><br />cd $DM_HOME/bin means --> C:\Documentum\product\5.3\bin<br /><br />dm_encrypt_password -docbase <docbase name> -rdbms -encrypt <database password> <br /><br />- Start the Docbase (repository).<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4854275710236208233?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-76815303746745924192008-08-11T15:23:00.001-07:002008-08-11T15:23:43.996-07:00Installed DCM and DA on APP Server machine but login page is not displayed but DOne message at status bar<br />Sol: Update the class path in weblogic.cmd and restart weblogic<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7681530374674592419?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-21522397709319722222008-08-11T15:21:00.000-07:002008-08-11T15:22:10.299-07:00Symptoms<br /><br />When running Document Transformation Services, the following message can be observed in the CTS log file located under Program Files\Documentum\CTS\logs:<br /><br />INFO [ main] CTSPluginHandlerImpl - Unable to instantiate the following MP: com.documentum.cts.plugin.wordperfect.WordPerfectPlugin<br />com.documentum.cts.plugin.common.CTSPluginException: Can't get object clsid from progid<br />Cause Exception was: Unable to instantiate WordPerfect MPI: Can't get object clsid from progid<br />com.jacob.com.ComFailException: Can't get object clsid from progid<br /> at com.jacob.com.Dispatch.createInstanceNative(Native Method)<br /> at com.jacob.com.Dispatch.<init>(Dispatch.java:160)<br /> at com.jacob.activeX.ActiveXComponent.<init>(ActiveXComponent.java:54)<br /><br /> <br /><br />Cause<br /><br />This issue will appear if WordPerfect is not installed on the DTS server. By default, the plugin for WordPerfect is included in the CTSPluginService.xml file located under Program Files\Documentum\CTS\config.<br /><br /> <br /><br />Resolution<br />- Take a back up for CTSPluginService.xml<br />Navigate to Program Files\Documentum\CTS\config and open the CTSPluginService.xml with a text editor. Locate the following line:<br /><br /><CTSPlugin CONFIGFILE="C:\PROGRA~1\DOCUME~1\CTS\config\wordperfect\wordperfect.xml" DELEGATE_CLASS="com.documentum.cts.plugin.wordperfect.WordPerfectPlugin"/><br /><br /> <br /><br />Comment out this line using the following syntax:<br /><br /><!--<CTSPlugin CONFIGFILE="C:\PROGRA~1\DOCUME~1\CTS\config\wordperfect\wordperfect.xml" DELEGATE_CLASS="com.documentum.cts.plugin.wordperfect.WordPerfectPlugin"/>--><br /><br /> <br /><br />Restart the CTS services and restart. The issue should be resolved.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2152239770931972222?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-40752180367552103822008-08-10T21:24:00.000-07:002008-08-10T21:27:19.301-07:00Error:<br />ORA-01034: Oracle not available<br />ORA-27101 : shared memory realm does not exist<br /><br />- restart Oracle Host service in services.msc in oracle server machine<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4075218036755210382?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-83046330404581046012008-08-10T21:18:00.001-07:002008-08-10T21:18:46.365-07:00- Copy the File store from Source to Target Environment<br /> .... copy the data folder to target Data folder<br />- Update the dm_location_s for filestore path<br /><br /> select file_system_path from dm_location_s<br /><br /> D:\Documentum\data\ABRAXIS_PRD\content_storage_01<br /> D:\Documentum\data\ABRAXIS_PRD\thumbnail_storage_01<br /> D:\Documentum\data\ABRAXIS_PRD\streaming_storage_01<br /> D:\Documentum\data\ABRAXIS_PRD\replicate_temp_store<br /> D:\Documentum\data\ABRAXIS_PRD\replica_content_storage_01<br /><br />Update the above to the targeted environment path<br /><br />restart the docbase<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-8304633040458104601?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-48812391612866723882008-08-10T20:57:00.001-07:002008-08-10T20:58:35.412-07:001. Shutdown the docbase being moved on the target server <br />2. Create a copy of the AEK file (aek.key) in \Documentum\dba\secure directory on the target server and rename it (e.g., aek.bak). This is just in case something happens to the file and we need to rollback. <br />3. From sql on the database: <br /> update dm_docbase_config_s set i_crypto_key = ' '; <br />4. From sql: <br /> SQL> select r_object_id from dmi_vstamp_s where i_application = 'dm_docbase_config_crypto_key_init'; <br />5. delete from dmi_object_type where r_object_id = 'returned r_object_id from above'; <br />6. SQL> commit; <br />7. SQL> delete from dmi_vstamp_s where r_object_id = 'returned r_object_id from step above'<br />8. SQL> commit; <br />9. From sql on the database <br /> update dm_docbase_config_s set i_ticket_crypto_key = ' '; <br />10. from sql: <br /> SQL> select r_object_id from dmi_vstamp_s where i_application = 'dm_docbase_ticket_config_crypto_key_init'; <br />11. delete from dmi_object_type where r_object_id = 'returned r_object_id from above'; <br />12. SQL> commit; <br />13. SQL> delete from dmi_vstamp_s where r_object_id = 'returned r_object_id from step above'<br />14. SQL> commit; <br />15. To re-encrypt the dbpasswd.txt file for the moved docbase, navigate to the <root>:\documentum\product\5.3 \bin directory in a command window.<br />16. From a command prompt, enter the following:<br />dm_encrypt_password -docbase <docbase name> -rdbms -encrypt <database password> <br />17. You will need to reboot the entire system - Content Server, PDF Aqua, Queue Manager, and Application and remove all caches once you have moved it.. <br />18. Startup the docbase service<br />19. You might have to repeat some of the steps from this process. especially the i_ticket_crypto_key. I was unable to find it the first time, but the second time I ran through the instructions after trying to <br />start the docbase once, I found this key and was able to delete it.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-4881239161286672388?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-78808207323735257522008-08-10T20:55:00.001-07:002008-08-10T20:55:43.071-07:00Migration/ Cloning an environment<br /> <br /><br />1. Create a new docbase with the same Repository name, repository Id on the target server <br />2. Have your DBA to create an empty oracle/sql schema with the same docbsae name in your source environment<br />3. Copy the file store from the source environment into the new 'Data' folder<br />4. Import Oracle Schema from the source environment into the target server<br />5. Update aek.key<br />6. If the path has to change , update dm_location_s entries<br />7. Restart the target database<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7880820732373525752?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-55607096292044359592008-08-09T14:57:00.001-07:002008-08-09T14:57:44.822-07:00File Store creation comprise of two parts first is creation of file location and second creation and association of file store with file location.<br /><br /> <br /><br />For creating file location through Documentum Administrator kindly follow the following procedure.<br /><br /> <br /><br />1 Create the folder physically on your content server for file store.<br /><br />2 Login to your Documentum Administrator instance.<br /><br />3 Select the Docbase<br /><br />4 Expand an Administration tab.<br /><br />5 Select Storage option under administration <br /><br /> <br /><br />Click on File and select New Location <br /><br />Provide the name for your new desired service location<br /><br />Now Select the file location where you have created the Folder physically to store the Documents.<br /><br />Leave the option Path type as Directory and security type as publicopen.<br /><br />Click on OK to create the new location for file store.<br /><br /> <br /><br />Follow the below procedure to create new File Store.<br /><br /> <br /><br />Now select File and click on New file Store option<br /><br />Give the name for your new file store<br /><br />Select the Location which you have created just before from Drop down list.<br /><br />Now Click on OK.<br /><br /> <br /><br />Run the following API to reinitialize the docbase connection<br /><br />.<br /><br />API>reinit,c<br /><br />API>flush,c,persistentcache<br /><br />API>flush,c,persistentobjcache<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-5560709629204435959?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-80658687031571317332008-08-09T00:03:00.000-07:002008-08-09T00:05:26.241-07:00Dump Script:<br /><br /> <br /><br />create,c,dm_dump_record<br /><br />set,c,l,file_name<br /><br />D:\Abraxisdump\testdata\CDMSFileDump.dmp<br /><br />set,c,l,include_content<br /><br />T<br /><br />append,c,l,type<br /><br />dm_document<br /><br />append,c,l,predicate<br /><br />object_name=’ ‘<br /><br />save,c,l<br /><br />getmessage,c<br /><br /> <br /><br /> <br /><br />Load Script:<br /><br /> <br /><br />create,c,dm_load_record<br /><br />set,c,l,file_name<br /><br />D:\AbraxisLoad\testdata\CDMSFileDump.dmp<br /><br />save,c,l<br /><br />getmessage,c<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-8065868703157131733?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-52005797901789773852008-08-08T23:43:00.001-07:002008-08-08T23:43:55.742-07:00Why do I see this error "[DM_API_E_NOTYPE]error: "Type name 'dm_application' is <br /> <br />Below is an excerpt of the error message seen in the docapp installer log. <br /><br />ERROR: Installation cannot proceed. <br /><br />DfException@1d0:: THREAD: main; MSG: [DM_API_E_NOTYPE]error: "Type name 'dm_application' is not a valid type."; ERRORCODE: 100; NEXT: null <br /><br />ERROR: Installation cannot proceed. <br /><br />DfException@1d0:: THREAD: main; MSG: [DM_API_E_NOTYPE]error: "Type name 'dm_application' is not a valid type."; ERRORCODE: 100; NEXT: null at com/documentum/fc/server/session/DfiSessionDMCL.dmAPIGet (DfiSessionDMCL.java) at com/documentum/fc/client/DfSession.apiGet (DfSession.java) at com/documentum/fc/client/DfPIntObjectL. (DfPIntObjectL.java) at com/documentum/fc/client/DfObjectCache.createPIntObject (DfObjectCache.java) at com/documentum/fc/client/DfObjectCache.newObject (DfObjectCache.java) at com/documentum/fc/client/DfSession.newObject (DfSession.java) at com/documentum/ApplicationManager/DfApplication.newApplication (DfApplication.java) at com/documentum/ApplicationInstall/DfAppInstallerUtilities.createLivePackage (DfAppInstallerUtilities.java) at com/documentum/ApplicationInstall/DfAppInstaller.createEnvironment (DfAppInstaller.java) at com/documentum/ApplicationInstall/DfAppInstaller.startInstall (DfAppInstaller.java) <br /><br />ABORT TRANSACTION <br /><br /><br />RESOLUTION: <br />This error occurs because the dm_application object type is not installed in the Documentum environment. This means the 'headstart.ebs' script failed or was not executed. <br /><br />Check the following path on the Content Server: <br /><br />\documentum\dba\config\<docbase name> <br /><br />Search for the 'headstart.out' file. <br />Open the file, look for creation of dm_application type. <br /><br />If the 'headstart.out' file is not listed, this means the script wasn't executed. <br /><br />Run the 'headstart.ebs' script. Follow the instructions as listed in the Content Server documentation for executing a script. <br /><br />Once this is executed. The dm_application type, will be created. <br /><br />Re-run the docapp installer, the docapp installation will now succeed.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-5200579790178977385?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-63374615741330940502008-08-08T23:40:00.001-07:002008-08-08T23:40:52.320-07:00Content Server (CS) Version 5.1 and higher uses new version of headstart.ebs which is replacing headstar.dql in previous version of eConentent Server (eCS). <br /><br />If for some reasons you need to run this script manually, include all 15 arguments for the dmbasic command. <br /><br />From the command line (Unix or Windows) type the following: <br /><br />dmbasic -fheadstart.ebs -eInstall -docbaseName <docbasenme> -docbaseUserPassword <password> -docbaseDescrption <any description> -documentumHome $DM_HOME -dataHome $DOCUMENTUM/data -dbaHome $DOCUMENTUM/dba -configureHome $DM_HOME/install -shareHome $DOCUMENTUM/share -hostName <local machine name> -osType <Windows or Unix> -localeLanguage en -smtpServerName <smtp server> -email <SMTP user email address> -loginUsername <install owner name><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-6337461574133094050?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-39360918636787515732008-08-08T23:34:00.000-07:002008-08-08T23:35:50.750-07:00Symptoms<br /><br />5.3 SP4 and SP5 Clients will see "RPC 116 error" and/or "Authentication failure".<br /><br />This error is only seen with trace -otrace_authentication and -oticket_trace options:<br />Start-AuthenticateUserByTicket:UserLoginName(testuser1), <br />TICKET TRACE: dmLoginTicketMgr::VerifyTicket() : encodedBuffer = DM_TICKET=AAAAAgAAAOQAAAAKAAAAFUeUZYRHlGawAAAAOGxzY21zAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEZyYW4gU2Nod2lldHprZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGxzY21zAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGx2Y21zMDEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGNlaWxpbmcxMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAM0pyOTdRTDJOakFUbVhwak15Y21CWDdLbG5zYnM2aUVUU1pXUy9kbHdwWjlzcllmaGIrNFZnPT0=<br />TICKET TRACE: dmLoginTicketMgr::LoadTicket() : Login ticket successfully loaded into dmLoginTicket struct.<br />TICKET TRACE: Failed to verify login ticket because user name mismatch: ticket.m_userName=tsestuser2, userName=testuser1<br />End-AuthenticateUserByTicket:<br />failure<br /><br />Cause<br /><br />If a ticketed session is timed out, the generated ticket would be different from the user who actually uses the ticket to establish the connection. Also setting the wrong password in the server's session causes subsequent server reconnects to fail in the case of client session timeout. <br /><br />Resolution<br /><br />This issue is resolved in CS 5.3 SP6, otherwise an eng patch request must be submitted.<br /><br />Determining if you are having this issue:<br />Perform the following 2 tests with tracing turned on.<br /><br /># To enable ticket trace<br />API> apply,c,NULL,SET_OPTIONS,OPTION,S,ticket_trace,VALUE,B,T<br /><br /># To disable ticket trace, after the test are completed.<br />API> apply,c,NULL,SET_OPTIONS,OPTION,S,ticket_trace,VALUE,B,F<br />Send us the content server log file with ticket trace info.<br /> <br />DESCRIPTION OF UNIT TESTING TO BE TO VERIFY CHANGE: <br /><br />This is an example, do not use the ticket generated in this example for your test.<br />Just use the api commands listed.<br /><br />Test 1:<br />=====<br />Run IAPI to connect to docbase as super user.<br />Make sure the login ticket timeout value is set to 5 minutes in serverconfig object.<br />Make sure the DMCL session timeout value is also set to 5 minutes.<br /><br />Generate a login ticket for any non-super user, say tuser1 (make sure tuser1's password is different from that of super user).<br /><br />API> getlogin,c,tuser1<br />...<br />DM_TICKET=AAAAAgAAAOQAAAABAAAAAUcxydlHMcsFAAAAOHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAHR1c2VyMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHJycHZtaW5kZXgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAFJSUFZNSU5ERVgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAG1hbmFnZXIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaUkzL25xYXZPZzdMWEY4WWVNajg0bVpNQVpyZ3BJT1JGcXZIY0w0V1h1S1oyMDRsY2x2ZnNnPT0=<br /><br />Dump login ticket to see expiration date.<br /><br />API>dumploginticket,c,DM_TICKET=AAAAAgAAAOQAAAABAAAAAUcxydlHMcsFAAAAOHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAHR1c2VyMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHJycHZtaW5kZXgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAFJSUFZNSU5ERVgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAG1hbmFnZXIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaUkzL25xYXZPZzdMWEY4WWVNajg0bVpNQVpyZ3BJT1JGcXZIY0w0V1h1S1oyMDRsY2x2ZnNnPT0=<br />...<br />LOGIN TICKET DUMP<br />==========================================<br />Version : 5.3 (ticket version 2)<br />Scope : global<br />Sequence Number : 0000000001<br />Single Use : No<br />Create Time : Wed Nov 07 06:21:13 2007<br />Expiration Time : Wed Nov 07 06:26:13 2007<br />User : tuser1<br />Password : *********<br />Domain : rrpvmindex01<br />Server : vmcs01_535_ora10g203<br />Docbase : vmcs01_535_ora10g203<br />Host : RRPVMINDEX01<br />Connect to docbase as "tuser1" using the newly generated ticket.<br /><br />API>connect,vmcs01_535_ora10g203,tuser1,DM_TICKET=AAAAAgAAAOQAAAABAAAAAUcxydlHMcsFAAAAOHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAHR1c2VyMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHJycHZtaW5kZXgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAFJSUFZNSU5ERVgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAG1hbmFnZXIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaUkzL25xYXZPZzdMWEY4WWVNajg0bVpNQVpyZ3BJT1JGcXZIY0w0V1h1S1oyMDRsY2x2ZnNnPT0=<br />...<br />s1<br /><br />******************************************************** <br />IMPORTANT: <br />Wait for at least 10 minutes to make sure the ticket is expired, and the DMCL client's connection to docbase/content server is timed out ******************************************************** <br /><br />Then, try to re-connect to content server after client session is timed out and ticket is expired, by trying to create a dm_document object.<br /><br />API> create,s1,dm_document<br />...<br /><br />Make sure you do not get the following error message, you should get a new object_id after the "create" command is issued.<br /><br />[DM_API_E_NOTYPE]error: "Type name 'dm_document' is not a valid type."<br />[DM_SESSION_E_START_FAIL]error: "Server did not start session. Please see your system administrator or check the server log.<br />Error message from server was:<br />[DM_SESSION_E_RPC_ERROR]error: "RPC error 116 occurred: Unknown error code 116 (_nl_error_ = 0). Extended network error: 0"<br />[DM_SESSION_E_AUTH_FAIL]error: "Authentication failed for user tuser1 with docbase vmcs01_535_ora10g203.""<br /><br /><br />Test 2:<br />=====<br />Run IAPI as super user to create "TestMethod" dm_method object. <br />-------------------------------------------------------<br />create,s0,dm_method<br />set,s0,l,object_name<br />TestMethod<br />set,s0,l,method_verb<br />"sh" "/testmethod.sh"<br />set,s0,l,method_type<br />program<br />set,s0,l,trace_launch<br />1<br />save,s0,l<br />-------------------------------------------------------<br />Create file testmethod.sh in /tmp directory. Contents of testmethod.sh is as follows:<br />-------------------------------------------------------<br />#!/bin/sh -xvf<br /># print date time stamp to output file<br />date > /tmp/testmethod_output.txt<br />------------------------------------------------------<br />Now connect to docbase as non-super user "tuser1"<br />Generate a login ticket for "tuser1" (for himself)<br /><br />API> getlogin,c<br />...<br />DM_TICKET=AAAAAgAAAOQAAAABAAAAAkcxy85HMcz6AAAAOHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAHR1c2VyMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHJycHZtaW5kZXgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAFJSUFZNSU5ERVgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAG1hbmFnZXIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaUkzL25xYXZPZzdMWEY4WWVNajg0dUw0R0tzcG94TVZkYW9sdnFHcmZzaFJ6VmUzNTFPRmJBPT0=<br /><br />Dump the login ticket to see ticket detail<br /><br />API>dumploginticket,c,DM_TICKET=AAAAAgAAAOQAAAABAAAAAkcxy85HMcz6AAAAOHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAHR1c2VyMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHJycHZtaW5kZXgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAFJSUFZNSU5ERVgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAG1hbmFnZXIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaUkzL25xYXZPZzdMWEY4WWVNajg0dUw0R0tzcG94TVZkYW9sdnFHcmZzaFJ6VmUZNTFPRmJBPT0=<br />...<br />LOGIN TICKET DUMP<br />==========================================<br />Version : 5.3 (ticket version 2)<br />Scope : global<br />Sequence Number : 0000000002<br />Single Use : No<br />Create Time : Wed Nov 07 06:29:34 2007<br />Expiration Time : Wed Nov 07 06:34:34 2007<br />User : tuser1<br />Password : *********<br />Domain : rrpvmindex01<br />Server : vmcs01_535_ora10g203<br />Docbase : vmcs01_535_ora10g2<br />Host : RRPVMINDEX01<br />API> quit<br /><br />Quit out of API. This is to make sure the next IAPI DMCL connection pool does not contain any "tuser1" entries.<br />Now run IAPI and connect as super user, say "dmadmin".<br /><br />Then connect to docbase as "tuser1" using the login ticket generated from the previous IAPI run.<br />API>connect,vmcs01_535_ora10g203,tuser1,DM_TICKET=AAAAAgAAAOQAAAABAAAAAkcxy85HMcz6AAAAOHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAHR1c2VyMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHJycHZtaW5kZXgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAHZtY3MwMV81MzVfb3JhMTBnMjAzAAAAAAAAAAAAAAAAAFJSUFZNSU5ERVgwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAG1hbmFnZXIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaUkzL25xYXZPZzdMWEY4WWVNajg0dUw0R0tzcG94TVZkYW9sdnFHcmZzaFJ6VmUzNTFPRmJBPT0=<br />...<br />s1<br />After new session is established. Run "apply DO_METHOD" to launch "TestMethod".<br /><br />API> apply,s1,,DO_METHOD,METHOD,S, TestMethod<br />...<br />q0<br /><br />Check the "/temp" directory, see if output file testmethod_output.txt is created successfully, and the output file "testmethod_output.txt" contains the date timestamp info.<br /><br />Run the following commands to make sure the "TestMethod" is run successfully.<br />Make sure you do NOT see errors like this:<br />API> next,c,q0<br />...<br />OK<br />API> dump,c,q0<br />...<br />USER ATTRIBUTES<br /> result : 0<br /> process_id : 0<br /> launch_failed : T<br /> method_return_val : 0<br /> os_system_error : No Error Message Available<br /> timed_out : F<br /> time_out_length : 60<br />SYSTEM ATTRIBUTES<br />APPLICATION ATTRIBUTES<br />INTERNAL ATTRIBUTES<br />API> getmessage,s1,3<br />...<br />[DM_METHOD_E_ASSUME_USER_UV]error: "Your method named (Method2) failed to execute because the assume user process could not validation your user credentials. Assume User Process returned (-11=DM_CHKPASS_BAD_LOGIN)."<br />API><br /><br />If testing proves it is a ticket timeout issue. <br />This issue will be resolved in CS 5.3 SP6<br />Since this support Note was written prior to reslease of SP6, please request a eng hot fix<br /><br />CS_5.3_SP5_BUG_148355_WINDOWS_ORACLE_HOTFIX.zip<br />CS_5.3_SP5_BUG_148355_WINDOWS_SQL_HOTFIX.zip<br />ContentServer_aix_oracle_5.3SP5_bug_148355.tar.gz<br />ContentServer_solaris_oracle_5.3SP5_bug_148355.tar.gz<br /><br />Please provide the following information:<br />1. Content server version.<br />2. OS platform and version.<br />3. RDBMS info.<br />4. Test results testing above.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3936091863678751573?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-28728463733152340782008-08-08T23:28:00.001-07:002009-02-27T12:33:17.233-08:00The following steps are required to perform a manual uninstall of a Content<br />Transformation Services product <br />1. Stop the CTS and CTS Agent Services in the Windows Services dialog.<br />2. Use Windows Add/Remove Programs to uninstall Documentum Content<br />Transformation Services.<br />3. Use Windows Add/Remove Programs to uninstall Documentum DFC.<br />4. Restart the host.<br />5. Delete the following folders and all their contents:<br />• C:\Documentum<br />• C:\Program Files\Documentum<br />6. Remove any remaining Documentum products using Windows Add/Remove<br />Programs.<br />7. Open Windows regedit.<br />8. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE.<br />9. Delete the Documentum entry.<br />10. Reboot the host.<br />11. Log in to the CTS configured repository as an administrator user using DAM,<br />Webtop, or DA.<br />12. Delete the Media Server folder, located in the \System cabinet (select all children<br />and all versions when prompted during delete).<br />13. Navigate to \System\Applications.<br />14. Delete the CTSTransformRequest and MediaProfile folder (select All Objects, All<br />Versions, All Descendants when prompted).<br />15. Run the following two DQL statements against the repository, in this order:<br />a. delete cts_instance_info object<br /><br />You can now start a new installation of any Content Transformation Services product<br />(such as DTS or MTS).<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2872846373315234078?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-3043147868889893392008-08-08T23:26:00.000-07:002008-08-08T23:27:04.413-07:00Symptom:<br />During the installation of DTS you notice a failure "DiWACTSTransformXML failed! - Premature end of file", <br />and in the setuperror.log an error like this:<br />(Apr 20, 2007 8:08:12 AM), Setup.product.install, com.documentum.install.shared.common.error.DiException, <br />err, An exception occured in: DiWACTSTransformXML, beanID: transformMediaServerServiceXml1 - <br />DiWACTSTransformXML failed! - Premature end of file.; For more detailed information, see the error log: <br />C:\Program Files\Documentum\CTS\server_install\setupError.log<br />(Apr 20, 2007 8:08:12 AM), Setup.product.install, com.documentum.install.shared.common.error.DiException, <br />err, ; Line#: -1; Column#: -1<br />javax.xml.transform.TransformerException: Premature end of file.<br /> at org.apache.xalan.transformer.TransformerImpl.fatalError(TransformerImpl.java:739)<br /> at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:715)<br /> at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1129)<br /> at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1107)<br /> at com.documentum.install.shared.common.services.xml.DiXMLUtils.transform(DiXMLUtils.java:181)<br /> at <br />com.documentum.install.cts.common.services.xsl.DiCTSXslTransformServices.transform(DiCTSXslTransformServices<br />.java:71)<br /> at <br />com.documentum.install.cts.common.beans.wizard.action.DiWACTSTransformXML.execute(DiWACTSTransformXML.java:9<br />7)<br /> at com.installshield.wizard.StandardWizardListener.execute(Unknown Source)<br /> at com.installshield.wizard.StandardWizardListener.currentBeanChanged(Unknown Source)<br /> at com.installshield.wizard.Wizard$RunThread.run(Unknown Source)<br /> <br />Resolution:<br />Check in the C:\Program Files\Documentum\CTS\config folder, and check if any of the XML files in this folder are empty, 0KB size. If so, take one of the backup files of this xml file (in the same folder with extension .bak.00) and rename it to the original xml files. This should allow you to continue with your installation<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-304314786888989339?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-652335340106341212008-08-08T23:24:00.000-07:002008-08-08T23:25:43.909-07:00Goal<br />How to test the Adlib installation, or test a particular document.<br /> <br />Resolution<br />The steps to test the Adlib installation, or to test a particular document are outlined as follows:<br /> <br />1) Copy the attached files to C:\Temp on the DTS/RPTS server.<br /> <br />2) Open the WSA Sample Application from:<br /> Start > All Programs > Adlib > Exponent Web Service Adaptor > Exponent WSAS Sample<br /> <br />3) Click the 'Submit Job Ticket' tab.<br /> <br />4) Click the Browse button next to the XML Job Ticket field.<br /> <br />5) For a DTS install, select C:\Temp\DTS_jobticket.xml.<br /> For a DTS install, select C:\Temp\RPTS_jobticket.xml.<br /> <br />6) Click 'Validate' to ensure the file is valid (a success message is displayed in the window).<br /> <br />7) Click 'AddJob()' under the Validate button.<br /> <br />The status of the job will be printed in the "Web Service Response" window. Click the 'GetJobSatus()' button to view the progress. A pdf file should be created in C:\Temp if the job is successful.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-65233534010634121?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-83912999263805825512008-08-08T23:11:00.001-07:002008-08-08T23:11:27.873-07:00Q) How to collect audit trails of searches performed by users? <br />Documentum does not capture any audit events for searches performed. However, search statistics and reports can also be used to identify frequently used keywords and tune the search engine to provide accurate results. <br /><br />The statistics can also be used for creating management reports if needed.<br /><br />Design Approach:<br />1. Create a new persistent object (”sp_search_log”) to store Search log information<br />2. Customize the search component’s behaviour class’s onRenderEnd() method to create a new “sp_search_log” object<br />3. Save the object before displaying the JSP<br /><br />Alternate Approaches:<br />1. Use JDBC to capture the information in a database table. Complicated approach involving opening database connections.<br />2. Create custom audit trails to create dm_audittrail objects. I have not yet studied the implications of this. <br /><br />CREATING A NEW TYPE to store Search Logs:<br />CREATE TYPE "sp_search_log"<br />( “r_search_id” ID,<br />“userid” CHAR(10),<br />“userdisplayname” CHAR(200),<br />“deptcode” CHAR(6),<br />“keyword” CHAR(100) REPEATING,<br />“location” CHAR(250) REPEATING,<br />“attrib_namevalue” CHAR(250) REPEATING,<br />“starttimeofsearch” DATE,<br />“endtimeofsearch” DATE,<br />“noofresults” INT,<br />“noofvieweddocs” INT<br />) WITH SUPERTYPE NULL PUBLISH<br /><br />OUTPUT OF DQL > new_object_ID 030004d2800001b9 <br /><br />ALTER TYPE “sp_search_log” DROP_FTINDEX ON “userid”<br />ALTER TYPE “sp_search_log” DROP_FTINDEX ON “userdisplayname”<br />ALTER TYPE “sp_search_log” DROP_FTINDEX ON “deptcode”<br />ALTER TYPE “sp_search_log” DROP_FTINDEX ON “location”<br />ALTER TYPE “sp_search_log” DROP_FTINDEX ON “attrib_namevalue”<br /><br />Use this DQL to drop any fields if needed:<br />ALTER TYPE “sp_search_log” DROP “Field-Name” PUBLISH<br /><br />Use this DQL to add new fields if needed later:<br />ALTER TYPE “sp_search_log” ADD “New-Field-Name” DATE PUBLISH<br />Note:<br />- “attrib_namevalue” CHAR(250) REPEATING will be used to store the params from advanced search in the form date=22/01/2006, etc.<br />- If the user uses a phrase search like “new york”, it can be stored in one keyword. If new york is used without quotes, it will be stored as two keywords<br /><br />SAMPLE JAVA SOURCE CODE FRAGMENTS<br />Note: This code is meant to prove the concept. This may not be the best approach for performance.<br />A better approach could be to store the “starttimeofsearch” in an instance variable then, create & save the<br /><br />sp_search_log object only once after the search operation is completed.<br /><br />public class SearchEx extends com.documentum.dam.search.SearchEx<br />implements IControlListener, IDfQueryListener, Observer,<br />IReturnListener, IDragDropDataProvider, IDragSource, IDropTarget<br />{<br />private boolean m_loggedToDB = false;<br />private boolean m_loggedNoOfResultsToDB = false;<br />private boolean m_isFirstCall = true;public void onInit(ArgumentList args)<br />{<br />System.out.println(”## Inside custom search”);<br />String strQuery = args.get(”query”);<br />System.out.println(”## strQuery: ” + strQuery);<br />super.onInit(args);<br />}<br /><br />public void onRenderEnd()<br />{<br />super.onRenderEnd();<br /><br />if(m_loggedToDB == false && m_isFirstCall==true) {<br />createSearchLogObject();<br />m_isFirstCall = false;<br />}<br /><br />if(m_loggedToDB == true && m_isFirstCall==false && m_loggedNoOfResultsToDB==false) {<br />updateSearchLogObject();<br />}<br />}<br /><br />private void createSearchLogObject(){<br />String objectId = null;<br /><br />IDfSession sess = this.getDfSession();<br /><br />String userid = “Not found”;<br />try {<br />userid = sess.getLoginUserName();<br />System.out.println(”### userid: ” + userid);<br /><br />String queryDesc = getQueryDescription();<br />System.out.println(”### queryDesc: ” + queryDesc);<br /><br />IDfPersistentObject searchLog =<br />(IDfPersistentObject)sess.newObject(”sp_search_log”);<br />searchLog.setString(”userid”, userid);<br />searchLog.setString(”userdisplayname”, userid);<br />//searchLog.setString(”deptcode”, “DEPT_CODE GOES HERE”);<br /><br />IDfTime timeNow = new DfTime();<br />searchLog.setTime(”starttimeofsearch”, timeNow);<br />searchLog.setInt(”noofresults”,-1);<br />setNewValuesForAttribute(”keyword”, queryDesc, ” “, searchLog);<br /><br />String searchLocations = getSearchSources();<br />setNewValuesForAttribute(”location”, searchLocations, “,”, searchLog);<br /><br />searchLog.save();<br /><br />m_NewSearchLogObjectId = searchLog.getObjectId().getId();<br />System.out.println(”************ Saved Search Log ************” + objectId);<br />m_loggedToDB = true;<br />} catch (DfException e) {<br />e.printStackTrace();<br />}<br /><br />}<br /><br />private void updateSearchLogObject(){<br />System.out.println(”### Updating the record”);<br /><br />Datagrid datagrid = (Datagrid)getControl(”doclistgrid”,<br /><br />com.documentum.web.form.control.databound.Datagrid.class);<br />//Get total number of results available from the underlying DataHandler<br />//Note that a value of -1 indicates that the DataHandler does not support results counting.<br />int noOfResults = datagrid.getDataProvider().getResultsCount();<br />System.out.println(”Datagrid noOfResults: ” + noOfResults );<br />if(noOfResults != -1) {<br />IDfSession sess = this.getDfSession();<br /><br />IDfClientX clientx = new DfClientX();<br />try {<br />IDfPersistentObject searchLog = (IDfPersistentObject)sess.getObject(<br />clientx.getId(m_NewSearchLogObjectId));<br /><br />IDfTime timeNow = new DfTime();<br />searchLog.setTime(”endtimeofsearch”, timeNow);<br />searchLog.setInt(”noofresults”,noOfResults);<br /><br />searchLog.save();<br />m_loggedNoOfResultsToDB=true;<br />System.out.println(”************ Updated Search Log ************”);<br />} catch (DfException e) {<br />e.printStackTrace();<br />}<br />}<br /><br />private void setNewValuesForAttribute(String attributeName,<br />String queryString, String delimiter, IDfPersistentObject obj) throws DfException {<br /><br />StringTokenizer st = new StringTokenizer(queryString, delimiter);<br />for (int i = 0; st.hasMoreTokens(); i++) {<br />obj.appendString(attributeName, st.nextToken());<br />}<br />}<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-8391299926380582551?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-27352611214744005772008-08-08T23:06:00.000-07:002008-08-08T23:07:10.204-07:00I recently installed Documentum Thumbnail Server on a Windows box and I had strange problem. The thumbnail server showed status as “Started” in the Windows Services console. But the DAM refused to show any thumbnails. <br /> <br /> To test if the Thumbnail server was running correctly, I used IE to hit this URL: http://localhost:8081/thumbsrv/getThumbnail? <br /> <br />If the thumbnail server was running allright, IE should display a default document icon. Instead I saw the logs of my McAfee Anti-virus. This meant that McAfee was using the port:8081 which is the default port used by Thumbnail server. <br /> <br />Fix: <br /> <br /> Since Thumbnail server uses Tomcat internally, I had to change the port to 8082. <br /> <br />a) Using Notepad, open the server.xml in the D:\Documentum\product\5.3\thumbsrv\container\conf <br />b) Search for “<!– Normal HTTP –>” and in this section for connectors, change the port number <parameter name=”port” value=”<newport>”/> I used 8082 successfully. <br />c) Restart the thumbnail server <br />d) Test using http://localhost:<newport>/thumbsrv/getThumbnail? <br /> <br />Update the configuration of the thumbnail file-store to change the base_url attribute. <br />a) Open Documentum Administrator (DA), <br />b) Look for the file-store - “thumbnail_store_01″ <br />c) View properties and update the base url. <br />d) Restart the docbase <br />e) Open DAM and test if thumbnails are being displayed correctly <br /><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-2735261121474400577?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-38878403635872052362008-08-08T22:49:00.000-07:002008-08-08T22:59:59.400-07:00Backup <br />Secondary copy of information <br />Used for recovery operations <br />Improves availability by enabling application to be restored to a specific point in time <br />Typically short-term (weeks or months) <br />Data overwritten on periodic basis (monthly) <br />Not useful for compliance <br /><br />Archive<br />Primary copy of information<br />Available for information retrieval<br />Adds operational efficiencies by moving fixed/unstructured data out of the operational environment <br />Typically long-term(months,years,decades)<br />Data retained for analysis or compliance<br />Useful for compliance<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3887840363587205236?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-57741653663414180002008-08-08T22:44:00.000-07:002008-08-08T22:45:10.810-07:00Registered tables are the tables that are present database which are registered in Documentum, so that it can be accessed using DQL. Basically Registered tables are used when the application needs to access data from the RDBMS within the Documentum. This can be either a Table or a View. The Scenarios where I mostly used registered tables are for providing value assistance for Object attributes. I am not getting into too much of details about Value Assistance here, Value assistance is a list of values that a client program (such as Webtop or a Custom WDK Application) displays at runtime for an object attribute. A user can select a value from this list (or, if allowed, add a new one to it). You can set the Value assistance for an Attribute using DAB (Documentum Application Builder).<br /><br />As I mentioned above uou can register a Table or a view as a Registered Table, The Registered tables are stored as dm_registered objects in repositories. This extends dm_sysobject. And the r_object_id of this type always starts with 19. The following table lists the attributes of dm_registered <br /><br />Name Info Description <br />column_count Integer - Single Number of columns in the table. <br />column_datatype string(64) - Repeating List of the datatypes of the columns. <br />column_length. integer R Lengths of the columns that have a string data type <br />column_name. string(64) - Repeating List of the names of the columns in the table <br />group_table_permit integer - Single Defines the RDBMS table permit level assigned to the registered table’s group. <br />is_key. Boolean Repeating Indicates if an index is built on the column <br />owner_table_permit integer - Single Defines the RDBMS table permit level assigned to the registered table’s owner <br />synonym_for string(254) - Repeating Name of the table in the underlying RDBMS (can be an Oracle table synonym, or an MS SQL Server or Sybase table alias) <br />table_name string(64) Single Name of the table. <br />table_owner string(64) Single Name of the owner of the RDBMS table (the person who created the RDBMS table). <br />world_table_permit integer - Single Defines the RDBMS table permit level assigned to the world <br /><br /> You should either own the table or have super user privileges to register a table. And since this object is linked with /system cabinet you should have write permission on /system cabinet. This is applicable only if the folder security is enabled in Repository <br /><br />You cannot version a dm_registered object. And also the changes made to the table are not automatically updated in dm_registered object. So if any changes has been made to the structure of the table or view you should unregister it first and register the table again with changes. <br /><br />How to Register a Table?<br /> Use the following DQL to register a table. REGISTER TABLE [owner_name.]table_name (column_def {,column_def}) [[WITH] KEY (column_list)][SYNONYM [FOR] ‘table_identification‘] This DQL will return the r_object_id of the newly created dm_registered object. In this owner_name is the name of the table owner. table_name is the name of the RDBMS table. column_def defines the columns in the registered table. <br /><br />column_def arguments should have following syntax column_name datatype [(length)] the valid values for types are float, double, integer, int, char, character, string, date, time. <br /><br />Length should be specified for character, char, or string data type.<br /><br /> column_list Identifies the columns in the table on which indexes have been built. column_list is usually separated with commas. table_ identification is the name of the table in the Database Example: <br /><br />REGISTER TABLE “hr.users” (”first_name” CHAR(30), last_name (char 40), “emp_id” INT)KEY (”emp_id”)<br /><br /> <br /><br />Granting Rights <br /> You need to give the permission to the users to access the registered tables. The values for various permission levels are as follows 0 (None): No access 1 (Select): The user can retrieve data from the registered table 2 (Update): The user can update existing data in the registered table4 (Insert): The user can insert new data into the registered table8 (Delete): The user can delete rows from the registered table If a user wants update and insert permissions the value should be 2+4 = 6 , The repository owner also should have the same level of permission in the underlying database to grand those permission to those users. Granting Rights full permission to users in the above example <br /><br />update dm_registered object set world_table_permit = 15 where object_name = ‘users’; <br /><br />update dm_registered object set owner_table_permit = 15 where object_name = ‘users’; <br /><br />update dm_registered object set group_table_permit = 15 where object_name = ‘users’;<br /><br /> <br /><br /><br />How to Unregister a Table? <br /><br />Use the following DQL to Unregister a Table. <br /><br /> UNREGISTER [TABLE] [owner_name.]table_name In this owner_name is the name of the table owner. table_name is the name of the RDBMS table. You should be the owner of table or super user to do this <br /><br /><br />Accessing Data from Registered Table <br /><br />Just like in RDBMS you can access registered table using the following syntax <br /><br /> Select [ATTRIBUTES] from dm_dbo.[REGISTERED_TABLE_NAME] where [CLAUSE] <br /><br />The Operations such as update/ delete also has the same RDBMS syntax that’s used for a ordinary SQL, Only difference is prefixing dm_dbo to the table name <br /><br />Example: <br /><br />Select first_name, last_name, emp_id from dm_dbo.users ;<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-5774165366341418000?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-5115071447305825312008-08-08T22:22:00.000-07:002008-08-08T22:25:15.871-07:00Sysadmin<br /><br /> Create, alter, and drop users and groups <br /> Create, modify, and delete system-level ACLs <br /> Grant and revoke Create Type, Create Cabinet, and Create Group privileges <br /> Create types, cabinets, and printers <br /> Manipulate workflows or work items, regardless of ownership <br /> Manage any object’s lifecycle <br /> Set the a_full_text attribute <br /> <br />The Sysadmin privilege does not override object-level permissions<br /><br />Super User<br /><br /> Perform all the functions of a user with Sysadmin privileges <br /> Unlock objects in the repository <br /> Modify or drop another user’s user-defined object type <br /> Create subtypes that have no supertype <br /> Register and unregister another user’s tables <br /> Select from any underlying RDBMS table regardless of whether it is registered or not <br /> Modify or remove another user’s groups or private ACLs <br /> Create, modify, or remove system ACLs <br /> Grant and revoke Superuser and Sysadmin privileges <br /> Grant and revoke extended privileges <br /> View audit trail entries<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-511507144730582531?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-18420411643385306612008-08-08T22:19:00.000-07:002008-08-08T22:20:32.324-07:001. Sharepoint 2007 is tightly integrated with Office 2007. Documentum has some light integration with Office through Webtop Application Connectors. Documentum has stronger integration with other authoring applications including Dreamweaver, QuarkXPress, and Adobe InDesign. <br />2. Sharepoint provides various mechanisms to access and modify content when offline (eg Outlook, Access, etc). Documentum only supports offline editing if you install Documentum Desktop application. <br />3. Sharepoint 2007 supports rights management with Office 2007 natively. Documentum requires you to install Information Rights Manager to have this feature. <br />4. Both Documentum and Sharepoint provide the ability to create custom object types. However, Sharepoint’s object model does not seem to support object inheritance. <br />5. Lifecycle features (eg applying actions, defining entry criteria, applying lifecycle to multiple documents, etc) is more extensive in Documentum than in Sharepoint. <br />6. Documentum security model is more extensive than Sharepoint. Documentum has extended permissions that allow users to perform specific functions (eg change ownership, change state, change permissions, etc). <br />7. All objects in Documentum are secured using the security model. In Sharepoint only certain objects can be secured (eg web site, list, folders, documents, etc). <br />8. Content can be only published to Sharepoint site; however, if content needs to publish outside of MOSS repository, this requires custom coding. Content can be published to any website using Documentum Site Caching and Site Delivery Services. Documentum also has portlets for various portal vendors that allow those portals to access content that is stored in Documentum repository. <br />9. The obvious - Sharepoint only runs on Windows using Microsoft SQL Server. If you are enterprise standard is UNIX/Linux or Oracle/DB2, then Sharepoint is not a valid option. Documentum is OS and database agnostic. Documentum is supported on various OS and database configurations. <br />10. The next obvious – Sharepoint is built on ASP.NET; thus, customizations are done via .NET framework. Documentum is built on DFC, which is built on Java. You should consider the development and support skills of your staff when considering which system to choose. <br />11. Content Storage - Sharepoint stores content within the SQL Server database. This allows Sharepoint to utilize SQL Server native search capabilities. This also means that backup of content is solely dependent on backing up of the database. Documentum stores content on a file storage system and content metadata in any database. This architecture allows for multi-server single docbase configuration. Since content is stored on file system, you can also create a mix storage architecture composed of SAN, NAS, RAID, tape, etc<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1842041164338530661?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-56953175681878900732008-03-23T14:08:00.000-07:002008-03-23T14:22:32.243-07:00Why do I have lots of ACLs in my docbase and how do I remove them?<br /><br /><br />If you believe that you have too many ACLs and they are causing the problem, please read this Support Note.<br /><br />Background:<br />Internal ACL vs Named ACL:<br />- A named ACL is an ACL that was created by an administrator or a user in the docbase. The attribute owner_name of this ACL will show a user name. For example, owner_name: dmadmin<br />- Internal ACLs are automatically generated by the docbase, and they have a computer generated name, such as dm_<hexadecimal>. For example dm_4500123480000101<br /><br /><br />What are the implications of having too many ACLs?<br />A large number of ACLs in your docbase is difficult maintain. Also, having too many internal ACLs may reveal an incorrect set up: If your business process is correctly implemented and set up, there should be very few occasions when internal ACLs are being generated.<br /><br /><br />How are Internal ACLs created? ……………….<br />Every dm_sysobject object in the docbase has an ACL assigned to it. Depending on the ACL inheritance of the serverconfig object, you can set how new objects get their ACL.<br /><br />There are 4 ways where you can set an ACL to a particular object:<br />1. user<br />If your serverconfig is set to use "user", then every time the user creates a new object, this object will get the same ACL values as the user's default ACL.<br /><br />2. folder<br />In a "folder" mode, the object gets its ACL from the folder where it is created.<br /><br />3. type<br />Using "type" mode, default ACL of the type is being used to set the values of the newly created object's ACL.<br /><br />4. permission set templates<br />You can use permission set template to set the ACL of an object. The requirement for permission set template is that the Server needs to be able to resolve any alias sets that might be related to the Permission Set Template. See Documentum eContent Server Object Reference Manual version 4.2 under (Alias Scope) page 1-26.<br /><br /><br />How do I find out the number of ACLs in my docbase?<br />1. Total ACLs:<br />DQL> select count(*) as Total_Number_of_ACLs from dm_acl<br /><br />2. For Named ACLs created by users or the system administrator, you can run:<br />DQL> select count(*) as Number_of_Named_ACLs from dm_acl where r_is_internal=0 and acl_class = 0<br /><br />3. For Template ACLs, you can run:<br />DQL> select count(*) as Number_of_Template_ACLs from dm_acl where r_is_internal=0 and acl_class <> 0<br /><br />4. For Internal ACLs, you can run:<br />DQL> select count(*) as Number_of_Internal_ACLs from dm_acl where r_is_internal=1 and acl_class = 0<br /><br />5. For Internal ACLs created from Template ACLs, you can run:<br />DQL> select count(*) as Number_of_Internal_ACLs_From_Template from dm_acl where r_is_internal=1 and acl_class <> 0<br /><br />You should have:<br />#1 = #2 + #3 + #4 + #5<br /><br />There is a good chance that the number of Internal ACLs (query #4 above) is high and represents more than 95% of the total number of ACLs in the docbase (query #1). Those are the ACLs that we can get rid of. Also, once your docbase is properly set up, no new Internal ACLs should be created any more.<br /><br />For more information on those topics, please refer to the eContent Server documentation.<br /><br />***********### IMPORTANT ###***********<br />Before going further in the resolution, we assume that you understand:<br />- DQL queries<br />- ACL model in Docbase<br />***************************************<br /><br /><br />==[ Step A ]=============================<br />Find out which Default ACL Mode the Docbase is currently using, then identify the folders / type / users which are using an Internal ACl and change it to a Named ACL so that the docbase stops generating Internal ACLs.<br /><br />A.1. First, run the following query to find out what Default ACL the docbase is using:<br />DQL> select default_acl as Default_ACL_Mode from dm_server_config where object_name='<your>'<br /><br />A.2. The result should be 1, 2 or 3 but regardless of the result, we suggest that you go through all the steps A.2.1, A.2.2 and A.2.3. The reason is that you want to remove all references to Internal ACls that folders or types or users may have.<br /><br />A.2.1 If Default ACL mode is 1 (Folder):<br />Retrieve all the folder names which have an Internal ACL:<br />DQL> select r_object_id, acl_name, acl_domain, object_name from dm_folder where acl_name like 'dm_45%'<br /><br />Update the ACLs of all folders that have Internal ACLs to your Named ACL.<br />DQL> update dm_folder objects set acl_name = '<your>', set acl_domain = '<your>' where acl_name like 'dm_45%'<br /><br />Note: 'your docbase name' is the name of the docbase and 'your system ACL' is the name of a system ACL that you want to use as the default ACL. A system ACL is a Named ACL owned by the system administrator which can be shared across users.<br /><br />Note: You need to update the acl_domain also if you want to update the acl of an object.<br /><br />Note: We strongly recommend that you use a Named ACL that is owned by System. The reason is because you want to easily share this Named ACL with other users.<br /><br /><br />A.2.2 If Default ACL mode is 2 (Type):<br />Retrieve the default ACL and the owner name of the ACL for object types if the types have an Internal ACL associated with them:<br />DQL> select r_type_name, acl_name, acl_domain from dmi_type_info where acl_name like 'dm_45%' or acl_name = ' '<br /><br />Update the ACLs of all types that using an Internal ACL or are don't have an ACL assigned and are subtypes of dm_sysobject by using Documentum Administrator interface. No DQL query is available for this task since dmi_type_info is an internal type.<br /><br /><br />A.2.3 - If Default ACL mode is 3 (User):<br />Retrieve all users (and groups) that are using an Internal ACL:<br />DQL> select r_object_id, user_name, acl_name from dm_user where acl_name like 'dm_45%'<br /><br />Assign a named ACL to those users (and groups):<br />DQL> update dm_user objects set acl_name = '<your>', set acl_domain = '<your>' where acl_name like 'dm_45%'<br /><br />Note: 'your docbase name' is the name of the docbase and 'your system ACL' is the name of a system ACL that you want to use as the default ACL. A system ACL is a Named ACL owned by the system administrator which can be shared across users.<br /><br />Note: Make sure you update the acl_domain together with the acl_name. If the acl that you are assigning is not part of the current acl_domain, the server will return an error.<br /><br />Note: We strongly recommend that you use a Named ACL that is owned by System acl_domain=<your> rather than acl_domain=<user><br /><br />The reason is because you want to easily share this Named ACL with other users and this is only possible if the ACL is owned by System.<br /><br />===[ Step B ]=======================<br />At this point, you docbase should not generate new Internal ACLs. However, existing objects may be using an Internal ACL. This step helps you indentify those objects and change the Internal ACL to a Named ACL. This step is required before attempting to remove Internal ACLs.<br /><br />B.1 - Retrieve all objects (content and folders) across the docbase that are using an Internal ACL:<br />DQL> select count(*) from dm_sysobject (all) where acl_name like 'dm_45%' and acl_name not like 'dm_45%\_8%' ESCAPE '\'<br /><br />If you need to review those objects one by one:<br />DQL> select r_object_id, object_name, acl_name, acl_domain from dm_sysobject (all) where acl_name like 'dm_45%' and acl_name not like 'dm_45%\_8%' ESCAPE '\'<br /><br />B.2 - Assign your Named ACL to all objects (content and folders) across the docbase that have Internal ACL:<br />DQL> update dm_sysobject (all) objects set acl_name='<your>', set acl_domain='<your>' where acl_name like 'dm_45%' and acl_name not like 'dm_45%\_8%' ESCAPE '\' and r_lock_owner is NULLSTRING<br /><br />Note: 'your docbase name' is the name of the docbase and 'your system ACL' is the name of a system ACL that you want to use as the default ACL. A system ACL is a Named ACL owned by the system administrator which can be shared across users.<br /><br />Note: Only the contents that are not checked out will be updated. You may want to run this query periodically until no contents get returned from the queries in B.1<br /><br />Note: You can refine the query so that only a subset of those objects get a Named ACL - per folder or creation date for instance.<br /><br />Note: Make sure you update the acl_domain together with the acl_name. If the acl that you are assigning is not part of the current acl_domain, the server will return an error.<br /><br />Note: We strongly recommend that you use a Named ACL that is owned by System (acl_domain=<your> rather than acl_domain=<user>). The reason is because you want to easily share this Named ACL with other users and this is only possible if the ACL is owned by System.<br /><br />Note: This query may take quite some time to run. In fact, the update statement may update so many objects at the same time that your database may run out of TEMP tablespace causing the query to fail. You may want to modify the query to modify a limited number of objects at the same time - by restricting per folder or creation date.<br /><br />Note: You may not be able to update non-CURRENT objects if they are immutable. If this is your case, the query will return error DM_SYSOBJECT_E_CANT_SAVE_IMMUTABLE. In order to resolve this issue, you can take the '(all)' keyword out of the update statement so that only CURRENT objects will be updated. This may leave quite a significant number of Internal ACLs left in the docbase that are used by non-CURRENT objects.<br /><br /><br />===[ Step C ]===============================<br />Now that no new Internal ACL is created and most of the objects in the docbase are assigned a Named ACL - the remaining Internal Acls are those created from Template ACLs. Your docbase is now hosting many orphan ACLs. It is time to clean them up!<br /><br />Job dm_clean can delete orphan ACLs from the docbase. While running job dm_clean (from Documentum Administrator or you can schedule the job to run periodically), make sure that argument '-clean_acl' is set to TRUE.<br /><br />Before running the job, you can find out how many ACL the job will clean after going through step A and B:<br />DQL> select count(*) as Number_of_Internal_ACLs from dm_acl where r_is_internal=1 and acl_class = 0<br /><br />To get more details about those ACLs:<br />DQL> select * from dm_acl where r_is_internal=1 and acl_class = 0<br /><br />If you agree with the result, run dm_clean and go to Step D.<br /><br />For more information, Refer to Documentum eContent Server Administrator's Guide Chapter 10 "Removing Unreferenced Internal ACLs".<br /><br /><br />===[ Step D ]===========================<br />Restart the docbase. Active sessions may still be running with no default ACLs and will keep generating internal ACLs.<br /><br />After running dm_clean and restarting the docbase, you can verify if all Internal ACLs are gone by re-running the same queries as in Step C:<br />DQL> select count(*) as Number_of_Internal_ACLs from dm_acl where r_is_internal=1 and acl_class = 0<br /><br />To get more details about those ACLs:<br />DQL> select * from dm_acl where r_is_internal=1 and acl_class = 0<br /><br />You can identify the remaining documents that are still using a Internal ACL:<br />DQL> select r_object_id, object_name, title, acl_name, owner_name, r_version_label from dm_sysobject (all) where acl_name in (select object_name from dm_acl where object_name like 'dm_45%' and object_name not like 'dm_45%\_8%' ESCAPE '\') order by 1<br /><br />For more information on how ACL are assigned in WebPublisher, please refer to Support Note 15997<br /><br /><br /><a></a><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-5695317568187890073?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com1tag:blogger.com,1999:blog-7871201595809525198.post-2282157437043145482008-03-23T14:06:00.000-07:002008-03-23T14:07:42.647-07:00<em>Sample Scenario: </em><br />You would like to configure a single lifecycle to assign ACLs to documents based on the line of business using the lifecycle. For example, Company A uses this lifecycle so that stage 1 attaches ACL 1-a to the document, but Company B uses the exact same lifecycle so that stage 1 attaches ACL 1-b to a document. <br /><br />1) Create a docapp <br /><br />2) Create a new alias set, say 'DLC_Alias' <br />- Create some new permission set aliases in this new 'DLC_Alias' set. <br />-Citibank_ACL <br />-Chase_ACL <br />-Manhattan_ACL <br />Resolve the aliases to the desired values. <br /><br />3) Create a lifecycle, add X states. <br /><br />4) Add your new DLC_Alias set as a default alias set to your lifecycle. <br /><br />5) Edit some of the states of the lifecycle, <br />Add a new action <br />- Select Set Permission Set <br />- Specify Permission Set Alias <br />At this point, when you select this option, you should then see the aliases 'Citibank_ACL, Chase_ACL, Manhattan_ACL' <br />You can specify this to the desired alias. <br /><br />6) Check-in the Lifecycle. <br /><br />When someone goes to apply the lifecycle, in Desktop and in Webtop, they should see the lifecycle as well as a list of available alias sets that can be used. <br /><br />They select the desired alias set and apply. <br /><br />As the document goes thru the lifecycle, various Permission Sets or "ACLs" will be applied to the document while in the lifecycle.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-228215743704314548?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-282901265482155772008-03-23T12:53:00.000-07:002008-03-23T13:25:56.017-07:00<strong>To disable the folderselect buttons in webtop</strong><br /><br />Modify the below tag in Fileselection.jsp file<br />dmf:fileselectorapplet width="500" name="fileselector" folderselectmode="tree" folderselect="'false'" height="250"<br />dmf:fileselectorapplet<br />?xml:namespace prefix = dmf<br />dmf:fileselectorapplet width="500" name="fileselector" folderselectmode="tree" folderselect="'false'" height="250"<br />dmf:fileselectorapplet<br /><br /><?xml:namespace prefix = dmf /><dmf:fileselectorapplet width="500" name="fileselector" folderselectmode="tree" folderselect="'false'" height="250"><br /></dmf:fileselectorapplet><dmf:fileselectorapplet width="500" name="fileselector" folderselectmode="tree" folderselect="'false'" height="250"></dmf:fileselectorapplet><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-28290126548215577?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-75804136474756545762008-03-23T12:44:00.001-07:002008-03-23T12:52:39.682-07:00Engineering Release Details: Webtop_53SP5_hotfix_152572.txt<br />============================<br />Product and Version this ER Works With: Webtop 5.3 SP5<br />Bug Number(s): 152572<br />Bug Abstract: A large cookie causes UCF operations to fail as WDK does not pass cookie info correctly to UCF. UCF fails if customer visits one of their web application first then vist the Webtop application, as their web application puts additional large cookies into the session. If they visit webtop only, UCF works without a problem.<br />Date: 02/22/2008<br /><br />Additional Required Engineering Releases and Patches:<br />=====================================================<br />None<br /><br />Installation Procedure:<br />=======================<br />1. Stop application server<br />2. Backup the following files to be able to revert back to the original installed product:<br /><br /><doc>\WEB-INF\classes\com\documentum\web\applet\ucfinvoker\LaunchRuntimeDelegate.class<br /><doc>\wdk\system\ucfinit.cab<br /><doc>\wdk\system\ucfinit.jar<br /><br />Where <doc>is the root directory of the exploded Webtop web application. For example, on Tomcat this typically is <catalina>\webapps\webtop<br />3. Unzip the supplied zip file into <doc>. This will place the following files in the target directory<br /><doc>\WEB-INF\classes\com\documentum\web\applet\ucfinvoker\LaunchRuntimeDelegate.class<br /><doc>\wdk\system\ucfinit.cab<br /><doc>\wdk\system\ucfinit.jar<br />4. Clean the all cache in 'Windows start menu -> Settings -> Control panel -> Java -> Delete Files'.<br />5. Restart the Application Server and test the fix.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-7580413647475654576?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-34296099123398155922008-03-23T12:32:00.000-07:002008-03-23T12:48:46.074-07:00By default, the clean up of the viewed files folder and registry settings will only occur every seven days when UCF is used as the content transfer mechanism.<br /><br />From Webtop 5.3 SP2 onwards it is possible to configure the interval by adding the house.keeping.interval configuration option to the ucf.client.config.xml<br />e.g.<br /><br />option name="house.keeping.interval"<br />value 1 value<br />option<br /><br /><option name="house.keeping.interval"><br /><value>1</value><br /></option><br /><br />With this value set you should find that the viewed files folder is cleaned of files older than the specified value when housekeeping is invoked. However we do not guarantee that that document will be deleted at exactly the time specified in this configuration parameter because UCF is not service like process, it starts only when client requests content transfer and ends shortly after that. Also when a view operation is performed against a file that exist in the viewed file folder housekeeping does not occur. The reason that the house keeping is only started when you view a file that has not been viewed before is a result of performance considerations made during the design of the functionality.<br /><br />Checkin and Checkout operations will also invoke the housekeeping.<br /><br />As the house.keeping.interval option is not part of the standard set of ucf client side configuration options you can actually add "house.keeping.interval" to the ucf.installer.config.xml file within the webapp/wdk/contentxfer folder on the application server in order to have the setting propagated to the client side configuration files by following the advice provided in support note 75075<br /><br />Note<br />You cannot set housekeeping interval to "0" because in this case UCF would have to delete document as client viewed it.<br /><br />see UCF Housekeeping info on developer web site http://developer.emc.com/developer/Articles/UCFHouseKeeping.htm<br /><br />wdk\contentXfer\ucf.installer.config.xml<br />Configuring the above XML, to check out to home directory looks good from my local machine running tomcat and webtop.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3429609912339815592?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-33530219646381353972008-03-23T12:22:00.000-07:002008-03-23T12:26:44.979-07:00In 5.3 webtop/da frequently getting the error "Error - Failed to retrieve content from ACS/BOCS server(s). The ACS/BOCS server(s) may be down or your machine may not be able to reach the server(s) due to network connectivity or configuration issues"<br />If you encounter this, try the below resolution. <br /><br />Symptoms Error - Failed to retrieve content from ACS/BOCS server(s). The ACS/BOCS server(s) may be down or your machine may not be able to reach the server(s) due to network connectivity or configuration issues<br /><br />com.documentum.ucf.common.UCFException: All remote hosts failed<br /><br />Cause<br />Content transfer is trying to use ACS instead of virtual link.<br /><br />Resolution <br />I finally found the failure. In the dmcl_QA that corresponds to the bug.The getservermap api call with the mn_acs_map parameter.The bug # is 129741. I am enclosing the hotfix and am adding it to the case. If you wish, you can disable the ACS instead.<br /><br />If you are not using ACS (used in Distributed Env) you can disable the ACS feature from your installation.Open the app.xml, on windows it's located under the following directory:C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps\"<da,><acs>, change <enable> to <false?, restart your app serverand you shouldn't have the issue. <br />DO this for all of your wdks.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-3353021964638135397?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-10074068751128077252008-03-22T18:50:00.000-07:002008-03-22T19:13:24.504-07:00<u>Documentum DA 5.3 Sp2: Audit Trail- Ref No : 114997 </u><br /><u><br /></u>- when choosing events for audit trail, the default 'show items' is ‘10’ and if you change it to 50/100, the results are displayed but the vertical scroll bar is missing and we cannot select items. This is a bug and it is fixed in 6.0<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1007406875112807725?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0tag:blogger.com,1999:blog-7871201595809525198.post-19458750051754408812008-03-21T13:30:00.000-07:002008-03-22T18:48:14.298-07:00Whenever a document is deleted, only the document's metadata is deleted. The content itself (i.e. the object pointed to by the dmr_content object) remains in the content storage area until the IAPI script generated by the dmclean utility is run.Assuming that the dmclean utility has not been run, it is still possible to recover the object's content file.<br /><br />Note: The document's attributes cannot be recovered without going back to a database backup. Below is an outline of a strategy which can be used to do this recovery.<br /><br />Initially, you need to gather some data on the document that you want to recover such as:<br />In DQL: select * from dm_audittrail where event_name='dm_destroy'<br />a) What was the name of the client machine where the file was last checked in? This is the set_client attribute.<br />b) What was the date/time of the last checkin? This is the set_time attribute.<br />c) What format was the document? This is the full_format attribute.<br />d) What was the name of the object? This is the object_name attribute.<br />For E.g : recoverddoc<br />With this information, the following query can be issued<br />IDQL: select r_object_id from dmr_content where any parent_id is null and set_client = and full_format = and set_time > DATE('')<br /><br />This will retrieve a set of r_object_id's that correspond to content objects that have been deleted and meet your criteria. Once you have found the appropriate r_object_id of the deleted document, you are ready to find the file.<br />Using IAPI, execute the following commands:<br />API> apply,c,<r_object_id>,GET_PATH<br />API> next,c,q0<br />API> get,c,q0,result<br />This returns the file system path to the object.<br />For example: 'c:\Documentum\data\happydays\content_storage_01\00003039\80\00\00\e6.doc'<br /><br />Using DQL:<br />create "dm_document" OBJECT SET "object_name"='recoverddoc',SET "authors"='chandu', SETFILE 'c:\Documentum\data\happydays\content_storage_01\00003039\80\00\00\e6.doc' with content_format='msw8'<br /><br />Alternatively using API’sNow that you have the path of the content file, you can create a new object with this content by doing the following:<br />API> create,c,dm_document 0900006580005a65<br />API> set,c,,object_name<br />SET> Restored Document<br />OK<br />API> setfile,c,,'c:\Documentum\data\happydays\content_storage_01\00003039\80\00\00\e6.doc'<br />OK<br />API> link,c,,/Temp<br />OK<br />API> save,c,<br />Now look for a document named "Restored Document" in the /Temp cabinet. If it is there, then you have successfully recovered the deleted document!<br /><br />Note:<br />- Add an event dm_destroy in the audit trails<br />- Stop dm_clean and dm_DMFilescan jobs which will instead clear contents of orphaned objects on scheduled basis<br />- select * from dm_audittrail where event_name='dm_destroy'<br />o this will give the details like ‘who,when,where deleted, object name’<br />- select * from dmr_content where any parent_id is null and set_time >= DATE(Today)<br />o this has the list of all the deleted documents on that day<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7871201595809525198-1945875005175440881?l=batlanki.blogspot.com' alt='' /></div>Batlankihttp://www.blogger.com/profile/01689247269588386393noreply@blogger.com0