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.2 vs v.6) - WSO2 Private PaaS 4.1.0 - WSO2 Documentation

Versions Compared

Key

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

...

The Git repository folder structure for the various WSO2 cartridges that are available in WSO2 Private PaaS are as follows:

...

The latter mentioned Git repository folder structures for WSO2 products have been derived by following the steps below:

...

Info

You do not need to create a folder structure for WSO2 API Manager (AM) cartridge uses an internal Git repository that is provided by WSO2 Private PaaS. Therefore, the tenant does not need to maintain a remote Git repository.

...

├── synapse-configs
│   └── default
│       ├── endpoints
│       ├── event-sources
│       ├── local-entries
│       ├── priority-executors
│       ├── proxy-services
│       ├── sequences
│       └── tasks

...

as users do not need to provide existing artifacts, because the artifact creation process happens in the publisher node. However, as artifact synchronization needs to take place in the Gateway nodes, you need to provide the artifact repository details at application signup for multitenant applications, and in the application definition JSON for single tenant applications.

To get the respective Git repository folder structure for WSO2 products follow the instructions below:

...

  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
    Localtab
    titleOn Linux
    Code Block
    ./wso2server.sh
    Localtab
    titleOn Windows
    Code Block
    wso2server.bat
  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.
      Image Added

    3. Enter the required details as follows:
      • Domain -  The domain name for the organization, which should be a unique name (e.g., abc.com).
      • 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
  7. Check the list of folders that need to be created in the Git repository.
    ls

 

...

  1. <TENANT_ID>
  2. Copy the content in the latter mentioned folder recursively to the local Git repository root folder.

    Info

    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

...

  1. module meta files, which are used to configure properties related to modules, such as, Rampart and Rahas

...

  1. .

You should take a look at the existing folder structure for a tenant on a standalone pack to identify the default configuration files that you need to add to the respective Git repository folder structure.
  1. Commit the changes and push it to the Git repository.