I got a DOTNETNUKE project. I am new to DOTNETNUKE. My client has given me the files and folder with Database(say abc.mdf). I was said to upgrade their developed site from version 6 to latest version v7.0. The issue when upgrading is "How to map the latest version to existing Database?" ie: when I installed v7.0 in my system, it creates new database with 137 default tables. How am I supposed to map those 137 default tables, stored procedures, etc to existing database(abc.mdf) so that up-gradation happens easily with database.
I didn't find a proper solution for that..
Can anyone help me?
Thanks in advance.
No need to map any tables OR files from new version to old version. Just follow up below steps to upgrade DNN website from old to new one. Here is the reference link.
Download 7.4.0 - Version Upgrade file from here.
Extract downloaded Zip file to root of your existing old version of DNN website. It is replacing all your old files with new one.
Run your website.
When you run your website, it will be automatically redirect to Upgrade Wizard page.
Just provide your HOST Username/Password and Click on Install button.
Now it will start process of mapping your old database tables & store procedures with new one.
After complete the process to 100%, click on Visit Website button.
Done. Your website updated.
Please let me know if you have any questions.
DNN will do all that for you.
Extract the UPGRADE package over your existing site. Hit the site, login as host, run the Upgrade.
I'm working with multiple Liferay Projects (different Portal, plugins, user and usergroups etc ) in the same time, and often have to switch between them. This switch requires lots of steps like
Editing the portal-ext.properties (to change the Liferay Database, and edit some custom project-specific properties), and edit 'portal-setup-wizard.properties'
Add/remove portlets themes and hooks from the Eclipse Server instance, sometimes clean the Tomcat's 'data' 'Webapps' and 'work' folder
Go to Liferay's Control-Panel/Server/Plugins Installation and re-index portlets like 'Users and Organizations' or 'Documents and Media'
So, I thought that creating a new Server Instance for each project, with a new tomcat and JRE, would be a nice idea. When I had to switch project, I could just stop the old server and start another. At first, I thought (was adviced actually) that using the same Liferay Plugins SDK (6.1.0), should be ok, as long as the Server instances are the same version.
Practically this doesn't work 100% perfectly. While most of the work is getting done, there are some problems here and there, like a theme not getting deployed propertly, hooks not beeing applied etc. As I understand, there is some [Liferay SDK] - [Liferay Server] binding, and that means that only 1 Server (the first one I created) will fully work.
For example, By investigating the [Liferay SDK folder]/bild.[user name].properties, I can see some properties that are referring to a specific Server/JRE location :
app.server.portal.dir
app.server.lib.global.dir
app.server.deploy.dir
app.server.type
app.server.dir
So, my question is, what should I do to work with multiple Liferay Projects ?
Is the multi-Server practice, a good approach to work with multiple-projects ?
If yes, should I create a different SDK for each Server? Maybe a different Eclipse workspace too ? Or is there some way to use the same SDK
What about working with Servers of different Liferay Version ?
Personally, I set up every project with its own source, tomcat, database, etc. even if it means duplication. These days storage is cheap and makes this possible. Of course your milage may very but I thought I'd share my setup with you.
I have a project directory with all my projects which looks like so:
/projects
/foo-project
/bar-project
/my-project
Inside a project I have
/my-project
/tomcat
/bin
/conf
...
/src
/portal
... my portal source ...
/plugins
... my plugin source ...
/portal-ext.properties
I then setup tomcat to use different ports (8080, 8081, 8082, etc...) so that I can just leave them all running if I have to or want to.
I setup Liferay to use different database for each Liferay instance.
I place the portal-ext.properties as a sibling to the tomcat directory and Liferay will read this file (assuming the default behavior). This offers quick and easy edits as well as figuring out how you've set each project up.
The advantages should be clear. You can just "walk away" from a project and into another without tearing down and setting up. And when you return everything will still be as you left it. Context switching is also quicker and helpful if you want to answer a question about a project you're not yet working on.
Depending on the complexity of each of your projects, multi-instance might not work for you. Hooks and EXTs may conflict with each other and it appears as if this is already the case with your projects.
If you can afford the space (which is not much) this has been the fastest way I have found as a Liferay developer.
If we start working on a new Liferay project in our company, we setup:
a new database schema,
a new, clean Liferay server connected with that schema and
a fresh Eclipse workspace, with
a clean SDK project
Only this way you're sure to have cleanly separate projects. To switch to another project, just shutdown the current Liferay server, startup the new one and switch to the right workspace in Eclipse. This all takes no more than 2 minutes, a lot less than to do all the cleanup actions you have to do if you share workspace and server.
In my opinion, this is the approach of most development teams.
Why mess with all these complications in a single computer? I use Oracle VirtualBox and set up a separate VM for each project. Even though I work on a laptop, it has 8 cores, and I've bumped my memory up to 16GB and set each machine up with 4GB of RAM.
I can have multiple VMs running at once and have set all active projects as home pages in Chrome. Using bridged networking each VM has its own IP address, and they all listen on 8080.
Another benefit is that, although my primary project is being developed using Eclipse Indigo and LR 6.1 CE GA1, I have another using Eclipse Juno, its specific IDE plugin and LR 6.1.1 CE GA2. So it also works as a new version tester.
VirtualBox is free. Memory is cheap. And remember that you can put a VM to sleep without shutting it down. That takes about 10-20 seconds and waking it up again takes 30-60 seconds.
The simplest solution would be :
Create 3 different users, the Liferay SDK's bundle.properties file is separate for each user. So, lets say, if you want to run 3 servers with the same sdk. Create 3 files like
bundle.user1.properties
bundle.user2.properties
bundle.user3.properties
Now, when you want to deploy something for server 1, log in the server using user1 and try to deploy the portlet, this will read bundle.user1.properties and it will deploy the portlet/hook to the specified location.
Hope this will resolve your deployment issue.
Also, when you have 3 users, you can run 3 different servers together in a different user accounts, in this way, they would be secure and apart from admin, nobody can shutdown the same.
Hope this helps!
I need to make an upgrade of Liferay, as mentioned above(5.2->6.0) So far, as my research (1,2,3) shows I need to:
Make backups of the Database and file system of plugins (especially portal*.properties).
Overwrite dependency jars
Deploy new .war
Set permission algorithm to 5 in the properties (as L-5.2 uses it, however L-6.0 uses 6)
Start application,
see if the DB updates correctly
see if the portal is working correctly
Clean up user-specific permissions
Convert legacy permission algorithm to 6 in the control Panel
Migrate a custom theme.
Upgrade EXT to EXT Plugin(p. 398)
It's fairly understandable, but I stumbled upon this thread(Missing FileEntryForm class). Are there any more changes of this kind?
Also, is there something else I'm missing?
Thanks :)
Liferay migration from one server to another help required. Can anyone share there steps for migration of Liferay portal 5.2.3 from one server to another. I am using Windows + Tomcat + MySql.
I have uploaded whole tomcat folder to the new windows machine and imported the database too with the corresponding change to the configuration file like Database details.
But after starting the tomcat server it is showing some error like "Unable to load repository http://plugins.liferay.com". Any idea why I am getting this error ?
These are the steps that I have followed and able to migrate the Liferay successfully:
Take the backup of Liferay files and database from first windows machine.
Install the same version of Liferay (Say Liferay 5.2.3) on second windows machine.
Shut down Liferay.
Import the database on new system.
Add portal-ext.properties with relevant entries. (e.g Datbase Name, User Name , Pasword etc)
Add \liferay-portal-5.2.3\data\document_library files from old machine.
Start the tomcat. It will automtically do the rest.
NOTE: In the above method I have not deployed Theme and custom plugins etc, you have to deploy Theme and custom plugins also that are used on old system.
Lifery is trying to connect to plugin repository to find whether there are updates for plugins.
Does your new machine have internet conectivity?
Also you have options to ignore that message or configure liferay not to check for updates.
For later put in portal-ext.properties
plugin.repositories.trusted=
plugin.repositories.untrusted=
UPDATE:
If behind proxy create (if not existent) system-ext.properties (beside portal-ext.properties) and add
com.liferay.util.Http.proxy.host=proxy_host
com.liferay.util.Http.proxy.port=proxy_port
Change proxy_host and proxy_port with your values.
Also remove from portal-ext.properties if you want liferay to check repositories
plugin.repositories.trusted=
plugin.repositories.untrusted=
After you have installed SharePoint you need to run the configuration wizard which typically asks what your Database server is what DB Name to use, what port to use for Central Admin, etc. Then it goes through its 1-9 install process...
Our problem is on one of our servers, which has a clean database, clean 12 hive, and no answer file is to be found (nor should it), the Configuration Wizard goes straight through to the 1-10 install process. It doesn't ask any questions at all...
Why would this occur?
This behavior is expected if your server is already attached to a farm. Was the machine previously part of a SharePoint farm and removed via the farm's Central Admin? Was a clean SharePoint uninstall/reinstall performed?