existing Cloud services integrations will work fine after upgrade from cq 5.6.1 to 6.2?

[asn11]

We are running on 5.6.1 with cloud services integrations with site catalyst, Search &Promote, Campaign.

We are looking at upgrading to 6.1 or 6.2.

But it wont necessarily be an in place upgrade , we could go with new aem 6.2 instance altogether.

Will the existing jsp components and functionalities related to  site catalyst, Search &Promote, Campaign will continue to work in 6.2.

We are mostly using OOTB integration components for these adobe solutions. Upgrading aem does not mean that we will also have to upgrade campaign and search & promote as well right?

Thanks in advance for any help.

[asn11]

Any Suggestions Guys?

[kautuk_sahni]

I do not think there would be a problem while upgrading the instance.

If it would be common problem then we could have faced this issues in community.

Documentation :- https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade.html and https://docs.adobe.com/docs/en/aem/6-1/release-notes/deprecated-removed-features.html

//

      

Cloud Services

Configuration Manager API

Configuration Manager was refactored due to lock down of /etc/cloudservices to pull properties from public sub nodes and not use an admin session. API is still the same and it is rather the content model that was changed and the old model was deprecated. OOTB cloud services are adapted during in-place upgrade, but custom cloud service configs may not work anymore on publish with anonymous user if access to properties is required. There is a compatibility mode customers can enable to get the old behaviour back.

But i would like other community members to share their thoughts on this.

~kautuk

[user2797012]

List of https://docs.adobe.com/docs/en/aem/6-1/release-notes/deprecated-removed-features.html