How to customize LiveLink interface?

Goldman_Opentext_KC_Generic_#1_(GOLSAC02User1_(Del

we have a need to pass thru all livelink interactions via a portal (other than MyLiveLink). Instead of repainting all interfaces ourselves using LAPI, we just want to "punch through" from the portal to the LiveLink via livelink URL's for various objects and services.The only requirement is that we want to hide the livelink banners, some or all of its drop down menus etc. We then would like to add our own banners, and our own drop dowm menus etc.What is the best way to do it? Any documentation?

Find more posts tagged with

Comments

eLink User

Message from Kevin Ward via eLinkOne option you should look into rather than customizing Livelink itself isto use XML Skins. You can place get Livelink to export in XML instead ofHTML by specifying &transform in the URL. You can also specify a stylesheet for the XML in the url and place the style sheet in the Livelinksupport directory. An example url would be:...?func=ll&objid=2000&objaction=xmlexport&stylesheet=tree.xsl&transformThis way, your skin could display only the information you want in anyformat you want without modifying Livelink.Hope this helps.-----Original Message-----From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf OfeLink Discussion: Development DiscussionSent: Thursday, June 14, 2001 10:11 AMTo: eLink RecipientSubject: How to customize LiveLink interface?How to customize LiveLink interface?Posted by GOLSAC02User1 on 06/14/2001 10:07 AMwe have a need to pass thru all livelink interactions via a portal (otherthan MyLiveLink). Instead of repainting all interfaces ourselves using LAPI,we just want to "punch through" from the portal to the LiveLink via livelinkURL's for various objects and services.The only requirement is that we want to hide the livelink banners, some orall of its drop down menus etc. We then would like to add our own banners,and our own drop dowm menus etc.What is the best way to do it? Any documentation?[To reply to this thread, use your normal e-mail reply function.]============================================================Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

Any sample skins out there ?!?!?Can we get some cool Preview center with different skins ..../magnus@ids.se

Eric_Slaghuis_(sasoladmin_-_(deleted))

I agree, skins is the answer. I do however have a question. If I write a xsl (skin) and put it in the /livelinksupport/.... directory, and call it, it works fine. I read however that one can put the xsl (skin) on livelink as a document, and then call it by using the ObjectID as the reference. For example http:///livelink/livelink.exe?func=ll&objId=1309016&objAction=xmlexport&scope=one&stylesheet=1280206The problem is:My skin works if I put it in the livelinksupport directory, but does not work if I put it on Livelink and use the objectID method. Is there something I am missing, or is it the way I create my skins?

eLink User

Message from Andrea Ilari via eLinkI'll try and let you know.btw, this could be interesting - in terms of having a folder of xsl managedby a development team...-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: giovedi 5 luglio 2001 14:40To: eLink RecipientSubject: I agree, skins is the answer. I do however have a question. IfI write a xsl...I agree, skins is the answer. I do however have a question. If I write axsl...Posted by SasolAdmin on 07/05/2001 08:37 AMI agree, skins is the answer. I do however have a question. If I write axsl (skin) and put it in the /livelinksupport/.... directory, and call it,it works fine. I read however that one can put the xsl (skin) on livelinkas a document, and then call it by using the ObjectID as the reference. Forexamplehttp:///livelink/livelink.exe?func=ll&objId=1309016&objAction=xmlexport&scope=one&stylesheet=1280206The problem is:My skin works if I put it in the livelinksupport directory, but does notwork if I put it on Livelink and use the objectID method. Is there something I am missing, or is it the way I create my skins?[To reply to this thread, use your normal e-mail reply function.]============================================================Topic: How to customize LiveLink interface?https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2532665&objAction=viewDiscussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

eLink User

Message from magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hope you have seen that there is a training in Europe 9-10 of August in

building XML Skins

See http://www.opentext.com/training/course_description.asp?id=1066

If you are intrested contact email Christa Meeng cmeeng@opentext.com

Small warning for the price tag 1800 Euro for 2 days ...

/Magnus@ids.se

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

In order to make it work, you should make the following changes to the opentext.ini file:

Add text/xml to the entry relativeLinkMimeTypes. After the change It will look like:

relativeLinkMimeTypes=text/html,application/pdf,text/xml

If you do the transformation on the server, you shouldn't need to make this change.

Hans Stoop

--------------
Register your subtypes in the OScript Registry:
https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2454603
Consultant Partner Programs Europe
hstoop@opentext.com
+31 23 5652333
http://www.opentext.com/

-----Original Message-----
From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf Of eLink Discussion: Development Discussion
Sent: donderdag 5 juli 2001 14:40
To: eLink Recipient
Subject: I agree, skins is the answer. I do however have a question. If I write a xsl...

I agree, skins is the answer. I do however have a question. If I write a xsl... Posted by SasolAdmin (slaghuis, Eric) on 07/05/2001 08:37 AM
In reply to: RE How to customize LiveLink interface? Posted by eLink on 06/14/2001 10:27 AM

I agree, skins is the answer. I do however have a question. If I write a xsl (skin) and put it in the /livelinksupport/.... directory, and call it, it works fine. I read however that one can put the xsl (skin) on livelink as a document, and then call it by using the ObjectID as the reference. For example http://<server>/livelink/livelink.exe?func=ll&objId=1309016&objAction=xmlexport&scope=one&stylesheet=1280206

The problem is:
My skin works if I put it in the livelinksupport directory, but does not work if I put it on Livelink and use the objectID method.

Is there something I am missing, or is it the way I create my skins?

eLink User

Message from Slaghuis, Eric (E) via eLinkIn other words, I should call it with the &transform=1 parameter? I dothis, but still get the same result. If I do not include this parameter,Livelink gives me an error stating that the document /livelink/cannot be found, which is the expected reaction.I can see it is my skin that is being displayed, but it displays incorrectMaybe if you look at this attachment you will see my error. This skin listsall the folders in a xml export, and shows them as hyperlinks. Like I said, if I put this in the support directory it works, but if I putit in Livelink and use the ObjectID to reference it, I get a totallydifferent result. I only see the last part of the URL that I want toreference. If I hack the hyperlink out to just display the folder name, Isee nothing.-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: 05 July 2001 03:03To: eLink RecipientSubject: RE I agree, skins is the answer. I do however have a question.If I write a xsl...

eLink User

Message from Slaghuis, Eric (E) via eLinkThank you, but I am 10000km south of Europe ;-} Somewhere on the southernend of darkest Africa. Implying a US$500 plane ticket and acommodation inanother currency than our weak Rand. What is the chance of Skins training at LivelinkUp 2001. I have a slighthope to be there.-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: 05 July 2001 02:57To: eLink RecipientSubject: Skin training announced

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

I've stored your stylesheet in LL and run it on a folder without subfolders. My URL is

http://localhost/Livelink900/livelink.exe?func=ll&objId=57723&objAction=xmlexport&transform&stylesheet=59043

My result is:

<?XML:NAMESPACE PREFIX = XSL />?func=ll&objId=&objAction=XMLExport&attributeinfo&stylesheet=/livelinksupport/xsl/

Without the transform I get:

The system cannot locate the object specified. Error processing resource 'http://localhost/Livelink900/59043'. If you look at the XML file you see <?xml-stylesheet type="text/xsl" href="59043"?>.I expected it to be something like <?xml-stylesheet type="text/xsl" href="/Livelink900/livelink.exe/listfolder.xsl?func=doc.Fetch&nodeId=59043"?>.

So it doesn't seem to work.

-----Original Message-----
From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf Of eLink Discussion: Development Discussion
Sent: donderdag 5 juli 2001 15:41
To: eLink Recipient
Subject: RE RE I agree, skins is the answer. I do however have a questi on. If I write a xsl...

RE RE I agree, skins is the answer. I do however have a questi on. If I write a xsl... Posted by eLink on 07/05/2001 09:41 AM
In reply to: RE I agree, skins is the answer. I do however have a question. If I write a xsl... Posted by eLink on 07/05/2001 09:02 AM

Message from Slaghuis, Eric (E) <eric.slaghuis@sasol.com> via eLink

In other words, I should call it with the &transform=1 parameter? I do
this, but still get the same result. If I do not include this parameter,
Livelink gives me an error stating that the document /livelink/<objectID>
cannot be found, which is the expected reaction.
I can see it is my skin that is being displayed, but it displays incorrect

Maybe if you look at this attachment you will see my error. This skin lists
all the folders in a xml export, and shows them as hyperlinks.

Like I said, if I put this in the support directory it works, but if I put
it in Livelink and use the ObjectID to reference it, I get a totally
different result. I only see the last part of the URL that I want to
reference. If I hack the hyperlink out to just display the folder name, I
see nothing.

-----Original Message-----
From: eLink Discussion: Development Discussion
[mailto:development@elinkkc.opentext.com]
Sent: 05 July 2001 03:03
To: eLink Recipient
Subject: RE I agree, skins is the answer. I do however have a question.
If I write a xsl...

Eric_Slaghuis_(sasoladmin_-_(deleted))

Thank you for your answer Hans, but my question is still not answered. I played around with my stylesheet again, and included a header row in my table. This header row is displayed correctly. I even removed the hyperlink from my stylesheet, just attempting to list the folders.My conclusion: Allthough the feature exists in Livelink to manage your stylesheets for you, it does not work. For some odd reason it fails to transform the xsl correctly if the stylesheet resides on the server.Can someone confirm this? Should I end my quest for xsl skins on Livelink, and rather bribe the system administrator for rights to the /livelinksupport directory?Oh, by the way, the transform parameter must be included as server side transformation is the only way it can work. The server cant send down both the xml and the xsl in one call to the workstation to tranform it on the client side.

Andrea_Ilari_(DNMMIL011_(Delete)_2335380)

I think there are a number of things to keep in mind here.1. when you try to transform xsl client-side, you decide to rely on the xml parser of the user's browser.This, actually, means that you need that all your clients are Microsoft Internet Explorer; more than this, you decide to rely on MS's xml parser, that is different from the XML parser used by LL. LL (as far as I know) uses Xalan/Xerces (see jakarta.apache.org for details on these products), and the result can be different.2. I think that XML parser have different functionalities depending on the browser's version. The dll used is something like msxml*.dll, and the installed version depends primarily on which IE version you have installed.In other words, my idea is that the best way to have XML transformation is to have it done server-side.I tried to have the xsl stored in livelink, referencing it by objId, and it works without problems.Bye.

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hi Eric,

I changed the first two line of your stylesheet to

<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">

Now the stylesheet works if I do a server side transformation and the stylesheet is referenced by its object ID.

-----Original Message-----
From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf Of eLink Discussion: Development Discussion
Sent: dinsdag 10 juli 2001 7:38
To: eLink Recipient
Subject: Is it a bug or a undocumented feature?

Is it a bug or a undocumented feature? Posted by SasolAdmin (slaghuis, Eric) on 07/10/2001 01:36 AM
In reply to: RE I agree, skins is the answer. I do however have a questi on. If I write a xsl... Posted by eLink on 07/05/2001 10:51 AM

Thank you for your answer Hans, but my question is still not answered. I played around with my stylesheet again, and included a header row in my table. This header row is displayed correctly. I even removed the hyperlink from my stylesheet, just attempting to list the folders.

My conclusion: Allthough the feature exists in Livelink to manage your stylesheets for you, it does not work. For some odd reason it fails to transform the xsl correctly if the stylesheet resides on the server.

Can someone confirm this? Should I end my quest for xsl skins on Livelink, and rather bribe the system administrator for rights to the /livelinksupport directory?

Oh, by the way, the transform parameter must be included as server side transformation is the only way it can work. The server cant send down both the xml and the xsl in one call to the workstation to tranform it on the client side.

eLink User

Message from Slaghuis, Eric (E) via eLinkWould you be so kind to foreward me a copy of this xsl, that I may learn.My stylesheet keeps on giving the wrong results. (I allways use server sidetransformations, but have not managed a successfull one yet.)-----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com]Sent: 10 July 2001 09:03To: eLink RecipientSubject: I think there are a number of things to keep in mind here.I think there are a number of things to keep in mind here.Posted by DNMMIL011 on 07/10/2001 03:01 AMI think there are a number of things to keep in mind here.1. when you try to transform xsl client-side, you decide to rely on the xmlparser of the user's browser.This, actually, means that you need that all your clients are MicrosoftInternet Explorer; more than this, you decide to rely on MS's xml parser,that is different from the XML parser used by LL. LL (as far as I know) usesXalan/Xerces (see jakarta.apache.org for details on these products), and theresult can be different.2. I think that XML parser have different functionalities depending on thebrowser's version. The dll used is something like msxml*.dll, and theinstalled version depends primarily on which IE version you have installed.In other words, my idea is that the best way to have XML transformation isto have it done server-side.I tried to have the xsl stored in livelink, referencing it by objId, and itworks without problems.Bye.[To reply to this thread, use your normal e-mail reply function.]============================================================Topic: How to customize LiveLink interface?https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2532665&objAction=viewDiscussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

Andrea_Ilari_(DNMMIL011_(Delete)_2335380)

No problems... there is only a little problem, the text is in italian... I translated somthing, to help you understand something.I have a folder that I'm using to play with this XML/XSL thing. in this folder i have the "website.xsl", uploaded as a document. I use this xsl to show the contents of the folder. In the subfolder I use a category attribute to keep track of the xsl to use (see xsl source for details).Then I call the transformation using a URL like this:http://mylivelinkserver/livelink/livelink.exe?func=ll&objId=2533&objaction=xmlexport&attributeinfo&sort=name&stylesheet=9014&transformAs a minimum, you will need to get your objId and substitute it in the url.It should work... I hope.Bye.