ReportCaster Repository Tables

ReportCaster uses a repository of tables that store distribution and scheduling information. At installation, an SQL-based repository is created in a selected location. The Report Library requires an SQL-based repository.

The following is a list of ReportCaster Repository tables, their contents, and primary keys.

Table

Contains

Primary Keys

BOTACCES

Access List names.

One record per Access List and 1:m with BOTLIST.

Access List name

BOTADDR

Properties of each Distribution List. For example, its name and whether it is a public or private list.

One record per list and 1:m with BOTDEST.

Distribution List name

BOTCAT

Library catalog table. Includes one record for each report in the Report Library. If the schedule is burst, each bursted report is a record.

Report group ID

BOTCDATE

Information about the custom run intervals of schedules.

 

BOTDEST

Recipients and destinations within a Distribution List. One record per destination.

Distribution List name and a counter from 1 to n for each member of a particular Distribution List.

BOTGRP

Group name and description.

Group name

BOTGUSER

User IDs within each group name.

Group name, user

BOTJOURN

Journal of all Two-Way events.

Process number that is generated when e-mail activity occurs on the mail Listener. Time of e-mail activity.

BOTLDATA

Report stored in the Report Library, in BLOB format.

Report ID and a counter from 1 to n for each report stored in the library.

BOTLIB

Version and expiration information. One record for each report in the Report Library.

Report group ID, and version.

BOTLIST

User IDs and burst values within each Access List. One record per destination.

Access List name and a counter from 1 to n for each member of a particular Access List.

BOTLOG

General log information, such as the start time and end time for each executed job.

One record per job run and a 1:m with BOTLOG2.

Process number that is generated when a job is run.

BOTLOG2

Detailed log records for all jobs that have run. One record per job message.

Process number and a counter that runs from 1 to n for each detail log record for a particular process number.

BOTPACK

Packet ID that uniquely identifies each schedule.

Packet ID

BOTPARMS

Parameter names and values for each Task. One record per parameter per Task.

Schedule ID, Task ID, parameter name, and a counter from 1 to n for each parameter in a Task.

BOTSBDS

Schedule Blackout Dates Table. Contains global and group schedule blackout dates and descriptions.

ID

BOTSCHED

Timing, frequency, and connection information about a particular schedule. Distribution methods (for example, e-mail or FTP), along with supporting information, such as Reply Address and location of recipient. Distribution List (if any).

One record per schedule.

Schedule ID

BOTSCIT

Information about the custom run intervals of schedules.

 

BOTSTATE

Failover and Workload Distribution information.

 

BOTTASK

Individual Task information. Includes the name of the Task, the Execution ID for the Task, and the WebFOCUS Reporting Server name. For Managed Reporting Standard Report or My Report Tasks, BOTTASK also lists the folder and domain. There is a BOTTASK record for each Task in a schedule. Since there can be multiple Tasks in a schedule, there is a 1:m relationship with BOTSCHED.

Task ID, Packet ID

BOTTELL

User subscription information.

E-mail ID of the Subscriber, ReportCaster user ID

BOTTSKEX

ReportCaster user ID. Execution ID and password. Contains execution type (for example, WF Server Procedure). Depending on execution type, contains server name (for WF Server Procedures and Managed Reporting reports), application name (for files), or server name and port (for URLs, FTP files, and mainframe output).

One record per Task.

ReportCaster User ID, Execution ID, server name, server type

BOTUPROF

User profiles and capabilities. One record per scheduling user.

ReportCaster user ID

BOTWATCH

Library Watch List information.

 


WebFOCUS