This document is specific to the hardware and software requirements of ASNA Wings 10.0 programs.
This document discusses the full lifecycle of using ASNA WingsRPG including IBM i, Windows Web Server, and the developer PC. It includes three sections:
All ASNA generally available product builds can be found ready for download at: https://docs.asna.com. You will need to have a user account at that site and to be logged in to download the products. If you are not logged in, you will receive an access denied message. This account doesn�t need any authorization from us.
ASNA assumes no liability for the security, protection, and/or use of your ASNA .aspx website, other ASNA products, your IBM i and its data, and/or anything so related, with these instructions.These instructions are intended specifically for developers to use to configure and deploy an ASNA .aspx application security-related issues are neither provided nor implied with this document. Deploying IIS provides more information on security related issues.
By reading these instructions you hereby hold ASNA Inc., harmless from any actual or alleged claims, demands, causes of action, liability, loss, damage, and/or injury (to property or persons) incurred by the use of this document.
Please consult with your network administrator or security officer before continuing with these instructions.
If you have any questions about the technical content of this document, please contact ASNA technical support at support@ASNA.com.
You must be running IBM i V6R1 or higher to install the required software.
This document describes installing OAR and PTFs on the IBM i if they are not already present.
This topic covers updating the System Values on the IBM i to support OAR and Wings.
Download the self-extracting exe from this page.
This document describes the process of installing and licensing DataGate for IBM i
Note that section 2 does not apply to production development. This section is only required for those who will be importing display files with Wings. This section discusses both the initial Visual Studio/Wings setup as well as deploying a Wings project.
On each PC on which you will do ASNA Wings modernization work, you will need:
Send your machine code from the ASNA Registration Assistant along with the product licenses needed to: codes@ASNA.com. Request the Wings Design Aid 10.0, Monarch Framework 10.0, DataGate WebPak 16.0, and the ASNA Visual RPG 16.0 for Visual Studio 2019 license (if used).
Once the required software is installed on the development PC, we can test connectivity between the development PC and DataGate 15.0 for IBM i.
To test this connectivity, start Visual Studio and select DataGate | DataGate Explorer
Right-Click on the Database Names Section and select: Add New Database Name
(Database name - A programmer-assigned name for this database connection. Used by the DBName parameter of the DclDB object)
Provide the Database name details
Server - Identify the location of the database server. This can be either a server name or IP address. You can use the browse button to locate the database server on your network.
Label - A programmer-assigned text label for the database name. By convention, db2 is generally used to identify IBM i database names.
Access to - Defines the platform to which this database name connects. Can be an IBM i, SQL Server, or the local DataGate database engine.
Pool connections - Determines if connections are pooled and if so, for how long.
User name - User ID used for this connection.
Password - User password for this connection.
The advanced options allow you to change more detailed properties. In general, you should not need to change these unless directed by ASNA technical Support. The common property that is changed in the advanced is the port number. (For those installs not on the on the default port 5042).
Once you have entered your database name details, click on the Test Connection button to test the connection. You should see the following screen:
If you do not see a "Test connection succeeded" message, you should receive an error notifying you of any incorrect or invalid settings. Please correct these settings and try the test connection again.
Press OK (twice) to save your database.
Enter a name for this connection and press enter. (You can always change the name or properties later)
Right-click on the database name and Select Open Connection. You should see a screen similar to the following listing your libraries:
Now we have confirmed the connection from the development PC to DataGate 15.0 for IBM i
A Wings project, as it lives in Visual Studio, needs to be "published" for use on a Web Server. We recommend that you publish first to a local folder on your local machine, and then deploy from that folder. In this case, "deploy" simply means copying from that target folder to the appropriate virtual directory on the Web Server.
Publishing the application prepares it to be copied to the Web Server.
From Visual Studio, click on Build... then Publish Website.
Choose a folder to put the published website. DO NOT select the same folder where your development (source) resides. You will overwrite and lose your source files.
Make sure the option to "Allow this precompiled site to be updateable" is selected (this is a Wings requirement).
Click OK to begin publishing the application.
You now have a folder containing your Wings application. You will copy the contents of this folder (using simple the XCOPY command from the command line or with Windows File Explorer) to the appropriate location your Web Server.
The application is now ready for use.
Note - If you have not already installed and configured IIS and DataGate WebPak on your Web Server, see the
Guide for more details about the Web Server installation and configuration.
If your web server is running Windows Server 2008 R2, follow the Server 2008 Deployment Guide instead.
We previously built and published our Wings 9.0 application on our development PC.
Copy the folder that contains the published Wings application form the development PC to the Web Server.
For this example, we will copy the application files to the
Start the Internet Information Services (IIS) Manager. Expand the server name and right-click on the Application Pools section to create an Application pool for our Wings application.
You can use any name, but we will call this one WingsPool
.NET Framework version: .NET Framework v4.0.30319
Managed pipeline mode: Integrated
Start Application pool immediately: Selected
In IIS Manager, expand Sites. Right-click on Default Web Site. Select Add Application.
The alias name will be part of the URL that you give users to access your Wings Application,
so you will want to make it something easy to reference. We will call ours "
Use the following screenshot as a guide for your application.
Set a default document for your Wings application. If you don't, you will receive an error about directory browsing not being enabled. To set the default document, make sure your Wings application is selected in the IIS Manager and select the Default Document feature.
Click on the Add action and type in the complete default document
name. The default document for our example application is
SignOn.aspx and it is located in the
Monarch folder, so we would enter for our default document: Monarch/Signon.aspx
Click on OK to save the setting.
The specified page should now appear in the list.
When you are done, select the application again (left pane) and click on the browse link to browse the Wings application from the Web Server.
If you still receive an error about directory browsing, you do not have the path/filename of the default document set correctly. Please check the file and path name of the default document and try again.
You can also access the web application from other computers from within the same intranet by typing the IP address of the Web Server (or DNS host name) and path to the application from a web browser. If you are not sure of this information, please check with your IT Network team.
You may remove the 2 test web applications,
wTestApp from web site.
(Right-click on the application name and select Remove. You may also remove the TestPool
application pool in the same manner, and delete the folders that contain the test applications: