nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changes in TBO not reflecting in DEV environment

rajesh.ghosh

HI All,

we have arecent Customisation work where we had to change a code piece, the basic Idea is wheneever a new training Doc is created in Trainjng/trainng material folder the Doc should be picked up by TBO(actual picking up work s done by SGS JOB-which I have not modified) and linked to training/signature object/publish folder(earlier it was trainn):

I have changed the Jar inside system/module/tbo/training_state folder, and deployed it , but the change is not been seen,

Also when I am creating new Training DOC in that folder, I am not able to see rendition, is this the reason for the problem I stated?

Find more posts tagged with

Comments

DCTM_Guru

Have you tried updating your module? Maybe the module has your old jars cached.

rajesh.ghosh

HI Jonny,

Thanks for reply can you elaborate how to do so?

DCTM_Guru

Read DFC Development guide.

Geks

if you apps places into dmServer

then:

stop dm-services

clear C:\documentum\caches

start dm-services

else:

clear C:\documentum\caches

rajesh.ghosh

@gek I dont really understand you as I have deployed the code in Dev server, Why will my catches be in C;//

Geks

your app - it is webtop?

OS in DEV server - it is Windows?

Jeremy Saumen

@rajesh.ghosh

Because it's the way TBO works with Documentum Content Server (>=5.3 i think) : the module is downloaded from the content server to the client application which needs it and dynamically added to the classloader to use it.

If the app your are using is faulty (using an old version of the module), try to find the dfc.properties your app is using and find the property dfc.cache.dir, the value should be a path to the cache folder your application is using.

If dfc.cache.dir doesn't exists, try to find the property dfc.data.dir, the value should be the path to documentum data directory, inside it you should find a folder name cache.

If dfc.data.dir doesn't exists then the default directory is used (usually a subdirectory of the directory from which the JVM is launched named documentum) : try to specify at least the dfc.data.dir, it's easier to maintain when you know where to search.

When you have found the cache directory, stop your application, delete the cache directory and restart your application : the directory is going to be recreated and your module will be downloaded when necessary.

If it doesn't work, try to reinstall your module using composer and retry the whole operation.