Hi Pete,
I logged two ArcSDE related bugs, but I don't think either is necessarily
the same as yours.
http://jira.codehaus.org/browse/GEOS-6066
http://jira.codehaus.org/browse/GEOS-6067
So it may be worth reporting yours as well.
Regards,
Jonathan
On 4 October 2013 04:45, von Minden, Peter A (DPIPWE) <
[email protected]> wrote:
> Thanks for having a crack at this one for me Jonathan. I think I have
> run out of options in trying to get a direct connect to ArcSDE. DId you end
> up logging a bug for this?
>
>
>
> Cheers
>
>
>
> Pete
>
>
>
> *From:* Jonathan Moules [mailto:[email protected]]
> *Sent:* Tuesday, 1 October 2013 9:10 PM
> *To:* von Minden, Peter A (DPIPWE)
> *Cc:* [email protected]; Andrea Aime
>
> *Subject:* Re: [Geoserver-users] I need help with an ArcSDE direct
> Connect in Geoserver 2.4.0
>
>
>
> So, after more extensive testing, the only thing I can say is, I'm
> confused. I don't think that wall of connections was actually from the
> direct connect but was an issue from the regular ArcSDE connection I'd
> created.
>
>
>
> ----
>
> So far I've had the following happen:
>
>
>
> a) When I have what I think are the right credentials (as in original
> screenshot), I don't get any error or feedback at all when I press save.
>
>
>
> b) But if I make it "wrong" information (add a typo), then I get an error
> that appears to be the same as yours Peter:
>
>
>
> Error creating data store, check the parameters. Error message: Can't
> create connection to sde:oracle11g:co_gislive for Session #20[SDE error
> -66][Error desc=SPECIFIED PARAMETER VALUE IS INVALID.][Extended desc= ]
>
>
>
> Either way, it completely fails to actually connect as best I can tell.
> But the two different failure modes suggests that maybe your credentials
> are wrong.
>
> Best I can manage I'm afraid. I've never gotten on with ArcSDE. :-)
>
> Regards,
>
> Jonathan
>
> On 1 October 2013 11:38, Jonathan Moules <
> [email protected]> wrote:
>
> Hi Pete,
>
> Well I didn't have the ArcSDE plugin installed, but it was on my todo
> list, so did it anyway.
>
> ArcSDE 9.3.1
>
> GeoServer 2.4.0
>
>
>
> The machine in question already has and ArcGIS install that
> direct-connects installed on it.
>
>
>
> I can get it to do a regular ArcSDE connection just fine, however the
> direct connect isn't working. I enter my credentials, press "Save" and
> nothing happens. I get the little "working" icon for a fraction of a second.
>
> The logs are almost empty - no error:
>
>
>
> 2013-10-01 10:26:06,354 TRACE [org.geotools.arcsde.ArcSDEDataStoreFactory]
> - com.esri.sde.sdk.client.SeConnection is in place.
>
> 2013-10-01 10:26:06,354 TRACE [org.geotools.arcsde.ArcSDEDataStoreFactory]
> - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
>
> 2013-10-01 10:26:06,354 TRACE [org.geotools.arcsde.ArcSDEDataStoreFactory]
> - com.esri.sde.sdk.client.SeConnection is in place.
>
> 2013-10-01 10:26:06,354 TRACE [org.geotools.arcsde.ArcSDEDataStoreFactory]
> - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
>
> 2013-10-01 10:26:06,354 TRACE [org.geotools.arcsde.ArcSDEDataStoreFactory]
> - com.esri.sde.sdk.client.SeConnection is in place.
>
> 2013-10-01 10:26:06,354 TRACE [org.geotools.arcsde.ArcSDEDataStoreFactory]
> - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
>
> 2013-10-01 10:26:06,354 TRACE [org.geotools.arcsde.ArcSDEDataStoreFactory]
> - com.esri.sde.sdk.client.SeConnection is in place.
>
> 2013-10-01 10:26:06,354 TRACE [org.geotools.arcsde.ArcSDEDataStoreFactory]
> - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
>
> 2013-10-01 10:26:06,355 DEBUG [org.geotools.arcsde.session] - populating
> ArcSDE connection pool
>
> 2013-10-01 10:26:06,355 DEBUG [org.geotools.arcsde.session] - Created
> ArcSDE connection pool for ArcSDEConnectionConfig[server=none,
> port=sde:oracle11g:co_gislive, database=none, user=OSMM, minConnections=2,
> maxConnections=6, timeout=500]
>
> 2013-10-01 10:26:06,355 DEBUG [org.geotools.arcsde.session] - Creating
> connection for session #7(try 1 of 3)
>
>
>
> Again, no error at all.
>
>
>
> But if I look in the log again later, it seems something did happen - I
> now have something like:
>
>
>
> 2013-10-01 10:26:06,355 DEBUG [org.geotools.arcsde.session] - Creating
> connection for session #7(try 1 of 3)
>
> 2013-10-01 10:26:34,331 DEBUG [org.geotools.arcsde.data] -
> FeatureTypeCache background process running...
>
> 2013-10-01 10:26:34,331 DEBUG [org.geotools.arcsde.session] - Grabbing
> session from pool on pool-6-thread-1
>
> 2013-10-01 10:26:34,332 DEBUG [org.geotools.arcsde.session] - Got session
> from the pool on pool-6-thread-1
>
> 2013-10-01 10:26:34,332 DEBUG [org.geotools.arcsde.session] - Got session
> from the in use queue on pool-6-thread-1
>
> 2013-10-01 10:26:35,257 TRACE [org.geotools.arcsde.data] - Ignoring non
> registered table MAPINFO.MAPINFO_MAPCATALOG
>
> 2013-10-01 10:26:35,260 TRACE [org.geotools.arcsde.data] - Ignoring non
> registered table OSMM.ADMPFEATURELAYER
>
> 2013-10-01 10:26:35,262 TRACE [org.geotools.arcsde.data] - Ignoring non
> registered table OSMM.ADMPIMPORTSETTINGS
>
> [hundreds of tables]
>
> 2013-10-01 10:26:35,681 TRACE [org.geotools.arcsde.data] - Ignoring non
> registered table WCCDATA.MAIN_SETTL_5KM_SEC_BUFF_WSHIRE
>
> 2013-10-01 10:26:35,684 TRACE [org.geotools.arcsde.data] - Ignoring non
> registered table WCCDATA.MOB_LIB_RTS_2012_WSHIRE_SOL
>
> 2013-10-01 10:26:35,708 TRACE [org.geotools.arcsde.data] - Ignoring non
> registered table WCCDATA.TRAFFIC_REG_ORDS_DATE
>
> 2013-10-01 10:26:35,742 TRACE [org.geotools.arcsde.session] -
> passivating connection Session[4]
>
> 2013-10-01 10:26:35,747 DEBUG [org.geotools.arcsde.data] - Finished
> updated type name cache
>
>
>
>
>
> So it seems to actually connect despite the GeoServer interface failing (a
> bug I'll report in a minute).
>
>
>
> My connection details:
>
>
>
> [image: Inline images 1]
>
>
>
> Despite what the documentation says. My password is only of the form
> "password", not "password@service".
>
>
>
> It also "works" without the extra ":/" in the "port" string.
>
>
>
> Hope that helps,
>
>
>
> Jonathan
>
>
>
> On 30 September 2013 23:17, von Minden, Peter A (DPIPWE) <
> [email protected]> wrote:
>
> Hi All,
>
>
>
> Jonathan is correct. The user name is the database name so I can use it to
> log in via sql developer or sqlplus.
>
>
>
> I can connect directly via ArcGIS and via FME. The string I use in the
> instance section for ArcGIS and for FME is sde:oracle11g:TESTDB.COM.AU,
> which is a little different to the way the Geoserver manual suggests as
> there is the extra ":/". I have tried to use the same instance in Geoserver
> that I use in ArcGIS and FME but still no luck.
>
>
>
> Jonathan, have you managed to do a direct connect to ArcSDE in Geoserver?
> If you have could you send me an example of the credentials you used and
> maybe an example of what you used in ArcGIS so I can see what you do
> differently between the two applications? (Same goes for any of you that
> may have successfully connected via a direct connect)
>
>
>
> Cheers
>
>
>
> Pete
>
>
>
> *From:* Jonathan Moules [mailto:[email protected]]
> *Sent:* Monday, 30 September 2013 8:23 PM
> *To:* Andrea Aime
> *Cc:* von Minden, Peter A (DPIPWE); [email protected]
> *Subject:* Re: [Geoserver-users] I need help with an ArcSDE direct
> Connect in Geoserver 2.4.0
>
>
>
> > * Are the username/password are the same for sde and the database? In
> direct connect the guide says to use the username/password of the
> geodatabase
>
>
>
> I'd be surprised if the passwords are different. SDE just transparently
> passes the credentials straight through to the database; the
> username/password are actually the database ones.
>
>
>
>
>
> Peter - Can you direct connect from ArcGIS to Oracle?
>
>
>
> Jonathan
>
>
>
>
>
>
>
> On 30 September 2013 07:13, Andrea Aime <[email protected]>
> wrote:
>
> On Mon, Sep 30, 2013 at 4:31 AM, von Minden, Peter A (DPIPWE) <
> [email protected]> wrote:
>
>
>
> But a direct connect using the following details does not work:
>
>
>
> *Server name or IP address ** = none, *Port ** =
> sde:oracle11g:/:TESTDB.COM.AU, *Instance name* = none,* User ** =
> test_user, *Password* =* *testPassw0rd
>
>
>
> Hi,
>
> know nothing of direct connect and never tried it but there are a couple
> of things that seem odd/out of place:
>
> * Are the username/password are the same for sde and the database? In
> direct connect the guide says to use the username/password of the
> geodatabase
>
> * The syntax reported by ESRI for direct connect provides a few options
> http://webhelp.esri.com/arcgisserver/9.3/java/index.htm#geodatabases/arcsde-2034353163.htm
> ,
>
> you seem to be going with the schema name one, however, can schema name
> contain dots?
>
>
>
> Cheers
>
> Andrea
>
>
>
> --
>
> ==
>
> Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
> information.
>
> ==
>
>
>
> Ing. Andrea Aime
>
> @geowolf
>
> Technical Lead
>
>
>
> GeoSolutions S.A.S.
>
> Via Poggio alle Viti 1187
>
> 55054 Massarosa (LU)
>
> Italy
>
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob: +39 339 8844549
>
>
>
> http://www.geo-solutions.it
>
> http://twitter.com/geosolutions_it
>
>
>
> -------------------------------------------------------
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
>
> This transmission is intended for the named addressee(s) only and may
> contain sensitive or protectively marked material up to RESTRICTED and
> should be handled accordingly. Unless you are the named addressee (or
> authorised to receive it for the addressee) you may not copy or use it, or
> disclose it to anyone else. If you have received this transmission in error
> please notify the sender immediately. All email traffic sent to or from us,
> including without limitation all GCSX traffic, may be subject to recording
> and/or monitoring in accordance with relevant legislation.
>
>
> ------------------------------
>
>
> CONFIDENTIALITY NOTICE AND DISCLAIMER
> The information in this transmission may be confidential and/or protected
> by legal professional privilege, and is intended only for the person or
> persons to whom it is addressed. If you are not such a person, you are
> warned that any disclosure, copying or dissemination of the information is
> unauthorised. If you have received the transmission in error, please
> immediately contact this office by telephone, fax or email, to inform us of
> the error and to enable arrangements to be made for the destruction of the
> transmission, or its return at our cost. No liability is accepted for any
> unauthorised use of the information contained in this transmission.
>
>
>
>
>
>
> This transmission is intended for the named addressee(s) only and may
> contain sensitive or protectively marked material up to RESTRICTED and
> should be handled accordingly. Unless you are the named addressee (or
> authorised to receive it for the addressee) you may not copy or use it, or
> disclose it to anyone else. If you have received this transmission in error
> please notify the sender immediately. All email traffic sent to or from us,
> including without limitation all GCSX traffic, may be subject to recording
> and/or monitoring in accordance with relevant legislation.
>
> ------------------------------
>
> CONFIDENTIALITY NOTICE AND DISCLAIMER
> The information in this transmission may be confidential and/or protected
> by legal professional privilege, and is intended only for the person or
> persons to whom it is addressed. If you are not such a person, you are
> warned that any disclosure, copying or dissemination of the information is
> unauthorised. If you have received the transmission in error, please
> immediately contact this office by telephone, fax or email, to inform us of
> the error and to enable arrangements to be made for the destruction of the
> transmission, or its return at our cost. No liability is accepted for any
> unauthorised use of the information contained in this transmission.
>
--
This transmission is intended for the named addressee(s) only and may
contain sensitive or protectively marked material up to RESTRICTED and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use it, or
disclose it to anyone else. If you have received this transmission in error
please notify the sender immediately. All email traffic sent to or from us,
including without limitation all GCSX traffic, may be subject to recording
and/or monitoring in accordance with relevant legislation.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
