Databases
StackOverflow2013
Postsdbo
POWSO2: Greg and ESB with shared registry issue
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWSO2: Greg and ESB with shared registry issue
    primarykey
    data
    text
    <p>I follow the guide <em>Governance Partition in a Remote Registry</em> found in WSO2 Documentaton. It seems to work fine but I am facing a strange problem. Let me explain my setup first.</p> <p><strong>Governance registry instalation</strong></p> <ul> <li>Installed GREG 4.5.3</li> <li>Set the offset to 1 in order to GREG console mgmt runs on port 9444 (carbon.xml)</li> <li>Create mysql database "wso2greg_reg" (for local/config/governance registry)</li> <li>Updated datasource WSO2_CARBON_DB to point to wso2greg_reg database (master-datasources.xml)</li> <li>Enabled clustering (axis2.xml)</li> <li>Run GREG server with -Dsetup option in order to create all tables</li> </ul> <p><strong>Enterprise Service Bus instalation</strong></p> <ul> <li>Installed ESB 4.6.0</li> <li>Set the offset to 2 in order to ESB console mgmt runs on port 9445 (carbon.xml)</li> <li>Create mysql database "wso2esb_reg" (for local/config registry)</li> <li>Updated datasource WSO2_CARBON_DB to point to wso2esb_reg database (master-datasources.xml)</li> <li>Added datasource WSO2_GREG_DB to point to wso2greg_reg database (master-datasources.xml)</li> <li>Enabled clustering (axis2.xml)</li> <li>Set registry.xml to mount governance registry using wso2greg_reg database</li> <li>Run ESB server with -Dsetup option in order to create all tables</li> </ul> <p>My problem is happening when I start the two servers, dependening on which was the first server started I have diferent problems on the console managmenet of the secondly started server.</p> <p><strong>First case:</strong></p> <p>I start GREG first and ESB in second. When navigating to ESB Console MGMT, I am unable to add a new Pass Through Proxy, the respetive form is not showing and exceptions are logged to the ESB logs (see <a href="http://pastebin.com/KCA5X37w" rel="nofollow">logs</a>).</p> <p><strong>Second case:</strong></p> <p>I start ESB first and GREG in second. When navigating to GREG Console MGMT, the metadata menu is empty and exceptions are loged to the GREG logs (see <a href="http://pastebin.com/3pR4DYDW" rel="nofollow">logs</a>)</p> <p>Can someone point me to what I am doing wrong?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMichael
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWSO2: Greg and ESB with shared registry issue
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWSO2: Greg and ESB with shared registry issue
      1. USChris Snow
      1. VTFavorite
    1. COCan you post a link to the documentation you have been following?
      singulars
      1. POWSO2: Greg and ESB with shared registry issue
      1. USChris Snow
    2. COhttp://docs.wso2.org/wiki/display/AS510/Governance+Partition+in+a+Remote+Registry
      singulars
      1. POWSO2: Greg and ESB with shared registry issue
      1. USMichael
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload