Data Portal installation and configuration steps

1.	The network configuration ( Firebird server installation or SQL Express or SQL Server) must be performed before following the Data Portal configuration steps.

2.	Confirm that you can connect to the networked AyaNova database from a local networked connected computer

3.	Server where the Data Portal will be installed has IIS installed before the steps below

Server where the Data Portal will be installed has confirmed that AyaNova runs successfully on it, and connects to the networked database (i.e. the Data Portal can be installed on the same server where the database actually resides, OR it can be installed to another computer that can access the AyaNova database through a networked config.txt)

5.	Your router/firewall has a static external IP address (you can not use a dynamic IP address as that means it constantly changes, and therefore your remote users won't be able to connect as won't know what IP address to use)

6.	Your router/firewall configured for port forwarding for the IIS computer.

7.	High-speed internet / network connection between remote user and network where database resides

1.	First the installation and configuration of the Data Portal itself

2.	And second the configuration of the remote station to connect to the Data Portal

B. Confirm that your router/firewall is configured to forward port to the database server where the Data Portal will be set up

•	Refer to your firewall documentation for setting up forwarding as every firewall is different and we would not be able to put here examples of every type available.

•	in our example screenshot - the database server’s internal IP address is 192.168.1.100 and the forwarding port we have set is 6969

•	Do not hesitate to contact a networking professional if you have any doubts about firewall configuration

•	In our example, we have the TCP Port as 6969 because as the above example, we have want to have remote users forwarded to port 6969 onto the server.

D. Run the AyaNovaSetup.exe installation again on this same server where you have already configured network AyaNova use and select the network administrator setup

•

As you will be selecting the Network administrator setup to install the Data Portal, run the AyaNovaSetup.exe file from the same folder where you placed the copy of your networked edited config.txt file as per step #7 of your AyaNova networking steps - as it will expect to find a copy of the config.txt file in the same folder.

•	If you run the AyaNovaSetup.exe file from a folder where a copy of your config.txt file is not located, you will get the following message. Just click on Ignore.

G. During the installation it will notify you that it created the virtual directory AyaNovaDP from C:\Program Files\Ground Zero Tech-Works Inc\AyaNova

H. If during the installation, it sees that there already is a config.txt file and will ask you if you want to overwrite it - click NO

•	You do NOT want to overwrite your config.txt file because it is already configured to point to your networked AyaNova database

NOTE: if you get a message such as below about replacing a file, this is occurring because you have something running. Click Abort, and then check to make sure you do NOT have the AyaNova program running, nor QBI or PTI or any of the import/export utilities, and check Services to make sure that the AyaNova Generator is shut off while installing. Then run the installation again.

I. After installation has completed, open the IIS Manager and confirm that AyaNovaDP is present

J. There is no editing of the web.config file because AyaNovaDP uses the same config.txt that the AyaNova program uses to connect to the networked database.

K. Confirm that AyaNovaDP web site is using Microsoft.NET Framework 3.5 (or higher).

NOTE: As Microsoft.NET Framework 3.5 is actually just a further update of 2, you will note that the ASP.NET version will show as 2.0.50727. Make sure this is selected and then your computer will know to use the latest 3.5 that is installed on it.

M. Test the connection via the data portal by opening Internet Explorer on this server where you have just performed the steps above, and typing in the URL where XXXX is the port number of your Default Web Site

•	When using Internet Explorer, you will and you do want to see similar to below:

•	If you see similar to the screenshot above, then continue to the next step. If not, recheck all of your steps from the start.

•	Note that not all web browsers for example such as Google Chrome may not show the above unless you select its Control the current page -> Developer -> View source; and Opera won't show anything at all. Use Internet Explorer to perform this step.

N. Data Portal is now installed and confirmed working at the server, you are now ready for the remote computer configuration

O. The following are additional rights settings you may want to set so that external users can not view the contents of the config.txt file

P. If installing the Data Portal onto a Vista or higher computer, do note the following 2 additional steps:

a. Go to Programs -> Features -> Turn Windows Features On or Off -> under Internet Information Services -> IIS 6 Management Compatibility, make sure all are check-marked.

2. Set the Application Pool for AyaNova Data Portal 5 to use the Classic .NET AppPool (the screenshot below shows doing this to AyaNovaWBI5, but do the same for the AyaNovaDP site)

NOTE: If on your server you can not use a web site off of Default Web Site as per the steps above, you can manually create a new virtual web site pointing to the AyaNova folder.

2.	In IIS Manager, delete the installed web site AyaNovaDP under Default Web Site (this should not remove the installed files)

3.	In IIS Manager, create a new web site pointing to the C:\Program Files\Ground Zero Tech-Works Inc\AyaNova folder with its own port #

•	The web site access permissions must be at minimum Read, Run scripts and Execute

•	Make sure .NET 2 is selected in the ASP.NET tab for this new site

•	You may or may not have to set the IP Address property of your new website to the computer's actual internal ip address instead of (All Unassigned)

As the site is not under Default Web Site, note of course that the URL for step #13 above would be http://localhost:xxxx/DataPortal.rem?wsdl where xxxx is the port number you gave when you manually created the site. (or use xxx.xxx.xxx.xxx:XXXX where xxx.xxx.xxx.xxx is the server's internal IP address)

a. on a networked computer within the local area network, open a web browser and enter in the local ip of the server, the port number for the dataportal etc as below

for example, if the local ip of the dataportal server was 192.168.1.100; and the port number you set for it was 6969, you would enter in:

•	if you do not see as above, that means either one or more of the following is a problem and you need to recheck your steps:

•	you did not enter in the correct local ip of the data portal server

b. once you have confirmed connectivity from within the local area network, then continue

a. on a remote computer connected to the Internet, open a web browser and enter in the public external ip of the router/firewall, the port number for the dataportal etc as below

for example, if the external public ip of your router is 222.333.66.23; and the port number you set for it was 6969, you would enter in:

•	if you do not see as above, that means either one or more of the following is a problem and you need to recheck your steps:

•	the router/firewall may not be configured for port forwarding correctly - recheck your router/firewall help

•	you did not enter in the correct local ip of the data portal server

b. once you have confirmed connectivity from outside of the local area network, then continue

a. Move to the C:\Program Files\Ground Zero Tech-Works Inc\AyaNova/examples folder on your Data Portal server

b. Make a copy of the EXAMPLE_DATAPORTALconfig.txt file and rename that copy to config.txt

•	Edit the example IP Address with the router's external IP address and the port number (that you configured in step 1 for your router/firewall that is the same in the Default Web Site and also performed in the step B.b above)

•	For example, if your router's public IP address is 222.333.111.6, and the port your Default web site is using is 6969 (which is also the same port you configured in the router/firewall and for AyaNovaDP), that config.txt would look like

d. Make that config.txt file accessible to your remote user - either give that config.txt file to your remote user by email or put it on a disk, etc) and have them save to a folder on their local hard drive

e. Have your remote user download the AyaNovaSetup.exe installation file and save to their local hard drive into that same folder

•	For example, the C:\Temp folder will now have both the AyaNovaSetup.exe file and the special edited config.txt file.

f. Have that remote user run the AyaNovaSetup.exe file from that folder location that also has the edited config.txt in that same shared location.

The AyaNovaSetup.exe will "see" that config.txt file in the same folder and automatically copy it to that computer's AyaNova program directory so no additional configuration is needed on that user's station.

The install will only install the AyaNova program files it has been told to install, will copy that config.txt file to the remote user's local hard drive workstations AyaNova program folder and will not install a trial database.

The AyaNova installation will place a desktop icon for AyaNova on the desktop as well as in the start menu.

If an issue with the Data Portal, you first need to confirm at what point an issue first occurs. This means the first thing you do is re-check every step.

If continue to experience an issue, check the AyaNova Support Forum for a solution similar to your issue

If continue to experience an issue, either post the following on the AyaNova Support Forum or send via direct email to AyaNova support:

•	Identify the issue you are having and what step it relates to - provide details of what exactly was done, possibly screenshots etc of the issue

•	Confirm each step performed in its order, and each step has been taken up to the point of the issue providing details on each of those steps

•	If issue in remote computer configuration, identify step at and config.txt with that step along with confirmation of testing steps done previously to that point