The Configuration wizard lets you set IIS parameters, define the catalog database connection, define a SMTP server connection, set default locations for user data, and so forth.
After completing the installation procedure outlined above, the Setup Manager shows the Configure option for the server in the Configuration section of the dialog:
From the Setup Manager dialog, click Configure and the ERDAS APOLLO Server Configuration Wizard dialog opens
Click Next and the Install missing features dialog opens. This dialog shows a green check for features that are enabled and a red X beside any features that still need to be installed. Click Configure features if there are any red Xs. Review Before You Install for details on configuring prerequisite components. After configuring, select the missing features click Refresh and the Next button becomes active.
Click Next and the Select web site dialog opens. This dialog may take a few minutes to open since it is gathering information from your system. This shows the web sites defined for your server through IIS. At a minimum you see the "Default Web Site" created when you installed IIS.
Select the web site where ERDAS APOLLO will be installed.
- Configure Web Site for JPIP Compatibility: Sets the website filter to enable JPEG 2000 Interactive Protocol on the server. Should be checked if JPIP capability is specifically needed; JPIP is only useable with JPEG 2000 images and NITF files containing JPEG 2000 code streams. For more information see https://en.wikipedia.org/wiki/JPIP.
- Restrict administration access to localhost connections only: Should be set by default, if unchecked anyone can connect to the Administration Console and possibly change the configuration.
- Disable Rapid Fail Protection: If checked, will allow Microsoft IIS to restart the server, should it crash. Under some circumstances, if ERDAS APOLLO crashes several times in a short window of time, IIS will disable the ERDAS APOLLO service.
- The application pool idle timeout specifies how long a period of inactivity occurs before APOLLO is unloaded.
- The Recycle application pool option specifies how long before the application is shut down and restarted periodically.
Enable Application Pool Memory Limit: If checked, sets the maximum amount of private memory the application can use. If unchecked, memory usage is unlimited.
- The maximum private memory specifies the maximum amount of private memory the application can use.
- Enable CORS: Allows the server to honor the Cross Origin Resource Sharing policy in a web application. For more information, see https://en.wikipedia.org/wiki/Cross-origin_resource_sharing.
- The Access-Control-Allow-Origin header refers to the server(s) that are allowed to access resources (e.g. images in an <IMG> tag in HTML) that are not from the same domain. Examples are “http://www.myserver.com” or “*” if any client can access resources on this server.
- Beginning with APOLLO 2018 Update 3, an updated version of the Tomcat application server is delivered that includes stronger enforcement of CORS security standards, including one that forbids “Origin:” to be set to “*” while “Credentials: true”. As such, it is no longer possible to have credentials enabled and use the wildcard Origin header simultaneously.
Click Next and the Administration Console default site dialog box opens.
Configure the web site where you want to install the Administration Console. The default is Default Web Site. You may also change the application name of the Administration Console.
Click Next and the Select Install Type dialog opens.
To configure a single instance of ERDAS APOLLO, take the default Standalone option. If you are creating a cluster configuration, select New cluster to install to the first node of the cluster, or select Add to existing cluster if you are configuring additional cluster nodes.
Refer to Configuring ERDAS APOLLO in a Cluster to learn more about cluster configuration options.
Click Next to open the Configure Authentication and Authorization dialog.
This page allows you to configure the system used for ERDAS APOLLO authentication. ERDAS APOLLO supports three types of authentication:
- Apollo: this is the standard, built-in authentication system that stores the user info in the ERDAS APOLLO catalog database.
- Windows: this option enables ERDAS APOLLO to delegate authentication to the operating system, using the domain that the server is currently joined to. Users and Roles are defined in the Windows Active Directory domain. Windows authentication also enables automatic login in Data Manager, Geospatial Portal, and to its HTTP APIs (the latter two, only when the web browser/HTTP client supports automatic Windows login through the NTLM or Negotiate protocols).
- LDAP: this option enables ERDAS APOLLO to delegate authentication to an LDAP server. Selecting the LDAP option will enable the Hostname, Port Number, LDAP Bind DN, and LDAP Password fields, which must be filled out for LDAP support. The Bind DN and Password provide basic credentials for accessing your LDAP server. The provided values are the defaults for ApacheDS, your server should require different values. See the product documentation on more details on how to set up your LDAP server for use with ERDAS APOLLO.
The Apollo System Username and Apollo System Password fields allow you to specify the credentials for an existing user that will be used as a "system" user in certain background operations and other processing that requires admin level privileges. Note that you are not setting the password for a user in this step, you are supplying the credentials for an existing user in the chosen authentication system, that has the esp_administrator role.
- For Apollo authentication, this should be the credentials for a user in the ERDAS APOLLO catalog database user store. The values are initialized to the default admin user in a new ERDAS APOLLO installation - admin/apollo123.
- For Windows authentication, this should be the credentials for a user in the Windows domain that the server is joined to, of the form <domain>\<username>.
- For LDAP authentication, this should be the credentials for a user in the LDAP store.
In all cases, the user must have the esp_administrator role and you must supply the credentials every time you run the Configuration Wizard. The values are always initialized to the default admin user credentials, previous entries are not remembered.
Click Next to display the Choose Credentials dialog.
Choose Default if you want to use the default credentials for the account that APOLLO application pools and Windows services will run under.
If you are updating an existing configuration, choosing Current preserves the existing selection.
Current does not refer to the current Windows account that you are using. It is the account currently configured for the APOLLO services.
Choose Custom to enter credentials for the account of your choice. Use this option if you will need to access shared network resources.
The Validate credentials option is available for Custom only and is enabled by default. Un-check the Validate credentials option to disable service account validation during the configuration.
Click Next and the Catalog Database Connection dialog opens.
Configure the connection parameters for the catalog database:
Database type - one of the following:
Oracle: NOTE - Starting with the 2016 release, using Oracle with ERDAS APOLLO requires the Oracle Client and/or ODAC to be installed on the system.
SQL Server: NOTE - Starting with the 2016 release, using SQL Server with ERDAS APOLLO requires the SQL client to be installed on the system.
Use OCI/TNS (Oracle only) - select this option to specify an Oracle TNS name instead of specific database connection information. When this option is selected the only required connection information will be the TNS name/Network alias, username and password.
Server - server where the database is located
If your SQL Server database resides on the same server that ERDAS APOLLO is configured on, you may use the actual server name or (local) – parentheses required. However, if the database resides in the default instance you must specify (local).
Port - listener port number
SID (Oracle only) - name of the database site ID, such as orcl
Service (Oracle only) - name of the database service, such as orcl.mydomain.com.
The Oracle SID and Service name are mutually exclusive. You will only specify one or the other, but never both.
Database name (SQL Server or Postgres) - name of the database
Network Alias (Oracle OCI/TNS only) - the TNS name/Network alias, defined in tnsnames.ora
For ERDAS APOLLO 16.5, ODAC version 188.8.131.52 is required in order to use the OCI/TNS option. When you install ODAC 184.108.40.206, you MUST enable the "Configure ODP.NET and/or Oracle Providers for ASP.NET at machine-wide level" option.
Username - database user name
Password - password for the database user name
Database instance - (optional, for SQL Server Only) the SQL server database instance name
If your database resides in the default instance of SQL Server, leave the Database instance blank. Otherwise use the actual instance name.
Click Next and the wizard verifies the database and the user, and then the HTTP Server Settings dialog opens.
Enter the internet connection information for the server.
Hostname - Name of the computer on which you are installing ERDAS APOLLO Server or the static IP address of that computer.
If you are setting up an internet site or configuring an SSL secured site using a domain level SSL certificate:
- Enter the full domain name, such as www.MyAPOLLO.com.
If you are setting up an Amazon Web Service (AWS) instance:
- Make sure that the AWS instance that is the license server has an elastic IP.
- Set the host name for the ERDAS APOLLO server to the public DNS name of the server.
Protocol - You select the port numbers for HTTP and HTTPS when you set up IIS. Select the protocol and port number for the bindings to use for your internet connection.
See the SSL Configuration section in the ERDAS APOLLO Administrator Guide for details on a SSL connection. This is only available if the selected website has a binding for HTTPS. If it does, then the HTTPS option is selected by default.
Click Next and the WMS Type dialog opens.
Organizations have an option to use the WMS capabilities of Core with data in the ERDAS APOLLO Catalog instead of the legacy WMS found in previous versions. The Core WMS service is faster and more robust than the legacy WMS and in future versions will become the default WMS service in ERDAS APOLLO.
However, with this implementation of the Core WMS in the ERDAS APOLLO Catalog, there are still some limitations on security and data formats supported. When selecting the Core (Limited) option in the Configuration Wizard, the Administrator will see a warning informing them of these current limitations and to review the Server User Guide for more information on the Core WMS.
NOTE: The Configuration Wizard cannot be used again to revert back to the Legacy service at a later time, nor if Legacy is initially selected can the wizard be used to switch to Core. Please review the Core WMS section in the Server User Guide to review how to switch between the services.
Click Next and SMTP Settings dialog opens.
The Simple Mail Transfer Protocol (SMTP) is required to define the location to send e-mails.
Host computer name that will send e-mail
Port SMTP port on the host
Username valid username for the host computer
Password valid password for the username of the host computer
- None - no security
- TLS - Transport Layer Security
- SSL - Secure Sockets Layer (SSL) protocol
Windows Firewall and other antivirus programs may block outgoing e-mail. Add your application server to the list of applications allowed to send e-mail from the server.
Click Next and the Custom Paths dialog opens.
Click the Configure custom locations checkbox to modify any of the default paths. To change a path, click and highlight the row you want to change and then click Browse... to browse to and select a different location for any of the files or the WPS output.
We recommend that you change all of the default paths so that they are not in the default ERDAS APOLLO delivery folder. This ensures that your user data is not deleted when you uninstall older versions of ERDAS APOLLO.
Click Next to display the Usage Database Connection dialog.
Select Enable storing usage information in the database to enable storing usage information from ERDAS APOLLO Core services in the selected database. This information can be stored on the same database as the ERDAS APOLLO Catalog or in a different database.
Click Next to display the OpenStreetMap configuration dialog.
You may elect to use OpenStreetMap as the default provider of background map tiles after reviewing the usage policy. Choose No if you intend to provide your own custom background map for your web portal.
Click Next and the Summary dialog opens.
Review the summary and click Finish when ready.
The Configuring your application dialog opens. The configuration process takes several minutes. Several messages display during configuration.
When the configuration process completes the Finished dialog opens
The Finished dialog indicates the process has completed.
Scroll the list of messages to verify that the configuration completed successfully. A log file notes all the steps taken to configure this instance of ERDAS APOLLO Server. Click Open Log File to view the log.
Click Close to exit. The Setup Manager now shows the Modify, repair, or remove option for the server.
Configure ERDAS APOLLO Server from the Command Line
You may choose to configure your ERDAS APOLLO Server installation using command line options or from a Windows batch file. The executable for the Configuration Wizard is found at ERDAS_APOLLO_HOME/configwizard/ConfigurationWizard.exe. Help for the command is available by running the executable with the --batch --help options.
The following is an example of using ConfigurationWizard.exe from command line.
ConfigurationWizard.exe --batch --installtype standalone --database Postgres:localhost:5432:apollocatalog:dbuser:dbpwd --httpserver "Default Web Site:http:80:myAPOLLOserver" --smtp smtp.myDomain.com:25:None:None --adminconsolevirtualdirectory AdminConsole --adminconsolesite "Default Web Site" --useDefaultOsmTileSource