- Configuring your Web Server for Web Synchronization
- Configuring Your SQL Server Publisher for Web Synchronization
- Configuring Your Publication for Web Synchronization
- Configure Your Local Subscribers for Web Synchronization
- Configure your Remote Subscribers for Web Synchronization
- Summary
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Configure Your Local Subscribers for Web Synchronization
If you can register your subscribers and publisher in SSMS, all you have to do is create a new pull subscription on the subscriber. Connect to the subscriber, expand the Replication folder, right-click on the Local Subscriptions folder, and select New Subscription.
You will see the New Subscription Wizard splash screen. Click Next. In the Publisher drop-down box, select your publisher, expand your publication database, select your publication, and click Next.
If your publisher does not appear here, select the Find SQL Server Publisher in the drop-down box and try to connect to it. If your publisher is not listed, add it via an alias using SQL Server Configuration Manager (you can find this program by clicking Start, pointing to All Programs, Microsoft SQL Server 2005, and Configuration Tools). Expand SQL Server Native Client Configuration and right-click on the alias node to create an new alias to the publisher—use TCP/IP and use the server name of the publisher as the alias name. You can determine the server name of the publisher by issuing a select @@servername on the publisher. For the server, you can enter the IP address. There is a good chance that if your subscriber is separated from the publisher by a different domain or by a highly restrictive firewall, LAN, or WAN, you will need to follow the instructions in the section "Configure Your Remote Subscribers for Web Synchronization."
In the Merge Agent Location dialog box, select Run Each Agent At Its Subscriber (Pull Subscriptions) and click Next. In the Subscribers dialog box, select your subscriber and the database you want the subscription to be pulled to. You have the option to select multiple subscribers here, each with a different subscription database. Click Next.
In the Merge Agent security dialog box you can select the accounts that will be used to connect to the publisher and subscriber. There are two enabled options:
- Specify The Domain Or Machine Account Under Which The Merge Agent Process Will Run When Synchronizing This Subscription
- Connect To The Subscriber
The first option (the publisher account) must be in the PAL, have security to read and list folder contents on the snapshot share, and be in the db_owner in the distribution database.
It is the account that is used to connect and authenticate to the web server and then connect to the database and synchronize. This should be a publisher domain or local machine account and entered in the dialog box as DomainName\AccountName.
The subscriber account should also be a subscriber domain or local machine account that is in the db_owner in the subscription database.
Click on Next. For the Synchronization Schedule, select a schedule. Click Next. In the Initialize Subscription dialog box, select Initialize Immediately. Click Next. In the Web Synchronization dialog box, select Use Web Synchronization (see Figure 3).
)
Figure 3 Enabling your subscription for Web synchronization
Click Next. In the for the Subscription Type dialog box, select Client in the Subscription Type drop-down box.
In the Wizard Actions dialog box, accept the defaults and click Next. Review the options selected in the Complete The Wizard dialog box and click Finish to implement them. Your subscription will be built.