You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Salamon (JIRA)" <ji...@apache.org> on 2019/04/11 14:47:00 UTC
[jira] [Assigned] (OOZIE-3428) [docs] Update Setting Up Oozie with
an Alternate Tomcat documentation
[ https://issues.apache.org/jira/browse/OOZIE-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andras Salamon reassigned OOZIE-3428:
-------------------------------------
Assignee: (was: Andras Salamon)
> [docs] Update Setting Up Oozie with an Alternate Tomcat documentation
> ---------------------------------------------------------------------
>
> Key: OOZIE-3428
> URL: https://issues.apache.org/jira/browse/OOZIE-3428
> Project: Oozie
> Issue Type: Improvement
> Components: docs
> Affects Versions: trunk
> Reporter: Andras Salamon
> Priority: Major
> Fix For: 5.2.0
>
>
> Although Oozie uses embedded Jetty now, during compilation it still creates a {{war}} file which can be run in a different servlet container.
> The [current documentation|https://oozie.apache.org/docs/5.1.0/AG_Install.html#Setting_Up_Oozie_with_an_Alternate_Tomcat] does not describe the full process, we need to enhance it:
> * A full sample of the {{addtowar}} script usage.
> * Necessary {{CATALINA_OPTS}} settings.
> * A simple script to cleanup the {{webapps}}, copy the war, restart Tomcat.
> * Some info about the supported Tomcat versions would be also useful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)