Reading values from opentext.ini

Can anybody please guide me as how to read and modify attribute and its values from opentext.ini using Oscript? An example code would be greatly appreciated.

Find more posts tagged with

Comments

Appu_Nair

are you saying that you have a prefs section for eg[options]wantDebug=trueand programmatically you want to dowantDebug=false is that the jist of your qn.There is an example in builder fileprefs section.I really think it is very expensive to refresh prefs maybe some other builder programmers would comment.You could try storing the value in KINI and read that and update it there so even if your code was running on different machines you have a single source you can maniplualate.Here's the code form the builder documentation.Here is an example which demonstrates how easily Fileprefs are created and used:String fname = "c:\tmp\s.prefs"List names = { "color", "name", "date", "count", "somepath" }List values = { "blue", "Joe", Date.Now(), 4, "c:\tmp\s.txt" }List sections = { "colors", "misc", "agents", "misc", "misc" }Integer iFileprefs fString nameString sectionDynamic valueAssoc readvalsif ( !IsError( Fileprefs.Create( fname ) ) ) if (!IsError( f = Fileprefs.Open( fname ) ) ) for ( i = 1; i <= Length( names ); i += 1 ) value = values[ i ] if ( Type( value ) != StringType ) value = Str.ValueToString( value ) end Fileprefs.AddPref( f, sections[ i ], names[ i ], value ) end Fileprefs.Close( f ) f = Fileprefs.Open( fname ) sections = Fileprefs.ListSections( f ) for section in sections readvals = Fileprefs.ListValues( f, section ) for name in Assoc.Keys( readvals ) value = Str.StringToValue( readvals.( name ) ) if ( IsUndefined( value ) ) value = readvals.( name ) end Echo( "[", section, "] ", name, '=', Str.String( value ) ) end end Fileprefs.Close( f ) else Echo( "Could not open " + fname ) endelse Echo( "Could not create " + fname )endI will post the example using kini shortly I can't find it now

sıɹɥɔ

Message from Chris Webster <cwebster@opentext.com> via eLink

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

To work with the opentext.ini file you should use the $KERNEL.SystemPreferences object. Typically you just want to set and get values having a known name. So, for example, if you want to obtain the name of the Livelink server your code is executing in it would be:

echo ($KERNEL.SystemPreferences.GetPrefGeneral ("DisplayServerName"))

If you want to save preferences for your module and later retrieve them:

$KERNEL.SystemPreferences.AddPref ("myModuleName", "myPreferenceName")

echo ($KERNEL.SystemPreferences.GetPref ("myModuleName", "myPreferenceName"))

Check the features of the object for other operations that are available. (Note that saving preferences in opentext.ini is not cluster-aware.)

The opentext.ini file has a format known as a "Fileprefs" file in OScript. There is a Fileprefs package that allows OScript code to manage such files (and is used by the above object). The package is documented in:

.../builder/documentation/packages/fileprefs.html

with example code. If you were wanting to create your own .ini file you could use this package directly, or instead orphan the FilePrefsObject in $KERNEL, just like the SystemPreferences object does, and use its script features.

Hope this helps,

-chris

From: eLink Discussion: Livelink Builder Discussion [mailto:componentbuilder@elinkkc.opentext.com]
Sent: Wednesday, January 14, 2009 10:46 AM
To: eLink Recipient
Subject: Reading values from opentext.ini

Reading values from opentext.ini

Posted by lloydsuser2 (Kashelkar, Vishal) on 2009/01/14 11:44

Can anybody please guide me as how to read and modify attribute and its values from opentext.ini using Oscript? An example code would be greatly appreciated.

Appu_Nair

The one's I was referring was CAPI.IniGet & CAPI.iniPut a lot of examples can be foound in builder code

Hans Stoop

Message from Hans Stoop <hstoop@opentext.com> via eLink

eLink

Hi Vishal,

Some additional information to the use of opentext.ini and the KIni table.

The values stores in opentext.ini are local to the Livelink instance. The values are cached, so any changes to them requires a restart of the Livelink service. (The thread that updates the opentext.ini will have th enew value, but the other threads do not. The builder uses only 1 thread!). Changes to opentext.ini must be applied manually to all available Livelink installs. Certain settings may be local to a Livelink instance and these must be put in opentext.ini.

Storing values in KIni will make the value available to all Livelink instances of a Livelink cluster. If you do not use caching of the values, then all the changes will automatically be available to all Livelink servers and threads without th eneed to cache. If the values are cached then you also need to restart the Livelink services.

Starting from LES 9.7.1 a caching mechanism is implemented by the Livelink server itself. When a change is made to the KIni table then all the Livelink servers in a Livelink cluster are notified and will update the cache. This makes things easier for administrators, but the refresh of the KIni cache is an expensive operation. Therefore you should not use KIni to store progress or auditing information that changes frequently. Because that will slow down the performance.

Hans

Von: eLink Discussion: Livelink Builder Discussion
Gesendet: Mi 1/14/2009 5:46
An: eLink Recipient
Betreff: Reading values from opentext.ini

Reading values from opentext.ini

Posted by lloydsuser2 (Kashelkar, Vishal) on 2009/01/14 11:44

Can anybody please guide me as how to read and modify attribute and its values from opentext.ini using Oscript? An example code would be greatly appreciated.

[To reply to this thread, use your normal E-mail reply function.]
Discussion:	Livelink Builder Discussion
Livelink Server:	knowledge-wlweb01

To Unsubscribe from this Discussion, send an e-mail to mailto:unsubscribe.componentbuilder@elinkkc.opentext.com?subject=Unsubscribe.

John W. Simon, Jr.

just a "build" on Chris' answer. On the end of the GetPref you can specify a default value...which only comes into play if it can not find the entry in the INI.

sıɹɥɔ

That's a useful parameter to use John, thanks for mentioning it.By the way I made an error in the code snippet I posted earlier. I said:$KERNEL.SystemPreferences.AddPref ("myModuleName", "myPreferenceName")when I should have said:$KERNEL.SystemPreferences.AddPref ("myModuleName", "myPreferenceName", "myPreferenceValue")System preferences and this object are documented in the Livelink SDK help at:.../builder/documentation/moddevguide/mdg_sysprefs.html

Support_Lloyds_Register

Dear Hans, Apu, Chris, John,Thank you very much for your support on this.Now i will try building up a project using your tips.I Will email you in need of any help.Have a great day