11.4 Creating Customized Reports

Using the following database information, you can create custom reports for the Server Policies and Tiered Electronic Distribution components.

However, for Tiered Electronic Distribution objects such as a Subscriber or the External Subscriber, you should use ZENworks reporting options (see Section 11.0, Reporting) or iManager (Section 2.0, Novell iManager) for determining the status of Distributions or policies.

The database file (zfslog.db) contains the following information:

11.4.1 Default Sybase Database User ID and Password

The Sybase database (zfslog.db) that ships with Server Management has the following default user ID and password:

User ID: dba

Password: sql

You can choose to change the password. For more information on changing the password, see Section 10.1.8, Changing the Default Sybase Database Password.

11.4.2 Server Policies Database Contents

Following are the database table definitions for server policies:

SERVERS

Contains one record for each server running the Policy/Package Agent.

Table 11-1 Servers Field Names

Field Name

Type

Use

 

 

SERVERID

integer

 

not null

Unique number that is automatically assigned.

SERVERNAME

varchar

not null

The short name of the server as seen on the console prompt.

SERVERDN

varchar

 

DN of the Server object in eDirectory (dot separated).

REVERSEDN

varchar

not null

SERVERDN in reverse order and backslash (\) delimited.

OSNAME

varchar

 

Name of the operating system, such as NetWare 5.1.

OSVERSION

char

 

Version of the operating system, such as 5.1, 6.0, and so on.

TREENAME

varchar

 

Name of the eDirectory tree containing the server.

Primary key (SERVERID)

SERVERIP

Contains one record for each server running the Policy/Package Agent.

Table 11-2 ServerIP Field Names

Field Name

Type

Use

 

 

SERVERIPKEY

integer

not null

Assigned automatically: Default Auto increment.

SERVERID

integer

not null

Links to the SERVERS table.

IPADDRESS

varchar

not null

Server’s IP address.

Primary key (SERVERID) REFERENCES SERVERS Primary key (SERVERIPKEY)

PACKAGES

Contains one record for each version of a software package that the Policy/Package Agent has attempted to process.

Table 11-3 Packages Field Names

Field Name

Type

Use

 

 

PACKAGEGUID

char

not null

Assigned automatically.

PACKAGENAME

char

 

Name of .cpk file or policy package.

PACKAGEDESC

char

 

Description contained in a Server Software Package component.

PACKAGEVERSION

char

 

Version of the software package.

BUILDDATE

integer

 

Date the software package was compiled.

Primary key (PACKAGEGUID)

POLICIES

Contains one record for each policy or policy package combination.

Table 11-4 Policies Field Names

Field Name

Type

Use

 

 

POLICYID

integer

not null

A globally unique ID.

POLICYDN

varchar

The DN of the eDirectory policy object.

POLICYPACKAGE

varchar

The DN of the policy package the policy belongs to.

POLICYCLASS

varchar

The class or type of policy. For definitions, see Valid Entries for POLICYCLASS.

POLICYTREENAME

varchar

The name of the tree the policy object is in.

Primary key (POLICYID)

Valid Entries for POLICYCLASS
  • zenZFSServerDowningPolicy
  • zenZFSScheduleDownPolicy
  • zenZFSSetServerParamPolicy
  • zenZFSServerScriptPolicy
  • zenZFSTextFilePolicy
  • zenZFSScheduledRunPolicy
  • zenZFSZFSPolicy
  • zenZFSCommunityPolicy
  • zenZFSSNMPTrapTargetPolicy
  • zenZFSSMTPHostPolicy
  • zenZFSDatabaseLocationPolicy
  • zenZFSLicenseLocationPolicy
  • zenZFSTEDPolicy

POLICYACTION

Contains one record for each action performed.

Table 11-5 PolicyAction Field Names

Field Name

Type

Use

 

 

POLICYACTIONKEY

integer

not null

Assigned automatically: Default Auto increment.

POLICYID

integer

not null

Links to the POLICIES table.

SERVERID

integer

not null

Links to the SERVERS table.

CREATIONDATE

timestamp

Time stamp of the action.

DESCRIPTION

varchar

Undefined string describing an error.

CODE

integer

Code representing the result of the action. For definitions, see Valid Entries for CODE.

ACTIONCODE

integer

The action being performed. For definitions, see Valid Entries for ACTIONCODE.

Primary key (POLICYACTIONKEY)

Valid Entries for CODE

RC_POL_SUCCESS

= 0

RC_POL_PARTIAL_SUCCESS

= 1

RC_POL_FAILURE

= ‑1

RC_POL_EMPTY

= ‑2

Exception: If the value in the ACTIONCODE field is AC_POL_DOWN_CONNECTIONS or AC_POL_DOWN_DISCONNECTIONS, then the value of CODE is either the current number of active connections, or the number of forced disconnects.

A number 1 in the CODE field can mean one of the following:

  • There was a partial success

  • There is one active connection

  • There was one forced disconnect

This is because the meaning of the entry in the CODE field is determined by the content of the ACTION CODE field.

Valid Entries for ACTIONCODE

AC_POL_DISCOVERED

= 101

AC_POL_SCHEDULED

= 102

AC_POL_APPLIED

= 103

AC_POL_APPLIED_CHANGE

= 104

AC_POL_NO_ENFORCER

= 105

AC_POL_DOWN_CONNECTIONS

= 106

AC_POL_DOWN_DISCONNECTIONS

= 107

AC_POL_DOWN_UNLOAD

= 108

AC_POL_DOWN_EMAIL

= 109

AC_POL_DOWN_NOTIFY

= 110

AC_POL_DOWN_CANCELED

= 111

AC_POL_DOWN_IGNORED

= 112

AC_POL_DOWN_REQUESTED

= 113

PACKAGEACTION

Contains one record for each action taken on a Server Software Package.

Table 11-6 PackageAction Field Names

Field Name

Type

Use

 

 

PACKAGEACTIONID

integer

not null

Assigned automatically: Default Auto increment.

PACKAGEGUID

char

not null

Links to the PACKAGES table.

SERVERID

integer

not null

Links to the SERVERS table.

CREATIONDATE

timestamp

Time stamp of the action.

DESCRIPTION

varchar

For definitions, see Valid Entries for DESCRIPTION.

CODE

integer

Code representing the results of the action. For definitions, see Valid Entries for CODE.

ACTIONCODE

integer

Code representing the action being performed. For definitions, see Valid Entries for ACTIONCODE.

STARTEDPACKAGEACTIONID

integer

0 = started running the package, or when the new action is logged then the PACKAGEACTIONID of the new action replaces the 0.

Primary key (PACKAGEACTIONID)

Valid Entries for DESCRIPTION
  • Started package
  • Finished rollback
  • Error description
  • Or it is empty
Valid Entries for CODE

Success

= 0

Failure

= 1

Partial

= 2

Valid Entries for ACTIONCODE

AC_PACKAGE_INSTALL

= 0

AC_PACKAGE_ROLLBACK

= 1

AC_PACKAGE_INSTALL_STARTED

= 2

AC_PACKAGE_ROLLBACK_STARTED

= 3

SOFTWARECOMPONENTACTION

Contains one record for each server Server Software Package component.

Table 11-7 SoftwareComponentAction Field Names

Field Name

Type

Use

 

 

SOFTWARECOMPONENTACTIONKEY

integer

not null

Assigned automatically: Default Auto increment.

PACKAGEACTIONID

integer

not null

Links to the PACKAGEACTION table.

NAME

char

not null

Name of the software component.

CREATIONDATE

timestamp

Time stamp of the action.

DESCRIPTION

varchar

The first record for the component the description is the description provided by the user when the component was created. As the components finish the description is one of those defined under Valid Entries for DESCRIPTION.

CODE

integer

Code representing the results of the action. For definitions, see Valid Entries for CODE.

ACTIONCODE

integer

Code representing the action being performed. For definitions, see Valid Entries for ACTIONCODE.

Primary key (SOFTWARECOMPONENTACTIONKEY)

Valid Entries for DESCRIPTION
  • Did not meet requirements
  • Error processing requirements
  • Pre-install load/unload
  • Error pre-install load/unload
  • Pre-install scripts
  • Error pre-install scripts
  • Copy file changes
  • Error processing copy file
  • Text file changes
  • Error processing text files
  • NetWare SET parameters
  • Error processing NetWare SET parameters
  • Registry process
  • Error processing Registry
  • NetWare products process
  • Error in NetWare products process
  • Post-install script process
  • Error in post-install script process
  • Post-install load/unload process
  • Error in post-install load/unload process
Valid Entries for CODE

Success

= 0

Failure

= 1

Partial

= 2

Valid Entries for ACTIONCODE

Started

= 200

Pre-Load

= 201

Pre-Scripts

= 202

Copy File Changes

= 203

Text File Changes

= 204

Set Parameters

= 205

Registry

= 206

Products.dat

= 207

Post Scripts

= 208

Post Load

= 209

Requirements

= 210

Foreign Keys

Foreign keys set up relationships between tables.

POLICYACTION

"add foreign key (POLICYID) references POLICIES (POLICYID)"

POLICYACTION

"add foreign key (SERVERID) references SERVERS (SERVERID)"

PACKAGEACTION

"add foreign key (PACKAGEGUID) references PACKAGES (PACKAGEGUID)"

PACKAGEACTION

"add foreign key (SERVERID) references SERVERS (SERVERID)"

SOFTWARECOMPONENTACTION

"add foreign key (PACKAGEACTIONID) references PACKAGEACTION (PACKAGEACTIONID)"

11.4.3 Tiered Electronic Distribution Database Contents

Following are the database table definitions for Tiered Electronic Distribution:

TAB_NODE

Contains one record for each Distributor, Subscriber, and External Subscriber in the tree.

Table 11-8 Tab_Node Field Names

Field Name

Type

Use

 

 

ID

numeric(8,0)

identity

not null

Unique number automatically assigned.

NAME

varchar(255)

 

not null

Tiered Electronic Distribution object DN.

TYPE

char

 

not null

"D"=Distributor "T"=Subscriber (Transceiver)

NETWORK_ADDRESS

varchar(255)

 

 

IP address of server.

SERVER_NAME

varchar(255)

 

 

Not currently used.

Primary key (ID) Unique (NAME)

TAB_CHANNEL

Contains one record for each Channel object in the tree.

Table 11-9 Tab_Channel Field Names

Field Name

Type

Use

 

 

ID

numeric(8,0)

identity

not null

Unique number automatically assigned.

NAME

varchar(255)

 

not null

DN of Channel object.

Primary key (ID) Unique (NAME)

TAB_DISTRIBUTION

Contains one record for each Distribution object in eDirectory.

Table 11-10 Tab_Distribution Field Names

Field Name

Type

Use

 

 

ID

numeric(8,0)

identity

not null

Unique number automatically assigned.

NAME

varchar(255)

 

not null

DN of Distribution object.

DISTRIBUTOR_ID

numeric(8,0)

 

not null

Links to the TAB_NODE table.

Primary key (ID) Unique (NAME)

TAB_DIST_VERSION

Contains one record for each version of a Distribution and it is linked to the TAB_DISTRIBUTION table.

Table 11-11 Tab_Dist_Version Field Names

Field Name

Type

Use

 

 

ID

numeric(10,0)

identity

not null

Unique number automatically assigned.

DISTRIBUTION_ID

numeric(8,0)

 

not null

Links to the TAB_DISTRIBUTION table.

VERSION

bigint

 

not null

Time stamp of the version.

SIZE

integer

 

not null

Size of distfile.ted (the file containing the Distribution).

TIMESTAMP

datetime

 

not null

Time stamp when the entry was made to the database.

DIRECT_ROUTING

bit

 

not null

Not used at the current time.

LATEST_VERSION

bit

 

not null

Latest version of this Distribution. Used internally to keep track of the latest version.

Primary key (ID) Unique (DISTRIBUTION_ID, VERSION)

TAB_DIST_ACTION

Contains multiple records for each Distribution version for Send, Received, and Extracted.

Table 11-12 Tab_Dist_Action Field Names

Field Name

Type

Use

 

 

ID

numeric(12,0)

identity

not null

Unique number automatically assigned.

DIST_VERSION_ID

numeric(10,0)

 

not null

Links to the TAB_DIST_VERSION table.

NODE_ID

numeric(8,0)

 

not null

Links to the TAB_NODE table for the node performing the following tasks:

  • Create
  • Send
  • Receive
  • Extract
  • Post process

TIMESTAMP

datetime

 

not null

Time stamp when the action was logged into the database.

STAGE

char

 

not null

"C"=Create "S"=Send "R"=Receive "E"=Extract "P"=Post process

STATUS

char

 

not null

"S"=Success "F"=Failure "P"=In process

STATUS_TIMESTAMP

datetime

 

not null

Time stamp when the record was updated.

REASON_TEXT

varchar(255)

 

 

Reason for success or failure. For definitions, see Valid Entries for REASON_TEXT.

CHANEL_DIST_ID

numeric(8,0)

 

 

Links to the TAB_CHANNEL_DISTRIBUTION table.

Primary key (ID)

Valid Entries for REASON_TEXT

The following are valid entries for the REASON_TEXT field name:

  • “The Distribution was not received because this Subscriber does not meet the platform restrictions.”

    Self-explanatory.

  • “The Distribution was shut down before it was received.”

    This one is received in one of two situations: 1) there is a new configuration on the Subscriber so it needs to be updated before it can receive the Distribution; or, 2) there is a signature exception, such as the Subscriber cannot trust the Distribution came from a Distributor it trusts.

  • “The Distribution was terminated before it was received.”

    The Distribution was cancelled for a controlled reason.

  • “There was an error receiving the Distribution.”

    Something unexpected failed. For example, a socket exception, transport exception, and so on.

TAB_CHANNEL_DISTRIBUTION

Contains one record for each Channel/Distribution.

Table 11-13 Tab_Channel_Distribution Field Names

Field Name

Type

Use

 

 

ID

numeric(8,0)

identity

not null

Unique number automatically assigned

CHANNEL_ID

numeric(8,0)

not null

Links to the TAB_CHANNEL table.

DISTRIBUTION_ID

numeric(8,0)

not null

Links to the TAB_DISTRIBUTION table.

TIMESTAMP

datetime

not null

Time stamp for when the Distribution was built.

Primary key (ID) Unique (CHANNEL_ID, DISTRIBUTION_ID)

Foreign Keys

Foreign keys set up relationships between tables.

TAB_DISTRIBUTION

" add foreign key FK_TAB_DIST_REF_591_TAB_NODE (DISTRIBUTOR_ID)" + " references TAB_NODE (ID) on update restrict on delete restrict;";

TAB_DIST_VERSION

" add foreign key FK_TAB_DIST_REF_37_TAB_NODE (DISTRIBUTOR_ID)" + " references TAB_DISTRIBUTION (ID) on update restrict on delete restrict;";

TAB_DIST_ACTION

" add foreign key FK_TAB_DIST_REF_380_TAB_NODE (DIST_VERSION_ID)" + " references TAB_DIST_VERSION (ID) on update restrict on delete restrict;";

TAB_DIST_ACTION

" add foreign key FK_TAB_DIST_REF_1525_TAB_NODE (NODE_ID)" + " references TAB_NODE (ID) on update restrict on delete restrict;";

TAB_CHANNEL_DISTRIBUTION

" add foreign key FK_TAB_DIST_REF_572_TAB_DIST (DISTRIBUTION_ID)" + " references TAB_DISTRIBUTION (ID) on update restrict on delete restrict;";

TAB_CHANNEL_DISTRIBUTION

" add foreign key FK_TAB_DIST_REF_572_TAB_CHAN (CHANNEL_ID)" + " references TAB_CHANNEL (ID) on update restrict on delete restrict;";