Registering a publication server v7

When you register a publication server, you're identifying the network location, admin user name, and password of a specific, running, publication server instance. You want to use this instance to manage all aspects of the publications you create subordinate to it.

It's important that you record the login information for the publication server. You must always use this same publication server instance to manage all publications created subordinate to it as represented in the Replication Server console replication tree.

Step 1: Start the publication server if it's not already running.

Note

If you're using Oracle publication or subscription databases, and the publication server wasn't restarted since copying the Oracle JDBC driver to the lib/jdbc subdirectory of your Replication Server installation, restart the publication server.

For Linux only: You can verify the publication server is running by using the systemctl command for CentOS 7 or RHEL 7 and Rocky Linux, AlmaLinux, or RHEL 8, and the service command for previous Linux versions.

Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8:

systemctl status edb-xdbpubserver

For previous Linux versions:

service edb-xdbpubserver status

If the publication server is running and you want to restart it, use the restart option.

For CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8:

systemctl restart edb-xdbpubserver

For previous Linux versions:

service edb-xdbpubserver restart

If the publication server isn't running, use the start option.

For CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8:

systemctl start edb-xdbpubserver

For previous Linux versions:

service edb-xdbpubserver start

Similarly, use the stop option to stop the publication server.

For Windows only: Open Control Panel > System and Security > Administrative Tools > Services. The publication server runs as a service named Publication Service for Replication Server. Use the Start or Restart link for the service.

If the publication server doesn't start, see Publication and subscription server startup failures.

Step 2: Register the publication server. Open the Replication Server console from the system’s application menu. For Replication Server installed from an Replication Server RPM package, invoke the script XDB_HOME/bin/runRepConsole.sh to start the Replication Server console.

Step 3: Select the top-level Replication Servers node. Select File > Publication Server > Register Server.

In the Register Publication Server dialog box, enter the values you supplied while installing Replication Server unless otherwise specified.

  • Host. Network IP address of the host running the publication server. This is the network IP address used for pub_ipaddr in the pg_hba.conf file in Postgres server authentication. (Don't use localhost for this field.)
  • Port. Port number the publication server is using. This is the port number you specified on the Publication Server Details screen in Step 16 of Postgres server authentication.
  • User Name. Admin user name used to authenticate your use of this publication server. This is the user name you specified on the Replication Server Admin User Details screen in Step 15 of Installing with Stack Builder or StackBuilder Plus.
  • Password. Password of the admin user given in the User Name field.
  • Save login information. Select this box if you don't want to register the publication server each time you open the Replication Server console. See Saving server login information for additional information on the advantages and disadvantages of saving server login information.
Note

The user name and password combination you enter is authenticated against the admin user name and password in the Replication Server configuration file residing on the host with the IP address you enter in the Host field.

After you fill in the fields, select Register. A Publication Server node appears in the replication tree of the Replication Server console. Expand the Publication Server node to expose the SMR and MMR type nodes.

Continue to build the single-master replication system under the SMR type node.