| --- |
| title: Setting Up the HTTP Module for tc Server |
| --- |
| |
| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| |
| To set up the HTTP Module for tc Server, start a tc Server instance with the appropriate tc Server template based on your preferred topology. |
| |
| **Note:** |
| In the procedures that follow, you may be required to log in as root or use sudo to run the commands in Unix, especially if you installed Pivotal tc Server from RPM using yum. |
| |
| ## <a id="tc_setting_up_the_module__section_564B0D4008E343D7AF2791A1271B1F8E" class="no-quick-link"></a>Setup and Start |
| |
| Edit the configuration in the appropriate file for the topology to set the locator host and port. For peer-to-peer topology, edit `geode-p2p/conf/catalina.properties` to set the `geode-p2p.locators` property. For client/server topology, edit `geode-cs/conf/cache-client.xml`. |
| |
| Create a tc Server instance using one of these commands, choosing the appropriate template for the topology. Add the `--version` option if you need to pin your tc Server instance to a specific version of the tc Runtime: |
| |
| ``` pre |
| In Unix, for a peer-to-peer topology: |
| $ ./tcruntime-instance.sh create my_instance_name --template geode-p2p |
| |
| In Unix, for a peer-to-peer topology, with a pinned tc Server instance: |
| $ ./tcruntime-instance.sh create --version 6.0.32.A.RELEASE \ |
| my_instance_name --template geode-p2p |
| |
| In Unix, for a client/server topology: |
| $ ./tcruntime-instance.sh create my_instance_name --template geode-cs |
| |
| In Unix, for a client/server topology, with a pinned tc Server instance: |
| $ ./tcruntime-instance.sh create --version 6.0.32.A.RELEASE \ |
| my_instance_name --template geode-cs |
| |
| In Windows, for a peer-to-peer topology: |
| $ tcruntime-instance.bat create my_instance_name --template geode-p2p |
| |
| In Windows, for a peer-to-peer topology, with a pinned tc Server instance: |
| $ tcruntime-instance.bat create --version 6.0.32.A.RELEASE ^ |
| my_instance_name --template geode-p2p |
| |
| In Windows, for a client/server topology: |
| $ tcruntime-instance.bat create my_instance_name --template geode-cs |
| |
| In Windows, for a client/server topology, with a pinned tc Server instance: |
| $ tcruntime-instance.bat create --version 6.0.32.A.RELEASE ^ |
| my_instance_name --template geode-cs |
| ``` |
| |
| To run, first start the locator, which will listen on its default of port number 10334: |
| |
| ``` pre |
| $ gfsh start locator --name=locator1 |
| ``` |
| |
| With a similar environment to this example that is for a client/server set up, |
| |
| ``` pre |
| TC_VER=tomcat-8.0.30.C.RELEASE |
| INSTANCE=geode-cs |
| CLASSPATH=$PWD/$INSTANCE/lib/geode-modules-1.0.0.jar:\ |
| $PWD/$INSTANCE/lib/geode-modules-tomcat8-1.0.0.jar:\ |
| $PWD/$TC_VER/lib/servlet-api.jar:\ |
| $PWD/$TC_VER/lib/catalina.jar:\ |
| $PWD/$TC_VER/lib/tomcat-util.jar:\ |
| $PWD/$TC_VER/bin/tomcat-juli.jar |
| ``` |
| |
| Start the server using `gfsh`: |
| |
| ``` pre |
| $ gfsh start server --name=server1 --locators=localhost[10334] \ |
| --server-port=0 --classpath=$CLASSPATH |
| ``` |
| |
| ## <a id="tc_setting_up_the_module__section_B6AA6C00DBBD44E68649BDB793578694" class="no-quick-link"></a>Starting the Application Server |
| |
| Once you've created a tc Server instance, you are ready to start the instance. |
| |
| ``` pre |
| In Unix: |
| $ ./tcruntime-ctl.sh my_instance_name start |
| |
| In Windows: |
| $ ./tcruntime-ctl.bat my_instance_name start |
| ``` |
| |
| Refer to the [tc Server](http://www.vmware.com/products/vfabric-tcserver) documentation for more information. Once started, <%=vars.product_name%> will automatically launch within the application server process. |
| |
| **Note:** |
| <%=vars.product_name%> session state management provides its own clustering functionality. If you are using <%=vars.product_name%>, you should NOT turn on Tomcat clustering as well. |
| |
| To verify that the system is running, check the log file for a message similar to: |
| |
| ``` pre |
| Mar 29, 2016 8:38:31 AM org.apache.geode.modules.session.bootstrap.AbstractCache |
| lifecycleEvent |
| INFO: Initializing <%=vars.product_name%> Modules |
| Modules version: 1.0.0 |
| Java version: 1.0.0 user1 032916 2016-11-29 07:49:26 -0700 |
| javac 1.<%=vars.min_java_version%>.0_<%=vars.min_java_update%> |
| Native version: native code unavailable |
| Source revision: c36591b73243c7ee3a0186710338453d12efe364 |
| Source repository: develop |
| Running on: /192.0.2.0, 8 cpu(s), x86_64 Mac OS X 10.11.4 |
| ``` |
| |
| Information is also logged within the <%=vars.product_name%> log file, which by default is named `gemfire_modules.log`. |