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.

  1. Develop your artifacts locally on your computer.
  2. Use WSO2 Developer Studio to package your application artifacts into deployable archives.  
  3. Deploy the Composite Application Archive (CAR) file, which contains your application artifacts, in the cluster.
    1. 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.
    2. Commit the CAR file to the Git repository.
  4. Deploy the application. 

    If the application is a single tenant application, ensure to add the artifact repository related details in the subscribableInfo section, under the artifactRepository section, of the application JSON definition.
    Example:

       "artifactRepository":{  
          "privateRepo":false,
          "repoUrl":"https://github.com/lakwarus/single-cartridge.git",
          "repoUsername":"",
          "repoPassword":""
       }
  5. 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.