# iNomads

Setup and Installation |

## Supported Web Servers

iNomads requires the use of a Web server to process end user requests and to send HTML documents. Any of the following Web servers can be used:

> PxPlus EZWeb Server
> Apache HTTP Server
> IIS ASP.NET Setup

See Frequently Asked Questions for answers to some commonly asked questions about iNomads.

#### Note:
For the purposes of this documentation, the assumption is that PxPlus has been properly installed onto your computer system.

## License Requirements

iNomads requires a supported PxPlus Web license. The user count on the license will control the number of concurrent sessions that can be run.

If using the PxPlus Web Server, you will need a Web license. No additional license is needed if using the Apache Web Server.

Demo License

For the purposes of demonstration and initial testing, the single user Demo license can be used.

## Configuring PxPlus Pathnames

PxPlus pathnames are defined using Configuration Maintenance, which is accessed from the iNomads Setup window.

To invoke the iNomads Setup window, use one of the following methods:

Location | Method
From the PxPlus IDE Main Launcher | Expand the Web Deployment category and select iNomads Setup.
From the PxPlus Command prompt | Enter the following command: RUN "*plus/inomads/admin"

The steps for defining PxPlus pathnames are:

| 1. | From the iNomads Setup window, select the Config button to invoke Configuration Maintenance.
| 2. | Select the Pathnames tab. For the Pathname to PxPlus executable and System library directory fields, enter the full pathname as shown below:
| 3. | Click OK to apply the changes and close Configuration Maintenance. The inomads.conf file will be configured to run your test.

#### Note:
If you are using EZWeb Server, setting the pathname is not necessary.

## Testing the Configuration

Once you have the Web Server configured and running, you can test the setup using a browser.

Authorization Message

If the system is not iNomads enabled, a message box will be displayed.

This message is displayed once every hour as a new session is launched. Click the OK button and resubmit your request, which will take you to the normal Demo iNomads Application Launchpad.

This message will not be displayed on a fully activated iNomads license.

iNomads Application Launchpad

You can select any of the pre-configured transactions from the system, or enter the Panel name, Library and working Directory of the NOMADS panel you want to run. See iNomads Application Launchpad.

## Launch Port

By default, when running iNomads programs, the Web server process itself launches the applications. This means that the application will need to be able to run on the same machine under the same user ID and same authorization levels associated with the Web server.

If desired, the PxPlus Simple Client Server can be used in conjunction with iNomads to launch the application processes. You can set the Launch_Port variable within the iNomads configuration to contain the IP address (name or direct address in the form xxx.xxx.xxx.xxx), followed by a ; (semi-colon) and the port address used by the Simple Client Server host (default 4093). When a process is launched, the request will be forwarded to the Client Server host, which can be on a different server and/or running a different user with different authentication rights.

See Running iNomads Application on a Separate Server.

When using IIS or Apache with iNomads, the pathnames must also be defined. See Configuring PxPlus Pathnames above.

If you want the system to only use the Remote process Launch_Port for access, set the Single_Port variable (available only with Apache and EZWeb Server, not with IIS).

(The Single_Port variable was added in PxPlus 2018.)

## Popup Blockers

One problem you may encounter in running iNomads is popup blockers. By default, iNomads launches new windows as popups, which are often blocked either internally by the browser or by a toolbar plug in such as the Google or Yahoo toolbar.

If iNomads is denied a request to create a new window, it will display an alert message box and wait for you to disable the blocker. Depending on the blocker, when you disable the blocking, the transaction may proceed as usual or get re-initialized.

For information on setting up your own transactions and system defaults, see Running Your Application.

## Character Sets

iNomads supports mixed character sets between the server process and the Web pages with on-the-fly character set translation. On the Misc tab of Configuration Maintenance, the following two Character set options are available: Character set to use on Web pages and Character set to use internally in application.

These can be set to any combination of UTF-8 or ISO-8859-1 (Windows standard). Changing the Character set to use on Web pages option requires that you restart the Web server being used.

#### Note:
If the internal character set is set to UTF-8, then the system parameter 'U8' is enabled. In addition, if the system parameter 'U8' is set during the iNomads start_up, then the internal character set will be set to UTF-8 regardless of what the configuration states.

## System HTML Messages

iNomads stores system error messages as internal HTML files in the syshtml directory (*plus/inomads). By specifying "blank" as the On Exit URL, the system will display the contents in sys_blank.htm. If "close" is specified as the On Exit URL, the system will display the contents in sys_close.htm. Both of these HTML files are in the syshtml directory.

You can also customize the system-loaded error message displayed in iNomads. This is done first by tailoring the contents in *plus/inomads/syshtml/sys_loaded.htm as desired and then setting the On Exit URL to "loaded" to have the system display the custom message.

(Support for customizing the system-loaded message was added in PxPlus 2020.)