UNABLE TO START OTCS AFTER DEVELOPING IN CSIDE

MarkedOne

Hi,

I kinda messed up the DEV env while playing with CSIDE in eclipse although I didn't to anything drastic.

What happened is that I imported DPS module and WEBADMIN to the srcmodules since I was looking to customize some DPS element. Then I created a new module in that folder and orphaned Utils.os from DPS to the module I've just created. Afterwards I kinda wanted to start from scratch and deleted all the modules that I've imported to the srcmodules and deleted manually my custom module from the OPENTEXT/staging folder. Afterwards the OTCS won't go up and the ECLIPSE is unable to start the server aswell.

Wanted to know if anyone has an idea of what the problem might be with the following screen shots that I took?

any idea what is DBWIZAPI?

Thanks.

appuq

See my reply and @Dave Carpeneto to get a feel for what you may end up doing…I m posting this in an attempt to help and not going to try to explain what the current error is :)

https://forums.opentext.com/forums/developer/discussion/312146/how-to-make-eclipse-working-more-predictable

If I had to guess most likely your module when one develops the module is in staging and you are supposed to install it, so from years of working with builder and cside here's some small housekeeping I do.

1. If I had to guess most likely your module when one develops the module is in staging and you are supposed to install it, so from years of working with builder and cside here's some small housekeeping I do.
2. I make a complete backup of <OTHOME>
3. I create the shell of a module and almost just run the wizard to completion won’t do anything at that step.
4. I shut down the builder and re-start it.
5. I go to the install module and my shell module is there to install
6. I installed it and re-start
7. Now my module shows up in the CS/CSIDE trees part of the startup
8. I made a note of the three lines in opentext.ini that the module has put this is a sign of a proper module. If not mistaken this would be the last items in that [module] section.Two or one there is almost a sign of a bad/module install. see an example

module_0=xecmqellus

ospaces_xecmqellus={'xecmqellus'}

xecmqellus=_16_2_3

1. The lines need not be contiguous but the numbers need to be . For e.g., if I had another module and it assumed module_1, if one had to manually uninstall module_0 one would have to manually re-number
2. OT has changed all their modules to go into the directory core, mostly customer modules may show up in the <OTHOME>\module
3. So to uninstall your module all you have to do is shut down the server move your module out comment or delete the 3 lines(obviously much more if it is DB schema inserting module and so on)
4. My guess is your opentext.ini has remnants of your failed /non-existing module.
5. BTW this used to be an exam question in administrator/developer of how to remove a module manually if it fails the ?func=admin.uninstallmodule procedure 😊
6. Now I start my research with my module installed in the system and not causing any problems
7. Orphan away
8. Compile
9. Cause havoc…

BTW if you import an OT vended module and mess with it the automatic project build may actually change OT code so either don't do that or have the auto-build turned off.

Your screencap looks interesting it broke on a line that it can't reconcile, it is thinking that there is schema in CS but no module about it this sometimes shows up in CS as "You have Chicken installed but no egg to go with it".Anyway I think you are brave for creating a module with a schema

DBWIZAPI- a high-level API that takes care of using client services like (ODBC, JDBC, drivers), etc that allows it to reach out to remote databases.Many things in Oscript we take for granted as Oscripters do not have access to many parts of it as they are black-boxed against us.Typically if you need to talk to the CS database like Dtree or something like that you will use CAPI(Connection API), DAPI(low-level Document), WAPI(workflow), LLIAPI(high-level API that stands for most everything that OT developers have produced)