I have no knowledge of how to use SQLAnywhere, but I am tasked with deploying this application into our environment to workstations as a backend to an application.

I would like it to also be part of our standard OS image. Is there an issuing with creating a base oS image with this application installed (duplicate name, guid, etc..)?

asked 15 Jul '11, 14:19

dannyalvarado's gravatar image

dannyalvarado
31113
accept rate: 0%

edited 15 Jul '11, 14:57

Justin%20Willey's gravatar image

Justin Willey
6.7k108137208


I would suggest that you take a look at the Deploying Databases and Applications section with the documentation.

Wrt making the application part of a standard OS image, this should not be a problem provided that you:

  • have appropriately licensed the software for use on all of the computers to which you will deploy the application
  • you are either using the Personal Server (dbengX) or if using the Network Server (dbsrvX) that you uniquely name the server so that there are no name collisions on your network - including the name of the host within the server name is a easy way of resolving this issue.
permanent link

answered 15 Jul '11, 14:33

Mark%20Culp's gravatar image

Mark Culp
22.9k9129269
accept rate: 41%

We've also just published a new whitepaper titled "Embedding SQL Anywhere in Commercial Applications Requiring a Database" in which four deployment methods are discussed (Deployment Wizard, Copy Files, InstallShield and Silent Install).

When you create the OS image, just deploy SQL Anywhere using one the methods described in the whitepaper. As Mark suggests, pay special attention to the database server licensing and network database server name.

You can find the whitepaper at http://www.sybase.com/detail?id=1093518.

permanent link

answered 15 Jul '11, 16:38

Jos%C3%A9%20Ramos's gravatar image

José Ramos
1.0k51524
accept rate: 30%

The paper was written for SQL Anywhere 12, but the concepts also apply to earlier versions.

(15 Jul '11, 16:39) José Ramos

Assuming that you are not installing server engines (dbsrvxx.exe - ie a database server that can be accessed over the network), and you have the licencing side covered, that should work fine.

It might be worth giving a bit more detail in case other people have relevant experience. You say "deploying this application into our environment to workstations as a backend to an application" - does each workstation have its own database, or are you installing clients connecting to a single backend database? What imaging solution are you using, etc?

permanent link

answered 15 Jul '11, 14:34

Justin%20Willey's gravatar image

Justin Willey
6.7k108137208
accept rate: 20%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×137
×41

question asked: 15 Jul '11, 14:19

question was seen: 1,072 times

last updated: 15 Jul '11, 16:39