Sample Applications

The sample applications demonstrate Mosaic functionality using real-world content and tasks. The samples are fully functional and you can use them to create your own applications.

To access Mosaic sample applications, deploy the samples to the standalone Tomcat server included with Mosaic. Or you can deploy them to a Mosaic server deployed to LiveCycle ES2.5. Ensure that the sample roles and users are defined on the server before you attempt to access the samples.

Deploying the sample applications

Use the Ant build files provided with the Mosaic installation to deploy sample applications to the server. By default, the build files are configured to deploy the samples to a Mosaic server using the following values:

<property name="protocol" value="http" /> 
<property name="server" value="localhost" /> 
<property name="port" value="8080" /> 
<property name="username" value="designer" /> 
<property name="password" value="password" />

Before you begin, ensure that you have Ant 1.7.0 or later installed.

To deploy to a different server location, modify the Ant build files with the new information before running Ant. You can also modify the Ant build files to use a different user or password.

To run Ant, type ant from the command line. When you do not provide arguments, Ant looks for a build.xml file in the current directory.

Note: If you encounter a timeout error while deploying sample applications or catalogs, add a maxwait attribute with a large value to the corresponding build.xml file. For example, the following change to the build.xml file located in the [Mosaic installation directory]/samples/general folder sets the maxwait attribute value to 60000000000 seconds:
<mosaic-application action="import" 
    maxwait="60000000000" />

Sample application to deploy

Directory in which to run Ant

All samples and demos

[Mosaic install directory]/samples/

General sample applications (Basic Application, Brokerage, HTML Example, Style Example, and TileGame)

[Mosaic install directory]/samples/general/

ClientDashboard and SlateDashboard applications

[Mosaic install directory]/samples/clientDashboard/

mockDataService application

[Mosaic install directory]/samples/stockDataService/

Accessing Mosaic sample applications

Once you deploy Mosaic samples to a Mosaic server, you can access the sample applications using the desktop client or browser client. The desktop client displays all deployed applications on the My Apps tab. To access sample applications using the browser client, type http://[host name]:[port]/mosaic/#/applications/[application name] in the URL line of a web browser. The application name corresponds to the name attribute specified in the Ant task used to deploy the application to the Mosaic server. For example, if you installed Mosaic on the standalone server, you can use the following URLs to connect to the sample applications:



Browser Client Default URL

Basic Application

The Basic application illustrates how to send messages and set context properties.



The Brokerage application allows you to manage portfolios for a list of contacts. When you select a contact in the Contacts tile, you can use the Portfolio tile to add or remove stocks from the selected contact’s portfolio. The Google Finance information for the stock that is selected in the Portfolio tile appears in the stock information tile.


Client Dashboard

The ClientDashboard application is a customer service desk that contains the tiles with the following functions:

  • Track open cases

  • Track bugs related to specific cases

  • Display detailed information about a client associated with a particular case

  • Display overall issue statistics for a client associated to a particular case

When you change the case in the open cases tile, the other tiles are updated to display information that is associated with the case.


HTML Example

The HTML Example application provides an HTML version of the Mosaic desktop client. You can launch sample applications, download Adobe AIR, and confirm the versions of the Mosaic client and server software.



An example of loading a "service" before loading any tiles within an application. The service example illustrates how to create functionality outside a tile and then use the features across multiple tiles.


Slate Client Dashboard

An alternative version of the Client Dashboard application, to illustrate how to use custom style sheets in an application. It uses a style sheet stored in the catalog to change the appearance of the application.


Style Example

An alternative version of the Basic application, to illustrate how you can use custom skinning to create unique navigation experiences for Mosaic users.



The TileGame application illustrates how you can use the interaction between tiles to create a game. Each tile represents a playing card with two sides. To start a game, click a tile. Continue turning over cards two at a time to find cards that match. The game is complete when you have found a match for each card. The timer tile tracks how long it takes you to complete the game.


To access the samples, you enter a user account and password. For example, the default user accounts include user and designer, which both use password as their password. For more information, see Mosaic users and roles.