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

LSCS Rest query not returning the document.

Murugan_P

As part of testing the LSCS installation i deployed a sample .txt file using the startdeploy.bat teamsite area diff deployment.

Then i queried the file with http://myhostname:8080/lscs/v1/document/path/lscs_test.txt
My browser displayed the content of the text file (expected result).
The lscs_test.txt file was created directly under workarea.

Now, i created a new branch and workarea and created another .txt file named sample.txt directly under the new workarea and executed the startdeploy.bat as done previously.

But now when i queried for the file with [color=navy]http://myhostname:8080/lscs/v1/document/path/sample.txt, [/color]i'm getting a 404 error code.

I've verified the existance of the file under the LSCS Authoring store file system and it is available.

when i query for all the documents using http://myhostname:8080/lscs/v1/document?q[color=navy]=*, i'm getting only the first file, lscs_test.txt[/color]

If i query for the document using the admin->debugpanel->documentquery i'm getting the sample.txt file as the result of my query with project=mynewprojectpath and q=*

Is there anything wrong with my REST request ?
I'm pretty much new to LSCS and REST based queries.

Thanks,
Murugan
TS 7.1, LSCS 7.1, OD 7.1, Win 2003

Find more posts tagged with

Comments

Frederik

I'm new to LSCS too... I guess everybody is Smiley Wink

I suspect that LSCS has interpreted your first deployed branch as defaultProject (see doc lscs_71_tech_ref_v01_en.pdf p.23).

check the names of defined projects with GET /lscs/v1/projects

and use project={project-name} in your queryString when searching/requesting documents

Murugan_P

I'm new to LSCS too... I guess everybody is

I suspect that LSCS has interpreted your first deployed branch as defaultProject (see doc lscs_71_tech_ref_v01_en.pdf p.23).

check the names of defined projects with GET /lscs/v1/projects

and use project={project-name} in your queryString when searching/requesting documents

Thank you very much. It worked fine.
Do we need this query string to be appended even if i query for the document using the document id ?

When i tried, only if i append the project name i'm getting the content.

Then what will be the purpose of searching a content using its id ? or Is the document id not unique accross projects ?

Thanks,
Murugan

AlexC

Also there is a simple interface for querying content and such at:

http:// your-server : your-port/lscs/admin/debugpanel

Murugan_P

Thank you very much. It worked fine.
Do we need this query string to be appended even if i query for the document using the document id ?

When i tried, only if i append the project name i'm getting the content.

Then what will be the purpose of searching a content using its id ? or Is the document id not unique accross projects ?

Thanks,
Murugan

Alex, What about the content addressing using document ID ?
Do we need to append the project name as query string ?

Binettoid

Please let me know, if you get an answer to this last query.

BOP.docx

BopReportv3.RPTDESIGN

Murugan_P

Please let me know, if you get an answer to this last query.

There's no answer whatsoever.

vpatel

You need to pass the project name as part of your query -- if you don't it'll only look into the "default" project which is typically the first project that you had deployed.

dd.png

Binettoid

Thanks Viral,
I am getting errors even when passing the project name as part of the document query!! I have components that perform a getDocumentList and then render the doc titles as links to click through to that document but when i click on any of them i get nothing, e.g.

the REST query is
http://servername:8080/lscs/v1/document/id/ac5da12b9ebd73f089b8e3f394c7415d?project=//DR1wwsd1/default/main/ms&format=json
OR
http://servername:8080/lscs/v1/document/path/templatedata/LiveSite/Factsheet/data/rentalchecklist.xml/$?project=//DR1wwsd1/default/main/ms&format=json
RETURN 404 on my platform.
I have tried deleting the project from LSCS but the results are the same.

Er... here's an update - I have two installations (7.1 & 7.2)and only after migrating to the new one (7.2) am i seeing this error on the new platform.
It's taken a while to see this but it seems on the new platform the REST query is subtly different and malformed, e.g.
http://servername:8080/lscs/v1/document/path/templatedata/LiveSite/Factsheet/data/rentalchecklist.xml/$&project=//DR1wwsd1/default/main/ms&format=json
Spot the first & - it should be a ?
But WHY is this happening?
My client has been messing around with this (their) platform and I have no idea what they have done, except that this mechanism (list docs, render links, click through) used to work.
Any ideas greatly appreciated.
Sobbing in desperation, Sydney.

vpatel

If you are getting a specific document -- try the format=xml or just remove the format attribute from your query all together.

Binettoid

Hey thanks for bothering, but did you even read my post?
I have traced this issue to the lscsclient.jar or the livesitecs-components.jar becoming modified on the 7.2 installation. They seem to be modified everytime a build is performed, while on my 7.1 system they remain unmodified since install. Replacing them with mine fixed this problem of malformed REST queries.
How can this happen in the first place?
Why does running build.bat on 7.2 modify these jars?
What other processes or development efforts might modify and corrupt these jars?