Configuring JDBC provisioning lookup types and connections
Below are instructions for configuring JDBC provisioning lookup types and the connection to the TimesTen database.
Configuring JDBC provisioning lookup types
Sentinel comes with three JDBC-based provisioning service implementations: for subscriber data, promotion buckets, and home zones.
Subscriber data
To use the JDBC-based provisioning service implementation for subscriber data, in the provisioning GUI:
1 |
Select Sentinel ⇒ Feature Configuration from the menu. |
---|---|
2 |
Select Subscriber Data Lookup from the Feature dropdown. |
3 |
Click the Lookup Config tab. |
4 |
Set the Sentinel selection key scope (Network, Session Type, and so on) to correspond to the subscriber data records stored in TimesTen.
|
5 |
Change the Lookup type option to dbQuery, and click Save. |
Promotion buckets
To use the JDBC-based provisioning service implementation as the default option for promotion buckets, in the provisioning GUI:
1 |
Select Sentinel ⇒ Promotion Configuration from the menu. |
---|---|
2 |
Click the Config tab. |
3 |
Set the Sentinel selection key scope (Network, Session Type, and so on) to correspond to the promotion bucket data stored in TimesTen.
|
4 |
Change the Default data source option to dbquery, and click Save. |
To use the JDBC-based provisioning service implementation only for specific promotion buckets, in the provisioning GUI:
1 |
Select Sentinel ⇒ Promotion Configuration from the menu. |
---|---|
2 |
Click the Bucket Config tab. |
3 |
Set the Sentinel selection key scope (Network, Session Type, and so on) to correspond to the scope the promotion bucket configuration data is stored at. |
4 |
Select one of the existing bucket configurations from the list, or click Add New to create a new one. |
5 |
Change the Data source option to dbquery, and click Save. |
Home zones
To use the JDBC-based provisioning service implementation for home zones, in the provisioning GUI:
1 |
Select Sentinel ⇒ Feature Configuration from the menu. |
---|---|
2 |
Select Home Zone from the Feature dropdown. |
3 |
Click the Config tab. |
4 |
Set the Sentinel selection key scope (Network, Session Type, and so on) to correspond to the home zone zones stored in TimesTen.
|
5 |
Change the Zone lookup type option to dbQuery, and click Save. |
Configuring TimesTen JDBC connection (using Tomcat server)
If using any JDBC-based provisioning service implementations, you’ll need to configure JNDI entries in your servlet container:
1 |
Install the TimesTen native client on the machine where from REM will be run. |
---|---|
2 |
Copy |
3 |
Edit (or create) # Specify the path to the lib directory of the local TimesTen client install LD_LIBRARY_PATH=/opt/TimesTen/tt1121/lib export LD_LIBRARY_PATH # (Solaris 64bit only) # If running on Solaris 64bit, specify the -d64 flag to run Tomcat using the 64bit JVM # Otherwise, Tomcat won't be able to load the 64bit TimesTen libraries #CATALINA_OPTS="-d64" |
4 |
Edit <!-- ... --> <GlobalNamingResources> <!-- ... --> <Resource name="SentinelDataSource" auth="Container" type="javax.sql.DataSource" driverClassName="com.timesten.jdbc.TimesTenDriver" url="jdbc:timesten:client:sentinelCS" username="username" password="password" maxActive="50" maxIdle="30" maxWait="-1"/> </GlobalNamingResources> <!-- ... --> |
5 |
Edit (or create) <Context> <!-- For provisioning Subscriber Data records in TimesTen --> <ResourceLink name="jdbc/subscriberdata" global="SentinelDataSource" type="javax.sql.DataSource"/> <!-- For provisioning Promotion Buckets in TimesTen --> <ResourceLink name="jdbc/promotions" global="SentinelDataSource" type="javax.sql.DataSource"/> <!-- For provisioning HomeZone Zones in TimesTen --> <ResourceLink name="jdbc/homezone" global="SentinelDataSource" type="javax.sql.DataSource"/> </Context> |
6 |
Start/restart Tomcat. |