Whoops, disregard the comment about SparkManager, seems like you’'re already on it.
Wimnms: renaming the database files to wildfire.* worked for us.
Thanks guys. I’'m going to create a knowledge base article with the update instructions so people can easily find the required info for the upgrade.
Regards,
– Gato
Wimnms: renaming the database files to wildfire.* worked for us.
Great!
I’'ll try it out this weekend or early yawn Monday morning.
BTW, I think I still noticed some jive-messenger references somewhere… I will have to go try to look for them again.
P.S. Nice logo
After a couple hours renaming, moving around stuff, altering databases, and updating scripts, it all works.
Hmmm, where’'s the cool new logo in the Admin Console?
Hey Cliff,
Glad to hear that it’'s working fine. For people that need to upgrade their installation to Wildfire, they can follow the instructions described in the following url=http://www.jivesoftware.org/community/entry.jspa?externalID=481&categoryID=2 2kb document[/url].
Regards,
– Gato
Hey guys,
SparkManager plugin has been updated. You can now download it again and enjoy it.
Regards,
– Gato
i’'m suing jive-messengerd to startup JM on reboot. There are environment paths pointing to MESSENGER, so i would have to change them to WILDFIRE?
#!/bin/sh
export JAVA_HOME=/opt/java/jre
- jive-messengerd
-
chkconfig: 2345 20 80
-
description: Used to start and stop the jive messenger XMPP server
-
Script used to start jive messenger 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 $MESSENGER_HOME/bin/messenger is
-
executable by the user you want to run messenger as
-
(chmod +x $MESSENGER_HOME/bin/messenger)
-
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.d
-
ln -s …/init.d/jive-messengerd $90jive-messengerd
-
Set this to tell this script where messenger lives
-
If this is not set the script will look for /opt/jive_messenger, then /usr/local/jive_messenger
#export MESSENGER_HOME=
-
If there is a different user you would like to run this script as,
-
change the following line
export MESSENGER_USER=jive
-
-
If a messenger home variable has not been specified, try to determine it
if ; 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"
else
echo “Could not find Jive Messenger installation under /opt or /usr/local”
echo “Please specify the Jive Messenger installation location in environment variable MESSENGER_HOME”
exit 1
fi
fi
function execCommand() {
OLD_PWD=pwd
cd $MESSENGER_HOME/bin
CMD="./messenger $1 >/dev/null"
su -c “$CMD” $MESSENGER_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
/code
Hmm… I just re-downloaded spark manager, and the page fed me sparkmanager_1_0_1.zip. I uncompressed the jar to my plugins directory, but Wildfire didn’‘t pick it up. I had to remove the old “sparkmanager” directory in the plugins directory and then restart Wildfire before it would take it. I assume this is because the version number of sparkmanager didn’'t change?
Graeme
Wimnms: renaming the database files to wildfire.* worked for us.
I’'ll try it out this weekend or early yawn Monday morning.
All happy now as of Monday morning Only had to kick one person off when I did it (it was early).
Yeah, life is good.
Thx. It works. But I have another problem, the big one. I posted as new thread with subject “Strage Behaviour with jabber clients connect to Wildfire server” (http://www.jivesoftware.org/community/click.jspa?searchID=72434&messageID=109094).
What does this mean?
wildfire-service.exe.vmoptions
I cannot find any references to this in the file system or database. I have skipped that step in the install and it seems to be working.
Also, is there any way to tell if Wildfire successfully upgraded the database? I am running Wildfire on Windows Server 2003 connecting to SQL 2000 database.
Any help would be greatly appreciated.
wildfire-service.exe.vmoptions
I cannot find any references to this in the file
system or database. I have skipped that step in the
install and it seems to be working.
It’‘s fully optional, so you can skip it. You’'ll only need to create that file when you have a lot of users and need to do some performance tuning.
Also, is there any way to tell if Wildfire
successfully upgraded the database? I am running
Wildfire on Windows Server 2003 connecting to SQL
2000 database.
If the app is working, you can assume it updated the database. It should have printed a log message to the logs as well.
Regards,
Matt