Problems installing modules developed in Builder (on Win2000) to a Livelink Server on Solaris

Marcelo_Cesario_(azertiauser6_-_(deleted))

I have developed a simple module on Livelink Builder (running on Windows 2000) and I've installed it on the Livelink in my SDK computer without any problem. When I take this module and try to install it on my production site that is running on Solaris (LL version 9.0.0.2), as soon as I copy the folder to the STAGING folder, the Administrative page to install modules in Livelink stops working and presents an ERROR message. Any ideas to help me?!. Thanks.

Find more posts tagged with

Comments

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

That problem is caused by not doing a d2u on the modules ini file.

The nex problem you will run into is that you have to remove the .oll and .xdb extensions from the files in the ospace directory.

Hans Stoop

----------------------
Livelink Appearance is shown at
LivelinkUp Europe 2003
Open Text User Conference
Paris, France
May 12th - 15th 2003

Find out how we're helping six million great minds
work together to improve efficiencies and save money.

http://www.opentext.com/livelinkup/

-----Original Message-----
From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: vrijdag 14 maart 2003 20:46
To: eLink Recipient
Subject: Problems installing modules developed in Builder (on Win2000) to a Livelink Server on Solaris

Problems installing modules developed in Builder (on Win2000) to a Livelink Server on Solaris Posted by AzertiaUser6 (Ocampo, Alberto A) on 03/14/2003 02:32 PM

I have developed a simple module on Livelink Builder (running on Windows 2000) and I've installed it on the Livelink in my SDK computer without any problem. When I take this module and try to install it on my production site that is running on Solaris (LL version 9.0.0.2), as soon as I copy the folder to the STAGING folder, the Administrative page to install modules in Livelink stops working and presents an ERROR message. Any ideas to help me?!. Thanks.

eLink User

Message from Sean M. Alderman via eLinkYou can run -$ perl -ne 's/\r\n/\n/g' -i .inito replace the CRLF's windows makes with LF's.also you'll want to $ mv /ospace/.oll /ospace/On Fri, 2003-03-14 at 14:46, eLink Discussion: Development Discussionwrote:> Problems installing modules developed in Builder (on Win2000) to a Livelink Server on Solaris> Posted by AzertiaUser6 on 03/14/2003 02:32 PM> > I have developed a simple module on Livelink Builder (running on Windows 2000) and I've installed it on the Livelink in my SDK computer without any problem. When I take this module and try to install it on my production site that is running on Solaris (LL version 9.0.0.2), as soon as I copy the folder to the STAGING folder, the Administrative page to install modules in Livelink stops working and presents an ERROR message. Any ideas to help me?!. Thanks.> > [To reply to this thread, use your normal e-mail reply function.]> > ============================================================> > Discussion: Development Discussion> https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=view> > Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe--Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795Life is like a 10 speed bicycle. Most of us have gears we never use. --C. Schultz

INACTIVE_Malla_Reddy

Hello Hans,

We followed the same procedure and be able to install the module in solaris machine.

Problem Description :

In our windows environment all the pages(<customModule>.RHName) are loading without any issues,

but after deploying to Solaris machine it is opening only a blank page.

Can you please suggest us how can we trace out the issue, as we are not having any option to debug in Solaris operating system for the custom module.

Pramod_Mohandas

Hi,

While deploying onto a UNIX environment which in this case is Solaris, did you first prepare the module for deployment?

You are advised to;

<![if !supportLists]>1. <![endif]>Remove the .oll extension from all OSpace files.

<![if !supportLists]>2. <![endif]>Run a dos2unix converter on all other files in your module.

I believe that step #1 should suffice in this case, if not go ahead with step #2 as well.

Thanks & Regards,

Pramod Mohandas

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Thursday, February 27, 2014 8:58 PM
To: eLink Recipient
Subject: Problems installing modules developed in Builder (on Win2000) to a Livelink Server on Solaris

Problems installing modules developed in Builder (on Win2000) to a Livelink Server on Solaris

Posted bymalla.reddy@ge.com (Reddy, Malla) On 02-27-2014 10:14

Hello Hans,

We followed the same procedure and be able to install the module in solaris machine.

Problem Description :

In our windows environment all the pages(<customModule>.RHName) are loading without any issues,

but after deploying to Solaris machine it is opening only a blank page.

Can you please suggest us how can we trace out the issue, as we are not having any option to debug in Solaris operating system for the custom module.

[To post a comment, use the normal reply function]
Topic:	Problems installing modules developed in Builder (on Win2000) to a Livelink Server on Solaris
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful.

Kyle_Swidrovich

Good news is that for CS 10.5+, you’ll be able to use Eclipse to debug Content Server, so you’re not just restricted to Windows anymore.

eLink User

It is probably a stupid question, but are you compiling the ospaces for the UN*X target? I mean there is on .oll file extension present on UN*X. It's not possible just copy the staging folder from Windows to Solaris. (You probably couldjust rename the files, though.)--- Ferda