Zoo2006-10-07_043Helsinki2005-10-15_16_019Somero2002_02Helsinki2005-10-15_16_042Saaristoleiri-Uto-2008_177Naginata Helsinki 2010-02-07 09playa06secret_552South.Africa.Roadtrip.2007-08_353Hannan-ja-Esan-haat.20100822.131652.703Kuortti.2010-06-26Nanbudo_WCh2006_076Pakkas03Pitkanen_076norge5oslo_169Saaristoleiri-Uto-2008_180Kuortti.2010-06-26Kuortti.2010-06-26Saaristoleiri 2009-08 34Kobe, Japan 2010-05-01Inujima, Japan 2010-04-30Jodo-Milano.2008-09_035italia2005-04_219Shiga, Japan 2010-04-18
Best before 23rd June

I will be soon out of date.

Openfire database integration changes

It seems that recently the way how database should be integrated for the use of the Openfire XMPP server, has changed.  The config file needs to have the additional settings but after they also need to be hand edited at the server settings page of the admin panel, thus the configuration file becomes like one below:

<?xml version="1.0" encoding="UTF-8"?>

<jive>
  <adminConsole>
    <port>9090</port>  
    <securePort>9091</securePort>
  </adminConsole>  
  <admin></admin>  
  <locale>en</locale>  
  <provider>
    <auth/>  
    <user/>  
    <group></group>
  </provider>  
  <jdbcProvider/>  
  <jdbcAuthProvider/>  
  <jdbcUserProvider/>  
  <jdbcGroupProvider></jdbcGroupProvider>  
  <log>
    <debug>
      <enabled>true</enabled>
    </debug>
  </log>  
  <connectionProvider>
    <className>org.jivesoftware.database.DefaultConnectionProvider</className>
  </connectionProvider>  
  <database>
    <defaultProvider>
      <driver>com.mysql.jdbc.Driver</driver>  
      <serverURL>jdbc:mysql://localhost:3306/openfire?useUnicode=true&amp;characterEncoding=UTF-8&amp;characterSetResults=UTF-8</serverURL>  
      <username>openfire</username>  
      <password>openfire</password>  
      <testSQL>select 1</testSQL>  
      <testBeforeUse>true</testBeforeUse>  
      <testAfterUse>true</testAfterUse>  
      <minConnections>5</minConnections>  
      <maxConnections>25</maxConnections>  
      <connectionTimeout>1.0</connectionTimeout>
    </defaultProvider>
  </database>  
  <setup>true</setup>
</jive>

The database properties are set to the following:

ofProperty values
namepropValue
admin.authorizedJIDsjuga@paazmaya.com
jdbcAuthProvider.passwordSQLSELECT password FROM users WHERE nickname = ? LIMIT 1
jdbcAuthProvider.passwordTypesha1
jdbcGroupProvider.allGroupsSQLSELECT title FROM groups ORDER BY title ASC
jdbcGroupProvider.descriptionSQLSELECT description FROM groups WHERE title = ?
jdbcGroupProvider.groupCountSQLSELECT COUNT(*) FROM groups
jdbcGroupProvider.loadMembersSQLSELECT A.nickname FROM users A, group_user B, groups C WHERE C.title = ? AND A.id = B.user AND B.group = C.id
jdbcGroupProvider.userGroupsSQLSELECT A.title FROM groups A, group_user B, users C WHERE A.id = B.group AND B.user = C.id AND C.nickname = ?
jdbcProvider.connectionStringjdbc:mysql://localhost:3306/tsuka_beta?user=tsuka_beta&password=tsuka_beta
jdbcProvider.drivercom.mysql.jdbc.Driver
jdbcUserProvider.allUsersSQLSELECT nickname FROM users ORDER BY nickname ASC
jdbcUserProvider.emailFieldemail
jdbcUserProvider.loadUserSQLSELECT nickname, email FROM users WHERE nickname = ? LIMIT 1
jdbcUserProvider.nameFieldnickname
jdbcUserProvider.searchSQLSELECT nickname FROM users WHERE
jdbcUserProvider.userCountSQLSELECT COUNT(*) FROM users
jdbcUserProvider.usernameFieldnickname
provider.admin.classNameorg.jivesoftware.openfire.admin.DefaultAdminProvider
provider.auth.classNameorg.jivesoftware.openfire.auth.JDBCAuthProvider
provider.group.classNameorg.jivesoftware.openfire.group.JDBCGroupProvider
provider.lockout.classNameorg.jivesoftware.openfire.lockout.DefaultLockOutProvider
provider.securityAudit.classNameorg.jivesoftware.openfire.security.DefaultSecurityAuditProvider
provider.user.classNameorg.jivesoftware.openfire.user.JDBCUserProvider
provider.vcard.classNameorg.jivesoftware.openfire.vcard.DefaultVCardProvider
xmpp.domainpaazmaya.com

Remember to make sure that the domain of the admin user matches to the domain of the server.

Time: 15/06/2009 22:46

QR code for paazio.nanbudo.fi