Brand Portal is configured with AEM Assets to have approved brand assets seamlessly ingested (or published) from AEM Assets author instance. Once configured, AEM Author uses a replication agent to replicate the selected asset(s) to Brand Portal cloud service for approved usage by Brand Portal users. Multiple replication agents are used AEM 6.2 SP1-CFP5, AEM CFP 220.127.116.11, and onwards to allow high-speed parallel publishing.
Adobe recommends upgrading to AEM 18.104.22.168 to ensure that AEM Assets Brand Portal is successfully configured with AEM Assets. A limitation in AEM 6.4 gives an error while configuring AEM Assets with Brand Portal and replication fails.
On configuring cloud service for brand portal under /etc/cloudservice, all necessary users and token are auto-generated and saved in the repository. Cloud service configuration is created, service users required for replication and replication agents to replicate content are also created. This creates four replication agents. So when you publish numerous assets from AEM to Brand Portal, these are queued and distributed among these replication agents through Round Robin.
However, publishing can fail intermittently due to- large sling jobs, increased Network and Disk I/O on AEM Author instance, or slowed performance of AEM Author instance. It is, therefore, advised to test the connection with the replication agent(s) prior to begin publishing.
To validate your publish configurations:
Tail logs while creating Cloud Service
Check tail logs. Check whether the replication agent is created or not. If the replication agent creation fails, edit the cloud service by making minor changes in cloud service. Validate and check again whether the replication agent is created or not. If not, re-edit the service.
If on repeatedly editing the cloud service it is not configured properly, report a daycare ticket.
Test connection with replication agents
View log, if errors are found in replication log:
Contact Adobe Support.
Retry clean-up and create publish configuration again.
Most of the times when publishing is not working, the reason can be that the user who is publishing (for example:
mac-<tenantid>-replication doesn’t have the latest private key, and hence publish fails with “401 unauthorized” error and no other error is reported in replication agent logs. You might want to avoid troubleshooting and create a new configuration instead. For the new configuration to work properly, clean up the following from AEM author setup:
localhost:4502/crx/de/ (considering you are running author instance on localhost:4502:
Go to localhost:4502/useradmin:
i. search for user
ii. delete this user
Now the system is all cleaned up. Now you can attempt creating a new cloudservice config and still use the already existing JWT application in https://legacy-oauth.cloud.adobe.io/. There is no need to create a new application, rather just the public key needs to be updated from the newly created cloud config.
If on https://legacy-oauth.cloud.adobe.io/, all the orgs (tenants) for which the current users hold system administrator are listed. If you don’t find the org name here or you can’t create an application for a required tenant here, please check if you have sufficient (system administrator) rights to do this.
There is one known issue on this user interface that for any tenant only top 10 applications are visible. When you create the application, stay on that page and bookmark the URL. You don’t need to go to the listing page of the application and find the application that you created. You can hit this bookmarked URL directly and update/delete the application whenever needed.
The JWT application might not be listed appropriately. It is, therefore, advised to note/bookmark the URL while creating JWT application.
If a replication agent (which was publishing to brand portal just fine) stops processing publish jobs, check replication logs. AEM has auto-retry built-in, so if a particular asset publish fails, it is retried automatically. If there is some intermittent issue like network error, it might succeed during re-try.
If there are continuous publish failures and queue is blocked, then you should check test connection and try to solve the errors that are being reported.
Based on the errors, you are advised to log a support ticket, so that Brand Portal engineering team can help you resolve issues.
Usually the publishing job fails with a timeout error if there are multiple pending requests in the replication queue. To resolve this issue, ensure that the replication agents are configured to avoid timeout.
Perform the following steps to configure the replication agents: