Differences

This shows you the differences between two versions of the page.

--- docpublic:systemes:esup:esup_socle_4_c7 [2016/05/25 13:25]
procacci@tem-tsp.eu [pb demarrage postgres]
+++ docpublic:systemes:esup:esup_socle_4_c7 [2016/05/27 13:14] (current)
procacci@tem-tsp.eu [parametrage]
@@ Line 4691: / Line 4691: @@
 </code>
-==== esup-filemanager ====
+===== esup-filemanager 3 =====
+https://www.esup-portail.org/wiki/display/PROJCANSTOCK/Esup+File+Manager
+on va utiliser git pour recuperer le source
+<code>
+[esup@esup4dz ~/portlet]
+$ git clone https://github.com/EsupPortail/esup-filemanager.git
+Cloning into 'esup-filemanager'...
+remote: Counting objects: 5383, done.
+remote: Total 5383 (delta 0), reused 0 (delta 0), pack-reused 5383
+Receiving objects: 100% (5383/5383), 1.89 MiB | 1.18 MiB/s, done.
+Resolving deltas: 100% (1908/1908), done.
+[esup@esup4dz ~/portlet]
+$ cd esup-filemanager/
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ ls
+LICENSE  NOTICE  pom.xml  src
+</code>
+visualisation de l'existant
+<code>
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ git config --global color.ui auto
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ git branch -a
+* master
+  remotes/origin/HEAD -> origin/master
+  remotes/origin/esup-filemanager-portlet_1_0
+  remotes/origin/master
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ git remote -v
+origin	https://github.com/EsupPortail/esup-filemanager.git (fetch)
+origin	https://github.com/EsupPortail/esup-filemanager.git (push)
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ tig
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ git tag
+esup-filemanager-2.1.0
+esup-filemanager-2.2.0
+esup-filemanager-2.2.1
+esup-filemanager-2.2.2
+esup-filemanager-3.0.0
+esup-filemanager-3.1.0
+</code>
+on se met le dernier tag/release plutot que de rester sur les "nigthly build" (cf tig)
+et on met notre propre branche .
+<code>
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ git checkout -b esup-filemanager-3.1.0-tem-tsp esup-filemanager-3.1.0
+Switched to a new branch 'esup-filemanager-3.1.0-tem-tsp'
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ git branch
+* esup-filemanager-3.1.0-tem-tsp
+  master
+</code>
+==== test localhost avec pluto =====
+pluto container de portlet (tomcat container de servlet ...) permet de tester la portlet simplement
+on lance la portlet dans la container pluto
+<code>
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ mvn clean portlet-prototyping:run
+[INFO] Scanning for projects...
+Downloading: http://repo.jlehtinen.net/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.5.1/maven-compiler-plugin-2.5.1.pom
+May 26, 2016 12:05:06 PM org.apache.pluto.driver.PortalStartupListener contextInitialized
+INFO: Starting up Pluto Portal Driver. . .
+May 26, 2016 12:05:06 PM org.springframework.web.context.ContextLoader initWebApplicationContext
+INFO: Root WebApplicationContext: initialization started
+May 26, 2016 12:05:06 PM org.mortbay.log.Slf4jLog info
+INFO: Loading Spring root WebApplicationContext
+May 26, 2016 12:05:06 PM org.springframework.core.CollectionFactory <clinit>
+INFO: JDK 1.4+ collections available
+May 26, 2016 12:05:06 PM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
+INFO: Loading XML bean definitions from ServletContext resource [/WEB-INF/pluto-portal-driver-services-config.xml]
+May 26, 2016 12:05:06 PM org.springframework.context.support.AbstractRefreshableApplicationContext refreshBeanFactory
+INFO: Bean factory for application context [Root WebApplicationContext]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [PortletContainer,PlutoServices,PortalDriverServices,PortalContext,DriverConfiguration,AdminConfiguration,ResourceConfigFactory,PortalURLParser,RenderConfigService,SupportedModesService,SupportedWindowStatesService,PortletRequestContextService,EventCoordinationService,FilterManagerService,PortletURLListenerService,PortletContextService,RequestDispatcherService]; root of BeanFactory hierarchy
+May 26, 2016 12:05:06 PM org.springframework.context.support.AbstractApplicationContext refresh
+INFO: 17 beans defined in application context [Root WebApplicationContext]
+May 26, 2016 12:05:06 PM org.springframework.context.support.AbstractApplicationContext initMessageSource
+INFO: Unable to locate MessageSource with name 'messageSource': using default [org.springframework.context.support.DelegatingMessageSource@a54379e]
+May 26, 2016 12:05:06 PM org.springframework.context.support.AbstractApplicationContext initApplicationEventMulticaster
+INFO: Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster@7b93bc9d]
+May 26, 2016 12:05:06 PM org.springframework.ui.context.support.UiApplicationContextUtils initThemeSource
+INFO: Unable to locate ThemeSource with name 'themeSource': using default [org.springframework.ui.context.support.ResourceBundleThemeSource@65ad7f3f]
+May 26, 2016 12:05:06 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
+INFO: Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [PortletContainer,PlutoServices,PortalDriverServices,PortalContext,DriverConfiguration,AdminConfiguration,ResourceConfigFactory,PortalURLParser,RenderConfigService,SupportedModesService,SupportedWindowStatesService,PortletRequestContextService,EventCoordinationService,FilterManagerService,PortletURLListenerService,PortletContextService,RequestDispatcherService]; root of BeanFactory hierarchy]
+May 26, 2016 12:05:06 PM net.jlehtinen.portlet.prototyping.portal.PortletPrototypingRenderConfigServiceImpl addPortletPrototypingPage
+INFO: Configuring Pluto portal for portlet prototyping
+May 26, 2016 12:05:06 PM net.jlehtinen.portlet.prototyping.portal.PortletPrototypingRenderConfigServiceImpl addPortletPrototypingPage
+INFO: Portlet context path = /esup-filemanager
+May 26, 2016 12:05:06 PM net.jlehtinen.portlet.prototyping.portal.PortletPrototypingRenderConfigServiceImpl addPortletPrototypingPage
+INFO: Portlet names = esup-filemanager
+May 26, 2016 12:05:06 PM net.jlehtinen.portlet.prototyping.portal.PortletPrototypingRenderConfigServiceImpl addPortletPrototypingPage
+INFO: Configured 1 portlets
+May 26, 2016 12:05:06 PM org.apache.pluto.container.impl.PortletContainerImpl infoWithName
+INFO: Portlet Container [pluto-portal-driver]: Container initialized successfully.
+May 26, 2016 12:05:06 PM org.springframework.web.context.ContextLoader initWebApplicationContext
+INFO: Using context class [org.springframework.web.context.support.XmlWebApplicationContext] for root WebApplicationContext
+May 26, 2016 12:05:06 PM org.springframework.web.context.ContextLoader initWebApplicationContext
+INFO: Root WebApplicationContext: initialization completed in 408 ms
+May 26, 2016 12:05:06 PM org.apache.pluto.driver.PortalStartupListener contextInitialized
+INFO: Initializing Portlet Container. . .
+May 26, 2016 12:05:06 PM org.apache.pluto.driver.PortalStartupListener contextInitialized
+INFO: Pluto portlet container started.
+May 26, 2016 12:05:06 PM org.apache.pluto.driver.PortalStartupListener contextInitialized
+INFO: ********** Pluto Portal Driver Started **********
+May 26, 2016 12:05:06 PM org.mortbay.log.Slf4jLog info
+INFO: Started SelectChannelConnector@0.0.0.0:8080
+[INFO] Started Jetty Server
+May 26, 2016 12:05:07 PM org.apache.pluto.driver.container.PortletContextManager fireRegistered
+INFO: Portlet Context '/pluto' registered.
+May 26, 2016 12:05:07 PM org.apache.pluto.driver.container.PortletContextManager register
+INFO: Registered portlet application for context '/pluto'
+May 26, 2016 12:05:07 PM org.apache.pluto.driver.container.PortletContextManager register
+INFO: Registering 3 portlets for context //pluto
+May 26, 2016 12:05:07 PM org.apache.pluto.driver.container.PortletContextManager register
+INFO: Portlet application for context '/pluto' already registered.
+May 26, 2016 12:05:07 PM org.apache.pluto.driver.container.PortletContextManager register
+INFO: Portlet application for context '/pluto' already registered.
+May 26, 2016 12:05:16 PM org.apache.pluto.driver.container.PortletContextManager fireRegistered
+INFO: Portlet Context '/esup-filemanager' registered.
+May 26, 2016 12:05:16 PM org.apache.pluto.driver.container.PortletContextManager register
+INFO: Registered portlet application for context '/esup-filemanager'
+May 26, 2016 12:05:16 PM org.apache.pluto.driver.container.PortletContextManager register
+INFO: Registering 1 portlets for context //esup-filemanager
+May 26, 2016 12:05:16 PM org.mortbay.log.Slf4jLog info
+INFO: Initializing Spring FrameworkPortlet 'esup-filemanager'
+</code>
+c'est accessible via localhost:8080/ (mais si tomcat tourne conflit de port => arreter tomcat )
+on peux aussi y acceder sur le FQDN http://esup4dz.tem-tsp.eu:8080/pluto/portal
+ne pas tenir compte du "404" (pas de context par defaut, il liste les 2 ) il suffit de cliquer sur le 2eme lien /pluto
+<code>
+Error 404 - Not Found.
+No context on this server matched or handled this request.
+Contexts known to this server are:
+    /esup-filemanager ---> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@3605ce8f{/esup-filemanager,/home/esup/portlet/esup-filemanager/src/main/webapp}
+    /pluto ---> org.mortbay.jetty.webapp.WebAppContext@7a3fafbd{/pluto,/home/esup/.m2/repository/net/jlehtinen/portlet/portlet-prototyping-portal/0.9/portlet-prototyping-portal-0.9.war}
+    </code>
+==== parametrage =====
+definir le serveur cas
+<code>
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ vim ./src/main/webapp/WEB-INF/web.xml
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ cp ./src/main/webapp/WEB-INF/web.xml ./src/main/webapp/WEB-INF/web.xml.orig
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ vim ./src/main/webapp/WEB-INF/web.xml
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ diff -ur ./src/main/webapp/WEB-INF/web.xml ./src/main/webapp/WEB-INF/web.xml.orig
+--- ./src/main/webapp/WEB-INF/web.xml	2016-05-26 17:16:18.430542157 +0200
++++ ./src/main/webapp/WEB-INF/web.xml.orig	2016-05-26 17:15:44.944549896 +0200
+@@ -80,7 +80,7 @@
+         <servlet-class>edu.yale.its.tp.cas.proxy.ProxyTicketReceptor</servlet-class>
+         <init-param>
+             <param-name>edu.yale.its.tp.cas.proxyUrl</param-name>
+-            <param-value>https://cas16.tem-tsp.eu/proxy</param-value>
++            <param-value>https://cas.mon-univ.fr/proxy</param-value>
+         </init-param>
+     </servlet>
+</code>
+definir les drives que l'on vaux afficher dans le filemanager
+<code>
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ cp ./src/main/webapp/WEB-INF/context/drives.xml ./src/main/webapp/WEB-INF/context/drives.xml.orig
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ vim ./src/main/webapp/WEB-INF/context/drives.xml
+</code>
+=== compilation ===
+<code>
+[esup@esup4dz ~/portlet/esup-filemanager]
+$ mvn clean package
+[INFO] Scanning for projects...
+[INFO]
+[INFO] ------------------------------------------------------------------------
+[INFO] Building esup-filemanager 3.1.0
+[INFO] ------------------------------------------------------------------------
+Downloading: http://repo.jlehtinen.net/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.10/maven-surefire-plugin-2.10.pom
+...
+[INFO] Exploding webapp...
+[INFO] Assembling webapp esup-filemanager in /home/esup/portlet/esup-filemanager/target/esup-filemanager
+[INFO] Copy webapp webResources to /home/esup/portlet/esup-filemanager/target/esup-filemanager
+[INFO] Generating war /home/esup/portlet/esup-filemanager/target/esup-filemanager.war
+[INFO] Building war: /home/esup/portlet/esup-filemanager/target/esup-filemanager.war
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESS
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 12.007s
+[INFO] Finished at: Thu May 26 17:25:41 CEST 2016
+[INFO] Final Memory: 20M/309M
+[INFO] ------------------------------------------------------------------------
+</code>
+=== deploiement ===
+ant deployPortletApp => ajoute dans le web.xml le fait que c'est le portail qui va lancer cette portlet (via pluto) et pousse le .war dans webapps .
+le deploy se fait depuis la racine des sources du portail
+<code>
+[esup@esup4dz ~/esup-uportal]
+$ cd /home/esup/esup-uportal
+</code>
+puis deploy via ant deployPortletApp
+<code>
+[esup@esup4dz ~/esup-uportal]
+$ ant deployPortletApp -DportletApp=/home/esup/portlet/esup-filemanager/target/esup-filemanager.war
+Buildfile: /home/esup/esup-uportal/build.xml
+checkForTomcat:
+deployPortletApp:
+install-parent-pom:
+[artifact:install] [INFO] Installing /home/esup/esup-uportal/pom.xml to /home/esup/.m2/repository/org/jasig/portal/uportal-parent/4.0.16-SNAPSHOT/uportal-parent-4.0.16-SNAPSHOT.pom
+    [touch] Creating /home/esup/esup-uportal/target/tmp/uportal-parent.pom-41461427-marker
+     [echo] Artifact '/home/esup/esup-uportal/bootstrap/pluto-assembler/target/pluto-assembler-4.0.16-SNAPSHOT.jar' is not available or out-of-date, calling 'mvn install'
+mvn:
+     [exec] [INFO] Scanning for projects...
+     [exec] [INFO]
+     [exec] [INFO] ------------------------------------------------------------------------
+     [exec] [INFO] Building Bootstrap - Pluto Assembler Dependencies 4.0.16-SNAPSHOT
+     [exec] [INFO] ------------------------------------------------------------------------
+     [exec] Downloading: http://repo.maven.apache.org/maven2/org/apache/portals/pluto/pluto-ant-tasks/2.1.0-M3/pluto-ant-tasks-2.1.0-M3.pom
+     [exec] Downloaded: http://repo.maven.apache.org/maven2/org/apache/portals/pluto/pluto-ant-tasks/2.1.0-M3/pluto-ant-tasks-2.1.0-M3.pom (2 KB at 2.6 KB/sec)
+     [exec] Downloading: http://repo.maven.apache.org/maven2/org/apache/portals/pluto/pluto-ant-tasks/2.1.0-M3/pluto-ant-tasks-2.1.0-M3.jar
+     [exec] Downloaded: http://repo.maven.apache.org/maven2/org/apache/portals/pluto/pluto-ant-tasks/2.1.0-M3/pluto-ant-tasks-2.1.0-M3.jar (12 KB at 42.1 KB/sec)
+     [exec] [INFO]
+     [exec] [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven) @ pluto-assembler ---
+     [exec] [INFO]
+     [exec] [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-versions) @ pluto-assembler ---
+     [exec] [INFO]
+     [exec] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ pluto-assembler ---
+     [exec] [INFO] Using 'UTF-8' encoding to copy filtered resources.
+     [exec] [INFO] skip non existing resourceDirectory /home/esup/esup-uportal/bootstrap/pluto-assembler/src/main/resources
+     [exec] [INFO]
+     [exec] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ pluto-assembler ---
+     [exec] [INFO] No sources to compile
+     [exec] [INFO]
+     [exec] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ pluto-assembler ---
+     [exec] [INFO] Using 'UTF-8' encoding to copy filtered resources.
+     [exec] [INFO] skip non existing resourceDirectory /home/esup/esup-uportal/bootstrap/pluto-assembler/src/test/resources
+     [exec] [INFO]
+     [exec] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ pluto-assembler ---
+     [exec] [INFO] No sources to compile
+     [exec] [INFO]
+     [exec] [INFO] --- maven-surefire-plugin:2.15:test (default-test) @ pluto-assembler ---
+     [exec] [INFO] No tests to run.
+     [exec] [INFO]
+     [exec] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ pluto-assembler ---
+     [exec] [WARNING] JAR will be empty - no content was marked for inclusion!
+     [exec] [INFO] Building jar: /home/esup/esup-uportal/bootstrap/pluto-assembler/target/pluto-assembler-4.0.16-SNAPSHOT.jar
+     [exec] [INFO]
+     [exec] [INFO] --- maven-site-plugin:3.1.r1174614:attach-descriptor (attach-descriptor) @ pluto-assembler ---
+     [exec] [INFO]
+     [exec] [INFO] --- maven-install-plugin:2.4:install (default-install) @ pluto-assembler ---
+     [exec] [INFO] Installing /home/esup/esup-uportal/bootstrap/pluto-assembler/target/pluto-assembler-4.0.16-SNAPSHOT.jar to /home/esup/.m2/repository/org/jasig/portal/pluto-assembler/4.0.16-SNAPSHOT/pluto-assembler-4.0.16-SNAPSHOT.jar
+     [exec] [INFO] Installing /home/esup/esup-uportal/bootstrap/pluto-assembler/pom.xml to /home/esup/.m2/repository/org/jasig/portal/pluto-assembler/4.0.16-SNAPSHOT/pluto-assembler-4.0.16-SNAPSHOT.pom
+     [exec] [INFO] ------------------------------------------------------------------------
+     [exec] [INFO] BUILD SUCCESS
+     [exec] [INFO] ------------------------------------------------------------------------
+     [exec] [INFO] Total time: 3.805s
+     [exec] [INFO] Finished at: Thu May 26 17:43:42 CEST 2016
+     [exec] [INFO] Final Memory: 16M/310M
+     [exec] [INFO] ------------------------------------------------------------------------
+[assemblePortlet] Assembling '/home/esup/portlet/esup-filemanager/target/esup-filemanager.war' to '/home/esup/esup-uportal/target/tmp'
+[assemblePortlet] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
+[assemblePortlet] SLF4J: Defaulting to no-operation (NOP) logger implementation
+[assemblePortlet] SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
+fastWarDeploy:
+     [echo]    extractWars=true
+     [echo] removeExisting=true
+    [mkdir] Created dir: /home/esup/esup-uportal/target/tmp/esup-filemanager
+    [unwar] Expanding: /home/esup/esup-uportal/target/tmp/esup-filemanager.war into /home/esup/esup-uportal/target/tmp/esup-filemanager
+     [echo] Moving /home/esup/esup-uportal/target/tmp/esup-filemanager to /opt/tomcat/webapps
+   [delete] Deleting: /home/esup/esup-uportal/target/tmp/esup-filemanager.war
+BUILD SUCCESSFUL
+Total time: 10 seconds
+</code>
+=== visualisation Cmd=edit option sur l'interface ===
+voir les options de personnalisation sur l'interface web (si css les caches)
+https://esup4dz.tem-tsp.eu/uPortal/f/welcome/p/esup-filemanager.u32l1n15/max/render.uP?p**Cmd=edit**
+==== esup-filemanager 2====
 === Sources ===

docpublic/systemes/esup/esup_socle_4_c7.1464182716.txt.gz · Last modified: 2016/05/25 13:25 by procacci@tem-tsp.eu

Show page Old revisions

[unknown link type]Back to top