Classic AEM Installation Guide: Cloud

Modified on Thu, 01 Dec 2022 at 12:11 PM

Classic AEM is a Adobe Experience Manager setup in which both frontend and backend are coupled and hosted in Adobe environment. A site with React or Angular in the frontend is not classified as Classic AEM.

To see schema markup on the website or to be eligible for rich results, this guide assumes that relevant schema markup has been created and published both on the Editor and on the Highlighter in Schema App software.

Step 1: On Schema App


Note: A project on Schema App consists of a group of URLs. Every site on AEM should have a configuration that is linked to a project on Schema App i.e. one configuration for every AEM site.

  1. Login to Schema App, Click on ‘Home’. If you have an existing project, Click the Edit icon to edit the Deployment option. Please select “Adobe Experience Manager”. If you do not have an existing project, a project will have to be created before proceeding with next steps.

  2.  Enter the base URL / Domain of your AEM website.

  3. Click ‘OK’ to save the selection.
  4. On the side menu bar. Click ‘Integrations’.
  5. Under Deployment options, Select ‘Adobe Experience Manager’. 
  6. Copy the Account ID. These will be required for registration on AEM.



Step 2: Download and Install Schema App AEM connector

This installation assumes that Experience Manager Cloud instance's source project is checked out from the git repository. 
Download the connector from  Adobe Marketplace Or via a link provided by Schema App (ask a CSM) and install using AEM Package Manager tool on all AEM instances.

  1. Download connector from Adobe Marketplace or from link provided by Schema App team. Once file is successfully download, login to your AEM environment.
  2. In AEM instance source project, navigate to  / create the path "[base project]/ui.apps/src/main/content/jcr_root/etc/packages/com.schemaapp" 
  3. Add the downloaded package. 
  4. Navigate to "[base project]/ui.apps/src/main/content/META-INF/vault/filter.xml" 
  5. Edit, add the line 
    <filter root="/etc/packages/com. schemaapp/[filename]"/> 
  6. Commit change to the git repository.
  7. Rebuild the instance.


Step 3: On Adobe Experience Manager

        1. Navigate  to /aem/start.html 

        2. Click on ‘Tools’ in the right menu bar.

      3. Click on Cloud Services and then Click on " Schema App Connector" tile.


    4. Click on ‘Create’ button on the top right.




    5. In the dialog box, Enter the Account ID, API key & Website URL (publisher). Choose your deployment based on what is configured in Schema App, either Crawler or JavaScript. click 'Connect to Schema App' to register the site.





Impact of choosing Crawler vs Javascript

Crawler: JavaScript is not added to the site, only JSON-LD is added and the meta tag, schema markup  is updated much less frequently like once a week.

JavaScript: JavaScript will be added, the Scheduler will try and get JavaScript schema markup, Highlight.js and meta tag. Schema markup will be updated every 4 hours.


    6. You should get a message "You site has been registered with Schema App'.
        Click 'Save' in top right corner of the page.



   7. New config should be listed on the left of the screen.





The next steps guide you on how to configure the Schema App Configuration to the required pages.

  8. Go back to the Home page of your Adobe Experience Manager.

  9. Click on ‘Sites’.



 10. Select the site that you want the configuration earlier created to apply to.

Graphical user interface, application Description automatically generated

 11. On the top menu bar, click ‘Properties’.

 12. Then Click on ‘Cloud Services’ tab

Graphical user interface, text, application, email Description automatically generated

  13. Select the appropriate configuration created earlier in the drop down.

   14. Click Save and Close.


Step 4: Confirming Meta data added to the Page. 
To confirm a meta data-page-path element is in the head element
- Open any page of the website.
- Right click, then select ‘Inspect’
- Search with ‘meta data-page' Schema App’, you should see the meta data path and the URL. 


Step 5: Confirming schema markup deployment on the website.
To confirm the integration and deployment is complete, allow for 5 minutes.
- Open any page of the website.
- Right click, then select ‘Inspect’
- Search with ‘Schema App’ and 'JSON-LD, you should see the required scripts with Account ID. And schema markup, if any schema markup has been created for the site.



Permissions & Services 

Below table highlights the permissions and services that will be required for the Plugin to work efficiently.    

 

Path

Read

Modify

Create

Notes

/content*

To create schemaapp JSON-LD data node under page content node.

/etc/cloudservices* 

  To create and read schemaapp config

    

 

Function

Role

Author

API registration.

Publisher

Receives requests from the dispatcher.

Scheduler

Makes calls to the Schema App CDN.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article