Step 3. Define the Repository Objects included in the Package.

1.  Open the Select repository objects dialog using the WorECA1  toolbar button.

     Expand the Files group and add the following file to the package:

xEmployee – Employees

2.  Select the file in the right hand list, and click the Cross Reference Wor7DCD toolbar button.

3.  Select these check boxes:

     These options will:

4.  Click OK to save these changes.

5.  Select the file xEmployee in the list, click on the File Data WorACC6 toolbar button:


6.  Select the option Include data (new files only). This option will include data for the file, if the file does not already exist in the database.

     Note: Typically, you would only include data for lookup tables, for examples a table containing a list of USA States. Application data files (e.g. invoices, orders, customers etc) would be empty files at this stage so they are deployed without data.

7.  With the file in the list selected, click the File Library Substitutions WorE0AE toolbar button.

8.  Select the PARTLIB Substitution Id, and click Select Library, which will also close the dialog.

     Tables in an SQL database are defined belonging to a schema (this term varies depending on the DBMS). LANSA uses the library name to set the table schema name. The selected option will give all files a schema based on the default file library name for the partition into which they are deployed. For example, a library name of T14TRNDTA will generate a SQL Server schema name of X4TRNDTA. The schema name is limited to eight characters.

     Note: See Mapping a File's Library to a Fixed Deployment Schema for a full description of the features available for managing the schema name used in an SQL database.

9.  Click OK to close the Select repository objects dialog.

     You have added the main application file (xEmployee) and any other files which it depends upon through validation rules and predetermined join fields.