How to configure constrained and unconstrained Package Server in a site hierarchy


Article ID: 180919


Updated On:


Management Platform (Formerly known as Notification Server)




Notification Server 6.0 SP3 introduces the possibility to configure constrained Package Server (abbreviated to cPS) and unconstrained package servers (uPS).

This ensures that Package Servers behind a slow link do not all download from the Notification Server; instead, one Package Server is set to be a uPS and all other are made cPS. In this way only one set of files will downloaded through the WAN link.

Now that we understand the theory, how would this be applied to a deep hierarchy, with a Notification Server in the company Global Head Quarter, country Offices and country Branch Offices? How should the site and subnet configuration be done in this case?

To describe the precise configuration steps required to configure the uPS and cPS in such an environment we will use an text case, detailed in the diagram here:

As you can see the country is managed from the Global Head Quarter. We have placed one unconstrained Package Server (uPS) on the country Head Quarter and one cPS per branch office. Each of these sites can have one or more subnets.

We will start by configuring the Notification Server; the site and subnet on the Site Maintenance page (Configuration > Server Settings > Notification Server Infrastructure > Site Maintenance).

As you can see, we have create the C01-HQ site with its and subnets, C01-BR01, C01-BR02 and C01-BR03 (not represented in the site diagram in 'Question' for clarity) also with their defined subnets.

We can now select the Subnets tab in the Site Maintenance page to verify that the subnets are configured properly:

You can see the sites and subnets we have defined as well as other subnets (of no interest to this particular case).

Let's go to the final tab now to look at the Package Server and do the manual server to site assignments (new feature in Notification Server 6.0 SP3). Note: The mapping is done automatically based on site, subnet, and Package Server IP Addresses, but we'll do a manual assignment for all elements in this example.

We only have two package servers available at this point in time, but they happen to be the one from the country Head Quarter (C01-HQ-uPS) and one from the country Branch Offices (C01-BR01-cPS). We have checked the Constrained check box for C01-BR01-cPS to make it a constrained Package Server.

Next we configure the site assignments for C01-HQ-uPS. Since this uPS will be the only Package Server downloading from the Notification Server, it will be in each of the country sites. Note: The red lines were added to show that the Select a Site Webpage dialog pops-up once you have selected the desired Package Server (highlighted in pale yellow) and clicked on the Assign to site button (shown in the red box).

Select OK. The site maintenance page, Package Server tab now shows that C01-HQ-uPS is assigned to four sites (as planned).

Now that we have selected all the sites for which our uPS will be delivering packages, we can configure each Branch Office constrained Package Servers individually. In this article we'll only configure C01-BR01-cPS as it would be the same for all other cPS in this country.

Here is the resulting view on the Package Servers tab:

Now that we have done it for the country uPS and one of the cPS, we can check back on the Sites tab to ensure that our C01-BR01 site as both a uPS (where the packages will be downloaded from the Notification Server) and a cPS (where the packages will be downloaded from the clients in the C01-BR01 site):