Run a composite application

To run a composite application, you can either launch it from Flash Builder or use a web browser to navigate to the application URL on the Experience Server.

    Launch a composite application from Flash Builder

    When you launch a composite application from Flash Builder, Flash Builder automatically deploys the application and any referenced catalogs before it runs the application.

    1. In Flash Builder, in Package Explorer, right-click the application (AXML) file and then click Run As > Run Configurations.

    2. In the list of launch configuration types, select Composite Application and then click the New Launch Configuration button .

      By default, the current project and AXML file are selected. If there is no current project, click Browse to select the AXML file.

    3. Optionally, under Autodeploy, clear Composite Application File if you do not want the launcher to deploy the application. Clear Referenced Catalogs if you do not want the launcher to deploy any catalogs associated with the application.

    4. Click Run.

      Flash Builder opens your default web browser and navigates to the application URL.

    5. Log in to the Experience Server. The default value for both the username and password is admin.

    Launch a composite application using a web browser

    You can run a composite applications by navigating to the application URL on the Experience Server. Application URLs use the following format, where [application name] is the value of the name attribute from the <Application> element in the application (AXML) file:

    http://[host name]:[port]/content/mosaic/#/applications/[application name]

    Customize the composite application URL

    By default, the URL for composite applications is http://[host name]:[port]/mosaic/#/applications/[application name].

    You can change the context root to a custom value. For example, http://[host name]:[port]/CustomUrlRoot/#/applications/[application name].

    Add a new mapping

    1. Log in to the Experience Server as an administrator. The default URL for the server is http://localhost:4502/.

    2. Click CRXDE Lite.

    3. In the upper-right corner of the CRXDE Lite page, ensure you are logged in as an administrator.

      For example, you cannot add the mapping if you are logged in as anonymous@crx.default.

    4. Right-click /etc/map/mosaic.default, and then click Copy.

    5. Right-click /etc/map/, and then click Paste.

    6. Right-click /etc/map/Copy of mosaic.default, and then click Rename.

    7. Enter the name of the context root that you want to use. For example, CustomUrlRoot.

    Modify the mapping properties

    1. In CRXDE Lite, select your renamed folder to display its properties on the Properties tab.

    2. On the Properties tab, double-click the sling:match item. For Value, replace mosaic with your context root. For example, ^[^/]+/[^/]+/CustomUrlRoot.

      Do not press Enter.

    3. When you are finished editing the value, click outside the Value field.

    Add the custom URL to POST.jsp

    1. In CRXDE Lite, double-click the following file to open it in the editor: /libs/mosaic/components/endpoint/POST.jsp.

    2. Locate the following entry in the file:

      String vanityUrl = null;

    3. Change null to your context root. For example:

      String vanityUrl = "CustomUrlRoot";

    4. In the upper-left corner of the CRXDE Lite page, click Save All to save your changes.

    Add security to the context root

    1. Log in to Apache Felix Web Console Configuration as an administrator.

      The URL for the web console is http://[host name]:[port]/system/console/configMgr. For example, http://localhost:4502/system/console/configMgr.

    2. On the Configuration panel, click Adobe LiveCycle Mosaic.

    3. In the last item in the list of sling.auth.requirements.name, click + (plus sign).

    4. In the new row, create an entry for applications at your context root. For example:

      +/CustomUrlRoot/applications

    5. In the entry you created, click + (plus sign). In the new row, create an entry for catalogs at your context root. For example:

      +/CustomUrlRoot/catalogs

    6. Click Save.

    You can now access your applications using the custom context root. For example, if the application Basic is deployed, you can access it using any of the following URLs:

    • http://localhost:4502/mosaic/#/applications/Basic

    • http://localhost:4502/content/mosaic/#/applications/Basic

    • http://localhost:4502/CustomUrlRoot/#/applications/Basic