Updating a Module's Version?

Deepika_Kowkuntla_(nidauser2_-_(deleted))

What is the sequence of actions when you want to update a module's version number? The documentation only discusses the version number in the context of a brand new module. It looks like both the orphaned WebModule.fVersion feature and the module directory name need to be updated but is the sequence that these items are changed important so the system stays in synch? It looks like the WebModule.0DumpModuleConfigToFile method needs to run sometime in this process as well to update the INI file.

Find more posts tagged with

Comments

Deepika_Kowkuntla_(nidauser2_-_(deleted))

I have tested using the procedure below and it works. It may not be the optimal technique. If others have suggestions for improvement, please post a reply.1) Open Builder.2) Unlock the Ospace.3) Update the value in Webmodule.fVersion.4) Execute WebModule.0DumpModuleConfigToFile.5) Execute Globals.BuildOSpace.6) Close Builder. 7) Open the Livelink Administrator.8) Uninstall the module.9) In the OpenText\staging directory rename the module directory to the new version (e.g., mymodule_x_y_z)10) Go to the Administration Install Module page (the uninstalled module might still list the old version number).11) Install the module.The list of installed modules should now list the updated version number.

Jeff_Lang_(lang_(Delete)_2245920)

Instead of uninstalling the module you would be better off copying the folder from the modules directory to the staging directory and changing the name on the copy. You don't want to uninstall because if the module adds schema to the database the uninstall will drop the tables and your data will be lost.

eLink User

Message from magnus <<A HREF="mailto:magnus@ids.se">magnus@ids.se> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Is there a possibility to set up so that an uninstall will have an option to delete a table or not ....

I have down an Yellow pages applications where we add data to a an extra table where it would be nice

if there was an option to delete the table ....

magnus@ids.se

----- Original Message -----

From: eLink Discussion: Development Discussion

To: eLink Recipient

Sent: Friday, April 27, 2001 7:38 AM

Subject: Re this procedure works

Re this procedure works Posted by lang (Lang, Jeff) on 04/27/2001 01:33 AM
In reply to: This procedure works Posted by NIDAUser2 (Huelskamp, Paul) on 04/26/2001 02:21 PM

Instead of uninstalling the module you would be better off copying the folder from the modules directory to the staging directory and changing the name on the copy. You don't want to uninstall because if the module adds schema to the database the uninstall will drop the tables and your data will be lost.

Jeff_Lang_(lang_(Delete)_2245920)

The way the module installer works is to just the install scripts on install and the uninstall scripts when you uninstall. If you write your module correctly then the uninstall scripts should remove any additional tables that are added to the schema.You shouldn't have to uninstall modules for an upgrade, just make sure that the upgrade code in the module is correct.

eLink User

Message from Sean M Alderman via eLinkSince we're on the subject of making a module install/uninstall...Is there any decent documentation on doing this? Something that might include how to make sure the dependencies are listed, how to create/delete any DB schema the module needs, as well as anything else that should be done during install/uninstall?We have a couple of modules that need some fixing up, and I'm just not clear on how to do it.At 12:48 AM 04/28/2001 -0400, you (eLink Discussion: Development Discussion) wrote:>Re uninstalling Modules>Posted by lang on 04/28/2001 12:44 AM>>The way the module installer works is to just the install scripts on install and the uninstall scripts when you uninstall. If you write your module correctly then the uninstall scripts should remove any additional tables that are added to the schema.>>You shouldn't have to uninstall modules for an upgrade, just make sure that the upgrade code in the module is correct.>>[To reply to this thread, use your normal e-mail reply function.]>>============================================================>>Topic: Updating a Module's Version?>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2503375&objAction=view>>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-2795

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

I have been playing around with Livelink Rendition and if you uninstall it you still get all the PDF files in deversdata vertype = I would say that a module uninstallation should delete that Any comments ....RegardsMagnus@ids.se

Deepika_Kowkuntla_(nidauser2_-_(deleted))

This topic is the best documentation I have found so far. Thanks to all for all of the feedback! Let's hope the Java-based LL V10 has this subject better documented ;-)paul