Job Management Partner 1/Software Distribution Client Description and User's Guide

[Contents][Glossary][Index][Back][Next]


1.1.3 Functions of the JP1/Software Distribution system

Table 1-1 shows the overview of functions for the entire JP1/Software Distribution system, and where they are described.

Table 1-1 JP1/Software Distribution system functions

Major classification Minor classification Explanation See:
Remote installation Software registration (packaging) This feature registers the software for distribution to the managing server. Section 2.2
Package management The managing server stores and manages the registered packages. Section 2.3
Package distribution This function distributes the packages from the managing server to the distribution-destination system. In the distribution-destination system, the distributed packages are installed automatically. Occasionally, installation work will be required on the distribution-destination system. Section 2.4
Remote collection Registering attributes of collection files This feature registers the attributes of files to be collected to the managing server. Registration is possible from the distribution-destination system or from the managing server itself. Section 3.2
Executing a file collection job This function collects files to the managing server from the distribution-destination system. Section 3.3
Reuse of collected resources Files collected by the managing server are taken out and used. It is also possible to distribute the files as a package. Section 3.4
Management of the distribution-destination system by the managing server System configuration management Automatically reporting the configuration of the distribution-destination system to the managing server allows the managing server to manage the system configuration. Setting is required both at the managing server and the distribution-destination system. Section 4.2
Inventory management This function gathers information about hard disk information and software installation status in the distribution-destination system from the managing server. Section 4.3
Grouping distribution-destinations It is possible to group the distribution-destination system to ensure smooth operation of distribution and collection of packages. Section 4.4
Transmission of information to the upper-level managing server This feature automatically reports the processing results of package distribution or file collection to the managing server.
The managing server can control the execution status of package distribution or file collection and the package status in the distribution-destination systems. The distribution-destination systems can send the status of the user resources in their machines to the managing server.
Section
4.5
Communication status management for distribution-destination systems This feature monitors the communication status between the local system and the lower-level distribution-destination systems. Section
4.6
Operation status management using related software products By linking with JP1 products, this feature monitors the operation status of JP1/Software Distribution Client.
JP1/IM - Manager can automatically execute processing according to the event reported by JP1/Software Distribution Client.
Section
4.7
Organization of this subsection
(1) Remote installation
(2) Remote collection
(3) Management of the distribution-destination system by the managing server

(1) Remote installation

Remote installation, or centralized distribution of software over a network, is the core function of a JP1/Software Distribution system.

Remote installation involves three steps: resource packaging, package management, and package distribution. Figure 1-1 shows how these functions work.

Figure 1-1 Remote installation

[Figure]

  1. Software packaging
    The packages to be distributed are registered on the managing server from a packager. This is called packaging. Package attribute information, such as distribution method and package storage period, is set at packaging time. Only packages that are registered correctly can be distributed.
  2. Package management
    On the managing server, the actual packages are stored and managed in a package storehouse, and the package attribute information is stored and managed in a package attribute file.
  3. Package distribution
    The packages are distributed to each distribution-destination system under the direction of the managing server. When packages are distributed via a relay system, they are temporarily stored in a file called a temporary package storehouse in the relay system, and then package copies are distributed to the individual managing servers.

(2) Remote collection

Resource files on the destination systems can be collected on the managing server. You can retrieve and reuse the collected files at the managing server, or convert them into packages and send them to the distribution-destination systems. Figure 1-2 shows how these functions work.

Figure 1-2 Remote collection

[Figure]

  1. Registration of collection conditions (collection information)
    Enter collection information such as the file names and collection timings in a collection-information file, and then register the file in the file for collected files' attributes on the managing server.
  2. Instructions for file collection (file collection job)
    The managing server requests file collection, according to the entered conditions.
  3. File collection
    The resource files collected from each system are stored in a file called collection storehouse on the managing server. Files collected via a relay system are stored temporarily in a file called a temporary collection storehouse on the relay system, then all the collected files are forwarded together to the managing server.

(3) Management of the distribution-destination system by the managing server

This function ensures smooth operation of software distribution and collection across the entire JP1/Software Distribution system.

JP1/Software Distribution provides various features to enable the managing server to adequately control the machines that function as distribution-destination systems. Figure 1-3 gives an outline of the features for the managing server to control distribution-destination systems.

Figure 1-3 Managing distribution destinations using the managing server

[Figure]

  1. Managing the system configuration
    The distribution-destination systems automatically report the system configuration to the managing server. The managing server stores the reported information in the system configuration file to manage the system configuration of the distribution-destination systems.
  2. Managing the inventory
    The managing server takes an inventory of the information about the distribution-destination systems such as the hardware status and the types of installed software and manages the inventory. The inventory can be automatically collected when a package is distributed. You can also collect the inventory of the distribution-destination systems by executing a job from the managing server. The collected inventory can be used to manage software licenses and the usage status of machines.
    Some inventory information can be reported to the managing server at the time when the information is updated at the distribution-destination system or when a new distribution-destination system is added.
  3. Grouping distribution-destination systems
    The managing server can create a distribution-destination group and manage some distribution-destination systems as a group. To register a distribution-destination system in a group, you specify the ID group. When distribution-destination systems are grouped, you can distribute software group by group.
  4. Reporting the results of jobs from lower-level systems
    This feature automatically reports whether the distribution job or the file collection job issued from the managing server was executed in the target distribution-destination systems. You can manage the executed jobs based on the processing results reported from the distribution-destination systems.
  5. Displaying the connection status
    This feature outputs the messages indicating the connection status between the managing server and the distribution-destination systems or the execution status of jobs. You can specify the output level of the messages that indicate the distribution results of packages. By displaying the connection status, you can check the status of the distribution-destination systems.
    JP1/Software Distribution Manager displays the connection status.
  6. Displaying the levels of distribution destinations
    This feature displays the number of routes (levels) that are taken between the managing server and the target distribution-destination system. By confirming the level, you can identify the distribution-destination system where an error has occurred. This allows you to perform troubleshooting measures effectively.
    JP1/Software Distribution Manager displays the levels of distribution destinations.
  7. Controlling the communication status between the relay system and the distribution-destination systems
    The managing server checks the communication status between the relay system and the distribution-destination systems. The managing server periodically checks whether there is communication from the distribution-destination systems during a specified length of time. If there is not, the managing server maintains the permitted number of connectable distribution-destination systems. The managing server also checks the startup status of the target distribution-destination systems when the relay system attempts to distribute a package. This way, the managing server can determine the cause of the failed startup.
    The communication status between the relay system and the distribution-destination system is managed by JP1/Software Distribution Manager.

[Contents][Back][Next]


[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.