There are two models in which you can setup a remotely deployed registry instead of an embedded registry
You have to change the URL of the database in the registry.xml file to point to the database of the remote registry instance.
<currentDBConfig>wso2registry</currentDBConfig>
<dbConfig name="wso2registry">
<url>jdbc:h2:database/WSO2CARBON_DB</url>
<userName>wso2carbon</userName>
<password>wso2carbon</password>
<driverName>org.h2.Driver</driverName>
<maxActive>50</maxActive>
<maxWait>60000</maxWait>
<minIdle>5</minIdle>
</dbConfig>
More information on setting up WSO2 Governance Registry with various types of databases can be found in the Registry Configurations guide.
You have to add the following entry in the carbon.xml, which is inside conf directory.
<Registry>
<Type>remote</Type>
<Url>http://remote-ip:port/registry/</Url>
<Chroot>/prefix</Chroot>
<Username>username</Username>
<Password>password</Password>
</Registry>
Provide the URL of the remote registry as the value of Url tag. As the value of chroot tag, you have to give the path to the directory you are going to use as the root. Then change the username and password by providing the credentials of the user.