Geoportal outside the firewall

MikeGregotski · ‎02-10-2011

2011-02-09 13:25:25 CST
Hi,

I have an installation of the Geoportal running within our organization's Intranet. I now want to move it outside our firewall and expose it to a larger Internet audience.

So the plan is to go from: http://machinename/geoportal/catalog/main/home.page

to:

http://externalname.domain.com/geoportal/catalog/main/home.page

From what I can see these are the steps I have to follow once I have secured the external IP address and external name for the server.

1) Allow port 80 to communicate through the firewall (I'm redirecting tomcat so the Web traffic goes through port 80).

2) Update the references in these files:

<Tomcatdir>\webapps\geoportal\WEB-INF\classes\gpt\metadata\cswCapabilities.xml <Tomcatdir>\webapps\geoportal\WEB-INF\classes\gpt\config\gpt.xml

to reflect the new external domain name.

3) Since I'm using some ArcGIS Server services on the machine to work with the geoportal I need to run the post installation and provide the new external domain name.

That should be it. I don't think I need to open ports 10389 for LDAP or 1433 for SQL Server in the firewall but I'm not sure.

Can anyone comment if the steps above are correct or if I have missed anything?

Thanks,
Mike

MikeGregotski · ‎02-17-2011

Hi,

Here is what I did to make this work. I needed to open port 80 in the firewall as suspected but no other ports were required.

Running the ArcGIS Server Post Installation was also needed to change the SOAP references for my existing ArcGIS Server services.

That was it.

My site is up and running now. Take a look at it if you like: http://gptserver.esricanada.com

Mike

JackReed · ‎08-11-2011

I am looking to do the same thing right now but am stuck at updating gpt.xml and cswCapabilities.xml. What specific lines did you edit in these files?

Thanks,
Jack

MikeGregotski · ‎08-11-2011

Hi Jack,

I didn't need to make any changes to the gpt.xml. I did have to make one change to the cswCapabilities.xml file. The line I updated was

<ows:ProviderSite xlink:href="http://site.domain.com"/>

to reflect the new external Website.

Hope this helps.

Mike