POST
|
Tim, You found the right approach to the solution. Geoportal automatically guesses what metadata standard an XML document conforms to. The way it does that is it looks at the metadata profiles registered in schemas.xml. Starting from the first metadata profile registered in schemas.xml and moving sequentially down the list, geoportal then looks at each definition.xml file for a match between the interrogation rule defined in the definition.xml file and the metadata xml. The first match it finds determines what metadata profile geoportal thinks it ought to apply to the metadata xml. Clive
... View more
10-28-2010
05:59 AM
|
0
|
0
|
1
|
POST
|
Hi Agatino, If you are looking for customization advice beyond what is in the link provided above, you might want to consider purchasing a 20-hour Geoportal Technical Support package that can provide you with direct access to one of our developers to give you advice on how to accomplish what you want to do. Feel free to contact me directly. Clive Clive Reece, PhD Professional Services, SDI/Geoportal Solutions Team ESRI | 880 Blue Gentian Road, Suite 200 | Saint Paul, MN 55121 Phone: 651.454.0600 x8376 | Fax: 651.454.0705 Mobile: 651.402.6029 | E-mail: creece@esri.com
... View more
10-28-2010
05:41 AM
|
0
|
0
|
3
|
POST
|
Migrating from a Simple Authentication to LDAP is straightforward (with a small LDAP learning curve if you're not familiar with that). Single-sign on is a different animal. It sounds like you want SSO. I would recommend you have a look at http://help.arcgis.com/en/geoportal_extension/10.0/help/00t0/00t000000037000000.htm . With SSO, there is a lot more configuration needed with regards to your web app server and the SSO provider. Also, by default, geoportal will still need some LDAP mapping for users and groups. If you are considering SSO with an authentication store that does not provide LDAP, then that would require some level of customization.
... View more
10-12-2010
12:16 PM
|
0
|
0
|
3
|
POST
|
np 😄 In a default install, the path to the doc is C:\ESRI\Geoportal Extension 10\Documentation\Installation\Geoportal10_MigrationGuide.pdf
... View more
10-08-2010
08:11 AM
|
0
|
0
|
3
|
POST
|
Kristen, Have you looked through the Geoportal 10 Migration Guide (pdf in the documentation folder)? If not, I recommend that as a good read for understanding your metadata migration options. Clive
... View more
10-08-2010
07:53 AM
|
0
|
0
|
3
|
POST
|
Kristen, You can use the same SQL Server database instance, but you will need to create a new database for use by geoportal 10. If you want to keep your old geoportal database, create the new one with a different name and make sure your JDBC and gpt.xml configuration values point to the right geoportal database.
... View more
10-08-2010
07:13 AM
|
0
|
0
|
3
|
POST
|
By "worked before", do you mean you previously published metadata about 'Desktop\geoportal\geoportal_base.gdb' and 'Desktop\geoportal\Untitled.mxd' successfully before using the current system software configuration? (file names from your log file)
... View more
10-08-2010
06:45 AM
|
0
|
0
|
2
|
POST
|
Sounds like you want to override the ArcGISFilehandler.exe behavior. Not sure if you can point it to a Citrix ArcMap.exe ...
... View more
10-01-2010
07:29 AM
|
0
|
0
|
2
|
POST
|
You've probably already done this, but check (and recheck) all your <ldapAdapter> values in the gpt.xml file. Pay close attention to the roles definition and make sure the groupDN is right: <role key="gptAdministrator" inherits="gptPublisher" groupDN="cn=gpt_admin,ou=Groups,ou=geoportal"/> good luck
... View more
10-01-2010
07:12 AM
|
0
|
0
|
5
|
Online Status |
Offline
|
Date Last Visited |
a week ago
|