Hi all,

I have a new customer who does not want to give me any
access to their server. I have bought an OEM sql anywhere
11.0.1. and i want to use the deployment wizard to create a
msi file for them to install sql anywhere 11.0.1. I dont
want to give them the master password , they might take
advantage of it. So how can i create a msi file with the
password already in it ?

Also i am curious to know how can i preset this msi file
already with a certain service created , with the necessary
parameters ?

I want to avoid that my customer has to manually type some
of my directions ...

TIA
JVL

The "Deploy SQL Anywhere" wizard will not do all of this for you.

JVL wrote:
I'm confused - which password are you referring to?

- If you're referring to your serial key to install SQL Anywhere, this
is not contained within the deployed components.

- If you're referring to supplying your connection string to connect to
the database, you may wish to provide a ".conf" file with the
information already hidden by "dbfhide" (See:
http://dcx.sybase.com/1101en/dbadmin...ty-syntax.html )

e.g.

[in connectstring.txt]
-c "UID=dba;PWD=MySecretPassword"

dbfhide connectstring.txt connect.conf

dbisql @connect.conf -c
"ENG=MyServer;DBN=MyDatabase;LINKS=tcpip(host=host name;port=2638)"

This is the main reason we encourage customers to build their own
installers. If you need to do this kind of operation, either use the
"dbsvc" utility afterwards and create a batch file for the customer to
run, or generate an installer using an "Install framework" to have the
installer create the service for you. e.g.

http://helpnet.acresso.com/robo/proj...addservice.htm

Regards,

--
Jeff Albion, Sybase iAnywhere

iAnywhere Developer Community :
http://www.sybase.com/developer/libr...ere-techcorner
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
SQL Anywhere Patches and EBFs :
http://downloads.sybase.com/swd/summ...&timeframe =0
Report a Bug/Open a Case : http://case-express.sybase.com/cx/

In addition to what Jeff said, if you want to deliver an initial
database that is protected, you can do that easily by just creating
the database yourself, changing userids/passwords as you desire, then
ship them the *.db file in addition to the *.msi stuff that installs
the software. Be sure to include other user ids that can do backups,
validations, etcetera so the customer can do those operations without
having full dba privileges.

Breck

On 1 Sep 2009 01:34:36 -0700, JVL wrote:

--
Breck Carter http://sqlanywhere.blogspot.com/

RisingRoad SQL Anywhere and MobiLink Professional Services
breck.carter (AT) risingroad (DOT) com