Commit a77b766d authored by Gaston Dombiak's avatar Gaston Dombiak Committed by gato

Changing name to Wildfire (initial work).

git-svn-id: http://svn.igniterealtime.org/svn/repos/messenger/trunk@3195 b35dd754-fafc-0310-a699-88a17e54d16e
parent e845e2ef
This diff is collapsed.
This diff is collapsed.
......@@ -4,14 +4,14 @@
- $Date$
-->
<!-- Resin 3.1.10+ configuration file for Jive Messenger site. Precondition: run 'ant jar'. -->
<!-- Resin 3.1.10+ configuration file for Wildfire site. Precondition: run 'ant jar'. -->
<resin xmlns="http://caucho.com/ns/resin" xmlns:resin="http://caucho.com/ns/resin/core">
<!-- Path to the messenger cvs project -->
<!-- Path to the wildfire cvs project -->
<system-property root="XXX EDIT THIS PATH XXX"/>
<system-property target="${root}\target"/>
<system-property messengerHome="${target}"/>
<system-property wildfireHome="${target}"/>
<log name="" level="info" path="stdout:" timestamp="%H:%M:%S "/>
<log name="com.caucho.java" level="config" path="stdout:" timestamp="%H:%M:%S "/>
......@@ -41,8 +41,8 @@
<!-- configures the default host, matching any host name -->
<host id="">
<!-- MESSENGER webapp -->
<web-app id="/messenger"
<!-- WILDFIRE webapp -->
<web-app id="/wildfire"
document-directory="${root}/src/web"
startup-mode="lazy"
temp-dir="${root}/src/web/WEB-INF/tmp"
......
......@@ -2,13 +2,13 @@
<html>
<head>
<title>Jive Messenger License: GPL</title>
<title>Wildfire License: GPL</title>
</head>
<body>
<pre>
Please see README.html for full licensing terms for Jive Messenger.
Please see README.html for full licensing terms for Wildfire.
---------------------------------------------------------------------
GNU GENERAL PUBLIC LICENSE
......
......@@ -2,7 +2,7 @@
<html>
<head>
<title>Jive Messenger Readme</title>
<title>Wildfire Readme</title>
<style type="text/css">
BODY {
font-size : 100%;
......@@ -49,7 +49,7 @@
<body>
<div class="header">
Jive Messenger Readme
Wildfire Readme
</div>
<p>
......@@ -64,14 +64,14 @@ Jive Messenger Readme
</table>
<p>
Thank you for downloading Jive Messenger!
Thank you for downloading Wildfire!
<p>
Jive Messenger is an instant messaging (IM) and groupchat server that uses the
Wildfire is an instant messaging (IM) and groupchat server that uses the
XMPP protocol. Start off by viewing the <a href="documentation/index.html">documentation</a>
that can be found in the "documentation" directory included with this distribution.
<p>
Further information can be found on the <a href="http://www.jivesoftware.org/messenger">
Jive Messenger website</a>.
Further information can be found on the <a href="http://www.jivesoftware.org/wildfire">
Wildfire website</a>.
<p><b>Changelog</b><p>
......@@ -80,33 +80,33 @@ last release.
<p><b>Support</b><p>
Free support is provided by the Jive Messenger community in the
Free support is provided by the Wildfire community in the
<a href="http://www.jivesoftware.org/forums">online forums</a>. Commercial
support (email and phone) from Jive Software is
<a href="http://www.jivesoftware.com/products/messenger">also available</a>.
<a href="http://www.jivesoftware.com/products/wildfire">also available</a>.
<p><b>License Agreements</b><p>
The Jive Messenger source code is governed by the GNU Public License (GPL), which
The Wildfire source code is governed by the GNU Public License (GPL), which
can be found in the <a href="LICENSE.html">LICENSE.html</a> file in this distribution.
Jive Messenger also contains Open Source software from third-parties.
Wildfire also contains Open Source software from third-parties.
Licensing terms for those components is specifically noted in the relevant source
files.<p>
Jive Messenger contains icons and images licensed from INCORS GmbH. All other
images are owned by Jive Software. All icons and images in Jive Messenger
Wildfire contains icons and images licensed from INCORS GmbH. All other
images are owned by Jive Software. All icons and images in Wildfire
are provided under the following license agreement:
<pre>
License Agreement
This is a legal agreement between You, the User of the Jive Messenger application
This is a legal agreement between You, the User of the Wildfire application
("The Software"), and Jive Software ("Jive Software"). By downloading the Software,
you agree to be bound by the terms of this agreement.
All ownership and copyright of the images and icons included in the Software
distribution remain the property of Jive Software and INCORS GmbH. Jive Software
grants to you a nonexclusive, non-sublicensable right to use the icons royalty-free
as part of Jive Messenger.
as part of Wildfire.
You may not lease, license or sub-license the icons, or a subset of the icons,
or any modified icons to any third party. You may not incorporate them into your
......
......@@ -2,7 +2,7 @@
<html>
<head>
<title>Jive Messenger Changelog</title>
<title>Wildfire Changelog</title>
<style type="text/css">
BODY {
font-size : 100%;
......@@ -65,9 +65,21 @@
<body>
<div class="header">
Jive Messenger Changelog
Wildfire Changelog
</div>
<p>
<b>2.4.0</b> -- December 14, 2005
<p>
<h2>New Features</h2>
<ul>
</ul>
<h2>Bug Fixes</h2>
<ul>
</ul>
<p>
<b>2.3.1</b> -- December 1, 2005
<p>
......@@ -126,7 +138,7 @@ Jive Messenger Changelog
<h2>Bug Fixes</h2>
<ul>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-322'>JM-322</a>] - Simplified admin account creation in setup. <b>(2 votes)</b></li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-446'>JM-446</a>] - Modified way admins were being specified in jive-messenger.xml</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-446'>JM-446</a>] - Modified way admins were being specified in wildfire.xml</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-442'>JM-442</a>] - Fixed shared group problem where contacts may incorrectly appear as offline.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-451'>JM-451</a>] - Members added to shared groups did not have correct presence subscription status in some cases.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-463'>JM-463</a>] - Couldn't add a contact to a group if the group matched the name of a shared group.</li>
......@@ -140,7 +152,7 @@ Jive Messenger Changelog
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-464'>JM-464</a>] - Server was ignoring room invitations when message contained many invitations.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-424'>JM-424</a>] - Replaced XMPPBootServlet with context listener. <b>(1 vote)</b></li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-443'>JM-443</a>] - "Launch Admin" button in launcher now works if only secure port is enabled.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-432'>JM-432</a>] - Jive Messenger was not handling different web types (flash, applets, etc.).</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-432'>JM-432</a>] - Wildfire was not handling different web types (flash, applets, etc.).</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-452'>JM-452</a>] - Invalid show value in Presence packet was breaking the admin console.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-455'>JM-455</a>] - Fixed concurrency error when getting room history.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-457'>JM-457</a>] - Stream header was not being added when sending some stream errors.</li>
......@@ -158,7 +170,7 @@ Jive Messenger Changelog
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-423'>JM-423</a>] - The returned size in bytes of offline messages of a user could be incorrect. Thanks to Conor Hayes.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-428'>JM-428</a>] - Remote users could broadcast messages faking local users.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-385'>JM-385</a>] - Fixed exception in Roster when contact has no username. Thanks to Nathan Palmer.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-389'>JM-389</a>] - Fixed jive-messengerd script to have unix line endings. <b>(1 vote)</b></li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-389'>JM-389</a>] - Fixed wildfired script to have unix line endings. <b>(1 vote)</b></li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-426'>JM-426</a>] - Fixed post-install script.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-390'>JM-390</a>] - Fixed sessions summary page to show its inline help.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-392'>JM-392</a>] - Fixed exception when removing the same item from the roster twice. Thanks to Nathan Palmer.</li>
......@@ -194,7 +206,7 @@ Jive Messenger Changelog
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-364'>JM-364</a>] - Reading XML using SAXParser was not thread safe. <b>(1 vote)</b></li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-366'>JM-366</a>] - Handling of offline messages was using a 0-12 hour format.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-368'>JM-368</a>] - Import and export users plugin now uses complete roster item JID instead of just the JID's node.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-371'>JM-371</a>] - Fixed messengerHome location code.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-371'>JM-371</a>] - Fixed wildfireHome location code.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-372'>JM-372</a>] - Fixed Packet.getError() to return correct XML.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-375'>JM-375</a>] - Fixed packet routing between components.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-376'>JM-376</a>] - The bin/extra directory was missing for the Unix builds.</li>
......@@ -353,7 +365,7 @@ Jive Messenger Changelog
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-229'>JM-229</a>] - Enabling sharing group did not select an option by default.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-238'>JM-238</a>] - Shared items could incorrectly stay in the roster.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-243'>JM-243</a>] - Sessions with no resource caused problems.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-244'>JM-244</a>] - Messenger can now send IQ packets to active but unavailable resources.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-244'>JM-244</a>] - Wildfire can now send IQ packets to active but unavailable resources.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-245'>JM-245</a>] - Updated the installer version, which fixes several bugs.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-248'>JM-248</a>] - Moved JiveGlobals to org.jivesoftware.util and made it more generic.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-249'>JM-249</a>] - Only set the sender of the packets when using ClientSessions.</li>
......@@ -464,7 +476,7 @@ Jive Messenger Changelog
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-10'>JM-10</a>] - LDAP can now be used for authentication and user information. <b>(3 votes)</b></li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-21'>JM-21</a>] - Created plugin to let users easily broadcast messages to groups. <b>(2 votes)</b></li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-22'>JM-22</a>] - Groups can now be automatically added to group member's rosters. <b>(10 votes)</b></li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-24'>JM-24</a>] - The lib directory can now be specified using the "messenger.lib.dir" Java system property.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-24'>JM-24</a>] - The lib directory can now be specified using the "wildfire.lib.dir" Java system property.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-39'>JM-39</a>] - History is now saved to the database in persistent group chat rooms.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-41'>JM-41</a>] - Added auto-archive process to clean-up unused group chat rooms.</li>
<li>[<a href='http://www.jivesoftware.org/issues/browse/JM-44'>JM-44</a>] - Added ability to cleanly shut down the server with a "stop" button in the admin console.</li>
......
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Jive Messenger Database Schema Guide</title>
<title>Wildfire Database Schema Guide</title>
<link href="style.css" rel="stylesheet" type="text/css">
</head>
<body>
<a name="top"></a>
<h1>Jive Messenger Database Schema Guide</h1>
<h1>Wildfire Database Schema Guide</h1>
<h2>Introduction</h2>
<p>
This document outlines the data type conventions and tables in the Jive
Messenger 2.1 database schema. Some information, like column indexes and foreign keys, is
Wildfire 2.1 database schema. Some information, like column indexes and foreign keys, is
omitted. For this, please read the individual schema of the database you're interested in.
<br>
</p>
<h2>Data Type Conventions</h2>
<p>
Date column type support varies widely across databases. Therefore,
Jive Messenger specially encodes dates as VARCHAR values. Each date is a Java long
Wildfire specially encodes dates as VARCHAR values. Each date is a Java long
value which is 0-padded to 15 characters. The long value is the internal
representation of Java Date objects, which can be obtained with code such as the
following:
......@@ -30,7 +30,7 @@ true.
</p>
<h2>Database Tables</h2>
<p>
Below is a description of each of the tables in the Jive Messenger
Below is a description of each of the tables in the Wildfire
database schema.
A <span class="primary-key">yellow row</span> denotes a primary key.
</p>
......@@ -149,7 +149,7 @@ Group)</th>
<tr class="primary-key">
<td>username</td>
<td>VARCHAR</td>
<td>32</td>
<td>100</td>
<td>User Name (Primary Key)</td>
</tr>
<tr class="primary-key">
......
This diff is collapsed.
......@@ -2,16 +2,16 @@
<html>
<head>
<title>Messenger: Overview - Jive Software</title>
<title>Wildfire: Overview - Jive Software</title>
<link type="text/css" rel="stylesheet" href="style.css">
</head>
<body>
<h1>Jive Messenger @version@</h1>
<h1>Wildfire @version@</h1>
<p>
Jive Messenger provides comprehensive group chat and instant
Wildfire provides comprehensive group chat and instant
messaging (IM) services using the XMPP protocol.
</p>
......@@ -20,19 +20,19 @@ messaging (IM) services using the XMPP protocol.
<ul>
<li>
<a href="install-guide.html">Installation Guide</a> -
How to install Jive Messenger.
How to install Wildfire.
</li>
<li>
<a href="database.html">Database Installation Guide</a> -
How to setup your database for use with Jive Messenger.
How to setup your database for use with Wildfire.
</li>
<li>
<a href="ssl-guide.html">SSL Guide</a> -
A guide to setting up Messenger's SSL secure socket support.
A guide to setting up Wildfire's SSL secure socket support.
</li>
<li>
<a href="ldap-guide.html">LDAP Guide</a> -
A guide to setting up Jive Messenger to work with LDAP user stores.
A guide to setting up Wildfire to work with LDAP user stores.
</li>
</ul>
......@@ -41,32 +41,32 @@ messaging (IM) services using the XMPP protocol.
<ul>
<li>
<a href="javadoc/index.html">JavaDocs</a> -
Jive Messenger API documentation.
Wildfire API documentation.
</li>
<li>
<a href="source-build.html">Building the Source</a> -
Instructions for downloading and compiling the Jive Messenger source code.
Instructions for downloading and compiling the Wildfire source code.
</li>
<li>
<a href="protocol-support.html">Protocol Support</a> -
Provides details on the XMPP support and JEPs that Jive Messenger implements.
Provides details on the XMPP support and JEPs that Wildfire implements.
</li>
<li>
<a href="plugin-dev-guide.html">Plugin Developer Guide</a> -
A guide to writing and installing plugins for Jive Messenger.
A guide to writing and installing plugins for Wildfire.
</li>
<li>
<a href="translator-guide.html">Translator Guide</a> -
Information for those interested in translating the admin console of Jive Messenger into other languages.
Information for those interested in translating the admin console of Wildfire into other languages.
</li>
<li>
<a href="database-guide.html">Database Schema Guide</a> -
A tour of the Jive Messenger database schema for developers and database administrators.
A tour of the Wildfire database schema for developers and database administrators.
</li>
</ul>
<p>
An active support community for Jive Messenger is available at
An active support community for Wildfire is available at
<a href="http://www.jivesoftware.org/forums/">http://www.jivesoftware.org/forums/</a>.
</p>
......
This diff is collapsed.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Jive Messenger LDAP Guide</title>
<title>Wildfire LDAP Guide</title>
<link href="style.css" rel="stylesheet" type="text/css">
</head>
<body>
<a name="top"></a>
<h1>Jive Messenger LDAP Guide</h1>
<h1>Wildfire LDAP Guide</h1>
<h2>Introduction</h2>
<p>
This document details how to configure your Jive Messenger installation to use
This document details how to configure your Wildfire installation to use
an external LDAP store when authenticating users and loading user profile information.
</p>
......@@ -27,22 +27,22 @@
</p>
<p>
By default, Jive Messenger stores all user data in a database and performs
By default, Wildfire stores all user data in a database and performs
authentication using database lookups. The LDAP module replaces that
functionality and allows Jive Messenger to:
functionality and allows Wildfire to:
<ul>
<li>Use a LDAP server to authenticate a user's identity.</li>
<li>Load user profile information from a LDAP directory.</li>
<li>Load group information from an LDAP directory.</li>
</ul>
<b>Note:</b> Jive Messenger treats the LDAP directory as read-only.
<b>Note:</b> Wildfire treats the LDAP directory as read-only.
</p>
<p>
This document will guide you through configuring LDAP support in Jive Messenger. These
This document will guide you through configuring LDAP support in Wildfire. These
instructions assume that you're a competent LDAP user, and that you're familiar
with Jive Messenger setup issues.
with Wildfire setup issues.
</p>
<h2>Configuration</h2>
......@@ -51,13 +51,13 @@
In order to configure your server to use LDAP:
<ol>
<li>
Stop Jive Messenger.
Stop Wildfire.
</li>
<li>Edit <tt>conf/jive-messenger.xml</tt> in your Jive Messenger installation folder as
<li>Edit <tt>conf/wildfire.xml</tt> in your Wildfire installation folder as
described below.
</li>
<li>
Restart Jive Messenger.
Restart Wildfire.
</li>
</ol>
</p>
......@@ -65,7 +65,7 @@
<h3>Editing the Config File</h3>
<p>
Open the configuration file <tt>conf/jive-messenger.xml</tt> from your Jive Messenger
Open the configuration file <tt>conf/wildfire.xml</tt> from your Wildfire
installation in your favorite
editor and add or change the following settings. Properties flagged with (<font color="red">
<b>*</b></font>)
......@@ -75,11 +75,11 @@
</p>
<ul>
<li>provider.user.className <font color="red"><b>*</b></font> -- set the value to
"org.jivesoftware.messenger.ldap.LdapUserProvider".</li>
"org.jivesoftware.wildfire.ldap.LdapUserProvider".</li>
<li>provider.auth.className <font color="red"><b>*</b></font> -- set the value to
"org.jivesoftware.messenger.ldap.LdapAuthProvider".</li>
"org.jivesoftware.wildfire.ldap.LdapAuthProvider".</li>
<li>provider.group.className <font color="red"><b>**</b></font> -- set the value to
"org.jivesoftware.messenger.ldap.LdapGroupProvider".</li>
"org.jivesoftware.wildfire.ldap.LdapGroupProvider".</li>
<li>ldap.host <font color="red"><b>*</b></font> -- LDAP server host; e.g. localhost or
machine.example.com, etc.</li>
<li>ldap.port -- LDAP server port number. If this property is not set, the default value is
......@@ -97,7 +97,7 @@
performed
with this account. The admin must be able to perform searches and load user records. The
user does
not need to be able to make changes to the directory, as Jive Messenger treats the
not need to be able to make changes to the directory, as Wildfire treats the
directory as read-only.
If this property is not set, an anonymous login to the server will be attempted.
</li>
......@@ -177,13 +177,13 @@
&lt;/ldap&gt;
&lt;provider&gt;
&lt;user&gt;
&lt;className&gt;org.jivesoftware.messenger.ldap.LdapUserProvider&lt;/className&gt;
&lt;className&gt;org.jivesoftware.wildfire.ldap.LdapUserProvider&lt;/className&gt;
&lt;/user&gt;
&lt;auth&gt;
&lt;className&gt;org.jivesoftware.messenger.ldap.LdapAuthProvider&lt;/className&gt;
&lt;className&gt;org.jivesoftware.wildfire.ldap.LdapAuthProvider&lt;/className&gt;
&lt;/auth&gt;
&lt;group&gt;
&lt;className&gt;org.jivesoftware.messenger.ldap.LdapGroupProvider&lt;/className&gt;
&lt;className&gt;org.jivesoftware.wildfire.ldap.LdapGroupProvider&lt;/className&gt;
&lt;/group&gt;
&lt;/provider&gt;
...
......@@ -209,7 +209,7 @@
<p><a name=""><h2>Custom Search Filter</h2></a></p>
<p>By default, Jive Messenger will load all objects under the baseDN that
<p>By default, Wildfire will load all objects under the baseDN that
have the attribute specified by <tt>ldap.usernameField</tt>. In the
case that the username field is set to "uid", the search for all users
would be "(uid=*)". However, there are cases when this logic does
......@@ -227,7 +227,7 @@
loading the list of all users or a username when loading a single user.</p>
<p>Some custom search filters may include reserved XML entities such as
"&". In that case, you must enter the search filter into the jive-messenger.xml
"&". In that case, you must enter the search filter into the wildfire.xml
file using CDATA:
<pre>&lt;searchFilter&gt;&lt;![CDATA[(&(sAMAccountName={0})(|(givenName=GEORGE)(givenName=admin)))]]&gt;&lt;/searchFilter&gt;</pre>
......@@ -285,13 +285,13 @@ clients that support the XMPP vCard extension. First, enable the provider:</p>
&lt;provider&gt;
...
&lt;vcard&gt;
&lt;className&gt;org.jivesoftware.messenger.ldap.LdapVCardProvider&lt;/className&gt;
&lt;className&gt;org.jivesoftware.wildfire.ldap.LdapVCardProvider&lt;/className&gt;
&lt;/vcard&gt;
...
&lt;/provider&gt;
</pre>
<p>Next, you must add mappings between LDAP fields and vCard fields in the jive-messenger.xml file.
<p>Next, you must add mappings between LDAP fields and vCard fields in the wildfire.xml file.
The vcard attributes are configured by adding an attrs="attr1,attr2" attribute to the vcard
elements. Arbitrary text can be used for the element values as well as MessageFormat style
placeholders for the ldap attributes. For example, if you wanted to map the LDAP attribute
......@@ -349,8 +349,8 @@ clients that support the XMPP vCard extension. First, enable the provider:</p>
<p>
<b>Can I create new users through Jive Messenger when using LDAP?</b>
<ul>No, Jive Messenger treats LDAP directories as read-only. Therefore, it's
<b>Can I create new users through Wildfire when using LDAP?</b>
<ul>No, Wildfire treats LDAP directories as read-only. Therefore, it's
not possible to create or edit users through the application.</ul>
<b>Why is the list of usernames not sorted in the admin console when using LDAP?</b>
......@@ -372,7 +372,7 @@ clients that support the XMPP vCard extension. First, enable the provider:</p>
</ol>
You can also enable debugging to get more information from the LDAP module. To
do this, add &lt;log&gt;&lt;debug&gt;&lt;enabled&gt;true&lt;/enabled&gt;&lt;/debug&gt;&lt;/log&gt;
to your <tt>conf/jive_messenger.xml</tt> file. Log statements will be written
to your <tt>conf/wildfire.xml</tt> file. Log statements will be written
to the <tt>logs/debug.log</tt> file.
</ul>
......
......@@ -2,27 +2,27 @@
<html>
<head>
<title>Jive Messenger Plugin Guide</title>
<title>Wildfire Plugin Guide</title>
<link href="style.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Jive Messenger Plugin Developer Guide</h1>
<h1>Wildfire Plugin Developer Guide</h1>
<a name="top"></a>
<h2>Introduction</h2>
<p>
Plugins enhance the functionality of Jive Messenger. This document is a
Plugins enhance the functionality of Wildfire. This document is a
developer's guide for creating plugins.
</p>
<h2>Structure of a Plugin</h2>
<p>
Plugins live in the <tt>plugins</tt> directory of <tt>messengerHome</tt>. When a plugin
Plugins live in the <tt>plugins</tt> directory of <tt>wildfireHome</tt>. When a plugin
is deployed as a JAR or WAR file, it is automatically expanded into a directory. The files in a
plugin directory are as follows:
</p>
......@@ -46,7 +46,7 @@ plugin directory are as follows:
</fieldset>
<p>The <tt>web</tt> directory exists for plugins that need to add content
to the Jive Messenger Admin Console. Further details are below.</p>
to the Wildfire Admin Console. Further details are below.</p>
<p>
The <tt>plugin.xml</tt> file specifies the main Plugin class. A sample
......@@ -88,8 +88,8 @@ file might look like the following:
<li>date -- the date the plugin was released. The date must be in the form MM/dd/yyyy, such
as 07/15/2005.</li>
<li>url -- a URL where additional information about the plugin is available.</li>
<li>minServerVersion -- the minimum version of Jive Messenger required
to run the plugin (supported by Jive Messenger 2.1.2 and later). If the
<li>minServerVersion -- the minimum version of Wildfire required
to run the plugin (supported by Wildfire 2.1.2 and later). If the
server version is less than the required value, the plugin will not be started.</li>
<li>parentPlugin -- the name of the parent plugin (given as "foo" for the "foo.jar" plugin).
When a plugin has a parent plugin, the parent plugin's class loader will be used instead
......@@ -107,8 +107,8 @@ end-users (all placed in the main plugin directory):
</ul>
<p>Your plugin class must be implement the
<tt><a href="javadoc/org/jivesoftware/messenger/container/Plugin.html">Plugin</a></tt>
interface from the <a href="javadoc/index.html">Jive Messenger API</a> as
<tt><a href="javadoc/org/jivesoftware/wildfire/container/Plugin.html">Plugin</a></tt>
interface from the <a href="javadoc/index.html">Wildfire API</a> as
well as have a default (no argument) contructor. The Plugin interface has
methods for initializing and destroying the plugin.
</p>
......@@ -118,13 +118,13 @@ methods for initializing and destroying the plugin.
<pre class="java">
package org.example;
import org.jivesoftware.messenger.container.Plugin;
import org.jivesoftware.messenger.container.PluginManager;
import org.jivesoftware.wildfire.container.Plugin;
import org.jivesoftware.wildfire.container.PluginManager;
import java.io.File;
/**
* A sample plugin for Jive Messenger.
* A sample plugin for Wildfire.
*/
public class ExamplePlugin implements Plugin {
......@@ -151,7 +151,7 @@ are a several steps to accomplishing this:
<li>JSP files must be compiled and put into the classpath of the
plugin. A <tt>web.xml</tt> file containing the compiled JSP
servlet entries must be put into the <tt>web/</tt> directory
of the plugin. <i>Note:</i> the Jive Messenger build script
of the plugin. <i>Note:</i> the Wildfire build script
can assist with compiling JSPs and creating the web.xml. This
is detailed below.
</li>
......@@ -196,7 +196,7 @@ the existing id attribute values in your own <tt>&lt;adminconsole&gt;</tt> defin
<h3>Admin Console Best Practices</h3>
There are several best practices to consider when making changes to
the Jive Messenger admin console via a plugin. The general theme is
the Wildfire admin console via a plugin. The general theme is
that plugins should integrate seamlessly:
<ul>
......@@ -209,14 +209,14 @@ that plugins should integrate seamlessly:
<li>Try to match the UI of the existing admin console in your custom
plugin pages.
<li>There is no need to create an admin console entry to show plugin
meta-data. Instead, let Jive Messenger inform the user about which
meta-data. Instead, let Wildfire inform the user about which
plugins are installed and provide plugin management.
</ul>
<h3>Writing Pages for the Admin Console</h3>
<p>
Jive Messenger uses the <a href="http://www.opensymphony.com/sitemesh/" target="_blank">Sitemesh</a>
Wildfire uses the <a href="http://www.opensymphony.com/sitemesh/" target="_blank">Sitemesh</a>
framework to decorate pages in the admin console. A globally-defined decorator is applied to
each page in order to render the final output, as in the following diagram:</p>
<br>
......@@ -260,10 +260,10 @@ The following HTML snippet demonstrates a valid page:
</pre>
</fieldset>
<h2>Using the Jive Messenger Build Script</h2>
<h2>Using the Wildfire Build Script</h2>
<p>
The Jive Messenger build script will help you build and develop plugins. It
The Wildfire build script will help you build and develop plugins. It
looks for plugin development directories in the following format:
</p>
......@@ -307,19 +307,19 @@ process.</p>
<h2>Implementing Your Plugin</h2>
<p>Plugins have full access to the Jive Messenger API. This provides a tremendous
<p>Plugins have full access to the Wildfire API. This provides a tremendous
amount of flexibility for what plugins can accomplish. However, there are several integration
points that are the most common:
<ol>
<li>Register a plugin as a <a href="javadoc/org/jivesoftware/messenger/Component.html">Component</a>.
<li>Register a plugin as a <a href="javadoc/org/jivesoftware/wildfire/Component.html">Component</a>.
Components receive all packets addressed to a particular sub-domain. For example,
<tt>test_component.example.com</tt>. So, a packet sent to <tt>joe@test_component.example.com</tt> would
be delivered to the component. Note that the sub-domains defined as components are unrelated to DNS entries
for sub-domains. All XMPP routing at the socket level is done using the primary server domain (example.com in the
example above); sub-domains are only used for routing within the XMPP server.
<li>Register a plugin as an <a href="javadoc/org/jivesoftware/messenger/IQHandler.html">IQHandler</a>. IQ handlers respond to IQ packets with a particular element name and
<li>Register a plugin as an <a href="javadoc/org/jivesoftware/wildfire/IQHandler.html">IQHandler</a>. IQ handlers respond to IQ packets with a particular element name and
namespace. The following code snippet demonstrates how to register an IQHandler:
<pre>
......@@ -328,14 +328,14 @@ points that are the most common:
iqRouter.addHandler(myHandler);
</pre>
<li>Register a plugin as a <a href="javadoc/org/jivesoftware/messenger/interceptor/PacketInterceptor.html">
<li>Register a plugin as a <a href="javadoc/org/jivesoftware/wildfire/interceptor/PacketInterceptor.html">
PacketInterceptor</a> to receive all packets being sent through the system and
optionally reject them. For example, an interceptor could reject all messages that contained
profanity or flag them for review by an administrator.</li>
<li>You can store persistent plugin settings as Jive Messenger properties using the
<li>You can store persistent plugin settings as Wildfire properties using the
JiveGlobals.getProperty(String) and JiveGlobals.setProperty(String, String) methods. Make
your plugin a property listener to listen for changes to its properties by implementing the
<tt>org.jivesoftware.messenger.event.PropertyEventListener</tt> method.
<tt>org.jivesoftware.wildfire.event.PropertyEventListener</tt> method.
You can register your plugin as a listener using the PropertyEventDispatcher.addListener(PropertyEventListener)
method. Be sure to unregister your plugin as a listener in your plugin's destroyPlugin() method.
......@@ -347,15 +347,15 @@ points that are the most common:
<b>Can I deploy a plugin as a directory instead of a JAR?</b>
<p>No, all plugins must be deployed as JAR or WAR files. When a JAR or WAR is not present for the plugin,
Jive Messenger assumes that the file has been deleted and that the users wants to destroy the plugin,
Wildfire assumes that the file has been deleted and that the users wants to destroy the plugin,
so it also deletes the directory.</p>
<b>What license agreement are plugins subject to?</b>
<p>Because Jive Messenger is released under the Open Source GPL license, any plugins developed
<p>Because Wildfire is released under the Open Source GPL license, any plugins developed
must also be released under the GPL or a compatible Open Source license. It is a
violation of the license agreement to create plugins that are not Open Source. Please visit
<a href="http://www.jivesoftware.com/products/messenger/">Jive Software</a> if you need different
licensing terms for Jive Messenger, including the right to create commercial plugins.</p>
<a href="http://www.jivesoftware.com/products/wildfire/">Jive Software</a> if you need different
licensing terms for Wildfire, including the right to create commercial plugins.</p>
<br><br>
......
......@@ -2,7 +2,7 @@
<html>
<head>
<title>Jive Messenger Protocol Support</title>
<title>Wildfire Protocol Support</title>
<link href="style.css" rel="stylesheet" type="text/css">
<style type="text/css">
.supported { background-color:#D0FFCB }
......@@ -13,19 +13,19 @@
<body>
<h1>Jive Messenger Protocol Support</h1>
<h1>Wildfire Protocol Support</h1>
<a name="top"></a>
<p>A major goal of the Jive Messenger project is to provide full support for the
<p>A major goal of the Wildfire project is to provide full support for the
<acronym title="Extensible Messaging and Presence Protocol">XMPP</acronym>
specifications defined by <a href="http://www.xmpp.org/specs/rfc3920.html">RFC 3920</a> and
<a href="http://www.xmpp.org/specs/rfc3921.html">RFC 3921</a>. In addition to full
XMPP support, Jive Messenger also provides support for numerous extensions to XMPP
XMPP support, Wildfire also provides support for numerous extensions to XMPP
that are defined through the
<acronym title="Jabber Enhancement Proposals">JEP</acronym> process at
<a href="http://www.jabber.org">Jabber.org</a>. This document provides a
summary of that protocol support and is updated for every Jive Messenger
summary of that protocol support and is updated for every Wildfire
release.</p>
<p>This document is broken down into the following sections:</p>
......@@ -120,7 +120,7 @@ Suite</a>.</p>
<a name="jeps"></a>
<h2>List of JEPs Supported</h2>
<p>The table below lists all JEPs supported by Jive Messenger and indicates which JEPs are part of the
<p>The table below lists all JEPs supported by Wildfire and indicates which JEPs are part of the
<a href="#basic">Basic</a> or <a href="#intermediate">Intermediate</a> Protocol Suites listed above.
JEPs that only require client-side support are omitted.</p>
......@@ -190,15 +190,15 @@ JEPs that only require client-side support are omitted.</p>
<a name="rfc3920"></a>
<h2>Notes on RFC 3920: XMPP Core</h2>
<p>Jive Messenger has full support for the XMPP Core specification (RFC 3920), <b>except</b> for the items listed below:
<p>Wildfire has full support for the XMPP Core specification (RFC 3920), <b>except</b> for the items listed below:
<ul>
<li><b>TLS</b> (<a href="http://www.xmpp.org/specs/rfc3920.html#tls">RFC3920.5</a>) -- Jive
Messenger provides support for client-to-server (c2s) TLS streams as defined in the RFC, but does not currently
Wildfire provides support for client-to-server (c2s) TLS streams as defined in the RFC, but does not currently
provide support for TLS between servers (s2s).</li>
<li><b>SASL</b> (<a href="http://www.xmpp.org/specs/rfc3920.html#sasl">RFC33920.6</a>) --
Jive Messenger provides support for client-to-server (c2s) SASL authentication, but does not currently
Wildfire provides support for client-to-server (c2s) SASL authentication, but does not currently
provide support for SASL between servers (s2s).</li>
</ul>
<br>
......@@ -206,7 +206,7 @@ JEPs that only require client-side support are omitted.</p>
<a name="rfc3921"></a>
<h2>Notes on RFC 3921: XMPP IM</h2>
<p>Jive Messenger has full support for the XMPP IM specification (RFC 3921), <b>except</b> for the item listed below:
<p>Wildfire has full support for the XMPP IM specification (RFC 3921), <b>except</b> for the item listed below:
<ul>
<li><b>Privacy Lists</b> (<a href="http://www.xmpp.org/specs/rfc3921.html#privacy">RFC3921.10</a>) </li>
......@@ -218,9 +218,9 @@ JEPs that only require client-side support are omitted.</p>
[<a name="fn1">1</a>] Some requirements of <u>JEP-0117: Intermediate IM Protocol Suite</u> do not pertain to servers.
<br>
[<a name="fn2">2</a>] The entity capabilities JEP is primarily for clients to implement. However, Jive Messenger does not support an optional server extensions defined by the JEP.
[<a name="fn2">2</a>] The entity capabilities JEP is primarily for clients to implement. However, Wildfire does not support an optional server extensions defined by the JEP.
<br>
[<a name="fn3">3</a>] Support for <u>JEP-0055: Jabber Search</u> is provided by the <a href="http://www.jivesoftware.org/messenger/plugins.jsp">Search plugin</a>.
[<a name="fn3">3</a>] Support for <u>JEP-0055: Jabber Search</u> is provided by the <a href="http://www.jivesoftware.org/wildfire/plugins.jsp">Search plugin</a>.
<br>
</body>
......
......@@ -2,7 +2,7 @@
<html>
<head>
<title>Jive Messenger Source Instructions</title>
<title>Wildfire Source Instructions</title>
<link href="style.css" rel="stylesheet" type="text/css">
<style type="text/css">
.code {
......@@ -30,14 +30,14 @@
<body bgcolor="#ffffff">
<h1>Jive Messenger Source Instructions</h1>
<h1>Wildfire Source Instructions</h1>
<p>
This document provides detailed information for developers that wish to
compile and make changes to the Jive Messenger source code.
compile and make changes to the Wildfire source code.
Use of the source code is governed by the GPL or the commercial license
you purchased for the codebase from Jive Software.
<b>If Jive Messenger
<b>If Wildfire
source is embedded into another application, that application must also
be released under the Open Source GPL license (unless you have a commercial OEM license
in place with Jive Software). Please see the license agreement
......@@ -48,21 +48,21 @@ the source, and that source is governed by the license given to it by its author
<p>For additional developer resources, please visit:
<a href="http://www.jivesoftware.org">
http://www.jivesoftware.org</a>. The Jive Messenger build process is based on Ant. Visit the
http://www.jivesoftware.org</a>. The Wildfire build process is based on Ant. Visit the
<a href="http://ant.apache.org/">Ant website</a>
for more information. There is no need to download and install Ant - a version of it is included
in this distribution.
<p>
This documentation is divided into three sections:
<ol>
<li> <a href="#source">Source</a> -- get te Jive Messenger source code.
<li> <a href="#setup">Setup</a> -- how to setup your environment for Jive Messenger development.
<li> <a href="#source">Source</a> -- get te Wildfire source code.
<li> <a href="#setup">Setup</a> -- how to setup your environment for Wildfire development.
<li> <a href="#tasks">Build tasks</a> -- tasks that can be performed using the build program.
</ol>
<p><a name="source"><b><font color="#0066cc">1.</font> Get the Jive Messenger Source</b></a><p>
<p><a name="source"><b><font color="#0066cc">1.</font> Get the Wildfire Source</b></a><p>
You can get the Jive Messenger source code by downloading a source distribution or
You can get the Wildfire source code by downloading a source distribution or
by checking out the source code from CVS. Instructions for both options can
be found on the <a href="http://www.jivesoftware.org/source.jsp">source page</a>.
......@@ -71,7 +71,7 @@ be found on the <a href="http://www.jivesoftware.org/source.jsp">source page</a>
Getting your machine ready for development requires a few steps. Wherever
possible, instructions are provided for both Unix/Linux and Windows users.
<p>
<b><a name="javaSetup">Configure Java for Jive Messenger</a></b>
<b><a name="javaSetup">Configure Java for Wildfire</a></b>
<ul>
Java 5 (JDK 1.5) must be installed and setup on your machine. To test the installation,
open a shell in a Unix or a MS-DOS prompt in Windows. Check your version of
......@@ -79,7 +79,7 @@ possible, instructions are provided for both Unix/Linux and Windows users.
If Java isn't installed, download a copy from the
<a href="http://java.sun.com/">Java website</a>.
<p>
<font color="red">Important!</font> -- the Jive Messenger build tool needs to know
<font color="red">Important!</font> -- the Wildfire build tool needs to know
where Java is installed on your system. You must configure the "JAVA_HOME"
environment variable to point to the correct directory. Instructions on
how to set this variable for various platforms are as follows:
......@@ -142,7 +142,7 @@ possible, instructions are provided for both Unix/Linux and Windows users.
<p><b><a name="ant">Install the Ant Build Tool</a></b><p>
The Jive Messenger build process uses Ant, so that tool must be installed
The Wildfire build process uses Ant, so that tool must be installed
and configured on your computer. First download Ant from:
<a href="http://ant.apache.org/">http://ant.apache.org</a>. Next, follow
the <a href="http://ant.apache.org/manual/installlist.html">installation instructions</a>.
......@@ -161,21 +161,21 @@ chmod u+x ant
</td></table>
<p>
Now, invoke the build tool to compile the Jive Messenger source code
Now, invoke the build tool to compile the Wildfire source code
<p>
Windows:<span class="code"> ant <br> </span><br clear="left">
Unix/Linux:<span class="code"> ./ant </span>
<p>
If the build tool is invoked correctly and Jive Messenger compiles, you've correctly
configured your copy of the Jive Messenger source distribution.
If the build tool is invoked correctly and Wildfire compiles, you've correctly
configured your copy of the Wildfire source distribution.
</ul>
<p><b>Finished!</b><p>
<ul>
If you've gotten this far, you've finished setting up the Jive Messenger source
If you've gotten this far, you've finished setting up the Wildfire source
distribution. Now, read below to learn about all of the tasks that you can perform
with the build tool.
</ul>
......@@ -185,7 +185,7 @@ with the build tool.
<p><b><a name="tasks"><font color="#0066cc">3.</font> Build Tasks</a></b><p>
The list of build tasks is below. All build commands should be
run from the "build" directory of your Jive Messenger distribution.
run from the "build" directory of your Wildfire distribution.
<br><br>
......@@ -233,8 +233,8 @@ Equivalent of calling "ant <a href="#jar">jar</a> javadoc".
<p><i>Description:</i></p>
Builds Jive Messenger into the <tt>target</tt> directory. You can then launch
Jive Messenger using the scripts in <tt>target/bin/</tt>.
Builds Wildfire into the <tt>target</tt> directory. You can then launch
Wildfire using the scripts in <tt>target/bin/</tt>.
<p>[<a href="#tasks">return to task list</a>]
</ul>
......
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Jive Messenger SSL Guide</title>
<title>Wildfire SSL Guide</title>
<link type="text/css" rel="stylesheet" href="style.css">
</head>
<body>
<a name="top"></a>
<h1>Jive Messenger SSL Guide</h1>
<h1>Wildfire SSL Guide</h1>
<h2>Introduction</h2>
<p>
This document outlines how to customize the SSL support in Jive Messenger.
This document outlines how to customize the SSL support in Wildfire.
<font color="red"><b>Important note:</b></font>
because Jive Messenger ships with self-signed certificates, most users can
because Wildfire ships with self-signed certificates, most users can
use the default configration and do not need to change the SSL environment. You should only
attempt to change the SSL settings if it's required for your deployment.</p>
<p>Jive Messenger's SSL support is built using the standard Java security
<p>Wildfire's SSL support is built using the standard Java security
SSL implementation (javax.net.ssl.SSLServerSocket). In this document, we will
describe how use the standard JDK 1.5 tools to accomplish these tasks.
</p>
......@@ -74,11 +74,11 @@ record keeping, and costs).
<h2>Sun JDK 1.5 security tools</h2>
<p>
The Sun JDK (version 1.5.x) ships with all the security tools you need
to configure SSL with Jive Messenger. The most important is the
to configure SSL with Wildfire. The most important is the
<tt>keytool</tt> located in the <tt>JAVA_HOME/bin directory</tt> of the
JDK. Sun JVMs persist keystores and truststores on the filesystem as
encrypted files. The <tt>keytool</tt> is used to create, read, update,
and delete entries in these files. Jive Messenger ships with a self-signed
and delete entries in these files. Wildfire ships with a self-signed
"dummy" certificate designed for initial evaluation testing. You will need
to adjust the default configuration for most deployments.
</p>
......@@ -87,9 +87,9 @@ In order to configure SSL on your server you need complete the
following tasks:
</p>
<ol>
<li>Decide on your Jive Messenger server's domain.</li>
<li>Decide on your Wildfire server's domain.</li>
<li>Create a self-signed SSL server certificate for your server
domain. Note: you may already have one if your Jive Messenger server
domain. Note: you may already have one if your Wildfire server
domain matches an existing web domain with SSL.
If so, you can skip to step 4.</li>
<li>[Optional] Have a certificate authority (CA) certify the SSL
......@@ -105,12 +105,12 @@ generated in step 2, the certificate is already imported and you can
skip this step.</li>
<li>Remove default certificates from the keystore.</li>
<li>Import client certificates into the truststore.</li>
<li>Adjust the Messenger configuration with proper keystore and
<li>Adjust the Wildfire configuration with proper keystore and
truststore settings.</li>
</ol>
<h3>1. Decide on a Server Domain</h3>
<p>
The Messenger server domain should match the host name of the server;
The Wildfire server domain should match the host name of the server;
for example, "example.com". Your user accounts will have addresses with
the format "user@example.com" like email addresses. We'll assume
the domain is "example.com" for the rest of the examples.
......@@ -119,7 +119,7 @@ the domain is "example.com" for the rest of the examples.
<p>
In order to create a self-signed server certificate go to the command
line and change directories to the <tt>resources/security</tt>
directory of your Jive Messenger installation. You should see the default
directory of your Wildfire installation. You should see the default
<tt>keystore</tt> and <tt>truststore</tt> files. First, you should
change the default keystore
password:
......@@ -194,9 +194,9 @@ Now import each certificate using the keytool:
</p>
<p><tt>keytool -import -keystore truststore -alias user_name -file
certificate_file</tt></p>
<h3>7. Configure Messenger</h3>
<h3>7. Configure Wildfire</h3>
<p>
Open the Jive Messenger Admin Console in your favorite
Open the Wildfire Admin Console in your favorite
browser and add or change the following system properties:
</p>
<ul>
......@@ -205,15 +205,15 @@ browser and add or change the following system properties:
5223 for XMPP)</li>
<li>xmpp.socket.ssl.storeType -- the store type used ("JKS" is
the Sun Java Keystore format used by the JDK keytool). If this property is
not defined, Messenger will assume a value of "jks".</li>
not defined, Wildfire will assume a value of "jks".</li>
<li>xmpp.socket.ssl.keystore -- the location of the keystore file
relative to your Jive Messenger installation root directory. You can leave this property
relative to your Wildfire installation root directory. You can leave this property
blank to use the default keystore.</li>
<li>xmpp.socket.ssl.keypass -- the keystore/key password you
changed in step 2.</li>
<li>xmpp.socket.ssl.truststore -- leave blank to not use a
truststore, otherwise the location of the truststore file relative to
your Jive Messenger installation root directory.</li>
your Wildfire installation root directory.</li>
<li>xmpp.socket.ssl.trustpass -- the truststore/key password you
changed in step 6.</li>
</ul>
......
......@@ -2,24 +2,24 @@
<html>
<head>
<title>Jive Messenger Translator Guide</title>
<title>Wildfire Translator Guide</title>
<link href="style.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Jive Messenger Translator Guide</h1>
<h1>Wildfire Translator Guide</h1>
<a name="top"></a>
<h2>Introduction</h2>
<p>
The Jive Messenger admin console can be easily translated into other languages. This document
The Wildfire admin console can be easily translated into other languages. This document
provides instructions for those that wish to make translations.
</p>
<p>
All text in the Jive Messenger admin console is stored in a resource
All text in the Wildfire admin console is stored in a resource
bundle. A resource bundle is a file containing key/value pairs. Words and phrases are
represented using keys. The correct values are retrieved based on locale settings
(English values are used for English locales, French values for French locales, etc).
......@@ -45,25 +45,25 @@ renaming the file, then translating its contents.</p>
<h2>Construct a Resource Bundle</h2>
<p>To start, make a copy of the default (English) locale file "messenger_i18n.properties".
It can be found in the <tt>resources\i18n</tt> directory of your Jive Messenger
<p>To start, make a copy of the default (English) locale file "wildfire_i18n.properties".
It can be found in the <tt>resources\i18n</tt> directory of your Wildfire
installation. Note: the files found in <tt>resources\i18n</tt> are copies of the
real resource bundles used by the application (the real resource bundles are contained
in the messenger.jar file). Editing the resource files in the <tt>resources\i18n</tt>
directory will not affect your running copy of Jive Messenger.</p>
in the wildfire.jar file). Editing the resource files in the <tt>resources\i18n</tt>
directory will not affect your running copy of Wildfire.</p>
<p>Next, you'll need to rename the file to match the locale that you're making a
translation for. The syntax of the name is "messenger_i18n_[lang]_[country].properties".
translation for. The syntax of the name is "wildfire_i18n_[lang]_[country].properties".
However, the country code should be used in most cases. For example, the German resource
bundle should be named "messenger_i18n_de.properties" because
bundle should be named "wildfire_i18n_de.properties" because
"de" is the language code for German. For French, the file would be called
"messenger_i18n_fr.properties". A list of language codes can
"wildfire_i18n_fr.properties". A list of language codes can
be found at:
<a href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt"
target="_new">http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt</a>.
Some locales require a combination of language and country code. For example
simplified Chinese would have the name "messenger_i18n_zh_CN.properties"
while traditional Chinese would have the name "messenger_i18n_zh_TW.properties".</p>
simplified Chinese would have the name "wildfire_i18n_zh_CN.properties"
while traditional Chinese would have the name "wildfire_i18n_zh_TW.properties".</p>
<h2>Translate the Resource Bundle</h2>
......@@ -80,7 +80,7 @@ use the "native2ascii" tool (bundled with Java) to convert international
characters to the ASCII format. To use the native2ascii tool:</p>
<pre>
native2ascii -encoding XXX my_translation.properties messenger_i18n_YY.properties
native2ascii -encoding XXX my_translation.properties wildfire_i18n_YY.properties
^ ^
input file output file
</pre>
......@@ -94,21 +94,21 @@ document. For example, if you created your translation using UTF-8 as your encod
you are making a Simplified Chinese translation:</p>
<pre>
native2ascii -encoding UTF8 my_translation.properties messenger_i18n_zh_CN.properties
native2ascii -encoding UTF8 my_translation.properties wildfire_i18n_zh_CN.properties
</pre>
<h2>Testing Your Translation</h2>
<p>To test your translation, copy the translated resource bundle file (example,
messenger_i18n_de.properties) to the <tt>lib/</tt> directory of your Jive Messenger
installation. Make sure Jive Messenger is stopped and then edit the <tt>conf/jive-messenger.xml</tt>
wildfire_i18n_de.properties) to the <tt>lib/</tt> directory of your Wildfire
installation. Make sure Wildfire is stopped and then edit the <tt>conf/wildfire.xml</tt>
file. Set the <tt>locale</tt> property to match your new resource
bundle such as "de" or "zh_CN". Start Jive Messenger and the admin console
bundle such as "de" or "zh_CN". Start Wildfire and the admin console
should now be using your translation. If you still see English text you may have
named your bundle incorrectly or used the wrong value for the <tt>locale</tt>
property.</p>
<p>Once your translation is complete and tested, please submit it to the Jive Messenger
<p>Once your translation is complete and tested, please submit it to the Wildfire
developers so that others can enjoy it in the next release!</p>
<br><br>
......
......@@ -2,38 +2,38 @@
# redhat-poinstall.sh
#
# This script sets permissions on the Jive Messenger installtion
# This script sets permissions on the Wildfire installtion
# and install the init script.
#
# Run this script as root after installation of jive messenger
# Run this script as root after installation of wildfire
# It is expected that you are executing this script from the bin directory
# If you used an non standard directory name of location
# Please specify it here
# MESSENGER_HOME=
# WILDFIRE_HOME=
MESSENGER_USER="jive"
MESSENGER_GROUP="jive"
WILDFIRE_USER="jive"
WILDFIRE_GROUP="jive"
if [ ! $MESSENGER_HOME ]; then
if [ -d "/opt/jive_messenger" ]; then
MESSENGER_HOME="/opt/jive_messenger"
elif [ -d "/usr/local/jive_messenger" ]; then
MESSENGER_HOME="/usr/local/jive_messenger"
if [ ! $WILDFIRE_HOME ]; then
if [ -d "/opt/wildfire" ]; then
WILDFIRE_HOME="/opt/wildfire"
elif [ -d "/usr/local/wildfire" ]; then
WILDFIRE_HOME="/usr/local/wildfire"
fi
fi
# Grant execution permissions
chmod +x $MESSENGER_HOME/bin/extra/jive-messengerd
chmod +x $WILDFIRE_HOME/bin/extra/wildfired
# Install the init script
cp $MESSENGER_HOME/bin/extra/jive-messengerd /etc/init.d
/sbin/chkconfig --add jive-messengerd
/sbin/chkconfig jive-messengerd on
cp $WILDFIRE_HOME/bin/extra/wildfired /etc/init.d
/sbin/chkconfig --add wildfired
/sbin/chkconfig wildfired on
# Create the jive user and group
/usr/sbin/groupadd $MESSENGER_GROUP
/usr/sbin/useradd $MESSENGER_USER -g $MESSENGER_GROUP -s /bin/bash
/usr/sbin/groupadd $WILDFIRE_GROUP
/usr/sbin/useradd $WILDFIRE_USER -g $WILDFIRE_GROUP -s /bin/bash
# Change the permissions on the installtion directory
/bin/chown -R $MESSENGER_USER:$MESSENGER_GROUP $MESSENGER_HOME
/bin/chown -R $WILDFIRE_USER:$WILDFIRE_GROUP $WILDFIRE_HOME
#!/bin/sh
# wildfired
#
# chkconfig: 2345 20 80
# description: Used to start and stop the wildfire XMPP server
#
# Script used to start wildfire as daemon
# The script has currently been tested on Redhat Fedora Core 3,
# but should theoretically work on most UNIX like systems
#
# before running this script make sure $WILDFIRE_HOME/bin/wildfire is
# executable by the user you want to run wildfire as
# (chmod +x $WILDFIRE_HOME/bin/wildfire)
#
# This script should be copied into /etc/init.d and linked into
# your default runlevel directory.
# You can find your default runlevel directory by typing:
# grep default /etc/inittab
#
# Link to the directory like follows
# cd /etc/rc<num>.d
# ln -s ../init.d/wildfired $90wildfired
#
# Set this to tell this script where wildfire lives
# If this is not set the script will look for /opt/jive_wildfire, then /usr/local/jive_wildfire
#export WILDFIRE_HOME=
# If there is a different user you would like to run this script as,
# change the following line
export WILDFIRE_USER=jive
# -----------------------------------------------------------------
# If a wildfire home variable has not been specified, try to determine it
if [ ! $WILDFIRE_HOME ]; then
if [ -d "/opt/wildfire" ]; then
WILDFIRE_HOME="/opt/wildfire"
elif [ -d "/usr/local/wildfire" ]; then
WILDFIRE_HOME="/usr/local/wildfire"
else
echo "Could not find Wildfire installation under /opt or /usr/local"
echo "Please specify the Wildfire installation location in environment variable WILDFIRE_HOME"
exit 1
fi
fi
function execCommand() {
OLD_PWD=`pwd`
cd $WILDFIRE_HOME/bin
CMD="./wildfire $1"
su -c "$CMD" $WILDFIRE_USER &
cd $OLD_PWD
}
start() {
execCommand "start"
}
stop() {
execCommand "stop"
}
case "$1" in
start)
start
;;
stop)
stop
;;
*)
echo "Usage $0 {start|stop}"
exit 1
esac
exit 0
@echo off
REM #
REM # $RCSfile$
REM # $Revision: 1102 $
REM # $Date: 2005-03-07 22:36:48 -0300 (Mon, 07 Mar 2005) $
REM #
if "%JAVA_HOME%" == "" goto javaerror
if not exist "%JAVA_HOME%\bin\java.exe" goto javaerror
goto run
:javaerror
echo.
echo Error: JAVA_HOME environment variable not set, Wildfire not started.
echo.
goto end
:run
if "%1" == "-debug" goto debug
start "Wildfire" "%JAVA_HOME%\bin\java" -server -jar ..\lib\startup.jar
goto end
:debug
start "Wildfire" "%JAVA_HOME%\bin\java" -Xdebug -Xint -server -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 -jar ..\lib\startup.jar
goto end
:end
#!/bin/sh
#
# $RCSfile$
# $Revision: 1194 $
# $Date: 2005-03-30 13:39:54 -0300 (Wed, 30 Mar 2005) $
#
# tries to determine arguments to launch wildfire
# OS specific support. $var _must_ be set to either true or false.
cygwin=false;
darwin=false;
case "`uname`" in
CYGWIN*) cygwin=true ;;
Darwin*) darwin=true
if [ -z "$JAVA_HOME" ] ; then
JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Home
fi
;;
esac
#if wildfire home is not set or is not a directory
if [ -z "$WILDFIRE_HOME" -o ! -d "$WILDFIRE_HOME" ]; then
if [ -d /opt/wildfire ] ; then
WILDFIRE_HOME="/opt/wildfire"
fi
if [ -d /usr/local/wildfire ] ; then
WILDFIRE_HOME="/usr/local/wildfire"
fi
if [ -d ${HOME}/opt/wildfire ] ; then
WILDFIRE_HOME="${HOME}/opt/wildfire"
fi
#resolve links - $0 may be a link in wildfire's home
PRG="0"
progname=`basename "$0$"`
# need this for relative symlinks
# need this for relative symlinks
while [ -h "$PRG" ] ; do
ls=`ls -ld "$PRG"`
link=`expr "$ls" : '.*-> \(.*\)$'`
if expr "$link" : '/.*' > /dev/null; then
PRG="$link"
else
PRG=`dirname "$PRG"`"/$link"
fi
done
#assumes we are in the bin directory
WILDFIRE_HOME=`dirname "$PRG"`/..
#make it fully qualified
WILDFIRE_HOME=`cd "$WILDFIRE_HOME" && pwd`
fi
WILDFIRE_OPTS="${WILDFIRE_OPTS} -DwildfireHome=${WILDFIRE_HOME}"
# For Cygwin, ensure paths are in UNIX format before anything is touched
if $cygwin ; then
[ -n "$WILDFIRE_HOME" ] &&
WILDFIRE_HOME=`cygpath --unix "$WILDFIRE_HOME"`
[ -n "$JAVA_HOME" ] &&
JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
fi
#set the WILDFIRE_LIB location
WILDFIRE_LIB="${WILDFIRE_HOME}/lib"
WILDFIRE_OPTS="${WILDFIRE_OPTS} -Dwildfire.lib.dir=${WILDFIRE_LIB}"
if [ -z "$JAVACMD" ] ; then
if [ -n "$JAVA_HOME" ] ; then
if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
# IBM's JDK on AIX uses strange locations for the executables
JAVACMD="$JAVA_HOME/jre/sh/java"
else
JAVACMD="$JAVA_HOME/bin/java"
fi
else
JAVACMD=`which java 2> /dev/null `
if [ -z "$JAVACMD" ] ; then
JAVACMD=java
fi
fi
fi
if [ ! -x "$JAVACMD" ] ; then
echo "Error: JAVA_HOME is not defined correctly."
echo " We cannot execute $JAVACMD"
exit 1
fi
if [ -z "$LOCALCLASSPATH" ] ; then
LOCALCLASSPATH=$WILDFIRE_LIB/startup.jar
else
LOCALCLASSPATH=$WILDFIRE_LIB/startup.jar:$LOCALCLASSPATH
fi
# For Cygwin, switch paths to appropriate format before running java
if $cygwin; then
if [ "$OS" = "Windows_NT" ] && cygpath -m .>/dev/null 2>/dev/null ; then
format=mixed
else
format=windows
fi
WILDFIRE_HOME=`cygpath --$format "$WILDFIRE_HOME"`
WILDFIRE_LIB=`cygpath --$format "$WILDFIRE_LIB"`
JAVA_HOME=`cygpath --$format "$JAVA_HOME"`
LOCALCLASSPATH=`cygpath --path --$format "$LOCALCLASSPATH"`
if [ -n "$CLASSPATH" ] ; then
CLASSPATH=`cygpath --path --$format "$CLASSPATH"`
fi
CYGHOME=`cygpath --$format "$HOME"`
fi
# add a second backslash to variables terminated by a backslash under cygwin
if $cygwin; then
case "$WILDFIRE_HOME" in
*\\ )
WILDFIRE_HOME="$WILDFIRE_HOME\\"
;;
esac
case "$CYGHOME" in
*\\ )
CYGHOME="$CYGHOME\\"
;;
esac
case "$LOCALCLASSPATH" in
*\\ )
LOCALCLASSPATH="$LOCALCLASSPATH\\"
;;
esac
case "$CLASSPATH" in
*\\ )
CLASSPATH="$CLASSPATH\\"
;;
esac
fi
wildfire_exec_command="exec \"$JAVACMD\" -server $WILDFIRE_OPTS -classpath \"$LOCALCLASSPATH\" -jar \"$WILDFIRE_LIB\"/startup.jar"
eval $wildfire_exec_command
<?xml version="1.0" encoding="UTF-8"?>
<!--
This file stores bootstrap properties needed by Wildfire.
Property names must be in the format: "prop.name.is.blah=value"
That will be stored as:
<prop>
<name>
<is>
<blah>value</blah>
</is>
</name>
</prop>
Most properties are stored in the Wildfire database. A
property viewer and editor is included in the admin console.
-->
<!-- root element, all properties must be under this element -->
<jive>
<adminConsole>
<!-- Disable either port by setting the value to -1 -->
<port>9090</port>
<securePort>9091</securePort>
</adminConsole>
<admin>
<!-- Use this section to define users that will have admin privileges. Below,
you will find two ways to specify which users are admins. Admins will
have access to the admin console (only local users) and may have also access
to other functionalities like ad-hoc commands. -->
<!-- By default, only the user with the username "admin" can login
to the admin console. Alternatively, you can specify a comma-delimitted
list usernames that should be authorized to login to the admin console
by setting the <authorizedUsernames> field below. -->
<!-- <authorizedUsernames></authorizedUsernames> -->
<!-- Comma-delimitted list of bare JIDs. The JIDs may belong to local
or remote users. -->
<!-- <authorizedJIDs></authorizedJIDs> -->
</admin>
<locale>en</locale>
<!-- Example LDAP settings -->
<!--
<ldap>
<host></host>
<port>389</port>
<usernameField>uid</usernameField>
<nameField>cn</nameField>
<emailField>mail</emailField>
<baseDN></baseDN>
<adminDN></adminDN>
<adminPassword></adminPassword>
</ldap>
<provider>
<user>
<className>org.jivesoftware.wildfire.ldap.LdapUserProvider</className>
</user>
<auth>
<className>org.jivesoftware.wildfire.ldap.LdapAuthProvider</className>
</auth>
</provider>
-->
<!-- End example LDAP settings -->
</jive>
\ No newline at end of file
-- $RCSfile$
-- $Revision: 395 $
-- $Date: 2004-11-13 16:57:13 -0300 (Sat, 13 Nov 2004) $
-- upgrades from Wildfire 1.1.x to 2.0.x
-- jiveUser: Adds new column "username". Removes "nameVisible" & "emailVisible". Changes primary key
ALTER TABLE jiveUser ADD COLUMN username VARCHAR(32) NOT NULL;
ALTER TABLE jiveUser DROP COLUMN nameVisible;
ALTER TABLE jiveUser DROP COLUMN emailVisible;
UPDATE jiveUser,jiveUserID SET jiveUser.username = jiveUserID.username where jiveUserID.objectID = jiveUser.userID;
ALTER TABLE jiveUser DROP PRIMARY KEY;
ALTER TABLE jiveUser ADD CONSTRAINT jiveUser_pk PRIMARY KEY (username);
-- jiveUserProp: Adds new column "username". Changes primary key
ALTER TABLE jiveUserProp ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveUserProp,jiveUser SET jiveUserProp.username = jiveUser.username where jiveUserProp.userID = jiveUser.userID;
ALTER TABLE jiveUserProp DROP PRIMARY KEY;
ALTER TABLE jiveUserProp ADD CONSTRAINT jiveUsrProp_pk PRIMARY KEY (username, name);
-- jiveGroupUser: Adds new column "username". Changes primary key
ALTER TABLE jiveGroupUser ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveGroupUser,jiveUser SET jiveGroupUser.username = jiveUser.username where jiveGroupUser.userID = jiveUser.userID;
ALTER TABLE jiveGroupUser DROP PRIMARY KEY;
ALTER TABLE jiveGroupUser ADD CONSTRAINT jiveGrpUser PRIMARY KEY (groupID, username, administrator);
-- jivePrivate: Adds new column "username". Changes primary key
ALTER TABLE jivePrivate ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jivePrivate,jiveUser SET jivePrivate.username = jiveUser.username where jivePrivate.userID = jiveUser.userID;
ALTER TABLE jivePrivate DROP PRIMARY KEY;
ALTER TABLE jivePrivate ADD CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace);
-- jiveOffline: Adds new column "username". Changes primary key
ALTER TABLE jiveOffline ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveOffline ,jiveUser SET jiveOffline.username = jiveUser.username where jiveOffline.userID = jiveUser.userID;
ALTER TABLE jiveOffline DROP PRIMARY KEY;
ALTER TABLE jiveOffline ADD CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID);
-- jiveRoster: Adds new column "username". Replaces old index with new one
ALTER TABLE jiveRoster ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveRoster,jiveUser SET jiveRoster.username = jiveUser.username where jiveRoster.userID = jiveUser.userID;
DROP INDEX jiveR_userid_idx;
CREATE INDEX jiveR_usrnme_idx ON jiveRoster (username ASC);
-- jiveVCard: Adds new column "username". Changes primary key
ALTER TABLE jiveVCard ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveVCard ,jiveUser SET jiveVCard.username = jiveUser.username where jiveVCard.userID = jiveUser.userID;
ALTER TABLE jiveVCard DROP PRIMARY KEY;
ALTER TABLE jiveVCard ADD CONSTRAINT jiveVCard_pk PRIMARY KEY (username, name);
-- Drops no longer needed tables
DROP TABLE jiveUserID;
DROP TABLE jiveChatbot;
DROP TABLE jiveDomain;
DROP TABLE jiveUserPerm;
-- Deletes no longer needed entries
DELETE FROM jiveID where idType = 0;
DELETE FROM jiveID where idType = 1;
DELETE FROM jiveID where idType = 2;
DELETE FROM jiveID where idType = 13;
DELETE FROM jiveID where idType = 14;
-- Finally remove "userID" column
ALTER TABLE jiveUserProp DROP COLUMN userID;
ALTER TABLE jiveUser DROP COLUMN userID;
ALTER TABLE jiveGroupUser DROP COLUMN userID;
ALTER TABLE jivePrivate DROP COLUMN userID;
ALTER TABLE jiveOffline DROP COLUMN userID;
ALTER TABLE jiveRoster DROP COLUMN userID;
ALTER TABLE jiveVCard DROP COLUMN userID;
-- Create new tables
CREATE TABLE jiveProperty (
name VARCHAR(100) NOT NULL,
propValue VARCHAR(3000) NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
-- MUC tables
CREATE TABLE mucRoom (
roomID INTEGER NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR(50) NOT NULL,
naturalName VARCHAR(255) NOT NULL,
description VARCHAR(255),
canChangeSubject INTEGER NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom INTEGER NOT NULL,
moderated INTEGER NOT NULL,
invitationRequired INTEGER NOT NULL,
canInvite INTEGER NOT NULL,
password VARCHAR(50) NULL,
canDiscoverJID INTEGER NOT NULL,
logEnabled INTEGER NOT NULL,
subject VARCHAR(100) NULL,
rolesToBroadcast INTEGER NOT NULL,
lastActiveDate CHAR(15) NULL,
inMemory INTEGER NOT NULL,
CONSTRAINT mucRoom_pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomid_idx ON mucRoom (roomID);
CREATE TABLE mucAffiliation (
roomID INTEGER NOT NULL,
jid VARCHAR(2000) NOT NULL,
affiliation INTEGER NOT NULL,
CONSTRAINT mucAffiliation_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucMember (
roomID INTEGER NOT NULL,
jid VARCHAR(2000) NOT NULL,
nickname VARCHAR(255) NULL,
CONSTRAINT mucMember_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucConversationLog (
roomID INTEGER NOT NULL,
sender VARCHAR(2000) NOT NULL,
nickname VARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR(255) NULL,
body LONG VARCHAR NULL
);
-- Unique ID entry for mucRoom
insert INTO jiveID (idType, id) VALUES (23, 1);
\ No newline at end of file
// $RCSfile$
// $Revision: 395 $
// $Date: 2004-11-13 16:57:13 -0300 (Sat, 13 Nov 2004) $
// upgrades from Wildfire 1.1.x to 2.0.x
// jiveUser: Adds new column "username". Removes "nameVisible" & "emailVisible". Changes primary key
ALTER TABLE jiveUser ADD COLUMN username VARCHAR(32) NOT NULL;
ALTER TABLE jiveUser DROP COLUMN nameVisible;
ALTER TABLE jiveUser DROP COLUMN emailVisible;
UPDATE jiveUser,jiveUserID SET jiveUser.username = jiveUserID.username where jiveUserID.objectID = jiveUser.userID;
ALTER TABLE jiveUser DROP PRIMARY KEY;
ALTER TABLE jiveUser ADD CONSTRAINT jiveUser_pk PRIMARY KEY (username);
// jiveUserProp: Adds new column "username". Changes primary key
ALTER TABLE jiveUserProp ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveUserProp,jiveUser SET jiveUserProp.username = jiveUser.username where jiveUserProp.userID = jiveUser.userID;
ALTER TABLE jiveUserProp DROP PRIMARY KEY;
ALTER TABLE jiveUserProp ADD CONSTRAINT jiveUserProp_pk PRIMARY KEY (username, name);
// jiveGroupUser: Adds new column "username". Changes primary key
ALTER TABLE jiveGroupUser ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveGroupUser,jiveUser SET jiveGroupUser.username = jiveUser.username where jiveGroupUser.userID = jiveUser.userID;
ALTER TABLE jiveGroupUser DROP PRIMARY KEY;
ALTER TABLE jiveGroupUser ADD CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupID, username, administrator);
// jivePrivate: Adds new column "username". Changes primary key
ALTER TABLE jivePrivate ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jivePrivate,jiveUser SET jivePrivate.username = jiveUser.username where jivePrivate.userID = jiveUser.userID;
ALTER TABLE jivePrivate DROP PRIMARY KEY;
ALTER TABLE jivePrivate ADD CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace);
// jiveOffline: Adds new column "username". Changes primary key
ALTER TABLE jiveOffline ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveOffline ,jiveUser SET jiveOffline.username = jiveUser.username where jiveOffline.userID = jiveUser.userID;
ALTER TABLE jiveOffline DROP PRIMARY KEY;
ALTER TABLE jiveOffline ADD CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID);
// jiveRoster: Adds new column "username". Replaces old index with new one
ALTER TABLE jiveRoster ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveRoster,jiveUser SET jiveRoster.username = jiveUser.username where jiveRoster.userID = jiveUser.userID;
DROP INDEX jiveRoster_userid_idx;
CREATE INDEX jiveRoster_username_idx ON jiveRoster (username);
// jiveVCard: Adds new column "username". Changes primary key
ALTER TABLE jiveVCard ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveVCard ,jiveUser SET jiveVCard.username = jiveUser.username where jiveVCard.userID = jiveUser.userID;
ALTER TABLE jiveVCard DROP PRIMARY KEY;
ALTER TABLE jiveVCard ADD CONSTRAINT jiveVCard_pk PRIMARY KEY (username, name);
// Drops no longer needed tables
DROP TABLE jiveUserID;
DROP TABLE jiveChatbot;
DROP TABLE jiveDomain;
DROP TABLE jiveUserPerm;
// Deletes no longer needed entries
DELETE FROM jiveID where idType = 0;
DELETE FROM jiveID where idType = 1;
DELETE FROM jiveID where idType = 2;
DELETE FROM jiveID where idType = 13;
DELETE FROM jiveID where idType = 14;
// Finally remove "userID" column
ALTER TABLE jiveUserProp DROP COLUMN userID;
ALTER TABLE jiveUser DROP COLUMN userID;
ALTER TABLE jiveGroupUser DROP COLUMN userID;
ALTER TABLE jivePrivate DROP COLUMN userID;
ALTER TABLE jiveOffline DROP COLUMN userID;
ALTER TABLE jiveRoster DROP COLUMN userID;
ALTER TABLE jiveVCard DROP COLUMN userID;
// Create new tables
CREATE TABLE jiveProperty (
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
// MUC Tables
CREATE TABLE mucRoom (
roomID BIGINT NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR(50) NOT NULL,
naturalName VARCHAR(255) NOT NULL,
description VARCHAR(255),
canChangeSubject INTEGER NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom INTEGER NOT NULL,
moderated INTEGER NOT NULL,
invitationRequired INTEGER NOT NULL,
canInvite INTEGER NOT NULL,
password VARCHAR(50) NULL,
canDiscoverJID INTEGER NOT NULL,
logEnabled INTEGER NOT NULL,
subject VARCHAR(100) NULL,
rolesToBroadcast INTEGER NOT NULL,
lastActiveDate CHAR(15) NULL,
inMemory INTEGER NOT NULL,
CONSTRAINT mucRoom_pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomid_idx ON mucRoom(roomID);
CREATE TABLE mucAffiliation (
roomID BIGINT NOT NULL,
jid VARCHAR(3071) NOT NULL,
affiliation INTEGER NOT NULL,
CONSTRAINT mucAffiliation_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucMember (
roomID BIGINT NOT NULL,
jid VARCHAR(3071) NOT NULL,
nickname VARCHAR(255) NULL,
CONSTRAINT mucMember_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucConversationLog (
roomID BIGINT NOT NULL,
sender VARCHAR(3071) NOT NULL,
nickname VARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR(255) NULL,
body LONGVARCHAR NULL
);
// Unique ID entry for mucRoom
INSERT INTO jiveID (idType, id) VALUES (23, 1);
\ No newline at end of file
# $RCSfile$
# $Revision: 395 $
# $Date: 2004-11-13 16:57:13 -0300 (Sat, 13 Nov 2004) $
# upgrades from Wildfire 1.1.x to 2.0.x
# jiveUser: Adds new column "username". Removes "nameVisible" & "emailVisible". Changes primary key
ALTER TABLE jiveUser ADD COLUMN username VARCHAR(32) NOT NULL;
ALTER TABLE jiveUser DROP COLUMN nameVisible;
ALTER TABLE jiveUser DROP COLUMN emailVisible;
UPDATE jiveUser,jiveUserID SET jiveUser.username = jiveUserID.username where jiveUserID.objectID = jiveUser.userID;
ALTER TABLE jiveUser DROP PRIMARY KEY;
ALTER TABLE jiveUser ADD PRIMARY KEY (username);
# jiveUserProp: Adds new column "username". Changes primary key
ALTER TABLE jiveUserProp ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveUserProp,jiveUser SET jiveUserProp.username = jiveUser.username where jiveUserProp.userID = jiveUser.userID;
ALTER TABLE jiveUserProp DROP PRIMARY KEY;
ALTER TABLE jiveUserProp ADD PRIMARY KEY (username, name);
# jiveGroupUser: Adds new column "username". Changes primary key
ALTER TABLE jiveGroupUser ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveGroupUser,jiveUser SET jiveGroupUser.username = jiveUser.username where jiveGroupUser.userID = jiveUser.userID;
ALTER TABLE jiveGroupUser DROP PRIMARY KEY;
ALTER TABLE jiveGroupUser ADD PRIMARY KEY (groupID, username, administrator);
# jivePrivate: Adds new column "username". Changes primary key
ALTER TABLE jivePrivate ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jivePrivate,jiveUser SET jivePrivate.username = jiveUser.username where jivePrivate.userID = jiveUser.userID;
ALTER TABLE jivePrivate DROP PRIMARY KEY;
ALTER TABLE jivePrivate ADD PRIMARY KEY (username, name, namespace);
# jiveOffline: Adds new column "username". Changes primary key
ALTER TABLE jiveOffline ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveOffline ,jiveUser SET jiveOffline.username = jiveUser.username where jiveOffline.userID = jiveUser.userID;
ALTER TABLE jiveOffline DROP PRIMARY KEY;
ALTER TABLE jiveOffline ADD PRIMARY KEY (username, messageID);
# jiveRoster: Adds new column "username". Replaces old index with new one
ALTER TABLE jiveRoster ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveRoster,jiveUser SET jiveRoster.username = jiveUser.username where jiveRoster.userID = jiveUser.userID;
ALTER TABLE jiveRoster DROP INDEX jiveRoster_userid_idx;
ALTER TABLE jiveRoster ADD INDEX jiveRoster_unameid_idx (username);
# jiveVCard: Adds new column "username". Changes primary key
ALTER TABLE jiveVCard ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveVCard ,jiveUser SET jiveVCard.username = jiveUser.username where jiveVCard.userID = jiveUser.userID;
ALTER TABLE jiveVCard DROP PRIMARY KEY;
ALTER TABLE jiveVCard ADD PRIMARY KEY (username, name);
# Drops no longer needed tables
DROP TABLE jiveUserID;
DROP TABLE jiveChatbot;
DROP TABLE jiveDomain;
DROP TABLE jiveUserPerm;
# Deletes no longer needed entries
DELETE FROM jiveID where idType = 0;
DELETE FROM jiveID where idType = 1;
DELETE FROM jiveID where idType = 2;
DELETE FROM jiveID where idType = 13;
DELETE FROM jiveID where idType = 14;
# Finally remove "userID" column
ALTER TABLE jiveUserProp DROP COLUMN userID;
ALTER TABLE jiveUser DROP COLUMN userID;
ALTER TABLE jiveGroupUser DROP COLUMN userID;
ALTER TABLE jivePrivate DROP COLUMN userID;
ALTER TABLE jiveOffline DROP COLUMN userID;
ALTER TABLE jiveRoster DROP COLUMN userID;
ALTER TABLE jiveVCard DROP COLUMN userID;
# Create new tables
CREATE TABLE jiveProperty (
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
PRIMARY KEY (name)
);
# MUC Tables
CREATE TABLE mucRoom (
roomID BIGINT NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR(50) NOT NULL,
naturalName VARCHAR(255) NOT NULL,
description VARCHAR(255),
canChangeSubject TINYINT NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom TINYINT NOT NULL,
moderated TINYINT NOT NULL,
invitationRequired TINYINT NOT NULL,
canInvite TINYINT NOT NULL,
password VARCHAR(50) NULL,
canDiscoverJID TINYINT NOT NULL,
logEnabled TINYINT NOT NULL,
subject VARCHAR(100) NULL,
rolesToBroadcast TINYINT NOT NULL,
lastActiveDate CHAR(15) NULL,
inMemory TINYINT NOT NULL,
PRIMARY KEY (name),
INDEX mucRoom_roomid_idx (roomID)
);
CREATE TABLE mucAffiliation (
roomID BIGINT NOT NULL,
jid TEXT NOT NULL,
affiliation TINYINT NOT NULL,
PRIMARY KEY (roomID,jid(70))
);
CREATE TABLE mucMember (
roomID BIGINT NOT NULL,
jid TEXT NOT NULL,
nickname VARCHAR(255) NULL,
PRIMARY KEY (roomID,jid(70))
);
CREATE TABLE mucConversationLog (
roomID BIGINT NOT NULL,
sender TEXT NOT NULL,
nickname VARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR(255) NULL,
body TEXT NULL
);
# Unique ID entry for mucRoom
INSERT INTO jiveID (idType, id) VALUES (23, 1);
\ No newline at end of file
REM // $RCSfile$
REM // $Revision: 784 $
REM // $Date: 2005-01-04 12:47:23 -0300 (Tue, 04 Jan 2005) $
REM // upgrades from Wildfire 1.1.x to 2.0.x
REM // jiveUser: Adds new column "username". Removes "nameVisible" & "emailVisible". Changes primary key
ALTER TABLE jiveUser ADD username VARCHAR2(32) NOT NULL;
ALTER TABLE jiveUser DROP COLUMN nameVisible;
ALTER TABLE jiveUser DROP COLUMN emailVisible;
UPDATE jiveUser,jiveUserID SET jiveUser.username = jiveUserID.username where jiveUserID.objectID = jiveUser.userID;
ALTER TABLE jiveUser DROP PRIMARY KEY;
ALTER TABLE jiveUser ADD CONSTRAINT jiveUser_pk PRIMARY KEY (username);
REM // jiveUserProp: Adds new column "username". Changes primary key
ALTER TABLE jiveUserProp ADD username VARCHAR2(32) NOT NULL;
UPDATE jiveUserProp,jiveUser SET jiveUserProp.username = jiveUser.username where jiveUserProp.userID = jiveUser.userID;
ALTER TABLE jiveUserProp DROP PRIMARY KEY;
ALTER TABLE jiveUserProp ADD CONSTRAINT jiveUserProp_pk PRIMARY KEY (username, name);
REM // jiveGroupUser: Adds new column "username". Changes primary key
ALTER TABLE jiveGroupUser ADD username VARCHAR2(32) NOT NULL;
UPDATE jiveGroupUser,jiveUser SET jiveGroupUser.username = jiveUser.username where jiveGroupUser.userID = jiveUser.userID;
ALTER TABLE jiveGroupUser DROP PRIMARY KEY;
ALTER TABLE jiveGroupUser ADD CONSTRAINT jiveGroupUser PRIMARY KEY (groupID, username, administrator);
REM // jivePrivate: Adds new column "username". Changes primary key
ALTER TABLE jivePrivate ADD username VARCHAR2(32) NOT NULL;
UPDATE jivePrivate,jiveUser SET jivePrivate.username = jiveUser.username where jivePrivate.userID = jiveUser.userID;
ALTER TABLE jivePrivate DROP PRIMARY KEY;
ALTER TABLE jivePrivate ADD CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace);
REM // jiveOffline: Adds new column "username". Changes primary key
ALTER TABLE jiveOffline ADD username VARCHAR2(32) NOT NULL;
UPDATE jiveOffline ,jiveUser SET jiveOffline.username = jiveUser.username where jiveOffline.userID = jiveUser.userID;
ALTER TABLE jiveOffline DROP PRIMARY KEY;
ALTER TABLE jiveOffline ADD CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID);
REM // jiveRoster: Adds new column "username". Replaces old index with new one
ALTER TABLE jiveRoster ADD username VARCHAR2(32) NOT NULL;
UPDATE jiveRoster,jiveUser SET jiveRoster.username = jiveUser.username where jiveRoster.userID = jiveUser.userID;
DROP INDEX jiveRoster_userid_idx;
CREATE INDEX jiveRoster_username_idx ON jiveRoster (username ASC);
REM // jiveVCard: Adds new column "username". Changes primary key
ALTER TABLE jiveVCard ADD username VARCHAR2(32) NOT NULL;
UPDATE jiveVCard ,jiveUser SET jiveVCard.username = jiveUser.username where jiveVCard.userID = jiveUser.userID;
ALTER TABLE jiveVCard DROP PRIMARY KEY;
ALTER TABLE jiveVCard ADD CONSTRAINT jiveVCard_pk PRIMARY KEY (username, name);
REM // Drops no longer needed tables
DROP TABLE jiveUserID;
DROP TABLE jiveChatbot;
DROP TABLE jiveDomain;
DROP TABLE jiveUserPerm;
REM // Deletes no longer needed entries
DELETE FROM jiveID where idType = 0;
DELETE FROM jiveID where idType = 1;
DELETE FROM jiveID where idType = 2;
DELETE FROM jiveID where idType = 13;
DELETE FROM jiveID where idType = 14;
REM // Finally remove "userID" column
ALTER TABLE jiveUserProp DROP COLUMN userID;
ALTER TABLE jiveUser DROP COLUMN userID;
ALTER TABLE jiveGroupUser DROP COLUMN userID;
ALTER TABLE jivePrivate DROP COLUMN userID;
ALTER TABLE jiveOffline DROP COLUMN userID;
ALTER TABLE jiveRoster DROP COLUMN userID;
ALTER TABLE jiveVCard DROP COLUMN userID;
REM // Create new tables
CREATE TABLE jiveProperty (
name VARCHAR2(100) NOT NULL,
propValue VARCHAR2(4000) NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
REM // MUC Tables
CREATE TABLE mucRoom(
roomID INT NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR2(50) NOT NULL,
naturalName VARCHAR2(255) NOT NULL,
description VARCHAR2(255),
canChangeSubject INTEGER NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom INTEGER NOT NULL,
moderated INTEGER NOT NULL,
invitationRequired INTEGER NOT NULL,
canInvite INTEGER NOT NULL,
password VARCHAR2(50) NULL,
canDiscoverJID INTEGER NOT NULL,
logEnabled INTEGER NOT NULL,
subject VARCHAR2(100) NULL,
rolesToBroadcast INTEGER NOT NULL,
lastActiveDate CHAR(15) NULL,
inMemory INTEGER NOT NULL,
CONSTRAINT mucRoom_pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomid_idx ON mucRoom (roomID);
CREATE TABLE mucAffiliation (
roomID INT NOT NULL,
jid VARCHAR2(4000) NOT NULL,
affiliation INTEGER NOT NULL,
CONSTRAINT mucAffiliation_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucMember (
roomID INT NOT NULL,
jid VARCHAR2(4000) NOT NULL,
nickname VARCHAR2(255) NULL,
CONSTRAINT mucMember_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucConversationLog (
roomID INT NOT NULL,
sender VARCHAR2(4000) NOT NULL,
nickname VARCHAR2(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR2(255) NULL,
body VARCHAR2(4000) NULL
);
REM // Unique ID entry for mucRoom
INSERT INTO jiveID (idType, id) VALUES (23, 1);
\ No newline at end of file
-- $RCSfile$
-- $Revision: 395 $
-- $Date: 2004-11-13 16:57:13 -0300 (Sat, 13 Nov 2004) $
-- upgrades from Wildfire 1.1.x to 2.0.x
-- jiveUser: Adds new column "username". Removes "nameVisible" & "emailVisible". Changes primary key
ALTER TABLE jiveUser ADD COLUMN username VARCHAR(32) NOT NULL;
ALTER TABLE jiveUser DROP COLUMN nameVisible;
ALTER TABLE jiveUser DROP COLUMN emailVisible;
UPDATE jiveUser,jiveUserID SET jiveUser.username = jiveUserID.username where jiveUserID.objectID = jiveUser.userID;
ALTER TABLE jiveUser DROP PRIMARY KEY;
ALTER TABLE jiveUser ADD CONSTRAINT jiveUser_pk PRIMARY KEY (username);
-- jiveUserProp: Adds new column "username". Changes primary key
ALTER TABLE jiveUserProp ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveUserProp,jiveUser SET jiveUserProp.username = jiveUser.username where jiveUserProp.userID = jiveUser.userID;
ALTER TABLE jiveUserProp DROP PRIMARY KEY;
ALTER TABLE jiveUserProp ADD CONSTRAINT jiveUserProp_pk PRIMARY KEY (username, name);
-- jiveGroupUser: Adds new column "username". Changes primary key
ALTER TABLE jiveGroupUser ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveGroupUser,jiveUser SET jiveGroupUser.username = jiveUser.username where jiveGroupUser.userID = jiveUser.userID;
ALTER TABLE jiveGroupUser DROP PRIMARY KEY;
ALTER TABLE jiveGroupUser ADD CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupID, username, administrator);
-- jivePrivate: Adds new column "username". Changes primary key
ALTER TABLE jivePrivate ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jivePrivate,jiveUser SET jivePrivate.username = jiveUser.username where jivePrivate.userID = jiveUser.userID;
ALTER TABLE jivePrivate DROP PRIMARY KEY;
ALTER TABLE jivePrivate ADD CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace);
-- jiveOffline: Adds new column "username". Changes primary key
ALTER TABLE jiveOffline ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveOffline ,jiveUser SET jiveOffline.username = jiveUser.username where jiveOffline.userID = jiveUser.userID;
ALTER TABLE jiveOffline DROP PRIMARY KEY;
ALTER TABLE jiveOffline ADD CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID);
-- jiveRoster: Adds new column "username". Replaces old index with new one
ALTER TABLE jiveRoster ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveRoster,jiveUser SET jiveRoster.username = jiveUser.username where jiveRoster.userID = jiveUser.userID;
DROP INDEX jiveRoster_userID_idx;
CREATE INDEX jiveRoster_username_idx ON jiveRoster (username);
-- jiveVCard: Adds new column "username". Changes primary key
ALTER TABLE jiveVCard ADD COLUMN username VARCHAR(32) NOT NULL;
UPDATE jiveVCard ,jiveUser SET jiveVCard.username = jiveUser.username where jiveVCard.userID = jiveUser.userID;
ALTER TABLE jiveVCard DROP PRIMARY KEY;
ALTER TABLE jiveVCard ADD CONSTRAINT jiveVCard_pk PRIMARY KEY (username, name);
-- Drops no longer needed tables
DROP TABLE jiveUserID;
DROP TABLE jiveChatbot;
DROP TABLE jiveDomain;
DROP TABLE jiveUserPerm;
-- Deletes no longer needed entries
DELETE FROM jiveID where idType = 0;
DELETE FROM jiveID where idType = 1;
DELETE FROM jiveID where idType = 2;
DELETE FROM jiveID where idType = 13;
DELETE FROM jiveID where idType = 14;
-- Finally remove "userID" column
ALTER TABLE jiveUserProp DROP COLUMN userID;
ALTER TABLE jiveUser DROP COLUMN userID;
ALTER TABLE jiveGroupUser DROP COLUMN userID;
ALTER TABLE jivePrivate DROP COLUMN userID;
ALTER TABLE jiveOffline DROP COLUMN userID;
ALTER TABLE jiveRoster DROP COLUMN userID;
ALTER TABLE jiveVCard DROP COLUMN userID;
-- Create new tables
CREATE TABLE jiveProperty (
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
-- MUC Tables
CREATE TABLE mucRoom (
roomID INTEGER NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR(50) NOT NULL,
naturalName VARCHAR(255) NOT NULL,
description VARCHAR(255),
canChangeSubject INTEGER NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom INTEGER NOT NULL,
moderated INTEGER NOT NULL,
invitationRequired INTEGER NOT NULL,
canInvite INTEGER NOT NULL,
password VARCHAR(50) NULL,
canDiscoverJID INTEGER NOT NULL,
logEnabled INTEGER NOT NULL,
subject VARCHAR(100) NULL,
rolesToBroadcast INTEGER NOT NULL,
lastActiveDate CHAR(15) NULL,
inMemory INTEGER NOT NULL,
CONSTRAINT mucRoom__pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomID_idx ON mucRoom(roomID);
CREATE TABLE mucAffiliation (
roomID INTEGER NOT NULL,
jid VARCHAR(3000) NOT NULL,
affiliation INTEGER NOT NULL,
CONSTRAINT mucAffiliation__pk PRIMARY KEY (roomID,jid)
);
CREATE TABLE mucMember (
roomID INTEGER NOT NULL,
jid TEXT NOT NULL,
nickname VARCHAR(255) NULL,
CONSTRAINT mucMember__pk PRIMARY KEY (roomID,jid)
);
CREATE TABLE mucConversationLog (
roomID INTEGER NOT NULL,
sender TEXT NOT NULL,
nickname VARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR(255) NULL,
body TEXT NULL
);
-- Unique ID entry for mucRoom
INSERT INTO jiveID (idType, id) VALUES (23, 1);
\ No newline at end of file
/* $RCSfile$ */
/* $Revision: 840 $ */
/* $Date: 2005-01-10 01:30:06 -0300 (Mon, 10 Jan 2005) $ */
/* upgrades from Wildfire 1.1.x to 2.0.x */
/* jiveUser: Adds new column "username". Removes "nameVisible" & "emailVisible". Changes primary key */
ALTER TABLE jiveUser ADD COLUMN username NVARCHAR(32) NOT NULL;
ALTER TABLE jiveUser DROP COLUMN nameVisible;
ALTER TABLE jiveUser DROP COLUMN emailVisible;
UPDATE jiveUser,jiveUserID SET jiveUser.username = jiveUserID.username where jiveUserID.objectID = jiveUser.userID;
ALTER TABLE jiveUser DROP PRIMARY KEY;
ALTER TABLE jiveUser ADD CONSTRAINT jiveUser_pk PRIMARY KEY (username);
/* jiveUserProp: Adds new column "username". Changes primary key */
ALTER TABLE jiveUserProp ADD COLUMN username NVARCHAR(32) NOT NULL;
UPDATE jiveUserProp,jiveUser SET jiveUserProp.username = jiveUser.username where jiveUserProp.userID = jiveUser.userID;
ALTER TABLE jiveUserProp DROP PRIMARY KEY;
ALTER TABLE jiveUserProp ADD CONSTRAINT jiveUserProp_pk PRIMARY KEY (username, name);
/* jiveGroupUser: Adds new column "username". Changes primary key */
ALTER TABLE jiveGroupUser ADD COLUMN username NVARCHAR(32) NOT NULL;
UPDATE jiveGroupUser,jiveUser SET jiveGroupUser.username = jiveUser.username where jiveGroupUser.userID = jiveUser.userID;
ALTER TABLE jiveGroupUser DROP PRIMARY KEY;
ALTER TABLE jiveGroupUser ADD CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupID, username, administrator);
/* jivePrivate: Adds new column "username". Changes primary key */
ALTER TABLE jivePrivate ADD COLUMN username NVARCHAR(32) NOT NULL;
UPDATE jivePrivate,jiveUser SET jivePrivate.username = jiveUser.username where jivePrivate.userID = jiveUser.userID;
ALTER TABLE jivePrivate DROP PRIMARY KEY;
ALTER TABLE jivePrivate ADD CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace);
/* jiveOffline: Adds new column "username". Changes primary key */
ALTER TABLE jiveOffline ADD COLUMN username NVARCHAR(32) NOT NULL;
UPDATE jiveOffline ,jiveUser SET jiveOffline.username = jiveUser.username where jiveOffline.userID = jiveUser.userID;
ALTER TABLE jiveOffline DROP PRIMARY KEY;
ALTER TABLE jiveOffline ADD CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID);
/* jiveRoster: Adds new column "username". Replaces old index with new one */
ALTER TABLE jiveRoster ADD COLUMN username NVARCHAR(32) NOT NULL;
UPDATE jiveRoster,jiveUser SET jiveRoster.username = jiveUser.username where jiveRoster.userID = jiveUser.userID;
DROP INDEX jiveRoster_userID_idx;
CREATE INDEX jiveRoster_username_idx ON jiveRoster (username ASC);
/* jiveVCard: Adds new column "username". Changes primary key */
ALTER TABLE jiveVCard ADD COLUMN username NVARCHAR(32) NOT NULL;
UPDATE jiveVCard ,jiveUser SET jiveVCard.username = jiveUser.username where jiveVCard.userID = jiveUser.userID;
ALTER TABLE jiveVCard DROP PRIMARY KEY;
ALTER TABLE jiveVCard ADD CONSTRAINT jiveVCard_pk PRIMARY KEY (username, name);
/* Drops no longer needed tables */
DROP TABLE jiveUserID;
DROP TABLE jiveChatbot;
DROP TABLE jiveDomain;
DROP TABLE jiveUserPerm;
/* Deletes no longer needed entries */
DELETE FROM jiveID where idType = 0;
DELETE FROM jiveID where idType = 1;
DELETE FROM jiveID where idType = 2;
DELETE FROM jiveID where idType = 13;
DELETE FROM jiveID where idType = 14;
/* Finally remove "userID" column */
ALTER TABLE jiveUserProp DROP COLUMN userID;
ALTER TABLE jiveUser DROP COLUMN userID;
ALTER TABLE jiveGroupUser DROP COLUMN userID;
ALTER TABLE jivePrivate DROP COLUMN userID;
ALTER TABLE jiveOffline DROP COLUMN userID;
ALTER TABLE jiveRoster DROP COLUMN userID;
ALTER TABLE jiveVCard DROP COLUMN userID;
/* Create new tables */
CREATE TABLE jiveProperty (
name NVARCHAR(100) NOT NULL,
propValue NTEXT NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
/* MUC Tables */
CREATE TABLE mucRoom (
roomID INT NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name NVARCHAR(50) NOT NULL,
naturalName NVARCHAR(255) NOT NULL,
description NVARCHAR(255),
canChangeSubject INT NOT NULL,
maxUsers INT NOT NULL,
publicRoom INT NOT NULL,
moderated INT NOT NULL,
invitationRequired INT NOT NULL,
canInvite INT NOT NULL,
password NVARCHAR(50) NULL,
canDiscoverJID INT NOT NULL,
logEnabled INT NOT NULL,
subject NVARCHAR(100) NULL,
rolesToBroadcast INT NOT NULL,
lastActiveDate CHAR(15) NULL,
inMemory INT NOT NULL,
CONSTRAINT mucRoom__pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomID_idx on mucRoom(roomID);
CREATE TABLE mucAffiliation (
roomID INT NOT NULL,
jid NVARCHAR(3000) NOT NULL,
affiliation INT NOT NULL,
CONSTRAINT mucAffiliation__pk PRIMARY KEY (roomID,jid)
);
CREATE TABLE mucMember (
roomID INT NOT NULL,
jid NVARCHAR(3000) NOT NULL,
nickname NVARCHAR(255) NULL,
CONSTRAINT mucMember__pk PRIMARY KEY (roomID,jid)
);
CREATE TABLE mucConversationLog (
roomID INT NOT NULL,
sender NVARCHAR(3000) NOT NULL,
nickname NVARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject NVARCHAR(255) NULL,
body NVARCHAR(3700) NULL
);
/* Unique ID entry for mucRoom */
INSERT INTO jiveID (idType, id) VALUES (23, 1);
\ No newline at end of file
-- $RCSfile$
-- $Revision: 795 $
-- $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
-- upgrades from Wildfire 2.0.x to 2.1.0
-- jiveGroup: Recreate table from scratch
DROP TABLE jiveGroup;
CREATE TABLE jiveGroup (
groupName VARCHAR(50) NOT NULL,
description VARCHAR(255),
CONSTRAINT jiveGroup_pk PRIMARY KEY (groupName)
);
-- jiveGroupProp: Recreate table from scratch
DROP TABLE jiveGroupProp;
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(2000) NOT NULL,
CONSTRAINT jiveGrpProp_pk PRIMARY KEY (groupName, name)
);
-- jiveGroupUser: Recreate table from scratch
DROP TABLE jiveGroupUser;
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGrpUser PRIMARY KEY (groupName, username, administrator)
);
-- mucRoom: Add new columns: "lockedDate" and "emptyDate". Rename column "invitationRequired" to "membersOnly". Delete columns: "lastActiveDate" and "inMemory".
ALTER TABLE mucRoom ADD COLUMN lockedDate CHAR(15) NOT NULL;
ALTER TABLE mucRoom ADD COLUMN emptyDate CHAR(15) NULL;
ALTER TABLE mucRoom RENAME COLUMN invitationRequired TO membersOnly;
ALTER TABLE mucRoom DROP COLUMN lastActiveDate;
ALTER TABLE mucRoom DROP COLUMN inMemory;
-- mucMember: Add new columns
ALTER TABLE mucMember ADD COLUMN firstName VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN lastName VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN url VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN email VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN faqentry VARCHAR(100) NULL;
-- mucConversationLog: Add new index
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
-- Deletes no longer needed entries
DELETE FROM jiveID where idType = 3;
DELETE FROM jiveID where idType = 4;
-- Add jiveVersion
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 1);
\ No newline at end of file
// $RCSfile$
// $Revision: 795 $
// $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
// upgrades from Wildfire 2.0.x to 2.1.0
// jiveGroup: Recreate table from scratch
DROP TABLE jiveGroup;
CREATE TABLE jiveGroup (
groupName VARCHAR(50) NOT NULL,
description VARCHAR(255),
CONSTRAINT jiveGroup_pk PRIMARY KEY (groupName)
);
// jiveGroupProp: Recreate table from scratch
DROP TABLE jiveGroupProp;
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT jiveGroupProp_pk PRIMARY KEY (groupName, name)
);
// jiveGroupUser: Recreate table from scratch
DROP TABLE jiveGroupUser;
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupName, username, administrator)
);
// mucRoom: Add new columns: "lockedDate" and "emptyDate". Rename column "invitationRequired" to "membersOnly". Delete columns: "lastActiveDate" and "inMemory".
ALTER TABLE mucRoom ADD COLUMN lockedDate CHAR(15) NOT NULL BEFORE canChangeSubject;
ALTER TABLE mucRoom ADD COLUMN emptyDate CHAR(15) NULL BEFORE canChangeSubject;
// ALTER TABLE <tablename> ALTER COLUMN <columnname> {RENAME TO <newname> };
ALTER TABLE mucRoom ALTER COLUMN invitationRequired RENAME TO membersOnly;
ALTER TABLE mucRoom DROP COLUMN lastActiveDate;
ALTER TABLE mucRoom DROP COLUMN inMemory;
// mucMember: Add new columns
ALTER TABLE mucMember ADD COLUMN firstName VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN lastName VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN url VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN email VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN faqentry VARCHAR(100) NULL;
// mucConversationLog: Add new index
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
// Deletes no longer needed entries
DELETE FROM jiveID where idType = 3;
DELETE FROM jiveID where idType = 4;
// Add jiveVersion table
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 1);
\ No newline at end of file
# $RCSfile$
# $Revision: 795 $
# $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
# upgrades from Wildfire 2.0.x to 2.1.0
# jiveGroup: Recreate table from scratch
DROP TABLE jiveGroup;
CREATE TABLE jiveGroup (
groupName VARCHAR(50) NOT NULL,
description VARCHAR(255),
PRIMARY KEY (groupName)
);
# jiveGroupProp: Recreate table from scratch
DROP TABLE jiveGroupProp;
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
PRIMARY KEY (groupName, name)
);
# jiveGroupUser: Recreate table from scratch
DROP TABLE jiveGroupUser;
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(32) NOT NULL,
administrator TINYINT NOT NULL,
PRIMARY KEY (groupName, username, administrator)
);
# mucRoom: Add new columns: "lockedDate" and "emptyDate". Rename column "invitationRequired" to "membersOnly". Delete columns: "lastActiveDate" and "inMemory".
ALTER TABLE mucRoom ADD COLUMN lockedDate CHAR(15) NOT NULL AFTER description;
ALTER TABLE mucRoom ADD COLUMN emptyDate CHAR(15) NULL AFTER lockedDate;
ALTER TABLE mucRoom CHANGE invitationRequired membersOnly TINYINT NOT NULL;
ALTER TABLE mucRoom DROP COLUMN lastActiveDate;
ALTER TABLE mucRoom DROP COLUMN inMemory;
# mucMember: Add new columns
ALTER TABLE mucMember ADD COLUMN firstName VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN lastName VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN url VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN email VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN faqentry VARCHAR(100) NULL;
# mucConversationLog: Add new index
ALTER TABLE mucConversationLog ADD INDEX mucLog_time_idx (time);
# Deletes no longer needed entries
DELETE FROM jiveID where idType = 3;
DELETE FROM jiveID where idType = 4;
# Add jiveVersion table
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 1);
\ No newline at end of file
REM // $RCSfile$
REM // $Revision: 795 $
REM // $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
REM // upgrades from Wildfire 2.0.x to 2.1.0
REM // jiveGroup: Recreate table from scratch
DROP TABLE jiveGroup;
CREATE TABLE jiveGroup (
groupName VARCHAR2(50) NOT NULL,
description VARCHAR2(255),
CONSTRAINT jiveGroup_pk PRIMARY KEY (groupName)
);
REM // jiveGroupProp: Recreate table from scratch
DROP TABLE jiveGroupProp;
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR2(100) NOT NULL,
propValue VARCHAR2(4000) NOT NULL,
CONSTRAINT jiveGroupProp_pk PRIMARY KEY (groupName, name)
);
REM // jiveGroupUser: Recreate table from scratch
DROP TABLE jiveGroupUser;
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR2(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGroupUser PRIMARY KEY (groupName, username, administrator)
);
REM // mucRoom: Add new columns: "lockedDate" and "emptyDate". Rename column "invitationRequired" to "membersOnly". Delete columns: "lastActiveDate" and "inMemory".
ALTER TABLE mucRoom ADD lockedDate CHAR(15) NOT NULL;
ALTER TABLE mucRoom ADD emptyDate CHAR(15) NULL;
ALTER TABLE mucRoom RENAME COLUMN invitationRequired TO membersOnly;
ALTER TABLE mucRoom DROP COLUMN lastActiveDate;
ALTER TABLE mucRoom DROP COLUMN inMemory;
REM // mucMember: Add new columns
ALTER TABLE mucMember ADD firstName VARCHAR2(100) NULL;
ALTER TABLE mucMember ADD lastName VARCHAR2(100) NULL;
ALTER TABLE mucMember ADD url VARCHAR2(100) NULL;
ALTER TABLE mucMember ADD email VARCHAR2(100) NULL;
ALTER TABLE mucMember ADD faqentry VARCHAR2(100) NULL;
REM // mucConversationLog: Add new index
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
REM // Deletes no longer needed entries
DELETE FROM jiveID where idType = 3;
DELETE FROM jiveID where idType = 4;
REM // Add jiveVersion table
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 1);
\ No newline at end of file
-- $RCSfile$
-- $Revision: 795 $
-- $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
-- upgrades from Wildfire 2.0.x to 2.1.0
-- jiveGroup: Recreate table from scratch
DROP TABLE jiveGroup;
CREATE TABLE jiveGroup (
groupName VARCHAR(50) NOT NULL,
description VARCHAR(255),
CONSTRAINT jiveGroup_pk PRIMARY KEY (groupName)
);
-- jiveGroupProp: Recreate table from scratch
DROP TABLE jiveGroupProp;
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
CONSTRAINT jiveGroupProp_pk PRIMARY KEY (groupName, name)
);
-- jiveGroupUser: Recreate table from scratch
DROP TABLE jiveGroupUser;
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupName, username, administrator)
);
-- mucRoom: Add new columns: "lockedDate" and "emptyDate". Rename column "invitationRequired" to "membersOnly". Delete columns: "lastActiveDate" and "inMemory".
ALTER TABLE mucRoom ADD COLUMN lockedDate CHAR(15) NOT NULL;
ALTER TABLE mucRoom ADD COLUMN emptyDate CHAR(15) NULL;
ALTER TABLE mucRoom RENAME COLUMN invitationRequired TO membersOnly;
ALTER TABLE mucRoom DROP COLUMN lastActiveDate;
ALTER TABLE mucRoom DROP COLUMN inMemory;
-- mucMember: Add new columns
ALTER TABLE mucMember ADD COLUMN firstName VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN lastName VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN url VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN email VARCHAR(100) NULL;
ALTER TABLE mucMember ADD COLUMN faqentry VARCHAR(100) NULL;
-- mucConversationLog: Add new index
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
-- Deletes no longer needed entries
DELETE FROM jiveID where idType = 3;
DELETE FROM jiveID where idType = 4;
-- Add jiveVersion table
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 1);
\ No newline at end of file
/* $RCSfile$ */
/* $Revision: 840 $ */
/* $Date: 2005-01-10 01:30:06 -0300 (Mon, 10 Jan 2005) $ */
/* upgrades from Wildfire 2.0.x to 2.1.0 */
/* jiveGroup: Recreate table from scratch */
DROP TABLE jiveGroup;
CREATE TABLE jiveGroup (
groupName NVARCHAR(50) NOT NULL,
description NVARCHAR(255),
CONSTRAINT group_pk PRIMARY KEY (groupName)
);
/* jiveGroupProp: Recreate table from scratch */
DROP TABLE jiveGroupProp;
CREATE TABLE jiveGroupProp (
groupName NVARCHAR(50) NOT NULL,
name NVARCHAR(100) NOT NULL,
propValue NVARCHAR(2000) NOT NULL,
CONSTRAINT jiveGroupProp_pk PRIMARY KEY (groupName, name)
);
/* jiveGroupUser: Recreate table from scratch */
DROP TABLE jiveGroupUser;
CREATE TABLE jiveGroupUser (
groupName NVARCHAR(50) NOT NULL,
username NVARCHAR(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupName, username, administrator)
);
/* mucRoom: Add new columns: "lockedDate" and "emptyDate". Rename column "invitationRequired" to "membersOnly". Delete columns: "lastActiveDate" and "inMemory". */
ALTER TABLE mucRoom ADD lockedDate CHAR(15) NOT NULL;
ALTER TABLE mucRoom ADD emptyDate CHAR(15) NULL;
ALTER TABLE mucRoom ADD membersOnly INT NOT NULL;
UPDATE mucRoom SET membersOnly = invitationRequired;
ALTER TABLE mucRoom DROP COLUMN invitationRequired;
ALTER TABLE mucRoom DROP COLUMN lastActiveDate;
ALTER TABLE mucRoom DROP COLUMN inMemory;
/* mucMember: Add new columns */
ALTER TABLE mucMember ADD firstName NVARCHAR(100) NULL;
ALTER TABLE mucMember ADD lastName NVARCHAR(100) NULL;
ALTER TABLE mucMember ADD url NVARCHAR(100) NULL;
ALTER TABLE mucMember ADD email NVARCHAR(100) NULL;
ALTER TABLE mucMember ADD faqentry NVARCHAR(100) NULL;
/* mucConversationLog: Add new index */
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
/* Deletes no longer needed entries */
DELETE FROM jiveID where idType = 3;
DELETE FROM jiveID where idType = 4;
/* Add jiveVersion table */
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 1);
\ No newline at end of file
-- $RCSfile$
-- $Revision: 1650 $
-- $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
-- upgrades from Wildfire 2.1.x to 2.2.0
-- Update jiveVersion to JM 2.2
UPDATE jiveVersion SET majorVersion=2, minorVersion=2;
-- jiveExtComponentConf: Create new table
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR(255) NOT NULL,
secret VARCHAR(255),
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
-- jiveRemoteServerConf: Create new table
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
-- mucRoomProp: Create new table
CREATE TABLE mucRoomProp (
roomID INTEGER NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(2000) NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
-- mucRoom: Add new columns: "useReservedNick", "canChangeNick" and "canRegister".
ALTER TABLE mucRoom ADD COLUMN useReservedNick INTEGER NOT NULL;
ALTER TABLE mucRoom ADD COLUMN canChangeNick INTEGER NOT NULL;
ALTER TABLE mucRoom ADD COLUMN canRegister INTEGER NOT NULL;
UPDATE mucRoom set useReservedNick=0, canChangeNick=1, canRegister=1;
-- jiveVCard: Recreate table from scratch
DROP TABLE jiveVCard;
CREATE TABLE jiveVCard (
username VARCHAR(32) NOT NULL,
value LONG VARCHAR NOT NULL,
CONSTRAINT jiveVCard_pk PRIMARY KEY (username)
);
// $RCSfile$
// $Revision: 1650 $
// $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
// upgrades from Wildfire 2.1.x to 2.2.0
// Update jiveVersion to JM 2.2
UPDATE jiveVersion SET majorVersion=2, minorVersion=2;
// jiveExtComponentConf: Create new table
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR(255) NOT NULL,
secret VARCHAR(255),
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
// jiveRemoteServerConf: Create new table
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
// mucRoomProp: Create new table
CREATE TABLE mucRoomProp (
roomID BIGINT NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
// mucRoom: Add new columns: "useReservedNick", "canChangeNick" and "canRegister".
ALTER TABLE mucRoom ADD COLUMN useReservedNick INTEGER DEFAULT 0 NOT NULL;
ALTER TABLE mucRoom ADD COLUMN canChangeNick INTEGER DEFAULT 1 NOT NULL;
ALTER TABLE mucRoom ADD COLUMN canRegister INTEGER DEFAULT 1 NOT NULL;
// jiveVCard: Recreate table from scratch
DROP TABLE jiveVCard;
CREATE TABLE jiveVCard (
username VARCHAR(32) NOT NULL,
value LONGVARCHAR NOT NULL,
CONSTRAINT jiveVCard_pk PRIMARY KEY (username)
);
# $RCSfile$
# $Revision: 1650 $
# $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
# upgrades from Wildfire 2.1.x to 2.2.0
# Update jiveVersion to JM 2.2
UPDATE jiveVersion SET majorVersion=2, minorVersion=2;
# jiveExtComponentConf: Create new table
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR(255) NOT NULL,
secret VARCHAR(255),
permission VARCHAR(10) NOT NULL,
PRIMARY KEY (subdomain)
);
# jiveRemoteServerConf: Create new table
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR(10) NOT NULL,
PRIMARY KEY (domain)
);
# mucRoomProp: Create new table
CREATE TABLE mucRoomProp (
roomID BIGINT NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
PRIMARY KEY (roomID, name)
);
# mucRoom: Add new columns: "useReservedNick", "canChangeNick" and "canRegister".
ALTER TABLE mucRoom ADD COLUMN useReservedNick TINYINT NOT NULL;
ALTER TABLE mucRoom ADD COLUMN canChangeNick TINYINT NOT NULL;
ALTER TABLE mucRoom ADD COLUMN canRegister TINYINT NOT NULL;
UPDATE mucRoom set useReservedNick=0, canChangeNick=1, canRegister=1;
# jiveVCard: Recreate table from scratch
DROP TABLE jiveVCard;
CREATE TABLE jiveVCard (
username VARCHAR(32) NOT NULL,
value TEXT NOT NULL,
PRIMARY KEY (username)
);
\ No newline at end of file
REM // $RCSfile$
REM // $Revision: 1650 $
REM // $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
REM // upgrades from Wildfire 2.1.x to 2.2.0
REM // Update jiveVersion to JM 2.2
UPDATE jiveVersion SET majorVersion=2, minorVersion=2;
REM // jiveExtComponentConf: Create new table
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR2(255) NOT NULL,
secret VARCHAR2(255),
permission VARCHAR2(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
REM // jiveRemoteServerConf: Create new table
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR2(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR2(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
REM // mucRoomProp: Create new table
CREATE TABLE mucRoomProp (
roomID INT NOT NULL,
name VARCHAR2(100) NOT NULL,
propValue VARCHAR2(1024) NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
REM // mucRoom: Add new columns: "useReservedNick", "canChangeNick" and "canRegister".
ALTER TABLE mucRoom ADD useReservedNick INTEGER NOT NULL;
ALTER TABLE mucRoom ADD canChangeNick INTEGER NOT NULL;
ALTER TABLE mucRoom ADD canRegister INTEGER NOT NULL;
UPDATE mucRoom set useReservedNick=0, canChangeNick=1, canRegister=1;
REM // jiveVCard: Recreate table from scratch
DROP TABLE jiveVCard;
CREATE TABLE jiveVCard (
username VARCHAR2(32) NOT NULL,
value LONG NOT NULL,
CONSTRAINT JiveVCard_pk PRIMARY KEY (username)
);
-- $RCSfile$
-- $Revision: 1650 $
-- $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
-- upgrades from Wildfire 2.1.x to 2.2.0
-- Update jiveVersion to JM 2.2
UPDATE jiveVersion SET majorVersion=2, minorVersion=2;
-- jiveExtComponentConf: Create new table
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR(255) NOT NULL,
secret VARCHAR(255),
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
-- jiveRemoteServerConf: Create new table
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
-- mucRoomProp: Create new table
CREATE TABLE mucRoomProp (
roomID INTEGER NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
-- mucRoom: Add new columns: "useReservedNick", "canChangeNick" and "canRegister".
ALTER TABLE mucRoom ADD COLUMN useReservedNick INTEGER NOT NULL;
ALTER TABLE mucRoom ADD COLUMN canChangeNick INTEGER NOT NULL;
ALTER TABLE mucRoom ADD COLUMN canRegister INTEGER NOT NULL;
UPDATE mucRoom set useReservedNick=0, canChangeNick=1, canRegister=1;
-- jiveVCard: Recreate table from scratch
DROP TABLE jiveVCard;
CREATE TABLE jiveVCard (
username VARCHAR(32) NOT NULL,
value TEXT NOT NULL,
CONSTRAINT jiveVCard_pk PRIMARY KEY (username)
);
/* $RCSfile$ */
/* $Revision: 1650 $ */
/* $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $ */
/* upgrades from Wildfire 2.1.x to 2.2.0 */
/* Update jiveVersion to JM 2.2 */
UPDATE jiveVersion SET majorVersion=2, minorVersion=2;
/* jiveExtComponentConf: Create new table */
CREATE TABLE jiveExtComponentConf (
subdomain NVARCHAR(255) NOT NULL,
secret NVARCHAR(255),
permission NVARCHAR(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
/* jiveRemoteServerConf: Create new table */
CREATE TABLE jiveRemoteServerConf (
domain NVARCHAR(255) NOT NULL,
remotePort INTEGER,
permission NVARCHAR(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
/* mucRoomProp: Create new table */
CREATE TABLE mucRoomProp (
roomID INT NOT NULL,
name NVARCHAR(100) NOT NULL,
propValue NVARCHAR(2000) NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
/* mucRoom: Add new columns: "useReservedNick", "canChangeNick" and "canRegister". */
ALTER TABLE mucRoom ADD useReservedNick INT NOT NULL;
ALTER TABLE mucRoom ADD canChangeNick INT NOT NULL;
ALTER TABLE mucRoom ADD canRegister INT NOT NULL;
UPDATE mucRoom set useReservedNick=0, canChangeNick=1, canRegister=1;
/* jiveVCard: Recreate table from scratch */
DROP TABLE jiveVCard;
CREATE TABLE jiveVCard (
username NVARCHAR(32) NOT NULL,
value NTEXT NOT NULL,
CONSTRAINT JiveVCard_pk PRIMARY KEY (username)
);
-- $RCSfile$
-- $Revision: 795 $
-- $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
-- upgrades from Wildfire 2.2.x to 2.4.0
-- Update jiveVersion to JM 2.4
UPDATE jiveVersion SET majorVersion=2, minorVersion=4;
-- jiveGroupUser: Alter length of username column
ALTER TABLE jiveGroupUser ALTER COLUMN username SET DATA TYPE VARCHAR(100);
\ No newline at end of file
// $RCSfile$
// $Revision: 795 $
// $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
// upgrades from Wildfire 2.2.x to 2.4.0
// Update jiveVersion to JM 2.4
UPDATE jiveVersion SET majorVersion=2, minorVersion=4;
// jiveGroupUser: Alter length of username column
ALTER TABLE jiveGroupUser ALTER COLUMN username VARCHAR(100) NOT NULL;
# $RCSfile$
# $Revision: 1650 $
# $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
# upgrades from Wildfire 2.2.x to 2.4.0
# Update jiveVersion to JM 2.4
UPDATE jiveVersion SET majorVersion=2, minorVersion=4;
# jiveGroupUser: Alter length of username column
ALTER TABLE jiveGroupUser CHANGE username username varchar(100) NOT NULL;
REM // $RCSfile$
REM // $Revision: 795 $
REM // $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
REM // upgrades from Wildfire 2.2.x to 2.4.0
REM // Update jiveVersion to JM 2.4
UPDATE jiveVersion SET majorVersion=2, minorVersion=4;
REM // jiveGroupUser: Alter length of username column
ALTER TABLE jiveGroupUser MODIFY username VARCHAR2(100) NOT NULL;
-- $RCSfile$
-- $Revision: 795 $
-- $Date: 2005-01-06 07:44:42 -0300 (Thu, 06 Jan 2005) $
-- upgrades from Wildfire 2.2.x to 2.4.0
-- Update jiveVersion to JM 2.4
UPDATE jiveVersion SET majorVersion=2, minorVersion=4;
-- jiveGroupUser: Alter length of username column
ALTER TABLE jiveGroupUser ALTER COLUMN username TYPE VARCHAR(100) NOT NULL;
\ No newline at end of file
/* $RCSfile$ */
/* $Revision: 840 $ */
/* $Date: 2005-01-10 01:30:06 -0300 (Mon, 10 Jan 2005) $ */
/* upgrades from Wildfire 2.2.x to 2.4.0 */
/* Update jiveVersion to JM 2.4 */
UPDATE jiveVersion SET majorVersion=2, minorVersion=4;
/* jiveGroupUser: Alter length of username column */
ALTER TABLE jiveGroupUser ALTER COLUMN username NVARCHAR(100) NOT NULL;
/* $RCSfile$ */
/* $Revision: 840 $ */
/* $Date: 2005-01-10 01:30:06 -0300 (Mon, 10 Jan 2005) $ */
/* upgrades from Wildfire 2.2.x to 2.4.0 */
/* Update jiveVersion to JM 2.4 */
UPDATE jiveVersion SET majorVersion=2, minorVersion=4;
/* jiveGroupUser: Alter length of username column */
ALTER TABLE jiveGroupUser MODIFY username NVARCHAR(100) NOT NULL;
-- $RCSfile$
-- $Revision: 1650 $
-- $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
CREATE TABLE jiveUser (
username VARCHAR(32) NOT NULL,
password VARCHAR(32) NOT NULL,
name VARCHAR(100),
email VARCHAR(100),
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
CONSTRAINT jiveUser_pk PRIMARY KEY (username)
);
CREATE INDEX jiveUsr_cDate_idx ON jiveUser (creationDate ASC);
CREATE TABLE jiveUserProp (
username VARCHAR(32) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(2000) NOT NULL,
CONSTRAINT jiveUsrProp_pk PRIMARY KEY (username, name)
);
CREATE TABLE jivePrivate (
username VARCHAR(32) NOT NULL,
name VARCHAR(100) NOT NULL,
namespace VARCHAR(200) NOT NULL,
value LONG VARCHAR NOT NULL,
CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace)
);
CREATE TABLE jiveOffline (
username VARCHAR(32) NOT NULL,
messageID INTEGER NOT NULL,
creationDate CHAR(15) NOT NULL,
messageSize INTEGER NOT NULL,
message LONG VARCHAR NOT NULL,
CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID)
);
CREATE TABLE jiveRoster (
rosterID INTEGER NOT NULL,
username VARCHAR(32) NOT NULL,
jid VARCHAR(1000) NOT NULL,
sub INTEGER NOT NULL,
ask INTEGER NOT NULL,
recv INTEGER NOT NULL,
nick VARCHAR(255),
CONSTRAINT jiveRoster_pk PRIMARY KEY (rosterID)
);
CREATE INDEX jiveR_userid_idx ON jiveRoster (username ASC);
CREATE TABLE jiveRosterGroups (
rosterID INTEGER NOT NULL,
rank INTEGER NOT NULL,
groupName VARCHAR(255) NOT NULL,
CONSTRAINT jiveRoGrps_pk PRIMARY KEY (rosterID, rank)
);
CREATE INDEX jiveRoGrps_rid_idx ON jiveRosterGroups (rosterID ASC);
CREATE TABLE jiveVCard (
username VARCHAR(32) NOT NULL,
value LONG VARCHAR NOT NULL,
CONSTRAINT jiveVCard_pk PRIMARY KEY (username)
);
CREATE TABLE jiveGroup (
groupName VARCHAR(50) NOT NULL,
description VARCHAR(255),
CONSTRAINT jiveGroup_pk PRIMARY KEY (groupName)
);
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(2000) NOT NULL,
CONSTRAINT jiveGrpProp_pk PRIMARY KEY (groupName, name)
);
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGrpUser PRIMARY KEY (groupName, username, administrator)
);
CREATE TABLE jiveID (
idType INTEGER NOT NULL,
id INTEGER NOT NULL,
CONSTRAINT jiveID_pk PRIMARY KEY (idType)
);
CREATE TABLE jiveProperty (
name VARCHAR(100) NOT NULL,
propValue VARCHAR(3000) NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR(255) NOT NULL,
secret VARCHAR(255),
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
-- MUC tables
CREATE TABLE mucRoom (
roomID INTEGER NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR(50) NOT NULL,
naturalName VARCHAR(255) NOT NULL,
description VARCHAR(255),
lockedDate CHAR(15) NOT NULL,
emptyDate CHAR(15) NULL,
canChangeSubject INTEGER NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom INTEGER NOT NULL,
moderated INTEGER NOT NULL,
membersOnly INTEGER NOT NULL,
canInvite INTEGER NOT NULL,
password VARCHAR(50) NULL,
canDiscoverJID INTEGER NOT NULL,
logEnabled INTEGER NOT NULL,
subject VARCHAR(100) NULL,
rolesToBroadcast INTEGER NOT NULL,
useReservedNick INTEGER NOT NULL,
canChangeNick INTEGER NOT NULL,
canRegister INTEGER NOT NULL,
CONSTRAINT mucRoom_pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomid_idx ON mucRoom (roomID);
CREATE TABLE mucRoomProp (
roomID INTEGER NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(2000) NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
CREATE TABLE mucAffiliation (
roomID INTEGER NOT NULL,
jid VARCHAR(1000) NOT NULL,
affiliation INTEGER NOT NULL,
CONSTRAINT mucAffiliation_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucMember (
roomID INTEGER NOT NULL,
jid VARCHAR(1000) NOT NULL,
nickname VARCHAR(255) NULL,
firstName VARCHAR(100) NULL,
lastName VARCHAR(100) NULL,
url VARCHAR(100) NULL,
email VARCHAR(100) NULL,
faqentry VARCHAR(100) NULL,
CONSTRAINT mucMember_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucConversationLog (
roomID INTEGER NOT NULL,
sender VARCHAR(1000) NOT NULL,
nickname VARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR(255) NULL,
body CLOB NULL
);
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
-- Finally, insert default table values
INSERT INTO jiveID (idType, id) VALUES (18, 1);
INSERT INTO jiveID (idType, id) VALUES (19, 1);
INSERT INTO jiveID (idType, id) VALUES (23, 1);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 2);
-- Entry for admin user
INSERT INTO jiveUser (username, password, name, email, creationDate, modificationDate)
VALUES ('admin', 'admin', 'Administrator', 'admin@example.com', '0', '0');
\ No newline at end of file
// $RCSfile$
// $Revision: 1650 $
// $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
CREATE TABLE jiveUser (
username VARCHAR(32) NOT NULL,
password VARCHAR(32) NOT NULL,
name VARCHAR(100),
email VARCHAR(100),
creationDate VARCHAR(15) NOT NULL,
modificationDate VARCHAR(15) NOT NULL,
CONSTRAINT jiveUser_pk PRIMARY KEY (username)
);
CREATE INDEX jiveUser_cDate_idx ON jiveUser (creationDate);
CREATE TABLE jiveUserProp (
username VARCHAR(32) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT jiveUserProp_pk PRIMARY KEY (username, name)
);
CREATE TABLE jivePrivate (
username VARCHAR(32) NOT NULL,
name VARCHAR(100) NOT NULL,
namespace VARCHAR(200) NOT NULL,
value LONGVARCHAR NOT NULL,
CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace)
);
CREATE TABLE jiveOffline (
username VARCHAR(32) NOT NULL,
messageID BIGINT NOT NULL,
creationDate VARCHAR(15) NOT NULL,
messageSize INTEGER NOT NULL,
message LONGVARCHAR NOT NULL,
CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID)
);
CREATE TABLE jiveRoster (
rosterID BIGINT NOT NULL,
username VARCHAR(32) NOT NULL,
jid VARCHAR(1024) NOT NULL,
sub INTEGER NOT NULL,
ask INTEGER NOT NULL,
recv INTEGER NOT NULL,
nick VARCHAR(255),
CONSTRAINT jiveRoster_pk PRIMARY KEY (rosterID)
);
CREATE INDEX jiveRoster_username_idx ON jiveRoster (username);
CREATE TABLE jiveRosterGroups (
rosterID BIGINT NOT NULL,
rank INTEGER NOT NULL,
groupName VARCHAR(255) NOT NULL,
CONSTRAINT jiveRosterGroups_pk PRIMARY KEY (rosterID, rank)
);
CREATE INDEX jiveRosterGroup_rosterid_idx ON jiveRosterGroups (rosterID);
CREATE TABLE jiveVCard (
username VARCHAR(32) NOT NULL,
value LONGVARCHAR NOT NULL,
CONSTRAINT jiveVCard_pk PRIMARY KEY (username)
);
CREATE TABLE jiveGroup (
groupName VARCHAR(50) NOT NULL,
description VARCHAR(255),
CONSTRAINT jiveGroup_pk PRIMARY KEY (groupName)
);
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT jiveGroupProp_pk PRIMARY KEY (groupName, name)
);
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupName, username, administrator)
);
CREATE TABLE jiveID (
idType INTEGER NOT NULL,
id BIGINT NOT NULL,
CONSTRAINT jiveID_pk PRIMARY KEY (idType)
);
CREATE TABLE jiveProperty (
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR(255) NOT NULL,
secret VARCHAR(255),
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
// MUC Tables
CREATE TABLE mucRoom (
roomID BIGINT NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR(50) NOT NULL,
naturalName VARCHAR(255) NOT NULL,
description VARCHAR(255),
lockedDate CHAR(15) NOT NULL,
emptyDate CHAR(15) NULL,
canChangeSubject INTEGER NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom INTEGER NOT NULL,
moderated INTEGER NOT NULL,
membersOnly INTEGER NOT NULL,
canInvite INTEGER NOT NULL,
password VARCHAR(50) NULL,
canDiscoverJID INTEGER NOT NULL,
logEnabled INTEGER NOT NULL,
subject VARCHAR(100) NULL,
rolesToBroadcast INTEGER NOT NULL,
useReservedNick INTEGER NOT NULL,
canChangeNick INTEGER NOT NULL,
canRegister INTEGER NOT NULL,
CONSTRAINT mucRoom_pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomid_idx ON mucRoom(roomID);
CREATE TABLE mucRoomProp (
roomID BIGINT NOT NULL,
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
CREATE TABLE mucAffiliation (
roomID BIGINT NOT NULL,
jid VARCHAR(1024) NOT NULL,
affiliation INTEGER NOT NULL,
CONSTRAINT mucAffiliation_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucMember (
roomID BIGINT NOT NULL,
jid VARCHAR(1024) NOT NULL,
nickname VARCHAR(255) NULL,
firstName VARCHAR(100) NULL,
lastName VARCHAR(100) NULL,
url VARCHAR(100) NULL,
email VARCHAR(100) NULL,
faqentry VARCHAR(100) NULL,
CONSTRAINT mucMember_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucConversationLog (
roomID BIGINT NOT NULL,
sender VARCHAR(1024) NOT NULL,
nickname VARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR(255) NULL,
body LONGVARCHAR NULL
);
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
// Finally, insert default table values.
INSERT INTO jiveID (idType, id) VALUES (18, 1);
INSERT INTO jiveID (idType, id) VALUES (19, 1);
INSERT INTO jiveID (idType, id) VALUES (23, 1);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 2);
// Entry for admin user
INSERT INTO jiveUser (username, password, name, email, creationDate, modificationDate)
VALUES ('admin', 'admin', 'Administrator', 'admin@example.com', '0', '0');
\ No newline at end of file
# $RCSfile$
# $Revision: 1650 $
# $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
CREATE TABLE jiveUser (
username VARCHAR(32) NOT NULL,
password VARCHAR(32) NOT NULL,
name VARCHAR(100),
email VARCHAR(100),
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
PRIMARY KEY (username),
INDEX jiveUser_cDate_idx (creationDate)
);
CREATE TABLE jiveUserProp (
username VARCHAR(32) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
PRIMARY KEY (username, name)
);
CREATE TABLE jiveGroup (
groupName VARCHAR(50) NOT NULL,
description VARCHAR(255),
PRIMARY KEY (groupName)
);
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
PRIMARY KEY (groupName, name)
);
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(32) NOT NULL,
administrator TINYINT NOT NULL,
PRIMARY KEY (groupName, username, administrator)
);
CREATE TABLE jivePrivate (
username VARCHAR(32) NOT NULL,
name VARCHAR(100) NOT NULL,
namespace VARCHAR(200) NOT NULL,
value TEXT NOT NULL,
PRIMARY KEY (username, name, namespace)
);
CREATE TABLE jiveOffline (
username VARCHAR(32) NOT NULL,
messageID BIGINT NOT NULL,
creationDate CHAR(15) NOT NULL,
messageSize INTEGER NOT NULL,
message TEXT NOT NULL,
PRIMARY KEY (username, messageID)
);
CREATE TABLE jiveRoster (
rosterID BIGINT NOT NULL,
username VARCHAR(32) NOT NULL,
jid TEXT NOT NULL,
sub TINYINT NOT NULL,
ask TINYINT NOT NULL,
recv TINYINT NOT NULL,
nick VARCHAR(255),
PRIMARY KEY (rosterID),
INDEX jiveRoster_unameid_idx (username)
);
CREATE TABLE jiveRosterGroups (
rosterID BIGINT NOT NULL,
rank TINYINT NOT NULL,
groupName VARCHAR(255) NOT NULL,
PRIMARY KEY (rosterID, rank),
INDEX jiveRosterGroup_rosterid_idx (rosterID)
);
CREATE TABLE jiveVCard (
username VARCHAR(32) NOT NULL,
value TEXT NOT NULL,
PRIMARY KEY (username)
);
CREATE TABLE jiveID (
idType INTEGER NOT NULL,
id BIGINT NOT NULL,
PRIMARY KEY (idType)
);
CREATE TABLE jiveProperty (
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
PRIMARY KEY (name)
);
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR(255) NOT NULL,
secret VARCHAR(255),
permission VARCHAR(10) NOT NULL,
PRIMARY KEY (subdomain)
);
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR(10) NOT NULL,
PRIMARY KEY (domain)
);
# MUC Tables
CREATE TABLE mucRoom (
roomID BIGINT NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR(50) NOT NULL,
naturalName VARCHAR(255) NOT NULL,
description VARCHAR(255),
lockedDate CHAR(15) NOT NULL,
emptyDate CHAR(15) NULL,
canChangeSubject TINYINT NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom TINYINT NOT NULL,
moderated TINYINT NOT NULL,
membersOnly TINYINT NOT NULL,
canInvite TINYINT NOT NULL,
password VARCHAR(50) NULL,
canDiscoverJID TINYINT NOT NULL,
logEnabled TINYINT NOT NULL,
subject VARCHAR(100) NULL,
rolesToBroadcast TINYINT NOT NULL,
useReservedNick TINYINT NOT NULL,
canChangeNick TINYINT NOT NULL,
canRegister TINYINT NOT NULL,
PRIMARY KEY (name),
INDEX mucRoom_roomid_idx (roomID)
);
CREATE TABLE mucRoomProp (
roomID BIGINT NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
PRIMARY KEY (roomID, name)
);
CREATE TABLE mucAffiliation (
roomID BIGINT NOT NULL,
jid TEXT NOT NULL,
affiliation TINYINT NOT NULL,
PRIMARY KEY (roomID,jid(70))
);
CREATE TABLE mucMember (
roomID BIGINT NOT NULL,
jid TEXT NOT NULL,
nickname VARCHAR(255) NULL,
firstName VARCHAR(100) NULL,
lastName VARCHAR(100) NULL,
url VARCHAR(100) NULL,
email VARCHAR(100) NULL,
faqentry VARCHAR(100) NULL,
PRIMARY KEY (roomID,jid(70))
);
CREATE TABLE mucConversationLog (
roomID BIGINT NOT NULL,
sender TEXT NOT NULL,
nickname VARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR(255) NULL,
body TEXT NULL,
INDEX mucLog_time_idx (time)
);
# Finally, insert default table values.
INSERT INTO jiveID (idType, id) VALUES (18, 1);
INSERT INTO jiveID (idType, id) VALUES (19, 1);
INSERT INTO jiveID (idType, id) VALUES (23, 1);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 2);
# Entry for admin user
INSERT INTO jiveUser (username, password, name, email, creationDate, modificationDate)
VALUES ('admin', 'admin', 'Administrator', 'admin@example.com', '0', '0');
\ No newline at end of file
REM // $RCSfile$
REM // $Revision: 1650 $
REM // $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
CREATE TABLE jiveUser (
username VARCHAR2(32) NOT NULL,
password VARCHAR2(32) NOT NULL,
name VARCHAR2(100),
email VARCHAR2(100),
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
CONSTRAINT jiveUser_pk PRIMARY KEY (username)
);
CREATE INDEX jiveUser_cDate_idx ON jiveUser (creationDate ASC);
CREATE TABLE jiveUserProp (
username VARCHAR2(32) NOT NULL,
name VARCHAR2(100) NOT NULL,
propValue VARCHAR2(1024) NOT NULL,
CONSTRAINT jiveUserProp_pk PRIMARY KEY (username, name)
);
CREATE TABLE jivePrivate (
username VARCHAR2(32) NOT NULL,
name VARCHAR2(100) NOT NULL,
namespace VARCHAR2(200) NOT NULL,
value LONG NOT NULL,
CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace)
);
CREATE TABLE jiveOffline (
username VARCHAR2(32) NOT NULL,
messageID INTEGER NOT NULL,
creationDate CHAR(15) NOT NULL,
messageSize INTEGER NOT NULL,
message LONG NOT NULL,
CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID)
);
CREATE TABLE jiveRoster (
rosterID INTEGER NOT NULL,
username VARCHAR2(32) NOT NULL,
jid VARCHAR2(1024) NOT NULL,
sub INTEGER NOT NULL,
ask INTEGER NOT NULL,
recv INTEGER NOT NULL,
nick VARCHAR2(255),
CONSTRAINT jiveRoster_pk PRIMARY KEY (rosterID)
);
CREATE INDEX jiveRoster_username_idx ON jiveRoster (username ASC);
CREATE TABLE jiveRosterGroups (
rosterID INTEGER NOT NULL,
rank INTEGER NOT NULL,
groupName VARCHAR2(255) NOT NULL,
CONSTRAINT jiveRosterGroups_pk PRIMARY KEY (rosterID, rank)
);
CREATE INDEX jiveRosterGroup_rosterid_idx ON jiveRosterGroups (rosterID ASC);
ALTER TABLE jiveRosterGroups ADD CONSTRAINT jiveRosterGroups_rosterID_fk FOREIGN KEY (rosterID) REFERENCES jiveRoster INITIALLY DEFERRED DEFERRABLE;
CREATE TABLE jiveVCard (
username VARCHAR2(32) NOT NULL,
value LONG NOT NULL,
CONSTRAINT JiveVCard_pk PRIMARY KEY (username)
);
CREATE TABLE jiveGroup (
groupName VARCHAR2(50) NOT NULL,
description VARCHAR2(255),
CONSTRAINT jiveGroup_pk PRIMARY KEY (groupName)
);
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR2(100) NOT NULL,
propValue VARCHAR2(4000) NOT NULL,
CONSTRAINT jiveGroupProp_pk PRIMARY KEY (groupName, name)
);
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR2(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGroupUser PRIMARY KEY (groupName, username, administrator)
);
CREATE TABLE jiveID (
idType INTEGER NOT NULL,
id INTEGER NOT NULL,
CONSTRAINT jiveID_pk PRIMARY KEY (idType)
);
CREATE TABLE jiveProperty (
name VARCHAR2(100) NOT NULL,
propValue VARCHAR2(4000) NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR2(255) NOT NULL,
secret VARCHAR2(255),
permission VARCHAR2(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR2(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR2(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
REM // MUC Tables
CREATE TABLE mucRoom(
roomID INT NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR2(50) NOT NULL,
naturalName VARCHAR2(255) NOT NULL,
description VARCHAR2(255),
lockedDate CHAR(15) NOT NULL,
emptyDate CHAR(15) NULL,
canChangeSubject INTEGER NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom INTEGER NOT NULL,
moderated INTEGER NOT NULL,
membersOnly INTEGER NOT NULL,
canInvite INTEGER NOT NULL,
password VARCHAR2(50) NULL,
canDiscoverJID INTEGER NOT NULL,
logEnabled INTEGER NOT NULL,
subject VARCHAR2(100) NULL,
rolesToBroadcast INTEGER NOT NULL,
useReservedNick INTEGER NOT NULL,
canChangeNick INTEGER NOT NULL,
canRegister INTEGER NOT NULL,
CONSTRAINT mucRoom_pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomid_idx ON mucRoom (roomID);
CREATE TABLE mucRoomProp (
roomID INT NOT NULL,
name VARCHAR2(100) NOT NULL,
propValue VARCHAR2(1024) NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
CREATE TABLE mucAffiliation (
roomID INT NOT NULL,
jid VARCHAR2(1024) NOT NULL,
affiliation INTEGER NOT NULL,
CONSTRAINT mucAffiliation_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucMember (
roomID INT NOT NULL,
jid VARCHAR2(1024) NOT NULL,
nickname VARCHAR2(255) NULL,
firstName VARCHAR2(100) NULL,
lastName VARCHAR2(100) NULL,
url VARCHAR2(100) NULL,
email VARCHAR2(100) NULL,
faqentry VARCHAR2(100) NULL,
CONSTRAINT mucMember_pk PRIMARY KEY (roomID, jid)
);
CREATE TABLE mucConversationLog (
roomID INT NOT NULL,
sender VARCHAR2(1024) NOT NULL,
nickname VARCHAR2(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR2(255) NULL,
body VARCHAR2(4000) NULL
);
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
REM // Finally, insert default table values.
INSERT INTO jiveID (idType, id) VALUES (18, 1);
INSERT INTO jiveID (idType, id) VALUES (19, 1);
INSERT INTO jiveID (idType, id) VALUES (23, 1);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 2);
REM // Entry for admin user
INSERT INTO jiveUser (username, password, name, email, creationDate, modificationDate)
VALUES ('admin', 'admin', 'Administrator', 'admin@example.com', '0', '0');
\ No newline at end of file
-- $RCSfile$
-- $Revision: 1650 $
-- $Date: 2005-07-20 00:18:17 -0300 (Wed, 20 Jul 2005) $
-- Note: This schema has only been tested on PostgreSQL 7.3.2.
CREATE TABLE jiveUser (
username VARCHAR(32) NOT NULL,
password VARCHAR(32) NOT NULL,
name VARCHAR(100),
email VARCHAR(100),
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
CONSTRAINT jiveUser_pk PRIMARY KEY (username)
);
CREATE INDEX jiveUser_cDate_idx ON jiveUser (creationDate);
CREATE TABLE jiveUserProp (
username VARCHAR(32) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
CONSTRAINT jiveUserProp_pk PRIMARY KEY (username, name)
);
CREATE TABLE jivePrivate (
username VARCHAR(32) NOT NULL,
name VARCHAR(100) NOT NULL,
namespace VARCHAR(200) NOT NULL,
value TEXT NOT NULL,
CONSTRAINT jivePrivate_pk PRIMARY KEY (username, name, namespace)
);
CREATE TABLE jiveOffline (
username VARCHAR(32) NOT NULL,
messageID INTEGER NOT NULL,
creationDate CHAR(15) NOT NULL,
messageSize INTEGER NOT NULL,
message TEXT NOT NULL,
CONSTRAINT jiveOffline_pk PRIMARY KEY (username, messageID)
);
CREATE TABLE jiveRoster (
rosterID INTEGER NOT NULL,
username VARCHAR(32) NOT NULL,
jid VARCHAR(1024) NOT NULL,
sub INTEGER NOT NULL,
ask INTEGER NOT NULL,
recv INTEGER NOT NULL,
nick VARCHAR(255),
CONSTRAINT jiveRoster_pk PRIMARY KEY (rosterID)
);
CREATE INDEX jiveRoster_username_idx ON jiveRoster (username);
CREATE TABLE jiveRosterGroups (
rosterID INTEGER NOT NULL,
rank INTEGER NOT NULL,
groupName VARCHAR(255) NOT NULL,
CONSTRAINT jiveRosterGroups_pk PRIMARY KEY (rosterID, rank)
);
CREATE INDEX jiveRosterGroups_rosterID_idx ON jiveRosterGroups (rosterID);
ALTER TABLE jiveRosterGroups ADD CONSTRAINT jiveRosterGroups_rosterID_fk FOREIGN KEY (rosterID) REFERENCES jiveRoster INITIALLY DEFERRED DEFERRABLE;
CREATE TABLE jiveVCard (
username VARCHAR(32) NOT NULL,
value TEXT NOT NULL,
CONSTRAINT jiveVCard_pk PRIMARY KEY (username)
);
CREATE TABLE jiveGroup (
groupName VARCHAR(50) NOT NULL,
description VARCHAR(255),
CONSTRAINT jiveGroup_pk PRIMARY KEY (groupName)
);
CREATE TABLE jiveGroupProp (
groupName VARCHAR(50) NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
CONSTRAINT jiveGroupProp_pk PRIMARY KEY (groupName, name)
);
CREATE TABLE jiveGroupUser (
groupName VARCHAR(50) NOT NULL,
username VARCHAR(32) NOT NULL,
administrator INTEGER NOT NULL,
CONSTRAINT jiveGroupUser_pk PRIMARY KEY (groupName, username, administrator)
);
CREATE TABLE jiveID (
idType INTEGER NOT NULL,
id INTEGER NOT NULL,
CONSTRAINT jiveID_pk PRIMARY KEY (idType)
);
CREATE TABLE jiveProperty (
name VARCHAR(100) NOT NULL,
propValue VARCHAR(4000) NOT NULL,
CONSTRAINT jiveProperty_pk PRIMARY KEY (name)
);
CREATE TABLE jiveVersion (
majorVersion INTEGER NOT NULL,
minorVersion INTEGER NOT NULL
);
CREATE TABLE jiveExtComponentConf (
subdomain VARCHAR(255) NOT NULL,
secret VARCHAR(255),
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveExtComponentConf_pk PRIMARY KEY (subdomain)
);
CREATE TABLE jiveRemoteServerConf (
domain VARCHAR(255) NOT NULL,
remotePort INTEGER,
permission VARCHAR(10) NOT NULL,
CONSTRAINT jiveRemoteServerConf_pk PRIMARY KEY (domain)
);
-- MUC Tables
CREATE TABLE mucRoom (
roomID INTEGER NOT NULL,
creationDate CHAR(15) NOT NULL,
modificationDate CHAR(15) NOT NULL,
name VARCHAR(50) NOT NULL,
naturalName VARCHAR(255) NOT NULL,
description VARCHAR(255),
lockedDate CHAR(15) NOT NULL,
emptyDate CHAR(15) NULL,
canChangeSubject INTEGER NOT NULL,
maxUsers INTEGER NOT NULL,
publicRoom INTEGER NOT NULL,
moderated INTEGER NOT NULL,
membersOnly INTEGER NOT NULL,
canInvite INTEGER NOT NULL,
password VARCHAR(50) NULL,
canDiscoverJID INTEGER NOT NULL,
logEnabled INTEGER NOT NULL,
subject VARCHAR(100) NULL,
rolesToBroadcast INTEGER NOT NULL,
useReservedNick INTEGER NOT NULL,
canChangeNick INTEGER NOT NULL,
canRegister INTEGER NOT NULL,
CONSTRAINT mucRoom__pk PRIMARY KEY (name)
);
CREATE INDEX mucRoom_roomID_idx ON mucRoom(roomID);
CREATE TABLE mucRoomProp (
roomID INTEGER NOT NULL,
name VARCHAR(100) NOT NULL,
propValue TEXT NOT NULL,
CONSTRAINT mucRoomProp_pk PRIMARY KEY (roomID, name)
);
CREATE TABLE mucAffiliation (
roomID INTEGER NOT NULL,
jid VARCHAR(1024) NOT NULL,
affiliation INTEGER NOT NULL,
CONSTRAINT mucAffiliation__pk PRIMARY KEY (roomID,jid)
);
CREATE TABLE mucMember (
roomID INTEGER NOT NULL,
jid VARCHAR(1024) NOT NULL,
nickname VARCHAR(255) NULL,
firstName VARCHAR(100) NULL,
lastName VARCHAR(100) NULL,
url VARCHAR(100) NULL,
email VARCHAR(100) NULL,
faqentry VARCHAR(100) NULL,
CONSTRAINT mucMember__pk PRIMARY KEY (roomID,jid)
);
CREATE TABLE mucConversationLog (
roomID INTEGER NOT NULL,
sender VARCHAR(1024) NOT NULL,
nickname VARCHAR(255) NULL,
time CHAR(15) NOT NULL,
subject VARCHAR(255) NULL,
body TEXT NULL
);
CREATE INDEX mucLog_time_idx ON mucConversationLog (time);
-- Finally, insert default table values.
INSERT INTO jiveID (idType, id) VALUES (18, 1);
INSERT INTO jiveID (idType, id) VALUES (19, 1);
INSERT INTO jiveID (idType, id) VALUES (23, 1);
INSERT INTO jiveVersion (majorVersion, minorVersion) VALUES (2, 2);
-- Entry for admin user
INSERT INTO jiveUser (username, password, name, email, creationDate, modificationDate)
VALUES ('admin', 'admin', 'Administrator', 'admin@example.com', '0', '0');
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
......@@ -13,7 +13,7 @@ package org.jivesoftware.admin;
import org.jivesoftware.util.ClassUtils;
import org.jivesoftware.util.Log;
import org.jivesoftware.messenger.XMPPServer;
import org.jivesoftware.wildfire.XMPPServer;
import org.dom4j.Document;
import org.dom4j.Element;
import org.dom4j.DocumentFactory;
......@@ -140,7 +140,7 @@ public class AdminConsole {
return globalVersion.getText();
}
else {
// Default to the Jive Messenger version if none has been provided via XML.
// Default to the Wildfire version if none has been provided via XML.
XMPPServer xmppServer = XMPPServer.getInstance();
return xmppServer.getServerInfo().getVersion().getVersionString();
}
......@@ -170,7 +170,7 @@ public class AdminConsole {
// Load the core model as the admin-sidebar.xml file from the classpath.
InputStream in = ClassUtils.getResourceAsStream("/admin-sidebar.xml");
if (in == null) {
Log.error("Failed to load admin-sidebar.xml file from Jive Messenger classes - admin "
Log.error("Failed to load admin-sidebar.xml file from Wildfire classes - admin "
+ "console will not work correctly.");
return;
}
......
......@@ -735,9 +735,9 @@ public class DbConnectionManager {
BufferedReader in = null;
Statement stmt;
try {
// Resource will be like "/database/upgrade/2.0_to_2.1/messenger_hsqldb.sql"
// Resource will be like "/database/upgrade/2.0_to_2.1/wildfire_hsqldb.sql"
String resourceName = "/database/upgrade/" + CURRENT_MAJOR_VERSION + "." + i +
"_to_" + CURRENT_MAJOR_VERSION + "." + (i+1) + "/messenger_" +
"_to_" + CURRENT_MAJOR_VERSION + "." + (i+1) + "/wildfire_" +
databaseType + ".sql";
in = new BufferedReader(new InputStreamReader(
DbConnectionManager.class.getResourceAsStream(resourceName)));
......
This diff is collapsed.
This diff is collapsed.
<body>
Jive Messenger is an open-source XMPP server.
Wildfire is an open-source XMPP server.
</body>
\ No newline at end of file
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment