| Oracle® Retail Predictive Application Server Installation Guide Release 14.1.2 E70811-01 |
|
 Previous |
 Next |
| Oracle® Retail Predictive Application Server Installation Guide Release 14.1.2 E70811-01 |
|
Previous |
Next |
The RPAS Classic Client can be installed through either of the following methods:
The following sections describe the installation processes for these two methods.
This section describes the installation of the RPAS Classic Client on Windows machines, and describes how to configure the client to connect to a domain.
Perform the following procedure to make the RPAS Classic Client available.
Create a directory on the network from where users will install the RPAS Classic Client.
The location and the name of the directory are up to the system administrator's preferences. This directory is henceforth referred to as the [RPASCLIENT] directory.
Extract the client from the ARPOPlatform-14.1.2.clients.zip included in the main package to the [RPASCLIENT] directory.
The RPAS Classic Client installation procedure is the same for all of the RPAS applications. Perform the following procedures to install the application onto a PC.
Run the setup.exe file located in the [RPASCLIENT] directory on the network.
The welcome page displays. Follow the installation procedures as prompted.
The setup program exits after the installation is complete.
After creating an RPAS domain and starting the DomainDaemon (refer to the Classic Client or Fusion Client version of the Oracle Retail Predictive Application Server Administration Guide.), you must configure the RPAS Classic Client to connect to the domain on a server. This section provides instructions for configuring the RPAS Classic Client on a local computer using a Microsoft Windows operating system.
EConfigure is a Windows application that configures the client-server communication for RPAS. EConfigure lets you specify communication parameters and produces a file that is used as input to the client. These files must be in FCF (Foundation Configuration File) format/extension. The files contain the necessary information for the client to start up the communication with the server. These files can be stored on the client machine or on the network.
When the client is run, a file named Foundation.FCF is expected in the same directory. If the file has a different name or if it is stored somewhere on the network, the path to this file must be passed in as an argument to the client.
EConfigure consists of a menu bar, a main view, and the advanced settings dialog box. Passwords saved in the FCF file are encrypted. To launch EConfigure, double-click the EConfigure.exe file, which is by default located in the root directory of the RPAS Classic Client.
The files produced by EConfigure may contain multiple connections. Each connection will be specific for a server with certain communication settings. Connections need to have unique descriptions, and they can be added and deleted using the menu bar.
The main view has the basic connection parameters. On this view, three groups of controls are available:
The connection group
The domains group
The Advanced Settings dialog
The connection group has these fields:
| Field | Description |
|---|---|
| Database Server | The hostname or the IP address of the server, for example, atldev03 or 10.2.1.23. This value should be localhost when running the RPAS Server on a Windows machine. |
| Daemon Port | The port number on which the domain daemon is listening. This must be an integer between 1025 and 65535 (for example, 55278). |
The domains group has these fields:
| Field | Description |
|---|---|
| Domain | The name of the domain that is displayed to the user when logging in. Select a domain from the list or type the name of a new domain and click Add Domain. You can delete a domain from the list by selecting it and then clicking Delete Domain. |
| Domain Path | The full path to the directory containing the domain, for example, /root/testenv/domain/Sample_Project. |
| User | Provide the user ID if you do not want to force the user to provide it when logging in. The user ID must be defined in the associated domain. |
| Password | Provide the password for the user if you do not want to force the user to provide it when logging in. This password must match the password defined in the domain for the associated user. |
The Advanced Settings Dialog has these fields for the default database login:
| Field | Description |
|---|---|
| User | The database user that is used by the client if a domain specific user has not been entered, for example, adm. |
| Password | Like the default database user, default database password is used if a domain specific password has not been entered, for example, adm. |
| Database Port Range | Port range is used to specify the range of ports on which the RPAS Server processes is started by the DomainDaemon (the rpasDbServer processes). The port Start and port End fields are the lower and upper limits of this range respectively.
These fields must be integers between 1025 and 65535, which are also the default values if values are not specified, for example, Start: 40000, End: 45000. |
| Compression Threshold | The number of bytes above which client and server are using compression. Only advanced users should manipulate this number. |
| Web Tunneling | The configuration of Web tunneling is no longer supported. |
| Proxy Settings | The configuration of the RPAS Classic Client to support a proxy server is not completed in this utility. |
For instructions on Classic Client web deployment for patch installations, refer to Chapter 7, "RPAS Classic Client Web Deployment". If the web environment needs to upgrade, the web deployment instructions for full installations and patch installations are the same. If the web environment is unchanged, install the new WAR file after the same preparation.
