POST
|
Thanks for the info. What about the MXD file on our GISServer feeding the outside world? Are the connection configurations stored in the MXD and used for the SDE connection? Thanks again..
... View more
11-17-2014
12:36 PM
|
0
|
1
|
348
|
POST
|
Hello.. We have an SDE database and we're using spatial database connections from within ArcCatalog for the connections; GISViewer, GISEditor, GISOwner. When we created our MXD maps, we used the GISViewer connection within ArcMap to add the different items to the map. Here is our problem, we've forgotten the password for our GISViewer account. The existing connections work, because they're configured for the forgotten password. But we need to document the passwords for auditing purposes. If I change the GISViewer password then re-created a database connection with the new password, would a simple replace of the datasource on the map file work properly? Or is there another step we'll be missing? Thanks..
... View more
11-17-2014
12:17 PM
|
0
|
3
|
2425
|
POST
|
I know this is an old post, but did you find a solution. I have the same question. Cheryl Hello Cheryl, Yes, we were able to get something working properly for a Development/Production environment. Both the production and development databases need to be named the same and thus the features classes for both databases are essentially named the same. SDE_DEV.Roads is different than SDE_PROD.Roads in the eyes of ArcGIS and if you try to change the Data Sources, it won't convert properly and you'd need to edit the production map document to point to the production database feature classes manually. Where-as SDE.Road is the same on both databases in the eyes of ArcGIS and it's the database connection which is used to select between development and production databases. If you only have one SQL database server available for testing, install another SQL instance and use that as a production area. For example, you'd have SDESQLServer as the main SQL instance and then another instance named SDESQLServer/Production as the other instance. Anyway, when you create a map document file, you'll use the development database connection and it's feature classes to create the map. Your database connections can be setup and configured from within ArcCatalog. Once you've finished creating your map document, use ArcCatalog and right-click said map document. There's a Set Data Source(s) option which you need to select; the set data sources window will open. The output file name will automatically be set to "Copy_of_" which is nice so you don't accidentally overwrite the good development map file. You can rename this to something to show you that it's the Production map. Below this, it'll list the data frames, the current data source and the new data source. First click on the Select All button. Then right-click in the blue selected area and select Replace All. The replace all dialog box will open. Change the Replace with: box area with the connection name of your production database connection. For example, the development connection name is Database Connections\SDE_DEV@GISViewer.sde. You'd change this to Database Connections\SDE_PROD@GISViewer.sde. Once you've changed this, click on Replace All; this may take a little while to complete depending on how many layers your map document has. This will change the data sources to your production database connection for all data frames. And since they're named the same by database and feature class name, the conversion will work properly. Click OK to complete this task, save the new map document and you're done. Hope this helps.. -Jeff
... View more
10-23-2012
08:22 AM
|
0
|
0
|
213
|
POST
|
Make sure the ArcGISSOC account has access to the folder the imagery is in. Patrick Yea, since the servers (GIS and server containing orthos share) are member servers of the domain, I had to create and use a domain ArcGISSOC account and grant access. Afterwards, we had no problems. Thanks.. -Jeff
... View more
10-12-2011
10:28 AM
|
0
|
0
|
249
|
POST
|
Hello.. We're in the process of replacing our ArcIMS installation, moving up to GIS Server 10 with the Image Server Extension and SDE. Overall, everything is going well. But, we have something odd. Thus far, we only have our 2010 Orthos and 1990 Orthos Rasters entered into a Mosaic dataset on their own separate SDE databases; no problems. The original 2010 rasters are configured for 6 inches per pixel and the 1990 are 2ft per pixel. I've created a MXD for each of raster sets and have them added as a Map service on our ArcGIS Server. Again, no problems yet. Yet if we view this map service online through the ArcGIS server, once we hit certain zoom levels, we begin seeing different shades of gray footprint boxes where the images should be instead of zooming in and pixalating the images. We'd like the later to occur. Is this a setting within ArcGIS server or the actual Raster dataset which we need to change? If I view the map document within ArcMap, I can zoom into 1:100 or even 1:1 (it isn't too pretty), but it still displays the pixalated images. Thanks.. -Jeff
... View more
10-06-2011
10:51 AM
|
0
|
4
|
858
|
POST
|
Hello.. We have a MXD file which we created for our development side of the house. It's grabbing it's layers from our development SDE server. We'd like to move the map file to the production environment which has it's own SDE box. Is there an easy way to configure the data sources of all the layers in the development map file to point to the production source so it can be used in the production environment? Thanks.. -Jeff
... View more
09-21-2011
11:44 AM
|
0
|
3
|
930
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|