Inventory Server Configurations

The following sections will help you configure your ZfD servers:

IMPORTANT:  The recommendations discussed in the scenarios are generic because of the unique nature of the topology; further refinements may become necessary.


Deploying Inventory in a LAN Environment

In ZfD, the deployment of inventory in a LAN environment implies deploying the product on a single inventory site.

The following scenarios and recommendations are addressed:


Scenario 1: LAN Environment with up to 5,000 Workstations

In this type of inventory configuration, the inventory server components and database are located on a Standalone Server. The Standalone Server is an inventory server with an Inventory database. There is no roll-up of data and the Sender-Receiver components are not used. This scenario is illustrated in the following figure.


A Standalone Server that has workstations attached to it and an Inventory database connected to it


Scenario 2: LAN Environment with more than 5,000 Workstations

In this type of configuration, there are multiple inventory servers without databases. These inventory servers (two Standalone Servers) are connected to a database server. The Database Location policy configures the database server for the Standalone Servers. This inventory deployment is illustrated in the following figure.


Two Standalone Servers connected to a database server

Follow this configuration for deploying inventory up to 10,000 workstations.

For deploying inventory on more than 10,000 workstations, attach one inventory server per 5,000 workstations, with two or three inventory servers per Inventory database.


Recommendations for Deployment in a LAN Environment


Deploying Inventory over a WAN Environment

In a WAN environment, complete the following tasks, in order, to design the inventory tree and deploy inventory:

Guidelines for Creating Policies in a WAN covers recommendations for deployment.


1. List the sites in the enterprise

Describe the entire network of your company.

The following figure illustrates the network organization of a company with servers in different locations.

This illustration depicts four sites (Site A, Site, B, Site C, and Site D) connected to a central site. It depicts the physical links between the sites and the type of links in terms of bandwidth.


Typical characteristics of each site include 1000 workstations per site, two NetWare servers per site, and five Windows NT servers per site. Site B, Site C, and Site D connect to the main site with a WAN connection of 2 MB. The WAN connection between the main site and Site A is 65 KB.


2. Which is the ideal place for the Root Server?

The Root Server in the Inventory Tree is the highest-level server. Necessarily, an Inventory database is attached to the Root Server.

The inventory information available from the Inventory database of the Root Server will consist of all information from lower-level sites on the network and from the Root Server site.

Factors that you must include:


3. Is any other database needed?

Besides the database at the Root Server, you can maintain database servers at different sites.

You may want to maintain additional databases if there are sites or subtrees that are managed for inventory at different locations, and these sites are connected to the network over a slow link.

You should also determine if there are specific reasons to have a separate database for a single site or a set of sites. There may be some organizational needs for your company to have the database server on different sites, even if there is no product deployment need to have any other database.

NOTE:  For a majority of enterprises, there may be no need to have any other database besides the enterprise-wide single database. All site-specific reports can be easily generated from this database.


Optional step: If another database is needed


4. Identify the route for Inventory data

Identify the routes for inventory data for all sites to the nearest database, and then identify the route to the database on the Root Server.

To devise a route plan:


5. Identify servers on each site for Inventory, Intermediate and Database Servers

A single server can have different roles if it has sufficient resources. For example, an inventory server can be a Leaf Server with Database. You can also designate a server as an Intermediate Server with Database, which receives inventory from the workstations and also has an Inventory database. A server can have any combination of roles.

In ZfD, you choose the role for each server. See Implementing the Inventory Server Roles for more information.

The number of workstations attached to the server also determines the load. The following table lists the disk space requirements for the server:

Server Type Disk Space Requirements

Leaf Server

(n1 x s) + (n1 x z)

Leaf Server with Database

(n1 x s x 2) + {(n1 x dbg)}

Intermediate Server

n2 x z

Intermediate Server with Database

(n2 x z) + (n2 x s) + {(n2 x dbg)}

Intermediate Server with Workstations

(n1 x s x 2) + (n2 x z)

Intermediate Server with Database and Workstations

(n1 x s x 2) + (n2 x z) + (n2 x s) + {(n1 x dbg) + (n2 x dbg)}

Root Server

(n2 x z) + (n2 x s) + {(n2 x dbg)}

Root Server with Workstations

(n1 x s x 2) + (n2 x z) + (n2 x s) + {(n1 x dbg) + (n2 x dbg)}

Standalone Server

(n1 x s x 1) + {(n1 x dbg)}

In the table, n1 is the number of workstations attached to the server.

s is the size of the scan data files. This file size varies depending on the data collected. Calculate 50 to 60 KB scan data from each workstation to calculate the load.

dbg is the storage space of the scan data in the database. Calculate 100 to 120 KB per workstation as the disk space for the database.

n2 is the number of workstations rolled up to the server.

z is the size of the compressed scan data file per workstation. Calculate 7 to 10 KB for the roll-up of 50 KB scan data.

{ } denotes the disk space of the database server, depending on whether the database is on the same server or if it is connected to the server. If the database is on the same server, calculate the total disk space including the database space for the server. For example, if the Leaf Server with Database has the Inventory database on the same server, calculate the requirements for storage of scan data, including the database disk space.


6. Create the tree of servers for company Inventory collection

Ensure that the Inventory tree you design follow these guidelines:


7. Create an implementation plan

After you design the tree, you should develop an implementation plan to cover the phased deployment plan for the network.

Some guidelines for the implementation plan:


8. Start the actual deployment

After your implementation plan is finalized, start the actual deployment according to the plan.

Follow these steps:

  1. Install the servers on the sites.
  2. Create the policies applicable to workstations.
  3. Create the Roll-Up policies to schedule the roll-up for each server.

Adding a Database server to an existing Inventory setup

If you have already configured the servers for inventory setup, and you need to add another database server, follow these instructions:

  1. Run the installation program to install the Inventory database on the server.

    The installation program installs the Sybase database. If you are maintaining the database in Oracle, make sure that the Oracle database exists. See Configuring the Inventory Database for Oracle.

  2. Shut down the Inventory Services.

  3. Based on the database you select, make sure that you configure the database. See Configure the Policies for the Database.

  4. Modify the role of the existing server for the Inventory Service object.

    If you are adding a new server, you need not modify the role of the server. If you want to change the role of the server, for example, from Leaf Server to Leaf Server with Database, you need to modify the role of the server in the Inventory Service object.

    1. In ConsoleOne, right-click the Inventory Service object (Servername_ZenInvservice) > click Properties > click the Inventory Service object Properties tab.

      1. Choose the new role of the Inventory Service object > click Apply.

      You will see a list of actions that you should follow based on the chosen role. For example, if you change the Root Server to Root Server with Workstations, you need to configure the Workstation Inventory policy for the workstations that you have attached. Similarly, to change the role to any other server, you need to follow the instructions to make the role change effective.

      Follow the actions that you need to change the role.

  5. Make sure that you enforce Full Scan for the Inventory Service object.

    1. In ConsoleOne, right-click the Inventory Service object (servername_ZenInvservice) > click Properties > click the Inventory Service object Properties tab.

    2. Check the Enforce Full Scan option > click OK.

  6. Bring up the Inventory service.


Possible Inventory Server Configurations for a WAN

The following sections cover these scenarios:


Scenario 1: WAN Inventory Deployment for up to 50 Inventory Sites without Intermediate Servers

All inventory servers are connected to a central enterprise database server. The Leaf Servers do not have a database and Intermediate Servers are not required. This scenario is illustrated in the following figure:


Several Leaf Servers connected to a central Root Server


Scenario 2: Up to 50 Intermediate Servers Connected to the Root Server

In this configuration, the Leaf Servers roll up data to the next-level Intermediate Server and finally to the Root Server. Another server at a different location is also connected to the Root Server. This scenario is illustrated in the following figure:


This illustration depicts two Leaf Servers that roll up to the Intermediate Server. The Intermediate Server rolls up data to the Root Server. Another Leaf Server from the same site directly rolls up data to the Root Server. Another Leaf Server in a different geographical location rolls up data to the Root Server.


Scenario 3: Intermediate Servers with Database Connected to the Root Server

In this configuration, the inventory servers are connected to the Intermediate Server over fast WAN links. The Intermediate Server also has an Inventory database and transmits the information to the Root Server. Other servers are also connected to the Root Server. This scenario is illustrated in the following figure:


This illustration depicts two Leaf Servers that connect to the Intermediate Server with Database over fast links. The Intermediate Server with Database connects to the Root Server over a slow WAN link. Another Leaf Server is in a different geographical location connects directly to the Root Server over a slow link. A group of workstations connects directly to the Root Server over the LAN.


Scenario 4: Database on Inventory Servers and Intermediate Servers Connected to a Root Server

In this configuration, there are branch offices and a main office. Both branch offices store inventory information.

At one branch office, the server is a Leaf Server with Inventory Database, and the other branch office has a Leaf Server. At the next level, there is another branch office with an Intermediate Server with Database. The two branch offices at the lower level roll up data to this Intermediate Server. In turn, this Intermediate Server with Database rolls up data to the main office at the next level. There is also another sales outlet with a Leaf Server with Database at a sales outlet. This server directly rolls up data to the main office. The sales outlet and the two branch offices connect to the main office over low-speed WAN. One branch office connects to the main site over high-speed WAN. This scenario is illustrated in the following figure:


Two branch offices with Leaf Servers, a branch office with an Intermediate Server with Database at the next level, and a sales outlet that directly rolls up data to the main office


Guidelines for Creating Policies in a WAN

In this type of inventory deployment, the scanners transmit information to the servers over a WAN or dial-up connection.



  Previous Page: Overview of Inventory Components  Next Page: Implementing the Inventory Server Roles