> I am trying to bundle up the SAP database with my > application. To avoid version inconsistencies, I want to ship > the SAP version (against which I tested my application) along > with my application.
It is generally possible to install several versions (or multiple installations of the same version) on one machine. - they share some files like the communication server - database names must be unique - the dabase manager will see all installations and databases > > Is there a way we could have my own application specific SAP > Version installed on a machine (ie., my SAP co-exists with > another instance of SAP that has already been installed on a > given machine). I am looking for something like prefixing the > registry key names and NT Service Names with "MYAPP". Is this > possible? Has somebody attempted this? Only if you compile your own version. There doesn't exist a list containing all the items that would have to be changed as well in addition to registry keys and service names. Probably the port for the communication server as well, maybe more ... > Also, I want to ship a installed directory tree (bundled with > my app) as opposed to shipping the installer itself The stuff in <dependent path> is easy, you can simply copy it and call dbmcli inst_reg ... The files in the <independent path> need to be installed, because this prevents an older release from overwriting a newer one. And of course you shouldn't remove these files if someone did a seperate SAP DB installation afterwards. If you look at a windows installation package, you'll notice that it contains a lot of .tgz archives. each archive contains a Perl script (e.g. jdbcinst) which contains all the commands for registration etc.) Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
