If you plan to run your Web Application on an IBM i Web Server, you will need to ensure the required objects are deployed to the IBM i environment. The first step is to check in and "compile" the LANSA objects required by the application.
You are probably familiar with checking in files and the like, so on the surface checking in Web Pages and Reusable Parts targeted for the web is pretty much the same. Under the surface though there are a few subtle differences you need to be aware of.
When is a Compile not a "Compile"?
When you check in (or deliver to) and compile a Web Page or Reusable Part targeted for the web the object is not actually "compiled" on IBM i. What really happens is that the files are generated in your IDE environment, including the HTML and JavaScript files, then copied to the IBM i. They are not re-generated on the IBM i.
This means that any references to the runtime in the HTML files are based on the Visual LANSA environment's current runtime not the IBM i runtime environment. In most cases this is not a problem as your Visual LANSA and IBM i systems should be at the same release level.
The runtime version may become an issue though when you export the Web Application to another LANSA system. When this happens, the generated files are again copied rather than regenerated, so they will still reference the runtime used to generate the files in the IDE. It is therefore important to ensure that any LANSA system these objects are deployed to also has the required Web runtime installed.
For information on setting up and configuring an IBM i Web Server refer to LANSA for I Administration Guide.