This documentation is for WSO2 App Factory 1.0.0. View documentation for the latest release.
Skip to end of metadata
Go to start of metadata

WSO2 App Factory supports the development of many types of enterprise applications such as Web apps, Ruby, PHP, workflows, integrations, business rules, mashups, mobile apps etc. After you log in to the App Factory portal, the portal's overview page appears. The overview page shows details of the applications you have created or been invited to participate in.

Create applications using the following steps:

  1. Log in to the App Factory portal (for the online version, try https://appfactorypreview.wso2.com). 
  2. The user overview window opens. It gives you  a summary view of all applications you participate in.
  3. Click Add New Application.
  4. Fill in the form that appears.


    The table below explains the mandatory fields:

    FieldDescription
    Application Name*A display name for the application. Must be up to 30 characters and contain only letters of the alphabet and numeric. For example, HelloWorldDemoApp.
    Application Key*

    The application's unique identifier, which is used to create the repository and deliverable names (for example, the WAR file name).

    App Factory auto-generates a key when you click inside that field after giving an application name. You can change this key if you want. The application key must be unique across the App Factory deployment and you get a warning message if it is already in use.

    Application Type*

    The type of the application archive. At the moment, App Factory supports the following types. Some of these types might be disabled if they are not configured in your system.

    • Web Application (deployed as WAR file)
    • PHP Web Application
    • JAX-RS
    • JAX-WS
    • WSO2 ESB
    • WSO2 BPS (BPEL process .zip file. Also see BPEL Support and Extensions )
    • Data Services (Data as a service)
    • WSO2 Jaggery (applications with server-side and client-side Java Script http://jaggeryjs.org)

    We work on facilitating all of the commonly-used application types with new versions of App Factory. In the meantime, if you cannot find a particular application type, you can add it. See Adding new Application Types.

    Repository Type*

    Defines the source code repository where the application is stored. Some of the options include GIT and SVN. Some of these types might be disabled if they are not configured in your system.

    While we work on facilitating all common types, if you cannot find the repository type of your choice, you can add it. See Configuring Repository Provider.

  5. Click Create Application button at the end of the screen. 
  6. Application creation process starts.

    It usually takes 20-30 seconds to complete as an underlying BPEL process executes multiple tasks in the background. Until these tasks complete, the application will be in Pending state. 
    Background tasks of application creation process

    • Creating a repository for the application with your credentials configured for this repository.
    • Creating a tenant for your application in each of the servers your application executes on (for example, development , staging and production). As the application's owner, you get the Admin role assigned to you.
    • Adding a build definition to the build server.
    • Committing a template application to the repository.
  7. Once the application is added, click on its name to view its Overview page. For example,

    The application's overview shows:

    • Build status: By default, a trunk is created in the repository type you selected. It is automatically built and deployed at the start. The default behavior of the system is to automatically build and deploy trunk/branches each time you commit to the code repository. You can change this default behavior and manually trigger builds and deployments. See Building and Deploying the Application.
    • Life cycle information: The life cycle stage of the application at the start is Development. For information on managing its entire life cycle, see Managing Lifecycles.
    • Team working on the application: Initially, the application creator (i.e., you) is listed as the App Owner. You can invite more people and build your team. See Building your Team.
    • List of bugs and issues: Initially, there are no issues or bugs opened against this application. By default, the system is integrated with Redmine for project management and tracking bugs, issues and features. You can also add a different tool of your choice. See Adding Tests and Tracking Issues.
    • Resources used by the application: List of data sources, databases, APIs, and properties. Initially, there are none but you can configure new ones. See Configuring Resources.
    • Test button: Since the trunk is automatically built and deployed for you, you get the Test button associated with the trunk by default. Use it to launch and interact with your application/service.

After adding a new application, the next step is to invite contributors to its development, testing and management tasks. See Building your Team.

  • No labels