Following the installation guide, I tried to download and install the Experience Services SDK using package share.
However, I always get an error page. After clicking the Package Share link, the browser hangs for some minutes, the present the following error page:
Trying to login using this "local" login page doesn't work.
In the server log, I found this kind of stack traces:
28.09.2011 18:09:02 *ERROR* PackageShareServlet: Adobe Package Share server not available (connection refused) (PackageShareServlet.java, line 306)
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
at com.day.crx.packaging.impl.EasySSLProtocolSocketFactory.createSocket( EasySSLProtocolSocketFactory.java:179)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java :707)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$Http ConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Htt pMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMe thodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.jav a:397)
at com.day.crx.packaging.impl.proxy.ProxyImpl.doGet(ProxyImpl.java:552)
at com.day.crx.packaging.impl.PackageShareServlet.doLogin(PackageShareSe rvlet.java:294)
at com.day.crx.packaging.impl.PackageShareServlet.doGet(PackageShareServ let.java:114)
at com.day.crx.j2ee.CRXHttpServlet.doGet(CRXHttpServlet.java:112)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at com.day.crx.j2ee.CRXHttpServlet.service(CRXHttpServlet.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at com.day.j2ee.servletengine.ServletRuntimeEnvironment.service(ServletR untimeEnvironment.java:228)
at com.day.j2ee.servletengine.RequestDispatcherImpl.doFilter(RequestDisp atcherImpl.java:315)
at com.day.j2ee.servletengine.RequestDispatcherImpl.service(RequestDispa tcherImpl.java:334)
at com.day.j2ee.servletengine.RequestDispatcherImpl.service(RequestDispa tcherImpl.java:378)
at com.day.j2ee.servletengine.ServletHandlerImpl.execute(ServletHandlerI mpl.java:346)
at com.day.j2ee.servletengine.HttpListener$Worker.run(HttpListener.java: 610)
at java.lang.Thread.run(Unknown Source)
Note that I use a proxy to access the internet, and I already configured it using the configuration console of the Experience Server, in the "Day Commons HTTP Client 3.1" as suggested in the Day documentation here http://dev.day.com/content/docs/en/cq/current/administering/package_ma nager.html#Package%20Share%20Account
How can I verify that the Package Share server provided by Adobe is actually alive? Is there any other configuration required in order for the package share to work? Can I find the required SDKs to create ADEP Experience Services applications in Flash Builder elsewhere?
Thank you
Cosma Colanicchia
I tried for two days, then I gave up because I managed to found a web access to the adobe package share on the following address:
http://dev.day.com/packageshare/landing/packageshare_trial.html
So I downloaded the required bundles and manually uploaded and installed it in my local quickstart instance.
The quickstart version, by the way, should be the 10.0 (looking at the jar filename), build 186 (crx.quickstart.build.number=186 in quickstart.properties file).
Browser is Google Chrome, but I also tried with Firefox without success. In my opinion, it looks like a proxy issue: maybe the proxy settings managed by Day Commons HTTP Client 3.1 (as I explained in my first post) are not being applied?
Looking at the issues, this was probably due to a temporary Package Share unavailability, as we had some issues a few weeks ago with our server.
Accessing Package Share from ADEP, there are 2 possible login screens:
(a) Package Share login screen
This comes from Package Share server and means the server is up, running and accessible (eventually behind well configured proxy).
(b) Product login screen
This screen is displayed after a connection to Package Share server timed out (not accessible) or was refused (bad proxy configuration).
North America
Europe, Middle East and Africa
Asia Pacific