[DOCU-117] WAR deployment on Tomcat Created: 01/Feb/11  Updated: 27/Jul/11  Resolved: 27/Jul/11

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Suzanne Deprez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File Remarks to last email.eml     File Some update for WAR file deployment.eml    
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Add Felix's tips to Tomcat WAR deployment instructions. Email attached.



 Comments   
Comment by Suzanne Deprez [ 29/Jun/11 ]

Assumed that the settings in the setup procedure are still needed even though there is no longer a WAR for the Tomcat installation bundle for CE and EE per the attached E-mails. Let me know if I incorrectly interpreted.

Activated changes.

Comment by Antti Hietala [ 07/Jul/11 ]

Suzanne, you misunderstood the type of installation. This procedure is not about a bundle install. It is about installing a standalone WAR file on an existing Tomcat. There is and continues to be a WAR file for Magnolia CMS 4.4, check the file server. Read Web Application Archive (WAR) to understand the context. The intro statement about 4.4. is therefore not correct.

What Felix meant is that he did not verify the advice regarding heap size and permSize on a WAR installation such as the one instructed here. He unpacked the WAR manually instead. His advice should still be applicable.

Also, the command export CATALINA_OPTS does not work on Windows. You cannot instruct people to add it to their setenv.bat. Compare setenv.bat and setenv.sh on your local bundle installation to see the differences in commands and syntax. Please revise the article.

Comment by Suzanne Deprez [ 27/Jul/11 ]

Activated new changes. Added an image that needed to be reduced.

Comment by Antti Hietala [ 27/Jul/11 ]

Reviewed and closed.

Generated at Mon Feb 12 01:06:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.