Let’s suppose you install ArcGIS Server on machine “foobar1″ and it serves out tiles from http://foobar1/arcgisoutput/.
Secondly, you have a subdomain that points to this machine and you want ArcGIS server to respond accordingly:
gisstuff.example.net --> ROUTES TO ------------> foorbar1 ArcGIS Server ---------> STILL RESPONDS WITH --> foorbar1 ???
Here, the ArcGIS website is getting requests through the subdomain. (Your router takes care of that) However, the ArcGIS HTTP responses do not point to the right address. They are still pointing to the machine itself without “knowing” of the router’s configuration.
http://foobar1/arcgisoutput/ --> IS RETURNED, INSTEAD OF --> http://gisstuff.example.com/arcgisoutput/
For this problem, (or any other reason you need to control the response URLs) look in ArcGIS Server’s configuration file at \server\system\Server.dat (Windows OS)
The Server.dat file maintains the server’s properties. The server object manager (SOM) reads the contents of this file at its startup and is configured accordingly … Be sure to restart the SOM service after editing this file.
For more info, see the web help HERE and HERE. There’s a lot you can configure with ArcGIS Server, you just have to know where to go. Good luck!
The ArcGIS Viewer for Silverlight 1.0 was released yesterday for public download. For details on what’s been added since the last release (beta 2), check out the What’s New topics on Esri’s website.
Here’s a Smart Pen demonstration for collecting field data. This is a custom app we designed for a specific utility data workflow, but the application is readily configurable to use in other industries.
It’s official, the time has come: Adobe announced this week that Flash Player is dead for mobile devices and the related Flex SDK is being released to the open source community.1
This is good news for proponents of open standards and HTML5. The company announced they are going to “aggressively contribute to HTML5″ as they believe it is the “best technology for enterprise application development”.
This is the message we started seeing after an ArcMap crash today.
Warning: Can't edit versioned workspace, check that you have proper permissions on the version.
I’m sure there’s more than one trigger for it, but in our case, ArcMap did not release a table from ArcSDE load only mode. We verified this with the following SQL statement; it prints all the Oracle tables in load only mode:
-- Lists all Oracle tables that are in load only modeSELECT a.owner OWNER,
a.TABLE_NAMETABLE_NAMEFROM sde.table_registry a,
sde.layers b
WHERE BITAND(b.eflags,1074790400)=1074790400AND a.owner = b.owner
AND a.TABLE_NAME= b.TABLE_NAME;
Once you know which tables are in load only mode, use sdelayer on the command line to change them. You can also use sdelayer to get the current mode of a table (in lieu of the SQL above).
REM Describe the current mode for a featureclass/tableREM See http://help.arcgis.com/en/geodatabase/10.0/admin_cmds/support_files/datamgmt/sdelayer.htm
sdelayer -o describe -l {owner.featureclass,shape} -u myUserName -p myPassword
REM Change the mode for a featureclass/table.
sdelayer -o {load_only_io | normal_io} -l owner.featureclass,shape -u myUserName -p myPassword
1. Motivate: Design your site to meet specific user needs and goals. Use motivators to draw different user “personae” into specific parts of your site.
2. User task flow: Who are your users? What are their tasks and online environment? For a site to be usable, page flow must match workflow.
3. Architecture – it’s 80% of usability, Build an efficient navigational structure. Remember – if they can’t find it in 3 clicks, they’re gone.
4. Affordance means obvious: Make controls understandable. Avoid confusion between emblems, banners, and buttons.
5. Replicate: Why reinvent the wheel? Use ergonomically designed templates for the most common 8-12 pages.
6. Usability test along the way: Test early in design using low-fidelity prototypes. Don’t wait until the end when it’s too late. Know the technology limitations Identify and optimize for target browsers and user hardware. Test HTML, JavaScript, etc. for compatibility.
7. Know the technology limitations: Identify and optimize for target browsers and user hardware.Test HTML, JavaScript, etc for compatibility.
8. Know user tolerances: Users are impatient. Design for a 2-10 second maximum download. Reuse header graphics so they can load from cache. Avoid excessive scrolling.
9. Multimedia – be discriminating: Good animation attracts attention to specific information, then stops. Too much movement distracts, slowing reading and comprehension.
10. Use a stats package: Monitor traffic through your site. Which pages offend user interest? Which pages make users leave? Adjust your site accordingly.
It’s official, the time has come: Adobe announced this week that Flash Player is dead for mobile devices and the related Flex SDK is being released to the open source community.
