Job Management Partner 1/Software Distribution Description and Planning Guide

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

Appendix D.2 Differences with JP1/Software Distribution for UNIX

The following describes the differences between the Windows and Unix versions of JP1/Software Distribution. These tables show the operations that the Windows and UNIX managing servers support for the clients.

Table D-1 Remote installation (software distribution)

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Managing server-based installation S S S S
Client user installation S S S S
Distribution of JP1/Software Distribution Client (client) S S S S
Distribution of JP1/Software Distribution Client (relay system) S S S S
Suppressing installation by system conditions S -- S --
Suppressing installation by software conditions S -- S --
Distribution schedule S S S S
Specifying installation date and time S S S S
Specifying installation timing S#1 S#2 S#1 S#2
Auto-booting of client machine after installation S S S S
Displaying dialogs during processing (setting packages) S -- -- --
Displaying processing message (client setup) S -- S --
Starting an external program in linkage to remote installation S
(Before and after distribution, error)
S
(Before and after distribution)
S
(Before and after distribution, error)
S
(Before and after distribution)
Automated installation of a package S S S S
Installation using a recorder file S -- S --
Installation using an AIT file S -- S --
Installation specifying a host group S S S S
Installation specifying an ID group S S S#3 S#3
Split distribution S S#4 S S
Multicast distribution S -- -- --
Suspending and resuming a job S S -- S
Distributing suspended jobs S S -- --
Remote booting and shutdown by client control S#5 S#6 -- --
Offline installation S -- -- --
Acquiring directory information S -- -- --

Legend:
S: supported
--: Not supported

#1
Installation at system startup or normal installation

#2
Installation at system startup, normal installation, or installation at system shutdown

#3
Information on the distribution destinations that are registered in the group ID for the UNIX version of JP1/Software Distribution is managed by the relay system. Therefore, distribution destination systems that are directly connected to the managing server cannot be registered in a group ID.

#4
Split distribution is supported only when the client is an end workstation.

#5
Remote startup via a relay system, by client control, can be used regardless of whether the relay system is a UNIX or a Windows based system.

#6
You can use only remote startup if the client version is 08-10 or later. You can use this operation over a relay system regardless of whether the relay system is UNIX or Windows.

Table D-2 Packaging

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Compression of package data S S S S
Copying packages between managing servers -- -- S S

Legend:
S: supported
--: Not supported

Table D-3 Inventory management

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Acquiring an inventory periodically S S -- --
Specifying acquisition timing S#1 S#2 -- --
Automatic reporting of updated inventory information S S#3 -- --
Managing system information S S S S
Managing registry information S -- -- --
Managing software information S S S S
Managing user inventory information S S S S
Acquiring other companies' software information S S -- --
Acquiring software information by a software search list S S -- --
Searching for a file S -- -- --
Acquiring software information with Search for Microsoft Office products specified. S -- -- --
Acquiring software information with Search for anti-virus products specified. S S#4 -- --
Acquiring patch information S S S --
Managing software licenses S -- -- --
Managing software generations S S S S
Managing offline machines S -- -- --
Output of management information to a CSV file S S S#5 S#5

Legend:
S: supported
--: Not supported

#1
Execution at system startup or during system operation

#2
Execution at system startup, during system operation, or at system termination

#3
Available only if the client version is 09-00 or later.

#4
Can be acquired only if the client's OS is Linux version 07-50 or later.

#5
JP1/Software Distribution Web - Console is required.

Table D-4 Remote collection (collecting files)

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Remote collection S S S S
Collection path name#1 S S S S
Specifying a collection timing S#2 S#2 S#2 S#3
Starting an external program in linkage with remote collection S S
(Before and after collection)
S S
(Before and after collection)
Suspending and resuming a job (batch collection) -- -- -- S
Remote activation and shutdown by client control S#4 S#5 -- --
Compressing a collected file S S S S
Distributing collected inventories -- -- S S

Legend:
S: supported
--: Not supported

#1
The maximum number of characters that can be specified for a collection path name is as follows:
[Figure] Windows client: 256 single-byte characters
[Figure] UNIX client: 63 single-byte characters

#2
At client startup or during client operations

#3
At client startup, during client operations, or at client shutdown

#4
Remote startup via a relay system, by client control, can be used regardless of whether the relay system is UNIX or Windows.

#5
You can use only remote startup if the client version is 08-10 or later. You can use this operation over a relay system regardless of whether the relay system is UNIX or Windows.

Table D-5 Software operation status monitoring

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Monitoring of software operation status S# -- -- --
Management of operating information with Asset Information Manager Subset S -- -- --

Legend:
S: supported
--: Not supported

#
If a relay system is used, this function is available whether the relay system is UNIX or Windows. However, the version must be 07-50 or later.

Table D-6 Remote control

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Client remote control S -- -- --
File transfer using the remote control facility S -- -- --

Legend:
S: supported
--: Not supported

Table D-7 Linkage facility

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
JP1/Base linkage S -- -- --
JP1/AJS2 - SO linkage -- -- S S
OpenView Linkage S S -- --
JP1/IM event linkage S S S S

Legend:
S: supported
--: Not supported

Table D-8 System configuration

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Hierarchical implementation of managing servers S S -- --
Multi Software Distribution facility -- -- -- S#1
Relational database capability S (Embedded RDB, Microsoft SQL Server, Oracle) S (Embedded RDB, Microsoft SQL Server, Oracle) S (HiRDB, Oracle) S (HiRDB, Oracle)
Operation under a cluster system#2 S S S S
Multiple LAN connection capability S S S S
Multiple higher systems capability S S S S
Auto dialing S -- S --
Priority settings for IP addresses that are to be reported to the higher system S S S S

Legend:
S: supported
--: Not supported

#1
Requires a relational database as a management file.

#2
JP1/Software Distribution Manager can be clustered.

Table D-9 System configuration information management

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Auto generation of system configuration information S S S S
Managing system configuration information deletion history S S -- --
ID linkage to system configuration information S S -- --
Management based on host IDs S S -- --
Host search function S S -- --
Detection of hosts on which JP1/Software Distribution is not installed S S -- --

Legend:
S: supported
--: Not supported

Table D-10 Client management

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Obtaining a patch S -- -- --
Detecting patch information S#1 -- -- --
Managing security updates with WSUS linkage S -- -- --
Reporting alerts to higher systems S -- -- --
Message transmission to client S#2 S#3 -- --
Client control using AMT S -- -- --

Legend:
S: supported
--: Not supported

#1
If a relay system is used, this function is available whether the relay system is UNIX or Windows.

#2
If a relay system is used, this function is available whether the relay system is UNIX or Windows. However, the version must be 07-50 or later.

#3
A text message can be sent alone if the client OS is Linux and the JP1/Software Distribution version is 09-00 or later.

Table D-11 Client facilities

Item Windows managing server UNIX managing server
Windows
client
UNIX
client
Windows
client
UNIX
client
Nonresident client S S S S
Job hold and cancellation S -- S --
Local System Viewer and system monitoring S# -- S# --

Legend:
S: supported
--: Not supported

#
Because these functions are used locally on the client, they are not available for operation from a higher system.