Prior to subscribing to a cartridge, the user will you have to create a remote Git repository in GitHub to store their your artifacts. The Git repository folder structure will vary based on the respective WSO2 cartridge. Therefore, it is very important that you create the user creates the Git folder structure accurately.
...
- 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
...
- Download the respective WSO2 product pack.
- Navigate to the
<PRODUCT_HOME>/repository/deployment/server/directory.cd <PRODUCT_HOME>/repository/deployment/server - Check the list of folders that need to be created in the Git repository.
ls