unable to integrate AEM with Launch using Adobe I/O having static templates

Avatar

Avatar
Give Back 3
Level 1
chirag_satija
Level 1

Like

1 like

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Boost 1
View profile

Avatar
Give Back 3
Level 1
chirag_satija
Level 1

Like

1 like

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Boost 1
View profile
chirag_satija
Level 1

27-05-2020

Hi,

 

I am trying to integrate AEM 6.5 with  Adobe Launch using Adobe I/O

Referring :- https://docs.adobe.com/content/help/en/experience-manager-learn/sites/integrations/adobe-launch-inte...

 

But i am unable to map Adobe Launch cloud service with my project as we have static templates and our project is not under conf.

 

Is it the case that we can only using header approach for integrating launch with static templates in AEM?

By any chance can we integrate Adobe Launch using Adobe IO while being on static templates.?

@neerajpandey24 @kautuk_sahni 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 50
Employee
berliant
Employee

Likes

207 likes

Total Posts

315 posts

Correct reply

98 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
berliant
Employee

Likes

207 likes

Total Posts

315 posts

Correct reply

98 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
berliant
Employee

27-05-2020

Yes, it's possible to complete:

1. From the Launch property, you've been working in, click the Environments nav element

2. Click the Install icon for the Production environment to trigger the Web Install Instructions dialog box:

berliant_0-1590586609442.png

 

3. Click the Copy icon to copy the embed code to the clipboard.

4. Add the Launch header code to a page template. For example, for the We.Retail site:

a. browse to /apps/weretail/components/structure

b. place the Launch embed code that you just copied to the bottom of the customheaderlibs.html file:

berliant_2-1590587017454.png

 

 
 
 

 

 

 

Answers (3)

Answers (3)

Avatar

Avatar
Boost 1
Level 1
chirag_satija13
Level 1

Likes

2 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
chirag_satija13
Level 1

Likes

2 likes

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
chirag_satija13
Level 1

28-05-2020

Thanks team the issue is resolved now.

There were two issues.

1. Configuration section under advanced tab was missing in my code.

2. We were using core/v1/page but that didn't contain the below scripts.

<sly data-sly-resource="${'cloudconfig-header' @ resourceType='cq/cloudconfig/components/scripttags/header'}"></sly>

<sly data-sly-resource="${'cloudconfig-footer' @ resourceType='cq/cloudconfig/components/scripttags/footer'}"></sly>

After adding this it works for me.

Avatar

Avatar
Validate 1
Level 4
raghavc
Level 4

Likes

63 likes

Total Posts

61 posts

Correct reply

19 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back
Boost 50
View profile

Avatar
Validate 1
Level 4
raghavc
Level 4

Likes

63 likes

Total Posts

61 posts

Correct reply

19 solutions
Top badges earned
Validate 1
Give Back 5
Give Back 3
Give Back
Boost 50
View profile
raghavc
Level 4

27-05-2020

The solution suggested by @berliant  would work , only draw back is the launch script will hard coded in page component, So if you support multiple sites which uses different launch properties you will have to handle it in the code instead of config. You can try the below to ensure the config is loaded from the config

 

If you static page component does not use core/foundation page component and if you do not see the cloud config option, then you will have to update the page component dialog to include cloud config option 

 <configuration
                    jcr:primaryType="nt:unstructured"
                    jcr:title="Configuration"
                    sling:resourceType="granite/ui/components/coral/foundation/form/fieldset">
                    <items jcr:primaryType="nt:unstructured">
                        <cqConf
                            jcr:primaryType="nt:unstructured"
                            sling:resourceType="cq/cloudconfig/components/admin/configpathbrowser"
                            emptyText="Select Configuration Path"
                            fieldLabel="Cloud Configuration">
                            <granite:data
                                jcr:primaryType="nt:unstructured"
                                cq-msm-lockable="cq:conf"/>
                        </cqConf>
                    </items>
                </configuration>

 

Then include the header and footer component present under /libs/cq/cloudconfig/components/scripttags into your page components head(before any clientlib) and footer(end of the page) section

 

 

 

Avatar

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

103 likes

Total Posts

240 posts

Correct reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

103 likes

Total Posts

240 posts

Correct reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile
hamidk92094312
Employee

27-05-2020

When you say "unable to map Adobe Launch cloud service with my project" can you clarify what happens? From the relevant steps in the following document which one is not working as expected:

 

https://helpx.adobe.com/experience-manager/using/aem_launch_adobeio_integration.html#MapanAdobeLaunc...