Code Generator Package Characteristics

Specify the following characteristics of the package:

Schema Name: Specify the name of the target schema. This selection appears only if you are generating a package in offline mode. To create a package in offline mode in JDeveloper, select New; in the Categories list of the New Gallery, expand Database Tier, and select Offline Database Objects. Data Mining PL/SQL Package is one of the items.
Note: If you are not creating a package in offline mode, you are operating in the context of an already-opened connection. This schema is used.
Package Name: The wizard generates a default name; you can change this name.
Package Comment: Optional comments describing the package.
Each activity in the package is listed in a grid. Each activity has a type (Build, Apply, or Test), a procedure name, and, for apply activities, result set support. To edit this data, select an activity, and click Edit. The default for apply activities is to include result set support. If you accept this default, you must manage the lifetime of the generated result sets, which are TYPE objects. For example, delete objects when the function is deleted. For more information about result set support, see Result Set Apply Functions.
Package execution: The default is Definer rights; to select Invoker rights, click the radio button. For information about this selection, see Invoker's Rights and Definer's Rights.
Drop existing objects: The default is to not drop existing objects. To drop existing objects, click the check box. The default names for output objects are those defined by the activity. If you do not either have new output names or change this setting to drop objects, you will get duplicate objects. When the procedure executes, if the output already exists and drop existing objects was not specified, the procedure will raise an exception to the caller and exit. However, if you drop activity objects, you might end up with broken activities.
Workflow API support: The default is to not include support for the Oracle Workflow application programming interface. To generate code that supports the Oracle Workflow API, click the check box. If you click the check box, you must install Oracle Workflow. Also, the generated procedures and the data sources used must be both executable and readable by the workflow engine; otherwise, the generated code will not compile. Detailed information about Oracle Workflow is on the Information Integration tab in the Oracle Database Documentation Library 10g Release 2 (10.2).
Note: Oracle Workflow is not shipping with Oracle Database 11g Release 1 (11.1).

Click Next to continue.