This is not the old manager application, which is now gone in 9.2
http://localhost:8098/arcimsmanager/main/login.jsf See:
http://webhelp.esri.com/arcims/9.2/general/topics/web_introduction.htm
I 'm not sure what is going on here. Deploying the app places in in the Tomcat localhost folder, instead of the Webapps folder. Thus I can't point the webserver at it with the mod_jk.conf file. I have to connect to it on port 8398.
Saturday, December 9, 2006
Friday, December 8, 2006
Enabling WMS on ArcGIS 9.2
http://forums.esri.com/Thread.asp?c=64&f=784&t=189206#560726
http://forums.esri.com/Thread.asp?c=64&f=784&t=190821#566247
--had to add
JkMount /wmsconnector ajp13
JkMount /wmsconnector/* ajp13
JkMount /wfsconnector ajp13
JkMount /wfsconnector/* ajp13
to mod_jk.conf
Go figure.
Also had to make sureWMSEsrimap_prop had a line exactly like this:
capabilitiesDir=F\:/ArcIMS/capabilities
http://forums.esri.com/Thread.asp?c=64&f=784&t=190821#566247
--had to add
JkMount /wmsconnector ajp13
JkMount /wmsconnector/* ajp13
JkMount /wfsconnector ajp13
JkMount /wfsconnector/* ajp13
to mod_jk.conf
Go figure.
Also had to make sureWMSEsrimap_prop had a line exactly like this:
capabilitiesDir=F\:/ArcIMS/capabilities
Wednesday, December 6, 2006
ArcIMS 9.2 installed on CIRGIS test server
Last night at the Anacapa meeting Wayne Rode and I sat down at the console with Dave Burkhart looking over our shoulders with the new ArcIMS CD.
We uninstalled ArcGIS 9.1, and then ArcIMS 9.1. We also uninstalled the current (5.0) version of the tomcat servlet engine, and installed the version 5.5 recommended by ESRI. Our current Apache version appeared to be OK. After that, we followed an intricate set of instructions that was linked from the ESRI install package for setting up tomcat and Apache with files downloaded from ESRI. After sniffing out a couple of typos, we finally got both Tomcat and Apache working again.
Unfortunately, we couldn't test the servlet engine with the ESRI string, because I had forgotten to install the servelt examples when we did the Tomcat5.5 installation (it defaults to Custom, not typical, and you have to add features). So we decided to proceed with installation anyway, and hope for the best.
We got through the installation (to E:\ -- this creates an e:\arcims folder), but we didn't have the registration code necessary to get through the post installation. So we wrote Steve a note asking him to send along the email from ESRI
------------------
Next day:
With remote desktop, I tried to run the post installation from the start menu item, after receiving the code from Steve. It said, however, that the software must be installed first! So I did a repair, and that didn't help, and then I did a modify, and that didn't help either. So I uninstalled the software and started over, and made sure that I didn't leave the install program before entering the code. Luckily, everything worked after that, and it is all setup the same way as when we had 9.1 running. Even our existing image services came right up. So it's done.
Next step: check that the WMS services are running, too.
We uninstalled ArcGIS 9.1, and then ArcIMS 9.1. We also uninstalled the current (5.0) version of the tomcat servlet engine, and installed the version 5.5 recommended by ESRI. Our current Apache version appeared to be OK. After that, we followed an intricate set of instructions that was linked from the ESRI install package for setting up tomcat and Apache with files downloaded from ESRI. After sniffing out a couple of typos, we finally got both Tomcat and Apache working again.
Unfortunately, we couldn't test the servlet engine with the ESRI string, because I had forgotten to install the servelt examples when we did the Tomcat5.5 installation (it defaults to Custom, not typical, and you have to add features). So we decided to proceed with installation anyway, and hope for the best.
We got through the installation (to E:\ -- this creates an e:\arcims folder), but we didn't have the registration code necessary to get through the post installation. So we wrote Steve a note asking him to send along the email from ESRI
------------------
Next day:
With remote desktop, I tried to run the post installation from the start menu item, after receiving the code from Steve. It said, however, that the software must be installed first! So I did a repair, and that didn't help, and then I did a modify, and that didn't help either. So I uninstalled the software and started over, and made sure that I didn't leave the install program before entering the code. Luckily, everything worked after that, and it is all setup the same way as when we had 9.1 running. Even our existing image services came right up. So it's done.
Next step: check that the WMS services are running, too.
CIRGIS2 Temporarily moved to Geosciences workroom
Last night we moved the new CIRGIS2 server out of the closet in Rm 113 because it was too hot and the fans were running at high speed. There was also a problem with unstable local network connections, whcih I suspect might have been caused by the heat.
I talked to Jim Mayer about putting it back into the closet once he has rigged up an exhaust fan, but for now it is sitting next to Anacapa and CIRGIS1. It has the same functional connections as before--a local gigbit crossover cable to CIRGIS1's 2nd NIC only.
I talked to Jim Mayer about putting it back into the closet once he has rigged up an exhaust fan, but for now it is sitting next to Anacapa and CIRGIS1. It has the same functional connections as before--a local gigbit crossover cable to CIRGIS1's 2nd NIC only.
Tuesday, November 28, 2006
SQL Server 2005 installed on CIRGIS2
In preparation for the installation of ArcSDE 9.2 Enterprise, I've installed and SP'd SQL Server 2005 Workgroup Edition (supported for Enterprise). I patched the machine with Windows Update (53!) after adding SQL Server SP1.
I grabbed IP 207.233.107.43 to talk to windows update, but there is a second, local gigabit connection to CIRGIS1 that I installed last night with a gigabit card and a crossover cable. That's intended to be the way that CIRGIS1 and CIRGIS2 talk in the future when CIRGIS1 makes a data request.
We might consider a dbo account instead of an SDE account for 9.2--see
http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=An_overview_of_ArcSDE_geodatabase_administration
Next steps: add more user accounts, antivirus software, and wait for the SDE 9.2 box while we pile up data.
I grabbed IP 207.233.107.43 to talk to windows update, but there is a second, local gigabit connection to CIRGIS1 that I installed last night with a gigabit card and a crossover cable. That's intended to be the way that CIRGIS1 and CIRGIS2 talk in the future when CIRGIS1 makes a data request.
We might consider a dbo account instead of an SDE account for 9.2--see
http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=An_overview_of_ArcSDE_geodatabase_administration
Next steps: add more user accounts, antivirus software, and wait for the SDE 9.2 box while we pile up data.
CIRGIS2 is up!
Last night I successfully loaded Windows 2003 Server R2. Turns out there was a CD in the Dell box that contained the drivers for the RAID array, and walked me through the installation of the OS.
I put the OS in a 20 GB C: partition, and I intend to use the rest of the 476GB mirrored array as an E: partition for programs and swap space. I'll make the ~2TB RAID5 container drive F: for data (which will be mostly SQL server, if we use SDE), and the solo disk as drive T:, for temp data and the tempdb.
I put the OS in a 20 GB C: partition, and I intend to use the rest of the 476GB mirrored array as an E: partition for programs and swap space. I'll make the ~2TB RAID5 container drive F: for data (which will be mostly SQL server, if we use SDE), and the solo disk as drive T:, for temp data and the tempdb.
Subscribe to:
Posts (Atom)