Magnolia 5.3 reached end of life on June 30, 2017. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

Unable to render {include} The included page could not be found.

Installing Magnolia on Solaris works the same as on Linux. For an already-installed application server, deploying the WAR file works the same way too. If you need to install the Tomcat Magnolia bundle, edit the /apache-tomcat/bin/catalina.sh file and change the shell from #!/bin/sh to #!/bin/bash. The shell is the first line in the file.

Prerequisites

Java Runtime Environment (JRE)

Magnolia needs a Java Runtime Environment (JRE). Most likely you already have it on your Linux computer. Use the Java Tester to check.

If you don't have JRE, download and install it from http://java.sun.com/javase/downloads/index.jsp. Installation directory varies from one Linux system to another. For example on Ubuntu Linux 10 the OpenJDK Runtime Environment is installed in /usr/lib/jvm/java-6-openjdk/jre by default.

Download

Download the Magnolia Tomcat bundle zip file from Nexus. The file name depends on the release, for example magnolia-tomcat-bundle-5.0-tomcat-bundle.zip. Get the latest.

Install

Extract the zip to a directory on your computer. If you are installing Magnolia for personal use extract to /usr/home/yourAccount or equivalent directory. If you are installing a production server extract to /usr/local or /opt. Regular user accounts may not have permissions to extract files into a target directory such as /opt. If this is the case extract the zip in the folder where you downloaded it, then open a terminal window and move the extracted folder using sudo mv magnolia-4.3.2. The sudo command will execute the mv (move) command as superuser, prompting you for a password.

The extracted folder structure looks like this:

magnolia-5.0
   add-ons
   apache-tomcat
      bin
      conf
      logs
      webapps
         MagnoliaAuthor
         MagnoliaPublic
         ROOT

Start

  1. Open a terminal window.
  2. Go to the Magnolia installation directory:
    cd /home/userAccount/magnolia-4.2.3/apache-tomcat/bin
    Your path may be different.
  3. Start Magnolia:
    ./magnolia_control.sh start && tail -f ../logs/catalina.out

The first part of the startup command ./magnolia_control.sh start launches Magnolia. The second part && tail -f ../logs/catalina.out displays startup messages written to /apache-tomcat/logs/catalina.out log file. This makes it easier to troubleshoot startup errors.

Magnolia reports startup information. If startup fails, look for the reason in the report. See Troubleshooting to resolve the issues. In a successful startup the last line reads:
INFO: Server startup in 12345 ms

To stop Magnolia, type ./magnolia_control.sh stop

Update

To run the Web update:

  1. Open a browser and go to http://localhost:8080.
  2. Click the Run the Web update on the author instance link. 
    A list of modules that need updating is displayed.
  3. Click Start install
    The modules are updated.
  4. Click Start up Magnolia.

Repeat the update on the public instance.

  1. Open a browser and go to http://localhost:8080.
  2. Click the Run the Web update on the public instance link. 
    A list of modules that need updating is displayed.
  3. Click Start install
    The modules are updated.
  4. Click Start up Magnolia.

Log in

  1. Open a browser and go to http://localhost:8080/magnoliaAuthor/.magnolia/admincentral
  2. At the login page, sign in with:
    • Username: superuser
    • Password: superuser

The app launcher is displayed.

Superuser is a system administration account that has permission to every function. End users should not use this account. See Users for instructions how to create new user accounts and Default users for accounts that you can use for testing right away.

Troubleshooting

Having problems? See Known issues.

  • No labels