The WebLogic Server EJB container allows you to automatically generated primary keys using the native automatic key generation facilities provided by Oracle or SQLServer databases. If you are not using one of those databases, you can enable key generation through a user-designated key table. If you specified automatic key generation in the EJB's weblogic-cmp-rdbms-jar.xml file, you can modify this configuration in the Administration Console.
Automatic primary key generation in the Programming WebLogic Enterprise JavaBeans Guide
Attributes
Attribute Label
Description
Value Constraints
Generator Type
Specifies the method by which the container generates keys. Valid values are as follows: 'ORACLE' - use Oracle's SEQUENCE 'SQL_SERVER' - use SQL SERVER's IDENTITY column 'NAMED_SEQUENCE_TABLE' - use USER designated SEQUENCE TABLE User specifies the name of a DBMS Table with the schema (sequence INT) which will be used to hold sequence values
Attribute: GeneratorType
Valid values:
"ORACLE"
"SQL_SERVER"
"NAMED_SEQUENCE_TABLE"
Readable: yes
Writable: yes
Generator Name
If GeneratorType specifies a type of database, then you can use this value to specify the name of the generator. For example, if <generator-type> is ORACLE, then <generator-name> is the name of the ORACLE SEQUENCE to use. The SEQUENCE is assumed to already exist in the database. If <generator-type>is NAMED_SEQUENCE_TABLE, then this value specifies the name of the SEQUENCE TABLE to use. The NAMED_SEQUENCE_TABLE is assumed to already exist in the database with 1 row.
Attribute: GeneratorName
Configurable: yes
Readable: yes
Writable: yes
Key Cache Size
Optional size of key cache. If <generator-type>is ORACLE, this value must match the Oracle SEQUENCE INCREMENT value. If <generator-type> is NAMED_SEQUENCE_TABLE, this value specifies the number of keys that the container will fetch in a single DBMS call. If <generator-type>is SQL_SERVER, this value is ignored.