Edit OSpace

[cdfly]

Hello,
I've never used the LiveLink builder before. I need to be able to edit an ospace and then export it to another directory. I make the changes to the ospace, compile and save it but when i open it back up in the builder my changes are not there. Can someone give me the steps on how to compile the changes and then be able to move it to another directory?

Thanks

 

[ggriffit]

cdfly,
I suggest that you attend the Builder Training course (

http://www.opentext.com/training/coursedetails.html?id=1535),

or get someone who knows Builder to help as this what you are doing is a relatively simple task to achieve.

Generally we don't just update the provide DLL's we orphan/override/patch them for support, so you will need to learn how that works.

if you have the OnLine Help for the Builder then there is a tutorial module that is worth the time getting to know inside out.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[cdfly]

Thanks.
I am scheduled to go to training this is just a task that came up. I'll google/look at the online help and see how to do this.

 

[ggriffit]

You will find almost nothing on Google, the OnLine help, KC Discussions at

https://knowledge.opentext.com/know...2120228/customview.html?func=ll&objId=2120228

are probably your best bet.

If you can provide more detail on what you are trying to do we may be able to give you a step list.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[cdfly]

Thanks for that link I'll check it out.
All I really need to do is change the permission in one of the scripts. Changing it is no problem, it's just saving it off so I can put it on the production server
I need to change

.fPerms = $PSee

TO

.fPerms = $PSee + $PSeeContents+$PModify+$PCREATENODE

 

[ggriffit]

Suggest you do this as an Override or a Patch rather than updating the Core LL OSpace, see

http://communities.opentext.com/communities/llisapi.dll/open/7960634

for the latter.

If this is a Custom module then you should be able to update and recompile it.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[appnair]

General steps on builder.
Find the ospace that you want to change something
find the ospace or feature that you are changing,write it down.
create a new module to hold your customization.
make sure you can install it without fail.
Open your ospace and orphan the object form the other ospace you are cahnging.
If there is .fenabled make it true and make sure it stays true
Change your script and put an echo statement to make sure when the other one is called your script is called.
Compile script if errors are there it will not compile.
Build ospace in the Globals object,this is why your saves are not getting saved even in the other ospace.
save or exist builder.

Do not take this as the panacea because different things/objects are done differently.As a matter of principle you should not open ospaces that OT producd or vendor produced because it will then be compiled by the oscript compiler of builder in your computer and may not work,so please back up the whole opentext tree before any dev.

Also good to know that you are atking up training that should clarify a whole lot to you.It is fun

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[cdfly]

Great. I appreciate all the help

 

[cdfly]

I created a patch using the steps in the link that ggriffit provided. The steps said to put the patch in the Livelink patch directory. My Livelink install does not have a patch directory, do I need to create that directory? Also will Livelink automatically pick up the patch or do I need to make a change to the .ini file

Thanks again for the help

 

[ggriffit]

if you don't have a patch directory, then you need to create one and simply drop the patch in there and on restart Livelink will pick it up. Remember that you will need to do this on EACH server you have.

I am a little suprised that you don't already have one as you should probably have applied a few patches including the latest monthly patch by now.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[cdfly]

Thanks. I just started on this project so I've never done any of the patches yet. I'll create that directory and see if my patches get put in

 

[ggriffit]

For the patches I was referring to the vendor / partner supplied ones rather than your own, the vendor ones can be found at

https://knowledge.opentext.com/know...patches_customview.html?func=ll&objId=3551049

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[cdfly]

I created a patch on my development machine, moved it into the patch directory and restarted the LLService and when I opened the module I was patching in the builder the changes were applied. I copied the patch onto a different box, restarted the service but the changes were not applied there. Is there something else I need to do when applying a patch on a different box?
Thanks

 

[appnair]

in the logs on the new server do you see your patch getting called.
If you put debug=2 and wantLogs=true you should see a lot of debug info one of them will say loading old style patch
if you put echo statments in your patch one can say for sure the patch got loaded.Are you by any chance using customizations_rt or some other advanced tools for this post your patch code so we can see what its going on with the patch and at least one of us can verify it works in our env or not.



Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[cdfly]

Ok, I'll take a look at the logs.
Thanks