This documentation is for WSO2 Private PaaS 4.1.0. View documentation for the latest release.
Git Repository Folder Structure - WSO2 Private PaaS 4.1.0 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Prior to subscribing to a cartridge, you have to create a remote Git repository in GitHub to store your artifacts. The Git repository folder structure will vary based on the respective WSO2 cartridge. Therefore, it is very important that you create the Git folder structure accurately.

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

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.

  • WSO2 Application Server (AS)

    ├── axis2modules
    ├── axis2services
    ├── jaggeryapps
    ├── jsservices
    ├── webapps

     
  • WSO2 Enterprise Service Bus (ESB)

    ├── axis2modules
    ├── axis2services
    ├── modulemetafiles
    ├── servicemetafiles
    ├── webapps

    ├── synapse-configs
    │   └── default
    │       ├── endpoints
    │       ├── event-sources
    │       ├── local-entries
    │       ├── priority-executors
    │       ├── proxy-services
    │       ├── sequences
    │       └── tasks
     
  • WSO2 Business Process Server (BPS)

    ├── axis2modules
    ├── axis2services
    ├── webapps
     
  • WSO2 Business Activity Monitor (BAM)

    ├── axis2modules
    ├── axis2services
    ├── bam-toolbox

    ├── jaggeryapps
    ├── webapps


  • WSO2 Identity Server (IS)

    ├── artifactMetafiles  
    ├── axis2modules  
    ├── axis2services
    ├── jaggeryapps 
    ├── modulemetafiles 
    ├── servicemetafiles 

    ├── userstores 
    ├── webapps 

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

  1. Download the respective WSO2 product pack.
  2. Navigate to the <PRODUCT_HOME>/repository/deployment/server directory.
    cd <PRODUCT_HOME>/repository/deployment/server
  3. Check the list of folders that need to be created in the Git repository.
    ls

 

You need to also add the required default configurations in the respective Git folder structure. For example for WSO2 ESB, there are a few module meta files, which are used to configure properties related to modules, such as, Rampart and Rahas. These configurations change based on the product.
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.

 

 

  • No labels