[Logo] Enterprise Client Community
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Updating an existing installation - (Non default installation)  XML
Forum Index -> Deployment
Author Message
CaptainCasa

Power User
[Avatar]

Joined: 21/11/2007 12:23:06
Messages: 5519
Offline

Hi,

please find here some infos on updating an existing installation. These are especially usefult when not using the default installation (setup.exe ...) but working in an own Tomcat/... environment, e.g. based on Linux.

For updating you need to:

(1.) Download the version via DevZone. Either the setup.exe program ("all inlusive") or the .zip file. In both cases you will find a "resources" folder after installation/unzipping.

(2.) Now the first thing: update the CaptainCasa tools. This is the /webapplications/editor.war file. You need to bring this into the tomcat environment that you use. Pay attention: in the web application the project files are managed in /editor/config/projects. Although CaptainCasa will never overwrite this, it is useful to keep a safety copy - in order to avoid deletion because of other reasons (e.g. Tomcat removing a web application).
The most trustful way of bringing the editor.war into your tomcat:
a) stop tomcat
b) make sagety copy of /tomcat/webapps/editor/config/projects
c) remove tomcat/webapps/editor.war and tomcat/webapps/editor directory
d) start tomcat
e) throw the saved project files back in

(3.) Now you need to update your projects: each project contains CaptainCasa parts, so you need to update these parts. This is easy:
in the installation you find the directory /webappaddons. Copy the whole content of this directory into the /webcontent part you project.

(4.) Remember: next time you start the layout editor and looking into your project: by reloading the project files will be copied from the project's directory into the tomcat runtime - so you need to press reload one time to see the updated version.

(5.) OK, this is optional, but also to do: the installation contains the web application /webapplications/demos.war. Bring this into your tomcat environment as well. Best way: stop tomcat, remove webapps/demos.war and webapps/demos-directory, copy new demos.war and restart tomcat.

Of course: we recommend to define an ANT script or a shell script to execute all these steps at once.

Hope this helps!

Björn

Björn Müller, CaptainCasa GmbH
CaptainCasa

Power User
[Avatar]

Joined: 21/11/2007 12:23:06
Messages: 5519
Offline

Hi,

today's version contains some tool support for upgrading existing projects: after having updated your editor.war and starting the Project overview you will get notified that your project version does not match the tool's version - and there is a "red button" which triggers the update.

Björn

PS: still, doing it via an ANT script is the cleanest and nicest way! ;-)

[Thumb - versionupdate.png]
 Filename versionupdate.png [Disk] Download
 Description Version Update
 Filesize 49 Kbytes
 Downloaded:  391 time(s)


Björn Müller, CaptainCasa GmbH
 
Forum Index -> Deployment
Go to:   
Powered by JForum 2.1.6 © JForum Team