From 8152eddf098ca23232b7526cf10697165c09d281 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 12 Oct 2023 16:24:44 -0400 Subject: [PATCH] edited nongenerated install topics for EPRS --- .../7/installing/installation_details.mdx | 10 ++--- .../7/installing/installing_jdbc_driver.mdx | 9 ++--- .../docs/eprs/7/installing/uninstalling.mdx | 25 +++++++------ .../upgrading_linux.mdx | 4 +- .../upgrading_with_gui_installer.mdx | 18 ++++----- .../upgrading_with_xdb_rpm_package.mdx | 6 +-- .../docs/eprs/7/installing/windows.mdx | 37 +++++++++---------- 7 files changed, 54 insertions(+), 55 deletions(-) diff --git a/product_docs/docs/eprs/7/installing/installation_details.mdx b/product_docs/docs/eprs/7/installing/installation_details.mdx index 2f1448b2a82..4884ed3d3d7 100644 --- a/product_docs/docs/eprs/7/installing/installation_details.mdx +++ b/product_docs/docs/eprs/7/installing/installation_details.mdx @@ -11,10 +11,10 @@ On Windows systems, the publication server and subscription server run as servic ## Linux details -On Linux hosts where you installed Replication Server with the graphical user interface or from the command line, you should now have a publication server daemon and a subscription server daemon running on your computer, assuming you chose to install the publication server and subscription server components. If you installed the Replication Server RPM package, you must start the publication server and the subscription server based on the instructions in [Registering a Publication Server](../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for the publication server and [Registering a Subscription Server](../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for the subscription server. +On Linux hosts where you installed Replication Server with the graphical installer or from the command line, a publication server daemon and a subscription server daemon are now running on your computer, assuming you chose to install the publication server and subscription server components. If you installed the Replication Server RPM package, you must start the publication server and the subscription server based on the instructions in [Registering a publication server](../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for the publication server and [Registering a subscription server](../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for the subscription server. !!! Note - On some Linux systems, you may have to restart the server before you can see the EPRS Replication Console choice in the application menu. If the Replication Console choice is still unavailable in the application menu, it can be started by invoking the script `XDB_HOME/bin/runRepConsole.sh`. + On some Linux systems, you might have to restart the server before you can see the EPRS Replication Console choice in the application menu. If the Replication Console choice is still unavailable in the application menu, you can start it by invoking the script `XDB_HOME/bin/runRepConsole.sh`. ## Additional details @@ -23,7 +23,7 @@ The Postgres application menu contains a new item for the EPRS Replication Conso !!! Note If Replication Server is installed from a Replication Server RPM package, start the EPRS Replication Console by invoking the script `XDB_HOME/bin/runRepConsole.sh`. -During the configuration process, you may need the following files that are created during installation. +During the configuration process, you might need the following files that are created during installation. | File Name | Location | Description | | ---------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------ | @@ -50,10 +50,10 @@ During the configuration process, you may need the following files that are crea - For Windows, Replication Server is installed in the `C:\Program Files\edb\EnterpriseDB-xDBReplicationServer` directory. !!! Note - `POSTGRES_HOME` is the home directory of the postgres operating system account (enterprisedb for Advanced Server installed in Oracle compatible configuration mode). + `POSTGRES_HOME` is the home directory of the postgres operating system account (enterprisedb for EDB Postgres Advanced Server installed in Oracle-compatible configuration mode). !!! Note - The publication and subscription services startup log files (`edb-xdbpubserver.log` and `edb-xdbsubserver.log`) are not generated for Windows and Mac OS X operating systems. + The publication and subscription services startup log files (`edb-xdbpubserver.log` and `edb-xdbsubserver.log`) aren't generated for Windows and Mac OS X operating systems. !!! Note `USER_HOME` is the home directory of the operating system account in use. diff --git a/product_docs/docs/eprs/7/installing/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/installing/installing_jdbc_driver.mdx index edf20254360..931fe13675c 100644 --- a/product_docs/docs/eprs/7/installing/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/installing/installing_jdbc_driver.mdx @@ -4,7 +4,7 @@ title: "Installing a JDBC driver" ## Choosing and installing a JDBC driver -Which JDBC driver you use depends on what database you're using. If you're using: +The JDBC driver you use depends on the database you're using. If you're using: - **EDB Postgres Advanced Server**, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). @@ -15,14 +15,14 @@ Which JDBC driver you use depends on what database you're using. If you're using - **Microsoft SQL Server**, use the freely available [Microsoft SQL Server JDBC](https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#102) driver. !!! Note -For Microsoft SQL Server, if your system uses JDK/JAVA then it is recommended that you use an equal or earlier mssql-jdbc jre version than the JDK/JAVA version on your system. For example, a system with JDK/JAVA version 18 can use `mssql-jdbc-11.2.0.jre18.jar`, `mssql-jdbc-11.2.0.jre17.jar`, and so on. +For Microsoft SQL Server, if your system uses JDK/JAVA, then we recommend that you use an equal or earlier mssql-jdbc jre version than the JDK/JAVA version on your system. For example, a system with JDK/JAVA version 18 can use `mssql-jdbc-11.2.0.jre18.jar`, `mssql-jdbc-11.2.0.jre17.jar`, and so on. !!! ## Configuring the driver After downloading the driver, create a symlink in the `XDB-install-folder/lib/jdbc` directory that points to the location where you installed the driver. -For Linux, create a symlink for the driver using these naming conventions: +For Linux, create a symlink for the driver using these naming conventions. | Driver | symlink name | | -------------------- | -------------- | @@ -32,5 +32,4 @@ For Linux, create a symlink for the driver using these naming conventions: | Microsoft SQL Server | mssql-jdbc.jar | | jTDS | jtds.jar | - For Windows, the drivers need to be copied to the `XDB-install-folder/lib/jdbc` directory and renamed using the same naming conventions. - + For Windows, copy the drivers to the `XDB-install-folder/lib/jdbc` directory and rename them using the same naming conventions. diff --git a/product_docs/docs/eprs/7/installing/uninstalling.mdx b/product_docs/docs/eprs/7/installing/uninstalling.mdx index 349b5876b22..e7c72a4afa9 100644 --- a/product_docs/docs/eprs/7/installing/uninstalling.mdx +++ b/product_docs/docs/eprs/7/installing/uninstalling.mdx @@ -7,7 +7,15 @@ redirects: -Uninstalling Replication Server results in the removal of the publication server, the subscription server, the EPRS console, the Replication Server command line interface, the EPRS replication configuration file, the Replication Server startup configuration file, the publication server configuration file, and the subscription server configuration file. +Uninstalling Replication Server results in the removal of the fllowing: +- Publication server +- Subscription server +- EPRS console +- Replication Server command line interface +- EPRS replication configuration file +- Replication Server startup configuration file +- Publication server configuration file +- Subscription server configuration file Uninstalling Replication Server doesn't remove any databases used as primary nodes, publication databases, or subscription databases. @@ -17,7 +25,7 @@ If you installed Replication Server using the Replication Server installer progr -## Uninstalling a RPM package installation +## Uninstalling an RPM package installation If you installed Replication Server from the RPM package, uninstall it using the yum package manager. @@ -93,23 +101,16 @@ Complete! ## Uninstalling a Windows installation -The following steps are for uninstalling Replication Server from a Windows host. +To uninstall Replication Server from a Windows host: 1. From the Windows Control Panel, select **Uninstall a Program**. - ![Uninstall a program](../images/image53.png) - -1. Select the Replication Server product in the list of programs to uninstall or change. Select **Uninstall/Change**. - - ![Uninstall or change a program](../images/image54.png) +1. From the list of programs to uninstall or change, select the Replication Server product. Select **Uninstall/Change**. 1. Select **Yes** to confirm that you want to unistall Replication Server. - ![Confirm Replication Server uninstallation](../images/image55.png) - -1. The Uninstallation Completed dialog box appears when the process has completed. Select **OK**. +1. The Uninstallation Completed dialog box appears when the process is complete. Select **OK**. - ![Uninstallation completed](../images/image56.png) ### Uninstalling in text or unattended mode diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx index 5c7febc4aa4..665023ca15a 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx @@ -10,11 +10,11 @@ If you have an existing Replication Server 7.x installation on Linux, you can us `yum upgrade edb-repo` -`yum` will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages: +`yum` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages: `yum upgrade edb-xdb*` -If you are upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details. +If you're upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details. After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](../installing_jdbc_driver/) for more information. diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx index 7de246140a8..cdba1735a7b 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx @@ -1,5 +1,5 @@ --- -title: "Upgrading with the graphical user interface installer" +title: "Upgrading with the graphical installer" redirects: - /eprs/7/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer/ - /eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer/ @@ -7,17 +7,17 @@ redirects: -You can upgrade to Replication Server 7 using the graphical user interface installer. +You can upgrade to Replication Server 7 using the graphical installer. 1. Before starting the upgrade process, replicate any pending backlog of transactions on the publication tables. 1. 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](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). -1. 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. +1. Ensure the installation user has administrative permissions on the `XDB_HOME/xdata` folder. On Windows, you can do this by opening the Replication Server installation directory in Windows Explorer and selecting the xdata folder. When prompted, select **Continue** to enable the required permission. 1. Install Replication Server 7. See [Installation and uninstallation](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for instructions on installing Replication Server, but note the differences described in the following steps. -1. 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**. +1. Following the acceptance of the license agreement, the Select Components screen appears but with the entries disabled. The old Replication Server components are replaced with the new ones in the old Replication Server’s directory location. Select **Next**. 1. The Existing Installation screen confirms that an existing Replication Server installation was found. To proceed with the upgrade, select **Next**. @@ -25,7 +25,7 @@ You can upgrade to Replication Server 7 using the graphical user interface insta The remaining screens that appear confirm completion of the installation process and allow you to exit from Stack Builder or StackBuilder Plus. -1. 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. +1. 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, which is an expected outcome of this process. 1. Complete the publication server and subscription server configuration file setup. @@ -33,15 +33,15 @@ You can upgrade to Replication Server 7 using the graphical user interface insta The old configuration files used by Replication Server version 6.2.x remain unchanged as `xdb_pubserver.conf` and `xdb_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` and `xdb_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` and `xdb_subserver.conf`. - In the `XDB_HOME/etc/sysconfig` directory, make sure the Replication Server startup configuration file `xdbReplicationServer-62.config` contains the parameter settings you want to use with Replication Server 7. See [Replication Server startup configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for information on this file. + In the `XDB_HOME/etc/sysconfig` directory, make sure the Replication Server startup configuration file `xdbReplicationServer-62.config` contains the parameter settings you want to use with Replication Server 7. See [Replication Server startup configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for more information. 1. Restart the publication server and the subscription server. See [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server)). 1. Check the publication server and subscription server log files to verify that no errors occurred (see [Publication and subscription server startup failures](../../10_appendix/02_resolving_problems/02_where_to_look_for_errors/#publication-and-subscription-server-startup-failures)). -1. Adjust the publication server and subscription server port numbers if necessary. +1. If necessary, adjust the publication server and subscription server port numbers. The Replication Server 7 publication and subscription servers are installed to use the default port numbers `9051` and `9052`, respectively. If the Replication Server 6.2.x replication systems used port numbers other than `9051` and `9052`, then make the changes to correct this inconsistency as described in [Updating the publication and subscription server ports](updating_sub_and_pub_ports). @@ -52,4 +52,4 @@ After upgrading and before using Replication Server, you need to download a JDBC You're 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`). + **For Windows:** If you give a new admin password during an upgrade, it's ignored. After the upgrade, Replication Server picks the old admin user name and password, which is saved in `edb-replconf`. diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx index 8c4758286d8..b392e85d7f3 100644 --- a/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx +++ b/product_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package.mdx @@ -24,7 +24,7 @@ If you're using Replication Server 6.2.x that was installed using the Replicatio - `/usr/edb/xdb/etc/xdb_subserver.conf` - `/usr/edb/xdb/etc/sysconfig/xdbReplicationServer-70.config` - Copies of these files are typically saved by the upgrade process if the files were modified since their original installation. However, it is safest to save copies in case the upgrade process doesn't. Use the saved files as your Replication Server 6.2.x configuration files for the updates described in Step 7. + Copies of these files are typically saved by the upgrade process if the files were modified since their original installation. However, it's safest to save copies in case the upgrade process doesn't. Use the saved files as your Replication Server 6.2.x configuration files for the updates described in Step 7. 1. If any Oracle publication or subscription databases are used in existing single-master replication systems, make sure a copy of the Oracle JDBC driver, version ojdbc5 or later, is accessible by the publication server and subscription server where Replication Server 7 will be installed. See [Enabling access to Oracle](../../05_smr_operation/01_prerequisites/03_enable_access_to_database/#enable_access_to_oracle) for information. @@ -171,9 +171,9 @@ If you're using Replication Server 6.2.x that was installed using the Replicatio 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 Replication Server 6.2.x and want to continue to use with Replication Server 7. - The final set of active configuration files must be contained in directory `/usr/edb/xdb/etc` named `xdb_pubserver.conf` and `xdb_subserver.conf`. In the `/usr/edb/xdb/etc/sysconfig directory`, make sure the Replication Server startup configuration file `xdbReplicationServer-70.config` contains the parameter settings you want to use with Replication Server 7. See [Replication Server configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for information on this file. + The final set of active configuration files must be contained in the directory `/usr/edb/xdb/etc` and named `xdb_pubserver.conf` and `xdb_subserver.conf`. In the `/usr/edb/xdb/etc/sysconfig directory`, make sure the Replication Server startup configuration file `xdbReplicationServer-70.config` contains the parameter settings you want to use with Replication Server 7. See [Replication Server configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for more information. -8. Restart the publication server and the subscription server (see sections [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server)). +8. Restart the publication server and the subscription server (see [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server)). 9. Check the publication server and subscription server log files to verify that no errors occurred (see [Replication Server configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file)). diff --git a/product_docs/docs/eprs/7/installing/windows.mdx b/product_docs/docs/eprs/7/installing/windows.mdx index 53ca41f57a4..1981241c7ef 100644 --- a/product_docs/docs/eprs/7/installing/windows.mdx +++ b/product_docs/docs/eprs/7/installing/windows.mdx @@ -12,27 +12,27 @@ EDB provides a graphical interactive installer for Windows. You can access it tw - Download the graphical installer from the [Downloads page](https://www.enterprisedb.com/software-downloads-postgres#replication-server) and invoke the installer directly. See [Installing directly](/eprs/latest/installing/windows/#installing-directly). -- Use Stack Builder (with PostgreSQL) or StackBuilder Plus (with EDB Postgres Advanced Server) to download the EDB installer package and invoke the graphical installer. See [Using Stack Builder or StackBuilder Plus](/eprs/latest/installing/windows/#using-stack-builder-or-stackbuilder-plus). +- Use Stack Builder (with PostgreSQL) or StackBuilder Plus (with EDB Postgres Advanced Server) to download the EDB installer package and invoke the graphical installer. See [Using Stack Builder or StackBuilder Plus](/eprs/latest/installing/windows/#using-stack-builder-or-stackbuilder-plus). ## Prerequisites -- You must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (Replication Console, publication server, or subscription server). Any Java product such as Oracle Java or OpenJDK may be used. Follow the directions for your host operating system to install the Java runtime environment. +- You must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (Replication Console, publication server, or subscription server). You can use Any Java product, such as Oracle Java or OpenJDK. Follow the directions for your host operating system to install the Java runtime environment. -- Be sure the system environment variable, `JAVA_HOME`, is set to the JRE installation directory of the JRE version and bitness (32-bit or 64-bit) you want to use with Replication Server. The Replication Server installer for a Windows platform contains both the 32-bit and 64-bit versions. The `JAVA_HOME` setting determines whether the 32-bit or the 64-bit version of Replication Server is installed. If `JAVA_HOME` is not set, the first JRE version encountered in the Path system environment variable determines the Replication Server version to be installed. +- Be sure the system environment variable, `JAVA_HOME`, is set to the JRE installation directory of the JRE version and bitness (32-bit or 64-bit) you want to use with Replication Server. The Replication Server installer for a Windows platform contains both the 32-bit and 64-bit versions. The `JAVA_HOME` setting determines whether the 32-bit or the 64-bit version of Replication Server is installed. If `JAVA_HOME` isn't set, the first JRE version encountered in the `path` system environment variable determines the Replication Server version to be installed. ## Installing directly After downloading the graphical installer, to start the installation wizard, assume sufficient privileges (superuser or administrator) and double-click the installer icon. If prompted, provide a password. -In some versions of Windows, to invoke the installer with Administrator privileges, you need to right-click on the installer icon and select **Run as Administrator** from the context menu. +In some versions of Windows, to invoke the installer with administrator privileges, you need to right-click the installer icon and select **Run as Administrator** from the context menu. -Proceed to the [Using the graphical installer](#using-the-graphical-installer) section. +Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using Stack Builder or StackBuilder Plus -If you are using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). +If you're using PostgreSQL, you can invoke the graphical installer with Stack Builder. See [Using Stack Builder](https://www.enterprisedb.com/docs/supported-open-source/postgresql/installer/03_using_stackbuilder/). 1. In Stack Builder, follow the prompts until you get to the module selection page. @@ -40,15 +40,15 @@ If you are using PostgreSQL, you can invoke the graphical installer with Stack B 1. Expand the **EnterpriseDB Tools** node and select **Replication Server**. -1. Proceed to the [Using the graphical installer](#using-the-graphical-installer) section in this topic. +1. Proceed to [Using the graphical installer](#using-the-graphical-installer). -If you are using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). +If you're using EDB Postgres Advanced Server, you can invoke the graphical installer with StackBuilder Plus. See [Using StackBuilder Plus](/epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/). 1. In StackBuilder Plus, follow the prompts until you get to the module selection page. 1. Expand the **EnterpriseDB Tools** node and select **Replication Server**. -1. Proceed to the [Using the graphical installer](#using-the-graphical-installer) section in this topic. +1. Proceed to [Using the graphical installer](#using-the-graphical-installer). ## Using the graphical installer @@ -58,34 +58,33 @@ If you are using EDB Postgres Advanced Server, you can invoke the graphical inst 1. Read the license agreement. If you accept the agreement, select the **I accept the agreement** option and select **Next**. -1. Browse to a directory where you want the Replication Server components to be installed, or allow the installer to install the components in the default location. Select **Next**. +1. Browse to a directory where you want to install the Replication Server components, or leave the default location. Select **Next**. -1. If you do not want a particular Replication Server component installed, uncheck the box next to the component name. Select **Next**. +1. If you don't want a particular Replication Server component installed, clear the box next to the component name. Select **Next**. 1. Enter information for the Replication Server administrator. !!! Note - From this point on, we suggest you record the values you enter as they will be needed during the publication and subscription server registration process. + From this point on, we suggest you record the values you enter as you need them during the publication and subscription server registration process. Enter values for the following fields: - - **Admin User** — The Replication Server administrator user name needed to authenticate some Replication Server actions such as registering a publication server or subscription server running on this host. Any alphanumeric string may be entered for the admin user name. The default admin user name is *admin*. + - **Admin User** — The Replication Server administrator user name needed to authenticate some Replication Server actions, such as registering a publication server or subscription server running on this host. You can enter any alphanumeric string for the admin user name. The default admin user name is admin. - **Admin Password** — Password of your choice for the Replication Server administrator. The admin user and the admin password (in encrypted form) are saved to the `XDB_HOME\etc\edb-repl.conf` configuration file. Select **Next**. -1. If a publication server is being installed, enter an available port on which the publication server can run. The default port number is *9051*. Select **Next**. +1. If a publication server is being installed, enter an available port on which the publication server can run. The default port number is `9051`. Select **Next**. -1. If a subscription server is being installed, enter an available port on which the subscription server can run. The default port number is *9052*. Select **Next**. +1. If a subscription server is being installed, enter an available port on which the subscription server can run. The default port number is `9052`. Select **Next**. -1. If you are using EDB Postgres Advanced Server installed in Oracle compatible configuration mode, enter `postgres` or `enterprisedb` for the operating system account under which the publication server or subscription server runs. +1. If you're using EDB Postgres Advanced Server installed in Oracle-compatible configuration mode, enter `postgres` or `enterprisedb` for the operating system account under which the publication server or subscription server runs. 1. On the Ready to Install page, select **Next**. - An information box shows the installation progress of the selected components. This may take a few minutes. + An information box shows the installation progress of the selected components. This might take a few minutes. -1. When the installation has completed, select **Finish**. +1. When the installation is complete, select **Finish**. Successful installation of Replication Server results in the creation of directory structures and files in your host environment as described in [Installation details](installation_details). Verify that the path to your Java runtime program set in `XDB_HOME\etc\edb-repl.conf` is correct. -