Deploying an Extension File

Once a Registry extension file is created, you have to upload it. Follow the instructions below to deploy the extension file in the WSO2 Governance Registry.

You need to manually add the static collections in the storage path of the extension file before deploying it. For instructions on how to add a collection, see Adding a Collection.

1. Start up the WSO2 Governance Registry. See Running the Product for more information.

2. Enter Username, Password to login to the Management Console.

Read about Managing Entries or Content to learn how to create the Collection structure and upload the Configuration File.

3. Click on the "Extensions" tab of the Management Console, then click on "Artifact Types" menu item from the Extensions menu and Click on "Add new Artifact" link.

4. Now user can edit the sample configuration model appropriately and click on "Save" button.

5.Restart the server to view the asset type which you added above in the Governance Center - Publisher.

You can avoid this restart by changing the default value of the assetTypesHotDelploy property to true, in the <G-REG_HOME>/repository/deployment/server/jaggeryapps/publisher/config/publisher-tenant.json and <G-REG_HOME>/repository/deployment/server/jaggeryapps/publisher/config/store-tenant.json files.

6. Click on the "Main" tab to see the Metadata panel. User could see that "Enterprise Application" label appears at the "Add" pane and "Enterprise Applications" label appears at the "List" pane.

6. Click "Enterprise Application" in the "Add" pane. User will see an "Add Enterprise Application" window. Enter the form fields and click on "Save" button.

7. Click "Enterprise Applications" in the "List" pane to see the list of Enterprise Applications that the user saved.

8. You can see the content in "Standard" or "Custom" view.

To switch to Custom view, click the "Custom view" link.