Working with Deployment Packages

To deploy an application you have created with the Active Expert, you need to create a deployment package. A deployment package contains all the application data needed by Active Expert at run-time (such as type libraries and registration information). The deployment package is a self-registering ActiveX control with the file extension .dpy.

You can generate a deployment package on one or more modules to jump start run-time testing and deployment of your client application.

You can also set options to control how deployment packages get generated.

Deployment Options

To set Deployment options:

1. Choose Tools->Options from the menu bar (or use keyboard shortcut Alt T O).

2. Click on the Deployment tab.

   This brings up the default options window for Deployment.

   Figure 3-14 Deployment Options

   

   The following table explains the options available on the Deployment options window.

   Table 3-8 Deployment Options

   Topic Section	Field	Description
   Housekeeping	Location	Indicates the default location to which deployment packages are generated. If this directory does not exist, the Application Builder prompts you when you try to generate a deployment package, and gives you the option of generating the deployment package into the current directory.
   	Confirm on overwrite	Enables or disables confirmation when a given deployment package already exists. (In the figure, this is on.)

3. When you have filled in the fields, click OK to save your changes and close the window. (You can also click Cancel to close the window without saving.)

To generate a deployment package on one or more modules:

1. Make sure the Workstation Objects window is open.

2. Choose Tools->Deploy Modules from the menu bar (or use the keyboard shortcut Alt T D).

   This brings up the Workstation Modules window that lists the modules available to be deployed. This window shows all registered modules and lets you select which ones you want to deploy. In Figure 3-15, only one module is showing because only one module was registered to the workstation.

   Figure 3-15 Workstation Modules (for deployment)

   

3. Select the modules you want to deploy and click OK to save your selection and close the window. (You can also click Cancel to close the window and interrupt the deployment.)

   This brings up the Deploy Modules file window (a file browser) in which you can verify the file name and location where you want the deployment package saved. (The default location shown on the file browser is determined by how the Deployment options are set.)

   In Figure 3-16, since only BANKAPP is chosen, the Deploy Modules window prompts you with the default name BANKAPP.dpy.

   Figure 3-16 Deploy Modules

   

   Had more than one module been chosen, the File name field in the Deploy Modules window would have the value *.dpy.

4. When the appropriate path and file name are showing on the browser, click Save on the file browser.

   This closes the window and creates the deployment package in the specified file and location.

   (You can also click Cancel to cancel your changes and close the window.)

   Note: Another shortcut to deploy a single module is to select a module in the Workstation Objects window and choose Deploy from the popup menu on the module (right mouse click to get popup menu). In this case, only one module is deployed, and the File name field contains the selected module name.

See also help on the Deployment Options and Workstation Modules (for Deployment).

Deploying a Client Application

To deploy an Active Expert client, perform the following steps.

Set Up the Run-time Environment

Ensure that the system on which you want to deploy your client application has the following software installed:

• TUXEDO /WS

• TUXEDO environment setup file specifying appropriate host and port

• Active Expert run-time environment

Ensure that TUXEDO and Contract Repository (IREPSVR) servers needed by your client application are running and accessible by the client.

Have a Deployment Package Ready

Make sure you have created the module deployment package (.dpy file) in the Active Expert. (Refer to the section "Generating a Deployment Package.")

Create the Client Executable

In your Windows development environment (Visual Basic, PowerBuilder, or Visual C++), create the client executable.

Configure Files for Setup Utility (Visual Basic Only)

In order for deployment of Active Expert applications to work automatically with the Visual Basic Application Setup Wizard, information about the deployment package must be provided to the appropriate setup wizard before it is run.

Visual Basic 4.0

An entry must be added to the file swdepend.ini. This file appears in the Windows directory, but it may not be there unless the Setup Wizard has been run at least once. Assuming that the deployment package is called bank.dpy, the entry has the following format:

[BANK.DPY]
Register=$(DLLSelfRegister)
Dest=$(WinSysPath)
Uses1=

This entry can be placed at the end of the file.

Visual Basic 5.0

A .dep file must be created with the same name as the deployment file, and placed in the same directory. For example, again assuming a deployment file of bank.dpy, create a file called bank.dep and place it in the same directory as bank.dpy. The format of bank.dep is as follows:

[Version]
Version = 1.0.0.0
[BANK.DPY]
Register=$(DLLSelfRegister)
Dest=$(WinSysPath)
Date=10/13/97
Time=16:34:11
Version=0.1.0.1
CABFilename=
CABDefaultURL=
CABINFFile=
CABRunFile=
Uses1=

For Visual Basic you can use the Setup Wizard. Follow the instructions and provide the requested input on the utility windows for setting up your client for distribution. When prompted by the setup windows, be sure to:

• Indicate the location of the Active Expert executable (for example, the "project file" in Visual Basic)

• Add your deployment package (clientname.dpy) to the set of files to be distributed with your application

The setup utility creates a "setup" executable for your client application (along with some associated files needed to carry out the installation). At this point, you are ready to distribute the new client.

For PowerBuilder and Visual C++, you will need to run regsvr32 after the package has been installed (for example, regsvr32 myapp.dpy).

Note: If the deployment package was not added to the set of files to be distributed with your application, then you can manually register the Active Expert deployment information by running the Windows regsvr32 utility. For example: regsvr32 DeploymentPackage.dpy

Load All Needed Files onto the Target System

Load the setup executable and all associated files onto a Windows system where you want to install the Active Expert client. Make sure that the Contract Repository server (IREPSVR) is running when the client application is being installed or when regsvr32 is run on the deployment package.

Run the Setup Executable to Install the New Client Application

Open the setup executable to start the installation process. Follow the instructions and provide the requested input on the windows to install your client application on the new machine.