Simple basic module debugging by the book - how??

yaronlu

Hi,

I am a Newbee to OpenText and trying to create simple module according to the "Content Server IDE Plug-in for Eclipse Quick Start Guide":

https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/15080935/-15106263/15106294/15106295/16376487/42329092/cside/index.html

My problem is simple:

I want to add an "hello world" line in the root OS file,

but whatever i try, i cant get my breakpoint or my echo statement, get hit.

I know it is probably a trivial issue, but hey.. we've all been NewBees sometime in our career :-)

Can someone give me a simple step by step guidance in addition to the one I have in the link above?

Thanks 

Yaron

eLink User

I looked at thematerial and it is different from its predecessor the "addressbook module”.In that there was a good effort for a new developer who had installed 1) aworking livelink system 2) a installed builder to say spend 1 -2 days and get a"Hello World" out. Actually more than that.If you can get your handson the old builder documentation it "may" make more sense. Now CSIDEis a very new thing to Oscript Dev and I am no expert in this but here's howone does this. Where simple explanations are possible I have tried to indicate.

1.    A working livelinksystem  //oscript to be seen its output 

2.    A installedcside(eclipse) jar //to see src code

3.    Create a new"OScript" project specifying the OTHOME as the place where yourlivelink server is.

4.    If all goes well youshould see in CSIDE console debug lines and almost at the end "Serverstarts on port 2099". if livelink was running it would ask should I stop, youshould that is your development mode.

5.    Oscript explorer theraw OS files side these get compiled to a single .oll on the livelink(moduleexplorer) side.

6.    Module Explorer therunning compiled oscript usually oll's in windows. Note if this side does notshow your working module after you have "installed" your module thenlivelink "does not" know your module.

7.    Without further adocreate a new "module" and resist the temptation of doing anythingsubstantial to it.If all goes well your module will be seen in /staging oflivelink with a <module>.ini .Perhaps follow the screen shot in the CSIDEdocumentation.

8.    Now install it byrunning?func=admin.installmodule you have to re-start the livelink server,CSIDEhas a convenient stop /start(Red/Green) on the module explorer side. Now savethis .oll or rather the module itself to a safe location. You will thank me ina later date.

9.    Now see the oscriptexplorer side and the module explorer side.On the right if your module appearsin all its red iconic glory and on the left on the oscript explorer side your modulenow looks like Objects. You can know because for e.g. the WebModule will have +uses and you can expand them. They are your objects.See OT screen shots.

10.  Now if you a write a"Hello World" in your Root object and you "compile" usingautomatic build or clean build you will see your "Hello World" when the server starts up or inthread0.out log.

And before OT peoplereprimand me if the intent of that documentation is to get a new programmer getup to speed in development consider a recorded video for that. Most of theoscripters in the world including me attended training at some time or theother so if you do not get a full grasp of how livelink programming works itmay cause you to have more doubts.

Things absolutely onemust not do experienced or starter

1. 1.    Do not change code inany vended modules whether OT or private Vendor.Create your module and “override”objects properly.Search "CUSTOMIZATIONS_RT" for a approach.
   
2. 2.    Always back up thelivelink server side on your dev VM ,many times mis compilation will render a  unusable livelink system. CSIDE throws more dump files than the older environment.
   
3. 3.    See the screenshots inthe OT Document so you can know the Oscript explorer side vs the livelinkmodule explorer side.
   

4.    Familiarize coreconcepts like Request Handlers, WebNodes,Its Actions, Subtypes(new node types)etc. above all try to see if you can debug a call from the GUI to oscript andout.

 

Awesome new paradigmof oscript dev by Christopher Meyer(schwiiz.org)

 

   Simple basic module debugging by the book - how?? 

Hi,

I am a Newbee to OpenText and trying to create simple module according to the "Content Server IDE Plug-in for Eclipse Quick Start Guide":

https://knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/15080935/-15106263/15106294/15106295/16376487/42329092/cside/index.html

My problem is simple:

I want to add an "hello world" line in the root OS file,

but whatever i try, i cant get my breakpoint or my echo statement, get hit.

I know it is probably a trivial issue, but hey.. we've all been NewBees sometime in our career :-)

Can someone give me a simple step by step guidance in addition to the one I have in the link above?

Thanks 

Yaron

Modified on: 04/26/2015 02:42 AM

..appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937