User's Guide
   PART 4. Database Administration and Advanced Use
     CHAPTER 27. Deploying Databases and Applications       

Deployment overview

The following deployment steps are examined in this chapter:

• Determining required files based on the choice of application platform and architecture.

• Configuring client applications.

• Understanding the file name convention to determine the function and platform of files.

  Deployment models

The files you need to deploy depend on the deployment model you choose. Here are some possible deployment models:

• Client deployment     You may deploy only the client portions of Adaptive Server Anywhere to your end-users, so that they can connect to a centrally located network database server.

• Network server deployment     You may deploy network servers to offices, and then deploy clients to each of the users within those offices.

• Embedded database deployment     You may deploy an application that runs with the personal database server. In this case, both client and personal server need to be installed on the end-user's machine.

• SQL Remote deployment     Deploying a SQL Remote application is an extension of the embedded database deployment model.

  Ways to distribute files

There are two ways to deploy Adaptive Server Anywhere:

• Use the Adaptive Server Anywhere installation     You can make the Setup program available to your end-users. By selecting the proper option, each end-user is guaranteed of getting the files they need.

  This is the simplest solution for many deployment cases. In this case, you must still provide your end users with a method for connecting to the database server (such as an ODBC data source).

• Develop your own installation     There may be reasons for you to develop your own installation program that includes Adaptive Server Anywhere files. This is a much more complicated option, and this chapter addresses the needs of those who are developing their own installation.

  If Adaptive Server Anywhere has already been installed for the server type and operating system required by the client application architecture, the required files can be found in the appropriately named subdirectory, located in the Adaptive Server Anywhere installation directory.

  For example, assuming the default installation directory was chosen, the win32 subdirectory of your installation directory contains the files required to run the server for the Windows 95/Windows NT platform.

Of course, whichever option you choose, you must not violate the terms of your license agreement.

  Where to install files

For a deployed application to work properly, the database server and client libraries must each be able to locate the files they need. The deployed files should be located relative to each other in the same fashion as your Adaptive Server Anywhere installation.

In practice, this means that on PC's, most files belong in a single directory.

     For a full description of the places where the software looks for files, see How Adaptive Server Anywhere locates files.

  UNIX deployment issues

UNIX deployments are different from PC deployments in some ways:

• Directory structure     For UNIX installations, the directory structure is as follows:

  Directory	Contents
  /opt/SYBSasa6/bin	Executable files
  /opt/SYBSasa6/lib	Shared objects and libraries
  /opt/SYBSasa6/res	String files

  On AIX, the default root directory is /usr/lpp/SYBSasa6 instead of /opt/SYBSasa6.

• File extensions     In the tables in this chapter, the shared objects are listed with an extension .so. For HP-UX, the extension is .sl.

  On the AIX operating system, shared objects that applications need to link to are given the extension .a.

• Symbolic links     Each shared object is installed as a symbolic link to a file of the same name with the additional extension .1 (one). For example, the libdblib6.so is a symbolic link to the file libdblib6.so.1 in the same directory.

  If patches are required to the Adaptive Server Anywhere installation, these will be supplied with extension .2, and the symbolic link must be redirected.

• Threaded and unthreaded applications     Some shared objects are provided in two forms, one of which has the additional characters _r before the file extension. For example, in addition to libdblib6.so, there is a file named libdblib6_r.so. In this case, threaded applications must be linked to the _r shared object, while non-threaded applications must be linked to the shared object without the _r characters.

     For a description of the places where the software looks for files, see How Adaptive Server Anywhere locates files.

  Windows CE deployment issues

For Win CE 2.0, all DLLs must go in the \Windows directory. To facilitate finding the Adaptive Server Anywhere DLLs in this directory, the DLLs for Windows CE all have the prefix ASA_:

• ASA_dblgen6.dll

• ASA_dblib6.dll

• ASA_dbodbc6.dll

• ASA_dbuodbc6.dll

• ASA_dbfile.dll

• ASA_dbsmtp.dll

• ASA_dbwtsp6.dll

In Windows CE 2.1, the operating system searches the directory containing the executable that loads the DLL, so the SQL Remote DLLs (dbfile and so on) could go into the folder that will contain Adaptive Server Anywhere. However, dblib6.dll and dbodbc6.dll, since they are loaded from other applications, must still go in \Windows, as must the language DLL dblgen6.dll.