DocumentationAEM GuidesAEM Guides Documentation

Upgrade Adobe Experience Manager Guides id224MBE0M0XA

Last update: Wed Nov 06 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
NOTE
Follow the upgrade instructions specific to the licensed version of your product.

You can upgrade your current version of Experience Manager Guides to version 4.6.0 Service Pack 1:

  • If you are using version 4.6.0, then you can directly upgrade to 4.6.0 Service Pack 1.
  • If you are using version 4.4, 4.3.1, or 4.3.0 , then you need to upgrade to version 4.6.0 before upgrading to 4.6.0 Service Pack 1.
  • If you are using version 4.2, 4.2.1 (Hotfix 4.2.1.3), 4.1, or 4.1.x then you need to upgrade to version 4.4 before upgrading to version 4.6.0.
  • If you are using version 4.0 you need to upgrade to version 4.2 before upgrading to version 4.3.x.
  • If you are using version 3.8.5, you need to upgrade to version 4.0 before upgrading to version 4.2.
  • If you are on a version prior to 3.8.5, refer to the Upgrade Experience Manager Guides section in the product-specific installation guide available on Adobe Experience Manager Guides help PDF archive.
NOTE
You must install AEM service pack before upgrading Experience Manager Guides version.

For more details, refer to the following procedures:

IMPORTANT
Before you begin to upgrade, take a complete system backup to avoid any loss of data.

Upgrade from version 3.8.5 to version 4.0 id2256DK003E1

If you are using Experience Manager Guides version 3.8.5, then you can upgrade to version 4.0 of Experience Manager Guides. With the upgrade feature, you don’t have to uninstall the previous version of Experience Manager Guides.

Before running the process there are certain tasks that you must complete. The following sub-sections will walk you through the prerequisites, report generation, and migration process. Also, after you install Experience Manager Guides version 4.0 you may customize various configurations, according to the customer settings.

NOTE
This Upgrade process is applicable only from version 3.8.5 to version 4.0. For the process to upgrade from version 3.4 or higher to 3.8.5, refer to the Upgrade Experience Manager Guides section in the product-specific installation guide available on Adobe Experience Manager Guides help PDF archive.

Prerequisites

Before you start the Experience Manager Guides upgrade process, ensure that you have:

  1. Imported the review comments in topics open for review.
  2. Closed all active reviews.
  3. Closed all translation tasks.
  4. Uninstall any Experience Manager Guides hotfixes installed on the top of the previous version (major or patch release) of Experience Manager Guides.

Before you install version 4.0

Before you install version 4.0, perform the following steps:

  1. Ensure at this point Experience Manager Guides is on version 3.8.5.
  2. Download the upgrade script package. To do so, search for “XML Documentation solution 4.0 Upgrade Package” on Adobe Software Distribution Portal which will download a zip file.
  3. Upload this package to AEM via Package Manager and install this package.
  4. Once the upgrade package is installed, run the below given scripts in the same order and follow the given instructions:

Check upgrade compatibility API

This API is designed to assess the current system status and report if the upgrade is possible or not. To run this script, trigger the below given endpoint:

End Point
/bin/dxml/upgrade/3xto4x/report
Request Type
GET You can use a web browser, where you are logged in to the AEM instance as an administrator.
Expected Response
- In case all required nodes can be moved, you will get a passed check.
- In case a node is present at the target location, you will get a relevant error. Clean up the repository (delete node /var/dxml) and reinstall the upgrade package and then trigger this endpoint again.
Note: This is not a common error as the target location is not used earlier by 3.x Experience Manager Guides.
- If this script does not succeed, do not proceed and report to your customer success team.

System data migration API

This API is designed to migrate the system data as mentioned in the Migration Mapping section.

  1. Do not execute this script if the Check upgrade compatibility API fails (do not proceed).
  2. Once the Check upgrade compatibility API returns success, you can run the upgrade script.
End Point
/bin/dxml/upgrade/3xto4x
Request Type
POST This script is a POST request hence should be executed via agents like Postman.
Expected Response
- Once the migration is successful, you can install XML Documentation solution version 4.0.
- In case there are errors, restore to the last checkpoint and share the error logs along with API output with your customer success team.

Migration Mapping: The above API migrates all the data under the source location to the target location.

Source
Target
/content/fmdita
/var/dxml
/content/dxml
/var/dxml
/etc/fmdita
/libs/fmdita

Install version 4.0 id23598G006XA

  1. Install version 4.0 only if the upgrade steps were successful.

  2. Download 4.0 version package from Adobe Software Distribution Portal:

    • If you are using UUID version of software, search for “4.0 UUID Release for XML Documentation solution for AEM 6.5.”
    • If you are using Non-UUID version of software, search for “4.0 Non-UUID Release for XML Documentation solution for AEM 6.5.”
      Upload the package to the existing AEM server instance(s) using CRX Package Manager and install it.
    note note
    NOTE
    Wait for all system components to start.

  3. Clear the browser cache after installing the package.

  4. If a dispatcher is configured on AEM Author instance, perform the following steps:

    • Ensure the following are handled in dispatcher rules:
    • The URL pattern /home/users/*/preferences is whitelisted.
    • The URL pattern /libs/cq/security/userinfo.json is not cached.

  5. Clear dispatcher cache (to clear any clientlibs cached).

Upgrade to version 4.2 id22A3F500SXA

Upgrading to version 4.2 depends on the current version of Experience Manager Guides.

If you are using version 4.0, 4.1 or 4.1.x, then you can directly upgrade to version 4.2.

Prerequisites

Before you start the Experience Manager Guides 4.2 upgrade process, ensure that you have:

  1. Upgraded to Experience Manager Guides version 4.0, 4.1 or 4.1.x.
  2. Closed all translation tasks.
  3. Changed the log level to INFO for com.adobe.fmdita.translationservices.TranslationMapUpgradeScript class and append these logs in a new log file, for example, logs/translation_upgrade.log.
NOTE
You should close all active reviews. If the review tasks are not closed while upgrading to 4.2, the older in-progress review tasks keep taking users on the older review pages, and the review tasks created after the upgrade will display the latest updates in the functionality.

Install version 4.2 id2245IK0E0EV

  1. Download 4.2 version package from Adobe Software Distribution Portal.

  2. Install version 4.2 package.

  3. After you complete the package installation, wait for the following message(s) in the logs:

    Completed the post deployment setup script

    The above message indicates that all the steps of installation are complete.

    In case you encounter any of the following ERROR prefixes, report them to your customer success team:

    • Error in post deployment setup script
    • Exception while porting the translation MAP
    • Unable to port translation map from v1 to v2 for property

  4. Upgrade Oxygen connector plugin released with version 4.2 (if needed).

  5. Clear the browser cache after installing the package.

  6. Continue upgrading the customizations as detailed out in the next section.

After you install version 4.2 id2326F02004K

IMPORTANT
Hi-tech template is not displayed on upgraded server. To include the hi-tech template on your server you can copy it: Source: /libs/fmdita/pdf/Hi-Tech Destination: /content/dam/dita-templates/pdf

After you install Experience Manager Guides, you may merge the various configurations applicable from the newly installed version to your setup.

NOTE
The dam-update-asset model may be customized. So, if any customizations have been done, then we need to sync the customizations and Experience Manager Guides into the working copy of the model.

  1. DAM Update Asset workflow (Post-processing changes):

  2. Open URL:

    code language-http 
    http://localhost:4502/libs/cq/workflow/admin/console/content/models.html

  3. Select DAM Update Asset workflow.

  4. Click on Edit.

  5. If the DXML Post Process Initiator component is present, ensure that the customizations are synced.

  6. If the DXML Post Process Initiator component is absent, perform the following steps to insert it:

  7. Click Insert component (Responsible for Experience Manager Guides post-processing as the final step in the process).

  8. Configure the Process step with below details:

    Common tab

    Title: DXML Post Process Initiator

    Description: DXML post process initiator step which will trigger a sling job for DXML post-processing of the modified/created asset

    Process tab

    • Select DXML Post Process Initiator from the Process drop down

    • Select Handler Advance

    • Select Done

  9. Click Sync on the top right after completing the changes. You will receive a success notification.

    note note
    NOTE
    Refresh and verify that customized changes and the Experience Manager Guides post-processing step is present in the final workflow model.

  10. Once DAM Update Asset workflow is validated, check corresponding launcher configurations. To do so, go to AEM Workflow interface and open launchers.

    code language-http 
    http://localhost:4502/libs/cq/workflow/content/console.html

    Find and make changes (if necessary) to the following two launchers (that should be active) corresponding to DAM Update Asset workflow:

  11. Launcher for “Node Created” for DAM Update Asset workflow- for condition "jcr:content/jcr:mimeType!=video", the ‘Globbing’ value should be:

    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • ‘excludeList’ should have "event-user-data:changedByWorkflowProcess".
    • Launcher for “Node Modified” for DAM Update Asset workflow - for condition “jcr:content/jcr:mimeType!=video”,
    • the ‘Globbing’ value should be:
    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • ‘excludeList’ should have "event-user-data:changedByWorkflowProcess".

  12. Once the upgrade is complete, ensure any of the customizations/overlays are validated and updated to match the new application code. Some examples are given below:

    • Any components overlayed from/libs/fmditaor/libsshould be compared with the new product code and updates should be done in overlayed files under/apps.
    • Any clientlib categories used from product, should be reviewed for changes. Any overridden configurations (examples below) should be compared with the latest ones so as to get the latest features:
    • elementmapping.xml
    • ui_config.json(may have been set in folder profiles)
    • amended com.adobe.fmdita.config.ConfigManager
    • Check if any of the custom code was using any old paths (as mentioned in the Migration Mapping section) - should be updated to the new paths so that the customizations also work as expected.

  13. Read about any new configurations brought in the current release (check Release Notes) and see if any functionality is impacted then take appropriate action. An example could be to make use of “Improved file and version handling” introduced in version 4.0, for which you need to enable a configuration.

Steps to index the existing content to use the new find and replace:

Perform the following steps for indexing the existing content and use the new find and replace text at map level:

  • Run a POST request to the server (with correct authentication) - http://<server:port\>/bin/guides/map-find/indexing. (Optional: You can pass specific paths of the maps to index them, by default all maps will be indexed || For example : https://<Server:port\>/bin/guides/map-find/indexing?paths=<map\_path\_in\_repository\>)

  • The API will return a jobId. To check the status of the job, you can send a GET request with job id to the same end point -

http://<server:port\>/bin/guides/map-find/indexing?jobId=\{jobId\}(For example: http://localhost:8080/bin/guides/map-find/indexing?jobId=2022/9/15/7/27/7dfa1271-981e-4617-b5a4-c18379f11c42)

  • Once the job is complete, the above GET request will respond with success and mention if any maps failed. The successfully indexed maps can be confirmed from the server logs.

If the upgrade job fails and the error log shows the following error:

“The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped.”

This could happen because the index is not properly set up for the query used in the upgrade. You can try the following workaround:

  1. In the damAssetLucene oak index, add the boolean property indexNodeName as true in the node.
    /oak:index/damAssetLucene/indexRules/dam:Asset

  2. Add a new node with the name excerpt under the node.

    /oak:index/damAssetLucene/indexRules/dam:Asset/properties
    and set the following properties in the node:

    code language-none 
    name - rep:excerpt
propertyIndex - {Boolean}true
notNullCheckEnabled - {Boolean}true

    The structure of damAssetLucene should look something like:

    code language-none 
    <damAssetLucene compatVersion="{Long}2" async="async, nrt" jcr:primaryType="oak:QueryIndexDefinition" evaluatePathRestrictions="{Boolean}true" type="lucene">
<indexRules jcr:primaryType="nt:unstructured">
  <dam:Asset indexNodeName="{Boolean}true" jcr:primaryType="nt:unstructured">
    <properties jcr:primaryType="nt:unstructured">
      <excerpt name="rep:excerpt" propertyIndex="{Boolean}true" jcr:primaryType="nt:unstructured" notNullCheckEnabled="{Boolean}true"/>
    </properties>
    </dam:Asset>
  </indexRules>
</damAssetLucene>

    (along with other existing nodes and properties)

  3. Reindex the damAssetLucene index (by setting the reindex flag as true under
    and wait for it to be false again (this indicates the reindexing is complete). Note that it may take a few hours depending on size of the index.

  4. Run the indexing script again by performing the previous steps.

Upgrade to version 4.2.1 upgrade-version-4-2-1

TIP
It is recommended to install Hotfix 4.2.1.3 on top of version 4.2.1.

Upgrading to version 4.2.1 depends on the current version of Experience Manager Guides. If you are using version 4.1 or 4.1.x, or 4.2 then you can directly upgrade to version 4.2.1.

NOTE
The post-processing and indexing may take a few hours. We recommend you to start the upgrade process during the off-peak hours.

Prerequisites

Before you start the Experience Manager Guides 4.2.1 upgrade process, ensure that you have:

  1. Upgraded to Experience Manager Guides version 4.1, 4.1.x, or 4.2.
  2. Closed all translation tasks.
  3. Changed the log level to INFO for com.adobe.fmdita.translationservices.TranslationMapUpgradeScript class and append these logs in a new log file, for example, logs/translation_upgrade.log.
NOTE
You should close all active reviews. If the review tasks are not closed while upgrading to 4.2, the older in-progress review tasks keep taking users on the older review pages, and the review tasks created after the upgrade will display the latest updates in the functionality.

Install version 4.2.1

  1. Download 4.2.1 version package from Adobe Software Distribution Portal.

  2. Install version 4.2.1 package.

  3. You can choose to HIT the trigger to start the translation map upgrade job. For details, see Enable trigger of script via a Servlet.

  4. After you complete the package installation, wait for the following message(s) in the logs:

    Completed the post deployment setup script

    The above message indicates that all the steps of installation are complete.

    In case you encounter any of the following ERROR prefixes, report them to your customer success team:

    • Error in post deployment setup script
    • Exception while porting the translation MAP
    • Unable to port translation map from v1 to v2 for property

  5. Upgrade Oxygen connector plugin released with version 4.2 (if needed).

  6. Clear the browser cache after installing the package.

  7. Continue upgrading the customizations as detailed out in the next section.

Enable trigger of script via a Servlet enable-trigger-serverlet

POST:

http://localhost:4503/bin/guides/script/start?jobType=translation-map-upgrade

Response:

{
"msg": "Job is successfully submitted and lock node is created for future reference",
"lockNodePath": "/var/dxml/executor-locks/translation-map-upgrade/1683190032886",
"status": "SCHEDULED"
}

In the above response JSON, the key lockNodePath holds the path to the node created in the repository pointing to the job submitted. It will automatically be deleted once the job is completed, till then, you can refer to this node for the current status of the job.

Sample log:
The following is a sample of logs that will appear in the log file after you trigger the script.

04.05.2023 14:17:12.876 *INFO* [[0:0:0:0:0:0:0:1] [1683190032736] POST /bin/guides/script/start HTTP/1.1] com.adobe.dxml.common.executor.RunnableSynchronizedOTS Acquiring lock for job : translation-map-upgrade
04.05.2023 14:17:12.897 *INFO* [pool-59-thread-1] com.adobe.fmdita.xmltranslation.ots.TranslationMapUpgradeOTS Starting the thread to upgrade translation map from V1 to V2
04.05.2023 14:17:12.899 *INFO* [pool-59-thread-1] com.adobe.dxml.common.executor.RunnableSynchronizedOTS Initiating lock for node : /var/dxml/executor-locks/translation-map-upgrade/1683190032886
04.05.2023 14:17:12.901 *INFO* [pool-59-thread-1] com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Starting porting of translation map from V1 to V2
04.05.2023 14:17:12.904 *INFO* [pool-59-thread-1] com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Memory increase is of : 764 kB
04.05.2023 14:17:12.906 *INFO* [pool-59-thread-1] com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Completed porting of translation map from V1 to V2
04.05.2023 14:17:12.907 *INFO* [pool-59-thread-1] com.adobe.dxml.common.executor.RunnableSynchronizedOTS Releasing lock for node : /var/dxml/executor-locks/translation-map-upgrade/1683190032886
04.05.2023 14:17:12.909 *INFO* [pool-59-thread-1] com.adobe.fmdita.xmltranslation.ots.TranslationMapUpgradeOTS Completed the thread to upgrade translation map from V1 to V2

Look for com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Completed porting of translation map from V1 to V2 and com.adobe.fmdita.xmltranslation.ots.TranslationMapUpgradeOTS Completed the thread to upgrade translation map from V1 to V2 before proceeding to the next steps.

After you install version 4.2.1

IMPORTANT
Hi-tech template is not displayed on upgraded server. To include the hi-tech template on your server you can copy it: Source: /libs/fmdita/pdf/Hi-Tech Destination: /content/dam/dita-templates/pdf

After you install Experience Manager Guides, you may merge the various configurations applicable from the newly installed version to your setup.

NOTE
The dam-update-asset model may be customized. So, if any customizations have been done, then we need to sync the customizations and Experience Manager Guides into the working copy of the model.

  1. DAM Update Asset workflow (Post-processing changes):

  2. Open URL:

    code language-http 
    http://localhost:4502/libs/cq/workflow/admin/console/content/models.html

  3. Select DAM Update Asset workflow.

  4. Click on Edit.

  5. If the DXML Post Process Initiator component is present, ensure that the customizations are synced.

  6. If the DXML Post Process Initiator component is absent, perform the following steps to insert it:

  7. Click Insert component (Responsible for Experience Manager Guides post-processing as the final step in the process).

  8. Configure the Process step with below details:

    Common tab

    Title: DXML Post Process Initiator

    Description: DXML post process initiator step which will trigger a sling job for DXML post-processing of the modified/created asset

    Process tab

    • Select DXML Post Process Initiator from the Process drop down

    • Select Handler Advance

    • Select Done

  9. Click Sync on the top right after completing the changes. You will receive a success notification.

    note note
    NOTE
    Refresh and verify that customized changes and the Experience Manager Guides post-processing step is present in the final workflow model.

  10. Once DAM Update Asset workflow is validated, check corresponding launcher configurations. To do so, go to AEM Workflow interface and open launchers.

    code language-http 
    http://localhost:4502/libs/cq/workflow/content/console.html

    Find and make changes (if necessary) to the following two launchers (that should be active) corresponding to DAM Update Asset workflow:

  11. Launcher for “Node Created” for DAM Update Asset workflow- for condition "jcr:content/jcr:mimeType!=video", the ‘Globbing’ value should be:

    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • ‘excludeList’ should have "event-user-data:changedByWorkflowProcess".
    • Launcher for “Node Modified” for DAM Update Asset workflow - for condition “jcr:content/jcr:mimeType!=video”, the ‘Globbing’ value should be:
    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • excludeList should have "event-user-data:changedByWorkflowProcess".

  12. Once the upgrade is complete, ensure any of the customizations/overlays are validated and updated to match the new application code. Some examples are given below:

    • Any components overlayed from/libs/fmditaor/libsshould be compared with the new product code and updates should be done in overlayed files under/apps.
    • Any clientlib categories used from product, should be reviewed for changes. Any overridden configurations (examples below) should be compared with the latest ones so as to get the latest features:
    • elementmapping.xml
    • ui_config.json(may have been set in folder profiles)
    • amended com.adobe.fmdita.config.ConfigManager
    • Check if any of the custom code was using any old paths (as mentioned in the Migration Mapping section) - should be updated to the new paths so that the customizations also work as expected.

  13. Read about any new configurations brought in the current release (check Release Notes) and see if any functionality is impacted then take appropriate action. An example could be to make use of “Improved file and version handling” introduced in version 4.0, for which you need to enable a configuration.

Steps to index the existing content to use the new find and replace:

Perform the following steps for indexing the existing content and use the new find and replace text at map level:

  • Ensure that the damAssetLucene indexing has been completed. It can take upto a few hours, depending on the amount of data present on the server. You can confirm that the reindexing is completed by checking that the reindex field is set as false in
    http://<server:port>/oak:index/damAssetLucene. Also, if you have added any customizations in damAssetLucene, you may need to apply them again.

  • Run a POST request to the server (with correct authentication) - http://<server:port\>/bin/guides/map-find/indexing. (Optional: You can pass specific paths of the maps to index them, by default all maps will be indexed || For example : https://<Server:port\>/bin/guides/map-find/indexing?paths=<map\_path\_in\_repository\>)

  • You can also pass a root folder to index the DITA maps of a specific folder (and its subfolders). For example, http://<server:port\>/bin/guides/map-find/indexing?root=/content/dam/test. Note that if both the paths parameter and root parameter are passed, only the paths parameter is considered.

  • The API will return a jobId. To check the status of the job, you can send a GET request with job id to the same end point - http://<server:port\>/bin/guides/map-find/indexing?jobId=\{jobId\}(For example: http://localhost:8080/bin/guides/map-find/indexing?jobId=2022/9/15/7/27/7dfa1271-981e-4617-b5a4-c18379f11c42)

  • Once the job is complete, the above GET request will respond with success and mention if any maps failed. The successfully indexed maps can be confirmed from the server logs.

Upgrade to version 4.3.0 upgrade-version-4-3

Upgrading to version 4.3.0 depends on the current version of Experience Manager Guides. If you are using version 4.2 or 4.2.x then you can directly upgrade to version 4.3.0.

NOTE
The post-processing and indexing may take a few hours. We recommend you to start the upgrade process during the off-peak hours.

Prerequisites

Before you start the Experience Manager Guides 4.3.0 upgrade process, ensure that you have:

  1. Upgraded to Experience Manager Guides version 4.2 or 4.2.x and completed their respective installation step.
  2. Closed all translation tasks.

Install version 4.3.0

  1. Download 4.3.0 version package from Adobe Software Distribution Portal.
  2. Install version 4.3.0 package.
  3. Clear the browser cache after installing the package.
  4. Upgrade the ui_config.json file from the XML Editor Configuration tab in the Folder Profile.

After you install version 4.3.0

After you install Experience Manager Guides, you may merge the various configurations applicable from the newly installed version to your setup.

Steps to post process the existing content to use the broken link report

Perform the following steps for post processing the existing content and using the new broken link report:

  1. (Optional) If there are more than 100,000 dita files in the system, update the queryLimitReads under org.apache.jackrabbit.oak.query.QueryEngineSettingsService to a larger value (any value greater than the number of assets present, for example 200,000) and then redeploy.

    table 0-row-3 1-row-3
    PID Property Key Property Value
    org.apache.jackrabbit.oak.query.QueryEngineSettingsService queryLimitReads Value: 200000
    Default Value: 100000

  2. Execute the following APIs to run post-processing on all the files:

    table 0-row-2 1-row-2 2-row-2
    End Point /bin/guides/reports/upgrade
    Request Type POST This script is a POST request hence should be executed via agents like Postman.
    Expected Response The API will return a jobId. To check the status of the job, you can send a GET request with job id to the same end point.
    Sample URL: http://<server:port>/bin/guides/reports/upgrade
    table 0-row-2 1-row-2 2-row-2 3-row-2
    End Point /bin/guides/reports/upgrade
    Request Type GET
    Param jobId: Pass the jobId received from the previous post request.
    Expected Response - Once the job is complete, the GET request responds with success.
    - In case there are errors, share the error logs along with API output with your customer success team.
    Sample URL: http://<server:port>/bin/guides/reports/upgrade?jobId=2022/9/15/7/27/7dfa1271-981e-4617-b5a4-c18379f11c42_678

  3. Revert back to the default or previous existing value of queryLimitReads if you have changed it in step 1.

Upgrade to version 4.3.1 upgrade-version-4-3-1

Upgrading to version 4.3.1 depends on the current version of Experience Manager Guides. If you are using version 4.3.0, 4.2, or 4.2.1 then you can directly upgrade to version 4.3.1.

NOTE
The post-processing and indexing may take a few hours. We recommend you to start the upgrade process during the off-peak hours.

Prerequisites

Before you start the Experience Manager Guides 4.3.1 upgrade process, ensure that you have:

  1. Upgraded to Experience Manager Guides version 4.3.0, 4.2, or 4.2.1 and completed their respective installation step.
  2. (Optional) Closed all translation tasks.
  3. Changed the log level to INFO for com.adobe.fmdita.translationservices.TranslationMapUpgradeScript class and append these logs in a new log file, for example, logs/translation_upgrade.log.

Install version 4.3.1

  1. Download 4.3.1 version package from Adobe Software Distribution Portal.

  2. Install version 4.3.1 package.

  3. You can choose to HIT the trigger to start the translation map upgrade job. For details, see Enable trigger of script via a Servlet.

  4. After you complete the package installation, wait for the following message(s) in the logs:

    Completed the post deployment setup script

    The above message indicates that all the steps of installation are complete.

    In case you encounter any of the following ERROR prefixes, report them to your customer success team:

    • Error in post deployment setup script
    • Exception while porting the translation MAP
    • Unable to port translation map from v1 to v2 for property

  5. Upgrade Oxygen connector plugin released with version 4.2 (if needed).

  6. Clear the browser cache after installing the package.

  7. Continue upgrading the customizations as detailed out in the next section.

Enable trigger of script via a Servlet enable-trigger-serverlet-4-3-1

POST:

http://localhost:4503/bin/guides/script/start?jobType=translation-map-upgrade

Response:

{
"msg": "Job is successfully submitted and lock node is created for future reference",
"lockNodePath": "/var/dxml/executor-locks/translation-map-upgrade/1683190032886",
"status": "SCHEDULED"
}

In the above response JSON, the key lockNodePath holds the path to the node created in the repository pointing to the job submitted. It will automatically be deleted once the job is completed, till then, you can refer to this node for the current status of the job.

Sample log:
The following is a sample of logs that will appear in the log file after you trigger the script.

04.05.2023 14:17:12.876 *INFO* [[0:0:0:0:0:0:0:1] [1683190032736] POST /bin/guides/script/start HTTP/1.1] com.adobe.dxml.common.executor.RunnableSynchronizedOTS Acquiring lock for job : translation-map-upgrade
04.05.2023 14:17:12.897 *INFO* [pool-59-thread-1] com.adobe.fmdita.xmltranslation.ots.TranslationMapUpgradeOTS Starting the thread to upgrade translation map from V1 to V2
04.05.2023 14:17:12.899 *INFO* [pool-59-thread-1] com.adobe.dxml.common.executor.RunnableSynchronizedOTS Initiating lock for node : /var/dxml/executor-locks/translation-map-upgrade/1683190032886
04.05.2023 14:17:12.901 *INFO* [pool-59-thread-1] com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Starting porting of translation map from V1 to V2
04.05.2023 14:17:12.904 *INFO* [pool-59-thread-1] com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Memory increase is of : 764 kB
04.05.2023 14:17:12.906 *INFO* [pool-59-thread-1] com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Completed porting of translation map from V1 to V2
04.05.2023 14:17:12.907 *INFO* [pool-59-thread-1] com.adobe.dxml.common.executor.RunnableSynchronizedOTS Releasing lock for node : /var/dxml/executor-locks/translation-map-upgrade/1683190032886
04.05.2023 14:17:12.909 *INFO* [pool-59-thread-1] com.adobe.fmdita.xmltranslation.ots.TranslationMapUpgradeOTS Completed the thread to upgrade translation map from V1 to V2

Look for com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Completed porting of translation map from V1 to V2 and com.adobe.fmdita.xmltranslation.ots.TranslationMapUpgradeOTS Completed the thread to upgrade translation map from V1 to V2 before proceeding to the next steps.

After you install version 4.3.1

After you install Experience Manager Guides, you may merge the various configurations applicable from the newly installed version to your setup.

NOTE
The dam-update-asset model may be customized. So, if any customizations have been done, then we need to sync the customizations and Experience Manager Guides into the working copy of the model.

  1. DAM Update Asset workflow (Post-processing changes):

  2. Open URL:

    code language-none 
    http://localhost:4502/libs/cq/workflow/admin/console/content/models.html

  3. Select DAM Update Asset workflow.

  4. Click on Edit.

  5. If the DXML Post Process Initiator component is present, ensure that the customizations are synced.

  6. If the DXML Post Process Initiator component is absent, perform the following steps to insert it:

  7. Click Insert component (Responsible for Experience Manager Guides post-processing as the final step in the process).

  8. Configure the Process step with below details:

    Common tab

    Title: DXML Post Process Initiator

    Description: DXML post process initiator step which will trigger a sling job for DXML post-processing of the modified/created asset

    Process tab

    • Select DXML Post Process Initiator from the Process drop down

    • Select Handler Advance

    • Select Done

  9. Click Sync on the top right after completing the changes. You will receive a success notification.

    note note
    NOTE
    Refresh and verify that customized changes and the Experience Manager Guides post-processing step is present in the final workflow model.

  10. Once DAM Update Asset workflow is validated, check corresponding launcher configurations. To do so, go to AEM Workflow interface and open launchers.

    code language-http 
    http://localhost:4502/libs/cq/workflow/content/console.html

    Find and make changes (if necessary) to the following two launchers (that should be active) corresponding to DAM Update Asset workflow:

  11. Launcher for “Node Created” for DAM Update Asset workflow- for condition "jcr:content/jcr:mimeType!=video", the ‘Globbing’ value should be:

    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • ‘excludeList’ should have "event-user-data:changedByWorkflowProcess".
    • Launcher for “Node Modified” for DAM Update Asset workflow - for condition “jcr:content/jcr:mimeType!=video”, the ‘Globbing’ value should be:
    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • excludeList should have "event-user-data:changedByWorkflowProcess".

  12. Once the upgrade is complete, ensure any of the customizations/overlays are validated and updated to match the new application code. Some examples are given below:

    • Any components overlayed from/libs/fmditaor/libsshould be compared with the new product code and updates should be done in overlayed files under/apps.
    • Any clientlib categories used from product, should be reviewed for changes. Any overridden configurations (examples below) should be compared with the latest ones so as to get the latest features:
    • elementmapping.xml
    • ui_config.json(may have been set in folder profiles)
    • amended com.adobe.fmdita.config.ConfigManager

Steps to index the existing content

NOTE
You need not perform these steps if you upgrade from 4.3.0 or 4.2.1.

Perform the following steps for indexing the existing content and use the new find and replace text at map level:

  • Run a POST request to the server (with correct authentication) - http://<server:port\>/bin/guides/map-find/indexing. (Optional: You can pass specific paths of the maps to index them, by default all maps will be indexed || For example : https://<Server:port\>/bin/guides/map-find/indexing?paths=<map\_path\_in\_repository\>)

  • The API will return a jobId. To check the status of the job, you can send a GET request with job id to the same end point - http://<server:port\>/bin/guides/map-find/indexing?jobId=\{jobId\}(For example: http://localhost:8080/bin/guides/map-find/indexing?jobId=2022/9/15/7/27/7dfa1271-981e-4617-b5a4-c18379f11c42)

  • Once the job is complete, the above GET request will respond with success and mention if any maps failed. The successfully indexed maps can be confirmed from the server logs.

Steps to post process the existing content to use the broken link report

NOTE
You need not perform these steps if you upgrade from 4.3.0

Perform the following steps for post processing the existing content and using the new broken link report:

  1. (Optional) If there are more than 100,000 dita files in the system, update the queryLimitReads under org.apache.jackrabbit.oak.query.QueryEngineSettingsService to a larger value (any value greater than the number of assets present, for example 200,000) and then redeploy.

    table 0-row-3 1-row-3
    PID Property Key Property Value
    org.apache.jackrabbit.oak.query.QueryEngineSettingsService queryLimitReads Value: 200000
    Default Value: 100000

  2. Execute the following APIs to run post-processing on all the files:

    table 0-row-2 1-row-2 2-row-2
    End Point /bin/guides/reports/upgrade
    Request Type POST This script is a POST request hence should be executed via agents like Postman.
    Expected Response The API will return a jobId. To check the status of the job, you can send a GET request with job id to the same end point.
    Sample URL: http://<server:port>/bin/guides/reports/upgrade
    table 0-row-2 1-row-2 2-row-2 3-row-2
    End Point /bin/guides/reports/upgrade
    Request Type GET
    Param jobId: Pass the jobId received from the previous post request.
    Expected Response - Once the job is complete, the GET request responds with success.
    - In case there are errors, share the error logs along with API output with your customer success team.
    Sample URL: http://<server:port>/bin/guides/reports/upgrade?jobId=2022/9/15/7/27/7dfa1271-981e-4617-b5a4-c18379f11c42_678

  3. Revert back to the default or previous existing value of queryLimitReads if you have changed it in step 1.

Upgrade to version 4.3.1.5 upgrade-version-4-3-1-5

Upgrading to version 4.3.1.5 depends on the current version of Experience Manager Guides. If you are using version 4.3.1 then you can directly upgrade to version 4.3.1.5.

Install version 4.3.1.5

  1. Download 4.3.1.5 version package from Adobe Software Distribution Portal.

  2. Install version 4.3.1.5 package.

  3. Wait for the installation process to complete successfully.

  4. Continue upgrading the customizations as detailed out in the next section.

After you install version 4.3.1.5

NOTE
If you want to use org.apache.velocity bundle, perform the following steps before uploading the bundle:
  1. Go to <server>:<port>/system/console/bundles.
  2. Search for org.apache.velocity.
  3. Uninstall the searched bundle.
  4. Install the required velocity bundle.

  1. Once the upgrade is complete, ensure any of the customizations/overlays are validated and updated to match the new application code. Some examples are given below:

    • Any components overlayed from /libs/fmdita or /libs should be compared with the new product code and updates should be done in overlayed files under /apps .
    • Any clientlib categories used from product, should be reviewed for changes. Any overridden configurations (examples below) should be compared with the latest ones so as to get the latest features:
    • elementmapping.xml
    • ui\_config.json\ (may have been set in folder profiles)
    • amended com.adobe.fmdita.config.ConfigManager

Upgrade to version 4.4.0 upgrade-version-4-4-0

Upgrading to version 4.4.0 depends on the current version of Experience Manager Guides. If you are using version 4.3.1, 4.3.0, 4.2, or 4.2.1 (Hotfix 4.2.1.3) then you can directly upgrade to version 4.4.0

NOTE
The post-processing and indexing may take a few hours. We recommend you to start the upgrade process during the off-peak hours.

Prerequisites

Before you start the Experience Manager Guides 4.4.0 upgrade process, ensure that you have:

  1. Upgraded to Experience Manager Guides version 4.3.1, 4.3.0, or 4.2.1 (Hotfix 4.2.1.3) and completed their respective installation step.
  2. (Optional) Closed all translation tasks.
  3. Changed the log level to INFO for com.adobe.fmdita.translationservices.TranslationMapUpgradeScript class and append these logs in a new log file, for example, logs/translation_upgrade.log.

Install version 4.4.0

  1. Download 4.4.0 version package from Adobe Software Distribution Portal.

  2. Install version 4.4.0 package.

  3. You can choose to HIT the trigger to start the translation map upgrade job. For details, see Enable trigger of script via a Servlet.

  4. After you complete the package installation, wait for the following message(s) in the logs:

    Completed the post deployment setup script

    The above message indicates that all the steps of installation are complete.

    In case you encounter any of the following ERROR prefixes, report them to your customer success team:

    • Error in post deployment setup script
    • Exception while porting the translation MAP
    • Unable to port translation map from v1 to v2 for property

  5. Upgrade Oxygen connector plugin released with version 4.4.0 (if needed).

  6. Clear the browser cache after installing the package.

  7. Continue upgrading the customizations as detailed out in the next section.

After you install version 4.4.0

After you install Experience Manager Guides, you may merge the various configurations applicable from the newly installed version to your setup.

NOTE
The dam-update-asset model may be customized. So, if any customizations have been done, then we need to sync the customizations and Experience Manager Guides into the working copy of the model.

  1. DAM Update Asset workflow (Post-processing changes):

  2. Open URL:

    code language-none 
    http://localhost:4502/libs/cq/workflow/admin/console/content/models.html

  3. Select DAM Update Asset workflow.

  4. Click on Edit.

  5. If the DXML Post Process Initiator component is present, ensure that the customizations are synced.

  6. If the DXML Post Process Initiator component is absent, perform the following steps to insert it:

  7. Click Insert component (Responsible for Experience Manager Guides post-processing as the final step in the process).

  8. Configure the Process step with below details:

    Common tab

    Title: DXML Post Process Initiator

    Description: DXML post process initiator step which will trigger a sling job for DXML post-processing of the modified/created asset

    Process tab

    • Select DXML Post Process Initiator from the Process drop down

    • Select Handler Advance

    • Select Done

  9. Click Sync on the top right after completing the changes. You will receive a success notification.

    note note
    NOTE
    Refresh and verify that customized changes and the Experience Manager Guides post-processing step is present in the final workflow model.

  10. Once DAM Update Asset workflow is validated, check corresponding launcher configurations. To do so, go to AEM Workflow interface and open launchers.

    code language-http 
    http://localhost:4502/libs/cq/workflow/content/console.html

    Find and make changes (if necessary) to the following two launchers (that should be active) corresponding to DAM Update Asset workflow:

  11. Launcher for “Node Created” for DAM Update Asset workflow- for condition "jcr:content/jcr:mimeType!=video", the ‘Globbing’ value should be:

    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • ‘excludeList’ should have "event-user-data:changedByWorkflowProcess".
    • Launcher for “Node Modified” for DAM Update Asset workflow - for condition “jcr:content/jcr:mimeType!=video”, the ‘Globbing’ value should be:
    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • excludeList should have "event-user-data:changedByWorkflowProcess".

  12. Once the upgrade is complete, ensure any of the customizations/overlays are validated and updated to match the new application code. Some examples are given below:

    • Any components overlayed from/libs/fmditaor/libsshould be compared with the new product code and updates should be done in overlayed files under/apps.
    • Any clientlib categories used from product, should be reviewed for changes. Any overridden configurations (examples below) should be compared with the latest ones so as to get the latest features:
    • elementmapping.xml
    • ui_config.json(may have been set in folder profiles)
    • amended com.adobe.fmdita.config.ConfigManager

  13. If you have added any customizations in damAssetLucene, you may need to apply them again. After making those changes, set reindex as true. This will reindex all the existing nodes with the customizations. Once completed, the reindex flag will be set to false again. This may take a few hours depending on number of assets in the system.

Steps to index the existing content

NOTE
You need not perform these steps if you upgrade from 4.3.0 or 4.3.1.

Perform the following steps for indexing the existing content and use the new find and replace text at map level:

  • Run a POST request to the server (with correct authentication) - http://<server:port\>/bin/guides/map-find/indexing. (Optional: You can pass specific paths of the maps to index them, by default all maps will be indexed || For example : https://<Server:port\>/bin/guides/map-find/indexing?paths=<map\_path\_in\_repository\>)

  • The API will return a jobId. To check the status of the job, you can send a GET request with job id to the same end point - http://<server:port\>/bin/guides/map-find/indexing?jobId=\{jobId\}(For example: http://localhost:8080/bin/guides/map-find/indexing?jobId=2022/9/15/7/27/7dfa1271-981e-4617-b5a4-c18379f11c42)

  • Once the job is complete, the above GET request will respond with success and mention if any maps failed. The successfully indexed maps can be confirmed from the server logs.

Steps to post process the existing content to use the broken link report

NOTE
You need not perform these steps if you upgrade from 4.3.0 or 4.3.1.

Perform the following steps for post processing the existing content and using the new broken link report:

  1. (Optional) If there are more than 100,000 dita files in the system, update the queryLimitReads under org.apache.jackrabbit.oak.query.QueryEngineSettingsService to a larger value (any value greater than the number of assets present, for example 200,000) and then redeploy.

    table 0-row-3 1-row-3
    PID Property Key Property Value
    org.apache.jackrabbit.oak.query.QueryEngineSettingsService queryLimitReads Value: 200000
    Default Value: 100000

  2. Execute the following APIs to run post-processing on all the files:

    table 0-row-2 1-row-2 2-row-2
    End Point /bin/guides/reports/upgrade
    Request Type POST This script is a POST request hence should be executed via agents like Postman.
    Expected Response The API will return a jobId. To check the status of the job, you can send a GET request with job id to the same end point.
    Sample URL: http://<server:port>/bin/guides/reports/upgrade
    table 0-row-2 1-row-2 2-row-2 3-row-2
    End Point /bin/guides/reports/upgrade
    Request Type GET
    Param jobId: Pass the jobId received from the previous post request.
    Expected Response - Once the job is complete, the GET request responds with success.
    - In case there are errors, share the error logs along with API output with your customer success team.
    Sample URL: http://<server:port>/bin/guides/reports/upgrade?jobId=2022/9/15/7/27/7dfa1271-981e-4617-b5a4-c18379f11c42_678

  3. Revert back to the default or previous existing value of queryLimitReads if you have changed it in step 1.

Enable trigger of script via a Servlet enable-trigger-serverlet-4-4-0

NOTE
You need not perform these steps if you upgrade from 4.3.0 or 4.3.1.

POST:

http://localhost:4503/bin/guides/script/start?jobType=translation-map-upgrade

Response:

{
"msg": "Job is successfully submitted and lock node is created for future reference",
"lockNodePath": "/var/dxml/executor-locks/translation-map-upgrade/1683190032886",
"status": "SCHEDULED"
}

In the above response JSON, the key lockNodePath holds the path to the node created in the repository pointing to the job submitted. It will automatically be deleted once the job is completed, till then, you can refer to this node for the current status of the job.

Look for com.adobe.fmdita.translationservices.TranslationMapUpgradeScript Completed porting of translation map from V1 to V2 and com.adobe.fmdita.xmltranslation.ots.TranslationMapUpgradeOTS Completed the thread to upgrade translation map from V1 to V2 before proceeding to the next steps.

NOTE
You should check if the node is still present and the status of the job.

GET: http://<aem_domain>/var/dxml/executor-locks/translation-map-upgrade/1683190032886.json

Steps to handle the 'fmdita rewriter' conflict

Experience Manager Guides has a custom sling rewriter module for handling the links generated in case of cross-maps (links between the topics of two different maps).

If you have another custom sling rewriter in your codebase, use an 'order' value greater than 50, as Experience Manager Guides sling rewriter uses 'order' 50. To override this, you need a value >50. For more details, view Output Rewriting Pipelines.

During this upgrade, since the 'order' value is changed from 1000 to 50, you need to merge the existing custom rewriter, if any, with 'fmdita-rewriter'.

Parent topic:Download and install

Upgrade to version 4.6.0 upgrade-version-4-6-0

TIP
It is recommended to install 4.6.0 Service Pack 1 on top of version 4.6.0. The upgrade process for the 4.6.0 Service Pack 1 release follows the same steps as the 4.6.0 release.

Upgrading to version 4.6.0 depends on the current version of Experience Manager Guides. If you are using version 4.4.0, 4.3.1, 4.3.0, 4.2, or 4.2.1 (Hotfix 4.2.1.3) then you can directly upgrade to version 4.6.0.

NOTE
The post-processing and indexing may take a few hours. We recommend you to start the upgrade process during the off-peak hours.

Prerequisites

Before you start the Experience Manager Guides 4.6.0 upgrade process, ensure that you have:

  1. Upgraded to Experience Manager Guides version 4.3.1, 4.3.0, or 4.2.1 (Hotfix 4.2.1.3) and completed their respective installation step.
  2. (Optional) Closed all translation tasks.
  3. Changed the log level to INFO for com.adobe.fmdita.translationservices.TranslationMapUpgradeScript class and append these logs in a new log file, for example, logs/translation_upgrade.log.

Install version 4.6.0

  1. Download 4.6.0 version package from Adobe Software Distribution Portal.

  2. Install version 4.6.0 package.

  3. You can choose to HIT the trigger to start the translation map upgrade job. For details, see Enable trigger of script via a Servlet.

  4. After you complete the package installation, wait for the following message(s) in the logs:

    Completed the post deployment setup script

    The above message indicates that all the steps of installation are complete.

    In case you encounter any of the following ERROR prefixes, report them to your customer success team:

    • Error in post deployment setup script
    • Exception while porting the translation MAP
    • Unable to port translation map from v1 to v2 for property

  5. Upgrade Oxygen connector plugin released with version 4.6.0 (if needed).

  6. Clear the browser cache after installing the package.

After you install version 4.6.0

After you install Experience Manager Guides, you may merge the various configurations applicable from the newly installed version to your setup.

NOTE
The dam-update-asset model may be customized. So, if any customizations have been done, then we need to sync the customizations and Experience Manager Guides into the working copy of the model.

  1. DAM Update Asset workflow (Post-processing changes):

  2. Open URL:

    code language-none 
    http://localhost:4502/libs/cq/workflow/admin/console/content/models.html

  3. Select DAM Update Asset workflow.

  4. Click on Edit.

  5. If the DXML Post Process Initiator component is present, ensure that the customizations are synced.

  6. If the DXML Post Process Initiator component is absent, perform the following steps to insert it:

  7. Click Insert component (Responsible for Experience Manager Guides post-processing as the final step in the process).

  8. Configure the Process step with below details:

    Common tab

    Title: DXML Post Process Initiator

    Description: DXML post process initiator step which will trigger a sling job for DXML post-processing of the modified/created asset

    Process tab

    • Select DXML Post Process Initiator from the Process drop down

    • Select Handler Advance

    • Select Done

  9. Click Sync on the top right after completing the changes. You will receive a success notification.

    note note
    NOTE
    Refresh and verify that customized changes and the Experience Manager Guides post-processing step is present in the final workflow model.

  10. Once DAM Update Asset workflow is validated, check corresponding launcher configurations. To do so, go to AEM Workflow interface and open launchers.

    code language-http 
    http://localhost:4502/libs/cq/workflow/content/console.html

    Find and make changes (if necessary) to the following two launchers (that should be active) corresponding to DAM Update Asset workflow:

  11. Launcher for “Node Created” for DAM Update Asset workflow- for condition "jcr:content/jcr:mimeType!=video", the ‘Globbing’ value should be:

    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • ‘excludeList’ should have "event-user-data:changedByWorkflowProcess".
    • Launcher for “Node Modified” for DAM Update Asset workflow - for condition “jcr:content/jcr:mimeType!=video”, the ‘Globbing’ value should be:
    code language-json 
    /content/dam(/((?!/subassets|/translation_output).)*/)renditions/original
    • excludeList should have "event-user-data:changedByWorkflowProcess".

  12. Once the upgrade is complete, ensure any of the customizations/overlays are validated and updated to match the new application code. Some examples are given below:

    • Any components overlayed from/libs/fmditaor/libsshould be compared with the new product code and updates should be done in overlayed files under/apps.
    • Any clientlib categories used from product, should be reviewed for changes. Any overridden configurations (examples below) should be compared with the latest ones so as to get the latest features:
    • elementmapping.xml
    • ui_config.json(may have been set in folder profiles)
    • amended com.adobe.fmdita.config.ConfigManager

  13. If you have added any customizations in damAssetLucene, you may need to apply them again. After making those changes, set reindex as true. This will reindex all the existing nodes with the customizations. Once completed, the reindex flag will be set to false again. This may take a few hours depending on number of assets in the system.

Steps to reindex the Experience Manager Guides indexes

  1. Open crx/de and navigate to the index path: /oak:index/guidesAssetProperties

  2. Set the reindex property as true (false by default) and click Save All.

  3. Once the reindex is complete, the reindex property is set to false again, and the reindex count is incremented by 1.

    note note
    NOTE
    This may take a few minutes, depending on the amount of data present.

    4. Follow the same steps for other added or modified indices: `guidesBulkActivation`, `guidesPeerLinkIndex`, and `guidesKonnectTemplateIndex`.

Steps to index the existing content

Perform the following steps for indexing the existing content:

  • Run a POST request to the server (with correct authentication) - http://<server:port\>/bin/guides/map-find/indexing. (Optional: You can pass specific paths of the maps to index them, by default all maps will be indexed || Example : https://<Server:port\>/bin/guides/map-find/indexing?paths=<map\_path\_in\_repository\>)

  • The API will return a jobId. To check the status of the job, you can send a GET request with job id to the same end point - http://<server:port\>/bin/guides/map-find/indexing?jobId=\{jobId\}(for example: http://localhost:8080/bin/guides/map-find/indexing?jobId=2022/9/15/7/27/7dfa1271-981e-4617-b5a4-c18379f11c42_678)

  • Once the job is complete, the above GET request will respond with success and mention if any maps failed. The successfully indexed maps can be confirmed from the server logs.

NOTE
If you are using the custom schema, you must define the path of the custom DTD and XSD catalog.xml files in the AEM repository in the Integrate Catalogs option.

Steps to handle the 'fmdita rewriter' conflict

Experience Manager Guides has a custom sling rewriter module for handling the links generated in case of cross-maps (links between the topics of two different maps).

If you have another custom sling rewriter in your codebase, use an 'order' value greater than 50, as Experience Manager Guides sling rewriter uses 'order' 50. To override this, you need a value >50. For more details, view Output Rewriting Pipelines.

During this upgrade, since the 'order' value is changed from 1000 to 50, you need to merge the existing custom rewriter, if any, with 'fmdita-rewriter'.

Parent topic: Download and install

recommendation-more-help
11125c99-e1a1-4369-b5d7-fb3098b9b178