You can access the Meta Catalog Preferences by choosing
and then selecting .The Meta Catalog preferences consist of the following pages:
Meta Catalog browse | Lists all catalogs currently defined in the current workspace.
Shows each catalog's name, its update mode, whether it is a local or
master catalog, and whether it is configured to start
automatically. Note: A master catalog always shows "false" in the
Auto start column, because it does not start when you open your
workspace. If the administrator has not started a database
server for it, you cannot access it.
|
New | Launches the Create Meta Catalog wizard that steps you through
creating a new local catalog to your workspace. Note: Each catalog
must have a unique name.
|
Add Master | Launches the Add Meta Catalog wizard that steps you through
adding connection information for a master catalog to your
workspace. Note: You cannot define a master catalog with the same
name as a local catalog.
|
Remove | Removes a catalog definition from your workspace. If you choose a local catalog, you can choose to also remove the physical database files. If you choose a master catalog, you can only remove the definition. |
Import | Imports a set of catalog and content builder definitions into
your workspace. Any current definitions are discarded, even if there
is no matching entry in the imported definitions. If a matching
database is not found for an imported local catalog definition, you
are given the option to rebuild the missing databases. Note: All the
designated content builders run to recreate the content from the
source code. This can take some time depending on the number of
catalogs being built and the number of resources from which data
is extracted.
|
Export All | Exports the current set of catalog and content builder definitions to an XML file. By default, the definitions are stored in the catalog.xml file. |
Rebuild | Rebuilds the selected
catalog. This option is disabled for master catalogs. Note: This
process deletes the physical database. All the designated
content builders run to recreate the content from the source
code. This can take some time if there are a lot of resources to
extract data from.
|
Main page | Catalog Name combo-box | The catalog definition to view or edit. The label to the right of the combo box indicates whether it is a local or master catalog. |
Update for open projects only toggle box | If selected, when a rebuild is launched for this catalog, only the resources in open projects are run through the content builders. | |
Update catalog radio set | Method for updating a
local catalog's content, as follows:
|
|
Restore Defaults | Loads the last catalog definition that was saved. | |
Apply | Saves any edits for the selected catalog to the internal version of the catalog.xml file in Progress Developer Studio for OpenEdge. | |
Database information | Local database toggle box | When selected, this indicates that the physical catalog database is on the local machine, rather than a remote machine. By default, local catalogs are assumed to be on the local machine. |
Meta Catalog database path | The full path of the physical catalog database, including the filename. | |
Service/Port for server (-S) | The connection port or service name for the catalog's database server. | |
Additional server parameters | Any necessary startup
parameters for the database.
|
|
Automatically start/stop server toggle box | Whether the catalog's server should automatically start or stop when you enter or leave this workspace. | |
Connection information | Host | Name of the host where the catalog is. |
Service/Port | The connection port or service for the catalog's database server. | |
Database | The logical name of the database. | |
User | The user name to use
connecting to the database. Note: Because the catalog database is
created with SQL, for local catalogs, you need to connect as a
user with proper access to update the database.
|
|
Password | The password to use connecting to the database. | |
Mapping of root path | Root path | The root path for a resource as it was originally read into the catalog. If you have resources on different paths loaded into the same catalog, each root path displays on a separate line of the browse. |
Local path | The path to your local copies of the resources in a master catalog. | |
Edit | Launches a dialog box where you can map a root path to a local path. When there is a mismatch between your local path and a master catalog's root path for the same resource, setting this mapping between the paths produces the appropriate search results. | |
Content Builders | Code | Lists the codes for content builders that are defined in this workspace. Checking the toggle box beside a code indicates that the content builder supplies data to this catalog. |
Description | The description of the content builder. | |
Projects | Project name | Lists the names of all projects in this workspace. Checking the toggle box beside a project indicates that data from that project's resources should be added to this catalog whenever an appropriate content builder runs. |
Code | The content builder's code. |
Description | The description of the content builder. |
Class | The Java class for the content builder. |
Extensions | The file extensions against which the content builder should run. |
New... | Launches a dialog for entering a new content builder definition. |
Edit... | Launches a dialog for editing a content builder definition. For example, you might add a custom file extension to the existing extensions. |
Remove | Removes a content definition from this workspace. This does not delete the content builder class file. |
Restore Defaults | Deletes the current definitions and replaces them with the default definitions of the predefined content builders that ship with Progress Developer Studio for OpenEdge. |
Apply | Saves any edits for the selected content builder to internal version of the catalog.xml file in Progress Developer Studio for OpenEdge. |