Tivoli Software Distribution Database Configuration

Tivoli®

Software DistributionDatabase ConfigurationVersion 4.1

Tivoli®

Software DistributionDatabase ConfigurationVersion 4.1

Tivoli Software Distribution Database Configuration, Version 4.1

Copyright Notice

© Copyright IBM Corporation 2001. All rights reserved. May only be used pursuant to a Tivoli Systems Software LicenseAgreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. Nopart of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without priorwritten permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions ofany machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporationcopyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document isnot intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed, including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBMCorporation.

Trademarks

IBM, DB2, Tivoli, and the Tivoli logo are trademarks or registered trademarks of International Business Machines Corporation orTivoli Systems Inc. in the United States, other countries, or both.

Windows, is trademark of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, orboth.

Other company, product, and service names may be trademarks or service marks of others.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available inall countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended toimply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or otherlegally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, exceptthose expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents orpending patent applications covering subject matter in this document. The furnishing of this document does not give you any licenseto these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,Armonk, New York 10504-1785, U.S.A.

ISO 9001 Certification

This product was developed using an ISO 9001 certified quality system.

Certification has been awarded by Bureau Veritas Quality International (BVQI) (Certification No. BVQI - 92086/A).

BVQI is a world leader in quality certification and is currently recognized by more than 20 accreditation bodies.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vTable Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Who Should Read This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Prerequisite and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

What This Guide Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. Activity Planner Database Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Definition Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Status Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Miscellaneous Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

ACTIVITY_PLAN Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

PLAN_TARGET Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

PLAN_TARGET_SPEC Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

VARIABLE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

ACTIVITY Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

ACT_LAYOUT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

ACT_TARGET_SPEC Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

ACTIVITY_TARGET Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

ACT_PARAMETER Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

EXECUTION_WINDOW Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

ACT_PLAN_STATUS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

ACTIVITY_STATUS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

ACT_STATUS_TGT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

APPL_OPERATION Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

APPL_ERRLEV Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

PLAN_LOCKS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 2. Change Configuration Manager Database Tables . . . . . . . . . . . . 21REFERENCE MODEL Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

ELEMENT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

iiiTivoli Software Distribution Database Configuration

DEPENDENCY Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

SUBSCRIBER Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

CCM_REPORT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 3. Web User Interface Database Tables. . . . . . . . . . . . . . . . . . . . . . . . . . 27SWP_SUBSCRIPTIONS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

MOD_SUBSCRIPTIONS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iv Version 4.1

Preface

Tivoli® Software Distribution Database Configuration provides details of all database tablesmaintained by Tivoli Software Distribution. The tables are separately maintained by threecomponents:

¶ Activity Planner (AP)

¶ Change Configuration Manager (CCM)

¶ Web User Interface (Web UI)

This manual is divided into separate chapters for each component. Each table has its ownsection, which commences with an explanation of the relationships that the table has withother Tivoli Software Distribution tables, and provides full details of the database fields,including the meaning of the values used. The information, although provided in a standardformat as used in any of the database management programs supported by Tivoli SoftwareDistribution, is prepared from tables maintained using the IBM® DATABASE2 (DB2®);users of other supported programs may notice minor differences in the presentation of theinformation.

Summary information about the tables is also provided in a schema, which is available as aseparate file. It shows graphically the table relationships and the contents of each table. It ismade available in conjunction with this document, in PDF format.

Table LegendThe columns in each database table are described in tabular format; the legend of thesedescriptive tables is as follows:

Name The name of the database column.

Type Industry standard column format description.

Key This can have one of the following values:

PK The column forms part or all of the primary key.

FK The column forms part or all of a foreign key for referential integrity withother tables.

Blank The column is not a key.

Null Whether the database column can accept a null value; the possible values are asfollows:

N Null is not allowed.

Y Null is allowed.

DescriptionThe description of the data stored in the column, and the possible values.

Who Should Read This DocumentThis document is intended for database administrators, or others, who need to understandhow Tivoli Software Distribution uses the tables that it maintains.

vTivoli Software Distribution Database Configuration

Prerequisite and Related DocumentsTo use the information in this guide, you should be familiar with the following manuals:

¶ Tivoli Software Distribution User’s Guide

Provides concepts and procedures for daily software package operations.

¶ Tivoli Software Distribution Reference Manual

Provides detailed information about managing and distributing software from thecommand line interface (CLI), including information about editing software packagedefinition files.

¶ Tivoli Software Distribution Release Notes

Provides prerequisite, troubleshooting and late-breaking information about the product,as well as listing details of fixed and open defects in the product and its documentation.

What This Guide ContainsTivoli Software Distribution Database Tables contains the following sections:

¶ “Activity Planner Database Tables” on page 1

¶ “Change Configuration Manager Database Tables” on page 21

¶ “Web User Interface Database Tables” on page 27

Conventions Used in This GuideThe guide uses several typeface conventions for special terms and actions. Theseconventions have the following meaning:

Bold Lowercase or mixed-case commands, command options in a syntaxstatement, the names of objects in procedures that you type, select, click, orpress, or any other information that you must use literally appear like this,in bold.

Italics Variables, new terms, and words and phrases that are emphasized appear likethis, in italics.

Monospace Code examples, output, and system messages appear like this, in amonospace font.

References in this guide to other documents, in the Tivoli Software Distribution library orother libraries, do not carry version numbers, unless a specific down-level version isreferenced. The latest version is assumed in all such references.

Accessing Publications OnlineThe Tivoli Customer Support Web site (http://www.tivoli.com/support/) offers a guide tosupport services (the Customer Support Handbook); frequently asked questions (FAQs); andtechnical information, including release notes, user’s guides, redbooks, and white papers.You can access Tivoli publications online at http://www.tivoli.com/support/documents/.The documentation for some products is available in PDF and HTML formats. Translateddocuments are also available for some products.

To access most of the documentation, you need an ID and a password. To obtain an ID foruse on the support Web site, go to http://www.tivoli.com/support/getting/.

Preface

vi Version 4.1

Resellers should refer to http://www.tivoli.com/support/smb/index.html for moreinformation about obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” for more information aboutobtaining Tivoli technical documentation.

Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html or by calling one of thefollowing telephone numbers:

¶ U.S. customers: (800) 879-2755

¶ Canadian customers: (800) 426-4968

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you have commentsor suggestions about our products and documentation, contact us in one of the followingways:

¶ Send e-mail to [email protected].

¶ Fill out our customer feedback survey at http://www.tivoli.com/support/survey/.

Contacting Customer SupportThe Tivoli Customer Support Handbook at http://www.tivoli.com/support/handbook/provides information about all aspects of Tivoli Customer Support, including the following:

¶ Registration and eligibility.

¶ How to contact support, depending on the severity of your problem.

¶ Telephone numbers and e-mail addresses, depending on the country you are in.

¶ What information you should gather before contacting support.

Preface

viiTivoli Software Distribution Database Configuration

Preface

viii Version 4.1

Activity Planner Database Tables

The tables and views that collectively constitute the Activity Planner (AP) database can begrouped in the following three sets:¶ Definition Tables¶ Status Tables¶ Miscellaneous Tables

See “Table Legend” on page v for a detailed explanation of the table legend.

Definition TablesThese tables contain the definition of the activity plans. Plans that are edited with the APEditor GUI or imported from an XML plan definition file are stored in these tables in theform of a ‘draft’ or ‘template’ activity plan. When the administrator submits a plan from apreviously defined template the data in the activity plan template are duplicated and theadministrator is allowed to override many of the plan parameters that have been previouslyspecified in the template. The tables are as follows:¶ ACTIVITY_PLAN¶ PLAN_TARGET¶ PLAN_TARGET_SPEC¶ VARIABLE¶ ACTIVITY¶ ACT_LAYOUT¶ ACT_TARGET_SPEC¶ ACTIVITY_TARGET¶ ACT_PARAMETER¶ EXECUTION_WINDOW

Status TablesThese tables store information about the status of the execution of submitted plans. Thestatus information is retained until the administrator decides to purge it using the wdelstatcommand or the automatic purging facility provided by the wsfdpln command. These tablesare more likely to vary in size than the other Activity Planner tables, because new recordsare created for each target addressed by each activity of a given plan when the plan issubmitted for execution, or when a new recursion of a recursive plan is started. Theadministrator should periodically remove status information that it is no longer needed toprevent the AP database size from growing indefinitely; commands and GUI options areprovided to facilitate this cleanup operation. The tables are as follows:¶ ACT_PLAN_STATUS¶ ACTIVITY_STATUS¶ ACT_STATUS_TGT

1

1Tivoli Software Distribution Database Configuration

1.A

ctivityP

lann

erD

atabase

Tables

Miscellaneous TablesThe following tables are also maintained by the Activity Planner:¶ APPL_OPERATION¶ APPL_ERRLEV¶ PLAN_LOCKS

Status Tables

2 Version 4.1

ACTIVITY_PLAN TableThis table contains information about an activity plan that is currently being edited (“draft”)or has been saved as template or is currently running. Every time a new plan is submittedfrom a template, a new row is created in the table, meaning that for every plan there are atleast two rows: a template row and a submitted row. Entries for submitted plans are deletedby the wdelstat and the wsfdpln commands or through the AP monitor GUI. Entries fortemplate and draft plans are deleted through the AP editor GUI or by the wdelpln command.When a plan is deleted from the database all the related entries in the child tables aredeleted from the database, including the status information.

Table 1. The ACTIVITY_PLAN TableName Type Key Null Description

PLAN_ID VARCHAR(80) PK N The numeric plan ID generated by the system

IS_TEMPLATE CHAR(1) N Type of plan. Possible values are:E DraftT TemplateS Submitted

IS_PAUSED CHAR(1) N Whether the plan is to be set to the paused statewhen submitted. Possible values are:T True -set to paused stateF False

PRIORITY INTEGER N Controls the order in which activities are run within agiven execution window.

NAME VARCHAR(128) N Used to identify activity plans saved as drafts ortemplates in the activity plan database.

STOP_ON_ERROR INTEGER N The error level above which the plan execution willbe stopped.

IS_CANC_CUTOFF CHAR(1) N Whether the outstanding activities must be canceledat cutoff. Possible values are:T True - canceled at cutoffF False

IS_POST_NOTICE CHAR(1) N Whether a notice must be posted to notify plansubmission and completion. Possible values are:T True - post a noticeF False

DESCRIPTION VARCHAR(251) Y Description of the activity plan.

REC_STOP_ON_ERROR INTEGER Y The error level above which the nth iteration of arecursive plan will be stopped

REC_STOP_OVERLAP CHAR(1) Y Whether the nth iteration of a recursive plan will bestopped if its execution overlaps with the nextiteration. Possible values are:T True - stop on overlapF False

REC_EXPIRE_TIME TIMESTAMP Y The date and time at which the recursion mechanismwill expire

ACTIVITY_PLAN Table


1.A

ctivityP

lann

erD

atabase

Tables

Table 1. The ACTIVITY_PLAN Table (continued)Name Type Key Null Description

REC_TYPE INTEGER Y Type of recursion mechanism. The possible valuesare:0 Plan is not recursive1 Recursion on specific days of week2 Recursion on specific days of month3 Recursion at specific date intervals4 Recursion at specific time intervals5 Recursion mechanism has expired6 Recursion mechanism has been stopped due to

an error7 Recursion mechanism has been stopped due to

overlapping of executing instances8 Recursion mechanism has been stopped by user

intervention

DAYS_OF_WEEK VARCHAR(16) Y Executes the activity plan on specific days of theweek, represented by a number from 1 to 7 separatedby a comma or hyphen. 1 represents Sunday. Forexample, for a recursion on Mondays and Fridays thiscolumn would have the value 2,6

DAYS_OF_MONTH VARCHAR(128) Y Executes the activity plan on specific days of themonth, represented by a number from 1 through 31separated by a comma or hyphen. For example, for arecursion on the 1st and 16th of each month, thiscolumn would have the value 1,16

REC_BY_DATE_INT CHAR(16) Y Specifies the date interval at which the plan recursionmechanism is activated. The format is yyyymmdd.For example, for a recursion every 10 days, thiscolumn would have the value 00000010

REC_BY_TIME_INT CHAR(16) Y Specifies the time interval at which the plan recursionmechanism is activated. The format is hh:mm:ss. Forexample, for a recursion every four and a half hours,this column would have the value 04:30:00

IS_DYN_RESOLV CHAR(1) Y Indicates whether targets should be resolved atexecution time. Possible values are:T True - targets are to be resolvedF False

MAIL_ADDRESS VARCHAR(251) Y User e-mail address to notify when an operation isperformed on the plan, such as, when the plan issubmitted, when the plan has completed, or when apause, resume, cancel, or restart operation isperformed on the plan.

NOT_BEFORE_TIME TIMESTAMP Y Earliest date and time at which the plan can beexecuted.

NOT_AFTER_TIME TIMESTAMP Y Latest date and time at which the plan can beexecuted.

ON_TERMINATION INTEGER Y ID of the activity that must be executed as the lastactivity, regardless of the result of the other activities.

CREDENTIALS LONG VARCHAR Y User credential to be used at plan execution.

ACTIVITY_PLAN Table

4 Version 4.1

PLAN_TARGET TableThe PLAN_TARGET table contains the full list of targets addressed by a given activity plan(provided that the user specifies that list at the plan level). Instances of recursive plans usingstatic target resolution will also input to this table. One row is created for each target.

Table 2. The PLAN_TARGET tableName Type Key Null Description

PLAN_ID VARCHAR(80) PKFK(ACTIVITY_PLAN)

N The numeric plan ID generated by thesystem

TARGET_NAME VARCHAR(128) PK N The name of the target addressed by theactivity plan

PLAN_TARGET Table


1.A

ctivityP

lann

erD

atabase

Tables

PLAN_TARGET_SPEC TableThe PLAN_TARGET_SPEC table contains information for the targets addressed by theactivity plan when they are specified as a query library, as an inventory query, as a variableor as a profile manager. There is one ’PLAN_TARGET_SPEC’ row for each activity plan.

Table 3. The PLAN_TARGET_SPEC tableName Type Key Null Description



SPEC_TYPE CHAR(1) N The way in which the targets are specified.Possible values are:F File nameL Query LibraryP Profile ManagerQ Inventory QueryT Target NamesV Variables

TARGET_SPEC VARCHAR(2000) N The value of the target specification. It canbe one of the following:¶ The name of a file¶ The name of a query¶ The name of a profile manager¶ The SQL text of a query¶ A list of target names separated by

commas¶ A variable

PLAN_TARGET_SPEC Table

6 Version 4.1

VARIABLE TableThe VARIABLE table contains information for the user variables defined for a given activityplan. There may be multiple variables for each activity plan.

Table 4. The VARIABLE tableName Type Key Null Description



NAME VARCHAR(128) PK N The name of the user variable.

CURR_VALUE VARCHAR(2000) N The current value of the variable.

VARIABLE Table


1.A

ctivityP

lann

erD

atabase

Tables

ACTIVITY TableThe ACTIVITY table contains the information for an activity that belongs to a specific plan.There may be multiple activities for each activity plan.

Table 5. The ACTIVITY tableName Type Key Null Description



ACTIVITY_ID INTEGER PK N The numeric activity ID generated bythe system

NAME VARCHAR(128) N The name of the activity.

DESCRIPTION VARCHAR(251) Y The description of the activity.

CONDITION VARCHAR(2000) Y A logical expression that defines howthe execution of an activity isconditioned by the outcome of theexecution of one or more conditioningactivities. See the Tivoli SoftwareDistribution Reference manual fordetailed information.

APPLICATION_TYPE VARCHAR(32) N Identifier of the application thatperforms the activity. The possiblevalues are:¶ SoftwareDistribution¶ TaskLibrary

OPERATION_TYPE VARCHAR(32) N Application specific identifier of theoperation performed with this activity.Valid values are provided by theapplication plug-ins.

ACTIVITY Table

8 Version 4.1

ACT_LAYOUT TableThe ACT_LAYOUT table contains information about the layout of a given activity in the APeditor GUI. One row in this table is created for each activity.

Table 6. The ACT_LAYOUT tableName Type Key Null Description

PLAN_ID VARCHAR(80) PKFK(ACTIVITY)

N The numeric plan ID generated by the system

ACTIVITY_ID INTEGER PKFK(ACTIVITY)

N The numeric activity ID generated by the system

USER_ID VARCHAR(64) PK N Reserved.

X_COORD INTEGER N The x coordinate of the activity node in the graphlayout.

Y_COORD INTEGER N The y coordinate of the activity node in the graphlayout.

ACT_LAYOUT Table


1.A

ctivityP

lann

erD

atabase

Tables

ACT_TARGET_SPEC TableThe ACT_TARGET_SPEC table contains information for the targets addressed by a givenactivity when they are specified as a query library, as an inventory query, as a variable or asa profile manager. There is one specification row for each activity.

Table 7. The ACT_TARGET_SPEC tableName Type Key Null Description





SPEC_TYPE CHAR(1) N The way in which the target was specified.Possible values are:F File nameL Query LibraryP Profile ManagerQ Inventory QueryT Target NamesV Variables

TARGET_SPEC VARCHAR(2000) N The value of the target specification. It can be oneof the following:¶ The name of a file¶ The name of a query¶ The name of a profile manager¶ The SQL text of a query¶ A list of target names separated by commas¶ A variable

ACT_TARGET_SPEC Table

10 Version 4.1

ACTIVITY_TARGET TableThe ACTIVITY_TARGET table contains the full list of targets addressed by a given activity(provided that the user specifies that list at the activity level). Instances of recursive plansusing static target resolution will also input to this table. One row is created for each target.

Table 8. The ACTIVITY_TARGET tableName Type Key Null Description





TARGET_NAME VARCHAR(128) PK N The name of the target addressed by the activity.

ACTIVITY_TARGET Table


1.A

ctivityP

lann

erD

atabase

Tables

ACT_PARAMETER TableThe ACT_PARAMETER table is used by the application plug-ins to store the parameters forthe application operation for a given activity. The number of entries in this table may varybetween 2 and about 30.

Table 9. The ACT_PARAMETER tableName Type Key Null Description




N The numeric activity ID generated by thesystem

PARAMETER_NAME VARCHAR(128) PK N The name of the parameter supplied by theapplication plug-in.

PARAMETER_DATA VARCHAR(128) N Application specific data for the parameter.

ACT_PARAMETER Table

12 Version 4.1

EXECUTION_WINDOW TableThe EXECUTION_WINDOW table contains information about the time windows in whichthe execution of a given activity is allowed. There may be multiple execution windows foreach activity, each represented by one row. Each row specifies a time window greater than 5minutes but not greater than one week. The time windows do not overlap and are at least 5minutes apart.

Table 10. The EXECUTION_WINDOW tableName Type Key Null Description





START_TIME TIMESTAMP PK N Weekday and time at which the execution windowopens. The system uses a date in the first completeweek (Sunday through Saturday) in the year 1970 torefer to a generic weekday. For example, if the timewindow for an activity of a plan is to open everyMonday at 10:00 a.m., this column contains thetimestamp for 10:00 a.m. on January 5, 1970, whichwas a Monday.

END_TIME TIMESTAMP N Weekday and time at which the execution windowcloses. The same weekday reference system is usedas for START_TIME.

EXECUTION_WINDOW Table


1.A

ctivityP

lann

erD

atabase

Tables

ACT_PLAN_STATUS TableThe ACT_PLAN_STATUS table contains status information for an activity plan that hasbeen submitted and it is currently in execution or has completed. One row is created foreach plan.

Table 11. The ACT_PLAN_STATUS tableName Type Key Null Description



REC_NUMBER INTEGER PK N The recursion number of the activityplan.

STATUS INTEGER N The current status of the activity plan.The possible values are:0 WAITING1 STARTED2 CANCEL_PENDING3 CANCELED4 CANCELED_BY_CONDITION5 PAUSED6 SUCCESS7 FAILED9 NO_UPD10 IGNORE11 HOLD_BY_CONDITION12 PAUSE_PENDING13 RESUME_PENDING

PREV_STATUS INTEGER N Previous status of the activity plan

START_TIME TIMESTAMP Y The time when the system started theactivity on the target.

COMPLETION_TIME TIMESTAMP Y The time when the system completed theactivity plan on the target.

ACT_PLAN_STATUS Table

14 Version 4.1

ACTIVITY_STATUS TableThe ACTIVITY_STATUS table contains status information for an activity that belongs to asubmitted plan. There is a row for each activity in the plan.

Table 12. The ACT_STATUS tableName Type Key Null Description




N The numeric activity ID generated by thesystem

REC_NUMBER INTEGER PK N The recursion number of the activity plan.The recursion number is a positive integerthat is incremented automatically at each planrecursion.

STATUS INTEGER N The current status of the activity plan. Thepossible values are:0 WAITING1 STARTED2 CANCEL_PENDING3 CANCELED4 CANCELED_BY_CONDITION5 PAUSED6 SUCCESS7 FAILED9 NO_UPD10 IGNORE11 HOLD_BY_CONDITION12 PAUSE_PENDING13 RESUME_PENDING

PREV_STATUS INTEGER N The previous status of the activity.

PRIORITY INTEGER N Priority given by the AP engine to theexecution of the activity.

TIME_ENQUEUED TIMESTAMP Y The time when the activity has been queuedto the AP engine to be executed.

APPL_SPEC_ACT_ID VARCHAR(64) Y Identifier supplied by the application that istracking the operation. The distribution_idreturned by MDIST2.

START_TIME TIMESTAMP Y The time when the system started the activity.

COMPLETION_TIME TIMESTAMP Y The time when the system completed theactivity.

ACTIVITY_STATUS Table


1.A

ctivityP

lann

erD

atabase

Tables

ACT_STATUS_TGT TableThe ACT_STATUS_TGT table contains status information for a target that is addressed byan activity that belongs to a submitted plan. There is a row for each target addressed by agiven activity.

Table 13. The ACT_STATUS_TGT tableName Type Key Null Description

PLAN_ID VARCHAR(80) PKFK(ACTIVITY_STATUS)


ACTIVITY_ID INTEGER PKFK(ACTIVITY_STATUS)

N The numeric activity ID generated bythe system

REC_NUMBER INTEGER PKFK(ACTIVITY_STATUS)

N The recursion number of the activitythat is tracked. The recursion numberis a positive integer that isincremented automatically at eachplan recursion.

TARGET_NAME VARCHAR(128) PK N The name of the target addressed bythe activity plan

STATUS INTEGER N The current status of the activity onthe target. The possible values are:0 WAITING1 STARTED2 CANCEL_PENDING3 CANCELED4 CANCELED_BY_CONDITION5 PAUSED6 SUCCESS7 FAILED9 NO_UPD10 IGNORE11 HOLD_BY_CONDITION12 PAUSE_PENDING13 RESUME_PENDING

PREV_STATUS INTEGER N The previous status of the activity onthe target on the target.

START_TIME TIMESTAMP Y The time when the system started theactivity on the target.

COMPLETION_TIME TIMESTAMP Y The time when the system completedthe activity on the target.

TARGET_OID VARCHAR(16) N The object ID of the target. A TivoliManagement Framework (TMF)object ID.

GATEWAY_OID VARCHAR(16) Y The object ID of the gateway towhich the target is attached. A TMFobject ID.

DEPOT_OID VARCHAR(16) Y Object ID of the depot from whichthe target receives the distributions. ATMF object ID.

GATEWAY_LABEL VARCHAR(128) Y The label of the gateway to which thetarget is attached.

ACT_STATUS_TGT Table

16 Version 4.1

Table 13. The ACT_STATUS_TGT table (continued)Name Type Key Null Description

DEPOT_LABEL VARCHAR(128) Y The label of the depot from which thetarget receives the distributions.

ERROR_INFO VARCHAR(256) Y Diagnostic message returned by theapplication.

ERROR_CODE INTEGER Y The return code returned by theapplication.

ACT_STATUS_TGT Table


1.A

ctivityP

lann

erD

atabase

Tables

APPL_OPERATION TableThe APPL_OPERATION table contains information on the registered application plug-insthat can be used by AP.

Table 14. The APPL_OPERATION tableName Type Key Null Description

APPLICATION_TYPE VARCHAR(32) PK N The ID of the application. The possible values are:¶ SoftwareDistribution¶ TaskLibrary

PACKAGE VARCHAR(251) N The name of the Java™ package that contains the plug-incode.

DESCRIPTION VARCHAR(128) Y The description displayed in the GUI that identifies theapplication.

APPL_OPERATION Table

18 Version 4.1

APPL_ERRLEV TableThe APPL_ERRLEV table contains the mapping between application-specific return codesand AP-defined error levels.

Table 15. The APPL_ERRLEV tableName Type Key Null Description

APPLICATION_TYPE VARCHAR(32) PKFK(APPL_OPERATION)

N The ID of the application. The possiblevalues are:¶ SoftwareDistribution¶ TaskLibrary

RET_CODE INTEGER PK N The return code of the application.

ERROR_LEVEL INTEGER N The error level defined by AP. Thepossible values are:0 SUCCESS1 WARNING2 ERROR3 FATAL

APPL_ERRLEV Table


1.A

ctivityP

lann

erD

atabase

Tables

PLAN_LOCKS TableThe PLAN_LOCKS table contains information about the plans that are currently locked byan active Activity Plan Editor GUI.

Table 16. The PLAN_LOCKS tableName Type Key Null Description

PLAN_ID VARCHAR(80) PK N The numeric plan ID generated by the system

NAME VARCHAR(80) N The name of the locked plan.

APMUSER VARCHAR(128) N The user who locked the plan.

MANAGED_NODE VARCHAR(128) N The managed node where the GUI runs.

LOCK_DATE TIMESTAMP N The date when the plan was locked.

PLAN_LOCKS Table

20 Version 4.1

Change Configuration Manager DatabaseTables

The Change Configuration Manager (CCM) database contains the following tables:¶ REFERENCE_MODEL¶ ELEMENT¶ DEPENDENCY¶ SUBSCRIBER¶ CCM_REPORT


2


2.C

CM

Datab

aseTab

les

REFERENCE MODEL TableThe REFERENCE MODEL table stores the information about each reference model node inthe tree hierarchy. Each time a node is added a new entry is created in this table. When anode is removed from the tree structure, the corresponding entry is deleted from the table. Inaddition, every element, subscriber and child node belonging to the node are deleted.

Table 17. The REFERENCE MODEL TableName Type Key Null Description

REF_MODEL_ID VARCHAR(32) PK N The reference model ID generated by the system.

NAME VARCHAR(64) N The name assigned by the administrator to the reference model.

VER VARCHAR(16) Y The version string assigned by the administrator to thereference model.

DESCRIP VARCHAR(255) Y The description assigned by the administrator to the referencemodel.

PARENT VARCHAR(32) Y The parent reference model in the reference model hierarchy.

LAST_UPDATE TIMESTAMP Y Timestamp of the last time when the reference model wasupdated

IS_LEAF INTEGER N Boolean value to indicate whether the reference model is a leafin the hierarchy. The possible values are:0 False1 True

REFERENCE MODEL Table

22 Version 4.1

ELEMENT TableThe ELEMENT table contains information about the configuration elements belonging to anode in the model tree. Such elements could be Inventory elements (defining a hardwarecondition) as well as Software Distribution elements (packages to be distributed). When anelement is removed from a reference model node, the corresponding entry in the database isdeleted together with each dependency entry that the element contains.

Table 18. The ELEMENT TableName Type Key Null Description

ELEMENT_ID VARCHAR(32) PK N The configuration element IDgenerated by the system.

NAME VARCHAR(255) N The name assigned by theadministrator to the configurationelement.

TYPE VARCHAR(64) N The type of configuration element. Thevalues are defined in theCONFCCM.XML file.

STATE VARCHAR(64) Y The state associated to theconfiguration element. Each applicationdefines a set of possible states.

REF_MODEL_ID VARCHAR(32) FK(REFERENCE_MODEL) N The reference model to which theconfiguration element belongs.

ELEMENT Table


2.C

CM

Datab

aseTab

les

DEPENDENCY TableThe DEPENDENCY table stores information about each Software Distribution element’sdependencies. Only Software Distribution elements contain dependencies. When adependency is removed from a configuration element, the corresponding entry in thedatabase is deleted.

Table 19. The DEPENDENCY TableName Type Key Null Description

DEPENDENCY_ID VARCHAR(32) PK N The dependency ID generated by the system.

NAME VARCHAR(64) N The name assigned by the administrator to thedependency.

TYPE VARCHAR(64) N The type of dependency. The values are defined inthe CONFCCM.XML file.

STATE VARCHAR(64) Y The state associated to the dependency. Eachapplication defines a set of possible states.

ELEMENT_ID VARCHAR(32) FK(ELEMENT) N The configuration element that has thisdependency.

DEPENDENCY Table

24 Version 4.1

SUBSCRIBER TableThe SUBSCRIBER table contains details of all the subscribers belonging to each referencemodel node in the tree structure. Each time the user adds a subscriber to a given node a newentry is inserted into this table. For a Web subscriber two records are created: one referringto the Web subscriber itself and one to the normal subscriber (Static, CSV, Profile Manager,Inventory and Query Library) to which it refers. Each time a subscriber is removed from areference model node the corresponding entry is deleted from the database. When a Websubscriber is removed, its entry and the entry for the normal subscriber it refers to aredeleted.

Table 20. The SUBSCRIBER TableName Type Key Null Description

SUBSCRIBER_ID VARCHAR(32) PK N The subscriber ID generated by thesystem.

NAME VARCHAR(255) N The name assigned by theadministrator to the subscriber.

TYPE VARCHAR(64) N The type of dependency. The valuesare defined in the CONFCCM.XMLfile.

EXCLUDED INTEGER Y Indicates if this subscriber is to beexcluded from the reference model.The possible values are:0 False1 True

PARENT_ID VARCHAR(32) N The parent node in the hierarchy ofsubscribers.

REF_MODEL_ID VARCHAR(32) FK(REFERENCE_MODEL) N The reference model to which thisentity is subscribed.

SUBSCRIBER Table


2.C

CM

Datab

aseTab

les

CCM_REPORT TableThe CCM_REPORT table is used to store information about the actions performed on areference model node. Each time a submit action is performed, a row is added to the tablefor each target addressed by the distribution action. In the case of static subscribers, a rowwill be added for each subscriber; in the case of all other types of subscriber a row will beadded for each target that the subscriber identifies at the moment when the submit action isperformed.

Rows in this table are not deleted automatically by the system: for this reason the databaseadministrator has to schedule a periodical purging activity.

Table 21. The CCM_REPORT TableName Type Key Null Description

REFERENCE_MODEL VARCHAR(64) PK N The reference model that is tracked in the report. Thisvalue is obtained by concatenating the reference modelid and the version strings.

TARGET_NAME VARCHAR(64) PK N The name of the target that is tracked in the report.

PLAN_ID VARCHAR(32) N The plan ID returned by the AP engine for the activityplan. It is used to synchronize the current referencemodel.

TARGET_TYPE VARCHAR(64) Y The type of target. The values are defined in theCONFCCM.XML configuration file.

SUBMIT_TIME TIMESTAMP Y Time at which the synchronize operation was submitted.

RECEIVE_TIME TIMESTAMP Y Time at which the activity report issued by AP has beenreceived from CCM.

PLAN_STATUS VARCHAR(32) N Final status of the activity plan on the target tracked inthe report. The possible values are:¶ Submitted¶ Successful¶ Failed

CCM_REPORT Table

26 Version 4.1

Web User Interface Database Tables

The Web User Interface (Web UI) adds the following two tables to the InventoryConfiguration Repository database:¶ SWP_SUBSCRIPTIONS¶ MOD_SUBSCRIPTIONS


3


3.W

ebU

serIn

terfaceD

atabase

Tables

SWP_SUBSCRIPTIONS TableThe SWP_SUBSCRIPTIONS table contains information about the Web users that havesubscribed to a software package. A new row is inserted into the table each time a Web usermakes a new subscription to a software package. The row is deleted if the Web userunsubscribes from that software package.

Table 22. SWP_SUBSCRIPTIONS TableName Type Key Null Description

TME_OBJECT_ID VARCHAR(128) PK N The valid object ID of the endpoint that subscribes.

SWP_NAME VARCHAR(64) PK N The name of the software package to which the subscriptionapplies.

SWP_VER VARCHAR(16) N Version string of the software package to which thesubscription applies.

SUB_TIME TIMESTAMP N Time at which the subscription is requested.

swp_subscriptions Table

28 Version 4.1

MOD_SUBSCRIPTIONS TableThe MOD_SUBSCRIPTIONS table contains information about the Web users that havesubscribed to a given version of a CCM Reference Model. A new row is inserted into thetable each time a Web user makes a new subscription to a Reference Model. The row isdeleted if the user unsubscribes from that model.

Table 23. The MOD_SUBSCRIPTIONS TableName Type Key Null Description

TME_OBJECT_ID VARCHAR(128) PK N The valid object ID of the endpoint that subscribes.

MOD_NAME VARCHAR(64) PK N The name of the reference model to which the subscriptionapplies.

MOD_VER VARCHAR(16) PK N Version string of the reference mode to which thesubscription applies.

SUB_TIME TIMESTAMP N Time at which the subscription is requested.

SIN_TIME TIMESTAMP Y Time at which the reference model has been synchronizedon the target.

MOD_SUBSCRIBTIONS Table


3.W

ebU

serIn

terfaceD

atabase

Tables

MOD_SUBSCRIBTIONS Table

30 Version 4.1

Index

AACT_LAYOUT table 9ACT_PARAMETER table 12ACT_PLAN_STATUS table 14ACT_STATUS table 15ACT_STATUS_TGT table 16ACT_TARGET_SPEC table 10ACTIVITY_ID column

ACT_LAYOUT table 9ACT_PARAMETER table 12ACT_STATUS table 15ACT_STATUS_TGT table 16ACT_TARGET_SPEC table 10ACTIVITY table 8ACTIVITY_TARGET table 11EXECUTION_WINDOW table 13

ACTIVITY_PLAN table 3Activity Planner database tables 1, 2ACTIVITY table 8ACTIVITY_TARGET table 11APMUSER column

PLAN_LOCKS table 20APPL_ERRLEV table 19APPL_OPERATION table 18APPL_SPEC_ACT_ID column

ACT_STATUS table 15APPLICATION_TYPE column

ACT_STATUS_TGT table 18ACTIVITY table 8APPL_ERRLEV table 19

CCCM_REPORT table 26Change Configuration Management database tables 21COMPLETION_TIME column

ACT_PLAN_STATUS table 14ACT_STATUS table 15ACT_STATUS_TGT table 16

CONDITION columnACTIVITY table 8

CREDENTIALS columnACTIVITY_PLAN table 4

CURR_VALUE columnVARIABLE table 7

DDAYS_OF_MONTH column

ACTIVITY_PLAN table 4

DAYS_OF_WEEK columnACTIVITY_PLAN table 4

DEPENDENCY_ID columnDEPENDENCY table 24

DEPENDENCY table 24DEPOT_LABEL column

ACT_STATUS_TGT table 17DEPOT_OID column

ACT_STATUS_TGT table 16DESCRIP column

REFERENCE MODEL table 22DESCRIPTION column

ACT_STATUS_TGT table 18ACTIVITY_PLAN table 3ACTIVITY table 8

EELEMENT_ID column

DEPENDENCY table 24ELEMENT table 23

ELEMENT table 23END_TIME column

EXECUTION_WINDOW table 13ERROR_CODE column

ACT_STATUS_TGT table 17ERROR_INFO column

ACT_STATUS_TGT table 17ERROR_LEVEL column

APPL_ERRLEV table 19EXCLUDED column

SUBSCRIBER table 25EXECUTION_WINDOW table 13

GGATEWAY_LABEL column

ACT_STATUS_TGT table 16GATEWAY_OID column

ACT_STATUS_TGT table 16

IIS_CANC_CUTOFF column

ACTIVITY_PLAN table 3IS_DYN_RESOLV column

ACTIVITY_PLAN table 4


Ind

ex

IS_LEAF columnREFERENCE MODEL table 22

IS_PAUSED columnACTIVITY_PLAN table 3

IS_POST_NOTICE columnACTIVITY_PLAN table 3

IS_TEMPLATE columnACTIVITY_PLAN table 3

LLAST_UPDATE column

REFERENCE MODEL table 22LOCK_DATE column

PLAN_LOCKS table 20

MMAIL_ADDRESS column

ACTIVITY_PLAN table 4MANAGED_NODE column

PLAN_LOCKS table 20MOD_NAME column

MOD_SUBSCRIPTION table 29MOD_SUBSCRIPTION table 29MOD_VER column

MOD_SUBSCRIPTION table 29

NNAME column

ACTIVITY_PLAN table 3ACTIVITY table 8DEPENDENCY table 24ELEMENT table 23PLAN_LOCKS table 20REFERENCE MODEL table 22SUBSCRIBER table 25VARIABLE table 7

NOT_AFTER_TIME columnACTIVITY_PLAN table 4

NOT_BEFORE_TIME columnACTIVITY_PLAN table 4

OON_TERMINATION column

ACTIVITY_PLAN table 4OPERATION_TYPE column

ACTIVITY table 8

PPACKAGE column

ACT_STATUS_TGT table 18PARAMETER_DATA column

ACT_PARAMETER table 12PARAMETER_NAME column

ACT_PARAMETER table 12PARENT column

REFERENCE MODEL table 22PARENT_ID column

SUBSCRIBER table 25PLAN_ID column

ACT_LAYOUT table 9ACT_PARAMETER table 12ACT_PLAN_STATUS table 14ACT_STATUS table 15ACT_STATUS_TGT table 16ACT_TARGET_SPEC table 10ACTIVITY_PLAN table 3ACTIVITY table 8ACTIVITY_TARGET table 11CCM_REPORT table 26EXECUTION_WINDOW table 13PLAN_LOCKS table 20PLAN_TARGET_SPEC table 6PLAN_TARGET table 5VARIABLE table 7

PLAN_LOCKS table 20PLAN_STATUS column

CCM_REPORT table 26PLAN_TARGET table 5, 6PREV_STATUS column


PRIORITY columnACT_STATUS table 15ACTIVITY_PLAN table 3

RREC_BY_DATE_INT column

ACTIVITY_PLAN table 4REC_BY_TIME_INT column

ACTIVITY_PLAN table 4REC_EXPIRE_TIME column

ACTIVITY_PLAN table 3REC_NUMBER column


REC_STOP_ON_ERROR columnACTIVITY_PLAN table 3

REC_STOP_OVERLAP columnACTIVITY_PLAN table 3

REC_TYPE columnACTIVITY_PLAN table 4

RECEIVE_TIME columnCCM_REPORT table 26

32 Version 4.1

REF_MODEL_ID columnELEMENT table 23REFERENCE MODEL table 22SUBSCRIBER table 25

REFERENCE_MODEL columnCCM_REPORTtable 26

REFERENCE MODEL table 22RET_CODE column

APPL_ERRLEV table 19

SSIN_TIME column

MOD_SUBSCRIPTION table 29SPEC_TYPE column

ACT_TARGET_SPEC table 10PLAN_TARGET_SPEC table 6

START_TIME columnACT_PLAN_STATUS table 14ACT_STATUS table 15ACT_STATUS_TGT table 16EXECUTION_WINDOW table 13

STATE columnDEPENDENCY table 24ELEMENT table 23

STATUS columnACT_PLAN_STATUS table 14ACT_STATUS table 15ACT_STATUS_TGT table 16

STOP_ON_ERROR columnACTIVITY_PLAN table 3

SUB_TIME columnMOD_SUBSCRIPTION table 29SWP_SUBSCRIPTION table 28

SUBMIT_TIME columnCCM_REPORT table 26

SUBSCRIBER_ID columnSUBSCRIBER table 25

SUBSCRIBER table 25SWP_NAME column

SWP_SUBSCRIPTION table 28SWP_SUBSCRIPTION table 28SWP_VER column

SWP_SUBSCRIPTION table 28

Ttable

ACT_LAYOUT 9ACT_PARAMETER 12ACT_PLAN_STATUS 14ACT_STATUS 15ACT_STATUS_TGT 16ACT_TARGET_SPEC 10ACTIVITY 8ACTIVITY_PLAN 3ACTIVITY_TARGET 11

table (continued)APPL_ERRLEV 19APPL_OPERATION 18CCM_REPORT 26DEPENDENCY 24ELEMENT 23EXECUTION_WINDOW 13MOD_SUBSCRIPTION 29PLAN_LOCKS 20PLAN_TARGET 5, 6REFERENCE MODEL 22SUBSCRIBER 25SWP_SUBSCRIPTION 28VARIABLE 7

TARGET_NAME columnACT_STATUS_TGT table 16ACTIVITY_TARGET table 11CCM_REPOR table 26PLAN_TARGET table 5

TARGET_OID columnACT_STATUS_TGT table 16

TARGET_SPEC columnACT_TARGET_SPEC table 10PLAN_TARGET_SPEC table 6

TARGET_TYPE columnCCM_REPORT table 26

TIME_ENQUEUED columnACT_STATUS table 15

TME_OBJECT_ID columnMOD_SUBSCRIPTION table 29SWP_SUBSCRIPTION table 28

TYPE columnDEPENDENCY table 24ELEMENT table 23SUBSCRIBER table 25

UUSER_ID column

ACT_LAYOUT table 9

VVARIABLE table 7VER column

REFERENCE MODEL table 22

WWeb User Interface database tables 27


Ind

ex

XX_COORD column

ACT_LAYOUT table 9

YY_COORD column

ACT_LAYOUT table 9

34 Version 4.1

Date post:	16-Feb-2022
Category:	Documents
Upload:	others
View:	12 times
Download:	0 times