We have ArcGIS Server 10.0 sp1 running on Windows (behavior exhibited in 2003 and 2008x64). The published MXD services have relates established in the MXD to Oracle tables. The tables are access via Oracle authentication. The related tables are not registered in the geodatabase or arcsde. In most cases, the tables are public synonyms of objects in another schema. The relates work fine in ArcMap but do not show up in the REST api once published. No errors or warnings are logged. Relates established to other featureclasses do show up. The behavior seems inconsistent as we have XP workstations with the exact same build of desktop and server which can make a relate to unregistered tables in another Oracle instance. Can anyone provide any insight on whether this is expected behavior? In other words, shouldn't any relationship (explicitly established as a relate in ArcMap) be visible to the REST api as long as there are no permissions issues (which there are not here)?