'톰캣'에 해당되는 글 3건

  1. 2023.06.30 AWS/Ubuntu EC2 셋팅
  2. 2011.10.02 톰캣 포트추가 및 root 변경
  3. 2010.06.15 UTF-8 인코딩 변환 예

AWS/Ubuntu EC2 셋팅

Programing 2023. 6. 30. 17:33
반응형

YUM 사용 : Amazon Linux, RedHat, CentOS

APT-GET 사용 : Ubuntu, Debian

 

1. mysql 설치

 

우분투 업데이트

sudo apt-get update

mysql server 설치

sudo apt-get install mysql-server

,Y

 

외부 접근 허용

sudo ufw allow mysql

mysql 실행

sudo systemctl start mysql

mysql 접속

sudo /usr/bin/mysql -u root -p

패스워드는 그냥 엔터

 

데이터베이스 생성

CREATE DATABASE GUIVING;

 

계정생성

create user 'jh'@'%' identified by 'password1234!!';
FLUSH PRIVILEGES;

 

계정에 권한 부여 (*.* 데이터베이스명.테이블명, *는 걍 다 줌)

grant all privileges on GUIVING.* to 'jh'@'%';
FLUSH PRIVILEGES;

 

외부 접근 셋팅

https://npre.tistory.com/entry/%EB%A6%AC%EB%88%85%EC%8A%A4-Mysql-%EC%99%B8%EB%B6%80%EC%A0%91%EC%86%8D-%EC%85%8B%ED%8C%85

 

리눅스 Mysql 외부접속 셋팅

1. user table 변경 mysql> grant all privileges on *.* 'root'@'%' identified by '패스워드'; mysql> flush privileges; 2. bind-address 주석 vi /etc/mysql/my.cnf 또는 해당 파일 내부 참조파일 3. mysql restart service mysql restart 4. 3306

npre.tistory.com

 

2. tomcat 설치 (java 설치)

자바 설치 확인

java --version

 

 

APT-GET update

sudo apt-get update

 

JRE install (필요한 버젼으로)

sudo apt install openjdk-11-jre-headless

JRE 여러개 설치 되었을 때 버젼 변경하는법 참조

https://freedeveloper.tistory.com/347

 

톰캣 설치 위치 만들기

sudo mkdir /home/tomcat

 

톰캣다운로드

 

https://tomcat.apache.org/download-90.cgi

 

Apache Tomcat® - Apache Tomcat 9 Software Downloads

Welcome to the Apache Tomcat® 9.x software download page. This page provides download links for obtaining the latest version of Tomcat 9.0.x software, as well as links to the archives of older releases. Unsure which version you need? Specification version

tomcat.apache.org

에서 다운로드 링크 복사

 

sudo tar xvfz apache-tomcat-9~~~

 

환경변수 설정

 

sudo chmod -R 777 /etc/profile
sudo vi /etc/profile


##추가
export CATALINA_HOME=/home/tomcat



source /etc/profile

 

권한설정해두기

sudo chmod -R 777 home/tomcat/

 

실행

sudo ./startup.sh

 

 

 

## 참고사항

EC2하나에 mysql과 tomcat을 동시에 셋팅하면 서버가 뻗어버리는 현상 발생, 프리티어 EC2두개로 생성하여 하나씩 셋팅하는것을 권장

Posted by npre
,
반응형

기본적으로 8080포트가 ROOT를 바라보고있어서

8081포트를 추가하여 ROOT말고 다른 폴더를 바라보게하였다.

server.xml에 Catalina2로 서비스를 하나 추가하고 포트번호와 리다이렉트 포트값들을 1씩 올려준다.

추가된 8081포트의 root를 바꾸기 위하여

<Host name="localhost" appBase="webapps/Gael"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">

로 root를 변경해주고 바로 밑에

<Context path="" docBase="." reloadable="true"/>

코드를 추가해 준다.

<Service name="Catalina2">

    <!-- A "Connector" represents an endpoint by which requests are received

         and responses are returned.  Each Connector passes requests on to the

         associated "Container" (normally an Engine) for processing.

         By default, a non-SSL HTTP/1.1 Connector is established on port 8080.

         You can also enable an SSL HTTP/1.1 Connector on port 8443 by

         following the instructions below and uncommenting the second Connector

         entry.  SSL support requires the following steps (see the SSL Config

         HOWTO in the Tomcat 5 documentation bundle for more detailed

         instructions):

         * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or

           later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".

         * Execute:

             %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)

             $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)

           with a password value of "changeit" for both the certificate and

           the keystore itself.

         By default, DNS lookups are enabled when a web application calls

         request.getRemoteHost().  This can have an adverse impact on

         performance, so you can disable it by setting the

         "enableLookups" attribute to "false".  When DNS lookups are disabled,

         request.getRemoteHost() will return the String version of the

         IP address of the remote client.

    -->

    <!- Define a non-SSL HTTP/1.1 Connector on port 8080 ->

    <Connector port="8081" maxHttpHeaderSize="8192"

               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

               enableLookups="false" redirectPort="8444" acceptCount="100"

               connectionTimeout="20000" disableUploadTimeout="true" />

    <!-- Note : To disable connection timeouts, set connectionTimeout value

     to 0 -->

<!-- Note : To use gzip compression you could set the following properties :

  compression="on" 

  compressionMinSize="2048" 

  noCompressionUserAgents="gozilla, traviata" 

  compressableMimeType="text/html,text/xml"

-->

    <!- Define a SSL HTTP/1.1 Connector on port 8443 ->

    <!--

    <Connector port="8443" maxHttpHeaderSize="8192"

               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

               enableLookups="false" disableUploadTimeout="true"

               acceptCount="100" scheme="https" secure="true"

               clientAuth="false" sslProtocol="TLS" />

    -->

    <!- Define an AJP 1.3 Connector on port 8009 ->

    <Connector port="8010" 

               enableLookups="false" redirectPort="8444" protocol="AJP/1.3" />

    <!- Define a Proxied HTTP/1.1 Connector on port 8082 ->

    <!- See proxy documentation for more information about using this. ->

    <!--

    <Connector port="8082" 

               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

               enableLookups="false" acceptCount="100" connectionTimeout="20000"

               proxyPort="80" disableUploadTimeout="true" />

    -->

    <!-- An Engine represents the entry point (within Catalina) that processes

         every request.  The Engine implementation for Tomcat stand alone

         analyzes the HTTP headers included with the request, and passes them

         on to the appropriate Host (virtual host). -->

    <!-- You should set jvmRoute to support load-balancing via AJP ie :

    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">         

    --> 

    <!- Define the top level container in our container hierarchy ->

    <Engine name="Catalina2" defaultHost="localhost">

      <!-- The request dumper valve dumps useful debugging information about

           the request headers and cookies that were received, and the response

           headers and cookies that were sent, for all requests received by

           this instance of Tomcat.  If you care only about requests to a

           particular virtual host, or a particular application, nest this

           element inside the corresponding <Host> or <Context> entry instead.

           For a similar mechanism that is portable to all Servlet 2.4

           containers, check out the "RequestDumperFilter" Filter in the

           example application (the source for this filter may be found in

           "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").

           Request dumping is disabled by default.  Uncomment the following

           element to enable it. -->

      <!--

      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>

      -->

      <!- Because this Realm is here, an instance will be shared globally ->

      <!-- This Realm uses the UserDatabase configured in the global JNDI

           resources under the key "UserDatabase".  Any edits

           that are performed against this UserDatabase are immediately

           available for use by the Realm.  -->

      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"

             resourceName="UserDatabase"/>

      <!-- Comment out the old realm but leave here for now in case we

           need to go back quickly -->

      <!--

      <Realm className="org.apache.catalina.realm.MemoryRealm" />

      -->

      <!-- Replace the above Realm with one of the following to get a Realm

           stored in a database and accessed via JDBC -->

      <!--

      <Realm  className="org.apache.catalina.realm.JDBCRealm"

             driverName="org.gjt.mm.mysql.Driver"

          connectionURL="jdbc:mysql://localhost/authority"

         connectionName="test" connectionPassword="test"

              userTable="users" userNameCol="user_name" userCredCol="user_pass"

          userRoleTable="user_roles" roleNameCol="role_name" />

      -->

      <!--

      <Realm  className="org.apache.catalina.realm.JDBCRealm"

             driverName="oracle.jdbc.driver.OracleDriver"

          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"

         connectionName="scott" connectionPassword="tiger"

              userTable="users" userNameCol="user_name" userCredCol="user_pass"

          userRoleTable="user_roles" roleNameCol="role_name" />

      -->

      <!--

      <Realm  className="org.apache.catalina.realm.JDBCRealm"

             driverName="sun.jdbc.odbc.JdbcOdbcDriver"

          connectionURL="jdbc:odbc:CATALINA"

              userTable="users" userNameCol="user_name" userCredCol="user_pass"

          userRoleTable="user_roles" roleNameCol="role_name" />

      -->

      <!-- Define the default virtual host

           Note: XML Schema validation will not work with Xerces 2.2.

       -->

      <Host name="localhost" appBase="webapps/Gael"

       unpackWARs="true" autoDeploy="true"

       xmlValidation="false" xmlNamespaceAware="false">

       <Context path="" docBase="." reloadable="true"/>

        <!-- Defines a cluster for this node,

             By defining this element, means that every manager will be changed.

             So when running a cluster, only make sure that you have webapps in there

             that need to be clustered and remove the other ones.

             A cluster has the following parameters:

             className = the fully qualified name of the cluster class

             name = a descriptive name for your cluster, can be anything

             mcastAddr = the multicast address, has to be the same for all the nodes

             mcastPort = the multicast port, has to be the same for all the nodes

             mcastBindAddr = bind the multicast socket to a specific address

             mcastTTL = the multicast TTL if you want to limit your broadcast

             mcastSoTimeout = the multicast readtimeout 

             mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat

             mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received

             tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes 

             tcpListenAddress = the listen address (bind address) for TCP cluster request on this host, 

                                in case of multiple ethernet cards.

                                auto means that address becomes

                                InetAddress.getLocalHost().getHostAddress()

             tcpListenPort = the tcp listen port

             tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS

                                  has a wakup bug in java.nio. Set to 0 for no timeout

             printToScreen = true means that managers will also print to std.out

             expireSessionsOnShutdown = true means that 

             useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.

                            false means to replicate the session after each request.

                            false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)

                            <%

                            HashMap map = (HashMap)session.getAttribute("map");

                            map.put("key","value");

                            %>

             replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.

                               * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.

                               * Synchronous means that the thread that executes the request, is also the

                               thread the replicates the data to the other nodes, and will not return until all

                               nodes have received the information.

                               * Asynchronous means that there is a specific 'sender' thread for each cluster node,

                               so the request thread will queue the replication request into a "smart" queue,

                               and then return to the client.

                               The "smart" queue is a queue where when a session is added to the queue, and the same session

                               already exists in the queue from a previous request, that session will be replaced

                               in the queue instead of replicating two requests. This almost never happens, unless there is a 

                               large network delay.

        -->             

        <!--

            When configuring for clustering, you also add in a valve to catch all the requests

            coming in, at the end of the request, the session may or may not be replicated.

            A session is replicated if and only if all the conditions are met:

            1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND

            2. a session exists (has been created)

            3. the request is not trapped by the "filter" attribute

            The filter attribute is to filter out requests that could not modify the session,

            hence we don't replicate the session after the end of this request.

            The filter is negative, ie, anything you put in the filter, you mean to filter out,

            ie, no replication will be done on requests that match one of the filters.

            The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.

            filter=".\.gif;.\.js;" means that we will not replicate the session after requests with the URI

            ending with .gif and .js are intercepted.

            The deployer element can be used to deploy apps cluster wide.

            Currently the deployment only deploys/undeploys to working members in the cluster

            so no WARs are copied upons startup of a broken node.

            The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"

            When a new war file is added the war gets deployed to the local instance,

            and then deployed to the other instances in the cluster.

            When a war file is deleted from the watchDir the war is undeployed locally 

            and cluster wide

        -->

        <!--

        <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"

                 managerClassName="org.apache.catalina.cluster.session.DeltaManager"

                 expireSessionsOnShutdown="false"

                 useDirtyFlag="true"

                 notifyListenersOnReplication="true">

            <Membership 

                className="org.apache.catalina.cluster.mcast.McastService"

                mcastAddr="228.0.0.4"

                mcastPort="45564"

                mcastFrequency="500"

                mcastDropTime="3000"/>

            <Receiver 

                className="org.apache.catalina.cluster.tcp.ReplicationListener"

                tcpListenAddress="auto"

                tcpListenPort="4001"

                tcpSelectorTimeout="100"

                tcpThreadCount="6"/>

            <Sender

                className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"

                replicationMode="pooled"

                ackTimeout="15000"/>

            <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"

                   filter=".\.gif;.\.js;.\.jpg;.\.png;.\.htm;.\.html;.\.css;.\.txt;"/>

            <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"

                      tempDir="/tmp/war-temp/"

                      deployDir="/tmp/war-deploy/"

                      watchDir="/tmp/war-listen/"

                      watchEnabled="false"/>

        </Cluster>

        -->        



        <!-- Normally, users must authenticate themselves to each web app

             individually.  Uncomment the following entry if you would like

             a user to be authenticated the first time they encounter a

             resource protected by a security constraint, and then have that

             user identity maintained across *all* web applications contained

             in this virtual host. -->

        <!--

        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />

        -->

        <!-- Access log processes all requests for this virtual host.  By

             default, log files are created in the "logs" directory relative to

             $CATALINA_HOME.  If you wish, you can specify a different

             directory with the "directory" attribute.  Specify either a relative

             (to $CATALINA_HOME) or absolute path to the desired directory.

        -->

        <!--

        <Valve className="org.apache.catalina.valves.AccessLogValve"

                 directory="logs"  prefix="localhost_access_log." suffix=".txt"

                 pattern="common" resolveHosts="false"/>

        -->

        <!-- Access log processes all requests for this virtual host.  By

             default, log files are created in the "logs" directory relative to

             $CATALINA_HOME.  If you wish, you can specify a different

             directory with the "directory" attribute.  Specify either a relative

             (to $CATALINA_HOME) or absolute path to the desired directory.

             This access log implementation is optimized for maximum performance,

             but is hardcoded to support only the "common" and "combined" patterns.

        -->

        <!--

        <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"

                 directory="logs"  prefix="localhost_access_log." suffix=".txt"

                 pattern="common" resolveHosts="false"/>

        -->

        <!-- Access log processes all requests for this virtual host.  By

             default, log files are created in the "logs" directory relative to

             $CATALINA_HOME.  If you wish, you can specify a different

             directory with the "directory" attribute.  Specify either a relative

             (to $CATALINA_HOME) or absolute path to the desired directory.

             This access log implementation is optimized for maximum performance,

             but is hardcoded to support only the "common" and "combined" patterns.

             This valve use NIO direct Byte Buffer to asynchornously store the

             log.

        -->

        <!--

        <Valve className="org.apache.catalina.valves.ByteBufferAccessLogValve"

                 directory="logs"  prefix="localhost_access_log." suffix=".txt"

                 pattern="common" resolveHosts="false"/>

        -->

      </Host>

    </Engine>

  </Service>

'Programing' 카테고리의 다른 글

[iPhone] uitextfield 자리수 제한  (0) 2011.10.28
[iPhone] 이미지 썸네일  (0) 2011.10.19
아이폰 근접센서  (0) 2011.08.24
[iPhone] 만보기 로직  (0) 2011.06.27
[iPhone] Tabbar Custom  (0) 2011.06.23
Posted by npre
,
반응형

String dong = req.getParameter("dong");
dong = new String(dong.getBytes("8859_1"), "utf-8");     //톰캣 문자열 처리

'Programing' 카테고리의 다른 글

input박스에 disable  (1) 2010.06.21
세션 타임아웃 지정  (0) 2010.06.21
Map은 절대로 for문을 돌리지 않는다.  (0) 2010.06.17
input 읽기만가능  (0) 2010.06.16
Spring에서 List와 Model  (0) 2010.06.15
Posted by npre
,