Document Uploaded with Web Services Dont Go to Archive Server

Hi All,

We have Archive Server configured as the storage provider for all >0KB Documents. But, when we use the Web Services to upload documents it goes to the Database. The documents get stored to Archive Server properly when uploaded using the Web UI. Why is this so?

Are we missing any Settings specific to Web Services?

Thanks

Find more posts tagged with

Comments

Appu_Nair1

Is your livelink setup so that 144 subtype goes to archive storage provider and is that the first rule that you see .If there are multiple rules then it is evaluated from top to bottom

And the first rule that matches could be used WSAPI and livelink should obey what you have setup at least that is how it used to work.

In other word you should not have in your storage provider rule this

First Rule if subtype== 144 then use EFS Provider

Second Rule if subtype== 144 then use myEASP

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Thursday, May 28, 2015 10:02 AM
To: eLink Recipient
Subject: [EXTERNAL]Document Uploaded with Web Services Dont Go to Archive Server

Document Uploaded with Web Services Dont Go to Archive Server

Posted bydimple.warke@cognizant.com (Warke, Dimple) On 05/28/2015 11:01 AM

Hi All,

Are we missing any Settings specific to Web Services?

Thanks

[To post a comment, use the normal reply function]
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

Dimple_Warke

Hi Appu,

We dont have multiple storage rules. Just one rule.

All >0 KB files go to Archive Server. So there shouldn't be any storage rule clash.

Thanks

Appu_Nair1

Then what I would do is put on that livelink server debug=2 ,wantlogs=true and wantlapilogs=true

If you want and know how to do it you may want to reduce the number of threads(purely optional)

Then I would do a GUI upload and WSAPI Upload and send the entire logs to OT

If you have access to builder or CSIDE an can put a break on the code you may be able to find it as well.

Obviously are you getting errors or is wsapi content being sent to EFS/CLOB?

The Archive Storage provider has its own logging does not need re-start it will be a file called easp_dsh.log(from about 4 yrs back memory)

That might tell you something as well.

The greater than 0 KB while it sounds good I would use the “Always” rule to test the condition. that rule is a hard code.

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Thursday, May 28, 2015 10:29 AM
To: eLink Recipient
Subject: [EXTERNAL]RE Document Uploaded with Web Services Dont Go to Archive Server

RE Document Uploaded with Web Services Dont Go to Archive Server

Posted bydimple.warke@cognizant.com (Warke, Dimple) On 05/28/2015 11:27 AM

Hi Appu,

We dont have multiple storage rules. Just one rule.

All >0 KB files go to Archive Server. So there shouldn't be any storage rule clash.

Thanks

[To post a comment, use the normal reply function]
Topic:	Document Uploaded with Web Services Dont Go to Archive Server
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

Dimple_Warke

The "Always" rule fixed the issue. Thanks Appu.

Appu_Nair1

I actually meant to use 'Always' as a way to test the anomaly .

Not a "good"idea you "need" to find a better rule that won't upset wsapi and livelink . If you have ELS (absolutely new livelink code this is now baked into core) code in that livelink then your storage rule provider rules get more things like you can say if subtype in(144,749) with this rule your other versionable content like categories,wfmaps,form templates ,search templates all will go to AS which will land you in more trouble in the future(technically AS will handle it but OT does not like you putting anything other than 144 or 749 in AS) At least for categories if they are being made in the Cats Volume you can say a rule if volume==categories go there. I would raise a ticket with OT to see why >0 does not obey what you originally said.

From: eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com>
Sent: Friday, May 29, 2015 4:33 AM
To: eLink Recipient
Subject: [EXTERNAL]RE RE Document Uploaded with Web Services Dont Go to Archive Server

RE RE Document Uploaded with Web Services Dont Go to Archive Server

Posted by dimple.warke@cognizant.com (Warke, Dimple) On 05/29/2015 05:32 AM

The "Always" rule fixed the issue. Thanks Appu.

[To post a comment, use the normal reply function]
Topic:	Document Uploaded with Web Services Dont Go to Archive Server
Forum:	Content Web Services Forum
Content Server:	Knowledge Center

Carsten_Kulms

Appu, you are right -- that rule should work no matter which upload method is used.After a (cursory) evaluation I think there is a flaw that causes the storage rule evaluation process observing a wrong value when the upload is performed by means of CWS. Therefore I just logged a new bug entry under LESAPI-1954 for this issue.