------------PostgreSQL 9.0.12 Based APOLLO 2013 Installation (64bit only)------------

Notice that Apollo 2013 drop support for 32bit OS, so Apollo 2013 only work for 64bit OS.

Windows 2008 R2 64bit

Where is the installation guide?

Click “Installation Guide” link will open the pdf file.

PostgreSQL Installation

Download

We don't support PostGIS2.0, (only support PostGIS 1.5), because PostGIS 2.0 is not compatible with some Apollo 2013 library. PostgreSQL 9.2 64bit will use PostGIS 2.0, which is not supported.

Please use “Version 9.0.12”, Win x86-32.

Install PostgreSQL 9.0.12- √

Password = leica.201212

Make sure to choose “Spatial Extensions->PostGIS 1.5 for PostgreSQL 9.0 (32bit) v1.5.5”

NOTE, if you only have PostGIS 2.0 option, no PostGIS 1.5, then you must use PostgreSQL 9.2 64bit installer.

Install PostGIS extension 1.5.5 - √

Password = leica.201212

Create Login Role for Apollo 2013 - √

Start the pgAdmin III from “Start->Programs->PostgreSQL 8.3->pgAdmin III”.Create Login role:

Right-click on the “Login Roles”, and choose “New login role...”From Properties Tab:Role Name = This is the role you will give your schemaPassword = give a passwordRole Privileges = make sure at least grant “Can create database objects” privilege.

EAIM_2010/leicaorEAIM_2011/leicaorEAIM_2013/leica

Click OK, now you should have the new login role “EAIM_2013”:

NOTE: the username (rolename) is case sensitive in PostgreSQL.

Create User Database for APOLLO 2013 - √

Start the pgAdmin III from “Start->Programs->PostgreSQL 8.3->pgAdmin III”.You should have 3 databases created for you. We need to create a new database so that this database is where the EAS/EAIM catalog table will be stored

Create database for EAS/EAIM 2013:Right click on the Database, and choose “New Database...”

From Properties Tab:Name = This is the database name you want to access it as (For example, EAIM_Catalog)Owner = Leave the owner as "EAIM_2013" Template = Make sure to use "template_postgis" to enable Spatial support. If you leave this empty (by default), then the created database is not Spatial database.

NOTE: Choose owner as “postgres” if multiple users are going to be connecting to the database

From Privileges Tab:Make sure you add the users you want to be able to access. At least Create, Temp and Connect privileges are required for EAIM

Click OK to create the new database:

Create Schema for Apollo 2013 (Optional)

Create New Schema for database “EAIM_CATALOG”:Right click on “Database->EAIM_CATALOG”, and choose “New Schema”:

From Properties Tab:Name = This is the name for your schemaOwner = choose “EAIM_2013” login role you just created

Click OK, Now you should have your new Schema “EAIM_2013”:

Config PostGIS database - √

This step is optional if you use “localhost” for DB during Apollo configuration.

[1] Allow remote IP address to access PostgreSQLEdit <POSTGRES_HOME>/data/pg_hba.conf to give access:

C:\Program Files\PostgreSQL\8.3\data\pg_hba.conf

# IPv4 local connections:host all all 127.0.0.1/32 md5# IPv6 local connections:#host all all ::1/128 md5

change to:

host all all 0.0.0.0/0 md5

NOTE: for IPV6 address, you need to add your IPV6 addresshost all all fe80::xxxx:xxxx:xxxx:xxxx/128 md5Or

host all all ::0/0 md5

[2] Allow communication over TCP/IP from All addressesEdit <POSTGRES_HOME>/data/postgresql.conf

C:\Program Files\PostgreSQL\8.3\data\postgresql.conf

#listen_addresses = 'localhost' # what IP address(es) to listen on;change to:listen_addresses = '*'

[3] Restart PostgreSQL service

Pre-requisites:

Enable IIS 7.5

Enable IIS 7.5 (installed by Windows 2008 R2 by default).Here is how to enable IIS 7.5 on your Windows 2008 R2 64bit[1]Click Start, point to Administrative Tools and then click Server Manager.[2]In Roles Summary, click Add Roles.[3]Use the Add Roles Wizard to add the “Web server (IIS)” role & “Application Server” role.

After installation, you should see the following messages:

Also, for good measure, before you install APOLLO the first time, you should open a command prompt, Run as Administrator, and go to …Windows\Microsoft.NET\Framework64\v4.# and run the command “aspnet_regiis –i” to register ASP.NET with IIS.

Add Windows Features (Windows 2008 R2 64bit)

From your windows 2008 R2, go to

Click to launch “Server Manager”

From Features, click “Add Features”

Make sure you have the following features checked* .NET Framework 3.5.1* Message Queuing Activation (at least you need “Message Queuing Servers->Message Queuing Server”)

Add Windows Roles (Windows 2008 R2 64bit)

From your windows 2008 R2, go to

Click to launch “Server Manager”

Click “Roles”, and then click “Add Roles Services”Make sure you have the following roles installed.

* Static Content* ISAPI Extensions* ISAPI Filters* IIS 6 Management Compatibility (all children options)* ASP.NET* Basic Authentication * Windows Authentication* Management Tools (installed) : (all children options)* WCF-HTTP-Activation

Update Windows .NET 4.0

Since ERDAS Foundation 2013 requires .NET 4.0, so install .NET 4.0Download the web installer from Microsoft website.

Install Foundation 2013

You need to install Founcation 2013, because Apollo may need to use the Global datum to do ortho resampling.Plus the Foundation 2013 also install licensing tool automatically.

Install License

Make sure you have valid liense.Once you installed the Foundation, you can launch the program from Start->All programs->Intergraph Licensing <version>->Intergraph License Administration. Once the license tool is opened, you can go to “File->Import License file” to load the license.

APOLLO Advantage/Professional 2013 Installation

Installation APOLLO Server

NOTE: APOLLO 2013 stop supporting 32bit system, you will get the following error message if you are trying to install APOLLO 2013 on 32bit OS.

IIS configuration

Right click on the C:\Intergraph folder, and choose “properties”, then click on “Security” tab.

Click “Edit” button to add new User/Groups, add the following 3 user/groups:Authenticated Users, IIS_IUSRS, Users @ your local machine (Not domain)

Make sure “Full control” is assigned to these 3 user/groups, and then click “Apply”.

Configure Apollo Server

After you finish “IIS Configuration”, now you can continue to “Configure” Apollo server.

For second time installation, you will see the following dialog

If you don't use localhost, use the servername, and then you may have the following error.

Sometimes, postgresql will have some problem if you are using the server hostname.You need to modify C:\Program Files (x86)\PostgreSQL\8.4\data\pg_hba.conf, so that the IPV6 address is added. See previous “PostgreSQL Installation->Config PostGIS database”

YOU will get the above error if you type the wrong username or password. Remember username and password is case senstive in PostgreSQL.

The information is read from IIS, so that you can not change anything here!If in IIS you have more than one bindings, then these bindings will also show up at this moment.

Here is the new one:

smtp.intergraph.comport 25, and there is no user name and password.

NOTE: log file is located @ C:\Intergraph\ERDAS APOLLO\configwizard\log.txt

Install Apollo Data manager

Restart your server

In order to make IIS work, you need to restart your server.

Test - data manager √

The default admin account is:Uesr = admin Pass = apollo123

Note: GeoServices is for ESRI ArcServer.

Test - Web Client √

Go to http://SERVERNAME/erdas-apollo/welcome/en/index.html

Click the “The ERDAS Apollo Geospatial Portal” will connect you to the web client. Beware that new web portal is slower than the old web client (2011).

Go to “Authentication” tab, and type your login account (admin/apollo123) if you want to connect to the Apollo catalog.

Click the “Browse ERDAS APOLLO Catalog”, you will see the APOLLO catalog.

Admin Console

Go to http://Server/erdas-apollo/, and click “The Geospatial Server Administration Console” link.

If your computer is on the domain, then use your domain login (domin\user)If your computer is not on the domain, then use local computer login (hostname\user)

For some reason, if the actual service is not started, you need to start the service.

Once the “Geospatial Server Administration Console Service” is started, you can see your instances from the admin console page.