Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Geronimo & Websphere Application Server Community Edition 2

Guidelines to use OFBiz with WASCE 2 using an exploded EAR

I got an issue with exploded WARs in exploded EAR in Geronimo 2.0.1 though it should work following claims of http://issues.apache.org/jira/browse/GERONIMO-1445. I will create an issue in Geronimo Jira soon and hopefully we will get them working together...

  • After the installation, don't forget to set your GERONIMO_HOME env var (for me for instance, on Windows it was C:\Program Files\IBM\WebSphere\AppServerCommunityEdition)
    If you need to set GERONIMO_HOME dymanically (for instance with multi Geronimo or WASCE versions) you can use the 3th optionnal parameter of the setup option like below, it overrides GERONIMO_HOME
    java -jar ofbiz.jar -setup wasce2 /META-INF/  ["myGERONIMO_HOME"]
    (using the real value of myGERONIMO_HOME of course for instance for me was <<-setup wasce2 /META-INF/ "C:\Program Files\IBM\WebSphere\AppServerCommunityEdition">>)
    The first parameter is related to the subdirectory from where you want to create deployment plans
    A fourth parameter is not used yet, but is reserved to allow running OFBiz multi-instance in Geronimo later.
    I'm still not sure I will keep the second parameter by the way
  • At this stage, don't try to install and use Eclipse plugins. They are not up to date yet, and will not be of a great help in our case anyway (I tried them, and lost some time around this)
  • From a clean OFBiz installation which runs well on the same machine than where WASCE is installed, at OFBiz root (or Eclipse or what else) run
    java -jar ofbiz.jar -setup geronimo201 /META-INF/  ["myGERONIMO_HOME"]
    (using the real value of myGERONIMO_HOME if it's needed)
  • This should generate 3 kinds of files
    • OFBiz jar files in the Geronimo repository
    • Deployment plans (application.xml and geronimo-application.xml) in a generated META-INF directory (in OFBiz root directory). Though the term "deployment plans" is normally used for Geronimo specific "J2EE deployment descriptors" (application.xml for instance is a standard "J2EE deployment descriptors")
    • Deployment plans (geronimo-web.xml) in each applications WEB-INF directories
    • Actually there is one more README file generated in OFBiz META-INF directory. Open it and follow its intructions.
  • Then you should be ready to deploy OFBiz in WASSCE (or Geronimo). Simply use a command like 
    deploy --user system --password manager --offline deploy --inPlace C:\OFBiz
    from GERONIMO_HOME\bin. If you have the application server already running, simply remove the --offline option in the command above.
    Something like "Illegal character in path" in the log means that you must remove the corresponding file, these errors are often related to .xls of .pdf files (or what else) found in the OFBiz directories structure. If it's not related directly to OFBiz remove it.

Note that system/manager are the defaut login/pwd coming with WASCE (and Geronimo); --offline allows to deploy without Geronimo running; --inPlace because we use and Exploded architecture.
Af first sight what this command does is replicating OFBiz directories structure and content in GERONIMO_HOME\repository\org\ofbiz\ofbiz\1.0\Ear\ofbiz-1.0.ear

  • Then if you launch the WASCE server using regular command (or preferably running Geronimo script from GERONIMO_HOME\bin) it should start also OFBIz in itself. For obvious conflict reasons, don't run standard OFBiz in the same time.
    • If you run the Geronimo script from GERONIMO_HOME\bin 
      geronimo run
      with the setenv and geronimo script modified following instructions in the README file you will see what happens. This is why I think it's a preferable way of launching the server.
  • You will find OFBiz specific logs in geronimo_home\bin\framework\logs directory
  • No labels