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

Page tree

Installing Magnolia to Solaris works the same way as installing on Linux. If you already have an application server, deploy the WAR file. If you need to install the Tomcat & Magnolia bundle, change the shell in /apache-tomcat/bin/catalina.sh 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.

Register for a license key

When you buy an Enterprise Edition license, a license key will be sent to you upon signing of the Magnolia Network Agreement.

Magnolia Enterprise Edition is also available for a free 30-day trial. Register to get a license key.

  1. Go to http://registration.magnolia-cms.com.
  2. Fill the form with your details. A license key will be sent to the email address you provide.

Download

Go to http://files.magnolia-cms.com/ and download Magnolia Enterprise Edition.

You have the following options:

  • Installer: Contains everything you need to get started, including Magnolia, Tomcat, Jackrabbit and DerbyDB.
  • Bundle: Same contents as above but without the installer. Uncompress the package.
  • WAR: Contains only the Magnolia application (.war file). You need to deploy it on your own application server. Smaller download size than above.
  • IBM WebSphere, Oracle WebLogic: WAR files for running Magnolia on IBM WebSphere or Oracle WebLogic application servers. Read the deployment instructions.

Install

Using the installer

  1. Double-click the installer file you downloaded.
  2. Select an installation language and click OK.
  3. Click Next.
  4. Accept the license terms and click Next.
  5. Optional: Configure Magnolia to use a Java Development Kit other than your default JDK. The default is usually fine. Click Next.
  6. Click Next.
  7. Select the installation path.
  8. Click Next. Installation will start.
  9. Click Next.
  10. Click Done.

Using the bundle

Use this method if you need to do fast installations repeatedly.

Extract the zip to a directory on your computer. If you are installing Magnolia for personal use extract to /usr/home/<your account> 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-5.0. 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

To start Magnolia:
  1. Open a terminal window.
  2. Go to the Magnolia installation directory. Your path may be different.

    cd /home/userAccount/magnolia-5.0.3/apache-tomcat/bin
  1. fake
  2. fake
  3. Start Magnolia.

    ./magnolia_control.sh start &amp;&amp; tail -f ../logs/catalina.out

The first part of the 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. 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

Tip! To stop Magnolia type:

./magnolia_control.sh stop

Run the Web 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.

Enter the license key

Now you need the license key that was sent to your email address. Copy only the key string from the message. Use the same email address you used when registering.

Before you paste the license key make sure that it is a continuous string of characters with no spaces or line breaks. If you have any problems you can paste the key to a plain text editor to strip out any formatting.

Log in to the author instance

  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.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels