LiveLink Ent Server integration with external application databases

We are new to LiveLink products and need some help to achieve the following:In LiveLink Enterprise Server Edition when users add documents at that time we would like to display a document attributes form where user will enter the Customer Number of that document and additional information about that record such as Customer Name, Address etc. will be displayed from external application database for review and submit for indexing.

Find more posts tagged with

Comments

Greg_Griffiths_(ggriffiths_-_(deleted))

Anil, this is certainly possible with a little modification to achieve, I would suggest using AJAX for the dataload and then use readonly attribute fields to store the data.

Bo_Warburton_(bowarburton_-_(deleted))

Message from Bo Warburton <bo@techrp.com> via eLink

eLink

Using AJAX would rely on dblookup – is that right?

From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]
Sent: Monday, December 24, 20074:42 AM
To: eLink Recipient
Subject: some thoughts

some thoughts		Posted by ggriffiths (Griffiths, Greg) on 12/24/2007 07:41 AM
In reply to: LiveLink Ent Server integration with external application databases		Posted by anil.sharma@dfa.state.ny.us (Sharma, Anil) on 12/18/2007 09:48 PM

Anil, this is certainly possible with a little modification to achieve, I would suggest using AJAX for the dataload and then use readonly attribute fields to store the data.

Donna Nalls

Hello Anil,I recently developed a customization for a client that uses a custom Livelink attribute, combined with the webforms db lookup to connect to external databases. It provides a search interface with filter capability and auto-populates other attributes in the category, based on the selected attribute value.My documentation for the project has proprietary client information, so i am not comfortable attaching it here...if this is an approach that you are interested in, i can put together some more generic documentation to better explain the application.If you are interested in purchasing this module, rather than developing from scratch, i can move the code into a standalone module and deliver it pretty quickly and cost-effecitvely. Regards,Donna

Greg_Griffiths_(ggriffiths_-_(deleted))

If you are using a form or a WebLingo page, you can use standard AJAX to connect to any database and then populate the screen with the information without using the DBLookup component.

Scott_Chate_(scottchate@corenttech.com_-_(deleted)

One of the capabilities that people seemed to be most intrigued with at the LivelinkUp 2007 conference, were the application integration possibilities that were afforded by the AgileTaxonomy? and AgileApplications? modules which we were showing there. The taxonomy module takes a different approach to the classification of data through taxonomy, by leveraging the decorator design pattern and ajax-based integration to provide taxonomy capabilities that are in a separate table, but within the Livelink database. This approach enables many types of application integration without mandating the use of Oscript to provide it. There is a new attribute type provided, which could enable the type of capability you describe. The AgileTaxonomy module has a dbconnection attribute type that allows you to specify a database relation ( one to one or one to many or even many to many ) to another table, which can reside on a Livelink database or another database. This may be an appropriate alternative to a dblookup type approach, especially if the data relationship is one where the field values are dynamic. The dbrelation approach is especially appropriate when the requirement is to have the related information accessible, but not have to worry about maintaining it in every document that refers to it, whenever it changes. This can be quite important for maintaining the integrity of the data relationship over time.The underlying methodology for the AgileTaxonomy and AgileApplications modules is the same, so every Category becomes a potential application as well, which opens up numerous possibilities for integration via the integrated triggers, rules and actions. I've attached the PDF of the handouts we used at the LivelinkUp conference, which provide additional information.