I have installed openfire on windows machine and pointing to our mysql database.I have created test users in openfire and testing with xmpp client on my machine . Everything is working fine.
I have opened our mysql database and seen so many tables are created from openfire where tablename starts with of like for example ofuser which stores user registration information.
Now instead of storing user registration information in ofuser ,I want to store user registration information in my custom table like for example chat_registrations.
Is it possible in openfire, if so how to do it?
You can do it but for this you have to modify openfire from source and build the system for yourself. To do this fork openfire from github, clone your repository in pc, open source code with you favourite IDE, then modify openfire's sql queries related to ofUser table. You will get them in src/database/openfire*.sql . Build the modified system and install it to server.
Related
I am working on a Linux, Apache2, MySQL and PHP server setup currently. I have a dynamic website up and running. I want to create a register / sign-in portal. How would I go about creating a user authentication using PHP and MySQL? I can't find anything on Stack Overflow, and I've searched over google but I'm only finding outdated information.
I have been using the normal javascript ajax chat i created manually. I also used this same format to create phone android messenger app. But it was using normal sockets.
so i have migrated to using ejabberd IM server and have developed the xmpp client messenger and it is working well with mysql module configurations.
But now i have history chats for messages by users and want to maintain the message. So i want to transfer these messages to the new database table called archive under ejabberd.
I have failed import the messages as they are very many in thousands.
so if some one know a script i can use to do the migration of data to the new database that will be good.
To my knowledge, there is not template migration script you can adapt already, but that would make a good contribution for ejabberd.
I have built a Joomla site for a client on a development server. It soon needs migrating to the client's Live site, which will mean a URL change as well as a physical server change.
I'm new to Joomla, but having worked a lot on WordPress previously I know it's a piece of cake to migrate one WP site to another, especially with the dozen or so available plugins.
However, this doesn't appear to be so easy on Joomla. I have searched for the best practice to achieve this with Joomla 3 but cannot find what I need.
Does anyone have a suggestion for this?
There are in fact a two ways to achieve this and they are quite easy.
1. The first one is the manual way, that is:
Copy the files of your local joomla installation and upload them to
your server
Export your local database and import it on your server.
Edit the configuration.php file to your new server credentials -db
name, db user, db server etc.
2. The second one is through the akeeba backup component.
In this case you create a backup and then restore it on the remote
server. Detailed info
here.
After uploading your remote site you are advised to follow these
guidelines
to secure your installation.
Recently I installed openstack trove using the automated script (devstack). After it is installed successfully and creating some user and projects, I manged to create a database instance and database inside it. unfortunately every database instance that I am going to build (via command line or horizon dashboard) trove gave me error status. Therefore when I tried to create database inside each of created database instance I stock with database instance is not ready.
I did some google and some people mentioned that I should check nova-compute.log, but unfortunately I did not find this log file. Would you please guide me?
Regards.
If you are running devstack it creates a screen session for all the services and it contains the logs. Try running "screen -x" to attach to the screen session and you can view the logs from there. Each window within the screen session is a separate service running.
If you had an issue creating an instance from trove it maybe because the image you are using is not setup correctly for trove because it needs the trove guest agent installed and a configuration for the guest agent baked in the image.
We have a repo that uses devstack to create a development trove installation that might be of use to test things out. This readme should help getting you started.
https://github.com/openstack/trove-integration/blob/master/README.md
Is there an up-to-date, complete guide on moving a Liferay Portal ?
How am I supposed to migrate a Portal to another Server in an efficient and safe way ?
I've been developing a Portal, connecting to a mySQL database. Then, I had to move both the portal and database to another Server.
So I did the following steps, pretty identical to this guide
export the mySQL Db and import it in the new Server. The data are moved correctly, as I've checked them manually
Copy a new (clean) copy of the Liferay Portal to the new server
copy the data folder
copy portal-ext.properties, then edit the db url and login credentials
Copy the portal-setup-wizard.properties, then change the 'liferay.home' param to the correct portal path
I run the server and my admin has the default 'test' password instead of the one I used before the migration
then I see that Can't have access to the previous content, like Users, UserGroups, Pages, etc. I Also tried re-indexing the database entries (Users and Organizations, Web Content etc). Again nothing
I also Tried copying the whole Portal, and only changing the .properties files to target the new database and portal path. Again the same problems, no Content from the old portal. It's like I started a fresh portal
So what did I do wrong this time ?
Used Liferay 6.1.0 ce ga1
I failed migrating the portal and had to create it from scratch. Almost 1 year later, i found out what caused the problem. Here it is. To be fair, it's a MySQL issue, not Liferay
The MySql database, since it got ported from a windows server to a Linux one, was exported with table names in Uppercase. When Liferay tries to connect to the database, it will not find the Liferay Model's tables, and will create new ones. Practically Liferay treats the Database as an empty one, and it starts as a fresh portal. I only found that, while exploring the database sometime later, and found out I had each Liferay Table both in uppercase and lowercase.
More info and solutions can be found here