11 Replies Latest reply on Apr 15, 2013 11:50 AM by 1001931

    Issues viewing the published site on the delivery system

    997874
      Hi Guys,
      Ive setup the management system which has a user interface,
      and the delivery system which does not have a user interface but i read on the install guide
      that delivery system does not have user interface? How true is that?

      Next I published avisports (RealTime Comlete Publish) and fisrtsiteII (real time mirror to server)
      changed the preview url from the management system to have ip and port for delivery, but to my suprise
      no site visible...Y?
      I get broswer error : HTTP Status 404 - Content Server could not process the request

      type Status report

      message Content Server could not process the request

      description The requested resource is not available.

      Apache Tomcat/6.0.36

      #####################################
      Sites Log:
      [2013-04-03 01:03:33,468 SAST] [ERROR] [http-7100-6] [logging.cs.satellite.request] Error accessing the external page with pmd: page: ?c=Page&childpagename=FirstSiteII/FSIILayout&cid=1118867611403&pagename=FSIIPreviewWrapper&rendermode=preview
      [2013-04-03 01:03:33,468 SAST] [ERROR] [http-7100-6] [fatwire.logging.cs.request] COM.FutureTense.Common.ContentServerException: ContentServerException: (Client error (HTTP status code: 404) fetching data through Remote Satellite Server) Error code:PAGE NOT FOUND

      Please assist thank you.
        • 1. Re: Issues viewing the published site on the delivery system
          Rodney-Oracle
          Hi,
          I assume you're running Sites 11gR1. It is indeed true that the contributor user interface is not deployed when a server is setup in Delivery Mode. The reason is security and second is that new content should never be created in the delivery environment directly. However a lightweight admin UI is deployed on the delivery system for admin purposes like cache information, log configuration etc.

          Before you publish when ever you created a new publish destination, did you initialize the publish destination accordingly? Did you follow the steps as stated in the admin guide? pg. 314 - Moving a Site to a Delivery System (http://docs.oracle.com/cd/E29495_01/doc.1111/webcenter_sites_11gr1_bp1_admin.pdf)

          Please note that the static files, like CSS etc needs to be moved manually as those are not published. This is the way the sample sites are designed. Only content Assets are published. They are located in: webapps/cs/avisports and webapps/cs/FirstSiteII

          Hope this info is useful to you.

          Regards,
          Rodney
          • 2. Re: Issues viewing the published site on the delivery system
            997874
            Thanks Rodney for the infor

            But i'm unable to locate the webapps/cs/avisports and webapps/cs/FirstSiteII folders.
            And the publication to the delivery system ran successfully.

            Regards
            • 3. Re: Issues viewing the published site on the delivery system
              Rodney-Oracle
              The cs/avisports and cs/FirstSiteII folders are located in the deploy directory of the application server. Let me know which app server you are using.
              You mentioned your site was successfully published did the site render accordingly on the delivery system?
              • 4. Re: Issues viewing the published site on the delivery system
                997874
                No it didnt render correctly.
                I'm using apache-tomcat-6.0.36.
                Published the avisports sites.

                thanks
                • 5. Re: Issues viewing the published site on the delivery system
                  Rodney-Oracle
                  If its tomcat, the location of the avisports stylesheets and supporting images are located in <tomcat directory>/webapps/cs/avisports. This directory needs to be copied to your delivery system in the same location.

                  Cheers,
                  Rodney
                  • 6. Re: Issues viewing the published site on the delivery system
                    997874
                    I've copied it to the delivery system but I'm still having the 404 error on the site.log file
                    when i direct to the avisports pagename url.
                    • 7. Re: Issues viewing the published site on the delivery system
                      Rodney-Oracle
                      Can you paste the log entry and what is the url that you access?
                      • 8. Re: Issues viewing the published site on the delivery system
                        997874
                        Hi Rodney,

                        please find below the log from the csHome install dir from today this is after I try to direct to url http://192.254.43.167:7100/cs/Satellite?pagename=avisports:

                        [2013-04-04 17:18:58,523 SAST] [INFO ] [      main] [fatwire.logging.cs.event] CSShutdownListener is initialized
                        [2013-04-04 17:18:58,685 SAST] [INFO ] [      main] [springframework.context.support.ClassPathXmlApplicationContext] Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@395d601f: display name [org.springframework.context.support.ClassPathXmlApplicationContext@395d601f]; startup date [Thu Apr 04 17:18:58 SAST 2013]; root of context hierarchy
                        [2013-04-04 17:18:58,913 SAST] [INFO ] [      main] [beans.factory.xml.XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [SSOConfig.xml]
                        [2013-04-04 17:18:59,551 SAST] [INFO ] [      main] [springframework.context.support.ClassPathXmlApplicationContext] Bean factory for application context [org.springframework.context.support.ClassPathXmlApplicationContext@395d601f]: org.springframework.beans.factory.support.DefaultListableBeanFactory@2f6b904d
                        [2013-04-04 17:18:59,610 SAST] [INFO ] [      main] [beans.factory.support.DefaultListableBeanFactory] Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@2f6b904d: defining beans [ssoprovider,ssofilter,ssolistener,auxlistener,ssoconfig]; root of factory hierarchy
                        [2013-04-04 17:19:33,679 SAST] [INFO ] [      main] [springframework.context.support.ClassPathXmlApplicationContext] Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@54c9f997: display name [org.springframework.context.support.ClassPathXmlApplicationContext@54c9f997]; startup date [Thu Apr 04 17:19:33 SAST 2013]; root of context hierarchy
                        [2013-04-04 17:19:33,680 SAST] [INFO ] [      main] [beans.factory.xml.XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [SitesSecurityContext.xml]
                        [2013-04-04 17:19:33,738 SAST] [INFO ] [      main] [beans.factory.xml.XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [ReqAuthConfig.xml]
                        [2013-04-04 17:19:33,773 SAST] [INFO ] [      main] [springframework.context.support.ClassPathXmlApplicationContext] Bean factory for application context [org.springframework.context.support.ClassPathXmlApplicationContext@54c9f997]: org.springframework.beans.factory.support.DefaultListableBeanFactory@7cbdb375
                        [2013-04-04 17:19:33,782 SAST] [INFO ] [      main] [beans.factory.support.DefaultListableBeanFactory] Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@7cbdb375: defining beans [cryptoPackage,securityConfig,tokenPackage,securityContext,reqAuthConfig]; root of factory hierarchy
                        [2013-04-04 17:19:34,381 SAST] [INFO ] [      main] [fatwire.logging.cs.filelock] ftFileLock using nio file locking
                        [2013-04-04 17:19:38,604 SAST] [INFO ] [      main] [beans.factory.xml.XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [BufferingConfig.xml]
                        [2013-04-04 17:19:46,146 SAST] [INFO ] [      main] [beans.factory.xml.XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [RestResources.xml]
                        [2013-04-04 17:19:46,176 SAST] [INFO ] [      main] [beans.factory.xml.XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [custom/RestResources.xml]
                        [2013-04-04 17:19:48,722 SAST] [INFO ] [      main] [logging.cs.satellite.host] Remote Host: http://localhost:80
                        [2013-04-04 17:19:48,743 SAST] [INFO ] [      main] [fatwire.logging.cs.satellite] Satellite Server running in stand-alone mode
                        [2013-04-04 17:19:48,859 SAST] [INFO ] [      main] [fatwire.logging.cs.satellite] Starting scratch cleaner with: 120 second(s) heart beat for temp folder :/u01/apache-tomcat-6.0.36/work/Catalina/localhost/cs/sscache/scratch/
                        [2013-04-04 17:19:48,861 SAST] [INFO ] [      main] [fatwire.logging.cs.satellite] Satellite Server servlet bootup complete
                        [2013-04-04 17:19:48,867 SAST] [INFO ] [      main] [logging.cs.satellite.host] Remote Host: http://localhost:80
                        [2013-04-04 17:19:48,868 SAST] [INFO ] [      main] [fatwire.logging.cs.satellite] Satellite Server running in stand-alone mode
                        [2013-04-04 17:19:48,868 SAST] [INFO ] [      main] [fatwire.logging.cs.satellite] Satellite Server servlet bootup complete
                        [2013-04-04 17:19:48,871 SAST] [INFO ] [      main] [logging.cs.satellite.host] Remote Host: http://localhost:80
                        [2013-04-04 17:19:48,872 SAST] [INFO ] [      main] [fatwire.logging.cs.satellite] Satellite Server running in stand-alone mode
                        [2013-04-04 17:19:48,872 SAST] [INFO ] [      main] [fatwire.logging.cs.satellite] Satellite Server servlet bootup complete
                        [2013-04-04 17:20:58,578 SAST] [ERROR] [http-7100-1] [logging.cs.satellite.request] Error accessing the external page with pmd: page: ?pagename=avisports
                        [2013-04-04 17:20:58,593 SAST] [ERROR] [http-7100-1] [fatwire.logging.cs.request] COM.FutureTense.Common.ContentServerException: ContentServerException: (Fetch failed for page: ?pagename=avisports) Error code:REMOTE SATELLITE SERVER CONNECTOR ERROR
                        COM.FutureTense.Common.ContentServerException: ContentServerException: (Fetch failed for page: ?pagename=avisports) Error code:REMOTE SATELLITE SERVER CONNECTOR ERROR
                             at com.openmarket.Satellite.RemoteContentServerEh.fetchCacheObject(RemoteContentServerEh.java:319)
                             at com.openmarket.Satellite.AbstractContentServer$CacheObjectFetchFunction.doWork(AbstractContentServer.java:413)
                             at com.openmarket.Satellite.AbstractContentServer.getCacheObject(AbstractContentServer.java:220)
                             at com.openmarket.Satellite.AbstractContentServerEh.getCacheObject(AbstractContentServerEh.java:168)
                             at com.openmarket.Satellite.RemoteContentServerEh.getCacheObject(RemoteContentServerEh.java:35)
                             at com.openmarket.Satellite.SatelliteServer.execute(SatelliteServer.java:83)
                             at com.openmarket.Satellite.servlet.BaseServlet.doGet(BaseServlet.java:121)
                             at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
                             at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
                             at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
                             at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                             at com.fatwire.auth.RequestAuthenticationFilter.doFilter(RequestAuthenticationFilter.java:192)
                             at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
                             at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                             at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:695)
                             at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)
                             at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
                             at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                             at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
                             at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
                             at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
                             at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
                             at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
                             at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
                             at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
                             at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
                             at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
                             at java.lang.Thread.run(Unknown Source)
                        Caused by: com.fatwire.cs.core.http.HttpAccessException: org.apache.http.conn.HttpHostConnectException: Connection to http://localhost:80 refused
                             at com.fatwire.cs.core.http.HttpAccess.execute(HttpAccess.java:367)
                             at com.openmarket.Satellite.RemoteContentServerEh.fetchCacheObject(RemoteContentServerEh.java:226)
                             ... 27 more
                        Caused by: org.apache.http.conn.HttpHostConnectException: Connection to http://localhost:80 refused
                             at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:158)
                             at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)
                             at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
                             at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573)
                             at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425)
                             at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
                             at com.fatwire.cs.core.http.HttpAccess.execute(HttpAccess.java:552)
                             at com.fatwire.cs.core.http.HttpAccess.execute(HttpAccess.java:343)
                             ... 28 more
                        Caused by: java.net.ConnectException: Connection refused
                             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 org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
                             at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)
                             ... 35 more
                        • 9. Re: Issues viewing the published site on the delivery system
                          Rodney-Oracle
                          Hi,
                          The URL you use to access the site homepage is not correct. The standard URL in Sites exists out of min 3 params:
                          pagename, c, cid where pagename is the template name which is usually preceded by the site name, where c is the asset type and where cid is the asset id.

                          So your URL should look like:

                          http://192.254.43.167:7100/cs/Satellite?pagename=avisports/[template name]&c=Page&cid=[id of that page asset]

                          The easiest way to get he url is to login into the Contributor UI, inspect the home page asset, preview the page in new window, copy the url and replace the ip address and port number to the one of your delivery environment.

                          If you want to have search engine friendly urls, you might want to check the developers guide about URLAssemblers.

                          Hope this helps.

                          Rodney
                          • 10. Re: Issues viewing the published site on the delivery system
                            997874
                            Hi,

                            I've tried followed your steps I get HTTP Status 500 - Content Server error

                            Regards
                            • 11. Re: Issues viewing the published site on the delivery system
                              1001931
                              Hi
                              Could you try with the contentserver servlet on live system?
                              Did you check the site entry parameter if you use cselement + sitentry?