Urgent. Importing Documents from ArchiveLink to Content Server.

Hello!

The case is very simple:

We have an ArchiveLink server connected to SAP CRM. All files accessed from CRM by link with unique docid. All this docids are in table TOA01 in CRM.

Now we connected this ArchiveLink server with new instance of Content Server.

The problem is:

How we can import all this Documents to Content Server? We need just create links in CS to access all this files from ArchiveLink.

Find more posts tagged with

Comments

eLink User

Since ContentServer already has a module that allows talking with archive server you may want to read upon the Archive Storage Provider

Also you may want to understand the plumbing that is provided by Enterprise Library Services.As such if a document is in AS then you have ways to
surface the document in Content Server you may not need to "import" it again. OT solutions such as RM link,xECM all use this kind of method of
showing non livelink content .in AS in livelink a.k.a Content Server.

Never argue with idiots. They drag you down to their level, and then beat you with experience.
Eat one live toad the first thing in the morning and nothing worse will happen to you the rest of the day

via : Laugh IT Out: Dilbert’s Best Quotes

On Fri, May 16, 2014 at 7:18 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

Urgent. Importing Documents from ArchiveLink to Content Server. Posted byalexander.embaturov@masterdata.ru (Embaturov, Alexander)On 05/16/2014 08:18 AM

Hello!

The case is very simple:

We have an ArchiveLink server connected to SAP CRM. All files accessed from CRM by link with unique docid. All this docids are in table TOA01 in CRM.

Now we connected this ArchiveLink server with new instance of Content Server.

The problem is:

How we can import all this Documents to Content Server? We need just create links in CS to access all this files from ArchiveLink.

More than 1000K documents.

Is there some regular scenario for this case??

[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: Content Server

Embaturov_Alexander

Thank you very much for answering.

I forgot about SAP: Declaring ArchiveLink documents using batch operations in xECM Administration guide.

This works well for me.

Embaturov_Alexander

Has another question in this topic.

I have SAP CRM connected to Archive Link Server.

ArchiveID associated to SAP CRM - D0.

I have already declared Storage Provider with ArchiveID=D0 in Content Server.

When I run batch report from SAP CRM (transaction SE38, program name /OTX/RM_MAKE_RECORDS) to declare documents in CS i have an error in rcs.log:

2014-05-21 18:57:48,537 ERROR [http-8080-33] otx.security : com.opentext.ecm.components.webservices.APIException - makeRecord() call for creating item failed!

com.opentext.ecm.services.entlib.ELServiceException: Creating element failed!<Wed May 21 18:57:48 MSK 2014|mydomain.com;node001> [{error_namespace=ELService, error_code=CreateFailed, error_category=Operation}] (com.opentext.livelink.service.core.LivelinkException: No Storage Provider found for ArchiveID D0.)
at com.opentext.ecm.services.entlib.impl.LesService.createRecord(LesService.java:451)
at com.opentext.ecm.services.entlib.impl.ELService.makeRecordEx(ELService.java:5592)
at com.opentext.ecm.services.entlib.impl.ELServicePluginDecorator.makeRecordEx(ELServicePluginDecorator.java:287)
at com.opentext.ecm.services.entlib.impl.ELService.makeRecordExWithRetry(ELService.java:5142)
at com.opentext.ecm.services.entlib.impl.ELService.processMakeRecordsTask(ELService.java:6351)
at com.opentext.ecm.services.entlib.impl.ELService.makeRecords(ELService.java:6023)
at com.opentext.ecm.api.entlib.impl.ser.ELService.makeRecords(ELService.java:1243)

Does anybody know what the problem is?

Thanks in advance.

Glenn Dieball

Hello, I see this thread is a few months old now.

Did you declare you new storage provider in content server? Also, did you set up all the rfc connections between CRM and sontent server?

nikhil.sanghvi

Hey,

We are also seeing the same error while running the document declaration job,

2017-07-12 12:04:43,043 ERROR [http-8080-46] otx.security : com.opentext.ecm.components.webservices.APIException - makeRecord() call for creating item failed!
com.opentext.ecm.services.entlib.ELServiceException: Creating element failed!<Wed Jul 12 12:04:43 EDT 2017|<Servername>;node001> [{error_namespace=ELService, error_code=CreateFailed, error_category=Operation}] (com.opentext.livelink.service.core.LivelinkException: No Storage Provider found for ArchiveID WW.)

did anyone find the solution?
Thanks.

Hans Stoop

The error message seem to indicate you need to define a Storage Provider in CS for the Archive Server and define one for logical archive WW.

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Mittwoch, 12. Juli 2017 18:21
To: eLink Recipient
Subject: Re Urgent. Importing Documents from ArchiveLink to Content Server. 2

Re Urgent. Importing Documents from ArchiveLink to Content Server. 2

Posted by Sanghvi, Nikhil On 07/12/2017 12:19 PM

Hey,

We are also seeing the same error while running the document declaration job,

did anyone find the solution?
Thanks.

[To post a comment, use the normal reply function]
Topic:	Urgent. Importing Documents from ArchiveLink to Content Server.
Forum:	Content Server Development Forum
Content Server:	Knowledge Center CS16

nikhil.sanghvi

Hi Hans,

We do have the storage provider as well as rule configured for logical archive WW.
We have the business folder on CS within which any data should go to this archive WW and have setup rule "object below ?" and browsed to the root folder and mapped to WW. If we login to CS and uploaded any document under the business folder, the data does get store into the logical archive WW which does work.

Now when we try to run the document declaration job which will store the data under the same business folder, we are getting the error "No storage provider for WW", while everything is in place.

We can see below error in the rcs log on the AS,
2017-07-13 04:06:17,441 ERROR [http-8080-10] otx.security : com.opentext.ecm.components.webservices.APIException - makeRecord() call for creating item failed!
com.opentext.ecm.services.entlib.ELServiceException: Creating element failed!<Thu Jul 13 04:06:17 EDT 2017|gsdvnt97.lvs.dupont.com;node001> [{error_namespace=ELService, error_code=CreateFailed, error_category=Operation}] (com.opentext.livelink.service.core.LivelinkException: No Storage Provider found for ArchiveID WW.)

Thanks,
Nikhil

Hans Stoop

Hi Nikhil,

The storage rules don’t play a role in this scenario.

The ArchiveLInk documents are also store in the logical archive WW in the same AS server used for CS?

ArchiveLink documents are not added to CS, there is only a ‘link’ made to the existing document in AS. There should be a Storage Provider defined for the AS and logical archive.

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Donnerstag, 13. Juli 2017 12:11
To: eLink Recipient
Subject: RE Re Urgent. Importing Documents from ArchiveLink to Content Server. 2

RE Re Urgent. Importing Documents from ArchiveLink to Content Server. 2

Posted by Sanghvi, Nikhil On 07/13/2017 06:10 AM

Hi Hans,

Now when we try to run the document declaration job which will store the data under the same business folder, we are getting the error "No storage provider for WW", while everything is in place.

Thanks,
Nikhil

[To post a comment, use the normal reply function]
Topic:	Urgent. Importing Documents from ArchiveLink to Content Server.
Forum:	Content Server Development Forum
Content Server:	Knowledge Center CS16

nikhil.sanghvi

Hi Hans,

yes that is correct the document are stored in the same logical archive WW in the same AS used for CS.

We have configured storage tier on AS and added WW in the particular storage tier. Could that be an issue?

Thanks,
Nikhil

nikhil.sanghvi

Hi,

We were able to fix the issue after we deleted the storage tier configuration from the Admin client. We had created 2 storage tier A and B for 2 different business and added business specific CR into the resp Storage tier.

After we removed the CR from the storage tier, Document declaration worked.

How is the storage tier configuration affecting the document declaration and its not able to find the storage provider on the AS? I was thinking that storage tier configuration is just to separate out the object logically on the admin client and does not have to do anything with other part of config.

Thanks,
Nikhil