If you use a distributed database configuration, you can use this sheet to record your decisions about how the database tables will be distributed in the network.
If you use the standard process for installing and configuring Telecom Web Services Server, the scripts will assign default values that will meet your needs in most cases. However, you can use this worksheet if you require a non-default configuration.
The table lists all of the components that require database tables. The first line is provided an example. Use the table to store the database server host name (fully-qualified), port, database name, database alias, data source, and DDL file name. Reference this information during the installation and configuration process.
Component | Database server host name | Database name | Port | Database Alias | Data source | Data source JNDI name | DDL file name |
---|---|---|---|---|---|---|---|
Access Gateway | mydomain.example.com | AGDB | 50000 | AgDb | AgDataSource | jdbc/AGDB | ESBDbDb2.ddl |
Access Gateway | |||||||
Service Policy Manager (runtime) | |||||||
Service Policy Manager (console) | |||||||
Notification Management component Web service | |||||||
Address Masking component Web service | |||||||
Usage Record component Web service | |||||||
TWSS Administration Console | |||||||
Parlay X Call Notification over SIP/IMS | |||||||
Parlay X Presence over SIP/IMS | |||||||
Parlay X Terminal Status over SIP/IMS | |||||||
Parlay X Third Party Call over SIP/IMS | |||||||
Parlay X Payment (PostPaid) | |||||||
Parlay X Address List Manager over XCAP | |||||||
WAP Push over SMPP | |||||||
Parlay X SMS over SMPP | |||||||
Parlay X Terminal Location over MLP | |||||||
Parlay X Multimedia Messaging over MM7 | |||||||
Parlay X Terminal Status over Parlay | |||||||
Parlay X Terminal Location over Parlay | |||||||
Parlay X SMS over Parlay | |||||||
Parlay X Call Handling over Parlay | |||||||
Parlay X Call Notification over Parlay | |||||||
Parlay X Third Party Call over Parlay |