WEB1, Step 4. Install the Deployment Material on the Target System

VLF Deployment Check Lists

 

WEB1, Step 4. Install the Deployment Material on the Target System

Step

 Activity                                   

How to Do It

ü

Install LANSA for the iSeries on the target IBM i server

From the LANSA CD install LANSA for the iSeries.

Note that the LANSA system has to be on the same version and EPC level as the system on which the deployment material was created.

 

Also install LANSA for the Web.

 

Follow the instructions in <A HREF="javascript:void(0);openCHM('lansa040.chm','main');">Installing LANSA on IBM i Guide</A>.

 

 

 

If deploying a VLF.NET Application, install Microsoft's .NET Framework on end-user PCs

See <A HREF="webnet_0045.htm">Install Microsoft's .NET Framework on end-user PCs</A>.

 

 

 

Verify that L4Web is installed and operational on the target system

Make sure the partition is web enabled. Execute a LANSA for the Web process or function.

 

  

 

 

Make sure that your HTTP server is configured to support server side includes

For example, if your HTTP Server configuration is called DEVINST you can execute this command in an IBM i command line:

WRKHTTPCFG DEVINST

Browse through the configuration details and make sure that it includes an entry like this one:

Imbeds On html

 

If it doesn't and you are not confident of adding it yourself, contact your IBM i administrator to add such an entry. When your HTTP server configuration has been changed, you generally need to stop and restart it before the changes take effect.

 

 

 

 

Ensure that Extended Exchange is enabled

The Enable Extended Exchange option needs to be selected.

 

Using the LANSA for the Web Administrator, connect to your server system.

 

From the Tools menu, choose Configure System. Select Miscellaneous tab and verify that Enable Extended Exchange is enabled (that is, the checkbox is checked).

 

 

If using VLF.NET, ensure IBM i Apache server configuration is correct

Some minor configuration changes may need to be made to the MIME types control table on IBM i Apache servers so that the files are served correctly.

Use the Apache administration browser interface (*ADMIN instance in port 2001) and click on Content Settings link.

In the MIME tab, click on the ADD button to add the following Content-type entries:

File Extension -                                  Value

application -       application/x-ms-application

manifest -          application/x-ms-manifest

deploy -             application/octet-stream

 

Or if editing the configuration file with a text editor, in the relevant section add these lines:

AddType application/x-ms-application application

AddType application/x-ms-manifest manifest

AddType application/octet-stream deploy

 

 

 

Create a private working folder for the Framework

You need to create a <A HREF="javascript:void(0);openCHM('lansa048.chm::/lansa/vlf1995.htm','main');">Private Working Folder</A> to upload the files required to run the Visual LANSA Framework in the browser.

Create this directory as a subdirectory of the LANSA for the Web images directory on your web server.

For example, if your LANSA for the Web images directory was named IMAGES, you might create a directory named <C:\Program Files\<LANSA>\Webserver\ IMAGES\VLF_Private_Folder.

The private working directory needs to be accessible via your web browser. To test, enter a URL like this:

http://<your host>/images/VLF_Private_Folder

 

Where <your host> is the IP address of your LANSA for the Web server.

 

 

·     

 

 

Import deployment material to the application server

Use LANSA's import facility to install everything from the save file Bnn_ALL to the appropriate partition on the target machine.

 

 

Use the option Import objects into this partition of the LANSA Housekeeping menu. Check that the import was successful.

 

 

 

Restore IFS objects

Restore all objects from Bnn_IFS into the images and the private working folders on the target system's IFS.

If you are using RAMP-NL, restore the RAMP objects.

 

Either use RST commands or a call to CL program.

See Notes on the SAV and RST commands.

If you are deploying RAMP-TS, see <A HREF="webrampts004.htm">Install your RAMP-TS Screen Definitions at the Deployment Target</A>.

 

 

 

 

 

 

Restore the non-LANSA objects

If your application contains non-LANSA objects, restore everything from the Bnn_OMn files into the appropriate IBM i library on the target system.

Use the RSTOBJ command to restore library-based objects from the save file. For example:

RSTOBJ OBJ(*ALL) SAVLIB(B01_OM1) DEV(*SAVF) SAVF(B01_OM1)

 

 

 

 

Create a directory to keep temporary files in

You need to create a working folder to keep temporary Framework files in.

Create this directory as a subdirectory of the LANSA for the Web image directory (typically called IMAGES).

 

 

For example, if your LANSA for the Web images directory is named IMAGES, you might create a directory on the IBM i named:

/LANSA_vlfpgmlib/webserver/images/VLF_Temporary_Files

 

 

If you want more information, see <A HREF="javascript:void(0);openCHM('lansa048.chm::/lansa/lansa048_0545.htm','main');">What is a temporary directory and what is it used for?</A>

 

 

 

Verify that the temporary directory is accessible to Web Browsers

For example if you created VLF_Temporary_Files as a subdirectory of real directory IMAGES or LANSAIMG (in pre version 11.0 versions of LANSA) open your Internet browser and in the address bar type:

 

http://<your host>/images/VLF_Temporary_Files/

 

Where <your host> is the IP address of your LANSA for the Web server.

The browser should display the contents of directory VLF_Temporary_Files in directory IMAGES or LANSAIMG.

Note: Your web server will interpret the real directory name LANSAIMG as virtual directory name /IMAGES/.

 

 

 

 

Execute the Administrator's Console to specify your system settings

Use the Administrator's Console to maintain system settings and clear temporary state data.

To execute the Administrator's Console, run this URL from an Internet Explorer workstation:

http://<your host>/cgi-bin/lansaweb?procfun+vf_pr004+vfu0402+<ppp>

 

Where <your host> is the IP address of your LANSA for the Web server and <ppp> is the partition to be used.

Click the Save and Verify Values button to save these system settings. The resulting web form should indicate that all the tests performed were PASSED.

 

Use these system settings:

Is the Framework Available?: Yes

Apache web server: Yes

Message when Framework not available: A message to show to users when all Frameworks using this partition are disabled.

Real directory for temporary files, for example:

/lansaimg/VLF_Temporary_Files/   

Virtual directory for temporary files:/images/VLF_Temporary_Files/

Use Server Side Include: Yes.

If you need more information see <A HREF="javascript:void(0);openCHM('lansa048.chm::/lansa/lansa048_2240.htm','main');">Execute Administrator's Console</A>. <A HREF="javascript:void(0);openCHM('lansa048.chm::/lansa/lansa048_2285.htm','main');"></A>. <A HREF="javascript:void(0);openCHM(' lansa048.chm::/lansa/lansa048_2285.htm','main');">

 

 

Verify the software installation was okay

To verify the LANSA for the Web component of the installation or upgrade was okay start Internet Explorer and execute this URL:

http://<your host>/cgi-bin/lansaweb?procfun+vf_pr004+vfu0401+<ppp>

 

The resulting window will show you details about the installed Framework.

 

 

 

 

Execute the Framework application

Execute the Framework application.

Note that you need to explictly indicate the partition to which you have deployed the application, otherwise you will be executing the Framework against your development partition.

You can do this by specifying the partition name in the URL as in the examples on the right, or you can open the vf_Sy001_System_xxx_xxx.htm file and change the value of the var __Partition setting to point to the partition.

Also see the topic <A HREF="javascript:void(0);openCHM('lansa048.CHM::/lansa/lansa048_2915.htm ','main');">The URL to start my deployed VLF web browser application is too complex for users to reliably type in to their browsers </A> in the Framework guide.

Typically starting URLs are formatted like this example:

http://nnn.nnn.nnn.nnn/../vf_Sy001_System_ENG_BASE.htm?partition=ppp

 

For example:

http://<your host>/images/Private/vf_sy001_system_ENG_BASE.HTM?partition=mpx

 

If the application does not execute, see the messages in x_err.log and run a trace. For example:

http://<your host>/images/Private/vf_sy001_system_ENG_BASE.HTM?trace=y+developer=y

 

We recommend you have a look at <A HREF="javascript:void(0);openCHM('lansa048.CHM::/lansa/lansa048_0900.htm','main');">Web Application Start Options</A> in the Framework guide to see what you can do when you launch the application.