Showing results for 
Search instead for 
Do you mean 

Upgrade Apollo 2016.0/2016.1/2016.2 to 2016.3 ( and update ISO metadata for the catalog)

by Technical Evangelist ‎07-25-2017 07:28 AM - edited ‎10-13-2017 07:41 AM (4,397 Views)

 

[0] If upgrading from Apollo 2016.0 to 2016.3 (support Full Motion Video data), user need to install the following features:

 

Windows Server 2012 R2
----------------------

1. Windows Server Essentials Experience role. Add this role to your system using
Windows Server Manager.
2. Windows Server Essentials Media Pack for Windows Server 2012 R2. Download and install from https://www.microsoft.com/en-us/download/details.aspx?id=40837

NOTE: It is not necessary to configure Windows Server Essentials. If Windows warns you or prompts you to configure the Windows Server Essentials Experience role or the Windows Server Essentials Media Pack, you can ignore these warnings and simply take all the defaults when installing these components.


Windows Server 2008 R2
----------------------

1. Desktop Experience feature. Add this feature to your system using Windows Server Manager.
2. Windows Media Services 2008 for Windows Server 2008 R2. Download and install from https://www.microsoft.com/en-us/download/details.aspx?id=20424

 

[1] Make sure Tomcat & Dropbox services setup as automatic, then stop both services


[2] Stop Geospatial Server administrator console Service


[3] Install Apollo data manager 16.3 patch


[4] Install Apollo Server 16.3 patch

 

[4.1] Check time stamp after you installed 16.3

There is a known issue with date timestamp (user will get a lot of 'quartzSchedulerFactory' related error in the Tomcat server log, and user will not be able to login to data manager): Basically user will get this issue when install a major version then immediately apply patches. There's a situation in which some configuration files don't get updated when they should. We've already identified the problem and will fix it in our next release. The problem only happens when the target (non .TEMPLATE) file has a modified date that is newer than the corresponding template file date. If you installed 16.0 when it came out and haven't modified these configuration files since, then the new files in 16.3 will have a newer mod date than the existing 16.0 files. The problem generally happens when you install 16.0 after 16.3 was released, then patch with 16.3. It's also not new to 16.0/16.3, the problem has been around for some time.


After installation, use TotalCommander (File->Change Attributes) to modify date of the following files to be 2015
<APOLLO_INSTALLATION>\config\erdas-apollo\apollo_quartz.properties
<APOLLO_INSTALLATION>\config\erdas-apollo\providers\coverage\providers.fac
<APOLLO_INSTALLATION>\config\erdas-apollo\providers\coverage\decoder.yaml
<APOLLO_INSTALLATION>\config\erdas-apollo\providers\vector\providers.fac
<APOLLO_INSTALLATION>\config\erdas-apollo\metadata\metadata.yaml

Basically the date of above files need to be older than the following *.TEMPLATE files; if above files are older than *.TEMPLATE files, then no need for TotalCommander workflow.
<APOLLO_INSTALLATION>\storage\config_ap_clean\erdas-apollo\apollo_quartz.properties.TEMPLATE
<APOLLO_INSTALLATION>\storage\config_ap_clean\providers\coverage\providers.fac.TEMPLATE
<APOLLO_INSTALLATION>\storage\config_ap_clean\providers\coverage\decoder.yaml.TEMPLATE
<APOLLO_INSTALLATION>\storage\config_ap_clean\providers\vector\providers.fac.TEMPLATE
<APOLLO_INSTALLATION>\storage\config_ap_cleano\metadata\metadata.yaml.TEMPLATE

NOTE: 64bit TotalCommander can be downloaded @ https://www.ghisler.com/amazons3.php

 

        Or

        use the following command line to modify the date for template files. 

 

>forfiles /P "C:\Program Files\Hexagon\ERDAS APOLLO" /M *.TEMPLATE /S /C "cmd /c Copy /B @path+,,"  

 

 



[5] Start Geospatial Server administrator console Service


[6] Configure Apollo. Run C:\Program Files\Hexagon\ERDAS APOLLO\configwizard\.ConfigurationWizard.exe as administrator.


[7] Set Tomcat & Dropbox services setup as manual start, then restart the physical server.


[8] Manually start Tomcat service.


[9] Start Apollo data manager to update ISO Metadata for Apollo catalog

 

Apollo 2016.3 significantly improves to the ISO Metada framework, user can use data manager to update existing ISO metadata to the new framework.
From data manager, go to Catalog->ROOT, and right-click on ROOT to choose "Update ISO Metadata". (see the following screen copy)
From "Update ISO Metadata" dialog, check "For Datasets" and "For Aggregates"
Click OK.

 

Customizing WMTS Tile Matrix Sets.jpg

Comments
by Technical Evangelist
on ‎09-19-2017 05:56 AM

If you didn't do step 4.1 when you install and config Apollo 2016.3, then just do step 4.1 and configure Apollo again.

by
on ‎09-19-2017 07:11 AM

Dears,

 

I found a solution to my problem. Let me share the steps that I executed to solve this.

 

I always follow all Steps that our Engineers recommend... But in this case, the problem occurred in 5 different servers.

 

Yesterday, before I execute a deinstall and install again all components in the APOLLO Server for 2 times, I decided to execute some steps that aren't described.

 

Just for your information, you can see all Steps that I did and now I have APOLLO SERVER 2016 SP3 working very well. Including a problem that I had with IPX now it's ok!

 

  1. I had installed APOLLO 2016 (original version) and before to start to configure the Catalog I've installed SP2.
  2. All steps were followed point by point...
  3. The Server worked very well until the IPX BUG appear...
  4. Following the suggestions of you and our colleagues, I decided to install SP3.
  5. All steps were followed point by point...
  6. The Server didn't work more... Something happened because the Services was invalidated...
  7. I opened the AdminConsole and delete the ApolloCatalogWMS and ApolloCatalogWMSPublic...
  8. I Executed again the Configuration Wizard, but I changed the option that can see in the image below...
  9. After finalized the Configuration Wizard, I restart the Server and it's working!!!

apollo.png

 

My problem was resolved just doing this. I repassed this to our partner in Brazil and the Technical Team executed the same steps and now they have the Apollo 2016 SP3 environment working and update.

 

Let me know if you have some comments... I would like to learn more about this.

 

Thanks
Wolmar

by
on ‎09-20-2017 02:03 PM

This is a guess, but in the past we had problems with installers when a site named 'Default Web Site' did not exist.

Perhaps you could try renaming 'Default Web Site' to 'First Site' and rename site 'Apollo' to 'Default Web Site' then run the installer / config wizard. When complete rename them back. At one stage also had to copy welcome.png and iisstart.htm to the IIS site root folder (that might have been for geospatial though). I've successfully installed EP03 on 4 servers without observing your issue, though I did a full uninstall and then installed 16.0 followed by EP03 so I could change some of the system config.

by
on ‎11-19-2017 10:27 AM

Hi,
we configure ERDAS Apollo in a cluster environment everything was working fine until we install latest release Erdas Apollo 16.3(ep03) it stop catalog web portal and Data Manager as well, after re running Configuration wizard Erdas Apollo Tomcat and Drop Box Services disabled,

Thanks,

 

kashif

Contributors