LSCS/AT oddities

OK, at a customer site, two things we noticed. Their app queries LSCS for a bunch of data. Works perfectly on LSCS/RT but one 732 and 731, AT returns the same query for each hidden edition. So if there are 5 versions of a file that match the query, all 5 are returned. Not certain of a good way to filter that out.

We ran across issue #2 trying to debug that. In 732 to query LSCS/AT you need a valid TS session. Oh, it will work, but it will return zero results if you are not logged into TeamSite. That was a fun one to figure out what the f*** was going on. 731 does not behave that way.

We have opened support cases on both, the latter I expect is a bug, I assume for the 1st one we are just missing something in the query (at least I hope so)

Find more posts tagged with

Comments

Vendim Birbili

WE have the same issue on 7.3.2 . The LSCS queries on Preview are not working. the values are returned null. only when we deploy to runtime it works

new_report_2.rptdesign

nipper

WE have the same issue on 7.3.2 . The LSCS queries on Preview are not working. the values are returned null. only when we deploy to runtime it works

Are you querying from the browser or your app ? Try logging into TS and then run the query from that browser.

Rick Poulin

We have opened support cases on both, the latter I expect is a bug, I assume for the 1st one we are just missing something in the query (at least I hope so)

I had the same painful experience discovering these little gotchas... In 7.3.2, they introduced two new params to the REST API (and to lscsclient.jar's Client class):

context: This parameter specifies which edition/staging/workarea you want to query. I was under the impression that it would default to 'STAGING' if not specified, but maybe it defaults to 'any context'. Try setting it to STAGING explicitly.
session: This is your CSSDK session string. It is a semi-intentional side effect of using TS Search as the IDOL repository, since that IDOL instance is configured to maintain ACLs on content. If you want to do 'anonymous access to everything' LSCS queries like before, you pretty much have to wrap your code in something that instantiates a CSClient as SYSTEM/iwui just to get a session string from it.

Personally, I find the session thing especially fugly because this forces you down a path of having to fork your Java MetadataService into separate subclasses on authoring vs. runtime just for this and specifying a specific context only on the auth side. I mean, I already did that forking for other reasons, but it just seems like bad design for the API to force it on you.

balajiranjan

HI,

I have seen such problems with session in the 7.3.1 authoring. It does require you to login to teamsite as it has an additional security layer. I couldn't even get the lscs debugpanel to work without logging on to team site.

THanks,
Balaji

Vendim Birbili

Are you querying from the browser or your app ? Try logging into TS and then run the query from that browser.

I can run query from the browser and I dont get any data