Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.) Date of First Response: 2009-03-20 11:14:45 project_key: SOA The following statement is from the 4.2 Registry Guide and also appears in the 4.3 Services guide in the corresponding section "For jUDDI we have two requirements that need to be fulfilled: 1. access to the jUDDI database. You will need to create a schema in your database, and add the jbossesb publisher. The product/install/jUDDI-registry directory contains database creation scripts for you favorite database." 'create a schema in your database, and add the jbossesb publisher' doesn't mean much to me, can you define these steps more concrete terms 'product/install/jUDDI-registry' doesn't exist in the SOA product. What is the SOA directory that it is referring to? In regard to the database creation scripts referred to, the following two comments have been made: "jbossesb.sar/juddi-sql doesn't contain database creation scripts, it has import scripts. jboss-as/server/production/deploy/jbossesb.sar/lib/juddi-2.0rc5.aop.jar seems to have creation scripts. Are users expected to unpack the jar to get at the files? " "You are right the user must use files from both JAR file (unpack it) and fro the directory. Moreover please look at the SQL files. Table nasmes are prefixed with ${prefix} string. So if the files are used manually this sting must be either removed or replaced with value of paramter juddi.tablePrefix fro esb.juddi.xml file" What steps are users expected to do here exactly?
The original section on jUDDI configuration is as below: " You have two requirements when using jUDDI: 1. You need access to the jUDDI database. You will need to create a schema in your database, and add the jbossesb publisher. The jUDDI-registry directory contains database creation scripts for several common database systems. 2. The configuration of jUDDI is done in esb.juddi.xml. If you do not use a datasource you need to take special care to set the following properties: <entry key="juddi.isUseDataSource">false</entry> <entry key="juddi.jdbcDriver">com.mysql.jdbc.Driver</entry> <entry key="juddi.jdbcUrl">jdbc:mysql://localhost/juddi</entry> <entry key="juddi.jdbcUsername">juddi</entry> <entry key="juddi.jdbcPassword">juddi</entry> If you do use a datasource you need something like: <entry key="juddi.isUseDataSource">true</entry> <entry key="juddi.dataSource">java:comp/env/jdbc/juddiDB</entry> The database can be automatically created if the specified user has enough rights to create tables. You must also ensure that the isCreateDatabase flag is set to true, and that the sqlFiles parameter settings indicates the database that you are using. The jUDDI creation scripts are located in the juddi.jar. <!-- <entry key="juddi.tablePrefix">JUDDI_</entry> --> <entry key="juddi.isCreateDatabase">true</entry> <entry key="juddi.databaseExistsSq">select * from ${prefix}BUSINESS_ENTITY </entry> <entry key="juddi.sqlFiles"> juddi-sql/mysql/create_database.sql,juddi sql/mysql/ insert_publishers.sql </entry> jUDDI supports the following databases: • Daffodildb • DB2 Using Scout and jUDDI 9 • Derby • Firebird • HSQLDB • informix • jdatastore • mysql • oracle • postgresql • Sybase (can be used for Microsoft SQLServer) • totalxml " As SOA-P already ships an ant tool to automatically configure databases, we do not need to let users know trivial details on how to configure db manually. Thus the whole section above should read as below: " JBOSS SOA-P Platform provides an Ant script to configure JBOSS SOA-P Platform to work with various databases. To run this tool, please go to <jboss-soa-p-installation-dir>\jboss-as\tools\schema directory. Using either UNIX or Windows: ant Then input configuration parameters according to the prompt. "
I have added the schema-tool content from the 4.3 admin guide to the 4.2 admin guide and replaced the content here in the registry guide to refer to it.
Link: Added: This issue is a dependency of SOA-1345
Link: Removed: This issue is a dependency of SOA-1345
Link: Added: This issue related SOA-1345
Link: Added: This issue is related to SOA-1346
Verified fixed in section: 2.5. Using Scout and jUDDI of the Registry Guide in 4.2 CP04 CR4