Mobicents Profile Persistence

As of 1.0b1, Mobicents implements profile persistence.

Enabling Profile Persistence

Persistence is disabled by default. To enable it, edit the configuration file jboss-treecache-profile-service.xml. Uncomment the following section

      <attribute name="CacheLoaderClass">org.jboss.cache.loader.JDBCCacheLoader</attribute>
      <attribute name="CacheLoaderShared">true</attribute>
      <attribute name="CacheLoaderPreload">/</attribute>
      <attribute name="CacheLoaderFetchTransientState">false</attribute>
      <attribute name="CacheLoaderFetchPersistentState">true</attribute>
      <attribute name="CacheLoaderConfig">
         cache.jdbc.table.name=PersistentTreeCache
         cache.jdbc.table.create=true
         cache.jdbc.table.drop=false
         cache.jdbc.fqn.column=fqn
         cache.jdbc.fqn.type=varchar(255)
         cache.jdbc.node.column=node
         cache.jdbc.node.type=LONGVARBINARY
         cache.jdbc.parent.column=parent
         cache.jdbc.datasource=java:/DefaultDS
      </attribute>     

The configuration above points Mobicents to a datasource bound in JNDI at java:/DefaultDS. The table that will be used to store SLEE profiles is named PersistentTreeCache^?. Once you start Mobicents with the persistence configuration enabled, the server will automatically detect whether the PersistentTreeCache^? table exists. It will be created automatically if it does not exist.

Profile persistence is based on JBoss TreeCache^? Loaders, which support any JDBC data source, JDBC driver, berkleydb files and flat files.

Related forum discussion

If you have comments on this feature, post on the related forum discussion: http://forums.java.net/jive/thread.jspa?threadID=1406.

Known issues

• Running the batch of TCK tests - tests/profiles/creation fails with errors due to garbage left after some of the tests. Further investigation required. The problem does not occur when persistence is disabled.

-- Main.ivelin - 12 Sep 2005