THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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 . 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..but there are some drawback due o Geronimo itself. See comments at end of this page.
WASCE 2.0.0.1 is based on Geronimo 2.0.3 which is a snapshot (previous versions, and so far 2.1, don't work), I got it there http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0.3-SNAPSHOT/geronimo-tomcat6-jee5-2.0.3-20080318.171132-2-bin.zip
To know more have a look at https://issues.apache.org/jira/browse/GERONIMO-3947
...
- First check and adapt the content of the appserver.properties file
- For instance system/manager are the defaut login/pwd coming with WASCE (and Geronimo). You may need to change them, but there are more important informations, please check
- 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
This should deploy OFBiz under your application server ( You may do it offline or inline depending of appserver.properties file setting for offline parameter) and generate 3 . Of course if you use offline=false the application server should run before. This should deploy OFBiz under your application server and generate 4 kinds of files.Code Block java -jar ofbiz.jar -setup wasce2
- 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 only 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
...
- There is one more README file generated in OFBiz META-INF directory. Open it and follow its intructions before running your application server (so the 1st time you need to deploy offline).
...
- Don't forget to have a look in this file, there are important informations generated there
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.
...
Don't worry, this is because the deployment tool try before to undeploy (not in redeploy mode, note that redeploy implies an application server running). And if you see this message it's only because this module is not deployed on the server. Of course if this error appears durnig during the deployment phase and not the undeployment one, there is a problem in your parameters.
...
- Instances are all the same (simple case)
- Instances are differents or mixed (some instances may be the same)
In the simple case we need only one root (ofbiz.home) and one classpath. Instances are numbered, except the "default one". This allows to keep OFBiz current code : all links from a numbered instances going out of the current application to another application will go to the corresponding called application in the default non numbered instance. This is more a hack but it works. It's interesting when you have a lot of people working in a sole application as it's the case when you have a group of people working to seel goods by phone or other channels (customer support) and for the eCommerce aplication as well.
In the second case there are as many as roots and classpathes couples as there are different instances. I have already in code what is needed to deal with both cases, but I got an issue when writing to modules web.xml (the xml root node is readonly and I don't understand why). In the simple case it's not a problem as we need only to write in the 1st web.xml file (in webtools's) and we can do it by hand (we don't need to dynamically put an instance number in it). Anyway there is much more than this since OFBiz is not build to run multi-instances. In the 1st case it's less a problem as all instances refer to the default corresponding application but to work properly in the general case it would need to introduce an instance number parameter in links. Waiting for such a solution I can see two ways :
- Introduce an instance number in the web.xml file of the 1st web app loaded (OOTB it's webtools). Then use 2 instances for each instance one numbered and the other not. This is of course very clumsy
- I also got a glimpse of another possibility during my reading of Geronimo or
...
- ? WASCE documentation but I forgot where. I'm pretty sure it's the right solution, but I would have to search anew... It's a bit like Ludovic Maître
...
- 's suggestion in one of his emails in user ML (he wrote about Tomcat namespaces but it was not clear to me about what exactly he was speaking).
Miscellaneous experiences
...
Remote deployment using the --inPlace option (for a totally exploded EAR with exploded and only exploded WARs inside as OFBiz is deployed above) is only possible if you exactly replicate the deployed directory structure on both the client and the server machine. If you are on Windows you must even replicate the drive more information on Geronimo forum. I have open a Jira issue for this https://issues.apache.org/jira/browse/GERONIMO-3963. Also beware of heterogeous environments (WIndows Windows to Linux for instance) as I did any such tests.