Step 3. Define Repository Objects Included in Package

In this step, you will add all components and files individually to the Version 1 package, without relying on cross references to add the reusable parts used by the web page, for example. In the exercise Define a Deployment Tool Application (DTE125) we showed how default cross reference rules can be defined. Due to a small fault in V14 SP1, we are not able to use cross referencing for web components, at this time. This will be corrected in V14 SP2.

1.  In the Deployment Tool main window, double click on Version 1 for the Application WEBAPP to open the Package Maintenance window.

2.  Open the Select repository objects dialog using the toolbar button.

3.  Expand the Web Pages group and locate your web page II_Employees (where II is your initials). Drag this onto the right hand panel, to include it in the package.

4.  Select the web page II_Employees and click the Cross Reference toolbar button.

     In the Cross Reference Settings dialog, click the Deselect All button and click OK to close the dialog. This removes cross reference processing for the web page.

5.  Expand the Reusable Parts group. Locate your six II_ components and drag them to the right hand list, to add them to the package.

6.  Expand the letter X and locate the reusable part xDemoWebMessageBar and add this to the package. This component is used by the Employee Editor component.

7.  Hold down the Shift key and select all the reusable parts in the right hand list. As before, use the toolbar button to open the Cross Reference Settings dialog. Click the Deselect All button and then the OK button, to remove cross reference processing for these components.

8.  Expand the Server Module group and locate the component II_DataServices. Add this to the package. In the Selected Objects list, there should be no tick on the left hand side, because cross reference defaults were not defined for server module components.

9.  Expand the Files group and locate the files xDepartments, xEmployee and xEmployeeImages. Drag them onto the right hand panel to add them to the package.

10. Select all three selected files on the right hand panel. Click the Include file data toolbar button and select Include data (new files only):

     This package is defining a new database. You need to include data for the three selected files.

11. With the three files selected, click the Set Library Substitution toolbar button. Select PARTDTALIB and click the Select Library button, which will also close the dialog.

     Tables in an SQL database are defined belonging to a schema or collection (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 Deployed Schema for a full description of the features available for managing the schema name used in an SQL database.

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

13. In the Package Maintenance dialog, click Save to save your current settings.