[jira] [Updated] (TOMEE-2424) Create TomEE-Cluster.adoc
[ https://issues.apache.org/jira/browse/TOMEE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roberto Cortez updated TOMEE-2424: -- Issue Type: Documentation (was: Improvement) > Create TomEE-Cluster.adoc > - > > Key: TOMEE-2424 > URL: https://issues.apache.org/jira/browse/TOMEE-2424 > Project: TomEE > Issue Type: Documentation > Components: Examples and Documentation >Affects Versions: 8.0.0-M1 > Environment: http://tomee.apache.org/tomee-8.0/docs/ >Reporter: Pavel Smajda >Priority: Minor > Labels: pull-request-available > Fix For: 8.0.0-M2 > > > There is only .txt format of document. We need to convert it to .adoc file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TOMEE-2424) Create TomEE-Cluster.adoc
[ https://issues.apache.org/jira/browse/TOMEE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Smajda updated TOMEE-2424: Environment: http://tomee.apache.org/tomee-8.0/docs/ > Create TomEE-Cluster.adoc > - > > Key: TOMEE-2424 > URL: https://issues.apache.org/jira/browse/TOMEE-2424 > Project: TomEE > Issue Type: Improvement > Components: Examples and Documentation >Affects Versions: 8.0.0-M1 > Environment: http://tomee.apache.org/tomee-8.0/docs/ >Reporter: Pavel Smajda >Priority: Minor > Labels: pull-request-available > Fix For: 8.0.0-M2 > > > There is only .txt format of document. We need to convert it to .adoc file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TOMEE-2424) Create TomEE-Cluster.adoc
[ https://issues.apache.org/jira/browse/TOMEE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated TOMEE-2424: -- Labels: pull-request-available (was: ) > Create TomEE-Cluster.adoc > - > > Key: TOMEE-2424 > URL: https://issues.apache.org/jira/browse/TOMEE-2424 > Project: TomEE > Issue Type: Improvement > Components: Examples and Documentation >Affects Versions: 8.0.0-M1 >Reporter: Pavel Smajda >Priority: Minor > Labels: pull-request-available > Fix For: 8.0.0-M2 > > > There is only .txt format of document. We need to convert it to .adoc file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TOMEE-2424) Create TomEE-Cluster.adoc
[ https://issues.apache.org/jira/browse/TOMEE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Smajda updated TOMEE-2424: Docs Text: = TomEE Cluster :index-group: Configuration :jbake-date: 2018-12-05 :jbake-type: page :jbake-status: published The scope of this document to to define how Apache TomEE can be configured for HA (High Availability) clustering. The configuration will focus on two local instances, with a view to an open ended remote configuration. It is beyond the scope of this documentation to discuss Tomcat Clustering in depth. Please read the [Apache Tomcat Clustering Howto](http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto .html) for more information. === Local cluster To test clustering locally (on the same physical machine) the default ports need to be modified on the second TomEE server. You do not need to do this if the second TomEE instance is to run on different machine or virtual host. Note: You cannot test load balancing on a local cluster as they will be running of different ports. This configuration is only useful for testing Session Replication and application deployment. In the *[TomEE]/conf/server.xml* look for and change the following port definitions to something like: === Test Startup Start both TomEE servers together and check for and resolve any errors before proceeding any further. Once you are sure both servers can run without error add the following to the section of both server.xml files: ... ... Start both TomEE servers together and again check for and resolve any errors before proceeding any further. Basically look in both *[TomEE]/logs/catalina.[date].log* and search for *"SimpleTcpCluster memberAdded"*. This lets us know that the cluster added a new member. Stop both the servers, as we will need to add some more configuration to the *server.xml*. First create the following directory structure within the TomEE installation (You can change the names later to suit your needs if required). [TomEE]/cluster [TomEE]/cluster/temp [TomEE]/cluster/watch [TomEE]/cluster/webapps We now need to add these paths to the **Host** section of the configuration file: ... ... ... was: = TomEE Cluster :index-group: Configuration :jbake-date: 2018-12-05 :jbake-type: page :jbake-status: published The scope of this document to to define how Apache TomEE can be configured for HA (High Availability) clustering. The configuration will focus on two local instances, with a view to an open ended remote configuration. It is beyond the scope of this documentation to discuss Tomcat Clustering in depth. Please read the [Apache Tomcat Clustering Howto](http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto .html) for more information. ### Local cluster To test clustering locally (on the same physical machine) the default ports need to be modified on the second TomEE server. You do not need to do this if the second TomEE instance is to run on different machine or virtual host. Note: You cannot test load balancing on a local cluster as they will be running of different ports. This configuration is only useful for testing Session Replication and application deployment. In the *[TomEE]/conf/server.xml* look for and change the following port definitions to something like: ### Test Startup Start both TomEE servers together and check for and resolve any errors before proceeding any further. Once you are sure both servers can run without error add the following to the section of both server.xml files: ... ... Start both TomEE servers together and again check for and resolve any errors before proceeding any further. Basically look in both *[TomEE]/logs/catalina.[date].log* and search for *"SimpleTcpCluster memberAdded"*. This lets us know that the cluster added a new member. Stop both the servers, as we will need to add some more configuration to the *server.xml*. First create the following directory structure within the TomEE installation (You can change the names later to suit your needs if required). [TomEE]/cluster [TomEE]/cluster/temp [TomEE]/cluster/watch [TomEE]/cluster/webapps We now need to add these paths to the **Host** section of the configuration file: ... ...
[jira] [Updated] (TOMEE-2424) Create TomEE-Cluster.adoc
[ https://issues.apache.org/jira/browse/TOMEE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Smajda updated TOMEE-2424: Docs Text: = TomEE Cluster :index-group: Configuration :jbake-date: 2018-12-05 :jbake-type: page :jbake-status: published The scope of this document to to define how Apache TomEE can be configured for HA (High Availability) clustering. The configuration will focus on two local instances, with a view to an open ended remote configuration. It is beyond the scope of this documentation to discuss Tomcat Clustering in depth. Please read the [Apache Tomcat Clustering Howto](http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto .html) for more information. ### Local cluster To test clustering locally (on the same physical machine) the default ports need to be modified on the second TomEE server. You do not need to do this if the second TomEE instance is to run on different machine or virtual host. Note: You cannot test load balancing on a local cluster as they will be running of different ports. This configuration is only useful for testing Session Replication and application deployment. In the *[TomEE]/conf/server.xml* look for and change the following port definitions to something like: ### Test Startup Start both TomEE servers together and check for and resolve any errors before proceeding any further. Once you are sure both servers can run without error add the following to the section of both server.xml files: ... ... Start both TomEE servers together and again check for and resolve any errors before proceeding any further. Basically look in both *[TomEE]/logs/catalina.[date].log* and search for *"SimpleTcpCluster memberAdded"*. This lets us know that the cluster added a new member. Stop both the servers, as we will need to add some more configuration to the *server.xml*. First create the following directory structure within the TomEE installation (You can change the names later to suit your needs if required). [TomEE]/cluster [TomEE]/cluster/temp [TomEE]/cluster/watch [TomEE]/cluster/webapps We now need to add these paths to the **Host** section of the configuration file: ... ... ... was: = TomEE Cluster :index-group: Configuration :jbake-date: 2018-12-05 :jbake-type: page :jbake-status: published The scope of this document to to define how Apache TomEE can be configured for HA (High Availability) clustering. The configuration will focus on two local instances, with a view to an open ended remote configuration. It is beyond the scope of this documentation to discuss Tomcat Clustering in depth. Please read the [Apache Tomcat Clustering Howto](http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto .html) for more information. ### Local cluster To test clustering locally (on the same physical machine) the default ports need to be modified on the second TomEE server. You do not need to do this if the second TomEE instance is to run on different machine or virtual host. Note: You cannot test load balancing on a local cluster as they will be running of different ports. This configuration is only useful for testing Session Replication and application deployment. In the */conf/server.xml* look for and change the following port definitions to something like: ### Test Startup Start both TomEE servers together and check for and resolve any errors before proceeding any further. Once you are sure both servers can run without error add the following to the section of both server.xml files: ... ... Start both TomEE servers together and again check for and resolve any errors before proceeding any further. Basically look in both [TomEE]/logs/catalina.[date].log and search for *"SimpleTcpCluster memberAdded"*. This lets us know that the cluster added a new member. Stop both the servers, as we will need to add some more configuration to the *server.xml*. First create the following directory structure within the TomEE installation (You can change the names later to suit your needs if required). [TomEE]/cluster [TomEE]/cluster/temp [TomEE]/cluster/watch [TomEE]/cluster/webapps We now need to add these paths to the **Host** section of the configuration file: ... ...
