Loggingconfigurator screws up log4j logging

Hello there,

We use Documentum 6.5SP2 as a ECM system for our J2EE project (a team of about 40 developers working on a project of about 30 maven modules). The setup is working okay, we use the DFC jar together with a self build dfcproperties jar that contains the dfc.properties, keystore and log4j configuration files for our project deployed on a Weblogic server. These jars are also on our local maven repository, so every developer automatically receives the correct config for its platform.

Still, once the dfc jar initializes, the logging format of the log4j logger is overwritten by a documentum class : com.documentum.fc.common.impl.logging.LoggingConfigurator

which claims that nog logging configuration could be found and that a default log4j.properties will be used.

I havent found how to override this behavior, does anyone have any clues on this one?

thanks in advance,

Jeroen.

Find more posts tagged with

Comments

lastnitescurry

sorry no clue to your problem but keystore files should not be saved. They are automatically generated by dfc and are used to secure the connection. If you use one from the wrong environment, then you will get DFC_PRINCIPALED_AUTHENTICATION errors.... or something like that

Francois Dauberlieu

The logging mechanism in DFC looks ONLY for the file mentionned to use with the DfLogger class than handles the logging in Documentum, therefore, you don't have any other choice than t use one