Summary At this point, you should have version 6.2 of OpenCms running. Version 6.2 has many new features and modifications. Many of these new features especially the ones in the OpenCms Workplace are documented in this book.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost java Web Hosting services
Final Steps The last screen of the upgrade wizard will prompt you to restart the server. At this point, the update wizard is complete. You can safely close your web browser. But remember, you need to restart tomcat to ensure that all of the changes take effect. OpenCms will automatically disable the wizard again, and you will not be able to rerun the wizard without changing the settings in the opencms.properties file. You can now view your OpenCms site and log back into the OpenCms Workplace.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost java Web Hosting services
Even for an update, this process can take a long time.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost java Web Hosting services
This page will list all of the updated XML configuration files. If you are migrating from the OpenCms 6.2 beta release (as is shown above), there is only one such file. Other versions of OpenCms may have more XML files in need of updating. Unless you have custom versions of these XML files, you should leave all of these selected. Clicking Continue installs the XML updates and then loads the module selection screen. This screen shows all the currently available modules, and all of them are checked by default. On a production server you may not want the documentation modules. For other reasons, you may have already identified other modules you do not want. If you know you do not want some of these modules and you know that uninstalling them will not cause problems, you can deselect the undesired modules. Otherwise, the best course of action is to install all of them. You can delete the unwanted ones later. (See Chapter 4.) Clicking Continue will bring up a progress screen, which will display information as the application installs.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost java Web Hosting services
Once you have entered the correct information, clicking Continue will load test the settings and load the next screen. If something you have entered is incorrect, the wizard will prompt you to start over again. Otherwise, it will take you to the XML Configuration Files Update page.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost java Web Hosting services
As long as the wizard is enabled, you will not be able to access either the public OpenCms site or the Workplace. As with the regular OpenCms installation, the first thing you will have to do is accept the OpenCms license agreement, which states that OpenCms is released under the GNU Lesser General Public License, an open-source license. Once you accept the license, the Continue button will be activated. The next screen will prompt you to enter some information that will be necessary for the upgrade. You will need to provide the administrator user name and password, since the update utility requires access to the entire VFS.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost java Web Hosting services
The next thing to do is extract the contents of the opencms_upgrade_to_6.2.1.zip file. It is best to unzip the archive into a temporary directory. Once you have unzipped the file, you should have three items in your working directory the WEB-INF folder, the update folder, and the readme.txt file. The readme.txt file will contain a brief set of instructions on the upgrade process. The WEB-INF folder contains the new and updated OpenCms files. The update folder contains the upgrade wizard. Moving Files At this point, we will start moving files. Make sure your servlet container (for example, tomcat) is stopped. If it is running during the upgrade, you may corrupt the OpenCms installation. Copy the update folder into the root directory of the existing OpenCms installation. With tomcat, this is in $CATALINA_OPTS/webapps/opencms. (Chapter 2 tells you where these files are stored on the file system.) Copy the contents of the WEB-INF folder from the upgrade package to the WEB-INF folder in your existing OpenCms folder. This will overwrite a number of files, which is exactly what you want new versions of OpenCms libraries will replace the older versions. There is one last thing to do before restarting the servlet container we need to turn the wizard back on. After doing the original installation of OpenCms, the installer automatically disables the wizard interface. To do an upgrade, we need the wizard interface re-enabled. With the text editor of your choice, open the file $CATALINA_HOME/webapps/opencms/ WEB-INF/config/opencms.properties. At the very bottom of this file is a line that reads: wizard.enabled=false Change false to true, save the file, and close the editor. At this point, you can restart tomcat. Running the Upgrade Wizard We are now ready to run the web-based upgrade wizard. Open a web browser and point it to the upgrade wizard. The URL should be something like http://myserver:8080/ opencms/update.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost tomcat Web Hosting services
B Upgrading OpenCms In this appendix, we will cover upgrading from OpenCms 6.0.4 to OpenCms 6.2 or later. Getting the Upgrade Package The first thing you will need to do is get the upgrade package from the official OpenCms website, http://www.opencms.org. The OpenCms upgrade package is different from the OpenCms installation package since it contains a special wizard to guide you through the process of upgrading. At the time of this writing, the most recent version of the updater is called opencms_upgrade_to_6.2.1.zip. Once you have the package, you are ready to begin the installation process. Preparing for the Upgrade While the upgrade process has been tested and is reliable, there is always the possibility that something could go wrong. Therefore, before proceeding, you should make a backup copy of your OpenCms installation. You may want to export your VFS and your custom modules. (See Chapter 4.) You may also want to dump a copy of your database. (Consult your database documentation.) During the upgrade, OpenCms will re-install all of the core OpenCms modules, including TemplateOne and the documentation. If you have modified any of these modules, your changes will be lost during the upgrade. You may want to export the changed resources (rather than the whole modules) so that you can re-import them after the update. It can also be a good idea to make a spare copy of the OpenCms web application directory. To do that, stop tomcat (or whatever servlet container you are running), and copy the $CATALINA_HOME/webapps/opencms folder to another location.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost tomcat Web Hosting services
The 0 indicates the offset from the beginning of the hour. (0 means there is no offset.) The 15 indicates that it should run every fifteen minutes. If we want the job to run at five minutes after the hour and then every fifteen minutes, we would have 5/15 instead of 0/15. The optional seventh field, year, can be specified to restrict the job to only run during the specified year or years. For example, to run a job at 7:15:30 AM every Tuesday during the first quarter of the years 2006 and 2007, I could use the string: 30 15 7 ? Jan-Mar Tue 2006-2007 The year must be between 1970 and 2099, inclusive. I would not recommend using OpenCms 6 in the years following 2099. Summary In this appendix, we have examined the cron expression syntax, looking at examples along the way. Expressions in this format can be used to schedule tasks using the New Job screen in the administration view.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost tomcat Web Hosting services
The month and day-of-the-week fields accept abbreviated names in lieu of numbers (e.g. month can have Jan to Dec instead of 1 to 12). These are not case sensitive, so MON, Mon, and mon will all evaluate to 2. L in the day-of-the-month field indicates that the job should be run on the last day in the month. When it is used in the day-of-the-month field, the scheduler will run the job on the last day of the month. L as a value in the day-of-the-week field means the last day in the week, so it has the same effect as 7. L can be also used as a modifier in the day-of-the-week field by appending it to a number, so that the job will be run on the last of that day in the month. For example, here is a cron expression to run a job at noon on the last Tuesday of the month: 0 0 12 ? * 3L The W modifier in the day-of-month field indicates that the task is to be run on weekdays only. If the date falls on a weekend, then the task is delayed until the next weekday. For example, consider this cron expression, which runs a job at 1:00 AM on the first of every month: 0 0 1 1W * ? LW indicates that a job is to be run on the last weekday in the month. For example: 0 0 1 LW * ? If the first of the month fell on a Saturday, then the job would not be executed until Monday. The hash sign, #, is used in the day-of-the-week field to indicate that the job should be run on the nth such day in the month. For example, to run a job at noon on the third Friday of the month, you would use a string like this: 0 0 12 ? * 6#3 As mentioned above, an asterisk, *, indicates any value. A dash, -, indicates a range. For example, if I want to run a job once an hour for three hours in a row, I can use this cron expression: 0 0 1-3 * * ? To set several different values in the same field, you can use commas to separate them. For example, to run four times in an hour, you could use the following: 0 0,15,30,45 * * * ? it will then run every fifteen minutes. Do not put spaces before or after the commas. Another way to do this would be to tell the job scheduler to run the job at various intervals. This can be accomplished with a forward slash, /. So instead of telling the scheduler to run at the specific minutes 0, 15, 30, and 45, we could tell it to run every fifteen minutes: 0 0/15 * * * ?
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost jsp Web Hosting services
Powered by Java Web Hosting