Unable to import SourceCode from OLL

I am trying to setup a new Oscript project in Eclipse. Copied the CSIDE jar in Eclipse plugins directory, and have created a new oscript project. When I go to import, and select 'import sourcecode from OLL' there are no modules present in Elcipse for me to select for installation.Please advise on how to complete the setup.

Find more posts tagged with

Comments

Dimple_Warke

Also I see some error messaged when eclipse is launched -

'Unable to launch Oscript Configuration'

'D:\Webapps\OpentextBrazil\bin\lldebug.dll.The specified procedure could not be found.'

Hany Samuel

This error indicates the VM can not run so the IDE basically can not start the server so for sure you can not import your module then or in fact do any work. Why this happens ? If you can provide some information about your installation we can work that out.

eLink User

Here are a few things that come to mind.

Your livelink server should be completely functional that is if you are a developer and you know the Admin and password you should be able to login.Preferably for a dev environment you want to keep it simple and use livelink userid/password as login method.This means that in your logs area you should not see trace files...I would start and stop that completely so that everything is stable.Note if you use OTDS for user authentication all the way I have no idea,but newer livelink servers allow an integrated OTDS which gets loaded into the Admin services which has to run for that to work.The idea is to see the last lines server started on 2099 awaiting requests... something around those lines
Now find a java and an eclipse that OT supports.I run eclipse LUNA and a stable jre java version "1.7.0_71".I run the com.opentext.cside_10.5.4.235.jar seems old but I have gotten used to its idiosyncrasies.
in old jars you probably do not want to create projects in the eclipse path what I mean is if your eclipse folder is e:\eclipse then your workspace be something like c:\workspace or even e:\workspace.
Then when you start eclipse with the plugin it will emulate the old builder command "Server is running do you want to shut it down" say 'Yes' and look at the console logs it should stabilize after quite a long time if you many modules and tonnes of patches to "23:24:12,040 INFO Server starts on port: 22099" I run my lapi port on 22099 that is why I see it like that.
I always check my <OTHOME> for the presence of huge mdmp(0.5 GB and up) files with almost no discernible info.You are supposed to let OT know and then they will analyze the dump.In the interest of time I just delete and move on.What we have noticed and reported to OT is when this occurs the whole env appears to be in a sorry state of mind and what you think is compiling but never gets compiled or you corrupt the running oll. Once you have a corrupt oll then the source code side or the module explorer will not load your module so you are kind of in a real mess.We created work arounds for that as well.This file is very important <your workspace>\.metadata\.log this gives OT key debug info.
Now if you follow the creation of a new project it will all work like magic.
If you want to import an oll then I believe you have to probably install it and be running as well load its dependencies.I am not too sure about that.As a practice I don't open OT modules unless I have compelling need to look at their code.

My suggestions are from my experiences about 8 months back and some new stuff I just tried.OT has provided tremendous improvement to the CS16 jar which I like and is probably much more stable.Your problems might just be from a bad install to start with so go along those lines.

.....appu appnair appunair

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

Dimple_Warke

Thank you for your suggestions! There was a IIS and folder level permission issue on the server because of which Eclipse on startup was not able to access the Opentext/cofig.ini file. When I installed Eclipse with cside jar on another environment it worked fine.