This documentation is for WSO2 Private PaaS 4.1.0. View documentation for the latest release.
Page Comparison - Creating a Git Repository for Artifact Distribution (v.5 vs v.6) - WSO2 Private PaaS 4.1.0 - WSO2 Documentation

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Download the WSO2 product pack that corresponds to the WSO2 application that you wish to deploy.
  2. Unzip the downloaded binary pack.
  3. Start the downloaded WSO2 product server.

    Localtab Group
    titleOn Linux
    Code Block
    titleOn Windows
    Code Block
  4. Create a tenant via the respective WSO2 product management console.
    1. Sign into the respective WSO2 product management console via one of the following URLs. Use admin as the username and password:

    2. On the Configure tab of the Management Console, click Add New Tenant.

    3. Enter the required details as follows:
      • Domain -  The domain name for the organization, which should be a unique name (e.g.,
      • Usage plan for the tenant - The usage plan defines limitations (such as number of users) for the tenant.  
      • First Name - First name of the tenant admin.
      • Last Name - Last name of the tenant admin. 
      • Admin Username - The username the tenant admin will use to log in. The username must always end with the domain name (e.g., [email protected]).
      • Email - The email address of the admin.
    4. Click Save.
    5. Sign out of the WSO2 product management console.
  5. Sign into the WSO2 product management console using the newly created tenant credentials.
  6. Navigate to the <PRODUCT_HOME>/repository/deploymenttenant/server<TENANT_ID> directory.
    cd <PRODUCT_HOME>/repository/deploymenttenant/server<TENANT_ID>
  7. Copy the content in the latter mentioned folder recursively to the local Git repository root folder.


    You need to copy the folder structure in this manner as there are default configurations that are needed, e.g., In WSO2 ESB, there are module meta files, which are used to configure properties related to modules, such as, Rampart and Rahas.

  8. Commit the changes and push it to the Git repository.