Page History
...
Info |
---|
If you want to migrate your Governance Registry configurations from one instance to another (such as when promoting your instance from test to production) using the same Governance Registry release, see Migrating the Governance Registry. |
Upgrading from an older version
...
To connect the new product version, to the database of the previous version, configure the following files:
- Configure
<G-REG_HOME>/repository/conf/datasources/master-datasources.xml
. For more information on how to do this for your database, see Working with Databases. Navigate to the
<G-REG _HOME>/repository/conf
directory, and update the datasource references inuser-mgt.xml
,registry.xml
andapi-manager.xml
files, to match the updated configurations in themaster-datasources.xml
file, which you made in the above step.Tip The following are sample configurations if the datasource is
jdbc/WSO2CarbonDB
. If you have either changed the default H2 CarbonDB, or created separate databases for user management, identity etc. in G-Reg 5.1.0, then point to the same databases in the respective configuration files of G-Reg 5.2.0 accordingly.Code Block language html/xml title registry.xml <dbConfig name="wso2registry"> <dataSource>jdbc/WSO2CarbonDB</dataSource> </dbConfig>
Code Block language html/xml title user-mgt.xml <UserManager> <Realm> <Configuration> ... <Property name="dataSource">jdbc/WSO2CarbonDB</Property> </Configuration> ... </Realm> </UserManager>
Code Block language html/xml title api-manager.xml <DataSourceName>jdbc/WSO2CarbonDB</DataSourceName>
- Configure
If there are several 1000s of artifacts in the system, increase the value of the
<indexingFrequencyInSeconds>
property (e.g. to 10), or reduce the value of the<batchSize>
property (e.g. to 10) in the<
G-REG_HOME>/repository/conf/registry.xml
file as shown below.Code Block language xml <indexingConfiguration> <solrServerUrl>http://192.168.48.220:8983/solr/registry-indexing</solrServerUrl> <startingDelayInSeconds>35</startingDelayInSeconds> <indexingFrequencyInSeconds>3</indexingFrequencyInSeconds> <!--number of resources submit for given indexing thread --> <batchSize>50</batchSize> <!--number of worker threads for indexing --> <indexerPoolSize>50</indexerPoolSize> <!-- location storing the time the indexing took place--> </indexingConfiguration>
...