Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
{panel} {toc} {panel} h1. Introduction Universal Agent
Wiki Markup
Panel
Table of Contents

Introduction

Universal Agent 6.3.x

...

consists

...

of

...

a

...

family

...

of

...

components

...

that

...

address

...

distributed

...

systems

...

management

...

and

...

automation.

...

The

...

components

...

are

...

packaged

...

together

...

as

...

product

...

installation

...

packages.

...

Product

...

installation

...

packages

...

are

...

provided

...

for

...

a

...

variety

...

of

...

operating

...

systems

...

and

...

hardware.

...

Stonebranch

...

provides

...

product

...

maintenance

...

in

...

the

...

form

...

of

...

updated

...

product

...

installation

...

packages

...

that

...

contained

...

the

...

latest

...

maintenance

...

levels

...

of

...

product

...

components.

...

These

...

pages

...

list

...

the

...

product

...

installation

...

package

...

and

...

component

...

maintenance

...

history

...

for

...

Universal

...

Agent

...

6.3.x.

...

Product Packaging

Agent components are bundled together into product installation packages, referred to simply as packages in this document. Each package is identified with a package version number and each component within a package is identified with a component version number.

Each package and component maintenance level is identified with a version number (see Versioning, below). The component maintenance level is incremented whenever a new component is made available that contains defect fixes or feature enhancements. A package maintenance level is incremented when a product component within the package changes or the package installation changes.

Package maintenance levels are not necessarily made available for all platforms. Package maintenance may be released for a subset of supported platforms. For example, Universal Agent 6.3.0 for z/OS and UNIX may be at maintenance level 6.3.0.1,

...

but

...

Universal

...

Agent

...

6.3.0

...

for

...

Windows

...

may

...

be

...

at

...

6.3.0.0.

...

Stonebranch

...

changes

...

product

...

version,

...

release,

...

or

...

modification

...

identifiers

...

at

...

its

...

discretion

...

when

...

it

...

deems

...

an

...

appropriate

...

number

...

of

...

enhancements

...

or

...

capabilities

...

have

...

been

...

introduced

...

to

...

warrant

...

the

...

change.

...

Versioning

Package version numbers are comprised of four numeric identifiers: version, release, modification level, and maintenance level.

For example, for Universal Agent 6.3.0.1:

...

  • 6

...

  • =

...

  • Version

...

  • 6

...

  • 3

...

  • =

...

  • Release

...

  • 3

...

  • 0

...

  • =

...

  • Modification

...

  • Level

...

  • 0

...

  • 1

...

  • =

...

  • Maintenance

...

  • Level

...

  • 1

...

Product

...

component

...

version

...

numbers

...

are

...

similar

...

to

...

the

...

package

...

version

...

numbers.

...

Each

...

product

...

component

...

within

...

the

...

package

...

is

...

identified

...

with

...

the

...

same

...

version,

...

release,

...

and

...

modification

...

level

...

as

...

the

...

package,

...

and

...

with

...

a

...

maintenance

...

level

...

that

...

is

...

independent

...

of

...

the

...

maintenance

...

level

...

of

...

the

...

package

...

or

...

other

...

components

...

in

...

the

...

package.

...

For

...

example,

...

within

...

a

...

Universal

...

Agent

...

6.3.0.1

...

package,

...

there

...

could

...

be

...

a

...

Universal

...

Command

...

6.3.0.0

...

component:

...

  • 6

...

  • =

...

  • Version

...

  • 6

...

  • 3

...

  • =

...

  • Release

...

  • 3

...

  • 0

...

  • =

...

  • Modification

...

  • Level

...

  • 0

...

  • 0

...

  • =

...

  • Maintenance

...

  • Level

...

  • 0

Packaging Methods

Packaging methods vary among platforms based on the installation conventions and vendor recommendations for the platform. The purpose of this section is to describe the packaging and distribution methods used for the Workload Automation package on its supported platforms.
 

z/OS

The Universal Agent 6.3.0

...

package

...

is

...

an

...

SMP/E

...

install

...

consisting

...

of

...

multiple

...

FMIDs.

...

The

...

package

...

is

...

composed

...

of

...

a

...

set

...

of

...

FMIDs

...

for

...

MVS

...

components

...

and

...

a

...

set

...

of

...

FMIDs

...

for

...

UNIX

...

System

...

Services

...

(USS)

...

components.

...

The

...

MVS

...

components

...

are

...

required

...

and

...

the

...

USS

...

components

...

are

...

optional.

...


 
Maintenance is packaged as a cumulative PTF file containing all available product PTFs for all products within the Workload Automation package.

Windows

All packages are created with the InstallShield Windows packaging tool. The package is installed with Microsoft’s Windows Installer (file extension .msi).
 
Product maintenance is packaged as an updated Windows Installer installation package. The installation process upgrades the current install to the latest product maintenance level.

UNIX

There are two installation methods supported on UNIX platforms, both of which are initiated from a Stonebranch script:

Wiki Markup
{html}<ul>
<li> A system installation uses the UNIX package management system to install the product in vendor-recommended installation directories.
<li> A user mode installation method is performed outside of the UNIX package management system. It allows installation of the product in user-selected directories, and supports multiple installs of differing versions or the same versions of the product.
</ul>
Product maintenance is packaged as an updated installation package. The installation process upgrades the current installation to the latest product maintenance level. <br><br>
UNIX vendor system installation formats are as follows:
<ul>
<li> AIX is packaged in a backup file format (extension .bff) and installed with the AIX installp command.
<li> Sun Solaris is packaged in a Sun software package format and installed with the Sun pkgadd command.
<li> HP-UX is packaged in a HP depot format and installed with the HP swinstall command.
<li> Linux is packaged in a RPM format and installed with the Linux rpm command.
<li> All other UNIX varieties are packaged as compressed tar files and installed with the Stonebranch UNIX installation scripts.
</ul>{html}

...

IBM i

The package is an IBM i Licensed Program and installed with the IBM i RSTLICPGM command. By default, all product and dependent product identifiers are installed.
 
Maintenance is packaged as a cumulative PTF file containing all available product PTFs.

HP NonStop

On the HP NonStop platform, Universal Command 2.1.1 product is packaged by itself. No other products are included in the distribution file.
 
The package is installed with a Stonebranch OBEY file.
 
Product maintenance is packaged as an updated installation package. The installation process upgrades the current install to the latest product maintenance level.

Package Maintenance Levels

For detailed information on the maintenance levels of platform-specific Universal Agent packages, see:

Component Maintenance Levels

For detailed information on the maintenance levels of individual Universal Agent components, see: