7 Replies Latest reply on Dec 11, 2017 3:57 AM by smacdonald2008

    Can i migrate AEM 6.0 to AEM 6.3 with the war file?

    christianb68544374

      Hi all

       

      The migration guide (Performing an In-Place Upgrade) says that it is important to bring up the instance with the quickstart jar file. But what I tried is doing the migration with the quickstart war file. Is this possible too or do I have necessariily have to use the self executing jar file? The way I did does not trigger any upgrade process. Apache Felix is not coming up, the first bundle it tries to load fails with the following message:

      06-Dec-2017 10:38:11.770 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: Setting sling.home=C:\apache-tomcat-8.5.24-author\bin\author (servlet parameter sling.home)
      06-Dec-2017 10:38:11.775 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: Sling  Extension Lib Home : C:\apache-tomcat-8.5.24-author\bin\author\launchpad\ext
      06-Dec-2017 10:38:11.783 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: Checking launcher JAR in C:\apache-tomcat-8.5.24-author\bin\author
      06-Dec-2017 10:38:11.783 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: Checking launcher JAR in folder C:\apache-tomcat-8.5.24-author\bin\author\launchpad
      06-Dec-2017 10:38:11.791 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: Existing launcher is up to date, using it: 5.6.0.2_6_10-B001 (org.apache.sling.launchpad.base.jar)
      06-Dec-2017 10:38:11.794 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: Loading launcher class org.apache.sling.launchpad.base.webapp.SlingServletDelegate from org.apache.sling.launchpad.base.jar
      06-Dec-2017 10:38:11.795 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: External Libs Home (ext) is null or does not exists.
      06-Dec-2017 10:38:11.803 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: Starting launcher ...
      06-Dec-2017 10:38:11.803 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log granite: Starting Apache Sling in C:\apache-tomcat-8.5.24-author\bin\author
      06-Dec-2017 10:38:13.582 SEVERE [FelixStartLevel] org.apache.catalina.core.ApplicationContext.log ERROR: Error starting slinginstall:C:\apache-tomcat-8.5.24-author\bin\author\launchpad\startup\0\org.apache.felix.http.bridge-2.2.0.jar (org.osgi.framework.BundleException: Unable to resolve org.apache.felix.http.bridge [1](R 1.1): missing requirement [org.apache.felix.http.bridge [1](R 1.1)] osgi.ee; (&(osgi.ee=JavaSE)(version=1.6)) Unresolved requirements: [[org.apache.felix.http.bridge [1](R 1.1)] osgi.ee; (&(osgi.ee=JavaSE)(version=1.6))])
       org.osgi.framework.BundleException: Unable to resolve org.apache.felix.http.bridge [1](R 1.1): missing requirement [org.apache.felix.http.bridge [1](R 1.1)] osgi.ee; (&(osgi.ee=JavaSE)(version=1.6)) Unresolved requirements: [[org.apache.felix.http.bridge [1](R 1.1)] osgi.ee; (&(osgi.ee=JavaSE)(version=1.6))]
              at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4112)
              at org.apache.felix.framework.Felix.startBundle(Felix.java:2118)
              at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1372)
              at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
              at java.lang.Thread.run(Thread.java:745)
      

       

      I feel like Apache Felix and Sling are still in the old version..

       

      Thanks,

       

      Chris