Completing the worksheet

Fill out each section of the installation worksheet.

rs_init supplies default values for most of the items on the worksheets in “Replication Server installation worksheet” and “Database setup worksheet”. Many of the defaults are constructed from values that you enter. For example, if you enter “TOKYO_RS” for the Replication Server name, rs_init names the log file TOKYO_RS.log. You can accept the displayed value or enter something else.

To use the rs_init defaults, complete the required items on the worksheet, which are marked with an asterisk (*). When you run rs_init, copy the default values from the menu to the worksheet so that you have a complete record of the configuration.

Replication Server reserves identifiers that begin with “rs_”. Do not use names that begin this way for Adaptive Servers, Replication Servers, database objects, or login names. See the Replication Server Reference Manual for other restrictions.

Release directory

The release directory—also called the installation directory—is where you install Replication Server software. Replication Server creates a new directory structure that allows you to use multiple versions of some components. For more information, see the Replication Server Installation Guide for your platform.

NoteWhen installing Replication Server 15.0.1 in the existing directory structure of Replication Server 15.0, the latest version replaces the old one. If you think of reverting from version 15.0.1 to 15.0, you must make a complete backup of the directory structure of version 15.0 prior to installing version 15.0.1. For more details, see Chapter 4,”Special upgrade and downgrade instructions” in the Release Bulletin for your platform.

You can install Replication Server version 15.0.1 in the existing directory structure of Replication Server version 12.0 and later.

Make sure the “sybase” user has write permission for the Sybase release directory. See the Replication Server Installation Guide for your platform for more information about the “sybase” user.

In the .cshrc or .profile file of the “sybase” user, set the SYBASE environment variable to the full path of the Sybase release directory. For example, if your path is /work/sybase, set the SYBASE environment variable as shown.

If you use the C shell, add this line to the .cshrc file:

setenv SYBASE /work/sybase

At the shell prompt, enter:

source .cshrc

If you use the Bourne shell, add this line to the .profile file:

SYBASE="/work/sybase"; export SYBASE

At the shell prompt, enter:

. .profile

Record the release directory on the worksheet.

NoteIn addition to $SYBASE, Replication Server version 15.0.1 uses environment variables for Replication Server ($SYBASE_REP), and Open Client/Server™ ($SYBASE_OCS). See Chapter 3 of the Replication Server Installation Guide for your platform for more information.

Replication Server information

This section explains how to complete the “Replication Server information” section of the worksheet:

Replication Server security information

This section explains how to fill out the “Replication Server security information” section of the worksheet. See Chapter 8 “Managing Replication Server Security” in the Replication Server Administration Guide Volume 1, for more information on security, and Chapter 5, “Secure Sockets Layer” in this book for information specific to configuring SSL.

Network security is available only on Solaris.

Replication Server interfaces information

Use the “Replication Server interfaces information” section of the worksheet to record information that defines the network port where Replication Server listens for connections. Each entry in the interfaces file is called a listener service.

NoteIf you are using network-based security, available with version 11.5 or later, use the directory services of your network security mechanism to register Replication Servers, Adaptive Servers, and gateway software. See the documentation that comes with your network-security mechanism for details.

ID Server information

One Replication Server in a replication system is the ID Server. In addition to the usual Replication Server tasks, the Replication Server acting as the ID Server assigns a unique ID number to every Replication Server and database in the replication system. The ID Server also maintains version information for the replication system. Otherwise, the ID Server is like any other Replication Server.

When you install a new Replication Server or add a database to your replication system, the ID Server must be running. This allows the new Replication Server, or the Replication Server that manages the new database, to log in and retrieve an ID number. The ID Server must also be running whenever you create a route.

You must install the ID Server before you install any other Replication Server. If you have only one Replication Server, that server is also the ID Server. If you are installing for the first time, the Replication Server is the ID Server. If you are adding a Replication Server to an existing replication system, you must know the name of the Replication Server in the system that is the ID Server.

WARNING! The ID Server is critical to your replication environment, and is difficult to move once it has been installed. Plan your installation carefully.

Replication Server System Database information

Replication Server maintains its system tables in its system database. You can choose to set up a Replication Server System Database (RSSD) in an Adaptive Server Enterprise database, or an Embedded Replication Server System Database (ERSSD) in an Adaptive Server Anywhere database. Use the information in this section to complete the “Replication Server System Database” section of the worksheet.

If you want an RSSD with Adaptive Server Enterprise, see “Adaptive Server Enterprise RSSD information”. If you want an ERSSD with Adaptive Server Anywhere, see “Adaptive Server Anywhere ERSSD information.”

Adaptive Server Anywhere ERSSD information

If you want an ERSSD, enter on your worksheet the information below. See Chapter 4, “Managing a Replication System” in the Replication Server Administration Guide Volume 1, for more information on ERSSDs. All fields are required.

Noters_init automatically fills these fields with default values on the same device. However for better performance and recoverability, place the ERSSD database directory, ERSSD transaction log directory, and ERSSD backup directory on separate devices.

Adaptive Server Enterprise RSSD information

If you want an RSSD using Adaptive Server Enterprise, enter the following:

Adaptive Server Enterprise RSSD device information

If you do not want rs_init to create the RSSD, skip this section. Go to “Disk partition information”.

If you selected Yes for “Create RSSD,” read this section and complete the “RSSD Device Information” section of the worksheet.

The RSSD device is the Adaptive Server database device where rs_init creates the Replication Server RSSD. Therefore, choose a database device other than the default master device, that has the minimum amount of space required. Use sp_helpdevice to list the available devices.

Noters_init by default uses a minimum of 40MB for the database size, and 16MB for the RSSD log size.

Select one of the following if the Adaptive Server does not have a device available for the RSSD:

If you want rs_init to create the device, verify that the disk file or raw partition you want to use exists and has the proper permissions. Execute sp_configure devices in Adaptive Server to verify that the value for devices is high enough to allow you to add a new device. See the Adaptive Server System Administration Guide for information about device requirements.

Use the information in this section to complete the “RSSD device information” section of the worksheet:

Disk partition information

Replication Server uses disk partitions for stable queues, which temporarily store the data it receives and sends.

Replication Server can use raw partitions, if they are available on your platform, or operating system files. Raw partitions provide improved recovery capability because the operating system does not buffer their I/O.

The minimum partition size is 20MB. You can add more partitions after the Replication Server is installed.

Use the information in this section to complete the “Disk partition information” section of the worksheet:

StepsCreating a disk partition

If you use an operating system file for a partition, the file must exist before you specify it in rs_init.

  1. To create an empty file for a partition, use a text editor or the UNIX touch command. Verify that there is enough free space on the file system for the file to grow to the size you specify. Replication Server extends the file to the full partition size during installation. Grant read and write permissions on the file to the “sybase” user.

    For example, log in as the “sybase” user, and create the file with this command, where path is the full path to the disk file:

    touch path
    
  2. Set the permissions on the file:

    chmod 600 path
    

Remote site connections information

The “Remote site connections information” section of the worksheet defines a login name for other Replication Servers to use when logging in to this Replication Server. rs_init creates this login after installing the Replication Server.

Database RepAgent information

See “Planning the replication system” for more information about when an RSSD requires a RepAgent.

Use the information in this section to complete the “Database Replication Agent information” section of the worksheet: