[ 
https://issues.apache.org/jira/browse/JUDDI-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750851#comment-13750851
 ] 

Kurt T Stam edited comment on JUDDI-594 at 8/27/13 1:25 AM:
------------------------------------------------------------

Seems to work ok. The instructions to run two juddi servers are:
1. copy juddiv3 to juddi
2. edit the juddiv3/META-INF/context.xml (and 
conf/Catalina/localhost/juddiv3.xml) to use the jdbc/JuddiV3DS datasource, and 
add v3 to the url: url="jdbc:derby:target/juddi-derby-test-db-v3;create=true"
3. edit the juddiv3/WEB-INF/classes/META-INF/persistence.xml to use 
<non-jta-data-source>java:comp/env/jdbc/JuddiV3DS and persistence-unit 
name="juddiV3Database"
4. edit the juddiv3/WEB-INF/classes/juddiv3.properties to have
<persistenceunit><name>juddiV3Database</name></persistenceunit>

That should be it.

--Kurt
                
      was (Author: kurtstam):
    Seems to work ok. The instructions to run two juddi servers are:
1. copy juddiv3 to juddi
2. edit the juddiv3/META-INF/context.xml (and 
conf/Catalina/localhost/juddiv3.xml) to use the jdbc/JuddiV3DS datasource
3. edit the juddiv3/WEB-INF/classes/META-INF/persistence.xml to use 
<non-jta-data-source>java:comp/env/jdbc/JuddiV3DS and persistence-unit 
name="juddiV3Database"
4. edit the juddiv3/WEB-INF/classes/juddiv3.properties to have
<persistenceunit><name>juddiV3Database</name></persistenceunit>

That should be it.

--Kurt
                  
> Reconfigure jUDDI so that multiple instances can be run from the same 
> container with different databases
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JUDDI-594
>                 URL: https://issues.apache.org/jira/browse/JUDDI-594
>             Project: jUDDI
>          Issue Type: Improvement
>            Reporter: Alex O'Ree
>            Assignee: Kurt T Stam
>             Fix For: 3.2
>
>
> Reconfigure jUDDI so that we can multiple instances from the same container 
> with different databases and thus different url endpoints. This is necessary 
> not only as a cool feature, but also for enabling some more advanced unit 
> test scenarios, such as custody transfer and replication

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to