Upgrading with the graphical user interface installer v7
You can upgrade to Replication Server 7 using the graphical user interface installer.
Before starting the upgrade process, replicate any pending backlog of transactions on the publication tables.
After all pending transactions are replicated to their target databases, stop the Replication Server 6.2.x publication server and subscription server. See Registering a publication server and Registering a subscription server.
Ensure the installation user has administrative permissions on the
XDB_HOME/xdata
folder. On Windows, this can be done by opening the Replication Server installation directory in Windows Explorer and selecting the xdata folder. When prompted, select Continue to enable the required permission.Install Replication Server 7. See Installation and uninstallation for instructions on installing Replication Server, but note the differences described in the following steps.
Following the acceptance of the license agreement, the Select Components screen appears but with the entries grayed out. The old Replication Server components are replaced with the new ones in the old Replication Server’s directory location. Select Next.
The Existing Installation screen confirms that an existing Replication Server installation was found. To proceed with the upgrade, select Next.
On the Ready to Install screen, select Next.
The remaining screens that appear confirm completion of the installation process and allow you to exit from Stack Builder or StackBuilder Plus.
After installation completes, the publication server of the new Replication Server product is running, connected to the controller database used by Replication Server 6.2. The subscription server might be running at this point. That is an expected outcome of this process.
Complete the publication server and subscription server configuration file setup.
In the
XDB_HOME/etc
directory, a new set of configuration files for Replication Server version 7 are created. These files are namedxdb_pubserver.conf.new
andxdb_subserver.conf.new
. The new configuration files contain any new configuration options added for Replication Server 7.The old configuration files used by Replication Server version 6.2.x remain unchanged as
xdb_pubserver.conf
andxdb_subserver.conf
.Merge the old and new configuration files so that the resulting, active configuration files contain any new Replication Server 7 configuration options as well as any nondefault settings you used with the Replication Server 6.2.x and want to continue to use with Replication Server 7. The final set of active configuration files must be named
xdb_pubserver.conf
andxdb_subserver.conf
.In the
XDB_HOME/etc/sysconfig
directory, make sure the Replication Server startup configuration filexdbReplicationServer-62.config
contains the parameter settings you want to use with Replication Server 7. See Replication Server startup configuration file for information on this file.Restart the publication server and the subscription server. See Registering a publication server and Registering a subscription server).
Check the publication server and subscription server log files to verify that no errors occurred (see Publication and subscription server startup failures).
Adjust the publication server and subscription server port numbers if necessary.
The Replication Server 7 publication and subscription servers are installed to use the default port numbers
9051
and9052
, respectively. If the Replication Server 6.2.x replication systems used port numbers other than9051
and9052
, then make the changes to correct this inconsistency as described in Updating the publication and subscription server ports.If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console as described in Registering a publication server and Registering a subscription server. The existing replication systems appear in the replication tree of the Replication Server Console.
You are now ready to use Replication Server 7 to create new replication systems and manage existing ones.
Note
For Windows: If you give a new admin password during an upgrade, it is ignored. After the upgrade, Replication Server picks the old admin user name and password (which is saved in edb-replconf
).