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; } } }

Connection on DFC

luca.preziati

Hi everyone.

I'm trying to implement a service for obtain r_object_id as explaned in High Volume Server.

So I implement a standalone Jar which i will connect to my docbroker server.

I copy the code and reorganize.

This is the code which done the authentication

public IDfSessionManager logOn(String userName, String password, String docbaseName, String docBroker, int docBrokerPort, String dfcDataDir)throws Throwable {final IDfClientX clientx = new DfClientX();final IDfClient client = clientx.getLocalClient();     (Point 1)final IDfTypedObject config = client.getClientConfig();config.setString(DfPreferences.DFC_DOCBROKER_HOST, docBroker);config.setInt(DfPreferences.DFC_DOCBROKER_PORT, docBrokerPort);final IDfSessionManager sessionManager = client.newSessionManager();final IDfLoginInfo loginInfoObj = clientx.getLoginInfo();loginInfoObj.setUser(userName);loginInfoObj.setPassword(password);sessionManager.setIdentity(docbaseName, loginInfoObj);return sessionManager;}

When I execute this part of code I have this exception:

5:08:14,558 ERROR [main] com.documentum.fc.client.security.impl.IdentityManager - [DFC_SECURITY_IDENTITY_INIT] no identity initialization or incomplete identity initializationjava.lang.NullPointerException          at com.rsa.jsafe.c.run(Unknown Source)          at java.security.AccessController.doPrivileged(Native Method)          at com.rsa.jsafe.CryptoJ.h(Unknown Source)          at com.rsa.jsafe.CryptoJ.b(Unknown Source)          at com.rsa.jsafe.CryptoJ.a(Unknown Source)          at com.rsa.jsafe.CryptoJ.f(Unknown Source)          at com.rsa.jsafe.JSAFE_SecureRandom.a(Unknown Source)          at com.rsa.jsafe.JSAFE_SecureRandom.getInstance(Unknown Source)          at com.documentum.fc.client.security.internal.CreateIdentityCredential$MultiFormatPKIKeyPair.<init>(CreateIdentityCredential.java:599)          at com.documentum.fc.client.security.internal.CreateIdentityCredential.<init>(CreateIdentityCredential.java:98)          at com.documentum.fc.client.security.impl.InitializeKeystoreForDfc.<init>(InitializeKeystoreForDfc.java:45)          at com.documentum.fc.client.security.internal.KeystoreMgr.initForDfcWithDefaultPolicy(KeystoreMgr.java:70)          at com.documentum.fc.client.security.impl.IdentityManager.initFromKeystore(IdentityManager.java:170)          at com.documentum.fc.client.security.impl.IdentityManager.<init>(IdentityManager.java:40)          at com.documentum.fc.impl.RuntimeContext.<init>(RuntimeContext.java:52)          at com.documentum.fc.impl.RuntimeContext.<clinit>(RuntimeContext.java:181)          at com.documentum.fc.client.DfClient.<clinit>(DfClient.java:700)          at com.documentum.com.DfClientX.getLocalClient(DfClientX.java:43)          at it.ubiss.gedi.dms.documentum.DocumentumServiceUtil.logOn(DocumentumServiceUtil.java:89)          at it.ubiss.gedi.dms.documentum.DocumentumServiceUtil.logOn(DocumentumServiceUtil.java:82)          at it.ubiss.gedi.dms.documentum.DocumentumOfflineUpload.prepareUpload(DocumentumOfflineUpload.java:35)          at it.ubiss.gedi.dms.documentum.RunDocumentumOfflineUploader.main(RunDocumentumOfflineUploader.java:26)

and I don't find nowhere the file dfc.keystore. Should I take it from the server?

Then, when I try to get session with the session = sessionManager.getSession(documentumUploadProperty.getDocbaseName()); I get this exception:

15:34:48.006 [main] ERROR i.u.g.d.d.DocumentumOfflineUpload - DFC-Exceptioncom.documentum.fc.client.DfDocbrokerException: [DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker "docl101t.hbl.local:1489" failed          at com.documentum.fc.client.DfDocbrokerException.newRequestFailedException(DfDocbrokerException.java:12) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.DocbrokerConnection.<init>(DocbrokerConnection.java:30) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.DocbrokerConnectionFactory.newDocbrokerConnection(DocbrokerConnectionFactory.java:27) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.docbroker.MapBuilder.issueRequest(MapBuilder.java:27) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.docbroker.ServerMapBuilder.getDataFromDocbroker(ServerMapBuilder.java:76) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.docbroker.ServerMapBuilder.getMap(ServerMapBuilder.java:35) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.docbroker.DocbrokerClient.getServerMap(DocbrokerClient.java:152) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.ServerChoiceManager.updateServerChoices(ServerChoiceManager.java:103) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.ServerChoiceManager.updateServerChoicesIfNecessary(ServerChoiceManager.java:92) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.ServerChoiceManager.getServerChoices(ServerChoiceManager.java:45) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.getServerChoices(DocbaseConnection.java:262) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.establishNewRpcClient(DocbaseConnection.java:220) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.open(DocbaseConnection.java:118) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>(DocbaseConnection.java:92) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.<init>(DocbaseConnection.java:56) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionFactory.newDocbaseConnection(DocbaseConnectionFactory.java:26) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbase.DocbaseConnectionManager.getDocbaseConnection(DocbaseConnectionManager.java:74) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.session.SessionFactory.newSession(SessionFactory.java:29) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.session.PrincipalAwareSessionFactory.newSession(PrincipalAwareSessionFactory.java:35) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.session.PooledSessionFactory.newSession(PooledSessionFactory.java:47) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.session.SessionManager.getSessionFromFactory(SessionManager.java:111) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.session.SessionManager.newSession(SessionManager.java:64) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.session.SessionManager.getSession(SessionManager.java:168) ~[dfc-6.5.jar:na]          at it.ubiss.gedi.dms.documentum.DocumentumOfflineUpload.prepareUpload(DocumentumOfflineUpload.java:37) ~[classes/:na]          at it.ubiss.gedi.dms.documentum.RunDocumentumOfflineUploader.main(RunDocumentumOfflineUploader.java:26) [classes/:na]Caused by: com.documentum.fc.client.DfIOException: [DM_SESSION_E_RPC_ERROR]error:  "Server communication failure"          at com.documentum.fc.client.DfIOException.newCommunicationFailureException(DfIOException.java:16) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.newDocbrokerRpcClient(NetwiseDocbrokerRpcClientFactory.java:39) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.DocbrokerConnection.<init>(DocbrokerConnection.java:25) ~[dfc-6.5.jar:na]          ... 23 common frames omittedCaused by: java.io.IOException: docl101t.hbl.local          at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.resolveHostNameCorrectly(NetwiseDocbrokerRpcClientFactory.java:273) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.access$100(NetwiseDocbrokerRpcClientFactory.java:28) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory$1.run(NetwiseDocbrokerRpcClientFactory.java:136) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory$1.run(NetwiseDocbrokerRpcClientFactory.java:124) ~[dfc-6.5.jar:na]          at java.security.AccessController.doPrivileged(Native Method) ~[na:1.6.0_21]          at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.openSocket(NetwiseDocbrokerRpcClientFactory.java:121) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.openSocket(NetwiseDocbrokerRpcClientFactory.java:103) ~[dfc-6.5.jar:na]          at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.newDocbrokerRpcClient(NetwiseDocbrokerRpcClientFactory.java:35) ~[dfc-6.5.jar:na]

Any suggestion?

Find more posts tagged with

Comments

luca.preziati

The first problem depends by missing of dfc.keystore. I have copied from composer and I solved, but I think I can recreate if miss.

Is it possible?

Imran_Yusubov

Hi,

Use of dfc.keystore file.

Each installed DFC has an identity, with a unique identifier extracted from the PKI

credentials. The first time an installed DFC is initialized, it creates its PKI credentials

and publishes its identity to the global registry known to the DFC. In response, a

client registration object and a public key certificate object are created in the global

registry. The client registration object records the DFC instance’s identity. The public key

certificate object records the certificate used to verify that identity.

The PKI credentials for a DFC are stored by default in a file named dfc.keystore in the

same directory as the dfc.properties file.

Recreate keystore file?

Shutdown your docbase and change the $DOCUMENTUM\config\dfc.keystore file to dfc.keystore.bak.

Then start your docbase,the keystore file will (should) be recreated.

For more information see Documentum Administration Guide and Documentum Content Server fundamentals guide.

Hope this helps

luca.preziati

I don't want recreate the dfc.keystore of the application server, I want recreate the dfc.keystore of my client application which I want connect to documentum.

lastnitescurry

a) keystore files.... delete them, will be regenerated automatically based on current IP address. Defainately need to do this if have dynaic IP

b) your code is useless

public

Your error is probably because of a using a dfc.properties on a network drive. Change to local dfc.properties

# The directory from which the configuration file was read.  # This is a read-only property that is initialized at system startup time.      # dfc.config.dir =  # The root directory of a tree of directories containing data used by DFC. If # 'user.dir' system property is not set, then the location defaulted to the # 'current working directory'/documentum                                        # dfc.data.dir = ${user.dir}/documentum

luca.preziati

My code isn't useless, I have this bacause i want have 3 different configuration in three different server, with the same jar, without deploy the file dfc.properties, but only change them in my custom file properties, loaded one per different servevr.

lastnitescurry

maybe useless was a bit extreme but as you are not using the methods I commented out then....

luca.preziati wrote:My code isn't useless, I have this bacause i want have 3 different configuration in three different server, with the same jar, without deploy the file dfc.properties, but only change them in my custom file properties, loaded one per different servevr.

That sounds intersting.... but dfc.properties provides a lot more than just docbroker host and port. How will you load those parameters?

luca.preziati

I know. But i work for a Bank and they want single pack to deploy in different context, integration, test and production and they don't want properties files for application, but in documenutum are accepted.

We use the enviroment variable to understand what configuration load.

However I think I should set only docbroker and port.

DCTM_Guru

It also contains the global registery repository, user name, and password. Without this correction configuration, you may not be able to call SBOs correctly and/or store/retrieve user preferences.

luca.preziati

I have found the problem to solve the problem to connect the docbroker, now work, after two days I found a problem in network connection...no words...

Thanks to anybody....

Imran_Yusubov

I don't want recreate the dfc.keystore of the application server, I want recreate the dfc.keystore of my client application which I want connect to documentum.

Read the documentation.

lastnitescurry

luca.preziati wrote:But i work for a Bank and they want single pack to deploy in different context, integration, test and production and they don't want properties files for application, but in documenutum are accepted.We use the enviroment variable to understand what configuration load.

There is another option you could try. Should have though of it earlier but was focused on fixing the problem you asked rather than your real problem... assuing the quoted is the real problem!!

DFC client app on a Content Server all have their own dfc.properties files but these files all point to a single central dfc.properties file. The #include is used to do this, for example:

#include \DocumentumDFCUser\config\dfc.properties

Assuming you can drop a server specfic config file down to your app servers. You can use the #includes to point the webtop, da or tasksapce wars to the server specfic file. As long as the file is in same location on every server your DFC client app should work.