Recent content by davidt50

Please verify that the Livelink/CS server is the correct time. At the time of creation of an object the local server dateteim is used, not the db time. Regarda David

Forgot to add, if your application can move the documents to a Livelink server and do the upload locally, it should be significantly faster.

Another approach could be to get the LAPI app to do multiple requests to differing threads and/or instance to divide the load. You may want to check network settings. There has been a number of times where network packet sizes etc can affect upload performance. Check with OT-CS and they...

Don't forget, on the Knowledge Centre there is also the ECM Champion Toolkit which has a lot of great documentation on various topics. https://knowledge.opentext.com/knowledge/llisapi.dll/open/Open_Text_ECM_Champion_Toolkit

All you need to do, and Livelink does this under the covers as well, is to add the location to the query to make it from here down to what ever the user search es on... "OTLocation":"12037" The "Within enterprise" is just taking the name of the folder.

Just for laughs and giggles, what is the query being generated to the search engine and what version?

Some other points to consider: - If you have over 60-70% constant Livelink thread usage then you are getting into thread saturation and need to reconsider your load requirements. - The previous point reflects on the RDB as well, if the system is designed to handle 100 concurrent users and the...

The password for users is stored in one-way encrypted from and when a user enters thier password itis encryped the same way and checked against the system. Most password system work like this and decryption is not possible nor desired :-)

If you are inside Livelink script, you can easily orphan a DAPINodeCallback ( based on LLIAPI:LLIAPI Root:NodeCallbacks ) and override the CBRename function. Making sure you set the fSubTypes to be the list you care about, in this case {0, 144}. The function passes in the existing node...

annikan you said: "at it and I was concerned about returning too much data via xml" The search api returns the data you describe in the display options to return. It is not much different then calling the LAPI interfaces, just looks and feels like more :-) That being said the attributes is...

Most/All of the Office properties that are in the index can be found in the regions page for the data source. They will be normally of the form OTDoc*, the following are some examples: OTDocCompany OTDocNumberofPages OTDocTemplate The list is not fixed since you will find custom ones...

You don't mention what version of Livelink you are running and what versions of MSWord? I have just tried what you mention in 9.5sp1 and I am not seeing what you describe. If you are running an older version of Livelink then anything is possible. If you have a particular set of documents...

For such events, do you have the SOV management emails set up? Those will notify you within 5 minutes if things like the search engine goes down.

If you are pegging the server 100% then definitely, it is time to off load the indexing across to multiple machines. I can see the extractor/livelink, document conversion and the Update Distributor running on the existing machine. As for the Index engines and search engines they should be...

I think this makes for better behaviour from a business point of view. WDYT? Does this operation make more sense?