Upgrade of custom module

Nuno Silva

Hello everyone,

I'm upgrading a Content Server from 9.7.1 to 16.2 and it has a few custom modules.

As in version 9 the modules were done in Builder, how is the better way to rebuild this modules?

I tried through Eclipse+CSIDE but I couldn't get the clean source code from .oll files.

Thanks in advance,

Nuno Silva

Find more posts tagged with

Comments

Appu Nair

It is not a given but what I had to do in 971 to 10/10.5 is like this. Haven't done any 16 but 16 and 10.5 is very similar both 64 bit starting with 10. 9.7 is 32 bit.

The Source 971 code which came from the"obsolete" Builder

I looked to see if the module was containing simple code like RH's, WebNodeActions etc
I then isolated things OT had deprecated in 10 or higher mental note.
Most of our modules were simple enough although a few had really complicated things

The "Beautiful" CSIDE of things

Attempted to change the ini file to reflect the correct kernel and dependencies
Installed the module on 10/10.5 if it installs chances are you can decompile
Used the import / utility on the source side to get int into the "beautiful" OS files
Try changing things and do a force recompile.I think I created a simple script file to help with recompiling all the individual objects just in case.
Made changes changing the versions etc so it looks professional.

The hard ones ranged from making sure the builder module was built without the offending objects and a lot of circus..

I had to do things in 971 like export to ascii,remove things by hand like bad dependencies etc,import it back so 971 is clean and then approach it in CS10 conversion.

Some extremely bright Oscript houses know that LL Oscript is compatible between old systems and new systems(for e.g GCI/http://schwiiz.org/?p=1989; (Chris Meyer) ) so they have built their own dev tools to handle the transition .For me at least I was doing the poor man's way and what looked logical to me.

Appu Nair
Principal Architect | Alitek
Website: alitek.com

From: eLink Entry: Content Server IDE Development Forum <contentserver-ide@elinkkc.opentext.com>
Sent: Wednesday, February 28, 2018 9:47 AM
To: eLink Recipient
Subject: Upgrade of custom module

Upgrade of custom module

Posted by nuno.silva@ixopen.pt (Silva, Nuno) On 02/28/2018 10:41 AM

Hello everyone,I'm upgrading a Content Server from 9.7.1 to 16.2 and it has a few custom modules.As in version 9 the modules were done in Builder, how is the better way to rebuild this modules?I tried through Eclipse+CSIDE but I couldn't get the clean source code from .oll files.Thanks in advance,Nuno Silva

[To post a comment, use the normal reply function]
Forum:	Content Server IDE Development Forum
Content Server:	My Support

Confidentiality Note: This message contains information, which may be privileged or confidential, or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee responsible for delivering the message to the intended recipient, you are hereby NOTIFIED that any dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you receive this message in error, please notify sender immediately.

John Simon

Quoted Nuno Silva on 03/01/2018 08:44 AM:

I tried through Eclipse+CSIDE but I couldn't get the clean source code from .oll files.

Can you say more about what this means? Why were you not able to get source code?

I just finished a project where we converted 30+ modules from CS10 to CS16.2. I started out converting modules doing the import thing but quickly changed over to recreating the module from scratch in CS16:
- I could not always get the old module to install in CS16, and if I was not able to install it then I was not able to import it (if anyone knows how to import a module you cannot install please share!)
- Imported code does not create packaging. I like packaging because it allows me to group code into units that make sense to me.
- Imported code (at least in the past) often renamed objects (the _1 problem)...though I think I heard this may have been corrected with the most recent dropin
- Over time I learned better oScript techniques, but I never seem to find time to go back and "fix" old code. Recreating the module allows me the opportunity to clean things up.
- Recreating the module is not as bad as it sounds. I would open a CS10 system (in one VM) and a CS16 system (in another VM) which made it very easy to cut and past code between the two sessions (so it is not like I had to rewrite every line of code).

Anyway, just my take. My colleagues did the import and adjust routine (created packages, refactored, etc.).

Cheers...

Chris Meyer

*.kc { font-family: Helvetica , arial , sans-serif; font-size: 16.0px; line-height: 1.6; background-color: rgb(255,255,255);}*.kc a { color: rgb(65,131,196);}*.kc a.absent { color: rgb(204,0,0);}*.kc a.anchor { display: block; padding-left: 30.0px; cursor: pointer; top: 0; left: 0; bottom: 0;}*.kc h1, *.kc h2, *.kc h3, *.kc h4, *.kc h5, *.kc h6 { margin: 20.0px 0 10.0px; padding: 0; font-weight: 700;}cursor:text {}position:relative {}*.kc h1:hover a.anchor, *.kc h2:hover a.anchor, *.kc h3:hover a.anchor, *.kc h4:hover a.anchor, *.kc h5:hover a.anchor, *.kc h6:hover a.anchor { text-decoration: none;}*.kc h1 code, *.kc h1 tt { font-size: inherit;}*.kc h2 code, *.kc h2 tt { font-size: inherit;}*.kc h3 code, *.kc h3 tt { font-size: inherit;}*.kc h4 code, *.kc h4 tt { font-size: inherit;}*.kc h5 code, *.kc h5 tt { font-size: inherit;}*.kc h6 code, *.kc h6 tt { font-size: inherit;}*.kc h1 { font-size: 28.0px; color: rgb(0,0,0);}*.kc h2 { font-size: 24.0px; border-bottom: 1.0px solid rgb(204,204,204); color: rgb(0,0,0);}*.kc h3 { font-size: 20.0px;}*.kc h4 { font-size: 18.0px;}*.kc h5 { font-size: 16.0px;}*.kc h6 { color: rgb(119,119,119); font-size: 16.0px;}*.kc blockquote, *.kc dl, *.kc li, *.kc ol, *.kc p, *.kc pre, *.kc table, *.kc ul { margin: 15.0px 0;}*.kc hr { border: 0 none; color: rgb(204,204,204); height: 4.0px; padding: 0;}*.kc body > h2:first-child { margin-top: 0; padding-top: 0;}*.kc body > h1:first-child { margin-top: 0; padding-top: 0;}*.kc body > h1:first-child + h2 { margin-top: 0; padding-top: 0;}*.kc body > h3:first-child, *.kc body > h4:first-child, *.kc body > h5:first-child, *.kc body > h6:first-child { margin-top: 0; padding-top: 0;}*.kc a:first-child h1, *.kc a:first-child h2, *.kc a:first-child h3, *.kc a:first-child h4, *.kc a:first-child h5, *.kc a:first-child h6 { margin-top: 0; padding-top: 0;}*.kc h1 p, *.kc h2 p, *.kc h3 p, *.kc h4 p, *.kc h5 p, *.kc h6 p { margin-top: 0;}*.kc li p.first {}*.kc li { margin: 0;}*.kc ol, *.kc ul { padding-left: 30.0px;}*.kc ol *:first-child, *.kc ul *:first-child { margin-top: 0;}*.kc dl { padding: 0;}*.kc dl dt { font-size: 16.0px; font-weight: 700; font-style: italic; padding: 0; margin: 15.0px 0 5.0px;}*.kc dl dt:first-child { padding: 0;}*.kc dl dt > *:first-child { margin-top: 0;}*.kc dl dt > *:last-child { margin-bottom: 0;}*.kc dl dd { margin: 0 0 15.0px; padding: 0 15.0px;}*.kc dl dd > *:first-child { margin-top: 0;}*.kc dl dd > *:last-child { margin-bottom: 0;}*.kc blockquote { border-left: 4.0px solid rgb(221,221,221); padding: 0 15.0px; color: rgb(119,119,119);}*.kc blockquote > *:first-child { margin-top: 0;}*.kc blockquote > *:last-child { margin-bottom: 0;}*.kc table { padding: 0; border-collapse: collapse;}*.kc table tr { border-top: 1.0px solid rgb(204,204,204); background-color: rgb(255,255,255); margin: 0; padding: 0;}

Hi John,

(if anyone knows how to import a module you cannot install please share!)

As I've mentioned elsewhere I've created my own .oll -> .os conversion tool, which means I can create my CSIDE source files from Builder and simply add it to my CSIDE project. Contact me if you'd like to try it out.

Imported code does not create packaging.

It seems OpenText hasn't been able to reproduce this (see here), and it probably won't get fixed until they do.

Nuno Silva

Thank you guys!

I'm going to check how is the better way to resolve our upgrade of custom modules.

Then I'll share with you or ask you for more help.

Cheers,

Nuno