Hi Team,
I am looking at the installation of an App, including the edbsrvr.
The actual installation of the App and Server is not an issue.
What I can't figure is, once installed, how to set the necessary various parameters.  
e.g. 'Configuration in memory', 'Configuration folder', 'Catalog Name', 'Temporary Tables Folder', 'Port Address' if not default, etc, etc.  Programmaticly.
I really don't want to give the Customer edbmgr.
Alternatively, it would be really nice if when installing edbsrvr it could be told to read its parameters from a text file.
I guess what can or cannot be done is also dependent on when edbsrvr.ini is created.

Thoughts/suggestions appreciated.
Regards,
Ian

Ian,

I use InnoSetup to install both my applications and EDB Server.
With InnoSetup you can read and write to ini files, including edbsrvr.ini, at install time and change all the server parameters.
Another option is to previously "cook" your own edbsrvr.ini and copy it to the destination folder at setup time.

The edbsrvr.ini file is by default created at:
{commonappdata} + '\Elevate Software\ElevateDB Server' if 32 bits
{commonappdata} + '\Elevate Software\ElevateDB Server (Win64)'if 64 bits

--
Fernando Dias
[Team Elevate]

Hi Fernando,
I did not know that about InnoSetup.  I will investigate.
I had started to roll my own but I figured there had to be an easier way.
Regards,
Ian

Ian,

I use an INI file similar to Fernado which is stored in {commonappdata}\<MyComparyName>\<ProjectName>

An example is:

[DB]
ConfigLocation=\\wck\Databases
Database=ES_StockDB

[dmData]
SessionType=stRemote
RemoteHost=wck
RemoteAddress=
RemotePort=12010
RemoteService=
RecordLockProtocol=lpPessimistic

I have attached a copy of an INNO Setup script that I have used for years. It displays pages asking for the DB Configuration file Location, the Database Name and other information. It saves a copy of the previous exe file with a <VersionNo> suffix. It gives some idea of what INNO Setup is capable of.

Richard

Ian Branch

If you have just one server (edbsrvr.exe) instance running my tip is: just put the INI file in the same folder. It will be easier to maintain.

If you are building your own installation application, then just create the ini file with the tips others gave you.

Regards
Eduardo

Hi Ian,

<< I am looking at the installation of an App, including the edbsrvr.
The actual installation of the App and Server is not an issue.
What I can't figure is, once installed, how to set the necessary various parameters.  
e.g. 'Configuration in memory', 'Configuration folder', 'Catalog Name', 'Temporary Tables Folder', 'Port Address' if not default, etc, etc.  Programmaticly.
I really don't want to give the Customer edbmgr.
Alternatively, it would be really nice if when installing edbsrvr it could be told to read its parameters from a text file.
I guess what can or cannot be done is also dependent on when edbsrvr.ini is created. >>

IMHO, building your own custom server is the way to go.

My custom servers have an INI file that they read some settings from.  Most of the properties are set in code inside the servers.

I use the SVCom components (http://www.aldyn-software.com/svcom.html) to create a custom server that runs as a service.

I use InnoSetup to install the server as well as other services.  I also have a separate program that allows the customer to manage the application services (see attached).

= Steve