AEM 6.5 - Cannot add DAM to AEM Sites Launch

[surenk]

We have site pages under project "/content/project/en/us/page-1" , and some of these page have components that fetch content from content fragments under "/content/dam/project/cfs/CF-1"

While creating an AEM > Sites > Launches (<server>/libs/launches/content/launches.html ) , we are able to add Pages, Experience fragments etc., but DOES NOT SHOW OR LET US browse to or show anything "/content/dam" (below).

Is there a work around? And/or are we missing anything?

[gkalyan]

Hi @surenk 

It looks more like a permission problem. Can you check the permissions and configurations to ensure that the DAM content paths are included in the launch.

Here is a similar adobe community question which might help - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-content-fragments-when...

[surenk]

Thanks @gkalyan 

How can i check the DAM content paths in the Launch?

The other adobe community link shared was more about Content-fragment-model and CF's created using that model.

We have several CF's under "content/dam/project/cf-hub" built using

the Content fragment model at "/conf/project/settings/dam/cfm/models/cf-hub-model"

When we create a Launch > Add Pages > /content/dam does not display anything.

I'm logged as "admin" on Author.

[HrishikeshKa]

Hi @surenk ,

Could you please follow the below steps:

1. Check Permissions: Ensure that the user account you're using to access AEM Sites Launches has the necessary permissions to browse and access assets in the DAM. You may need to adjust the permissions for the user or group in AEM's security settings.

2. Verify Configuration: Double-check your AEM configuration to ensure that the DAM is properly integrated with AEM Sites Launches. Make sure that the DAM is configured as a valid asset source for launches.

3. Check Path Restrictions: There might be path restrictions set up in AEM that prevent certain paths, such as /content/dam, from being accessed or included in launches. Review the configuration settings in AEM to see if there are any restrictions that need to be adjusted.

4. Use Asset References: Instead of directly adding assets from the DAM to launches, consider referencing them indirectly. You can add components or content fragments to your pages that reference assets in the DAM without directly including them in the launch configuration.

5. Explore APIs or Custom Solutions: If the AEM interface doesn't allow you to browse and select assets from the DAM for launches, you might need to explore alternative methods. This could involve using AEM's APIs to programmatically include assets in launches or developing custom solutions to integrate the DAM with launches.

6. Consult Adobe Support or Community: If you're unable to resolve the issue on your own, consider reaching out to Adobe Support or consulting the AEM community forums for assistance. They may be able to provide more insight into the issue and potential workarounds or solutions.

[surenk]

Thanks @HrishikeshKa 

I am using AEM default "admin" login, assuming should have access to all paths?

How can we verify this?

Verify Configuration: Double-check your AEM configuration to ensure that the DAM is properly integrated with AEM Sites Launches. Make sure that the DAM is configured as a valid asset source for launches.

[HrishikeshKa]

Hi @surenk ,

o verify whether the default "admin" login in Adobe Experience Manager (AEM) has access to all paths, you can follow these steps:

1. Login to AEM Console: Access the AEM web console using your browser. This is typically available at http://localhost:4502/libs/granite/core/content/login.html.

2. Login as Admin: Log in using the default "admin" credentials or any other credentials with administrative privileges.

3. Access CRXDE Lite: Once logged in, navigate to CRXDE Lite. You can access CRXDE Lite by appending /crx/de/index.jsp to your AEM instance URL. For example, http://localhost:4502/crx/de/index.jsp.

4. Browse Content Repository: In CRXDE Lite, you can navigate through the content repository and inspect the access rights of the "admin" user.

5. Check Permissions: Select any node in the repository and look for the "Access Control" tab. Here, you'll be able to see the permissions granted to different users and groups, including the "admin" user. Make sure that the "admin" user has sufficient permissions to access the necessary paths.

6. Verify Access: Try accessing various paths and functionalities within AEM using the "admin" login. If you encounter any access restrictions, you may need to adjust the permissions accordingly.

Regarding the second part of your question about verifying the configuration for DAM integration with AEM Sites Launches:

1. Access AEM Console: Log in to the AEM web console as described above.

2. Navigate to Tools: From the AEM console, navigate to the "Tools" menu.

3. Access DAM Configuration: Depending on your AEM version, look for options such as "Cloud Services", "Configuration", or "Settings" related to Digital Asset Management (DAM).

4. Verify DAM Configuration: Within the DAM configuration settings, look for options related to AEM Sites Launches integration. Ensure that the DAM is configured as a valid asset source for launches. You may need to specify the paths or folders within DAM that are available for use in launches.

5. Test Integration: After verifying the configuration, you can test the integration by creating or editing a launch and verifying that you can select assets from DAM as expected.

By following these steps, you can verify the access rights of the "admin" user in AEM and ensure that DAM is properly integrated with AEM Sites Launches.

If you get idea or understanding please make answer correct

[surenk]

Thanks for the detailed steps @HrishikeshKa 

Re:  Steps 3, 4 .. I am not able to find DAM / AEM Sites Launches specific integrations/permissions. Sorry to stretch this..

User "admin" has all the permissions.

[surenk]

After a lot of research, looks like

Adobe Experience Manager (AEM) 6.5's launch console is limited to adding pages. It doesn't currently support adding assets directly.

Launches are designed to create copies of pages that can be edited and published at a later date, allowing for planned content updates and marketing campaigns. If you need to add or manage assets, you typically do this directly in the Digital Asset Management (DAM) console or through workflows that handle assets.

(from ChatGpt, Gemini, Meta.ai)

Read every word several times on these pages https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/authoring/launches/la... and no reference to adding Assets.