Topic Last Modified: 2010-07-19
After you define your topology in Topology Builder, you must publish the topology to the Central Management database. The Central Management database provides a robust, schematized storage of the data needed to define, set up, maintain, administer, describe, and operate a Communications Server deployment. It also validates the data to ensure configuration consistency. All changes to this configuration data happen at the Central Management database, eliminating “out-of-sync” problems. Read-only copies of the data are replicated to all servers in the topology, including Edge Servers.
|In order to publish the topology, the SQL Server back-end server must be online and accessible with firewall exceptions in place. For details about specifying firewall exceptions, see the Configure Firewall Exceptions section. For more details about configuring SQL Server, see Configure SQL Server for Communications Server 2010.|
To publish a topology
From the Communications Server 2010 (Beta Refresh) program group, open Communications Server Topology Builder.
Choose the option to open the topology from a local file. For details, see Import the Topology Definition to the First Front End Server.
Right-click the Communications Server 2010 (Beta Refresh) node, and then click Publish Topology.
On the Publish the topology page, click Next.
On the Create databases page, select the databases you want to publish, and then click Next.
Note: If you don’t have the appropriate permissions to create the databases, you can uncheck the databases and someone with appropriate permissions can create the database later.
On the Select Central Management Server page, select a Front End pool, and then click Next.
When the publish process has completed, click Finish.
Now that the topology has been published successfully, you can begin installing a local replica of the Central Management database on each server role in your topology. For details, see Setting Up Front End Servers and the Enterprise Pool.