Upgrading from AEM 6.0 to 6.3 - Code deployment question | Community
Skip to main content
A
atulp44324524
New Participant
March 23, 2017
Solved

Upgrading from AEM 6.0 to 6.3 - Code deployment question

  • March 23, 2017
  • 13 replies
  • 7015 views

Hello All,

this is my first post in this forum. At Cisco we are currently using AEM 6.0 and have built a pretty big code around it :-) We are planning to upgrade the AEM version to 6.3 and have started a POC.

We have just installed the 6.3 on a sandbox environment and trying to deploy the existing code to it. Some of the bundles are not getting active. There are bunch of errors in the error.log but they are all pretty much same about some version complain. I have pasted a couple of them below. I think we need to change some of the com.day.cq.* jar versions in our pom.xml file but not exactly sure which ones. Can someone please help us out here ?

Thanks

- Atul

23.03.2017 16:56:31.950 *INFO* [OsgiInstallerImpl] org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start bundle it.cits.ciscoworkforcecontentservices.wem.cdc-devops.workflows [617]. Reason: {}. Will retry.
org.osgi.framework.BundleException: Unable to resolve it.cits.ciscoworkforcecontentservices.wem.cdc-devops.workflows [617](R 617.0): missing requirement [it.cits.ciscoworkforcecontentservices.wem.cdc-devops.workflows [617](R 617.0)] osgi.wiring.package; (&(osgi.wiring.package=com.cisco.wem.services)(version>=1.35.0)(!(version>=2.0.0))) [caused by: Unable to resolve it.cits.ciscoworkforcecontentservices.wem.cdc-devops.services [608](R 608.0): missing requirement [it.cits.ciscoworkforcecontentservices.wem.cdc-devops.services [608](R 608.0)] osgi.wiring.package; (&(osgi.wiring.package=com.cisco.wem.author.common.services)(version>=1.35.0)(!(version>=2.0.0))) [caused by: Unable to resolve it.cits.ciscoworkforcecontentservices.wem.cdc-devops.authoringcommonutils [530](R 530.0): missing requirement [it.cits.ciscoworkforcecontentservices.wem.cdc-devops.authoringcommonutils [530](R 530.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.replication)(version>=5.5.0)(!(version>=6.0.0)))]] Unresolved requirements: [[it.cits.ciscoworkforcecontentservices.wem.cdc-devops.workflows [617](R 617.0)] osgi.wiring.package; (&(osgi.wiring.package=com.cisco.wem.services)(version>=1.35.0)(!(version>=2.0.0)))]
        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.BundleImpl.start(BundleImpl.java:998)
        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
        at org.apache.sling.installer.core.impl.tasks.BundleStartTask.execute(BundleStartTask.java:97)
        at org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:894)
        at org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(OsgiInstallerImpl.java:729)
        at org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:286)
        at java.lang.Thread.run(Thread.java:745)
23.03.2017 16:56:32.018 *INFO* [OsgiInstallerImpl] org.apache.sling.installer.core.impl.tasks.BundleStartTask Could not start bundle it.cits.ciscoworkforcecontentservices.wem.cdc-devops.authoringcommonutils [530]. Reason: {}. Will retry.
org.osgi.framework.BundleException: Unable to resolve it.cits.ciscoworkforcecontentservices.wem.cdc-devops.authoringcommonutils [530](R 530.0): missing requirement [it.cits.ciscoworkforcecontentservices.wem.cdc-devops.authoringcommonutils [530](R 530.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.replication)(version>=5.5.0)(!(version>=6.0.0))) Unresolved requirements: [[it.cits.ciscoworkforcecontentservices.wem.cdc-devops.authoringcommonutils [530](R 530.0)] osgi.wiring.package; (&(osgi.wiring.package=com.day.cq.replication)(version>=5.5.0)(!(version>=6.0.0)))]
        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.BundleImpl.start(BundleImpl.java:998)
        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by diptinarang

    Hi

    Sorry couldn't revert earlier. I would suggest following approach:

    Deploy your code base to AEM 6.3 and simply try to build. Your build will show errors related to jars which are not compatible with 6.3. For such dependencies, you should look into Adobe's maven repository first. In case you are not able to find the jar, then go to OSGI bundles and search for the dependency name. Keep note of the bundle id and now go to your crx-repository on the file system. Let's say the bundle number is 102. Go to crx-quickstart->launchpad->felix->bundle-<id> (bundle-102) . You can check the .info file, it will contain the same information as you can see if you open the bundle from OSGI bundle console.

    I am attaching screenshots too. 

    I think I downloaded uber-jar for 6.3 beta latest load. Let me get back to you on this by tomorrow EOD.

    Thanks, Dipti 

    13 replies

    Show previous replies
    kautuk_sahni
    kautuk_sahni
    Employee
    March 24, 2017

    AEM 6.3 is not released yet though if someone attended Adobe Digital summit 2017 they would have seen some demo/Announcements.

    Currently Beta program is going on.

    ~kautuk 

    Kautuk Sahni
    sandeepm744005
    sandeepm744005
    New Participant
    March 24, 2017

    Can someone confirm from Adobe, is AEM6.3 available to use ? i was under the impression that only beta is available and actual version would be released in May.

    Terms & ConditionsAccessibility statement

    Loading footer...