We do a similar procedure in a Linux RPM, Solaris package, and a Windows InstallShield script using method "a" below. The problem with method "b" is getting all the registry setting and file setting correct and updates when a version changes (many of the settings change). You also need to reload the system catalog on an update (performed by sdbupd).
We do the following for the initial install:
sdbinst -batch -profile all -depend <path> -indep_prog <path> -indep_data <path>
Then use commands similar to the create_demo_db.sh as Matthias has already suggested (actually we generate this file based on user sizing requirements). You can tailor the packages installed - the command is just a bit longer. For updates, I have been doing:
sdbinst -batch -profile all sdbupd -batch -d XXX -u UUU,PPP -package all
Good luck! Mark
Axel Busch wrote:
Hi Matthias,
thank you for your comment. However, that was not what I wanted to know. Maybe my request was not clear enough.
I would like to integrate the SAP DB _installation process_ within another installation routine for one of my software products that utilizes SAP DB.
To accomplish this, I need to know how to
a) either feed the SDBINST program with default input and handle errors or b) what to do when a) is not possible.
My thoughts regarding b) run along the line 1) Make a default installation 2) save all files and the registry keys to someplace 3) For installation, copy all the files to the clients computer 4) create the required registry entries, taking care to set the right folders 5) enter the sql16 etc. lines in windows' services file 6) register the x_server
The next step would then be what you suggested, to create the database instance.
Any ideas anybody?
best regards, Axel
If you're intereseted, here is the long story:
I have a Software Product that uses some Database System as data storage. Very inventive, isn't it :)
Personally I prefer SAP DB, because it has all the features/benefits
I need (Multi Platform Support, Trigger, DbProcs, low administration,
... you name it. We all know why we love our SAP DB.).
Unfortunately my Clients don't always see it that way, and when
I want to install (or ask their admin to install) SAP DB, I am often confronted by "SAP DB? Why, we have this perfect ORACLE/MSSQL/
DB2/SYBASE Database. You have to use this."
Haha. Converting all those tables, triggers, stored procedures
and supporting them for the next hundred years is something I can do without. By integrating the SAP DB installation into one big installation
process, it just becomes part of the whole package. No questions,
no problems.
And we really have only the best experiences with our SAP DB installations for more than two years now. I cannot say this from
Oracle or SQL Server. Great praise and thanks to the people in Berlin!
-----Urspr�ngliche Nachricht-----
Von: Matthias Griem [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 10. Februar 2004 12:28
An: [EMAIL PROTECTED]
Betreff: Re: embedded SAP DB / unattended installation
Am Dienstag, 10. Februar 2004 09:17 schrieb Axel Busch:
Hi,install SAP DB on a Linux-box have a look in this file:
i would like to use SAP DB in a kind of embedded environment. Does SAP DB provide a method of unattended/automatic installation?
I checked the installation log for windows. Is copying the
files, setting the windows registry keys and adding the entries
to the services file really enough?
How about linux?
/opt/sapdb/testdb74/create_demo_db.sh
with repmcli in shell-scripts you can do nearly everything ;-)
------snip--------
Prog="repmcli -u ${DBuser},${DBpass} -d ${DB} -n ${DBhost}"
INSTROOT=/opt/sapdb/depend74 PATH=/opt/sapdb/depend74/bin:$PATH export PATH
echo "create Tables, manipulate Data, etc ..." ${Prog} -b file_with_sql_statements_inside.sql
-----snap---------
best regards
Matthias
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
