Prior to the start of the course, you will be asked to take part in a brief online course called Introduction to Liferay. The Introduction to Liferay course consists of three videos. The first video begins with an Introduction to Liferay, explaining what Liferay Portal is, what it does, and what makes Liferay Portal an ideal choice for running your web site. In the second video, you will be introduced to the concepts of Users, User Groups, Organizations, Sites, and Teams. You will see how all of these work together to enable you to design your web site in the most efficient way. In the last video, you will be introduced to Liferay's user interface. These three videos are the foundation for the Portal Developer training.
The Liferay Developer course begins with an introduction to the Liferay Plugins Software Development Kit (SDK). The Plugins SDK is at the heart of the development process and it is important for developers to be familiar with how the build and deploy process works. You will learn the differences between the different types of Liferay Plugins and when to use each. This will better equip you to come up with a development strategy that gives you the most flexibility.
Next, you will begin getting your hands dirty by setting up your Liferay development environment. All students that attend Liferay Developer training will receive a copy of the Liferay Developer Studio which provides an all-in-one, integrated development environment for Liferay Portal Enterprise Edition platform. The installation of Liferay Developer Studio includes the Liferay-Tomcat bundle and the Liferay Plugins SDK.
With the setup of our development environment complete, we jump in with both feet with an introduction to the features of the Java Portlet API, JSR-286. The first portlet you create will illustrate the lifecycle of a portlet and help you understand how to use Portlet Preferences to store portlet configuration data.
After this, you will explore some advanced features of the JSR-286 API by creating a project which implements communication between two portlets, using a Baseball metaphor: one portlet "throws" a pitch and the other "catches" it. You will see how you could use inter-portlet communication to implement applications composed of multiple portlets.