The base subcomponents of Telecom Web Services Server require
several different database tables. You can configure your system so
that the database tables reside in a single, shared database or in
multiple databases. After you create your database or databases, the
tables are defined when you perform initial configuration using the First Steps script.
Most Telecom Web Services Server installations
use a shared or consolidated database configuration.
In this configuration, database tables for all Telecom Web Services Server subcomponents
are created in one database, typically called TWSSDB. Additionally,
the tables for the Parlay Connector is now also a part of the same
database. Multiple data sources are now provided for ease of modifying
to a distributed topology.
Alternatively, you can use a distributed database configuration
in which database tables for all Telecom Web Services Server subcomponents
are created in multiple database instances. Using this configuration
can improve performance and prevent bottlenecks when accessing the
database tables.
During the standard installation and configuration process, the First Steps script sets
up a shared database configuration by default.
The following tables list the names of the database instances and
other information for TWSS subcomponents using both the shared configuration
and the distributed configuration.
Shared configuration
In a shared or consolidated
configuration, database tables for the various subcomponents reside
in a single database commonly called TWSSDB. This database also can
include tables for the Parlay Connector, if you plan to deploy any
of the Parlay-based Web service implementations.
For
each component, the following table lists:
When you are configuring for a shared database, the BaseDbxxx.ddl file
creates database tables for all of the base components: Access Gateway, Service Policy Manager, TWSS Administration Console,
and Service Platform components.
Refer
to the topic Database tables for Web service implementations for
a list of the database tables that are required for the Web service implementations.
Table 1. Database tables for TWSS components (shared database configuration)Component |
Sample DB instance |
DDLs |
Database tables created |
Notes |
Access Gateway |
TWSSDB |
BaseDbDb2.ddl
BaseDbOra.ddl
|
TRANSACTIONS
NETWORKSTATISTICS
ATTACHMENT_CONTENTS
MESSAGELOG
TARGETLOG
SLADATA
|
For
Oracle databases, the following views are created: MSGLOG and NETWORKSTATISTICSVIEW. |
Service Policy Manager |
TWSSDB |
BaseDbDb2.ddl
BaseDbOra.ddl
|
REQUESTERS
SERVICES
OPERATIONS
POLICYTYPES
POLICIES
|
Stores policy data for the Web services. When
you deploy each service, an associated initialization (DDL) populates
the database tables. |
TWSS Administration Console |
TWSSDB |
BaseDbDb2.ddl
BaseDbOra.ddl
|
CONFIGPROPERTIES
|
Network Resources component Web service also
uses this database. |
Usage Record component Web service |
TWSSDB |
BaseDbDb2.ddl
BaseDbOra.ddl
|
USAGERECORDS
|
|
Notification Management component Web service |
TWSSDB |
BaseDbDb2.ddl
BaseDbOra.ddl
|
NOTIFICATIONS
CRITERIA
TARGET
|
Needed only when you deploy the Notification Management component Web service. |
Address Masking component Web service |
TWSSDB |
AddressMaskingDbDb2.ddl
AddressMaskingDbOra.ddl
|
TRANSACTIONIDIDENTIFIER
INPUTVALUE
OUTPUTVALUE
REQUESTER
INTERNALEXPIRYEXTERNALEXPIRYEXECUTECOUNT
|
|
Fault and Alarm component Web service |
TWSSDB |
None.
|
None.
|
Can be configured to use CEI, which uses a database. |
Parlay Connector |
TWSSDB |
ParlayConnectorDb2.ddl
ParlayConnectorOra.ddl
|
PUBLISHEDDATA
CFGPROPERTIES
KEYGENERATOR
SERVERPROPERTIES
EVENTRESOURCE
|
Needed only when you deploy Parlay-based Web
services Stores configuration data for the Parlay Connector and
the Parlay Administration Console.
|
Distributed configuration
In a distributed
configuration, database tables for the various subcomponents reside
in multiple databases.
The First Steps script creates tables for a single shared database that is shared by all of the TWSS components. If you prefer to use a distributed database configuration, you will need to configure the databases manually as described in the topic Migrating data in a distributed database configuration.
For
each component, the following table lists:
Table 2. Database tables for TWSS components (distributed database configuration)Component |
Sample DB instance |
DDLs |
Database tables created |
Notes |
Access Gateway |
AGDB, ATTACHDB |
ESBDbDb2.ddl
ESBDbOra.ddl
|
TRANSACTIONS
NETWORKSTATISTICS
ATTACHMENT_CONTENTS
MESSAGELOG
TARGETLOG
SLADATA
|
When creating a unique database
during the installation, you must define a corresponding data source
with a unique JNDI name. For
Oracle databases, the following views are created: MSGLOG and NETWORKSTATISTICSVIEW.
|
Service Policy Manager |
SPMDB |
SPMDbDb2.ddl
SPMDbOra.ddl
Note: If you are moving the Service Policy Manager database
tables after an initial installation, the tables contain policy data
that will also need to be moved.
|
REQUESTERS
SERVICES
OPERATIONS
POLICYTYPES
POLICIES
|
Stores policy data for the Web services. When
you deploy each service, an associated initialization (DDL) populates
the database tables. When creating a unique database
during the installation, you must define a corresponding data source
with a unique JNDI name.
|
TWSS Administration Console |
ADMINDB |
AdminDbDb2.ddl
AdminDbOra.ddl
Note: If you are moving the database table after using the First Steps script to
perform initial configuration, the table will contain configuration
data that also needs to be moved.
|
CONFIGPROPERTIES
|
When creating a unique database
during the installation, you must define a corresponding data source
with a unique JNDI name.
Network Resources component Web service also
uses this database.
|
Usage Record component Web service |
USAGEDB |
UsageDbDb2.ddl
UsageDbOra.ddl
|
USAGERECORDS
|
You can either create a unique database for
the usage record data or create the tables in a shared instance. When creating a unique database
during the installation, you must define a corresponding data source
with a unique JNDI name.
|
Address Masking component Web service |
AMDB |
AddressMaskingDbDb2.ddl
AddressMaskingDbOra.ddl
|
|
|
Fault and Alarm component Web service |
|
Not applicable |
Not applicable |
Can be configured to use CEI, which uses a database. |
Notification Management component Web service |
NMDB |
ServicePlatformDbDb2.ddl
notifymgmtDbDb2.ddl
ServicePlatformDbOra.ddl
notifymgmtDbOra.ddl
|
NOTIFICATIONS
CRITERIA
TARGET
|
Needed only when you deploy the Notification Management component Web service. |
Parlay Connector |
PARLAYDB |
ParlayConnectorDb2.ddl
ParlayConnectorOra.ddl
|
PUBLISHEDDATA
CFGPROPERTIES
KEYGENERATOR
SERVERPROPERTIES
EVENTRESOURCE
|
Needed only when you deploy Parlay-based Web
services Stores configuration data for the Parlay Connector and
the Parlay Administration Console.
|