Configure "ini" file

Hi
I have an application that uses the serial commnication. I'm running
this application in 2 PCs and they use diffrent serial ports. Can I
set the serial port that I want to use in the "ini" file? How can I
set the initial valor of a control before run the application?
thanks

try to use Configuration File VIs under File I/O menu.
Create a standart ini file stg like
[COMM] ; section name
PORT = 1 ; key
read this file using Configuration File VIs.
then initialize your control with that key.
ozan...
"Cheech" wrote in message
news:[email protected]..
> Hi
>
> I have an application that uses the serial commnication. I'm running
> this application in 2 PCs and they use diffrent serial ports. Can I
> set the serial port that I want to use in the "ini" file? How can I
> set the initial valor of a control before run the application?
>
> thanks

Similar Messages

  • Modification to Write Configuration .ini file

    I have found one of the annoying things about Labview's configuration file VI's is that when the configuration file is written, all spacing between sections is eliminated making it hard to read, even if the spacing was there to begin with when the file was read.  For example, I would like the file to look like
    [Header1]
    key1=value1
    key2=value2
    [Header2]
    key3=value3
    key4=value4
    But it comes out looking like:
    [Header1]
    key1=value1
    key2=value2
    [Header2]
    key3=value3
    key4=value4
    making it harder to read.
    I made a modification to the file Config Data to String.vi which is located \vi.lib\UTILITY\config.llb\
    Make a backup copy of \vi.lib\UTILITY\config.llb\Config Data to String.vi and replace the file in the config.llb with the attachment (saved as LV 8.0).
    What I did was any time a section header is to be written to the file, I preceded it with another CRLF character so that it creates a blank line just before the section header.  To keep from having an extra blank line at the beginning of the .ini file, it does not create the CRLF there.
    I hope others will find this modification useful.
    Attachments:
    Config Data to String.vi ‏26 KB

    tst wrote:
    The idea itself is great, but I don't like the idea of changing vi.lib files (for several reasons).
    I didn't look at your code, but I assume that at least in this case, the resulting files will still be processed fine by machines which don't have this modification, so it's probably not as bad, but I still don't like it.
    You should probably go to the Product Suggestion Center and tell NI about this idea.
    I agree about not trying to change the vi.lib files.  It gets into modifying code that is rather deeply embedded about 3 or 4 sub-vi's down.  By my testing, machines without the modification do handle the files just fine.  The alternative would be to create a backup copy of the whole library and rename the files and use my own versions instead. I've recently installed the OpenG files and looked into them.  I like the functionality they provide to be able to store and retrieve clusters of configuration data.  Of course they have NI's write configuration files at the heart as well, so if they link to the original VI library then they will generate the same .ini files missing the extra lines that I like.
    tst wrote:
    You should probably go to the Product Suggestion Center and tell NI about this idea.
    Thanks, I already did this some time ago when I created a test VI to just read and close an .ini file.  I found that without setting the "write configuration file" flag in the close config file VI (which defaults to True), the whole file got rewritten even though nothing had changed.  That's how I stumbled across this loss of blank lines thing.
    I hope NI will look into that suggestion and add it to the config file VI library in the future.  It would probably need to be implemented with a flag that says "Add blank lines?" that would default to False so that the original behavior of the VI could be maintained.  Since the VI that controls the appearance of the file is a few layers deeper than Close config file VI, that flag would have to be passed through a couple of sub-VI's.
    Thanks for your feedback.
    Message Edited by Ravens Fan on 09-22-2007 03:22 PM

  • Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration: Agentry Error

    Hello Experts,
    I follow the flightbooking tutorial to create a Material application to get material list. I  can start the agentry server but when I connect to SAP server and get data, I face below issue
    Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER
    I check the parameters name in SAP Agentry Config panel, all are correct. Why cannt it get the data. Do I have to add anything in javaBE.ini? Please help me. Thank you very much.
    My javaBE
    [HOST]
    server=be1.vdc.csc.com
    APPNAME=ZCH_MATERIALLIST
    [CLIENT_NUM]
    CLIENT=800
    [SYSTEM_NUM]
    SYSNUM=01
    [LOGON_METHOD]
    ; USER_AUTH if standard UID/Password authentication is used
    ; USER_AUTH_GLOBAL if pooled connections using single UID/Password is used
    ; USER_AUTH_GROUP if UID/Password authentication with SAP Message Server
    ;   (load balancing) is used
    LOGON_METHOD=USER_AUTH
    [GLOBAL_LOGON]
    ; referenced when LOGON_METHOD=USER_AUTH_GLOBAL
    ; uses a pool of connections to the SAP backend all utilizing a single
    ;    UID/password
    UID=
    UPASSWORD=
    SHAREDCONNECTION=0
    GET_PERSONNEL_INFO=
    [SERVICE_LOGON]
    ENABLED=true
    UID=hngu3
    UPASSWORD=xxxxxxx
    UPASSWORDENCODED=false
    [GROUP_LOGON]
    ; referenced when LOGON_METHOD=USER_AUTH_GROUP
    ; individual user authentication using an SAP Message Server which distributes
    ; client connections among a "group" of SAP application servers based on load
    ; balancing criteria
    ; host name or IP address of SAP Message Server
    MESSAGE_SERVER=
    GROUP_NAME=
    SYSTEM_ID=
    CLIENT=
    [LANGUAGE]
    LANG=EN
    [LOGGING]
    Level=4
    [REQUIRED_BAPI_WRAPPER]
    com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK
    com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT
    com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET
    com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET
    com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD
    com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD
    com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET
    com.syclo.sap.bapi.GetEmployeeDataBAPI=/SYCLO/HR_EMPLOYEE_DATA_GET
    com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL
    com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET
    com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD
    com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT
    com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL
    com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
    com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT
    com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL
    com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
    com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
    com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
    com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.TransactionCommitBAPI=WFD_TRANSACTION_COMMIT
    com.syclo.sap.bapi.SignatureCaptureBAPI=/SYCLO/CS_DOBDSDOCUMENT_CRT

    Hi Tahir, please help me check the log below
    Agentry Runtime Worker Thread###throwExceptionToClient::begin |
    Agentry Runtime Worker Thread###throwExceptionToClient::com.syclo.sap.material.steplet.MaterialSteplet::throwExceptionToClient::397::MaterialSteplet - Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER |
    Agentry Runtime Worker Thread###Exception: 17:15:35 06/17/2014 : 20 (Agentry3), Java Business Logic Error (com.syclo.agentry.BusinessLogicException: MaterialSteplet - Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER),  |
    Agentry Runtime Worker Thread###loggedOut::begin |
    Agentry Runtime Worker Thread###HNGU3: SESSION END |
    Agentry Runtime Worker Thread###BAPI::begin |
    Agentry Runtime Worker Thread###create::nulled repository::created new repository |
    Agentry Runtime Worker Thread###create::/SYCLO/CORE_MDW_SESSION1_DEL Connection ID: com.sap.mw.jco.JCO$Client@2656ed99 |
    Agentry Runtime Worker Thread###create::Function /SYCLO/CORE_MDW_SESSION1_DEL created |

  • How to configure the .ini file with applet

    hai
    i am using native methods in that methods they use some ip addresses. when i am using that native methods in applet run the applet using appletviewer tool it works fine but when i am open that applet using html page browser not configure that .ini file data .how to configure that .ini file with browser

    Hi Jay SenSharma,
    Thanks for your immediate response.
    I saw your URL links, But in your link give the recursive deployment using wlst. But my question is how to configure the oracle weblogic library files into Admin server & Managed Servers by using the wls.jar file through wlst script to create the new domain.
    But if create the new domain by using GUI mode then we manually give the admin server port number & managed servers port number and name.
    By default the library files are configured with the Admin server in GUI mode. But the Managed server the Library files are not configured with the Managed servers. Then we manually select all the library files to the corresponding managed servers. Then only the applications are deployed into the corresponding managed server.
    Regards,
    S.vinoth Babu

  • Memory leakage when using Ini-file VIs

    I'm using the Configuration File Vis to read and write data to different .ini files. The files contain both standard keys and clusters written as a segment using the Open G toolkit. Instead of opening the files and keeping them in the memory of the Config VIs I'm just using them to read and write, decode and encode...the references are all closed using the Close Config Data.vi. The problem is that even though immediately close the config data the application keeps grabbing more and more data...every time a configuration file is open, read or written to and the closed everything from 4K to 50K of additional memory has been allocated by the application (this is a stripped down application that only deals with the config files, so
    there are no other sources for the memory leak).
    Has anyone else experienced this? How can you repeatedly open and close config file slike this without it continoulsy allocating more memory?
    Attached is a copy of the VIs, the directory structure must be kept intact if the ini file is to be read correctly.
    I've been stearing so hard on this the whole day that I might just be overlooking something obvious...
    In the full application the VI init and write operations are only done when the user reconfigures the system, which may be a couple of times per month...so the memory leak would not cause a problem right away, but it would not be healthy to leave it there...
    MTO
    Attachments:
    Memory_Leak_Demo.zip ‏1391 KB

    Could you post a 6.1 version?
    LV7 is still about two weeks away for me.
    Does the problem show up in 6.1?
    I ran across an error while writting to a FP output that was not configured that would cause a "drop of memory" to leak every time the VI performed the write. The leak did not show up in the profiler but windows would show te memory foot print growing continually as long as the writes continued. The work around was "don't do that!".
    I bring this up because I found and reported this just prior to LV7 release and the featur may still be present in LV7. I also believe that Jean-Pierre used a "write and check" metod to detail with the unknown data types of of complex data structures.
    If you just read does it leak?
    If you just use simple data types do
    es it leak?
    Is the ini file growing?
    I really appreciate the effort you have been putting into the Dev-Exchange Mads! I wish i could do to more to help.
    Keep us posted.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • .INI files vs .TXT files for changing default values in a .EXE?

    Hi,
    I have a two-part question related to updating the default values of controls in an executable:
    I am creating a LabVIEW executable for installation on two different production-floor computers.   I need to be able to change the default values of the front panel controls (as I would do with the “make this value default” command during development). From reading prior posts, I understand that I could use the “Write Configuration Settings File.vi” and “Read Configuration Settings File.vi” to generate a .INI file that would be read by the .EXE and would establish the desired values of the controls. However when I took a look at the block diagrams for those configuration .VIs, they don’t appear (to me) to be any easier to use than just reading values from a spreadsheet file. IE: Instead of using these configuration files and a .INI file, could I not instead just read values from a .TXT file that contains the desired values?   I’ve never used a .INI file before, or had to worry about “keys” and “sections,” so from my (perhaps naïve) perspective, the .INI method seems less easy to use. Is there any advantage to the .INI format?
    Regardless of whether I use the .INI file or a .TXT file, I have this additional problem: One of the things that changes when I install my .EXE file on a new computer is the COM port numbers used by two serial devices.   (On my development computer, the two serial devices use COM5 and COM6, whereas on the two production-flood computers, the COM ports will almost certainly be different).   I suppose I could use the Device Manager on the production-floor computers to change the COM ports to be the same as those on my development computer, but I’d prefer to be able to (again) change the default value of the COM ports in my .EXE.   However, I’m not sure how to do that.   The configuration VIs, have options for reading / writing Booleans, strings, paths, and numeric, but not, (so far as I can tell) for a VISA class.
    Any thoughts / suggestions are welcome. Thanks.
    Solved!
    Go to Solution.

    Dan_the_Clam wrote:
    Thanks for your reply, Yamaeda,
    Great that I can use a string to open a VISA session - I had no idea.  I'll try that.  
    And - ah - you are right about the .INI files.  I just did an experiment in which I re-ordered the sections and randomly changed which letters were capitalized in the key values, and the "read configuration settings.VI" still read the file correctly.  Thanks for that.
    Unfortunately, in my existing code, the controls on the block-diagram aren't all co-located together; they are scattered throughout the block diagram - some of them in case structures and loops.   I suppose that means I'll have to move them all to the left side of the block diagram, route them to these "Write Key.VIs" and then wire them up into the cases and loops with fairly long wires.   It's just a hassle, and is going to make my block diagram more complicated.  Well, I suppose that's how one learns...
    Thanks again.
    dan
    Assuming you have a state machine and an Init state it's a fair use of Local Variables to update controls from the ini-file. The same goes for saving the values.
    /Y
    LabVIEW 8.2 - 2014
    "Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
    G# - Free award winning reference based OOP for LV

  • MDT 0xc0000098 The windows boot configuration data file does not contain a valid OS entry

    hello,
    i installed WDS+MDT for OS deployment. all was working fine.
    Now i need our branch office to be able to deploy OS as well.
    I installed a new Win 2008R2 server, and installed the WDS service on it.
    When reading about this on the internet i saw i need, on the MDT at our main office, to make a link, under "Advanced Configuration" - "Linked Deployment Shares" to the new WDS server (I used this: http://www.balm.se/?p=115")
    when doing so i entered the UNC path to the new server and then, on the created link, i right click and choose "Replicate now".
    after doing so, i tried booting a laptop just to see if there is any impact, and now, I'm getting this error:
    Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
    1. insert your windows installation disk and restart your computer
    2. choose your language, and then click "Next"
    3. Click "Repair your computer"
    If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
    File: \Boot\BCD
    Status: 0xc0000098
    Info: The windows Boot Configuration Data file does not contain a valid OS entry.
    I know that usually when I'm getting this message, it means that a previous MDT installation was started and did not finished correctly, and the are some [stuff] on the HD, so i do a partition erase and start over and all working fine.
    Now it's not working. I tried several computer, even new ones, and NADA.
    someone know the cause?
    I know I read something, i don't remember where or how to find it, that when doing the steps I did, it alter\change some ini or xml, or something like this. is that true? any one know on what file do i need to look and see if something is misconfigured?
    thanks a lot for your help

    hello,
    i installed WDS+MDT for OS deployment. all was working fine.
    Now i need our branch office to be able to deploy OS as well.
    I installed a new Win 2008R2 server, and installed the WDS service on it.
    When reading about this on the internet i saw i need, on the MDT at our main office, to make a link, under "Advanced Configuration" - "Linked Deployment Shares" to the new WDS server (I used this: http://www.balm.se/?p=115")
    when doing so i entered the UNC path to the new server and then, on the created link, i right click and choose "Replicate now".
    after doing so, i tried booting a laptop just to see if there is any impact, and now, I'm getting this error:
    Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
    1. insert your windows installation disk and restart your computer
    2. choose your language, and then click "Next"
    3. Click "Repair your computer"
    If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
    File: \Boot\BCD
    Status: 0xc0000098
    Info: The windows Boot Configuration Data file does not contain a valid OS entry.
    I know that usually when I'm getting this message, it means that a previous MDT installation was started and did not finished correctly, and the are some [stuff] on the HD, so i do a partition erase and start over and all working fine.
    Now it's not working. I tried several computer, even new ones, and NADA.
    someone know the cause?
    I know I read something, i don't remember where or how to find it, that when doing the steps I did, it alter\change some ini or xml, or something like this. is that true? any one know on what file do i need to look and see if something is misconfigured?
    thanks a lot for your help
    For a branch solution I would use DFS(R) rather than linked deploymentshares.
    If there is infrastructure at the remote sites you could use the MDT environment at your main site, and  then at each other site use an existing server or build a new server (VM is available). Create a Deploymentshare on each sever
    and copy the contents of the MDT environment from the first site into this share.  Next you will have to add the WDS service to each site's server. For WDS add the boot image. Of course as Keith noted ensure that you
    have the same versions of MDT and the WAIK/ADK on all systems
    You can use DFS to replicate to all of the other sites, but you will still have to create a deploymentshare, and install WDS at each site. So each site talks to its own WDS server you can use the DefaultGateway parameter instead -
    [Settings]
    Priority=Default, DefaultGateway
    [Default]
    SkipBDDWelcome=YES
    [DefaultGateway]
    192.168.10.1=Bergen
    192.168.20.1=Oslo
    [Bergen]
    DeployRoot=\\MDT-Bergen\DeploymentShare$
    [Oslo]
    DeployRoot=\\MDT-Oslo\DeploymentShare$
    If this post is helpful please click "Mark for answer", thanks! Kind regards

  • Why is the .ini file deleted by iteself?

    Hi all,
    I am working on a large program. It is really large and messy, but it works. The problem is sometimes it deletes .ini file by itself. This program uses a .ini file to keep all kinds of configurations. Sometimes when the program exits, it causes the computer to reboot -- even worse, at same time it deletes the .ini file......who can tell me the possible reasons?
    Thanks!

    Hi steady,
    Does your program use the LabVIEW configuration file VIs to maintain its own INI file? In LabVIEW 7.1, I think the Close Config Data VI used to write the data back to the INI file by default even when nothing changed. Try setting "write configuration data?" to false when you call that VI.
    Do you have any more information about the reboot? It may be a system crash caused by a device driver. Why Does My Computer Automatically Reboot For No Reason? explains how to obtain more information about system crashes.
    Brad
    Brad Keryan
    NI R&D

  • Using CookieName in the iisproxy.ini file

    Hello All,
              According to the Weblogic 451 docs, In the IISProxy.ini file, you should
              set the "CookieName= "
              property to whatever value you have specified for the
              "weblogic.httpd.session.cookie.name="
              property in your weblogic.properties file. (If it is anything other than the
              default name which is "WeblogicSession").
              We have an IIS proxy fronting 2 Weblogic App Servers which run in a
              clustered mode. Also the
              cookie name is specified in the properties file to something different than
              the default WeblogicSession
              (lets say it is "mySession").
              When we do this we see the strange behavior of the application routing us
              back to our Login page in the middle
              of a session. We assume this is happening because when our request is
              switched to a different App Server it
              cannot be associated with any session. And so we are asked to login and
              create a new session.
              This started happening only when we switched to using IIS Proxy and have the
              CookieName
              set to "mySession". This problem goes away if we change the cookieName to be
              the default and remove
              the entry from the IISProxy.ini file.
              Our App Servers are running Weblogic 4.5.1 with sp8.
              Any ideas ??
              Thanks
              Ketan.
              

    The cookie name in your ISAPI plugin and weblogic.properties should be the
              same in all your plugins and weblogic servers. This is required. Plugin and
              WLAS share the same cookie. However, plugin and WLAS are in different
              processes. In order for plugin and WLAS to locate the same cookie, same
              cookie name in the configuration is required.
              Cheers - Wei
              Ketan Bhukhanwala <[email protected]> wrote in message
              news:[email protected]...
              > Hello All,
              >
              > According to the Weblogic 451 docs, In the IISProxy.ini file, you should
              > set the "CookieName= "
              > property to whatever value you have specified for the
              > "weblogic.httpd.session.cookie.name="
              > property in your weblogic.properties file. (If it is anything other than
              the
              > default name which is "WeblogicSession").
              >
              > We have an IIS proxy fronting 2 Weblogic App Servers which run in a
              > clustered mode. Also the
              > cookie name is specified in the properties file to something different
              than
              > the default WeblogicSession
              > (lets say it is "mySession").
              >
              > When we do this we see the strange behavior of the application routing us
              > back to our Login page in the middle
              > of a session. We assume this is happening because when our request is
              > switched to a different App Server it
              > cannot be associated with any session. And so we are asked to login and
              > create a new session.
              >
              > This started happening only when we switched to using IIS Proxy and have
              the
              > CookieName
              > set to "mySession". This problem goes away if we change the cookieName to
              be
              > the default and remove
              > the entry from the IISProxy.ini file.
              >
              > Our App Servers are running Weblogic 4.5.1 with sp8.
              >
              > Any ideas ??
              >
              > Thanks
              > Ketan.
              >
              >
              

  • Labview ini file syntax

    Hi
    I have a ini file built into an application as a support file. When I did some changes on ini file, some change was reflected in executable file but some not. I suspect the syntax in ini file are not right so aren't recognized.
    Besides, how ini file works? when I change the ini file, do I have to re-execute the application in order to getting the reflection in application? Or if the configuration is changed via the menu Tools->option in application, will they rewrite the ini file automatically? Do I have to stop the application in order to reading a changed ini file?
     Where can I find a documentation about labview ini file as well as its syntax?
    Thanks.

    An .ini file is a standard file and is not something that is special to LabVIEW. LabVIEW itself uses an .ini file to store some application settings that you change via the Tools->Options menu. It is not wise to change this file yourself manually. You can create your own .ini files for your application. You can use the VIs in the Configration File VIs palette to read/write .ini files. This palette is a sub-palette from the File I/O palette.
    As for its format, it's made up of sections and keys like this:
    [Section1]
    keyname=value
    keyname=value
    [Section2]
    keyname=value
    ;this is a comment
    If the value you're trying to save is a string you should use quotes.
    What you store in the .ini file is up to you and how you use it is also up to you. You can access the keys on an as-needed basis, or you can read the keys in at the beginning of your program, store them someplace like a global variable and access them as needed. It's kind of dependent on the size and architecture of your application.

  • INI file preference not being followed - Regarding SAP Note 1409494

    Hi,
    Following SAP Note 1409494, it seems like there is a preference over locations of INI files.
    I have setup on my Citrix servers, the environment variable (SAPLOGON_INI_FILE) pointing to a central location of INI file.
    The problem is that in the same server there is the BW logon pad that requires a different set of configurations, therefore a second INI file.
    When I try to use the first option on the note (command line parameter /INI_FILE) pointing to a second INI file, it uses the one on the environment variable.
    Is that the way it's supposed to work???
    Is there a way to bypass this?
    Thanks!

    Hello Vijith,
    I guess you are talking about <a href="https://service.sap.com/sap/support/notes/1034932">note 1034932</a>. It is currently being changed, what it will basically say is:
    If you put the jars somewhere in /usr/sap and later on upgrade the engine you will actually loose the entire folder and will have to copy the jar files again.                                                   
    As a permanent solution you could define an <a href="http://help.sap.com/saphelp_nw04/helpdata/en/ee/0618d0899001408d821096c85ff8a2/frameset.htm">HTTP Alias</a> on the engine (not an application alias but an http alias) which will point to a folder on the file system outside the /usr/sap folders.       
    After that just set JavaGuiCodeBase for the applet to whatever you chose for the http alias name.
    If you have suggestions to further improve the note, please let us know.
    Best regards
    Rolf-Martin

  • Content of Ini-File with config-data sometimes deleted?

    Hello,
    i have a simple vi attached where i read config-data from a file.
    Sometimes it happens that the content is lost. I am not sure why, but perhaps there a errors in the vi.
    I wonder about the last vi "Close Config Data" there is an onput-parameter "write configuration file? (T)".
    Why is this parameter set to default-TRUE? Could it be that i shouzld set it to False? Perhaps this
    close-vi overwrite my data with nothing.
    The vi reads the section [Par1] from this file:
    [Par1]
    PathFile=C:\\profile.txt
    [Par2]
    PathFile=C:\\variants.txt
    and returns --> C:\\profile.txt
    Thx for your help
    Attachments:
    example.vi ‏21 KB

    The values set by using the INI file functions only exist in memory and are NOT written to disk until the "Close" VI with the constant set TRUE.
    If your code executes in multiple threads where one thread sets the values but another thread closes the file without the constant set true, the values will be removed from memory and will not be written to disk.
    So make sure you only execute the "Close" after all values have been set and make sure the constant is set true when the files are closed.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Editing Executable's INI file with "HideRootWindow"

    Hello
    I'm trying to create an executable so that it shows only one window in the taskbar. On one of the Knowledgebase articles (http://digital.ni.com/public.nsf/allkb/6E660558F3D420C786256FCB005B4F52) I had read about setting HideRootWindow=True in the INI file. I did and it worked. The problem though is that everytime I rebuild the exe in LabVIEW, the line disappears & I have to manually edit the INI file each time. I was wondering if there was anyway I could do it automatically though LabVIEW so that it itself appends that line to INI file at each Build process.
    Appreciate any help. Thank you!
    Solved!
    Go to Solution.

    Instead of checking Use the default LabVIEW Configuration file, uncheck this option and add your own ini file. Also make sure that you add the ini file to the Project too! This will help in maintenance.
    Hope this helps.

  • We want your LabVIEW INI files!

    Hello:  
    As some of you might know, the Tools>>Options dialog box allows you to control options that are stored in the LabVIEW.INI file. With each release of LabVIEW, we have steadily increased the number of available options to customize LabVIEW environment. For example, the LabVIEW R&D team has added over 15 block diagram options since LabVIEW 5.x and only removed a small handful.
    As the LabVIEW team introduces new features, we provide more and more configurable options to satisfy different development styles or interests. However, the proliferation of options can prove confusing. It becomes difficult to distinguish between widely-used options and ones that are applicable only to a small set of customers.
    To gain a better sense of how customers use the settings in the Tools>>Options dialog box, I would like to collect as many customer INI files as possible. This will allow me to analyze option usage and improve the usability of the Tools>>Options dialog box.
    Please help by sending your INI file(s) to the following email address along with answers to a few simple questions. The more INI files, the better. Therefore, encourage your colleagues to send their INI files, too! If you are a MacOS or Linux user, attach your LabVIEW Preferences or .labviewrc file.  I'm interested in receiving INI files from users of all experience levels -- novice, intermediate, advanced!
    Send to: [email protected]
    What is the first version of LabVIEW that you used?
    When upgrading to a new version of LabVIEW, do you copy the LabVIEW.INI file from the older version of LabVIEW to the newer version of LabVIEW?
    When launching a new version of LabVIEW, do you immediately change any particular settings in the Tools>>Options dialog box? If so, which ones?
    When upgrading to a new version of LabVIEW, do you review the New and Changed page in the Tools>>Options dialog box?
    Which options are you the most passionate about? Please provide a brief reason for each.
    Do you have any suggestions to improve the usability of the Tools>>Options dialog box?
    Please do not forget to attach your LabVIEW.INI file.  
    Note:  On Windows the LabVIEW.INI file resides next to the LabVIEW.exe.   On Mac OS, your options are stored in the LabVIEW Preferences text file in the System: Preferences folder.  On Linux, the .labviewrc file is in your home directory.  
    Thank you,
    Noel Adorno
    LabVIEW R&D

    Hai noel,
    Its great and delighting to hear that LabVIEW R&D team is in an constant effort in collecting the information about user experience and appropriate changes are done.  Each enhancment or feature inclusion that is done to LabVIEW makes the users more comfortable with the environment and kindles the user for new version LabVIEW experience...
    Hats off to LabVIEW R&D team.
    With regards,
    JK
    (Certified LabVIEW Developer)
    Give Kudos for Good Answers, and Mark it a solution if your problem is solved.

  • Where are settings stored (foldeer/ini file/Registry)? Backup settings poss

    Where are the settings of SQL Developer stored?
    Is this a folder, an *.ini file or the Registry?
    If it is a folder: Can I change the location of the folder?
    If yes: Where exactly?
    How can I otherwise export/save settings otherwise?
    Peter

    In your home directory will be created a path like ...\SQL Developer\system1.5.4.59.40
    There SQL developer stores the local data.
    You can change this path (here ...my_options/system) with th following line in the sqldeveloper.conf, located in path ...\sqldeveloper\sqldeveloper\bin:
    # This is to enforce storing of configuration information in the "/my_options/system"
    # subfolder I have created in the SQL-Developer installation directory (instead
    # of in the "C:\Documents and Settings\<user>\Application Data\SQL Developer"),
    # so that SQL-Developer installation directory can be just copied to another
    # location (e.g. a stick) and along with the configuration information.
    AddVMOption -Dide.user.dir=../../my_options/system
    Thanks to Juri W. for this solution!
    Before changing the path you should save your connection and custom report - settings via right click -> export in the connection and custom report view, I had to reimport these settings after movimg my directory.
    Gerhard

Maybe you are looking for