Retek® Integration Bus™ 11.0
Data Model
Corporate Headquarters:
Retek Inc. Retek on the Mall 950 Nicollet Mall Minneapolis, MN 55403 USA
888.61.RETEK (toll free US) Switchboard: +1 612 587 5000
Fax: +1 612 587 5100
European Headquarters:
Retek 110 Wigmore Street London W1U 3RW United Kingdom
Switchboard: +44 (0)20 7563 4600
Sales Enquiries: +44 (0)20 7563 46 46
Fax: +44 (0)20 7563 46 10
The software described in this documentation is furnished under a license agreement, is the confidential information of Retek Inc., and may be used only in accordance with the terms of the agreement.
No part of this documentation may be reproduced or transmitted in any form or by any means without the express written permission of Retek Inc., Retek on the Mall, 950 Nicollet Mall, Minneapolis, MN 55403, and the copyright notice may not be removed without the consent of Retek Inc.
Information in this documentation is subject to change without notice.
Retek provides product documentation in a read-only-format to ensure content integrity. Retek Customer Support cannot support documentation that has been changed without Retek authorization.
Retek® Integration BusTM is a trademark of Retek Inc.
Retek and the Retek logo are registered trademarks of Retek Inc.
This unpublished work is protected by confidentiality agreement, and by trade secret, copyright, and other laws. In the event of publication, the following notice shall apply:
©2004 Retek Inc. All rights reserved.
All other product names mentioned are trademarks or registered trademarks of their respective owners and should be treated as such.
Printed in the United States of America.
Retek Integration Bus
Customer Support Customer Support hours
Customer Support is available 7x24x365 via email, phone, and Web access.
Depending on the Support option chosen by a particular client (Standard, Plus, or Premium), the times that certain services are delivered may be restricted. Severity 1 (Critical) issues are addressed on a 7x24 basis and receive continuous attention until resolved, for all clients on active maintenance. Retek customers on active maintenance agreements may contact a global Customer Support representative in accordance with contract terms in one of the following ways.
Contact Method Contact Information
E-mail [email protected]
Internet (ROCS) rocs.retek.com Retek’s secure client Web site to update and view issues
Phone +1 612 587 5800
Toll free alternatives are also available in various regions of the world:
Australia +1 800 555 923 (AU-Telstra) or +1 800 000 562 (AU-Optus) France 0800 90 91 66 United Kingdom 0800 917 2863 United States +1 800 61 RETEK or 800 617 3835
Mail Retek Customer Support Retek on the Mall 950 Nicollet Mall Minneapolis, MN 55403
When contacting Customer Support, please provide:
• Product version and program/module name.
• Functional and technical description of the problem (include business impact).
• Detailed step-by-step instructions to recreate.
• Exact error message received.
• Screen shots of each step you take.
Overview
Overview Following is an overview of the two sections of the data model:
• Relational Integrity Diagrams
• Data Dictionary Language
Relational Integrity Diagrams
These diagrams show the relationship between the various tables within functional area. They include:
• Table names
• Column names
• Primary and foreign keys
Data Dictionary Language
This section includes the Data Dictionary Language (DDLs) for the Retek Integration Bus (RIB) database. The DDLs include:
• Table names and descriptions
• Column summaries
• Primary and foreign keys (if applicable)
• Check constraints (if applicable)
• Index summaries (if applicable)
• Column detail information
RIB_MESSAGE_ROUTING_INFO
MESSAGE_NUM
SEQ_NUMBER
NAME
VALUE
DETAIL1_NAME
DETAIL1_VALUE
DETAIL2_NAME
DETAIL2_VALUE
RIB_MESSAGE_HOSPITAL_REF
MESSAGE_NUM
SEQ_NUMBER
HOSPITAL_REF
LOCATION
MESSAGE_FAMILY
NEW_REASON_CODE
OLD_REASON_CODE
RIB_MESSAGE_FAILURE
MESSAGE_NUM
SEQ_NUMBER
TIME
LOCATION
DESCRIPTION
ERROR_TYPE
ERROR_CODE
RIB_MESSAGE
MESSAGE_NUM
LOCATION
FAMILY
TYPE
ID
RIB_MESSAGE_ID
PUBLISH_TIME
IN_QUEUE
MESSAGE_DATA
ATTEMPT_COUNT
MAX_ATTEMPTS
NEXT_ATTEMPT_TIME
DELETE_PENDING
TOPIC_NAME
THREAD_VALUE
JMS_QUEUE_ID
CUSTOM_FLAG
CUSTOM_DATA
REASON_CODE
Diagram : DD_RIB_HOSPITALTitle : Rib Hospital Diagram
RMH_RMG_FK
RMR_RMG_FK
RMF_RMG_FK
Oracle Designer
RTKDBA
20 August 2004
T:\RIB11.0\cktci.pdf
Parameter Values
Workarea :
Container :
Tables : Yes
Tab/View/Snap Name : %
Tables CreatedOn/After :
On/Before :
Tables Changed
20 August 2004
20 August 2004
Yes Column Details :
Views : Yes Snapshots : Yes
Diagram :
Includes
On/After :
On/Before :
and
Report : TABLE DEFINITION
Filename :
Run by :
Report Date :
Total Pages :
Container Version : Recurse Sub-Containers :
GLOBAL SHARED WORKAREA
RIB 11.0
N
19
20 August 2004 Page 2 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RDOAlias :
Column
RIB_DOC_TYPES_I1
Name
NOT UNIQUE
Index Type
Primary Key
DOC_NAME
DOC_TYPE_URL
ACTIVE_IND
DOC_TYPE_DATA
Specifies the message name.
Specifies a location on the network where the DTD can be found.
Specifies whether the message is currently used in the system.
Column Detail
Index Summary
10
20
30
40
Optional ? :No ; Varchar2 (255) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (255) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (1) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Clob () ;() ; ; Uppercase ? :No ;
DOC_NAME
DOC_TYPE_URL
ACTIVE_IND
DOC_TYPE_DATA
Column
VARCHAR2 (255)
VARCHAR2 (255)
VARCHAR2 (1)
CLOB ()
Type
NOT NULL
NOT NULL
NOT NULL
NOT NULL
Nulls ?Col.Seq.
10
20
30
40
Column Summary
Seq.
1
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_DOCTYPES DOC_NAME
Name Column
This table contains the DTD (Document Type Definition) information forRIB messages used in CLOB-based APIs.
Description :
Table Name : RIB_DOCTYPES
20 August 2004 Page 3 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Contains the DTD
Column Detail
20 August 2004 Page 4 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RBEAlias :
LANG references RIB_LANG.LANG
RBE_RBL_FK
CHK_RIB_ERRORS_APPROVED_IND
CHK_RIB_ERRORS_TYPE
Name
Check Constraints
Foreign Keys
Primary Key
TYPE
Where Validate Clause
Column Detail
10
Optional ? :No ; Varchar2 (2) ;() ; ; Uppercase ? :No ;
TYPE
CODE
LANG
TEXT
APPROVED_IND
Column
VARCHAR2 (2)
VARCHAR2 (25)
NUMBER (6, 0)
VARCHAR2 (255)
VARCHAR2 (1)
Type
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
Nulls ?Col.Seq.
10
20
30
40
50
Column Summary
APPROVED_IND IN ('Y','N')
TYPE IN ('BL','SY')
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_ERRORS TYPECODELANG
Transferable ?
Mandatory ?
Update Rule :
Delete Rule :
Yes
Yes
Restricted
Restricted
Name Column
Contains error message codes and their corresponding message text.Similar to the RTK_ERRORS table, except the errors on RIB_ERRORS areowned by the RIB.
Description :
Table Name : RIB_ERRORS
20 August 2004 Page 5 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
CODE
LANG
Column
RIB_ERRORS_I1
RIB_ERRORS_I2
Name
NOT UNIQUE
NOT UNIQUE
Index Type
CODE
LANG
TEXT
APPROVED_IND
Represents the type of error that the message is describing. Valid values are:'BL' - Business Logic, 'OR' - A system related error, 'SY'.
Contains a code for the error message. When an error is initially raised, thecode is specified
Specifies what language the message text was written in. This numbercorresponds to a record in the RIB_LANG table.
Contains the text of the message.
Indicates whether or not the message has been approved. Valid values are 'Y'and 'N'
Column Detail
Index Summary
20
30
40
50
Optional ? :No ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Number (6, 0) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (255) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (1) ;() ; ; Uppercase ? :No ;
Seq.
1
1
20 August 2004 Page 6 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RBLAlias :
Primary Key
LANG
DESCRIPTION
Contains a number that uniquely identifies a language.
Contains a description or name for the language.
Column Detail
10
20
Optional ? :No ; Number (6, 0) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (30) ;() ; ; Uppercase ? :No ;
LANG
DESCRIPTION
Column
NUMBER (6, 0)
VARCHAR2 (30)
Type
NOT NULL
NOT NULL
Nulls ?Col.Seq.
10
20
Column Summary
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_LANG LANG
Name Column
Used in conjunction with the RIB_ERRORS table to decode messages.Description :
Table Name : RIB_LANG
20 August 2004 Page 7 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RMGAlias :
Primary Key
MESSAGE_NUM
Column Detail
10
MESSAGE_NUM
LOCATION
FAMILY
TYPE
ID
RIB_MESSAGE_ID
PUBLISH_TIME
IN_QUEUE
MESSAGE_DATA
ATTEMPT_COUNT
MAX_ATTEMPTS
NEXT_ATTEMPT_TIME
DELETE_PENDING
TOPIC_NAME
THREAD_VALUE
JMS_QUEUE_ID
CUSTOM_FLAG
CUSTOM_DATA
REASON_CODE
Column
NUMBER (8, 0)
VARCHAR2 (60)
VARCHAR2 (25)
VARCHAR2 (30)
VARCHAR2 (255)
VARCHAR2 (255)
DATE
VARCHAR2 (1)
CLOB ()
NUMBER (4, 0)
NUMBER (4, 0)
DATE
VARCHAR2 (1)
VARCHAR2 (255)
NUMBER (22, 8)
VARCHAR2 (255)
VARCHAR2 (1)
CLOB ()
VARCHAR2 (10)
Type
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
NOT NULL
NULL
NULL
NULL
NOT NULL
NULL
NOT NULL
Nulls ?Col.Seq.
10
20
30
40
50
60
70
80
90
100
110
120
130
140
150
160
170
180
190
Column Summary
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_MESSAGE MESSAGE_NUM
Name Column
The main table of the four RIB Hospital tables, which usually residein the subscribing application's database. Holds the elements from the<ribMessage> node.
Description :
Table Name : RIB_MESSAGE
20 August 2004 Page 8 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
ID
FAMILY
LOCATION
JMS_QUEUE_ID
Column
RIB_MESSAGE_IX1
RIB_MESSAGE_IX1
RIB_MESSAGE_IX1
RIB_MESSAGE_IX1
Name
NOT UNIQUE
NOT UNIQUE
NOT UNIQUE
NOT UNIQUE
Index Type
LOCATION
FAMILY
TYPE
ID
RIB_MESSAGE_ID
PUBLISH_TIME
IN_QUEUE
MESSAGE_DATA
ATTEMPT_COUNT
Unique primary key, generated from RIB_MESSAGE_SEQ sequence.
The collaboration (module) and e*Way (sub-module) of the publisher of thismessage.
The message family
The message type.
The Business Object ID
Unique identifier of where this message came from.
The timestamp of when this message was published
Signifies whether message has been put back onto JMS.
The message data XML payload.
Column Detail
Index Summary
20
30
40
50
60
70
80
90
100
Optional ? :No ; Number (8, 0) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (60) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (30) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (255) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (255) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (1) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Clob () ;() ; ; Uppercase ? :No ;
Optional ? :No ; Number (4, 0) ;() ; ; Uppercase ? :No ;
Seq.
1
2
3
4
20 August 2004 Page 9 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
MAX_ATTEMPTS
NEXT_ATTEMPT_TIME
DELETE_PENDING
TOPIC_NAME
THREAD_VALUE
JMS_QUEUE_ID
CUSTOM_FLAG
CUSTOM_DATA
REASON_CODE
How many times this message has been retried.
The maximum times this message will be retried (rib.properties).
The next time this message will be retried (rib.properties).
When set to 1, signals to Hospital Controller to delete this record and it'schildren.
The JMS Topic where this message needs to be re-published to during retry.
The RIB thread that this message is being processed with.
The JMS hostname:port of the environment the message came from.
Signifies whether the custom data tag is populated or not.
The custom data/payload.
A high level code representing why this record is in the Hospital. SUB (fromsubscriber), PUB (from publisher) or JMS (problem with JMS).
Column Detail
110
120
130
140
150
160
170
180
190
Optional ? :No ; Number (4, 0) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Date ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (1) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (255) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Number (22, 8) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (255) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (1) ;() ; ; Uppercase ? :No ; Default Value :F ;
Optional ? :Yes ; Clob () ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (10) ;() ; ; Uppercase ? :No ; Default Value :SUB ;
20 August 2004 Page 10 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RMFAlias :
MESSAGE_NUM references RIB_MESSAGE.MESSAGE_NUM
RMF_RMG_FK
Foreign Keys
Primary Key
MESSAGE_NUM
SEQ_NUMBER
TIME
Unique primary key, generated from RIB_MESSAGE_SEQ sequence.
Incrementing number for each subsequent failure
Column Detail
10
20
30
Optional ? :No ; Number (8, 0) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Number (2, 0) ;() ; ; Uppercase ? :No ;
MESSAGE_NUM
SEQ_NUMBER
TIME
LOCATION
DESCRIPTION
ERROR_TYPE
ERROR_CODE
Column
NUMBER (8, 0)
NUMBER (2, 0)
DATE
VARCHAR2 (60)
VARCHAR2 (4000)
VARCHAR2 (2)
VARCHAR2 (25)
Type
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
Nulls ?Col.Seq.
10
20
30
40
50
60
70
Column Summary
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_MESSAGE_FAILURE MESSAGE_NUMSEQ_NUMBER
Transferable ?
Mandatory ?
Update Rule :
Delete Rule :
Yes
Yes
Restricted
Restricted
Name Column
A child table of the RIB Hospital. Holds the elements from the<failure> nodes.
Description :
Table Name : RIB_MESSAGE_FAILURE
20 August 2004 Page 11 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
LOCATION
DESCRIPTION
ERROR_TYPE
ERROR_CODE
Time of the Failure
The collaboration (module) and e*Way (sub-module) of the publisher of thismessage.
The error message or Exception itself.
The error type from the RIB_ERRORS table.
The error code from the RIB_ERRORS table.
Column Detail
40
50
60
70
Optional ? :No ; Date ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (60) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (4000) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (2) ;() ; ; Uppercase ? :No ; Default Value :SY ;
Optional ? :Yes ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
20 August 2004 Page 12 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RMHAlias :
MESSAGE_NUM references RIB_MESSAGE.MESSAGE_NUM
RMH_RMG_FK
Foreign Keys
Primary Key
MESSAGE_NUM
SEQ_NUMBER
HOSPITAL_REF
Unique primary key, generated from RIB_MESSAGE_SEQ sequence.
Incrementing number for each record.
Column Detail
10
20
30
Optional ? :No ; Number (8, 0) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Number (2, 0) ;() ; ; Uppercase ? :No ;
MESSAGE_NUM
SEQ_NUMBER
HOSPITAL_REF
LOCATION
MESSAGE_FAMILY
NEW_REASON_CODE
OLD_REASON_CODE
Column
NUMBER (8, 0)
NUMBER (2, 0)
VARCHAR2 (8)
VARCHAR2 (60)
VARCHAR2 (25)
VARCHAR2 (10)
VARCHAR2 (10)
Type
NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NULL
Nulls ?Col.Seq.
10
20
30
40
50
60
70
Column Summary
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_MESSAGE_HOSPITAL_REF MESSAGE_NUMSEQ_NUMBER
Transferable ?
Mandatory ?
Update Rule :
Delete Rule :
Yes
Yes
Restricted
Restricted
Name Column
A child table of the RIB Hospital. Holds the elements from the<hospitalRef> nodes.
Description :
Table Name : RIB_MESSAGE_HOSPITAL_REF
20 August 2004 Page 13 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
LOCATION
MESSAGE_FAMILY
NEW_REASON_CODE
OLD_REASON_CODE
The MESSAGE_NUM of a record in the hospital to potentially update.
The collaboration (module) and e*Way (sub-module) of the publisher of thismessage.
The Message Family
The reason code this message in the hospital should be changed to.
The reason code this message originally went into hospital with.
Column Detail
40
50
60
70
Optional ? :No ; Varchar2 (8) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (60) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (10) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (10) ;() ; ; Uppercase ? :No ;
20 August 2004 Page 14 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RMRAlias :
MESSAGE_NUM references RIB_MESSAGE.MESSAGE_NUM
RMR_RMG_FK
Foreign Keys
Primary Key
MESSAGE_NUM
SEQ_NUMBER
Unique primary key, generated from RIB_MESSAGE_SEQ sequence.
Incrementing number for each record.
Column Detail
10
20
Optional ? :No ; Number (8, 0) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Number (2, 0) ;() ; ; Uppercase ? :No ;
MESSAGE_NUM
SEQ_NUMBER
NAME
VALUE
DETAIL1_NAME
DETAIL1_VALUE
DETAIL2_NAME
DETAIL2_VALUE
Column
NUMBER (8, 0)
NUMBER (2, 0)
VARCHAR2 (25)
VARCHAR2 (300)
VARCHAR2 (25)
VARCHAR2 (300)
VARCHAR2 (25)
VARCHAR2 (300)
Type
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NULL
NULL
NULL
NULL
Nulls ?Col.Seq.
10
20
30
40
50
60
70
80
Column Summary
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_MESSAGE_ROUTING_INFO MESSAGE_NUMSEQ_NUMBER
Transferable ?
Mandatory ?
Update Rule :
Delete Rule :
Yes
Yes
Restricted
Restricted
Name Column
A child table of the RIB Hospital. Holds the elements from the<routingInfo> nodes.
Description :
Table Name : RIB_MESSAGE_ROUTING_INFO
20 August 2004 Page 15 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
NAME
VALUE
DETAIL1_NAME
DETAIL1_VALUE
DETAIL2_NAME
DETAIL2_VALUE
Contains the RoutingInfo <name> element
Contains the RoutingInfo <value> element.
Contains the first RoutingInfoDetail <name> element.
Contains the first RoutingInfoDetail <value> element.
Contains the second RoutingInfoDetail <name> element.
Contains the second RoutingInfoDetail <value> element.
Column Detail
30
40
50
60
70
80
Optional ? :No ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (300) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (300) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :Yes ; Varchar2 (300) ;() ; ; Uppercase ? :No ;
20 August 2004 Page 16 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RSTAlias :
Primary Key
FAMILY
MAX_DETAILS_TO_PUBLISH
NUM_THREADS
MINUTES_TIME_LAG
The Message Family
How many details to include in a message before publishing it.
The number of threads to use when publishing. Also used to determine thethread value when publishing.
The number of minutes that a publishing application may wait before publishingan 'incomplete' business object create message.
Column Detail
10
20
30
40
Optional ? :No ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Number (6, 0) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Number (4, 0) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Number (4, 0) ;() ; ; Uppercase ? :No ;
FAMILY
MAX_DETAILS_TO_PUBLISH
NUM_THREADS
MINUTES_TIME_LAG
Column
VARCHAR2 (25)
NUMBER (6, 0)
NUMBER (4, 0)
NUMBER (4, 0)
Type
NOT NULL
NOT NULL
NOT NULL
NOT NULL
Nulls ?Col.Seq.
10
20
30
40
Column Summary
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_SETTINGS FAMILY
Name Column
Table resides in database, and only current implementation is for non-J2EE applications. Contains the message publishing aggregationconfiguration for each message family (Oracle Object interfaces only).
Description :
Table Name : RIB_SETTINGS
20 August 2004 Page 17 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
Display Title :
RTSAlias :
FAMILY references RIB_SETTINGS.FAMILY
FK_RIB_SETTINGS_FAMILY
Foreign Keys
Primary Key
FAMILY
TYPE
DO_DBMS_OUTPUT
The Message Family
The Message Type
Set to 'Y' if DBMS_OUTPUT is on, 'N' if not. Defaults to 'N'.
Column Detail
10
20
30
Optional ? :No ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (25) ;() ; ; Uppercase ? :No ;
Optional ? :No ; Varchar2 (1) ;() ; ; Uppercase ? :No ; Default Value :N ;
FAMILY
TYPE
DO_DBMS_OUTPUT
DO_LOG_OUTPUT
Column
VARCHAR2 (25)
VARCHAR2 (25)
VARCHAR2 (1)
VARCHAR2 (1)
Type
NOT NULL
NOT NULL
NOT NULL
NOT NULL
Nulls ?Col.Seq.
10
20
30
40
Column Summary
No
Storage
Index-organized ?
Volumes
Start Rows : End Rows :
PK_RIB_TYPE_SETTINGS FAMILYTYPE
Transferable ?
Mandatory ?
Update Rule :
Delete Rule :
Yes
Yes
Restricted
Restricted
Name Column
Table defines, on a per message family/ message type basis, whetherinformational and debugging log entries should be output using theDBMS_OUTPUT Oracle packages and/or written to a log file.
Description :
Table Name : RIB_TYPE_SETTINGS
20 August 2004 Page 18 ofTable Definition
Oracle Designer Report : cktci
19
Container : RIB 11.0 Version :
DO_LOG_OUTPUT
Set to 'Y' if Log to file is on, 'N' if not. Defaults to 'N'.
Column Detail
40
Optional ? :No ; Varchar2 (1) ;() ; ; Uppercase ? :No ; Default Value :N ;
Oracle Designer
TABLE DEFINITION
End of Report