Skip to main content

Mounting remote governance registry

Let's say we have AS instance and G-reg instance, both instance have pointed their governance registry to MySql database.

Now I want to mount the AS's governance registry to G-reg's /_system/as/governance path

1. Shutdown both instances

2. Configurations to be done in G-reg side (in registry.xml file)

mount G-reg governance registry as

<mount path="/_system/governance" overwrite="true">
        <instanceId>greggov</instanceId>
        <targetPath>/_system/governance</targetPath>
    </mount>

mount AS governance registry as

<mount path="/_system/as/governance" overwrite="true">
        <instanceId>asgov</instanceId>
        <targetPath>/_system/as/governance</targetPath>
    </mount>

3. Configuration to be done in AS side (in registry.xml file)

mount AS governance registry

<mount path="/_system/governance" overwrite="true">
        <instanceId>asgov</instanceId>
        <targetPath>/_system/as/governance</targetPath>
    </mount>

4. Now we need to do a data migration as follows
Use AS database and execute following sql commands

Update REG_PATH Set REG_PATH_VALUE = REPLACE(REG_PATH_VALUE, '/_system/governance', '/_system/as/governance') where REG_PATH_VALUE like '/_system/governance%';

Update REG_LOG Set REG_PATH = REPLACE(REG_PATH, '/_system/governance', '/_system/as/governance') where REG_PATH like '/_system/governance%';

Update REG_LOG Set REG_ACTION_DATA = REPLACE(REG_ACTION_DATA, '/_system/governance', '/_system/as/governance') where REG_ACTION_DATA like '%/_system/governance%';

Update REG_ASSOCIATION Set REG_SOURCEPATH = REPLACE(REG_SOURCEPATH, '/_system/governance', '/_system/as/governance'), REG_TARGETPATH = REPLACE(REG_TARGETPATH, '/_system/governance', '/_system/as/governance') where REG_SOURCEPATH like '/_system/governance%' or REG_TARGETPATH like '/_system/governance%';

5. Restart the both instances.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to generate random unique number in SOAP UI request

eg 1: ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} eg 2: ${=java.util.UUID.randomUUID()} ${=java.util.UUID.randomUUID()} ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf
Post a Comment
Read more

Tips on using environment variables in WSO2 Integration Cloud

Environment variables allow you to change an application's internal configuration without changing its source code. Let’s say you want to deploy the same application in development, testing  and production environments. Then database related configs and some other internal configurations may change from one environment to another. If we can define these configurations as an environment variables we can easily set those without changing the source code of that application. When you deploy your application in WSO2 Integration Cloud, it lets you define environment variables via the UI. Whenever you change the values of environment variables, you just need to redeploy the application for the changes to take effect. Predefined environment variables Key Concepts - Environment Variables   provides you some predefined set of environment variables which will be useful when deploying applications in WSO2 Integration Cloud. Sample on how to use environment variables ...
Post a Comment
Read more

WSO2 ESB communication with WSO2 ESB Analytics

This blog post is about how & what ports involved when connecting from WSO2 ESB to WSO2 ESB Analytics. How to configure: This document explains how to configure it https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics Let's say we have WSO2 ESB  and WSO2 ESB Analytics packs we want to run in same physical machine, then we have to offset one instance.  But we don't want to do that since WSO2 ESB Analytics by default come with the offset. So WSO2ESB will run on 9443 port, WSO2 ESB Analytics will run on 9444 port WSO2 ESB publish data to the WSO2 ESB Analytics via thrift. By default thrift port is 7611 and corresponding ssl thrift port is 7711 (7611+100), check the data-bridge-config.xml file which is in analytics server config directory .  Since we are shipping analytics products with offset 1 then thrift ports are 7612 and ssl port is 7712. Here, ssl port (7712) is used for initial authentication purposes of data publisher ...
Post a Comment
Read more