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

Adding a SOAP Service

You can create SOAP service artifacts using the G-Reg Publisher either manually, or by adding a WSDL as explained below.

Adding a SOAP service using a WSDL

Follow the steps below to create a SOAP service using a WSDL.

  1. Log in to the G-Reg Publisher using the following URL and admin/admin credentials: https://<G-REG_HOST>:<G-REG_PORT>/publisher
  2. Click the Add button of the SOAP Service box as shown below.

  3. Select Add a SOAP Service using a "WSDL" option as shown below.

  4. Click Continue.

  5. Select whether to import the WSDL from URL or upload it from a file as shown below.

  6. If you selected Import Policy from a URL, specify the URL of the WSDL, its name and version as shown below. 

    During the WSDL import, G-Reg provides WSDL validation (not supporting WSDL2), WS-I Validation, and Schema Validation. WSDL and Schema validation requires a connection to the internet for the very first time, and will not work on systems without internet connectivity. Instead of just storing the required asset in the repository, G-Reg does some other tasks that are specific to the metadata type, and those information are mentioned on metadata type-based descriptions. You can disable WSDL and Schema validation in the <G-REG_HOME>/repository/conf/registry.xml file. For information on validating WSDLs offline, see Validating WSDLs Offline.

  7. If you selected Upload WSDL from a file, click Browse to select a single WSDL file or an archived file (in .zip or .gar extension) containing multiple WSDL files to upload it. Then specify its version as shown below. 

    Governance Archives can be used to upload multiple base WSDLs at the same time. This can be done by placing all the base WSDLs at the top-level folder of the archive (.zip or .gar file), and including the others inside a directory named "wsdls". For information on uploading a WSDL file with several associated resources (e.g. Schemas and other WSDLs), see Uploading a WSDL with other associated assets.

  8. Click Create

  9. Refresh the screen to view the new WSDL artifact you added as shown below.

Uploading a WSDL with other associated assets

A WSDL file can have several associated resources (e.g. Schemas and other WSDLs) that are required to be uploaded with it. Follow the instructions below to create a governance archive of the WSDL file you want to upload, including the associated Schemas placed in a proper directory structure.

  1. Save the WSDL file in your local file system to a directory (e.g. myWSDL).
  2. Open the WSDL file, and identify the directory structure of the associated resources. 
  3. Create a folder named "schemas" inside the folder myWSDL. Now, place the Schemas within the "schemas" folder. 

    If you are importing a WSDL that has other associated WSDLs, place the associated WSDLs in a directory named "wsdls."

  4. Replace the Schema locations to reflect a relative directory structure in the WSDL file.
  5. Open each Schema file, and make the absolute Schema locations of the other associated Schemas relative.  
  6. Save and close the WSDL and Schema files. 
  7. Create a Governance Archive of the myWSDL directory (e.g. myWSDL.zip or myWSDL.gar). 
  8. Upload the archived file to the Governance Registry using the G-Reg Publisher. You can browse and view all the uploaded assets added separately in each asset type menu.

Adding a SOAP service manually

Follow the steps below to manually create a SOAP service.

  1. Log in to the G-Reg Publisher using the following URL and admin/admin credentials: https://<G-REG_HOST>:<G-REG_PORT>/publisher
  2. Click the Add button of the SOAP Service box as shown below.

  3. Select Add a SOAP Service manually option as shown below.
  4. Click Continue.
  5. Enter the details of the service which you want to create as shown in the example below.
  6. Click Create

  7. Refresh the screen to view the new WSDL artifact you added as shown below.

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