documentation.HELP! LANSA Deployment Tool Documentation

21 How To

LANSA Deployment Tool

previous page next page

21. How To ... ?

21.1 Create a Deployment Version

21.2 Connect to the Required Server

21.3 Search Packages including an object

21.4 Back up your Application Definitions

21.5 Deploy an external ActiveX control

21.6 Deploy LANSA Components published for ActiveX

21.7 Deploy User Defined RDML BIFs

21.8 Install Runtime License for Application

21.9 Set DLL Version Information

21.10 Specify Installation-Specific Database Connection Settings

21.11 Deploy a 64-bit Application

21.12 Install Application Files into a consistent schema name

 

 

previous page start next page

Menu

  • Homepage

Table of contents

  • LANSA Application Deployment Tool
    • About this Guide
      • Who should use this Guide
      • How to use this Guide
      • Additional Information
    • 1. Introduction
      • 1.1 What is the Deployment Tool?
      • 1.2 The Deployment Model
        • 1.2.1 What is an Application?
        • 1.2.2 What is a Version?
        • 1.2.3 What is a Patch?
        • 1.2.4 What is a Package?
        • 1.2.5 What do you need to deploy?
      • 1.3 Upgrading a LANSA-developed Application previously deployed
      • 1.4 Who should use the LANSA Deployment Tool?
    • 2. What's New?
      • 2.1 A New Deployment Model
      • 2.2 File Library Automatically set to Partition Library
      • 2.3 Set File Library
      • 2.4 Control File Data Loading and Unloading
      • 2.5 Network Client Installation decided during Installation
      • 2.6 Runtime always Included in Installation Files
      • 2.7 Translation Tool integrated into Visual LANSA Tools
      • 2.8 Unknown objects are no longer dropped when Package is saved
      • 2.9 Host Route Table and Listener defined at Application Level only
      • 2.10 Backup or Restore Applications
      • 2.11 New option Require Elevation
      • 2.12 New options to install Web Features
      • 2.13 Options not selected to Prompt during Installation are no longer shown
    • 3. Plan your Deployment
      • 3.1 Deployment Tool Environment
        • 3.1.1 Using a Workstation as a Server
      • 3.2 Lifecycle of an Application
        • 3.2.1 Mapping a File's Library to a Fixed Deployed Schema
      • 3.3 Version or Patch Upgrade?
      • 3.4 Per-User or Per-Machine Install?
      • 3.5 Digital Signatures
        • 3.5.1 Why digitally sign MSI and MSP files?
      • 3.6 Installation Mode
      • 3.7 SCCM Integration
    • 4. Getting Started with the Deployment Tool
      • 4.1 Deployment Tool Main Window
        • 4.1.1 File menu
        • 4.1.2 View menu
        • 4.1.3 Tools menu
        • 4.1.4 Main window toolbar
      • 4.2 Package Maintenance Window
        • 4.2.1 Package File Menu
        • 4.2.2 Package Edit Menu
        • 4.2.3 Package Verify Menu
        • 4.2.4 Package Maintenance toolbar
      • 4.3 Help
    • 5. Configure the Deployment Tool
      • 5.1 Set up Company Details
        • 5.1.1 Company Maintenance
        • 5.1.2 Create a Company
      • 5.2 Default Cross Reference Settings
    • 6. Applications
      • 6.1 Create an Application
      • 6.2 Change an Application's Details
      • 6.3 Delete an Application
      • 6.4 Include Communications Tables
    • 7. Versions and Patches
      • 7.1 Create a Version
      • 7.2 Create a Patch
      • 7.3 Open a Package
        • 7.3.1 Edit Installation Options
        • 7.3.2 Edit Settings
        • 7.3.3 Change Description
        • 7.3.4 Associated Template
      • 7.4 Delete a Package
      • 7.5 Convert a Pre-V13 Package
      • 7.6 Save a Package
      • 7.7 Check a Version or Patch
      • 7.8 Build a Version or Patch
        • 7.8.1 Package Build Log
      • 7.9 Package Distributed
    • 8. Options & Settings
      • 8.1 Installation Options
        • 8.1.1 Execution Parameters
        • 8.1.2 Additional LANSA Features
        • 8.1.3 Just in Time
        • 8.1.4 SuperServer
        • 8.1.5 Database
        • 8.1.6 Desktop Settings
        • 8.1.7 Upgrade Options
        • 8.1.8 MSI Installation Dialogs
      • 8.2 Select Repository Objects
        • 8.2.1 Selected Object Viewer
        • 8.2.2 Special Considerations for Object Types
        • 8.2.3 Cross Reference Settings
        • 8.2.4 Include and Process File Data
        • 8.2.5 Configure the File Library Substitution
        • 8.2.6 Configure the Non-LANSA Object Installation Path
      • 8.3 Settings
      • 8.4 Application Icon
      • 8.5 X_RUN Arguments
      • 8.6 Commands to execute
        • 8.6.1 Conditions to Control the Execution of a Command
        • 8.6.2 Valid Commands and Parameters
        • 8.6.3 Valid Substitution Variables for Command Parameters
      • 8.7 Languages
        • 8.7.1 Custom Language Definition
      • 8.8 Web Designs
      • 8.9 Files with Special Processing
    • 9. Deploy LANSA Communications
      • 9.1 Include Host Route and Listener Tables
      • 9.2 LANSA Communications Package Settings & Options
    • 10. Deploy Client / Server Applications
      • 10.1 Client / Server Deployment Considerations
      • 10.2 SuperServer Application using Built-In Functions to connect to server
      • 10.3 SuperServer Application connecting to a Windows or Linux Server
      • 10.4 SuperServer Application connecting to an IBM i server
      • 10.5 Network Client Installation
    • 11. Deploy LANSA for the Web Applications
      • 11.1 Web Server Deployment
      • 11.2 Data Application Server with Windows Application Database
    • 12. Just In Time Upgrade Guidelines
      • 12.1 Major differences in Package 13 JIT Upgrade
      • 12.2 Package Upgrades
      • 12.3 Application Servers
      • 12.4 Target PCs and the Client Application
      • 12.5 Application Server Development Life Cycle Recommendations
      • 12.6 Just In Time Upgrade Recommended Settings
      • 12.7 Troubleshooting Just in Time
      • 12.8 Tracing Just in Time Connections
      • 12.9 Upgrading to Version 13 using JIT Upgrade
      • 12.10 Customizing Just In Time Package Upgrade
    • 13. Deployment Templates
      • 13.1 Create a Deployment Template
      • 13.2 Review, Change or Delete a Deployment Template
      • 13.3 Convert a Pre-V13 Template
      • 13.4 Deployment Template Options & Settings
        • 13.4.1 Template Installation Options
        • 13.4.2 Template Option Values and Appearance
        • 13.4.3 Template Subset Appearance
      • 13.5 Supplied Deployment Templates
        • 13.5.1 XACTIVEX - Publish LANSA Component wrapped as ActiveX
        • 13.5.2 XALONE - Standalone system
        • 13.5.3 XAPPSV - Set up an Application Server without database for Just In Time Package serving
        • 13.5.4 XAPPSVDB - Set up an Application Server with database for Just In Time Package serving
        • 13.5.5 XCLT400 - Client application using SuperServer to connect to an IBM i data server
        • 13.5.6 XCLT400X - Client application using SuperServer to connect to a RDMLX IBM i data server
        • 13.5.7 XCLTBIF - Client application using SuperServer Built-In Functions to connect to the data server
        • 13.5.8 XCLTJIT - LANSA SuperServer application updated by Just in Time
        • 13.5.9 XCLTOTH - SuperServer application connected to an "Other" data server
        • 13.5.10 XEXPORT – Export internal definitions
        • 13.5.11 XOTHOBJ – Deploy Non-LANSA Objects
        • 13.5.12 XSRVNET - Set up a Network server
        • 13.5.13 XSRVOTH - Set up an "Other" data server
        • 13.5.14 XTRNAPP – Translation Application with Object Details for Translation
        • 13.5.15 XTRNEXP – Export Object Details for Translation
        • 13.5.16 XWAMENB – Web Enable for WAM Application
    • 14. Translate a LANSA-developed Application
      • 14.1 Translate using standalone Translation Application
        • 14.1.1 Deploy Translation Application including Objects to Translate
        • 14.1.2 Install Translation Application and Translate Objects
      • 14.2 Translate with Visual LANSA development environment
        • 14.2.1 Deploy Objects to Translate
        • 14.2.2 Run the Translation Application and Translate Objects
      • 14.3 Load Translations for Appropriate Language
    • 15. Review your Deployment Package
      • 15.1 Objects included in Package
      • 15.2 Search Application
      • 15.3 Convert pre-V13 Package
    • 16. Test your Deployment Package
      • 16.1 Allocate a PC for building your Deployment Packages
      • 16.2 Allocate the necessary PCs for testing your Deployment Package
      • 16.3 Troubleshoot the Deployed Application
    • 17. Install an Application
      • 17.1 Windows Installer File Install
        • 17.1.1 Double-click the MSI or MSP file in explorer
        • 17.1.2 msiexec.exe Command-Line Options
        • 17.1.3 Administrative Install
        • 17.1.4 Installation from a Web Browser
        • 17.1.5 SCCM Integration
        • 17.1.6 Version Installation Dialogs
          • Welcome Dialog
          • End-User License Agreement Dialog
          • Installation Scope Dialog
          • Destination Folder Dialog
          • Setup Application Dialog
          • Setup Local Database Dialog
          • User ID Dialog
          • Web Sites for IIS Plugin Dialog
          • Web Site Virtual Folders Dialog
          • Communication Ports Dialog
          • Setup Server Dialog
          • Setup Type Dialog
          • Verification Dialog
          • Progress Dialog
          • Completion Dialog
        • 17.1.7 Patch Installation Dialogs
          • Welcome Dialog
          • Confirmation Dialog
          • Progress Dialog
          • Completion Dialog
        • 17.1.8 Network Client Installation
        • 17.1.9 Change, Repair or Remove Application
          • Re-install MSI File
          • Windows Programs and Features
      • 17.2 Just in Time Install
      • 17.3 LANSA Import
      • 17.4 Troubleshoot the Installation
    • 18. Upgrade an Existing MSI Application
    • 19. Upgrade an Existing V12 Application
    • 20. Cloud Customizations
      • 20.1 Amazon Web Services
        • 20.1.1 Add Alarms to Your CloudWatch Log Files
          • Installation Error Alarm
          • MSI installation error
          • Other Alarms to Consider
        • 20.1.2 Procedure to follow when Upgrading Your Application
        • 20.1.3 Using a Single Availability Zone (AZ)
        • 20.1.4 Auto Scaling Considerations
    • 21. How To ... ?
      • 21.1 Create a Deployment Version
      • 21.2 Connect to the Required Server
      • 21.3 Search Packages including an object
      • 21.4 Back up your Application Definitions
      • 21.5 Deploy an external ActiveX control
      • 21.6 Deploy LANSA Components published for ActiveX
      • 21.7 Deploy User Defined RDML BIFs
      • 21.8 Install Runtime License for Application
      • 21.9 Set DLL Version Information
      • 21.10 Specify Installation-Specific Database Connection Settings
      • 21.11 Deploy a 64-bit Application
      • 21.12 Install Application Files into a consistent schema name
    • Deployment Tool Tutorials
      • About the Exercises
        • System Requirements for these Exercises
      • Set Up the Deployment Tool
        • DTE010 – Set Up the Deployment Tool
          • Step 1. Define Company
          • Step 2. Define Default Cross Reference Settings
          • Step 3. Define an Application
          • Summary
      • Deploy Client Server Applications
        • DTE015 – Create Client Server Application
          • Step 1. Import the supplied Employees Application
          • Step 2. Copy the supplied Employee Application
          • Step 3. Test the Client Server Application
          • Summary
        • DTE020 – Create Version 1
          • Step 1. Add Routing Table to Application
          • Step 2. Define Version 1
          • Step 3. Define Execution Parameters
          • Step 4. Review the Package Settings
          • Step 5. Build the Version 1
          • Summary
        • DTE025 – Install Version 1
          • Step 1. Locate the Install File
          • Step 2. Install Version 1 of Personnel System
          • Step 3. Set Version 1 to Deployed
          • Summary
        • DTE030 – Modify the Employees Application
          • Step 1. Remove Real Start and Terminate Dates from the Editor
          • Step 2. Modify the Data Component (II_DATA)
          • Step 3. Modify the Store component (II_STORE)
          • Step 4. Modify the Browser Component (II_BRWSR)
          • Step 5. Re-test the Employees Application
          • Summary
        • DTE035 – Create a Patch for the Employees Application
          • Step 1. Set DLL Version and Recompile Changed Components
          • Step 2. Create a Patch
          • Step 3. Install the Patch
          • Summary
        • DTE040 – Create Version 2
          • Step 1. Set DLL Version
          • Step 2. Enhance the Application
          • Step 3. Create Version 2 Package
          • Step 4. Install Version 2
          • Summary
      • Deploy a Stand Alone Application
        • DTE045 – Create a Stand Alone Application
          • Step 1. Import the supplied Employee Application
          • Step 2. Copy the supplied Employee Application
          • Step 3. Test the Stand Alone Employees Application
          • Summary
        • DTE050 – Create Version 1
          • Step 1. Create an SQL Server Database
          • Step 2. Define Version 1
          • Step 3. Define Execution Parameters
          • Step 4. Define the Database Parameters
          • Step 5. Review the Package Settings
          • Step 6. Build Version 1
          • Summary
        • DTE055 – Install Version 1
          • Step 1. Locate the Install File
          • Step 2. Install Version 1 of Employee Application
          • Summary
        • DTE060 – Modify the Employees Application
          • Steps
          • Summary
        • DTE070 – Create Version 2
          • Steps
          • Summary
      • Deploy Applications using JIT
        • DTE075 – Create a Just in Time Server Installation
          • Step 1. Create a JIT Server Package
          • Step 2. Install the JIT Server Installation
          • Summary
        • DTE080 – Create a Client Install Package with JIT Update
          • Step 1. Define Version 1 Package
          • Step 2. Define X_RUN Arguments
          • Step 3. Define Required Execution Parameters
          • Step 4. Define the Just in Time Parameters
          • Step 5. Review the Package Settings
          • Step 6. Add Routing Table to the Application
          • Step 7. Build the Install Package
          • Step 8. Copy Client Application Package to JIT Server
          • Summary
        • DTE085 – Install Client Application with JIT Update
          • Step 1. Locate the Install File
          • Step 2. Install Version 1 of Client Personnel System with JIT Update
          • Summary
        • DTE090 – Create a Patch for Client Personnel Application with JIT Update
          • Step 1. Change Main Form II_MAIN
          • Step 2. Create a Patch for Client Personnel System with JIT Update
          • Step 3. Update Application: Client Personnel with JIT Update
          • Summary
      • Deploy to a Windows Server
        • DTE095 – Create a Windows Server Installation
          • Step 1. Define a new SQL Server Database
          • Step 2. Create Windows Server Installation Package
          • Step 3. Define the Repository Objects included in the Package.
          • Step 4. Define Required Execution Parameters
          • Step 5. Define the Database
          • Step 6. Define Additional LANSA Features
          • Step 7. Check and Build the Package
          • Step 8. Install Windows Server Application
          • Step 10. Review Windows Server Installation
          • Summary
        • DTE100 – Execute Client to Windows Server Installation
          • Client Connecting to a Windows Server
          • Starting LANSA Windows Applications
          • Step 1. Run the Client to Windows Server Application
          • Debugging Your Windows Client Server application
          • Summary
    • Cloud Tutorials
      • System Requirements for these Exercises
      • Deploy A WAM Application into AWS
        • CTE015 – Subscribe to the LANSA Image
          • Step 1. Locate the LANSA Scalable AMI
          • Summary
        • CTE030 – Upload your LANSA WAM Application
          • Step 1.Create a bucket
          • Summary
        • CTE040 – Create the LANSA Stack
          • Step 1. Select Template
          • Step 2. Specify Parameters
          • Step 3. Options & Review
          • Step 4. Test the Stack
          • Summary
        • CTE050 – Watch the LANSA Stack Scale In
          • Step 1. Select Auto Scaling Group
          • Step 2. Wait for the Auto Scaling Group to Scale Out
          • Step 3. Allow the Auto Scaling Group to Scale In
          • Summary
        • CTE060 – Apply Windows Updates to all Web Server Instances
          • Step 1. Select Stack to Update
          • Step 2. Specify Parameters
          • Step 3. Check that Windows Updates have been Applied
          • Summary
        • CTE070 – Apply LANSA Patch to all Web Server Instances
          • Step 1. Select Stack to Update
          • Step 2. Specify Parameters
          • Step 3. Check that the patch has been Applied
          • Summary
        • CTE080 – Apply LANSA Application Upgrade to all Web Server Instances
          • Step 1. Select Stack to Update
          • Step 2. Specify Parameters
          • Step 3. Check that DBWebServer has been Upgraded
          • Step 4. Upgrade the WebServer Stack
          • Summary
    • Glossary

Get in touch

Submit feedback about this site to:

  • [email protected]

© documentation.help. Design: rehmann.co.