Add Omniscripts to Adobe Experience Manager (Managed Package)

For the managed package runtime, add Omniscripts to Adobe Experience Manager using OmniOut. Omniscripts hosted in AEM require a Salesforce connection to send data between servers.

1. Create a Salesforce connection in AEM. See Integrate Salesforce Cloud Services into Adobe Experience Manager (Managed Package).
2. Set resource paths in OmniOut to load Lightning and Newport styles into your app. See Set the OmniOut Resource Path (Managed Package).
3. Deploy OmniOut to AEM. See Deploy OmniOut to Adobe Experience Manager (Managed Package).
4. Add the OmniOut component to an AEM page. See Add the Vlocity LWC OmniOut Component to Adobe Experience Manager (Managed Package).

• Integrate Salesforce Cloud Services into Adobe Experience Manager (Managed Package)
  For the managed package runtime, create a Salesforce connection in Adobe Experience Manager (AEM). The connection setup isn’t part of the Vlocity package.
• Set the OmniOut Resource Path (Managed Package)
  For the managed package runtime, load your custom styling resources into your Adobe Experience Manager application by setting the correct resource paths.
• Deploy OmniOut to Adobe Experience Manager (Managed Package)
  For the managed package runtime, add your AEM credentials to OmniOut and deploy it to your AEM server. The deployment adds a Vlocity LWC OmniOut component to AEM. The Vlocity LWC OmniOut component allows you to add your Omniscripts to an AEM page.
• Add the Vlocity LWC OmniOut Component to Adobe Experience Manager (Managed Package)
  For the managed package runtime, launch Omniscripts from an AEM page by adding the Vlocity LWC OmniOut Component. The Vlocity LWC OmniOut component hosts the Omniscript and uses the Salesforce Cloud Services configuration to make calls to Salesforce.