Configure Oracle WebLogic Communication Services Persistence Options

Configuring SIP Data Tier Partitions and Replicas 6-9 2. Start the SQLPlus application, connecting to the Oracle database in which you will create the required tables. Use the same username, password, and connect to the same database that you specified when configuring the JDBC driver in Section 6.4.4.1, Configure JDBC Resources . For example: sqlplus usernamepasswordconnect_identifier where connect_identifier connects to the database identified in the JDBC connection pool. 3. Execute the Oracle WebLogic Communication Services SQL script, callstate.sql: START callstate.sql 4. Exit SQLPlus: EXIT

6.4.5 Using Persistence Hints in SIP Applications

Oracle WebLogic Communication Services provides a simple API to provide hints as to when the SIP data tier should persist call state data. You can use the API to disable persistence for specific calls or SIP requests, or to persist data more frequently than the default setting at SIP dialog boundaries. To use the API, simply obtain a WlssSipApplicationSession instance and use the setPersist method to enable or disable persistence. Note that you can enable or disable persistence either to an RDBMS store, or to as geographically-redundant Oracle WebLogic Communication Services installation see Section 6.6, Using Geographically-Redundant SIP Data Tiers . For example, some SIP-aware load balancing products use the SIP OPTIONS message to determine if a SIP Server is active. To avoid persisting these messages to an RDBMS and to a geographically-redundant site, a Servlet might implement a doOptions method to echo the request and turn off persistence for the message, as shown in Example 6–6 . Example 6–6 Disabling RDBMS Persistence for Option Methods protected void doOptionsSipServletRequest req throws IOException { WlssSipApplicationSession session = WlssSipApplicationSession req.getApplicationSession; session.setPersistWlssSipApplicationSession.PersistenceType.DATABASE, false; session.setPersistWlssSipApplicationSession.PersistenceType.GEO_REDUNDANCY, false; req.createResponse200.send; }

6.5 Introducing Geo-Redundancy

Geo-Redundancy ensures uninterrupted transactions and communications for providers, using geographically-separated SIP server deployments. A primary site can process various SIP transactions and communications and upon determining a transaction boundary, replicate the state data associated with the transaction being processed, to a secondary site. Upon failure of the primary site, calls