Archivelink to assap authentication error - documentum

[Former Member]

Hi,

On our project we have configured SAP ArchiveLink Content Repositories (OAC0) that link to Documentum Archive Services for SAP (assap). Documents attached using FB03 for example would physically be saved in a Documentum repository. This was tested several times and was working correctly.

After a reboot of the Documentum server the archivelink component could no longer authorize itself on the documentum assap component.

The following error message is displayed in sap.

HTTP error: 400 Petici n incorrecta  Bad Request:
No connection to Docbase 'Doc_dev':  No connection
to Docbase 'Doc_dev(8)':  [DM_SESS

The Documentum assap error log indicates the following:

[2009-05-27 17:14:39,015|INFO |Thread-1              |com.documentum.ei.al.ALServlet|logVersionInfo|216 ]	
[2009-05-27 17:15:06,625|WARN |Thread-1              |com.documentum.ei.repository.ConnectionPool|<init>|85  ]	locksByDbConnections.size() == 0 is true
[2009-05-27 17:15:08,484|WARN |Thread-1              |com.documentum.ei.al.ALServlet|init|85  ]	Process Statistics Collection Disabled!
[2009-05-27 17:18:09,343|ERROR|http-8080-2           |com.documentum.ei.repository.ConnectionPool|initializeDocbase|366 ]	Session was not established for 'Doc_dev(1)'; trying one more time
com.documentum.ei.repository.exception.NoConnectionException: No connection to Docbase 'Doc_dev(1)':  [DM_SESSION_E_AUTH_FAIL]error:  "Authentication failed for user admindoc with docbase Doc_dev.Doc_dev@dw3doc."at com.documentum.ei.repository.ConnectionPool.getSession(ConnectionPool.java:199)
	at com.documentum.ei.repository.ConnectionPool.initializeDocbase

We have tried the username and password in Documentum Administrator and it works. Also in the ArchiveLink configuration in Documentum the connection seems to be ok. It is just from SAP that we are not able to connect anymore.

If anyone has encountered a similar situation before or has an idea of where we could look for the error. Your input would be very much appreciated.

Thanks & Regards,

Giwan

[Former Member]

Hello,

I'm affraid that with ArchiveLink it's not possible to use anything else than the SAP DocId as object_name.

You can use Content Services for SAP to create a Replicate SAP action to replicate attribute values from SAP to Documentum.

[Former Member]

Hi,

We are also integrating using Archive and Content services for SAP. The repositories created in oac0 are able to store documents from DMS into Documentum.

However, the documents are stored with DocId as object name in documentum. Can someone pls tell me, how I can obtain the original name of physical document instead.

Rgrds

Shaaj

[Former Member]

Hi Shaaj,

I'm facing the same issue, did you solve it? Can we define another name to be used by Documentum when the document is stored from SAP or is it mandatory to use the Doc ID?

Thank you

Mattia

[Former Member]

Hi,

Thank you all for your input. However we have also been working with EMC to resolve the issue. In the end they were able to help us.

The problem was the keystore file that documentum uses to encrypt the passwords. It seems that when one of the web components (i.e. assap) is not able to find the Documentum Keystore file, it creates it's own keystore file.

Due to this however the encrypted password that is provided is not "always" decrypted correctly, resulting in the message that SAP archivelink is not able to login with the credentials provided.

We have resolved the issue by providing a parameter in all the dfc.properties files that points to a single keystore file in the Documentum installation directory.

The issue seems to have been resolved and has been working for 1.5 business day now.

Thanks again.

Regards,

Giwan

[Former Member]

Have you tried resending a certificate?

[Former Member]

Hi,

Please, check these entries once again,

1.Launch the transaction OAC0.Double click on the respective content

repository.

2.Go to edit mode.click on the 'Full Adminstarion' tab.

3.Please maintain a protocol if not maintained already.for example the

protocol SAPHTTP.save it.

4.Launch the transaction OAA3.Create an entry with the same protocol and

the same version.Save it.

5.Double click on the protocol and it will take you to a screen

'Over view of protocol'.

Then click on 'Display Stored document' >Choose the document type

'TIF' >choose the communication type as 'ARCHIVELNK' >Click on

continue.

Similarly click on 'Retrieve Stored Document on Client PC' >choose the

communication type as 'TABLE' >Click on continue.

Then click on 'Display local file' >choose communicaion type as

'ARCHIVELNK' >Click on continue.

6.SAVE the settings.

Note:1. if dose't works, please try to restablish both connetion.

2. check Data carrier type also.

Benakaraj

??

[Former Member]

Are you able to ping the documentum server from the SAP server -- OS level?

What storage type (RFC or HTTP) is used? If it is an RFC archive, check the RFC destination as well.

Please update. Thx!