Вдогонку к посту victorae
http://community.livejournal.com/ru_jabber/19425.html
http://community.livejournal.com/ru_jabber/19425.html
MAVrADMIN
victorae
Миранда - окно регистрации не прокручивается, хотя вслепую править поля можно
Сам JMC показывает только последнее непрочитанное письмо
проблемы с установкой Java машины, не хватает каких-то файлов
Openfire стал гнать не подетски,подскажите как его полностью переустановить, с сохранением юзверей и групп?
Openfire стал гнать не подетски,подскажите как его полностью переустановить, с сохранением юзверей и групп?
1. Stop Wildfire.
2. Backup the Wildfire installation directory. This step is critical because the data will be overwritten with the new RPM install.
3. Backup the Wildfire database. Note that the embedded database is backed up in step 2.
4. Install the RPM.
5. Copy the conf directory from the backup to the installation directory.
6. Copy the embedded-db directory from the backup to the installation directory.
7. Copy the enterprise directory from the backup to the installation directory, if it exists.
8. Copy the plugins directory from the backup to the installation directory except for plugins/admin.
9. Copy the resources/security/keystore file from the backup to the installation directory.
10. Copy the resources/security/truststore file from the backup to the installation directory if you modified this file.
11. Start Wildfire.
апгрейд я уже делал,,,не помогло
я хочу полностью переставить все компоненты программы,,,,,только чтобы сохранились юзверы и группы,,,чтобы мне не перезаводить все заново --а это без малого 190 пользователей.
если глюки после переустановки полезут снова, значит сноси и базу
забэкапь только таблицу пользователей
Люди добрые, подскажте, какую кодировку выставить в настройках IM Gateway'а, а то принимаю от асечных юзеров кракозябры. По дефолту стоит iso-8859-1.
Помогите, столкнулся с проблемой, не устанавливаются плагины.
Скачивал в ручную, клал в папку плагинов, он в ней распаковывается, и на етом все.
java.lang.NoClassDefFoundError: org/jivesoftware/wildfire/container/Plugin
Никаких обновлений не делалось
Да работает
"OpenFire home page"
This document provides the steps to follow in order to upgrade a Wildfire 3.2 installation into an Openfire installation. If you need to update an old version of Wildfire then first update it to Wildfire 3.2 using the Wildfire Upgrade Guide and the Upgrade guide to Wildfire Enterprise 3.2.0 if you are using the Enterprise Edition.
Windows
1) Stop the server
2) Back up setup
3) If running as a service then remove old service: wildfire-service /uninstall
4) Install 3.3.0
5) Delete conf/openfire.xml and rename conf/wildfire.xml to conf/openfire.xml
6) Search for org.jivesoftware.wildfire. and replace with org.jivesoftware.openfire. in conf/openfire.xml
7) If using embedded database then rename embedded-db\wildfire* files to embedded-db\openfire*
8) Delete all jar files in the plugin folder and drop new versions of plugins
9) Start up the server using new launch scripts localted in bin
10) Optionally install as a service again: openfire-service /install
Unix/Linux (RPM)
1) Stop the server
2) Back up setup
3) Run rpm -ivf openfire_3_3_0.rpm
4) Go to /opt/openfire and copy configuration from old setup
4.1) Copy conf/wildfire.xml and rename it to conf/openfire.xml
4.2) Search for org.jivesoftware.wildfire. and replace with org.jivesoftware.openfire. in conf/openfire.xml
4.3) If using embedded database then copy and rename embedded-db\wildfire* files to embedded-db\openfire*
4.4) Copy new version of plugins to opt/openfire/plugins (except admin folder)
4.5) Copy old certificates from resources/security/ to same location in openfire
5) If running as a service update service to use new scripts located in bin
6) Start up the server using new launch scripts located in bin
7) To uninstall Wildfire run rpm -e wildfire
Zip/Tar.gz
This process is similar to the RPM except that step 3 is replaced with:
3) Unzip content to /opt/openfire (unix/linux)
3) Unzip content to C:\Program Files\openfire (windows)
Mac
1. Install Openfire using the .pkg installer
2. Use the System Preferences pane to turn Openfire off
3. For steps 4-8 assume paths are relative to /usr/local
4. Copy wildfire/conf/wildfire.xml to openfire/conf/openfire.xml
5. Search for org.jivesoftware.wildfire. and replace with org.jivesoftware.openfire. in conf/openfire.xml
6. If using embedded database then copy and rename embedded-db\wildfire* files to embedded-db\openfire*
7. Copy new version of plugins to openfire/plugins (except admin folder)
8. Copy old certificates from resources/security/ to same location in openfire
9. Use the System Preferences pane to turn Openfire back on
Если в логон скрипт засунуть
куда рыть?
переставил openfire полностью,,,только в этот раз базу сделал mysql а не встроенню,,
но вотпроблема сразу дала о себе знать,,,все контакты в листе вопросами!!?
CREATE DATABASE my_database DEFAULT CHARACTER SET utf8;
Using MySQL and Unicode with Wildfire
Author: Greg Unrein, Created on: Jan 18, 2006 4:04 PM
Introduction
Until recently, MySQL did not have proper Unicode support, which made supporting postings in non-Western languages difficult. By configuring Wildfire correctly it is possible to work around this limitation.
Symptoms
Unicode characters are garbled.
Resolution
In order for character encodings to work correctly with MySQL, Wildfire administrators will need to specify the encoding in two places.
First, in the JDBC URL for MySQL add "characterEncoding={character set}" to the end of the URL as a parameter. The character set in this case should be the one for MySQL and not for Wildfire. For example, if UTF-8 is being used in the Wildfire then utf8 is the correct character set to specify since this is the character set that MySQL expects. This setting is only used to establish the JDBC connection with the MySQL server. The complete JDBC URL for the example above is:
jdbc:mysql://{host name}:{port}/{database name}?characterEncoding=utf8
You can get a list of MySQL character sets in the MySQL console by running typing this command:
SHOW CHARACTER SET;
Next, the MySQL JDBC driver has a workaround which should be enabled by adding
<mysql>
<useUnicode>true</useUnicode>
</mysql>
to the <database> section of the config.xml file.
Note: Changes to config.xml should be done with Wildfire stopped.
Community powered by the Integrated Server from Jive Software.
Страницы: 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
Предыдущая тема: Делаю комп.класс, возникают проблемы, помогите решить.