com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.
Deploying Custom Application Artifacts in Private PaaS
After you have deployed PPaaS, you can now look at deploying your own custom application artifacts as a service (e.g., ESB as a service).
Follow the instructions below to deploy an application artifact in Private PaaS.
- Develop your artifacts locally on your computer.
- Use WSO2 Developer Studio to package your application artifacts into deployable archives. Â
- Deploy the Composite Application Archive (CAR) file, which contains your application artifacts, in the cluster.
- Create a Git repo with the folder structure that corresponds to the respective application.
For example, if you are deploying ESB as a service, create the ESB folder structure in the Git repository.
For more information, see Creating a Git Repository for Artifact Distribution. - Commit the CAR file to the Git repository.
- Create a Git repo with the folder structure that corresponds to the respective application.
Deploy the application.Â
If the application is a single tenant application, ensure to add the artifact repository related details in theÂ
subscribableInfo
 section, under theartifactRepository
section, of the application JSON definition.
Example:"artifactRepository":{ "privateRepo":false, "repoUrl":"https://github.com/lakwarus/single-cartridge.git", "repoUsername":"", "repoPassword":"" }
- Optionally, sign up to the application if the application is a multi-tenant application.
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.