The OEDA application server is available for Linux, OSX and Windows.

The Oracle Exadata Deployment Assistant (OEDA) Web browser-based user interface is available starting with the October 2018 OEDA release. The OEDA browser-based interface can import previous OEDA XML configuration files created with the Java-based version of OEDA.

To set up the OEDA application server and start the browser-based user interface, perform the following steps.

1. Download the latest OEDA release from Exadata Database Machine and Exadata Storage Server Supported Versions (My Oracle Support Doc ID KB153930) and copy the archive to the system where you want to run the OEDA application server.

2. On the system where you want to run the OEDA application server, extract the contents of the downloaded compressed file. The extracted contents is written to a directory based on the operating system, such as linux-x64, macosx-x64, or windows-i586. This is referred to as the OEDA_HOME directory.

3. If you are using a version of OEDA released in conjunction with Oracle Exadata System Software release 26.1.0 or later, ensure that any system running OEDA programs contains Java Development Kit (JDK) version 17 or later. You can download a supported JDK from https://www.oracle.com/java/technologies/downloads/.

   Before running any OEDA program, check the following to ensure that the required JDK is installed and available:

   • Ensure that the JAVA_HOME environment variable references the intended JDK.

   • Ensure that JAVA_HOME/bin/java is executable.

   • Run java --version and confirm that the output reports Java version 17 or higher.

4. Launch the OEDA application server (located in the OEDA_HOME directory).

   • On Linux, OSX, and UNIX run:

     installOedaServer.sh [-p port-number] [-g] [-https | -https-keystore keystore-path [-https-password]]

   • On Microsoft Windows run:

     installOedaServer.cmd [-p port-number] [-g] [-https | -https-keystore keystore-path [-https-password]]

   In the command:

   • -p port-number — optionally specifies the port number for the OEDA application server.

     If not specified, the default port number is 7072. However, you can specify any unused port number. It is not recommended to use port numbers less than 1024.

   • -g — optionally specifies that the OEDA application server accepts connections on all available network interfaces.

     If not specified, the OEDA application server only listens on the localhost interface (127.0.0.1).

   Additionally, in versions of OEDA released in conjunction with Oracle Exadata System Software release 26.1.0 or later, the following arguments enable optional support for HTTPS in the OEDA application server.

   • -https — enables HTTPS in the OEDA application server using the self-signed certificate bundled with OEDA.

     The bundled self-signed certificate only supports HTTPS on the localhost interface (127.0.0.1). Therefore, this option cannot be used in conjunction with the -g option.

   • -https-keystore keystore-path — enables HTTPS in the OEDA application server using a user-provided certificate, which is contained in a PKCS12 keystore located at keystore-path.

     A user-provided certificate is required to enable HTTPS support using a specific hostname.

   • -https-password — securely prompts the user to provide the keystore password, if required.

   You can run the installOedaServer program using a non-privileged OS user account. You do not need to be logged in as an OS administrator.

   When you run the installOedaServer program, previous OEDA application server instances are stopped and removed before starting the latest OEDA application server version.

5. Access the OEDA browser-based user interface.

   After you start the OEDA application server, you can access the browser-based interface by opening a browser and entering the following URL:

   http[s]://host-name:port-number/oeda

   In the URL:

   • host-name is the application server host name.

   • port-number is the network port number that you specified when starting the installOedaServer program. For example, 7072.

   If you did not specify the -g option when starting the OEDA application server, then you must run the browser on the same host as the OEDA application server and specify localhost as the application server host name.