Upgrading liferay dxp 7.0 to 7.1 electricity and magnetism physics


Take a backup of your production portal database and the Liferay document_library folder. Never run the Liferay DB upgrade tool directly against your production database! Once you have taken the backup, the best practice to follow would be to create a new schema, load the back up into the newly created schema, and use that schema to run the upgrade. Download the latest version of Liferay DXP 7.0 bundle, point this temporary installation to the new schema and the backed up document_library folder, and then start the server. This step is needed to verify that the database backup that we took is a working version, and that no problems occurred while taking the backup. e seva power bill payment Also, make sure you have the latest fix pack installed in your Liferay Server before proceeding ahead. 2. Setup Liferay DXP 7.1

Download the latest version of Liferay DXP 7.1 from the Liferay Customer Portal. Make sure you have the most recent version of the JDK 8 installed on your machine. Unpack Liferay DXP 7.1 and point it to the new schema with the database dump we created in the last step. Take the portal-ext.properties from your old Liferay DXP 7.0, and put it in the folder. Take document_library folder dump from 7.0 and put it in your /data folder. Note that if you start your 7.1 servers now, you will get an error on your server logs saying that the Release_ table contains data for an older version of Liferay. 3. Upgrading the Portal Database

Once you have set up the 3 properties files, you can go ahead and run the DB upgrade tool using the .bat file in windows or .sh file in Linux environment. While the tool runs, it will log both success and error messages so you will be aware of what is going on. You can find a lot more details about the DB upgrade tool on Liferay Developer Site.

Once the DB upgrade tool finishes, start your Liferay DXP 7.1 server. types of electricity generation If any issue occurs during Liferay startup, delete the database schema, delete the bundle, and restart the upgrade process by creating a new schema as mentioned in the Prerequisites step. This time, make sure that you have the latest fix pack for Liferay DXP 7.0 before proceeding forward. If it fails again, try disabling the Non Core Modules auto upgrade steps. Once the upgrade is successful, start the server. You should be able to access all your sites, users and contents. Finally, you should be certain to reindex the contents of the site in the portal search indexes after the upgrade process and validation has been completed. 4. Upgrading Theme

In order to upgrade a theme for use on Liferay DXP 7.1, one should follow this tutorial on Liferay developer site. It lists all the required steps in order to get your theme up and running on 7.1. gas in oil If your theme was created using the Liferay Theme generator, then you can easily upgrade it using the command gulp upgrade; before running the upgrade, make sure you are using the latest version of liferay-theme-tasks. gas national average You can obviously upgrade the theme tasks by running npm install liferay-theme-tasks@8.0.0-beta.5 –save in your themes folder (8.0.0-beta.5 was the latest version of liferay-theme-tasks when this blog was written). 5. Upgrading Application Display Templates

As you can see from the highlighted lines in the figure above, the dynamic-content reference is a Relative URL which points to the document; you can put that Relative URL in an img tag source or an anchor tag href in your ADT, and the document will be displayed as expected. In Liferay 7.1, though, they have updated the way that this reference is stored in the database.

If you are getting an error when accessing staticUtil from your templates, make sure that staticUtil is removed from the restricted variables list. To verify that this configuration change is in place, go to the Control Panel > Configurations > System Settings > Template Engines > FreeMarker Engine. If staticUtil is listed in the restricted variables list, remove it from the list and restart the Liferay server. 6. Upgrading Plugins

Upgrading portlets from 7.0 to 7.1 is fairly straightforward. One of the items you need to take care of is the dependencies in the build.gradle file. Update the Liferay dependencies to Liferay 7.1 versions, otherwise custom plugin modules will remain in the Installed state in OSGi container. For example, in 7.0 the dependency for the portal kernel jar was as follows:

You can check out the latest version of the jar files from the Central Maven Repo. Make sure to remove any deprecated classes and replace them with appropriate updated classes. For example, the com.liferay.portal.kernel.util.StringPool class has been deprecated and must be replaced with com.liferay.petra.string.StringPool from the Petra String jar.

Once these tasks have been completed, you can follow the instructions given on Liferay’s developer site for JAX-RS services to make changes to your existing REST service code. As you will find on the JAX-RS link, for version 7.1 Liferay has tied the REST services to their OAuth framework, which makes it impossible to call the service without an OAuth access token. Follow the documentation to find out how to generate an access token and invoke the service. For more details about OAuth in Liferay 7.1, you can check the article on the Liferay developer network. electricity recruitment 2015 Summary