Q & A. VI

It seems that Jens decided to take pity on myself after dmcl-applications startup time post and suggested following:

Hi Andrey,

I am working for fme in Brunswick (Germany) and one of my colleagues has created the tool DQMan. It is free to use and it helps me in my daily job to get Documentum things done faster.

It is up to you to try it:
http://www.fme-us.com/technologies/ecm/emc-documentum/dqman/

And thank you for your really cool blogs posts here.

Thanks,
Jens

Jens, thanks for suggestion 🙂

At first, I managed to cut iapi startup time to 2.8s:

 ~]$ time iapi -X -Sapi </dev/null
Running with non-standard init level: api
API> Bye

real    0m2.819s
user    0m2.593s
sys     0m0.116s

All that was required is remove dumb RSA security providers:

--- java.security.emc   2015-05-07 05:34:38.593021383 +0300
+++ java.security       2015-05-08 21:30:07.008428097 +0300
@@ -43,17 +43,15 @@
 #
 # List of providers and their preference orders (see above):
 #
-security.provider.1=sun.security.rsa.SunRsaSign
-security.provider.2=com.rsa.jsafe.provider.JsafeJCE
-security.provider.3=com.rsa.jsse.JsseProvider
-security.provider.4=sun.security.provider.Sun
-security.provider.5=sun.security.ec.SunEC
-security.provider.6=com.sun.net.ssl.internal.ssl.Provider
-security.provider.7=com.sun.crypto.provider.SunJCE
-security.provider.8=sun.security.jgss.SunProvider
-security.provider.9=com.sun.security.sasl.Provider
-security.provider.10=org.jcp.xml.dsig.internal.dom.XMLDSigRI
-security.provider.11=sun.security.smartcardio.SunPCSC
+security.provider.1=sun.security.provider.Sun
+security.provider.2=sun.security.rsa.SunRsaSign
+security.provider.3=sun.security.ec.SunEC
+security.provider.4=com.sun.net.ssl.internal.ssl.Provider
+security.provider.5=com.sun.crypto.provider.SunJCE
+security.provider.6=sun.security.jgss.SunProvider
+security.provider.7=com.sun.security.sasl.Provider
+security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI
+security.provider.9=sun.security.smartcardio.SunPCSC

At second, I have taken a look at dqman extended video:

and I would say that DQMan seems to be the only usefula must have tool for Documentum developers and administrators – some of it’s features look really cool, for example generation of API scenario, unfortunately, I’m happy with iapi 🙂

One thought on “Q & A. VI

  1. Pingback: Fighting with DEV ENV | Documentum in a (nuts)HELL

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s