com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.

Uploading a Created Data Service

After creating a data service (.dbs file) file from scratch, deploy it to the ESB profile of WSO2 Enterprise Integrator (WSO2 EI) using one of the methods listed below:

Uploading via the management console

Follow the steps given below to upload the data service through the management console:

  1. Download the product installer from here, and run the installer.
    Let's call the installation location of your product the <EI_HOME> directory. This is located in a place specific to your OS as shown below:

    OSHome directory
    Mac OS/Library/WSO2/EnterpriseIntegrator/6.6.0
    WindowsC:\Program Files\WSO2\EnterpriseIntegrator\6.6.0\
    Ubuntu/usr/lib/wso2/EnterpriseIntegrator/6.6.0
    CentOS/usr/lib64/EnterpriseIntegrator/6.6.0

  2. Start the ESB profile:

  3. Go to the management console: https://localhost:9443/carbon.
  4. Sign in using admin as the username and password.
  5. Click Data Service > Upload.
  6. Select the database backup (.dbs) file and click Upload

    Don't' have a database backup file? Upload a sample data service that is stored in the <EI_HOME>/samples/data-services/dbs folder.

  7. If the file is deployed successfully, the Deployed Services window appears with the new data service listed. From here, you can manage your service. See Working with Data Services .

Uploading as a hot deployment

Alternatively, copy the database backup (.dbs) file to <EI_HOME>/repository/deployment/server/dataservices folder.
It will be deployed instantly as hot deployment, which is enabled in Data Services Server by default.

When adding a data service file to the ESB profile for the first time, you need to create a folder named dataservices in the <EI_HOME>/repository/deployment/server directory. 

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.