This utility sets options for adding reference data from Excel workbooks to the catalog database.
Reference data to bulkload
Displays one or more Excel workbooks for loading into the catalog database. These workbooks contain the reference data.
The software bulk loads the files in the order they are listed in the Excel files box.
Lists additional Excel workbooks in the Excel files box.
If UAC is turned on, the software can also list Excel files from the virtual store path. Before initiating the bulkload process, you must make sure that all the selected files are available in the physical path location. If you select a file from the virtual store path that is not available in the physical path, the data in that file is not added to the catalog database.
Removes currently selected Excel workbooks from the Excel files box.
Excel codelist files
Lists the codelist Excel workbooks. Click the browse button to access the Open dialog box, which allows you to select one or more Excel codelist workbooks for loading into the catalog schema database. To remove a codelist workbook, you must click Reset to clear all boxes on the Bulkload utility.
You must select a codelist workbook when one of the following criteria is met:
You have updated the codelist information and want to bulk load the modified data into the live database.
You are creating a new catalog with the Bulkload to a new catalog option.
For all other instances, the Excel codelist files box can remain empty.
Allows you to select the type of bulkload.
Bulkload to a new catalog
Select this mode when you want to create a new catalog database set. You can use this mode to create a new catalog containing your company data and not any delivered reference data. In this mode, you must specify a template file for the schema.
It is not recommended that you create a new catalog database when bulkloading the reference data. The catalog database created when bulkloading is not associated with any site database.
Append to the existing catalog
Select this mode when you want to only add new classes to the catalog database. In this mode, the software does not read any add/modify/delete flags in the column beginning each row. Use this mode for large updates to the catalog.
Add, modify, or delete records in existing catalog
Select this mode when you want to modify the catalog database on a smaller scale than in the append mode. Use this mode for small updates to the catalog.
In the add/modify/delete mode, the Bulkload utility scans the workbook(s) for the following flags at the beginning of rows:
For example, if the Bulkload utility sees an M at the beginning of a row in the workbook, the software modifies that entry in the catalog database.
Delete and replace records in existing catalog
Replaces existing data in the catalog database with the data in Excel workbooks. New part classes are appended to the catalog.
This option has some limitations. You can change the definition of a part class, but you cannot change the part class type. This option is not supported for sheets common to all the workbooks, such as the ClassNodeType and R- Hierarchy sheets. If you bulk load these unsupported sheets, the utility writes a warning to the log file and does not process the sheets.
If you are re-creating part classes or parts, you must include the R- ClassNodeDescribes sheets in the workbooks in order to establish relationships among the hierarchical nodes in the reference data.
Select this option when you want to compute and store in the catalog the specific geometry for each different size of a part class. This mode allows users to place an occurrence of a particular part in the model without having a license for Solid Edge on their computers. However, you must have Solid Edge installed on the administrator computer that does the bulkload process for the specific parts and flavors.
Update Object Type Hierarchy and Catalog Views
Select this option to update the Object Type Hierarchy (BOC) and the catalog view after bulkloading the data. Clearing this option will significantly reduce the time it takes to bulkload the workbooks. However, you should leave this option selected unless you are bulkloading to a test catalog. Do not bulkload to a production catalog without making sure this option is selected.
Specifies the type of database, either ORACLE or MSSQL. ORACLE is only available if you are creating a new plant database set.
Database server name
Select the MSSQL server that stores the catalog database. This box is available when you select MSSQL for Database Type.
Select the name of the Oracle net service for the catalog database connection. This box is available when you select ORACLE for Database Type.
Select the name of the catalog database into which you want to load reference data. If you are using the Bulkload to a new catalog mode, select <New Database>, and type a name in the Database name box. If you select a site or model database in this box, the utility displays a notification message.
Template file to be used to create schema
Specifies the template file for the catalog schema. This box appears only for the Bulkload to a new catalog mode.
For MSSQL, use the apprepos.dat file to create the catalog schema. This file is located in [Product Folder]\DatabaseTemplates on the computer where the reference data was installed.
For ORACLE, use the apprepos.dmp file to create the catalog schema. This file is located in [Product Folder]\DatabaseTemplates on the computer where the reference data was installed.
The following boxes display only for the append, add/modify/delete, and delete/replace modes.
Catalog schema server
Displays the name of the server that stores the catalog schema database. This server is the same as the name in the Database server name box.
Catalog schema database
For pre-existing catalog sets, select the name of the catalog schema database.
If the necessary schema database does not appear in the Schema database name list, click <Refresh>. This situation occurs if you created a schema database after opening the Bulkload utility.
If you are using the Bulkload to a new catalog mode, the Catalog schema server and Catalog schema database boxes do not appear. Instead, complete the box labeled Template file to be used to create schema.
Click the browse button to specify a location and name for the log file, which records the bulkloading status, including any error messages. The log file name must follow operating system constraints and cannot contain any special characters. However, you can use the backslash when specifying a UNC path to a log file.
You must use the file extension .log for the log file.
You must have write privileges to the folder to which you are saving the log file.
Symbol and custom program file location
Displays the location for symbols in Solid Edge or Visual Basic format. In the Append, Add/Modify/Delete, and Delete/Replace modes, the Bulkload utility automatically populates this box with the current symbol location. For these modes, you cannot modify the symbol path for the catalog. In the New mode, you can click the browse button to specify the location.
This location is stored in the catalog database and is accessed by the other tasks at run-time in order to read and compute the symbol files. To allow all workstations to access the symbols, specify a UNC path (for example, \\MyServer\SharedContent) to a shared folder on a remote computer, such as the server. At a minimum, users need read access to this share. They need change access in order to modify the symbols.
You can also specify a path (such as D:\SharedContent) on the local computer, but this action does not allow other workstations to access the symbols.
Starts the bulkload.
Resets the utility to its default values, and removes workbooks from the Excel files and Excel codelist files options.
Closes the utility. If bulkload options are defined, a bulkload is not started.