Custom Module Not Available to Insall

gregory_lloyd

Hello,

I am trying to write a custom module and am following the Builder tutorial precisely except for the module name.  I beleive I have done everything correctly but cannot see my module on the Admin page.

My .ini file looks like this:

[dependencies]
requires_1={'kernel',10,10}

[description]
moduleName=iqbghowcoutils
Name=IQBGHowardCountyUtilities
Version=10.0 d 0

[install]
Url=func=iqbghowcoutils.configure&module=iqbghowcoutils&nextURL=%1

[OSpaces]
ospace_1=iqbghowcoutils

My staging folder has only one subfolder named iqbghowcoutils_10_0_0

in that folder are:

subfolders: html, ospace, and support

the .ini file is also in this folder

ospace contains iqbghowcoutils.oll

I have built, saved, closed, restarted services and cannot get the module to appear.

How can I debug?  What else should I look at?

Thanks

Greg

 

Appu_Nair1

Is your LLserver you are developing a 10 or a 10.5  if you are developing code for 10.5 or CS16 then builder is not the tool to do it.So any inferences from old builder documentation should be  taken with a pinch of salt. At the end of my post I have included a link to a utility script.CSIDE(Oclipse) incorporates that kind.Assuming you are sincerely on Builder(Livelink 10 and backwards) my post can be read.

requires_1={'kernel',10,5} each LL server can only run the kernel it is made with but Cs10 modules can be loaded into CS10.5 by changing the kernel number.I doubt if 10.5 will work in 10 withoutr some work.

I assume you have not forgotten to "Build Ospace",SetRequesthandlers,maybe enable the objects,if you locate f__initobjs in your "Globals" do you see the stuff you apparently did there? like in inspect?

Here are some tips I know not whether it will jive but coming from a developer who has gone throughh the pains before.

1. Staging should contain only modules starting with <modulename>_10_0_0 also if you have numbers or something which I think you don't it will cough up.
2. When you run builder on this machine you should get the startup correctly like it should say starting on 2099 waiting for requests .If the builder loads like only 1/3^rd of the tree lights up it is basically some problem happened that caused the loader to go cuckoo.
3. Staging really should not contain zip files and other things that will confuse the server.Most of the times a SDNR would result in that case
4. Many times windows if you extract a module will place <modulename>_10_0_0 and a sublevel <modulename>_10_0_0 livelink is expecting a first level shell and then all the others .
5. Last resort...Here's a "Make New CS10 Module" script that is handy to make a shell it works in my env,if you are new to it put this under /scripts and then restart builder.If the script file is compilable you should see a link called "Make New CS10 Module" in your tools menu and thank the previous great developers of OT and others. "Make New CS10 Module.lxe" can be accessed via the following link: https://knowledge.opentext.com/knowledge/cs.dll/properties/63120126
6. Above all before doing anything in LL backup the <OTHOME> before you develop.The advice and script I give contains no warranties whatsover:)