Removing an existing Adaptive Server

1.                           To remove an existing Adaptive Server, from $SYBASE, enter:

2.                               rm servername.*

3.                           Change to the directory $SYBASE/$SYBASE_ASE/install and run the following commands:

4.                               rm RUN_servername.*

5.                               rm servername.*

6.                           Edit $SYBASE/interfaces, to remove all references to the Adaptive Server.

7.                           If you used operating system files for database devices, remove those.

 

 

********************************************************************************************************************************************************************************************
This message is intended only for the stated addressee(s) and may be confidential. Access to this email by anyone else is unauthorised. Any opinions expressed in this email do not necessarily reflect the opinions of Fidessa. Any unauthorised disclosure, use or dissemination, either whole or in part is prohibited. If you are not the intended recipient of this message, please notify the sender immediately.

Fidessa plc - Registered office:
Dukes Court, Duke Street, Woking, Surrey, GU21 5BH, United Kingdom
Registered in England no. 3781700 VAT registration no. 688 9008 78

Fidessa group plc - Registered Office:
Dukes Court, Duke Street, Woking, Surrey, GU21 5BH, United Kingdom
Registered in England no. 3234176 VAT registration no. 688 9008 78

One server process multiple network handlers

One server process multiple network handlers

Configuring the server for multiple network handlers

To configure multiple network listeners:

1. Define a unique host name for each network interface in your operating system’s host database.

2. In your interfaces file, use a text editor to add copies of the “master” line for your Adaptive Server; one for each additional interface you want the server to listen on.

3. Include a unique host name on each line to configure a network handler for each network interface.

4. Port numbers within the interface need not be the same, but they can be. They fall under the same rules for naming and numeric range as the primary network interface.

Sample interfaces files for multiple network handlers

The following example shows an interfaces file for an Adaptive Server with two network interfaces. The server host machine is known as SERV_CORPNET on the corporate network and SERV_ENGNET on the engineering network.

# PRODUCTION server with two network listeners

 PRODUCTION<tab>3<tab>3<newline>

 <tab>master tcp ether SERV_CORPNET 4559

 <tab>master tcp ether SERV_ENGNET 5479

 <tab>query tcp ether SERV_CORPNET 4559

When Adaptive Server restarts, it spawns a network handler process for each master line in the entry that corresponds to the server’s DSLISTEN value. Connections made on each interface are handled equally, as peers.