Installation Guide Adaptive Server Enterprise for Silicon Graphics IRIX

Appendix A Alternative Installation Methods

Chapter 11

Alternative Installation Methods

Resource file installation

You can create an Adaptive Server or Backup Server, using values specified in a resource file that defines the attributes for the server.

Resource files are ASCII format template files that contain configuration variables. To use the template files, edit the resource file, replace variables with desired values, and execute the svrbuildres utility. The svrbuildres utility uses the variables to create servers.

Resource files allow you to create servers in batch mode. You can create servers on multiple systems from the same resource file by editing a few values in that file. Within a single resource file, you can create only one server at a time.

The server files must already exist on the computer before the servers can be created. Use procedures in Chapter 4, "Installing Sybase Servers ."

You cannot install Monitor Server, XP Server or the full-text search engine using resource files.

To install an Adaptive Server or Backup Server using resource files:

Edit a resource file as described in "Installing from a resource file".
Execute the srvbuildres utility, using the edited resource file as described in "Using srvbuildres".

Installing from a resource file

You can install Sybase servers via a resource file. You can use either:

The sample resource file provided with the software, or
The resource file that is created by the srvbuild utility.

Editing a sample resource file

Sample resource files for creating Adaptive Server and Backup Server are included in your Adaptive Server distribution in:

$SYBASE/$SYBASE_ASE/init/sample_resource_files.

Edit these files to specify the attributes for the servers you want to create.

Note the following:

If you use USE-DEFAULT as the Adaptive Server name, the utility substitutes the name of the computer on which it is running for the server name. If you use USE-DEFAULT, do not create Backup Server entries in the resource file. They are created automatically using the default name.
To create a server with a different name, change the Adaptive Server name and use the new name with the "_BK" extensions for Backup Server. For example, the Backup Server for PIANO should be PIANO_BK.
The master device size must be at least 30MB.
The system procedure device and sybsystemprocs database sizes must be at least 100MB.
The auditing entries in the resource file are not supported and will not be processed by the utility. To enable auditing, see Configuring Adaptive Server Enterprise.

Editing a resource file created by srvbuild

You can create a resource file by running the srvbuild utility. A new file containing the values you specified for the Adaptive Server or Backup Server is written to:

$SYBASE/$SYBASE_ASE/init/logs/srvbuildMMDD.VVV-servername.rs.

Edit these files to specify the attributes for the servers you want to create.

Warning!

Be sure to edit the resource file generated by srvbuild to change attributes, such as device names, that may be different on another system.

Resource file attributes for Adaptive Server

Table A-1 shows the Adaptive Server resource file attributes, their default values, and other options.

The attributes in bold type are required.

All alpha values are case sensitive.

The prefix of the attribute name varies, depending on whether the resource file was created by srvbuild or by sybinit (from a pre-11.5 SQL Server). The prefix is ignored by srvbuildres when processing the resource file.

The attribute names in Table A-1 are the attribute names provided in the sample resource file included in your Adaptive Server distribution.

Resource file attributes for Adaptive Server
Attribute	Default value [other options]
sybinit.release_directory	The value of $SYBASE at your site
sybinit.product	sqlsrv
sqlsrv.server_name	server_name
sqlsrv.new_config	yes (required value)
sqlsrv.do_add_server (to interfaces file)	yes [no]
sqlsrv.network_protocol_list	tcp [spx]
sqlsrv.network_hostname_list	hostname
sqlsrv.network_port_list	port_number
sqlsrv.master_device_physical_name	path_and_name_of_master_device
sqlsrv.master_device_size	30 (MB)
sqlsrv.master_database_size	5 (MB)
sqlsrv.errorlog	$SYBASE/$SYBASE_ASE/install/server_name.log
sqlsrv.do_upgrade	no (required value)
sqlsrv.sybsystemprocs_device_physical_name	path_and_name_of_sybsystemprocs_device
sqlsrv.sybsystemprocs_device_size	100 (MB)
sqlsrv.sybsystemprocs_database_size	100 (MB)
sqlsrv.sybsytemdb_device_physical_name	path_and_name_of_ sybsystemdb_device
sqlsrv.sybsystemdb_device_size	5 (MB)
sqlsrv.sybsystemdb_database_size	5 (MB)
sqlsrv.default_backup_server	server_name_back

Resource file attributes for Backup Server

Table A-2 shows the Backup Server resource file attributes, their default values, and other options.

The attributes in bold type are required.

All values are case sensitive.

The attribute names in Table A-2 are the attribute names provided in the sample resource file included in your Adaptive Server distribution.

Resource file attributes for Backup Server
Attribute	Default value [other options]
sybinit.release_directory	$SYBASE
sybinit.product	bsrv
bsrv.server_name	server_name_back
bsrv.do_add_backup_server (to interfaces file)	yes [no]
bsrv.network_protocol_list	tcp [spx]
bserv.network_hostname_list	hostname
bsrv.network_port_list	port_number
bsrv.language	us_english [chinese, french, german, japanese, spanish]
bsrv.character_set	iso_1[iso_1, cp850, cp437, deckanji, ascii_8, eucgb, eucjis, mac, roman8, sjis, utf8]
bsrv.tape_config_file	$SYBASE/$SYBASE_ASE/ backup_tape.cfg
bsrv.errorlog	$SYBASE/$SYBASE_ASE/ server_name_back.log

Using srvbuildres

To execute srvbuildres at the UNIX prompt enter:

$SYBASE/$SYBASE_ASE/bin/srvbuildres -r resource_file

where resource_file specifies the resource file containing the attributes that describe the server to build.

Unlike srvbuild, the srvbuildres utility does not require any X libraries.

When you have completed resource file installation, go to Chapter 5, "Post-Installation Tasks."

Installing files in NOGUI mode

To install components in a NOGUI environment, perform all pre-installation preparation steps as described; however, replace the window-based Studio Installer instructions (Chapter 4, "Installing Sybase Servers ") with these instructions.

There are several arguments you can use when you run Studio Installer from the command line. The syntax is:

install -argument

-debug:
Use this argument to display output normally sent to the Installer.log.
-f filename
Use this argument to provide the file name of the file that contains all the input you want to use for a silent installation.
Before using this argument, you must create a file containing all the installation inputs (target directory, components to be installed, and so on).
-c
Use this argument run the installer without the graphical user interface. The Studio Installer prompts the user for the required user input.
-trace
Use this argument to print more detailed information to the Installer.log, which is useful for tracking abnormal executions of installations.
-version
Use this argument to obtain version information for the installer. Do not use any other arguments when using this argument.

Complete the following steps:

IRIX mounts the CD automatically.
If the CD is in your first CD-ROM drive, the CD is automounted as /CDROM.
At the prompt, type:
```
cd /CDROM
./install -c
```
Select the type of install to perform.
- Full Install
- Standard Install
- Cancel
From the prompt, enter the installation directory (the default is /usr/sybase/).
Select one of the following:
- Continue - to continue.
- Previous Menu - to return to the previous screen.
- Cancel - to terminate the installation procedure.
The installer prompts: "Have you registered Sybase Software Asset Management Certificates at a central license host?"
If Yes, enter the following information about the primary network node from which this machine will be checking out licenses:
- License Manager Host is the host name of the primary network node on which you installed the asset management software.
- License Manager Port is an unused port number on the primary network node. The local Adaptive Server uses this port number to contact the primary network node when checking out licenses.

For information on licensing features on the primary license host, see Chapter 3, "Sybase Software Asset Management (SySAM)."

Completing the installation process

Follow the directions on the screen.
When the installation is complete, use the asecfg utility to:
- Configure a New Server - launches the srvbuild utility (Chapter 4, "Installing Sybase Servers .")
- Upgrade an Existing Server - launches the sqlupgrade utility (Chapter 8, "Upgrading Sybase Servers .")
- Localize an Existing Server - launches the sqlloc utility. See Configuring Adaptive Server Enterprise.
- Edit the Interface File - launches the dsedit utility to modify the interfaces file.
- Exit - exits the configuration utility.
  For information about these Sybase installation and configuration utilities, see the Utility Guide for your platform.
Exit the asecfg utility.
Check the installation log file to see a record of the installation process. The server log file is located in:
$SYBASE/Installer.log
When the unloading is complete, log out as the "sybase" user.
When the unloading is complete, eject the CD using the eject command.

Installing components in cmdfile

To install components by means of a cmdfile, you must begin in GUI mode. To begin the installation process:

Verify that you are logged in as the "sybase" user with "root" privileges and that your environment is set up as described in the "Pre-installation tasks ".
Insert the Server CD in the CD-ROM drive.
At the UNIX prompt, start the Studio Installer:
```
cd /CDROM
./install
```
Select the type of installation to be performed. Backup Server, Monitor Server, and XP Server are installed, by default, with Adaptive Server.
- Standard Install - a standard install installs all the components necessary for most users.
- Full Install - a full install installs every component on the CD.
- Customized Install - a customized install allows you to select which components to install. Certain components are automatically installed if they are required to run other selected components.
Select a new installation directory, or accept the default.
If you select Customized Install, the next window is the Component Selection screen, which allows you to specify the components to install.
Components that would be installed in a standard installation appear with a check in the check box to the left of the product name. You may select or deselect components from this list. Components with subcomponents have a More... button enabled. Click this button to select or deselect subcomponents.
Click Save.
Specify a directory. The component information is automatically generated when saving to the cmdfile. You may rename the cmdfile.
After the information is written to the cmdfile, the installer returns you to the GUI. Click Cancel, then Yes, to exit the Studio Installer.
To complete the installation using the cmdfile, go to a command-line prompt at the CD-ROM drive and enter:
```
./install -f path/filename
```
where path is the full path to the cmdfile, and filename is the name of the cmdfile.
When the installation is complete, log out as the "sybase" user.
When the installation is complete, eject the CD using the eject command.
After Studio Installer is exited, the environment variables are set manually or with the.sh and .csh script files, automatically downloaded by the Studio Installer. The procedures for using the scripts files are provided in Chapter 4, "Installing Sybase Servers ."
Check the installation log file to see a record of the installation process. The server log file is located in:
$SYBASE/Installer.log
The PC-client installation log file is in:
%SYBASE%\Installer.log


	Expand Search