Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This uses a totally exploded EAR architecture (with exploded WARs as well).
The deployment tool is for the moment intended to be use on a sole machine : you can't deploy remotely (on a Linux Server from a Windows machine for instance, or whatever actually). I'm working on a solution to be able to deploy remotely...

...

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

Code Block
java -Xms256M -Xmx512M -XX:MaxPermSize=128M -jar ofbiz.jar -setup wasce2

...

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 (these kinds of files don't exist in OFBiz OOTB). If it's not related directly to OFBiz remove it.

You might see an error message like

Error: ofbiz does not appear to be a the name of a module available
on the selected server. Perhaps it has already been stopped or
undeployed? If you're trying to specify a TargetModuleID, use the
syntax TargetName|ModuleName instead. If you're not sure what's
running, try the list-modules command.

Don't worry, this is because the deployment tool try before to undeploy. And if you see this message it's only because this module is not deployed on the server.

Note that system/manager are the defaut login/pwd coming with WASCE (and Geronimo). You may need to change them in appserver.properties

I should mention that it seems to me that deploying with a server already running (offline=false in appserver.properties) is faster but I did not measure exactly yet. Anyway, you need to deploy offline the 1st time you deploy since you need to generate put the generated and mandatory informations found in META-INF/README informations .

Run

  • Then if you launch the WASCE server using regular command (or running "Geronimo run" from GERONIMO_HOME\bin) it should start with OFBiz modules loaded. For obvious port conflicts reason, don't run standard OFBiz at the same time.
    • If you run the Geronimo script from GERONIMO_HOME\bin
      Code Block
      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.

...