Essbase.ini file location

Essbase 6.2.2 In MS Terminal Server, how do I specify which essbase.ini file to use (ie. file path)? I logged in using the admininstrator account to solve another issue and ever since it is bypassing the individual client file and using the administrator version. Any ideas? Thanks in advance!

Hi thanks for your link.
The document you pointed me towards led me to SAP note number 756686
which explains that you can edit the SAP icon on your desktop (by right-clicking and opening with notepad) and then adding a line cmd="/ini_file='path to ini file'\saplogon.ini'
Thanks for your assistance.
Edited by: Mike Ellis on Mar 4, 2008 1:05 PM

Similar Messages

Where are the *.ini files located?

I remember a discussion about deleting some of the *.ini files (or whatever they are called) but I can't find the link, don't remember the filenames and can't find their location.
I'm having the same problem with Media Encoder where it only goes partway through an encode and then returns an error message. The last time I experienced that, I deleted the startup files and things worked fine. I think that there was a link from Dennis Draeke about some config files and their location.
All help gratefully accepted!
TIA,

After experiencing the situation where a codec (LEAD MJPG) that had worked previously suddenly would not export through AME again, I tracked down the preferences files as outlined above and removed the following files:
Adobe Premiere Pro Prefs,
Adobe Premiere Pro Prefs~2
AMEPrefs.xml
And once again I could export with any codec settings I chose with no problems.
I'm working with 1280x720, 30P, square pixels, 44.1kHz, 16-bit stereo material.
When not working, the encode would proceed about 1/2- to 2/3 of the way through and then stop and return the message:
- Preset Used: 1280x720P TX-1 Settings - LEAD Codec
- Video: 1280x720, 30 [fps], Progressive, Quality 90
- Audio: 44100 Hz, Stereo, 16 bit
- Bitrate:
- Encoding Time: 00:15:27
4/10/2010 2:56:50 PM : Encoding Failed
Error compiling movie.
Codec compression error.
This codec may be unable to support the requested frame size, or there may be a hardware or memory problem.
After removing those three files, encoding would finish properly and return the message:
- Preset Used: 1280x720P TX-1 Settings - LEAD Codec
- Video: 1280x720, 30 [fps], Progressive, Quality 90
- Audio: 44100 Hz, Stereo, 16 bit
- Bitrate:
- Encoding Time: 00:03:09
4/11/2010 1:39:31 PM : File Successfully Encoded
4/11/2010 1:39:31 PM : Queue Stopped
Thought I'd post the results in case it might help help someone solve a problem.

Saplogon.ini file location question

Hi, any advice would be appreciated thanks
we have rolled the sap gui 6.40 to all our clients - all using a local copy of the saplogon.ini file in the local windows directory. however we wish to change this approach and have a central saplogon.ini file on a file server and point all the clients to this file.. any changes only then have to be made in one place.
can anyone help me with this, firstly is it possible, and if so how to change the client setting to adjust the location.
many thanks.

Hi thanks for your link.
The document you pointed me towards led me to SAP note number 756686
which explains that you can edit the SAP icon on your desktop (by right-clicking and opening with notepad) and then adding a line cmd="/ini_file='path to ini file'\saplogon.ini'
Thanks for your assistance.
Edited by: Mike Ellis on Mar 4, 2008 1:05 PM

What is Essbase.ini , Essbase.id, Essadmin.ini

Just for your info about : Essbase.ini , Essbase.id , and Essadmin.ini files
Essbase.ini
Spreadsheet options are per worksheet. However, the options set in the Global tab are for all sheets. The Essbase.ini holds these user settings. The sheet will override these settings if 1) the sheet has other values already set (from a prior change and save) and 2) the user changes these settings, in which case it SHOULD be page specific. Any changes from the default settings will modify the .ini file whether the sheet is saved or not.
The bottom line here is the following: If we open up a saved template, any subsequent NEW template created after doing so will utilize the Options for that previous template even if Excel is closed. This is the case for all versions of Essbase. Therefore, if we close out of Excel completely and open up a NEW sheet, we will also utilize the settings that were used last by this user. If you want to know what the default options that are provided, just rename the Essbase.ini file before Excel startup.
Theoretically, yes this should be possible. An issue might arise with the sheet options, though (such as #Missing settings, etc). This is set on a per-sheet basis, and any changes from the default settings will modify the .ini file. But this file doesn't make specific references to the machine on which it's located, so it should be portable.
Essbase tracked some client information using the file essbase.ini
Engineering confirmed that unfortunately pre-Essbase 6.5 there is no way to set the essbase.ini to be written somewhere else other then your c:\winnt.
Essbase.id
Essbase uses an unique key, Essbase.id, created on the client machine in the C:\WINNT directory, plus the user id as the seeds to identify the number of ports needed. You cannot create the essbase.id file manually; it has to be created by Essbase.
The first time that you install/use a client on a machine, the essbase.id is created and you do require read/write privileges to do this.
Thereafter, only read privileges are required.
The essbase.id file cannot be moved from the \winnt (or \windows) folder, this location is hard-coded in the Essbase code.
The Essbase.id contains information to distinguish ports.
It is used to manage ports.
Essadmin.ini
When you login from Application manager for the first time it creates the essadmin.ini file.

Just for your info about : Essbase.ini , Essbase.id , and Essadmin.ini files
Essbase.ini
Spreadsheet options are per worksheet. However, the options set in the Global tab are for all sheets. The Essbase.ini holds these user settings. The sheet will override these settings if 1) the sheet has other values already set (from a prior change and save) and 2) the user changes these settings, in which case it SHOULD be page specific. Any changes from the default settings will modify the .ini file whether the sheet is saved or not.
The bottom line here is the following: If we open up a saved template, any subsequent NEW template created after doing so will utilize the Options for that previous template even if Excel is closed. This is the case for all versions of Essbase. Therefore, if we close out of Excel completely and open up a NEW sheet, we will also utilize the settings that were used last by this user. If you want to know what the default options that are provided, just rename the Essbase.ini file before Excel startup.
Theoretically, yes this should be possible. An issue might arise with the sheet options, though (such as #Missing settings, etc). This is set on a per-sheet basis, and any changes from the default settings will modify the .ini file. But this file doesn't make specific references to the machine on which it's located, so it should be portable.
Essbase tracked some client information using the file essbase.ini
Engineering confirmed that unfortunately pre-Essbase 6.5 there is no way to set the essbase.ini to be written somewhere else other then your c:\winnt.
Essbase.id
Essbase uses an unique key, Essbase.id, created on the client machine in the C:\WINNT directory, plus the user id as the seeds to identify the number of ports needed. You cannot create the essbase.id file manually; it has to be created by Essbase.
The first time that you install/use a client on a machine, the essbase.id is created and you do require read/write privileges to do this.
Thereafter, only read privileges are required.
The essbase.id file cannot be moved from the \winnt (or \windows) folder, this location is hard-coded in the Essbase code.
The Essbase.id contains information to distinguish ports.
It is used to manage ports.
Essadmin.ini
When you login from Application manager for the first time it creates the essadmin.ini file.

How to Regenerate the Essbase.sec file

Hi
Could any one please let me knowthe steps on how to generate a new Essbase.sec file.
Please notethat other methods of restoring the .bak or bak_startp are known.If possible please let us know the steps to Craeate a new ESSBASE.SEC
Thanks and regards
krishnatilak

The easiest way to do it is to
1. Stop Essbase
2. delete or rename the Essbase.sec file located in the arborpath\bin directory
3. From the bin directory, start Essbase.exe (double click on it)
4. Enter the userid, password and company info as it asks for it. Note although it asks for your user Id, it wants the ID you want to be the system Admin ID
5. stop the foreground version(optional)
6. restart it as a service(optional)
If you want to reassociate applications to the security file so it can see them. In EAS do a create application with the same name as an existing one Like Sample. IT will see that the application already exists and add it to the security file.

11.1.2 essbase upgrade not recognizing application files location

Hi all
I am upgrading an essbase database (Planning) from 11.1.1.3 to 11.1.2.2,
I trying to configure 2 essbase servers (original 11.1.1.3 and new 11.1.2) running on 1 physical server using different ports and filesystems
Following all the steps in the Deployment guide in Preparing Essbase Data for Upgrading,
I ran all the steps in the Manual file transfer instructions to copy from source machine to target machine.
I have started the steps in rehosting the essbase applications,
- Completed enable lookup by cluster name:
- I completed the server to cluster script on the HSS box (updateEssbaseServer )
when i went to run EssbaseUpdateEssbaseServer one of the planning databases did not update i got this error
[Mon May 21 14:03:50 2012]cphypd.sherwin.com///admin/Error(1002097)
Unable to load database [PlanFcst]
Error loading application = 1002097, continue...
looking in the logs i found that it was trying to go to the prior location of the 11.1.1.3 instance and not the new location of the 11.1.2 instance
Why is it not recognizing the new datafile locations

I saw this in the guide
I followed these instructions and specified a different directory when running the staging tool, the script was empty, i do not believe it should be, it should contain mapping info to update essbase.sec, which it did not
On the Configure Essbase Server page, for Full path to application location (ARBORPATH), specify the location of the existing or replicated Essbase data.
Note:
If you replicated data to a new machine, and if you selected Differently-named disk volumes, table spaces, or ARBORPATH on source and target or Consolidated disk volumes or tablespaces on target by exporting data during data replication, you must run a script immediately after configuring Essbase to update the Essbase security file to reflect the disk volumes on the upgraded system. The Essbase Staging Tool provides a script to update the settings in the security file (essbase.sec):
Start the Essbase Server and EPM System services. Navigate to ARBORPATH/app on the machine that is hosting the upgraded Essbase Server and run the following script using MaxL:
%ARBORPATH%/bin/startMaxl.bat -u userName editagtsec.msh
where userName is the Administrator user name to connect to the upgraded Essbase server. The script prompts you to enter the password.
Note:
editagtsec.msh could be empty in some scenarios. For example, when you launched the Staging Tool, the Staging Tool reports on existing volumes. If no volumes are listed, editagtsec.msh is empty.

Placing ini file in specific location when building the application

Hello,
I have a small problem. I have an ini file that I use to store certain parameters. Lets call this file app.ini. When I build the Application.exe, it puts that file into the data directory. I was hoping that it would be one level higher and be located in the same directory as Application.exe is (otherwise it won't read the file correctly.) I looked at the Source File Settings in the Category list in the properties window for the build and set the Destination to be "Same as caller", but that didn't put it where I wanted it. I'd really like this file to be one directory higher when I make my build in order for my app to read it correctly. Any suggestions?
I use this executable later on when I make my installer and the problem simply propagates there too, not good.
Solved!
Go to Solution.

One way to solve the problem:
1) In build properties window select Destinations and create a new destination. Select as "Destination Path" the same dir where the exe will be stored
2) Assign this destination to the .ini file.
Let me know if it works
Marco

Syntax error in NQSConfig.ini.file

# NQSConfig.INI
# Copyright (c) 1997-2006 Oracle Corporation, All rights reserved
# INI file parser rules are:
# If values are in literals, digits or _, they can be
# given as such. If values contain characters other than
# literals, digits or _, values must be given in quotes.
# Repository Section
# Repositories are defined as logical repository name - file name
# pairs. ODBC drivers use logical repository name defined in this
# section.
# All repositories must reside in OracleBI\server\Repository
# directory, where OracleBI is the directory in which the Oracle BI
# Server software is installed.
[ REPOSITORY ]
Star = OracleBIAnalyticsApps.rpd, DEFAULT
# Query Result Cache Section
[ CACHE ]
ENABLE = NO;
// A comma separated list of <directory maxSize> pair(s)
// e.g. DATA_STORAGE_PATHS = "d:\OracleBIData\nQSCache" 500 MB;
DATA_STORAGE_PATHS = "C:\OracleBIData\cache" 500 MB;
MAX_ROWS_PER_CACHE_ENTRY = 100000; // 0 is unlimited size
MAX_CACHE_ENTRY_SIZE = 1 MB;
MAX_CACHE_ENTRIES = 1000;
POPULATE_AGGREGATE_ROLLUP_HITS = NO;
USE_ADVANCED_HIT_DETECTION = NO;
MAX_SUBEXPR_SEARCH_DEPTH = 7;
// Cluster-aware cache
// GLOBAL_CACHE_STORAGE_PATH = "<directory name>" SIZE;
// MAX_GLOBAL_CACHE_ENTRIES = 1000;
// CACHE_POLL_SECONDS = 300;
// CLUSTER_AWARE_CACHE_LOGGING = NO;
# General Section
# Contains general server default parameters, including localization
# and internationalization, temporary space and memory allocation,
# and other default parameters used to determine how data is returned
# from the server to a client.
[ GENERAL ]
// Localization/Internationalization parameters.
LOCALE = "English-usa";
SORT_ORDER_LOCALE = "English-usa";
SORT_TYPE = "binary";
// Case sensitivity should be set to match the remote
// target database.
CASE_SENSITIVE_CHARACTER_COMPARISON = OFF ;
// SQLServer65 sorts nulls first, whereas Oracle sorts
// nulls last. This ini file property should conform to
// that of the remote target database, if there is a
// single remote database. Otherwise, choose the order
// that matches the predominant database (i.e. on the
// basis of data volume, frequency of access, sort
// performance, network bandwidth).
NULL_VALUES_SORT_FIRST = OFF;
DATE_TIME_DISPLAY_FORMAT = "yyyy/mm/dd hh:mi:ss" ;
DATE_DISPLAY_FORMAT = "yyyy/mm/dd" ;
TIME_DISPLAY_FORMAT = "hh:mi:ss" ;
// Temporary space, memory, and resource allocation
// parameters.
// You may use KB, MB for memory size.
WORK_DIRECTORY_PATHS = "C:\OracleBIData\tmp";
SORT_MEMORY_SIZE = 4 MB ;
SORT_BUFFER_INCREMENT_SIZE = 256 KB ;
VIRTUAL_TABLE_PAGE_SIZE = 128 KB ;
// Analytics Server will return all month and day names as three
// letter abbreviations (e.g., "Jan", "Feb", "Sat", "Sun").
// To use complete names, set the following values to YES.
USE_LONG_MONTH_NAMES = NO;
USE_LONG_DAY_NAMES = NO;
UPPERCASE_USERNAME_FOR_INITBLOCK = NO ; // default is no
// Aggregate Persistence defaults
// The prefix must be between 1 and 8 characters long
// and should not have any special characters ('_' is allowed).
AGGREGATE_PREFIX = "SA_" ;
# Security Section
# Legal value for DEFAULT_PRIVILEGES are:
# NONE READ
[ SECURITY ]
DEFAULT_PRIVILEGES = READ;
PROJECT_INACCESSIBLE_COLUMN_AS_NULL = NO;
MINIMUM_PASSWORD_LENGTH = 0;
#IGNORE_LDAP_PWD_EXPIRY_WARNING = NO; // default is no.
#SSL=NO;
#SSL_CERTIFICATE_FILE="servercert.pem";
#SSL_PRIVATE_KEY_FILE="serverkey.pem";
#SSL_PK_PASSPHRASE_FILE="serverpwd.txt";
#SSL_PK_PASSPHRASE_PROGRAM="sitepwd.exe";
#SSL_VERIFY_PEER=NO;
#SSL_CA_CERTIFICATE_DIR="CACertDIR";
#SSL_CA_CERTIFICATE_FILE="CACertFile";
#SSL_TRUSTED_PEER_DNS="";
#SSL_CERT_VERIFICATION_DEPTH=9;
#SSL_CIPHER_LIST="";
# There are 3 types of authentication. The default is NQS
# You can select only one of them
#----- 1 -----
#AUTHENTICATION_TYPE = NQS; // optional and default
#----- 2 -----
#AUTHENTICATION_TYPE = DATABASE;
# [ DATABASE ]
# DATABASE = "some_data_base";
#----- 3 -----
#AUTHENTICATION_TYPE = BYPASS_NQS;
# Server Section
[ SERVER ]
SERVER_NAME = Oracle_BI_Server ;
READ_ONLY_MODE = NO; // default is "NO". That is, repositories can be edited online.
MAX_SESSION_LIMIT = 2000 ;
MAX_REQUEST_PER_SESSION_LIMIT = 500 ;
SERVER_THREAD_RANGE = 40-100;
SERVER_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
DB_GATEWAY_THREAD_RANGE = 40-200;
DB_GATEWAY_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
MAX_EXPANDED_SUBQUERY_PREDICATES = 8192; // default is 8192
MAX_QUERY_PLAN_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_INFO_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_QUERY_CACHE_ENTRIES = 1024; // default is 1024
INIT_BLOCK_CACHE_ENTRIES = 20; // default is 20
CLIENT_MGMT_THREADS_MAX = 5; // default is 5
# The port number specified with RPC_SERVICE_OR_PORT will NOT be considered if
# a port number is specified in SERVER_HOSTNAME_OR_IP_ADDRESSES.
RPC_SERVICE_OR_PORT = 9703; // default is 9703
# If port is not specified with a host name or IP in the following option, the port
# number specified at RPC_SERVICE_OR_PORT will be considered.
# When port number is specified, it will override the one specified with
# RPC_SERVICE_OR_PORT.
SERVER_HOSTNAME_OR_IP_ADDRESSES = "ALLNICS"; # Example: "hostname" or "hostname":port
# or "IP1","IP2":port or
# "hostname":port,"IP":port2.
# Note: When this option is active,
# CLUSTER_PARTICIPANT should be set to NO.
ENABLE_DB_HINTS = YES; // default is yes
PREVENT_DIVIDE_BY_ZERO = YES;
CLUSTER_PARTICIPANT = NO; # If this is set to "YES", comment out
# SERVER_HOSTNAME_OR_IP_ADDRESSES. No specific NIC support
# for the cluster participant yet.
// Following required if CLUSTER_PARTICIPANT = YES
#REPOSITORY_PUBLISHING_DIRECTORY = "<dirname>";
#REQUIRE_PUBLISHING_DIRECTORY = YES; // Don't join cluster if directory not accessible
DISCONNECTED = NO;
AUTOMATIC_RESTART = YES;
# Dynamic Library Section
# The dynamic libraries specified in this section
# are categorized by the CLI they support.
[ DB_DYNAMIC_LIBRARY ]
ODBC200 = nqsdbgatewayodbc;
ODBC350 = nqsdbgatewayodbc35;
OCI7 = nqsdbgatewayoci7;
OCI8 = nqsdbgatewayoci8;
OCI8i = nqsdbgatewayoci8i;
OCI10g = nqsdbgatewayoci10g;
DB2CLI = nqsdbgatewaydb2cli;
DB2CLI35 = nqsdbgatewaydb2cli35;
NQSXML = nqsdbgatewayxml;
XMLA = nqsdbgatewayxmla;
ESSBASE = nqsdbgatewayessbasecapi;
# User Log Section
# The user log NQQuery.log is kept in the server\log directory. It logs
# activity about queries when enabled for a user. Entries can be
# viewed using a text editor or the nQLogViewer executable.
[ USER_LOG ]
USER_LOG_FILE_SIZE = 10 MB; // default size
CODE_PAGE = "UTF8"; // ANSI, UTF8, 1252, etc.
# Usage Tracking Section
# Collect usage statistics on each logical query submitted to the
# server.
[ USAGE_TRACKING ]
ENABLE = YES;
//==============================================================================
// Parameters used for writing data to a flat file (i.e. DIRECT_INSERT = NO).
STORAGE_DIRECTORY = "<full directory path>";
CHECKPOINT_INTERVAL_MINUTES = 5;
FILE_ROLLOVER_INTERVAL_MINUTES = 30;
CODE_PAGE = "ANSI"; // ANSI, UTF8, 1252, etc.
//==============================================================================
DIRECT_INSERT = YES;
//==============================================================================
// Parameters used for inserting data into a table (i.e. DIRECT_INSERT = YES).
PHYSICAL_TABLE_NAME = "OBI Usage Tracking"."Catalog"."dbo"."S_NQ_ACCT" ; // Or "<Database>"."<Schema>"."<Table>" ;
CONNECTION_POOL = "OBI Usage Tracking"."Usage Tracking Writer Connection Pool>" ;
BUFFER_SIZE = 10 MB ;
BUFFER_TIME_LIMIT_SECONDS = 5 ;
NUM_INSERT_THREADS = 5 ;
MAX_INSERTS_PER_TRANSACTION = 1 ;
//==============================================================================
# Query Optimization Flags
[ OPTIMIZATION_FLAGS ]
STRONG_DATETIME_TYPE_CHECKING = ON ;
# CubeViews Section
[ CUBE_VIEWS ]
DISTINCT_COUNT_SUPPORTED = NO ;
STATISTICAL_FUNCTIONS_SUPPORTED = NO ;
USE_SCHEMA_NAME = YES ;
USE_SCHEMA_NAME_FROM_RPD = YES ;
DEFAULT_SCHEMA_NAME = "ORACLE";
CUBE_VIEWS_SCHEMA_NAME = "ORACLE";
LOG_FAILURES = YES ;
LOG_SUCCESS = NO ;
LOG_FILE_NAME = "C:\OracleBI\server\Log\CubeViews.Log";
# MDX Member Name Cache Section
# Cache subsystem for mapping between unique name and caption of
# members for all SAP/BW cubes in the repository.
[ MDX_MEMBER_CACHE ]
// The entry to indicate if the feature is enabled or not, by default it is NO since this only applies to SAP/BW cubes
ENABLE = NO ;
// The path to the location where cache will be persisted, only applied to a single location,
// the number at the end indicates the capacity of the storage. When the feature is enabled,
// administrator needs to replace the "<full directory path>" with a valid path,
// e.g. DATA_STORAGE_PATH = "C:\OracleBI\server\Data\Temp\Cache" 500 MB ;
DATA_STORAGE_PATH = "C:\OracleBIData\cache" 500 MB;
// Maximum disk space allowed for each user;
MAX_SIZE_PER_USER = 100 MB ;
// Maximum number of members in a level will be able to be persisted to disk
MAX_MEMBER_PER_LEVEL = 1000 ;
// Maximum size for each individual cache entry size
MAX_CACHE_SIZE = 100 MB ;
# Oracle Dimension Export Section
[ ORA_DIM_EXPORT ]
USE_SCHEMA_NAME_FROM_RPD = YES ; # NO
DEFAULT_SCHEMA_NAME = "ORACLE";
ORA_DIM_SCHEMA_NAME = "ORACLE";
LOGGING = ON ; # OFF, DEBUG
LOG_FILE_NAME = "C:\OracleBI\server\Log\OraDimExp.Log";
Help me out Gurus thanks in advance

Hi,
Star = OracleBIAnalyticsApps.rpd, DEFAULTthis should be end with semicolon
Star = OracleBIAnalyticsApps.rpd, DEFAULT;
Assign Points and close thread, if your question is answered...
Cheers,
Aravind

.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

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

Reading INI files with dashes in the section name

I am trying to read an INI file from a web site. Within that INI file are sections that have dashes in them. I need to be able to read several sections so I can locate specific files to download referenced within the INI files. I found a script for parsing
INI files, but when I run it, the script fails to handle the sections that have dashes. Any ideas on how I can work around the issue?
$Web = New-Object System.Net.WebClient
Function Get-INIContent ($ContentList){
$INI = @()
Switch -regex ($contentList)
"^\[(.+)\]"
[string]$Section = $Matches[1]
$INI[$Section] = @{}
$CommentCount = 0
$ContentList = $Web.Downloadstring("http://download.nai.com/PRODUCTS/COMMONUPDATER/avvdat.ini")
Get-INIContent $contentlist
What I was hoping to do was search through the INI until I found the sections I want, and then read the fields for that section so I know what to download. I won't be pulling all of the files, so I need to find a way to search for the sections I am
looking for then read all of the lines for that section and process them.

Found part of the problem... When I pull the file into a variable I lose the ability to search it line by line. For example:
$Web = New-Object System.Net.WebClient
$ContentList = $Web.Downloadstring("http://download.nai.com/PRODUCTS/COMMONUPDATER/avvdat.ini")
#For some reason this returns the entire file
$contentlist | select -first 1
$contentlist | %{
#Thought this would be one line, but it is also
#the entire file...
$_
I have since shifted to a different method of reading the ini and I can process row by row...
$Web = New-Object System.Net.WebClient
$INILocation = "c:\SomeLocation\avvdat.ini"
$Web.DownloadFile("http://download.nai.com/PRODUCTS/COMMONUPDATER/avvdat.ini",$INILocation)
$INIFile = [System.IO.File]::OpenText($INILocation)
Do {
$CurrentLine = $INIFile.ReadLine()
#This is now one line like it should be.
$CurrentLine
While ($INIFile.EndOfStream -ne $True)

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.
 >
 >

How to create a comment in config.ini file

Does anyone know how to create a comment line in the Essbase config.ini file (server config file, not client, if they are different)?I know that for ESSCMD it is :Calcs it is /*but not sure of syntax for commenting config files. Thanks in advance!

The comment character for the essbase.cfg file (I assume that is what you are talking about) is a semi-colon (;)Regards,Jade-----------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Essbase Audit Files not Updating

Hi All,
My Essbase Audit files are not updating....both .ALG and .ATX files.
They used to update up to the last month but those are not updating.
I checked the .cfg file and is okay with SAUDITR.
Please suggest.

Some of the terminology Dreamweaver uses can make what you're saying a bit confusing, so I'm going to try to clarify so we can better understand the situation.
You and your coworker are each on your work computers using Dreamweaver. You have both created site definitions in Dreamweaver, pointing to a folder on your company's internal server.
The "Local Site Folder" setting of your site definition should be pointing to a location on your own computer. The same setting on your coworker's site definition in Dreamweaver should be pointing to a location on their computer.
This means that when you select "Local view" in the Files panel, it will only show files on your computer. Likewise, when your coworker does the same, it will only show files on their computer.
It is the "Server Folder" setting in the server settings on each of your computers that should be pointing to that folder on your company's internal server.
This means that when you select "Remote Server" (or "Testing Server" if you checked that box instead for the server in your site definition) in the Files panel, you will be viewing the files on your company's server.
In order to essentially share files between your copy of Dreamweaver and your coworker's, you need to "upload" (i.e. copy) files from your Local View to your Remote Server. Your coworker would then see these files by looking at Remote Server on their computer. And the reverse is true; they upload from Local View to Remote Server, and you would see the files by looking at the Remote Server view on your computer.
Hope this helps.

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

Essbase.ini file location

Similar Messages

Maybe you are looking for