HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide

[Contents][Glossary][Index][Back][Next]

2.5.1 Setting up a source Datareplicator's communications environment

This section explains the settings for a source Datareplicator's communications environment and includes examples.

Organization of this subsection
(1) Settings for a source Datareplicator's communications environment
(2) Examples of a communications environment for a source Datareplicator

(1) Settings for a source Datareplicator's communications environment

The following shows the settings for a source Datareplicator's communications environment.

Table 2-10 Settings for a source Datareplicator's communications environment

Communications environment Settings Server machine subject to setup
Source HiRDB is a single server Source HiRDB is a parallel server
/etc/services Specify the service-name and port-number#1 to be used for communication with the target system. Specify this service name in the hdeservice operand in the transmission environment definition. Use the same port number as for the target system. SDS BES
/etc/services Specify the service-name and port-number#1 to be used for communication with the extraction master process and the extraction node master process. Specify this service name in the mstservice operand of the extraction system definition. Use the same port number for the server containing the system manager and back-end server. SDS MGR, BES#2
/etc/hosts Specify the IP-address and host-name to be used for communication with the target system. Specify this host name in the hdehost operand of the transmission environment definition. SDS BES
/etc/inetd.conf Register the entry used to start the extraction node master process. SDS MGR, BES

SDS: Server machine at which a single server is defined for the source HiRDB.

MGR: Server machine at which a system manager is defined for the source HiRDB.

BES: Server machine at which a back-end server (including back-end servers that do not contain any database subject to data extraction) is defined for the source HiRDB.

#1: You cannot specify a port number that has already been registered in the services file or that is being used by other software.

#2: Set up the communications environment for the server machine at which the system manager is defined with the source HiRDB and for all server machines at which a back-end server is defined.

(2) Examples of a communications environment for a source Datareplicator

The following are examples of setting up a source Datareplicator's communications environment.

(a) Example of /etc/services for a source Datareplicator

The following is an example of specifying the service name and port number in /etc/services:

service-name port-number/tcp

Note:
The underlined portion is a fixed value.

service-name
Specify any name.

port-number
Specify a valid value in the communications environment. No other service can be using this port number.
(b) Example of /etc/hosts for a source Datareplicator

The following is an example of specifying the IP address and host name in /etc/hosts:

IP-address host-name

IP-address
Specify any address.

host-name
Specify any name.
(c) Example of /etc/inetd.conf for a source Datareplicator

The following is an example of registering an entry to start the extraction node master process in /etc/inetd.conf.

For HP-UX or Solaris Datareplicator
hdeserv stream tcp nowait user1 /opt/hirdbds/lbin/hdenodemst hdenodemst

Note:
The underlined portions are fixed values. These examples are for the HP-UX Datareplicator.
To apply the change to the /etc/inetd.conf settings, execute the following command:
  • kill -HUP inetd-process-ID

For AIX Datareplicator
 
hdeserv  stream  tcp  nowait  user1  /bin/env  env [EXTSHM=ON] PSALLOC=early
NODISCLAIM=true
[LDR_CNTRL=MAXDATA=0x ... ] /opt/hirdbds/lbin/hdenodemst
 
Note:
The underlined values are fixed.
To apply the change to the /etc/inetd.conf settings, execute the following command:
  • kill -HUP inetd-process-ID

For Linux Datareplicator
In the Linux edition, replace /etc/inetd.conf with /etc/xinetd.conf and replace the inetd process with the xinetd process.
The following shows an example of /etc/xinetd.conf. Modify the underlined portion as appropriate to your environment.
service hdeserv
{
    socket_type     = stream
    protocol        = tcp
    wait            = no
    user            = user1
    server          = /opt/hirdbds/lbin/hdenodemst
}
Note:
To apply the change to the /etc/xinetd.conf settings, execute the following command:
/sbin/service xinetd reload

hdeserv
Specify the service name that is specified in mstservice in the extraction system definition.

user1
Specify a user name that belongs to the same group as the source HiRDB user.