Saturday, February 28, 2015

UCF content transfer operational issues for new JRE release


Oracle released Java Runtime Environment (JRE) 1.7u51 and the security baseline was also upgraded from the earlier baseline of JRE 1.7u45. This internal Java property is set automatically and may affect Documentum Web Development Kit (WDK) based clients running on browsers using JRE versions 1.7u45 or1.7u25. Customers may experience issues with applets, such as content transfer and file selection applets, or may see security warning messages.   

Issue :
Unified Client Facilities (UCF) content transfer and file selection operational issues may occur due to LiveConnect changes in JRE 1.7u51 that block UCF applet calls in Documentum WDK-based clients running JRE version 1.7u45/1.7.u25.

Customers running JRE 1.7u21 or earlier supported versions will not experience operational issues, but may see an upgrade popup message prompting them to upgrade the JRE version to 1.7u51 and a Security Warning message for UCF and file selector applets. 

Environment :
Documentum WDK based browser clients:

Workaround:
The customer Documentum/Network Administrator should perform the steps below.

1. Go to: C:\Users\{localUser.Name}\AppData\LocalLow\Sun\Java\Deployment.
Edit the deployment.properties file. This is a default location in Windows 7.
2. Back up the deployment.properties file before making the following changes.

JRE 1.7u45:
1. Comment out all timestamp-related properties. 

2. Add these entries for JRE update 1.7u45 in the deployment.properties file:
    a. deployment.expiration.check.enabled=false
    b. deployment.expiration.decision.suppression.10.45.2=true
    c. deployment.expiration.decision.10.45.2=later.

JRE 1.7u25:
Add these entries for JRE update 1.7u25 in the deployment.properties file:
    a. deployment.expiration.check.enabled=false
    b. deployment.expiration.decision.suppression.10.25.2=true
   c. deployment.expiration.decision.10.25.2=later.

Manual Interpretation Documentum r_object_id



  1. Execute the below DQL query  to get ( data_ticket ,file_format, file_path, docbase_id )

select data_ticket, dos_extension, r_docbase_id, file_system_path from dmr_content c, dm_format f, dm_filestore fs, dm_location l, dm_docbase_config dc where any c.parent_id = '09XXXXXXXXXXXXXX' and f.r_object_id = c.format and fs.r_object_id = c.storage_id and l.object_name = fs.root

data_ticket          dos_extension     r_docbase_id     file_system_path
 -2147483646      ppt                      55555                 /NFS/data/EMC_LIFE/content_storage_01


  1. Data ticket convertion formula
1)      Data ticket +  2’s complement of 32  ►► -2147483646 + 4294967296 = 2147483650
2)      Convert result of step 1 as HEX    ►► converting 2147483650 to hex = 80000002
3)      Split each 2 digit as the HEX value (step 2 answer) ►► 80\00\00\02
4)      Convert the      r_docbase_id (99999) to hex  ►►000186F9  ( add zero before , the digit count should be 8 )

  1. Assemble the values:

Step 1 ,file_system_path + step 2 ,4 value + step 2, 3 value +Step1 dos_extension

/NFS/data/EMC_LIFE/content_storage_01/000186F9/80/00/00/02.ppt  


Content server API

  1. Get file path API (storage location)
API>getpath,c,09XXXXXXXXXXXXXX
...
/NFS/data/EMC_LIFE/content_storage_01/000186F9/000184b9/80/00/00/02.ppt
API>
  1. Get file API ( get the content file in your local  drive)

API>getfile,c, 09XXXXXXXXXXXXXX
...
/NFS/documentum/local/process9122184072070732161.tmp/208/060184b980000100.ppt
API>


Thursday, February 26, 2015

Documentum - API Command for Tracing


If you want to set up tracing for longer than just the current session, you can configure tracing for all future sessions by issuing the “Apply” API command with the “SET_OPTIONS” parameter:
               
apply,c,NULL,SET_OPTIONS,OPTION,S,<Trace option>,VALUE,B,<enable/disable option>

<Trace option>

Trace Options (4th parameter of the apply with SET_OPTIONS command):
  • debug – Configures tracing for session debug messages during shutdown, launches, forks, and change checks
  • docbroker_trace – Configures docbroker tracing
  • lock_trace – Configures tracing for Windows NT locking
  • net_ip_addr – Configures tracing of IP addresses used by the client
    and server for authentication
  • nettrace – Configures tracing for remote procedure calls (including calls to Netwise). Shows the connection ID, client host address and host name
  • sqltrace – Configures tracing of RDBMS SQL commands (during future sessions)
  • trace_authentication – Configures tracing of authentication

<enable/disable option>
·     T (On) enable tracing
·     F (Off) disable tracing

        

Example API command to turn on SQL tracing:


               
apply,c,NULL,SET_OPTIONS,OPTION,S,sqltrace,VALUE,B,T

Sample error logs

SELECT * FROM dmi_dd_type_info_rv UE_ , dmi_dd_type_info_sv TE_  WHERE
 (TE_.R_OBJECT_ID=:handle AND TE_.R_OBJECT_ID=UE_.R_OBJECT_ID) ORDER BY
 UE_.R_OBJECT_ID,UE_.I_POSITION
:handle = 690f481d80000d0d
 SELECT J_.I_TYPE FROM bf_demo.dmi_object_type J_ WHERE J_.R_OBJECT_ID=
:handle
:handle = 090f481d80002980
select user_name, message, priority, oneshot, sen/articles/il, event, is_audittrail,
 registered_id from dmi_registry_s where (event = 'dm_setfile' or event = 'all')
 and registered_id ='090f481d80002980'
select s.group_name from dm_group_s s where s.group_name = :p0
:p0 = docu