Get specific type of all nodes without root node

Hi,
I am using Content server 2010. I am writing java web based application where i am using CS 2010 webservices.

Is it possible to retirive specific type of all nodes without fetch root node or parent node?.

e.g.

                                                             Type
EnterpriseWS                                   - root
       - Colleges                                     - Folder
             - FC                                        - Folder
                  - Academic Project           - Project
                        - Java                            - Folder
                       - Dot Net                     - Folder
              - Wadia                                   - Folder
                     -  Academic Project        - Project
                         - Java                          - Folder
                         - Dot Net                      - Folder

PersonalWS                 - root
        - My Project            - Project
                 - My Java        - Folder
                 - My Dot Net     - Folder


My Current approach is
   First get "EnterpriseWS" root node & then take its all child recursively & after that collect only Folder type nodes.
   & do the same for "PersonalWS" root node

   Result - Flat structure
   - Colleges   - Folder
   - FC            - Folder
   - Java            - Folder
   - Dot Net       - Folder
   - Wadia           - Folder
   - Java             - Folder
   - Dot Net        - Folder
   - My Java        - Folder
   - My Dot Net   - Folder

I think this is not correct way & also it will take more time.

Is there any other way to get specific type of nodes without fetching root node?

Find more posts tagged with

Comments

Jason_Smith

There are a few different approaches you could take here. One approach would be to use DocumentManagement.GetNodesInContainer and filter out the unwanted nodes returned client side. This would allow you to make a single web service call, but would likely return way more information than what you really want.

Another approach would be to use DocumentManagement.ListNodesByPage(). This call has options that allow you to filter based on type. For example, you could set the type filter to get only Folder objects. However, this will not retrieve nodes recursively so you would have to make multiple calls if you wanted to get items deeper than the parent level. Also note, this method allows you to filter for container objects so if you wanted to get nodes recursively you could do the recursion yourself after getting all the containers.

Another option is to use the Search Service and perform a search to get the nodes you want. I'm not an expert with the Search Service, but there is a sample pinned at the top of this forum that you could take a look at.

Hope that helps.

Jason

Appu_Nair

You can get this in SQL by doing this.I am sure service methods may exsist but it is good to know the livelink schema

Enterprise workspace is a volume its parentid=-1

Personal workspace is a volume its aprentid=-1

Folders /documents have parents identified by parentid

Recursive search like you are doing in oracle is akin to say your folder id-2000

select name,dataid from dtree where subtype=0 /--limit to folders--/

connect by prior dataid=parentid start with 2000

This will give you the connected hierarchy.

but all volumes have another important key called ownerid which is the negative dataid of the dtree.dataid

so for all folders in enterprise workspace

select * from dtree where subtype=0 and ownerid=-2000 (usually this is not a hardcode sometimes)

So if you know your ownerid then you can get the flat structure

for e.g if my userid in livelink is 12345 then -12345 will be my ownerid in dtree so I can find all items in my personal workspace with this query

select * from dtree where ownerid=-12345

LAPI had a listnodes which would take dtree and a where condition.I will be surprsied if EWS don't have it.You should be able to do the same by doing xml search api or LQL as well

Ferdinand Prantl

The Search API would support broad span of different customers and is ready-to-use from remote applications over HTTP/XML or HTTP/SOAP. The WS methods mentioned by Jason would make you implementation simpler but each would put some limitations onto your application. However, if you build an application for a specific customer they may not apply and you save time (for now).

If you can afford deploying your own modules on CS you can go Appu's SQL way or use the faceted browsing (LLIAPI:DynamicView.NodeListContentsByPageAndFacet). You're probably familiar with the faceted browsing by using its UI - facet sidebar panel. It does exactly what you want - shows all items of specific criteria starting in a root container recursively. And it has another advantage - you can get the items by pages - similarly like search queries work - so that also huge hierarchies can be handled with good performance on the client side. If you write your own SQL you'd have to handle all finesses on your own.

Currently there's no WS exposing faceted browsing. But I've heard that it is planned for future. Now you'd have to knock up your own HTTP/XML, HTTP/SOAP or LAPI method.

--- Ferda

Appu_Nair

Hi Ferda,

My intention wa sto expose the user to how the nodes are arrnged in livelink dtree and was not suggeting him to use SQl.In lapi there is a ListNodes which takes a where condition.

For eg I could write ListObjects( "subtype=0") so i was wondering whether EWS lost that capability or whether it is still there..My intention was not to suggest using SQL.I thought it would be way too easy to find the flat structure if you went after the ownerid.

Ferdinand Prantl

Aaa, now I got what you mean. Yes, the solution suggested by you (SQL expression passed to ListNodes) is the easiest solution for LAPI-based applications.

I doubt that WS will ever expose so low-level parameters like custom SQL excerpts as input parameters. Even this feature of ListObjects has been shunned. (You have to turn it on in opentext.ini for LL 9.7.1 after applying some security patch.)

--- Ferda