WIN2, Step 2. Package the Deployment Material on the Source System

Step

 Activity

How to Do It

ü

Start the Deployment Tool

Logon to Visual LANSA and start the Deployment Tool.

Start Visual LANSA and logon to the partition containing the application to be deployed.

Ensure that you use a user profile which is authorized to the objects that are being deployed.

From the Tools ribbon, select the Deploy button. The Visual LANSA Deployment Tool's main window will open.

Create a Deployment Tool application and package

Create an application and a package using the Deployment Tool.

Do not use any template.

Click on the New Application button on the tool bar or select the New command from the Application menu.

Fill in the application details.

Click OK. You are prompted to create a Package. Fill in the package details and click OK.

The Package Control Panel is displayed

Specify package settings

·      Deploy to Client Without Local Database

·      Deploy System/Partition Definitions

·      Omit Object Definitions

·      Deploy LANSA Execution Environment

·      Deploy with Component Support 

·      Deploy LANSA Communications

Click on the Package Settings button on the toolbar to display the Package Settings window.

Configure the application to use remote database

Because you are deploying for access to a remote database, you must configure the application not to use a specific database. In the Database section, set the database options to No and specify the DBMS Type (DBUT=) as No Database.

Double-click on the DBMS Type (DBUT=) parameter.

Define the connection behavior

Accept the defaults in the Communications and SuperServer sections.

Specify the startup form

Enter the name of the start-up form in your application.

UF_EXEC is the standard start-up form. Most likely you have created your own entry point form so specify its name.

Note that your entry point form needs to point to the correct Framework  definition file. For more information see <A HREF="javascript:void(0);openCHM('lansa048.chm::/lansa/lansa048_3430.htm','main');"> Deploying a Framework Version </a> in the Framework Guide.

Double-click on the parameter Form to Execute (FORM=) in the Required Execution Parameters area.

Decide what execution parameters need to be prompted

If you want to prompt for a setup parameter when the package is installed, enable the prompting by selecting the parameter and checking the Prompt during installation option.

For example, to enable the Prompting of the Target Directory option, double-click the parameter and select the Prompt during SETUP check box in the window which is displayed.

Add LANSA programs

Add all the LANSA programs in your application.

Add forms starting with FP_*, UF_* and VF_*.

Add reusable parts starting with FP_*, UF_* and VF_*.

, (If you want to be able to run the demonstration system, include all forms and reusable parts starting with DF_* and process DF_PROC, and the *.htm, *.bmp and *icon files required.)

Include process VF_PR001, VF_PROX1 and UF_SYSBR with all their functions.

Click on the Select Repository Objects button. Drag the objects you want to include to the area on the right.

Then select all the objects on the right and select the Cross-Reference icon above the selected components. A new dialog will open to allow you to select the cross-reference settings.

Ensure all required object types are selected

Add Other Framework Objects

Locate your XML files in the execute directory of your partition (for example C:\Program Files\LANSA\X_WIN95\X_LANSA\x_DEM\execute).

Add these files to the package (if you have saved your Framework definitions with other names, add the corresponding XML files):

·      vf_sy001_system.xml

·      vf_sy001_users.xml (if using)

·      vf_sy001_servers.xml

·      vf_sy001_tables.xml

If you are deploying a RAMP-TS application, add the VF_SY001_nodes.xml file, the corresponding VF_SY001_nodes*.js file and the <framework_name>_eng.js file.

Add U_bif987.dll and u_bif985.dll from the X_LANSA Execute directory.

If you want to deploy default Virtual Clipboard content, select VF_Framework_Virtual_Clipboard_Default.dat and/or VF_User_Virtual_Clipboard_Default.dat.

Bring up the Other Objects tab.

Double-click Non-LANSA Objects to browse for the objects. Make sure you are browsing in the LANSA system you are currently using.

Note that the Deployment Tool does NOT default to the current system and partition, you have to select them manually.

Select the objects and click OK.

Then set the path where the objects are to be installed:

·      Use SYSPATH (system execute directory) as the installation Path Id for U_bif987.dll and u_bif985.dll. For the other objects:

·      Use DFTPATH as the Installation Path Id (for example *PART_DIR_EXECUTE)

Include your client-side objects

Add  your objects (filters, command handlers, start-up forms, etc.),  multilingual text variables, system variables, message files, files, processes, functions and images used in the client side of your application.

Click on the Select Repository Objects button on the toolbar.

Ensure that all non-LANSA objects have correct installation paths specified for the target machine.

Add an icon

Add an icon to be used with the shortcut created on the target machine when the package is installed.

Click on the Application Icon button on the toolbar of the Package Control Panel.  Select an icon.

Choose Desktop settings

Choose the Desktop settings depending on your preferences.

For example, you may want to select these options:

·      Create Communications Administration Shortcut

·      Create ODBC Administration Shortcut

Include RAMP-NL objects

If you are deploying a RAMP-NL client that will connect to an IBM i server, you need to add RAMP objects to the package.

Follow the steps in <A HREF="VLFDpl_0050.htm">Check List/Planning Sheet => WIN-RAMP-NL</A>.

Save the package

Save the package definition.

Include the host route for an Application

Include the host route for the server definition (the lroute.dat file) in the package.

From the Visual LANSA Deployment Tool Main window, select your application and then click on the Communications Administrator tool bar button.

The Communications Administrator is displayed. Make sure an entry is specified for the server you have defined in step 1.

Close the Communications Administrator. Make sure the application is selected, and click on the Application menu and select the Package Communications Administration option to select it.

Build the package

Check and build the package.

Your application package is created in the X_APPS\PackageName directory (for example. C:\Program Files\LANSA\X_WIN95\X_LANSA\ X_APPS\PackageName).

Select the Check Package option in the Options menu. The message you receive should tell that no errors were encountered.

Click on the Build button. Wait for the package compilation to complete.

Note that if you are working in a partition that has not been enabled for full RDMLX, you may see errors saying that the copy of some dlls has failed. Just ignore the messages.