Creating Applications

Applications are created from the "My Applications" tab of App Builder, which is the default tab shown after running appbuilder open. If there are no applications, then the tab appears similar to:

With applications listed, the tab might look like the following:

Applications are created by using the "Actions" links found along the left-hand side.

Create new application

The "Create new application" link is equivalent to the CLI command zero create <name>:

• "Name" is the application name.
• "Root directory" is the parent directory in which the new application is created.
• (Optional) "Description" is available for developers. The value is stored in config/ivy.xml for that application.
• "Module Group" indicates the module group from which the application will be created. Only known module groups are listed.

Create from repository

The "Create from repository" link is equivalent to the CLI commands zero create <name> copy <module> or zero create <name> linkto <module>, depending on the selected setting in the dialog:

• "Module Group" indicates the module group from which the module will be copied. Only known module groups are listed.
• "Module to Copy / Linkto" specifies the module to copy. This field also operates as a filter for the list. For example, entering ".demo" filters the list to the module references (org:module:version) that contain that string.
• "Name" is the name of the application to be created; defaults to the name of the module to be copied/linked.
• "Link application to the specified module" specifies whether the create is a "copy" or "linkto".
  • Choose "copy" (unchecked) if you want a local copy of the module.
  • Choose "link" (checked) if you're overridding a module (config, code) and want to be able to update that dependent module at some point.
• "Root Directory" is the parent directory in which the new application is created.

Open existing application

Existing applications may be opened in App Builder with the "Open existing application" link:

• "Application Home" is the path to the application directory. The type-ahead feature allows you to browse the file system.

Import application

Zipped WebSphere sMash modules are uploaded, expanded, and added to the application list in one step. Zipped modules include those produced by the zero package command.

"Not Runnable" applications

Applications are resolved when they are created/opened/imported. If the application cannot be resolved, then a warning message is displayed with details and the status is shown as "Not Runnable".

Common causes of this situation are:

1. Invalid ivy.xml or zero.config
2. An application that's out of sync with the local repository.

The first cause is rememdied by editing the offending file. The second cause, likely shown in the warning as "missing dependencies", can be reconciled by "updating" the application, as described in the Managing application dependencies section.