Generating PL/SQL library modules for Oracle Forms and Oracle Reports applications

Introducing Library Generator

PL/SQL library module generation

Design capture of existing PL/SQL library modules

Library Generator dialog boxes


Introducing Library Generator

Related Topics

About Library Generator

Features added for Library Generator in 6i

Features added to Library Generator in previous releases


About Library Generator

Related Topics

About Library Generator

Library Generator is part of Oracle Designer - Oracle’s application modeling, design and generation toolset. Using Library Generator, you can:

•	generate PL/SQL library modules from module definitions recorded in the repository

•	capture existing PL/SQL library modules into the repository

When generating PL/SQL library modules, you can run Library Generator in one of two ways:

•	to generate specific PL/SQL library modules, you can run Library Generator standalone

•	when using Form Generator or Report Generator to generate an Oracle Forms or Oracle Reports module, you can run Library Generator automatically to generate any attached PL/SQL library modules

A generated PL/SQL library module can be used by both Oracle Forms and Oracle Reports modules, unless the generated PL/SQL library includes calls to language-specific built-ins. If the generated PL/SQL library does include calls to such built-ins, Library Generator uses the appropriate compiler (i.e. either the Oracle Forms or the Oracle Reports compiler) to compile the PL/SQL library.

Note that it is the repository module's Language property that Library Generator uses to determine which compiler to use. It is your responsibility to ensure that:

•	the repository module's Language property is appropriate for the built-ins called in the module

•	built-ins from different languages are not called by the same PL/SQL library module

•	the appropriate compiler is available (for generating and capturing repository modules of Language Oracle Common Library, both the Oracle Forms and the Oracle Reports compilers are suitable)


Features added for Library Generator in 6i

Related Topics

New features in Library Generator 6i

Support for generation from versioned repositories.

New repository features enable you to use the repository as well as the filesystem to store generated files after generation. Storing files in the repository gives you access to features such as the Dependency Analyzer and version control.

Other new and improved Library Generator features in 6i

New colors for those messages displayed in the Message Window that indicate whether Library Generator has successfully or unsuccessfully updated repository properties during generation and design capture.

As part of the support for generation from versioned repositories, Library Generator no longer maintains a module's Status property.


Features added to Library Generator in previous releases

Related Topics

Features added to Library Generator in Oracle Designer Release 6.0?

Features added to Library Generator in Oracle Designer Release 2.1.2?

Features added to Library Generator in Designer/2000 Release 2.1.1?

Features added to Library Generator in Designer/2000 Release 2.1?


Features added to Library Generator in Oracle Designer Release 6.0

Related Topics

Major new features in Oracle Designer Library Generator Release 6.0

No new features were added to Library Generator in Oracle Designer Release 6.0.


Features added to Library Generator in Oracle Designer Release 2.1.2

Related Topics

New features in Oracle Designer Library Generator Release 2.1.2

Generation and design capture of multiple modules is now supported by the Design Editor's new batch processing tools.


Features added to Library Generator in Designer/2000 Release 2.1.1

Related Topics

No new features were added to Library Generator in Designer/2000 Release 2.1.1.


Features added to Library Generator in Designer/2000 Release 2.1

Related Topics

Features of the new Library Generator

Generation of PL/SQL library modules from repository library module definitions (either as a separate operation or during generation of a module to which it is attached)

Design capture of existing PL/SQL library modules into the repository


PL/SQL library module generation

Related Topics

About PL/SQL library modules

About Oracle Designer library modules

Defining library modules in the repository

Attaching PL/SQL library modules to generated Oracle Forms/Reports modules.

Generating PL/SQL library modules

Generated PL/SQL library properties

Repository module properties used by library generator


About PL/SQL library modules

Related Topics

About PL/SQL library modules

A PL/SQL library module is a collection of subprograms, including user-named procedures, functions, and packages.

PL/SQL libraries provide a convenient means of storing client-side program units and sharing them among multiple applications.

Once you create a PL/SQL library, you can attach it to any other form, menu, report, or library module. Then, you can call library program units from triggers and user-named routines you write in the modules to which you have attached the library.

The same PL/SQL library can be attached to multiple modules. Conversely, a single module can have more than one attached PL/SQL library.

PL/SQL libraries can also be attached to other libraries. When a PL/SQL library attaches another library, program units in the first library can reference program units in the attached library.

About library file formats

There are three different library file formats:

File suffix	Notes
.PLL	Contains uncompiled source code, and may also contain compiled platform-specific executable code The .PLL file is created or updated when you save a library module. In addition, when you save a library module, the changes are reflected in each module to which the library is attached.
.PLX	Contains platform-specific executable code but no source code. When you are ready to deploy your application, you will probably want to generate a version of your library that contains only the compiled code, without any source.  You can generate a .PLX file from the appropriate Builder tool (i.e. either Form Builder or Report Builder) or from the command line.
.PLD	A text format file. The .PLD file can be used to source-control library files.

When you attach a library to a module, you attach the .PLL version of the library. At runtime, the application looks for a .PLX file by that name in search paths specified by Registry variables. If no .PLX file is present, the application looks for the .PLL file by that name.


About Oracle Designer library modules

Related Topics

An Oracle Designer library module is a definition of a module containing code that can be used by other repository modules linked to it. The module definition includes either the code in the library (for repository-based library modules) or the file containing the code (for file-based library modules)

Links between a library module and other modules (including other library modules) are recorded as a module network.

There are two types of Oracle Designer library module, distinguished by the location of their code:

Type of Oracle Designer library module	Location of code
repository-based library module	Code is stored in the repository as application logic named routines. Because the code is stored in the repository, it is easy to modify and generate new library modules.
file-based library module	Code is stored in a PL/SQL library module file (with the suffix .pll or .plx) specified by the repository module's Source Path property.  Because a file-based library module is simply a reference to an existing file, it cannot be generated. The repository module definition exists simply to enable you to attach it to other module definitions.

For more information, refer to Defining library modules in the repository.

About generating Oracle Designer library modules

You can generate PL/SQL library modules from repository-based library module definitions using Library Generator.

Library Generator can create PL/SQL library module files in the formats and for the Oracle tools shown below:

File suffix	Notes	Oracle Forms	Oracle Reports
.PLL	Contains uncompiled source code, and may also contain compiled platform-specific executable code.	Yes	Yes
.PLX	Contains platform-specific executable code but no source code.	Yes	Yes
.PLD	A text format file.	Yes	Yes

You can optionally use Library Generator to generate any library modules attached to the library module currently being generated. When generating attached libraries, note that Library Generator does not generate library modules attached to file-based library modules.

As well as storing generated PL/SQL library files in the filesystem, you can also store generated files in the repository after generation. Storing files in the repository gives you access to features such as the Dependency Analyzer and version control. For more information, refer to About storing generated files in the repository after generation.

About attaching Oracle Designer library modules

To specify that a generated PL/SQL library module is to be attached to another generated Oracle Forms or Oracle Reports module, link the two repository module definitions in a repository module network. For more information, refer to Attaching PL/SQL library modules to generated Oracle Forms/Reports modules.


Defining library modules in the repository

Related Topics

To define a library module in the repository:

1.	Create a new repository module definition of type Library.  How?

2.	Use the table below to determine how to set the module's Language property: .

If code in the library module:	then set the module's Language property to:
is to contain calls to Form Builder built-ins	Oracle Forms
is to contain calls to Report Builder built-ins	Oracle Reports
is to contain no calls to Form Builder or Report Builder built-ins	Oracle Common Library

3.	If the library module is to be file-based (i.e. the code for the repository library module is to be held in a file with a .pll or .plx suffix)

•	set the repository library module's Source Path property to the name of the file (to ensure generated applications are portable between systems, we strongly recommend you specify only the name of the library module file in the Source Path property and use Registry variables to specify the path to locate the file at runtime)

•	set the appropriate Registry variable to indicate the location of the library file, using the table below:

Language of repository library module:	Location of PL/SQL library file referenced by Source Path property is specified by these Registry variables:
Oracle Forms	FORMS60_PATH, ORACLE_PATH
Oracle Reports	REPORTS60_PATH, ORACLE_PATH
Oracle Common Library	ORACLE_PATH

4.	If the library module is to be repository-based (i.e. the code for the repository library module is to be held as application logic in the repository itself), use the Module Logic Editor to enter the code.

For more information about the Logic Editor, refer to Creating, editing, and checking logic in the Design Editor help system.


Attaching PL/SQL library modules to generated Oracle Forms/Reports modules

Related Topics

About attaching PL/SQL library modules

When you want a generated Oracle Forms or Oracle Reports module to call code from a PL/SQL library module, you must link the modules in one of the following ways:

•	by linking repository module definitions in a repository module network

•	by attaching the PL/SQL library module to a template form or report

•	using the Form Generator MODLIB preference or the Report Generator MODLIB preference

The Registry variables that Oracle Forms and Oracle Reports uses to locate an attached PL/SQL library module at runtime depend on the Language property of the repository module definition.

Language of repository library module:	Oracle Forms/Reports searches for PL/SQL library in path specified in these Registry variables:
Oracle Forms	FORMS60_PATH, ORACLE_PATH
Oracle Reports	REPORTS60_PATH, ORACLE_PATH
Oracle Common Library	ORACLE_PATH

Before attempting to run a generated Oracle Forms or Oracle Reports module that has an attached PL/SQL library, add the PL/SQL library path to the appropriate Registry variable.

To attach a library module to another module using a module network:

1.	Define the library module in the repository.  How?

2.	Link the library module to one or more modules in a module network.  How?

If the library module is repository-based (i.e. the code for the library module is held as application logic in the repository), during generation of the module to which the library module is attached:

•	the link between the library module and the module being generated is recorded as a library attachment

•	(optionally) the attached library module is generated as well

If the library module is file-based (i.e  the code for the library module is not held in the repository), the relationship between the library module and the generated module is recorded as a library attachment for the generated module.

To attach a library module to a generated module using a template:

1.	In the appropriate Builder tool (i.e. Form Builder or Report Builder), create a library module.

2.	In the appropriate Builder tool, attach the library module to the template form or report.

When you generate a module that uses this template, the library attached to the template is attached to the generated module.

To attach a library module to a generated form or report using MODLIB:

•	Set the Form Generator MODLIB preference or the Report Generator MODLIB preference to the name of the PL/SQL library to attach to the generated form or report.


Generating PL/SQL library modules

Related Topics

Note that file-based library modules will not be generated.

To generate a repository-based library module during generation of a module to which it is attached:

1.	Select the repository form, menu, report, or library module that you want to generate as an Oracle Forms or Oracle Reports module.

2.	Select Generate→Generate Module to display the appropriate Generate dialog box.

For more information about the settings on the dialog box, refer to:

•	Generate Form dialog box

•	Generate Report dialog box

•	Generate Library dialog box

3.	Check the Generate Attached Libraries check box.

If there are repository-based library modules attached to the module being generated, during the generation of that module Library Generator will be invoked to generate PL/SQL library modules from the attached library modules (and from any library modules attached to the attached library modules).

Note that the attached library will only be generated if its Language property is set to one of the following:

•	the same as the Language property of the module being generated

•	Oracle Common Library

4.	Display the appropriate Generator Options dialog box by selecting the Options button and set generation options as necessary.

5.	Click on the Start button to generate the Oracle Forms or Oracle Reports module and its attached library module.

6.	(optional) When generation is complete, you can use the Build Actions dialog to:

•	view the generated PL/SQL library module using Form Builder or Report Builder

•	compile the generated PL/SQL library module using Form Builder or Report Builder

•	view any messages output during library generation (Library Generator messages are saved in a text file with the name <generated_library_name>.log)

For more information, refer to Displaying the Build Actions dialog box in the Design Editor help system.

7.	Before attempting to run a generated Oracle Forms or Oracle Reports module that has an attached PL/SQL library, add the library path to the appropriate Registry variable.

For more information about the Registry variables to use, refer to Attaching PL/SQL library modules to generated Oracle Forms/Reports modules.

Batch generation of multiple modules

You can generate multiple modules of the same and different languages using the Design Editor's batch processing tools.

To generate a repository-based library module as a separate operation (i.e. not during the generation of another module to which it is attached):

1.	Select the repository-based library module that you want to generate.

2.	Select Generate→Generate Module to display the Generate Library dialog box.

For more information about the settings on this dialog box, refer to Generate Library dialog box.

3.	(Optional)  To generate other library modules attached to the library module you select, check the Generate Attached Libraries check box.

Note that an attached library will only be generated if its Language property is set to one of the following:

•	the same as the Language property of the module being generated

•	Oracle Common Library

4.	Display the Library Generator Options dialog box by selecting the Options button on the Generate Library dialog box and set generation options as necessary.

For more information about the available options, refer to Library Generator options dialog box.

5.	Click on the Start button to generate the PL/SQL library module.

6.	(optional) When generation is complete, you can use the Build Actions dialog to:

•	view the generated PL/SQL library module using Form Builder or Report Builder

•	view any messages output during library generation (Library Generator messages are saved in a text file with the name <generated_library_name>.log)

For more information, refer to Displaying the Build Actions dialog box in the Design Editor help system.

7.	Before attempting to run a generated Oracle Forms or Oracle Reports module that is attached to the PL/SQL library you have just generated, add the library path to the appropriate Registry variable.

For more information about the Registry variables to use, refer to Attaching PL/SQL library modules to generated Oracle Forms/Reports modules.

Batch generation of multiple modules

You can generate multiple modules of the same and different languages using the Design Editor's batch processing tools.


Repository module properties used by Library Generator

Related Topics

Module Property	Use to specify to Library Generator	Notes and Related Topics
Short Name	Determines the name of the PL/SQL library module, the .pld, .pll, and .plx files, (if the Implementation Name property is set, this property is not used on generation).
Name	Not used by Library Generator.
Language	The environment in which the PL/SQL Library is used.	Set to one of the following languages: • Oracle Forms • Oracle Reports • Oracle Common LIbrary For more information, refer to Defining library modules in the repository
Purpose	Not used by Library Generator.
Implementation Name	If set, overrides the Short Name property (on generation only) and determines the name of the generated library module.
Module Type	Verifies that the module has been specified for implementation as a PL/SQL library.	Should be set to Library.
Display
Top Title	Not used by Library Generator.
Bottom Title	Not used by Library Generator.
Short Title	Not used by Library Generator.
Layout Format	Not used by Library Generator.
Planning
Status	Not used by Library Generator.
Candidate	Not used by Library Generator.
Prevent Generation?	Not used by Library Generator.
Size	Not used by Library Generator.
Complexity	Not used by Library Generator.
Project	Not used by Library Generator.
Activity	Not used by Library Generator.
Task	Not used by Library Generator.
Time Estimate	Not used by Library Generator.
Estimate Units	Not used by Library Generator.
Invocation
Top Level?	Not used by Library Generator.
Command Line	Not used by Library Generator.
Return Type	Not used by Library Generator.
Runtime Path	Not used by Library Generator.
Source
Source Path	Determines whether the library module is file or repository based.	If set to the filename of .pll or .plx then the library is file based (code for the repository library module will be held in the specified file). If not set to a filename of .pll or .plx then the library is repository based (code for the repository library module will be held as application logic in the repository).
Help
User/Help Text	Not used by Library Generator.
Help File Name	Not used by Library Generator.
Help Graphic File Name	Not used by Library Generator.
Help Context Id Prefix	Not used by Library Generator.
Documentation
Release Notes	Not used by Library Generator.
Description	Not used by Library Generator.
Notes	Not used by Library Generator.


Generated PL/SQL library properties

Related Topics

PL/SQL Library Property	Derived from or set to:	Notes and Related Topics
Name	Repository module's Implementation Name (if set) or Short Name property


Design capture of existing PL/SQLlibrary modules

Related Topics

About capturing PL/SQL library modules

Capturing PL/SQL library modules


About capturing PL/SQL library modules

Related Topics

About capturing PL/SQL library modules

Using Library Generator you can capture PL/SQL library modules into the repository.

You can specify:

•	whether the PL/SQL library module is captured as a new repository module or merged with an existing repository module

•	whether the captured library module is repository-based or file-based (i.e. whether the code in the library module is stored in the repository or in a file specified by the captured module's Source Path property)

•	whether to capture PL/SQL libraries attached to the PL/SQL library being captured

Note that how you capture a PL/SQL library module (either as a new module or merged with an existing module) will determine how the repository module's Language property is set, as shown in the table below:

PL/SQL Library module captured:	Language property set to:	Notes
as a new repository module	OracleCommon Library	If the captured module contains calls to language specific (i.e. Oracle Forms or Oracle Reports) built-ins, modify the captured module's Language property accordingly. For any attached PL/SQL libraries that are also captured but which do not already exist in the repository, the Language property is also set to Oracle Common Library.
and merged with an existing repository library module definition	Language property of existing repository module definition	If the newly-merged module now contains calls to built-ins that are specific to a language other than that specified by the Language property, modify the newly-merged module's Language property accordingly. If attached PL/SQL library modules are captured: • if a definition of the attached library module already exists in the repository, its Language property is not changed • if a definition of the attached library module does not already exist in the repository, a new repository module definition is created and its Language property is set to the language of the newly captured parent library module
About capturing PL/SQL library modules attached to the PL/SQL library module being captured

As with Oracle Forms and Oracle Reports modules, PL/SQL library modules can have other PL/SQL library modules attached to them. When capturing PL/SQL library modules, you can capture any attached PL/SQL library modules as well. Library Generator captures an attached PL/SQL library as a module in a module network (creating new library modules where necessary) and enables you to specify whether the attached module is file-based or repository-based.

Note that Library Generator only captures a PL/SQL library module and its attached PL/SQL libraries into the repository if all the attached libraries are stored in the same directory, or in directories specified by the appropriate Registry variable.

PL/SQL Library module captured:	Registry variable used to locate attached PL/SQL libraries:
as a new repository module	ORACLE_PATH
and merged with an existing repository library module definition	FORMS60_PATH, ORACLE_PATH  (if Language property of existing repository module is Oracle Forms) REPORTS60_PATH, ORACLE_PATH (if Language property of existing repository module is Oracle Reports) ORACLE_PATH (if Language property of existing repository module is Oracle Common Library)


Capturing PL/SQL library modules

Related Topics

To capture the design of an existing PL/SQL library into a new repository module:

1.	Select Generate→Capture Design of→Library to display the Capture Library Design dialog box.

2.	Use the Destination module field as follows:

•	to capture a PL/SQL library into a new repository library module, you can specify a short name for the repository module that will be created by the design capture process in the Destination module field (if you do not specify a name, Library Generator creates a unique name based on the name of the PL/SQL library module)

•	to capture a PL/SQL library and merge it with an existing repository module, specify the name of the existing repository module in the Destination module field

3.	Specify the name of the PL/SQL library file you want to capture into the repository.

4.	If you want to capture the module as a repository-based module, check the Capture Code checkbox.

If you do not check the Capture Code checkbox, Library Generator captures the PL/SQL library as a file-based library module and sets the captured repository module's Source Path property to the name of the PL/SQL library file.

5.	If you want to capture PL/SQL library modules attached to the PL/SQL library module you have selected for capture, check the Capture Attached Libraries checkbox and specify whether to capture code from the attached libraries into the repository as follows:

•	select the Capture Links Only radio button to capture attached PL/SQL libraries as file-based library modules in a module network

•	select the Capture Links and Code radio button to capture attached PL/SQL libraries as repository-based modules in a module network (where repository module definitions already exist, specify whether existing application logic is to be updated using the Update Existing Modules checkbox)

6.	Use the Additional Containers field to specify the location of objects (e.g. attached libraries, languages) that are referenced by the library being captured but which are not in the target container.

7.	Use the Post Capture options to specify whether to save changes to the repository during design capture:

•	Commit - update repository objects

•	Browse/Edit - show proposed repository changes, enabling you to choose how to process them

Note that there are some circumstances when Library Generator will not update properties of repository objects. For more information, refer to When are repository objects not updated during generation and design capture.

8.	Click the Start button to begin the design capture process.

Batch design capture of multiple modules

You can capture multiple modules of the same and different languages using the Design Editor's batch processing tools.


Library Generator dialog boxes

Related Topics

Generate Library dialog box

Library Generator options dialog box

Capture Library Design dialog box


Generate Library dialog box

Related Topics

Use this dialog box to control the runtime behavior of Library Generator.

Module

Displays the Short Name of the module selected for generation.

Generate Option - Generate Attached Libraries checkbox

Check this checkbox to generate library modules attached to the library module specified in the Module field.

Post Generation

Use the Post Generation options to specify what happens when generation is complete.

Post Generation - Commit

Select this option to update repository objects when generation is complete.

Note that there are some circumstances when Library Generator will not update properties of repository objects. For more information, refer to When are repository objects not updated during generation and design capture.

Post Generation - Revert

Select this option if you do not want to update repository objects with the property settings used during generation.

Post Generation - Browse/Edit mode

Select this option to activate Post Processing Mode, which enables you to choose how to process proposed repository changes.

For more information about Post Processing Mode, refer to About the Design Editor Post Processing Mode.

Start button

Click this button to start library generation.

Options button

Click this button to display the Library Generator options dialog. For more information, refer to Library Generator options dialog box.


Library Generator Options dialog box

Related Topics

Use this dialog box to specify options for controlling the runtime behavior of Library Generator.

Generated Library - Destination of generated .PLL files

Specifies a location for the .PLL file generated from the repository library module definition.

If no location is specified, generated files are saved to the working directory of the program item or shortcut used to start Oracle Designer. The default location is <ORACLE_HOME>\BIN\.

Generated Library - Destination of generated .PLL files Browse button

To view and select from a valid list of destinations, select this button.

Generated Library - Generate .PLD checkbox

Check this checkbox to generate a .PLD file as well as a .PLL file during library generation.

Upload generated files to repository checkbox

To save generated files in the repository folder mapped to the directory specified in the Destination of generated .PLL files field, check this checkbox. If a repository folder is not mapped to the destination directory, files are not saved in the repository.

For more information about saving generated files in the repository, refer to About storing generated files in the repository after generation.

Generated Library - Destination of generated .PLD files

Specifies a location for the .PLD file generated from the repository library module definition.

If no location is specified, generated files are saved to the working directory of the program item or shortcut used to start Oracle Designer. The default location is <ORACLE_HOME>\BIN\.

To enable this field, check the Generate .PLD checkbox.

Generated Library - Destination of generated .PLD files Browse button

To view and select from a valid list of destinations, select this button.

Upload generated files to repository checkbox

To save generated files in the repository folder mapped to the directory specified in the Destination of generated .PLD files field, check this checkbox. If a repository folder is not mapped to the destination directory, files are not saved in the repository.

For more information about saving generated files in the repository, refer to About storing generated files in the repository after generation.

Compile Library radio buttons

Specifies whether Library Generator compiles a generated PL/SQL library module into a .PLX file.

•	No - Library Generator never compiles the generated PL/SQL library module at the end of the generation process. When generation is complete, a compilation option appears in the Build Action window for each generated library module. To compile a generated PL/SQL library, double click on the corresponding option.

•	Yes - Library Generator always compiles the generated PL/SQL library module at the end of the generation process.

Compile Library - .PLX destination

Specifies a location for the .PLX file generated from the repository library module definition.

Compile Library - .PLX Destination Browse button

To view and select from a valid list of destinations, select this button.

Connect String

Specifies the connect string for compiling the PL/SQL library module.

Note:	The full connect string, including username, password and database must be specified, and must of the form: <usr>/<passwd>@<database>.


Capture Library Design dialog box

Related Topics

Use this dialog box to control the runtime behavior of Library Generator during design capture.

Target container

Specifies the container into which to capture the PL/SQL library.

Destination module

To capture a PL/SQL library into a new repository library module, you can use this field to specify a short name for the repository module that will be created by the design capture process (if you do not specify a name, Library Generator creates a unique name based on the name of the PL/SQL library module).

To capture a library and merge it with an existing repository module, use this field to specify the name of the existing module.

File - Name

Specifies the name of the .PLD or .PLL file to be captured.

File - Browse button

To search for the library that you want to capture, click Browse.

File - Capture Code checkbox

Check this checkbox to capture code into the repository from the PL/SQL library specified in the Name field.

File - Capture Attached Libraries checkbox

Check this checkbox to capture PL/SQL libraries attached to the PL/SQL library specified in the Name field.

Attached libraries

Specifies whether to capture code from attached PL/SQL libraries into the repository as follows:

•	Capture links only radio button - Library Generator captures attached PL/SQL libraries as file-based library modules in a module network (i.e. a captured repository module's Source Path property is set to the name of the PL/SQL library file).

•	Capture links and code radio button - Library Generator captures attached PL/SQL libraries as repository-based modules in a module network (i.e. code from the PL/SQL library is stored in the repository as application logic for the captured module).

•	Update existing modules checkbox - If the Capture Links and Code checkbox is checked, use this checkbox to specify whether application logic in existing repository library modules is to be updated.

Library Generator identifies existing repository library modules to link to the library being captured and (optionally) to update, by searching for a module with the same name (i.e. unique Implementation Name, or Short Name if the module does not have an Implementation Name) as the name of the library attached to the module being captured. If one (and only one) existing repository module is located, that module is linked to the module being captured and (optionally) updated. If no such existing repository library module is located (or if more than one module is located), Library Generator creates a new file-based or repository-based library module and gives it a Short Name based on the name of the attached library module being captured.

Note that Library Generator only creates or updates attached library modules that are in the same target container as the library module being captured. Library Generator never updates attached library modules in additional containers.

Additional Containers

Use this field to specify additional containers in which to locate objects referenced by the library being captured. Use a comma to separate container names.

Library Generator captures the library into the specified target container. If the objects being captured refer to other objects (e.g. languages, attached libraries) that are not in the target container, Library Generator attempts to locate the referenced objects by searching the specified additional containers.

Note the following:

•	Library Generator does not update or create referenced objects in additional containers during design capture.

•	If Library Generator identifies an existing repository library module in an additional container as being attached to the library module being captured, Library Generator links the repository library module to the captured library module but does not update it.

•	Referenced objects must be visible in the current workarea.

•	Library Generator searches for referenced objects in the additional containers in the order in which you enter the containers in the field.

•	If referenced languages do not exist in either the target container or the additional containers, Library Generator is unable to capture the module.

•	If referenced attached libraries do not exist in either the target container or the additional containers, Library Generator captures the library but does not capture or create the attachment.

Additional Containers - Browse button

To search for the container containing referenced objects, click Browse.

Post Capture

Use the Post Capture options to specify what happens when design capture is complete.

Post Capture - Commit

Select this option to update repository objects when design capture is complete.

Note that there are some circumstances when Library Generator will not update properties of repository objects. For more information, refer to When are repository objects not updated during generation and design capture.

Post Capture - Browse/Edit mode

Select this option to activate Post Processing Mode, which enables you to choose how to process proposed repository changes.

For more information about Post Processing Mode, refer to About the Design Editor Post Processing Mode.