New or updated for this feature pack


wsdbgen command

The command allows users to utilize the pureQuery feature in Java™ Persistence API (JPA) applications.

New or updated for this feature pack The Feature Pack for OSGi Applications and JPA 2.0 introduces support for Apache OpenJPA 2.0.

This command has been renamed wsdbgen for the Feature Pack for OSGi Applications and JPA 2.0 and later releases. The command is used in the same way as the wsdb2gen command. The command, wsdb2gen, which implies for DB2® only, works only for DB2 database in WebSphere® Application Server Version 7.0. In the Feature Pack, this command can be used for DB2, Informix® and Oracle databases. Because of that, a synonym, wsdbgen command, is introduced.

Run the JPA commands (.bat on Windows® or .sh on UNIX®) from the <profile_home>/bin directory, rather than from the <app_server_root>/bin directory to make sure you have the latest version of the commands for your release level.

Syntax

The command syntax is as follows:

[AIX] [HP-UX] [Linux] [Solaris] [z/OS]
wsdbgen.sh [parameters]
[Windows]
wsdbgen.bat [parameters]

Before running the command, your persistence.xml file must be in the META-INF directory and the META-INF directory must be in the class path.

Parameters

  • -help : This parameter displays the help information.
  • -pu : The name of the persistence unit defined in persistence.xml file.
  • -collection : The collection-id which is assigned to package names. The default is NULLID.
  • -url : The URL of the target database. This is used to validate the generated SQL. A URL must be specified either in the persistence.xml file or as a command option. If both are specified, the URL that is specified in the command option is used.
  • -user : The user ID
  • -pw : The corresponding password to connect to target database. If this parameter is not specified, the value found in the persistence.xml file is used.
  • -package : If this parameter is specified, the -package parameter takes the string value package name and a single database package with the specified name is generated. If the -package parameter is not specified, then one package is generated for each entity class. The entity name is used as package name if the -package option is not specified. The name length limit is the database limit -1, for example: 128 - 1 = 127.

Usage

The persistence.xml file must be included in the application Java archive (JAR) file and is also used as input in the DB2 bind to create the DB2 package. The command requires a connection to a database in order to validate generated SQL. The database does not have to be the same as the run time database, but it should be at the same version and release level.

Ensure the following JAR files are on the class path:
  • pdq.jar
  • pdqmgmt.jar
  • db2jcc.jar
  • db2jcc_licence_cu.jar.
If the database URL specifies a DB2 for zOS database, then the following JAR file must also be on the class path: db2jcc_licence_cisuz.jar
Attention: Read more about the DB2 JAR level compliance for pureQuery at the IBM® Support Website: System requirements for IBM Optim™ pureQuery Runtime for Linux®, UNIX, and Windows.
Attention: You can review information about pureQuery StaticBinder in the Data Studio Information Center by reading the topic, "The pureQuery StaticBinder utility."

Examples

DB2

[AIX] [HP-UX] [Linux] [Solaris] [z/OS]
wsdbgen.sh  -pu payroll -collection prod1 -url jdbc:db2://myhostname:50000/proddb  -user produser -pw secret 
[Windows]
wsdbgen.bat  -pu payroll -collection prod1 -url jdbc:db2:\\myhostname:50000\proddb  -user produser -pw secret 

Informix

[AIX] [HP-UX] [Linux] [Solaris] [z/OS]
wsdbgen.sh  -pu payroll -collection prod1 -url jdbc:ids://myhostname:9089/proddb  -user produser -pw secret 
[Windows]
wsdbgen.bat  -pu payroll -collection prod1 -url jdbc:ids:\\myhostname:9089\proddb  -user produser -pw secret 



Subtopics
New or updated for this feature pack Developing JPA 2.x applications for a Java EE environment
New or updated for this feature pack Developing JPA 2.x applications for a Java SE environment
Related tasks
Configuring JDBC providers to use pureQuery to access DB2
Configuring data source JDBC providers to use pureQuery in a Java SE environment
Related information
System requirements for IBM Optim pureQuery Runtime for Linux, UNIX, and Windows
The pureQuery StaticBinder utility
Reference topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 3:02:28 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700osgijpa&product=was-nd-mp&topic=rejb_wsdbgen
File name: rejb_wsdbgen.html