HP UX

11.xx 일 경우
# getconf KERNEL_BITS
64

10.xx 일 경우
# getconf LONG_MAX
2147483647
(64비트임)로 확인할 수 있습니다

AIX

현재 load된 kernel 이 32-bit 혹은 64-bit 인지 확인하는 명령어
# bootinfo -K
32

사용중인 machine이 32-bit 혹은 64-bit 인지 확인하는 명령어
# bootinfo -y
32


SOLARIS

# isainfo -kv
64-bit sparcv9 kernel modules
현재 이 시스템은 64bit 커널을 가지고 운영을 하는 시스템 이다.

# isainfo -kv
32-bit sparcv kernel modules
이 시스템은 32bit 커널을 가지고 운영을 하는 시스템이다.

# isainfo -v
64-bit sparcv9 applications 32-bit sparc applications
"-v"만 했을 경우 이 시스템에서는 32bit / 64bit 체계의 프로그램을 사용할 수 있다.

# isainfo -v
32-bit sparc applications
이 시스템은 32bit 체계의 프로그램만 구성하여 사용할 수 있다.

 이더넷 채널 본딩
* 정의 : 네트워크 대역폭 (서버의 네트워크 트래픽을 감소시키기 위해) 을 늘리기 위해 다수의 네트워크 인터페이스를 묶어 하나의 채널로 사용하는것
 
1) bond 0 모드 : 네트워크 대역폭 증가
CentOS4 리눅스 커널에 이미 bonding module이 이미 설정 되어 있으므로 bonding moudule을 사용하겠다고 커널에 알려주기만 하면 된다.
/etc/modprobe.conf

[추가]
alias bond0 bonding
options bond0 miimon=100 mode=1 primary=eth0
 

▷ mode 옵션
- balance-rr or 0 : 라운드 로빈 방식 , 두 개 이상의 네트워크 인터페이스를 이용하여 번갈아 사용한다.
- active-backup or 1 : active-standby 방식으로 네트워크 인터페이스의 이중화 구성.장애방지 목적 (대부분)
- balance-xor or 2 : xor 방식, 수신시 첫 번째, 송신시 두 번째 인터페이스를 이용.
- broadcast or 3 : 모든 인터페이스에 전송.

▷ miimon 옵션
- 네트워크 인터페이스가 살아있는지 확인하는 시간 0.001초 단위
▷ max_bonds 옵션
- 본딩의 개수를 지정하는 옵션

2) 본딩 모듈 인식
- 커널에 인식 시켜줘야 한다.
시스템 재부팅 혹은 modprobe 명령어 이용
# modprobe bonding bond0 options mode=1 miimon=100 user_carrier=0 max_bonds=1

 
3) 인터페이스 설정
☞ /etc/sysconfig/network-scripts/ifcfg-bond0 파일 생성
# bond0 is Public Network NIC
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
NETWORK=192.168.100.0
NETMASK=255.255.255.0
IPADDR=192.168.100.201
GATEWAY=192.168.100.1
USERCTL=no
 

☞ /etc/sysconfig/network-scripts/ifcfg-eth0 파일 편집
# eth0 is Public Network NIC
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
 
☞ /etc/sysconfig/network-scripts/ifcfg-eth1 파일 편집
# eth1 is Public Network NIC
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no

4) 이더넷 채널 본딩 적용
- 네트워크 데몬 재실행
# service network restart
->ifconfig 를 하면 eth0, eth1의 MAC address가 같은 것을 확인 할 수 있다.
5) 본딩 해제
# rmmod bonding

Introduction

This document describes the password recovery procedure for the Cisco Catalyst Layer 2 fixed configuration switches 2900XL/3500XL, 2940, 2950/2955, 2960, and 2970 Series, as well as the Cisco Catalyst Layer 3 fixed configuration switches 3550, 3560, and 3750 Series.

Before You Begin

Conventions

For more information on document conventions, see the Cisco Technical Tips Conventions.

Prerequisites

There are no specific prerequisites for this document.

Step-by-Step Procedure

Follow the password recovery procedure below.

1. Attach a terminal or PC with terminal emulation (for example, Hyper Terminal) to the console port of the switch.

   Use the following terminal settings:

   • Bits per second (baud): 9600

   • Data bits: 8

   • Parity: None

   • Stop bits: 1

   • Flow Control: Xon/Xoff

   Note: For additional information on cabling and connecting a terminal to the console port, refer to Connecting a Terminal to the Console Port on Catalyst Switches.

2. Unplug the power cable.

3. Power the switch and bring it to the switch: prompt:

   For 2900XL, 3500XL, 2940, 2950, 2960, 2970, 3550, 3560, and 3750 series switches, do this:

   Hold down the mode button located on the left side of the front panel, while you reconnect the power cable to the switch.

   Catalyst Switch Series	LED Behavior and Mode Button Release Action
   2900XL, 3500XL, 3550	Release the Mode button when the LED above Port1x goes out.
   2940, 2950	Release the Mode button after approximately 5 seconds when the Status (STAT) LED goes out. When you release the Mode button, the SYST LED blinks amber.
   2960, 2970	Release the Mode button when the SYST LED blinks amber and then turns solid green. When you release the Mode button, the SYST LED blinks green.
   3560, 3750	Release the Mode button after approximately 15 seconds when the SYST LED turns solid green. When you release the Mode button, the SYST LED blinks green.

   Note: LED position may vary slightly depending on the model.

   Catalyst 3524XL

   

   Catalyst 2950-24

   

   For 2955 series switches only:

   The Catalyst 2955 series switches do not use an external mode button for password recovery. Instead the switch boot loader uses the break-key detection to stop the automatic boot sequence for the password recovery purposes. The break sequence is determined by the terminal application and operating system used. Hyperterm running on Windows 2000 uses Ctrl + Break. On a workstation running UNIX, Ctrl-C is the break key. For more information, refer to Standard Break Key Sequence Combinations During Password Recovery.

   The example below uses Hyperterm to break into switch: mode on a 2955.

   C2955 Boot Loader (C2955-HBOOT-M) Version 12.1(0.0.514), CISCO DEVELOPMENT TESTVERSIONCompiled Fri 13-Dec-02 17:38 by madisonWS-C2955T-12 starting...Base ethernet MAC Address: 00:0b:be:b6:ee:00Xmodem file system is available.Initializing Flash...flashfs[0]: 19 files, 2 directoriesflashfs[0]: 0 orphaned files, 0 orphaned directoriesflashfs[0]: Total bytes: 7741440flashfs[0]: Bytes used: 4510720flashfs[0]: Bytes available: 3230720flashfs[0]: flashfs fsck took 7 seconds....done initializing flash.Boot Sector Filesystem (bs:) installed, fsid: 3Parameter Block Filesystem (pb:) installed, fsid: 4*** The system will autoboot in 15 seconds ***Send break character to prevent autobooting.!--- Wait until you see this message before !--- you issue the break sequence.!--- Ctrl+Break is entered using Hyperterm.The system has been interrupted prior to initializing the flash file system to finish loading the operating system software:flash_initload_helperbootswitch:

4. Issue the flash_init command.

   switch: flash_initInitializing Flash...flashfs[0]: 143 files, 4 directoriesflashfs[0]: 0 orphaned files, 0 orphaned directoriesflashfs[0]: Total bytes: 3612672flashfs[0]: Bytes used: 2729472flashfs[0]: Bytes available: 883200flashfs[0]: flashfs fsck took 86 seconds....done Initializing Flash.Boot Sector Filesystem (bs:) installed, fsid: 3Parameter Block Filesystem (pb:) installed, fsid: 4switch:!--- This output is from a 2900XL switch. Output from !--- other switches will vary slightly.

5. Issue the load_helper command.

   switch: load_helperswitch:

6. Issue the dir flash: command.

   Note: Make sure to type a colon ":" after the dir flash.

   The switch file system is displayed:

   switch: dir flash:Directory of flash:/2    -rwx  1803357   <date>               c3500xl-c3h2s-mz.120-5.WC7.bin!--- This is the current version of software.4    -rwx  1131      <date>               config.text!--- This is the configuration file.5    -rwx  109       <date>               info6    -rwx  389       <date>               env_vars7    drwx  640       <date>               html18   -rwx  109       <date>               info.ver403968 bytes available (3208704 bytes used)switch:!--- This output is from a 3500XL switch. Output from !--- other switches will vary slightly.

7. Type rename flash:config.text flash:config.old to rename the configuration file.

   switch: rename flash:config.text flash:config.oldswitch:!--- The config.text file contains the password !--- definition.

8. Issue the boot command to boot the system.

   switch: bootLoading "flash:c3500xl-c3h2s-mz.120-5.WC7.bin"...#####################################################################################################################################################################################File "flash:c3500xl-c3h2s-mz.120-5.WC7.bin" uncompressed and installed, entry point: 0x3000executing...!--- Output suppressed.!--- This output is from a 3500XL switch. Output from other switches !--- will vary slightly.

9. Enter "n" at the prompt to abort the initial configuration dialog.

   --- System Configuration Dialog ---At any point you may enter a question mark '?' for help.Use ctrl-c to abort configuration dialog at any prompt.Default settings are in square brackets '[]'.Continue with configuration dialog? [yes/no]: n !--- Type "n" for no.Press RETURN to get started.!--- Press Return or Enter.Switch>!--- The Switch> prompt is displayed.

10. At the switch prompt, type en to enter enable mode.

    Switch>enSwitch#

11. Type rename flash:config.old flash:config.text to rename the configuration file with its original name.

    Switch#rename flash:config.old flash:config.textDestination filename [config.text] !--- Press Return or Enter.Switch#

12. Copy the configuration file into memory.

    Switch#copy flash:config.text system:running-configDestination filename [running-config]? !--- Press Return or Enter.1131 bytes copied in 0.760 secsSw1#

    The configuration file is now reloaded.

13. Overwrite the current passwords that you do not know. Choose a strong password with at least one capital letter, one number, and one special character.

    Note: Overwrite the passwords which are necessary. You need not overwrite all of the mentioned passwords.

    Sw1# conf t!--- To overwrite existing secret passwordSw1(config)#enable secret <new_secret_password>!--- To overwrite existing enable passwordSw1(config)#enable password <new_enable_password>!--- To overwrite existing vty passwordSw1(config)#line vty 0 15Sw1(config-line)#password <new_vty_password>Sw1(config-line)#login!--- To overwrite existing console passwordSw1(config-line)#line con 0Sw1(config-line)#password <new_console_password>

14. Write the running configuration to the configuration file with the write memory command.

    Sw1#write memoryBuilding configuration...[OK]Sw1#

This document describes the password recovery procedure for the Cisco Catalyst Layer 2 fixed configuration switches 2900XL/3500XL, 2940, 2950/2955, 2960, and 2970 Series, as well as the Cisco Catalyst Layer 3 fixed configuration switches 3550, 3560, and 3750 Series.

Before You Begin

Conventions

For more information on document conventions, see the Cisco Technical Tips Conventions.

Prerequisites

There are no specific prerequisites for this document.

Step-by-Step Procedure

Follow the password recovery procedure below.

1. Attach a terminal or PC with terminal emulation (for example, Hyper Terminal) to the console port of the switch.

   Use the following terminal settings:

   • Bits per second (baud): 9600

   • Data bits: 8

   • Parity: None

   • Stop bits: 1

   • Flow Control: Xon/Xoff

   Note: For additional information on cabling and connecting a terminal to the console port, refer to Connecting a Terminal to the Console Port on Catalyst Switches.

2. Unplug the power cable.

3. Power the switch and bring it to the switch: prompt:

   For 2900XL, 3500XL, 2940, 2950, 2960, 2970, 3550, 3560, and 3750 series switches, do this:

   Hold down the mode button located on the left side of the front panel, while you reconnect the power cable to the switch.

   Catalyst Switch Series	LED Behavior and Mode Button Release Action
   2900XL, 3500XL, 3550	Release the Mode button when the LED above Port1x goes out.
   2940, 2950	Release the Mode button after approximately 5 seconds when the Status (STAT) LED goes out. When you release the Mode button, the SYST LED blinks amber.
   2960, 2970	Release the Mode button when the SYST LED blinks amber and then turns solid green. When you release the Mode button, the SYST LED blinks green.
   3560, 3750	Release the Mode button after approximately 15 seconds when the SYST LED turns solid green. When you release the Mode button, the SYST LED blinks green.

   Note: LED position may vary slightly depending on the model.

   Catalyst 3524XL

   

   Catalyst 2950-24

   

   For 2955 series switches only:

   The Catalyst 2955 series switches do not use an external mode button for password recovery. Instead the switch boot loader uses the break-key detection to stop the automatic boot sequence for the password recovery purposes. The break sequence is determined by the terminal application and operating system used. Hyperterm running on Windows 2000 uses Ctrl + Break. On a workstation running UNIX, Ctrl-C is the break key. For more information, refer to Standard Break Key Sequence Combinations During Password Recovery.

   The example below uses Hyperterm to break into switch: mode on a 2955.

   C2955 Boot Loader (C2955-HBOOT-M) Version 12.1(0.0.514), CISCO DEVELOPMENT TESTVERSIONCompiled Fri 13-Dec-02 17:38 by madisonWS-C2955T-12 starting...Base ethernet MAC Address: 00:0b:be:b6:ee:00Xmodem file system is available.Initializing Flash...flashfs[0]: 19 files, 2 directoriesflashfs[0]: 0 orphaned files, 0 orphaned directoriesflashfs[0]: Total bytes: 7741440flashfs[0]: Bytes used: 4510720flashfs[0]: Bytes available: 3230720flashfs[0]: flashfs fsck took 7 seconds....done initializing flash.Boot Sector Filesystem (bs:) installed, fsid: 3Parameter Block Filesystem (pb:) installed, fsid: 4*** The system will autoboot in 15 seconds ***Send break character to prevent autobooting.!--- Wait until you see this message before !--- you issue the break sequence.!--- Ctrl+Break is entered using Hyperterm.The system has been interrupted prior to initializing the flash file system to finish loading the operating system software:flash_initload_helperbootswitch:

4. Issue the flash_init command.

   switch: flash_initInitializing Flash...flashfs[0]: 143 files, 4 directoriesflashfs[0]: 0 orphaned files, 0 orphaned directoriesflashfs[0]: Total bytes: 3612672flashfs[0]: Bytes used: 2729472flashfs[0]: Bytes available: 883200flashfs[0]: flashfs fsck took 86 seconds....done Initializing Flash.Boot Sector Filesystem (bs:) installed, fsid: 3Parameter Block Filesystem (pb:) installed, fsid: 4switch:!--- This output is from a 2900XL switch. Output from !--- other switches will vary slightly.

5. Issue the load_helper command.

   switch: load_helperswitch:

6. Issue the dir flash: command.

   Note: Make sure to type a colon ":" after the dir flash.

   The switch file system is displayed:

   switch: dir flash:Directory of flash:/2    -rwx  1803357   <date>               c3500xl-c3h2s-mz.120-5.WC7.bin!--- This is the current version of software.4    -rwx  1131      <date>               config.text!--- This is the configuration file.5    -rwx  109       <date>               info6    -rwx  389       <date>               env_vars7    drwx  640       <date>               html18   -rwx  109       <date>               info.ver403968 bytes available (3208704 bytes used)switch:!--- This output is from a 3500XL switch. Output from !--- other switches will vary slightly.

7. Type rename flash:config.text flash:config.old to rename the configuration file.

   switch: rename flash:config.text flash:config.oldswitch:!--- The config.text file contains the password !--- definition.

8. Issue the boot command to boot the system.

   switch: bootLoading "flash:c3500xl-c3h2s-mz.120-5.WC7.bin"...#####################################################################################################################################################################################File "flash:c3500xl-c3h2s-mz.120-5.WC7.bin" uncompressed and installed, entry point: 0x3000executing...!--- Output suppressed.!--- This output is from a 3500XL switch. Output from other switches !--- will vary slightly.

9. Enter "n" at the prompt to abort the initial configuration dialog.

   --- System Configuration Dialog ---At any point you may enter a question mark '?' for help.Use ctrl-c to abort configuration dialog at any prompt.Default settings are in square brackets '[]'.Continue with configuration dialog? [yes/no]: n !--- Type "n" for no.Press RETURN to get started.!--- Press Return or Enter.Switch>!--- The Switch> prompt is displayed.

10. At the switch prompt, type en to enter enable mode.

    Switch>enSwitch#

11. Type rename flash:config.old flash:config.text to rename the configuration file with its original name.

    Switch#rename flash:config.old flash:config.textDestination filename [config.text] !--- Press Return or Enter.Switch#

12. Copy the configuration file into memory.

    Switch#copy flash:config.text system:running-configDestination filename [running-config]? !--- Press Return or Enter.1131 bytes copied in 0.760 secsSw1#

    The configuration file is now reloaded.

13. Overwrite the current passwords that you do not know. Choose a strong password with at least one capital letter, one number, and one special character.

    Note: Overwrite the passwords which are necessary. You need not overwrite all of the mentioned passwords.

    Sw1# conf t!--- To overwrite existing secret passwordSw1(config)#enable secret <new_secret_password>!--- To overwrite existing enable passwordSw1(config)#enable password <new_enable_password>!--- To overwrite existing vty passwordSw1(config)#line vty 0 15Sw1(config-line)#password <new_vty_password>Sw1(config-line)#login!--- To overwrite existing console passwordSw1(config-line)#line con 0Sw1(config-line)#password <new_console_password>

14. Write the running configuration to the configuration file with the write memory command.

    Sw1#write memoryBuilding configuration...[OK]Sw1#

1.1.1. 장비설정 초기화

Switch# erase startup-config

Switch# reload

1.1.2.  Enable passwd 설정

Switch# config t

Switch(config)# enable secret test

Switch(config)# end

Switch# wr (저장)

1.1.3.  Telnet 접근제어

Switch(config)#line vty 0 4

Switch(config)#password test

Switch(config-line)# access-class 20 in

Switch(config-line)#exit

Switch(config)#access-list 20 permit 200.1.1.1

1.1.4. 레이블링 하기

장비이름 설정

Switch(config)# hostname  test2950

포트에 주석달기       

Switch(config)#int f0/1

Switch(config-if)# description  gr.thseo.com

SW11-Main#show  interfaces  des

1.1.5. 포트속도와 duplex는 수동으로 설정하라

Switch(config)#int range fa 0/23 - 24

Switch(config-if-range)#speed 100

Switch(config-if-range)#duplex full

Switch(config-if-range)#spanning-tree portfast

Switch(config)#show int status  // 인터페이스 상태 확인

1.1.6. 관리용 ip설정

Switch(config)# int VLAN 1

Switch(config-if)# no shut  (필수)

Switch(config-if)# ip address 10.10.10.10 255.255.255.0

Switch(config)#ip default-gateway 10.10.10.254

1.1.7. snmp 설정

Switch(config)# snmp-server community inet ro 12

Switch(config)# access-list 12 permit host 203.255.113.37

- Root-

d0----d10(c0t0d0s0) + d20(c1t0d0s0)(d10, d20 이랑 미러)

- Swap-

d2----d11 + d21(d11, d21이랑 미러)

Step 1. 미러할 대상 하드에 파티션정보 싱크하기

# prtvtoc /dev/rdsk/c0t0d0s0 |fmthard -s - /dev/rdsk/c1t0d0s0

Step 2. 미러구성정보 생성 및 확인
#metadb -a -f -c 3 c0t0d0s3
#metadb -a -f -c 3 c1t0d0s3

* -a : 추가생성시

  -f : 처음생성시 입력하는 옵션

 -c 3 : 복사본 3개를 만들겠다는 뜻

#metadb -i (metadb 등록 정보를 확인)

Step3.  MetaDB 정보생성
#metainit -f d10 1 1 c0t0d0s0

-d10에 c0t0d0s0 할당

- 1 1 : 원본 1개를 사본 1개만 만들겠다는 뜻
#metainit -f d11 1 1 c0t0d0s1

-d11에 c0t0d0s1할당
#metainit -f d20 1 1 c1t1d0s0
#metainit -f d21 1 1 c1t1d0s1

Step4. d0에 d10,d11할당
#metainit d0 -m d10
#metainit d1 -m d11
#metastat -p (metadisk 구성 정보를 확인)

Step 5. Root Main 설정
#metaroot d0

-d0을 Main Root 로 설정

-실행시 /etc/system 에 forceload항목이 생긴다.

-vfstab 파일 수정

Step6. 재부팅

Step7. 미러할 디스크 할당
#metattach d0 d20
#metattach d1 d21
#metastat -p (metadisk 구성정보 최종 확인)
#df -k

--------------------------------------------------------------------------------------
3. 제우스홈/bin/jeus.properties 조정
    - JEUS_WSDIR 부분을 주석처리 하거나 삭제
    - PATH 에서 $JEUS_HOME/webserver 부분도 제거
--------------------------------------------------------------------------------------
4. webtob 와 jeus 를 부팅 후 확인
   http://주소:8080/exapmples/index.jsp 에서 테스팅 페이지 보기
--------------------------------------------------------------------------------------
### DB 연동 ###
--------------------------------------------------------------------------------------
* MySQL 커넥션풀 샘플 (WEBMain.xml에 추가)
JEUS에서 제공하는 ConnectionPool은 JDBC Drive를 통해 얻은 Connection의 관리는 
엔진에서 해주는 것이므로 JDBC Driver를 $JEUS_HOME/lib/datasource 아래에 두고
DBConnectionPool은 container.xml에 DataSource는 JeusMain.xml에 다음과 같이 
설정을 하시면 사용하실 수가 있습니다. 
 
1) DBConnectionPool
------------------------------------------------------------------------------
<DBConnectionPool MaxUseCount="-1" 
                  C 
                  CloseDelayMillis="-1" 
                  MaxActiveTimeSecs="-1" 
                  C 
                  C 
                  DriverClassName="org.gjt.mm.mysql.Driver" 
                  DynamicIncrement="true" 
                  C 
                  LoginDelayMillis="-1" 
                  CloseL 
                  C> 
        <DBPoolControl MaxCapacity="30" 
                   InitCapacity="20" 
                   MaxIdleTimeSecs="300" 
                   IncrementRate="4" /> 
        <DBAConnection ForcedClose="false" />
</DBConnectionPool>
 
 
2) DataSource
------------------------------------------------------------------------------
<DataSource> 
    <Database> 
            <Vendor>others</Vendor> 
            <ExportName>mysql</ExportName> 
            <DataSourceClassName>
                jeus.jdbc.driver.blackbox.BlackboxConnectionPoolDataSource
            </DataSourceClassName> 
            <Property> 
                <Name>URL</Name> 
                <Type>java.lang.String</Type> 
                <Value>jdbc:mysql://localhost:3306/mysql</Value> 
            </Property> 
            <Property> 
                <Name>DriverClassName</Name> 
                <Type>java.lang.String</Type> 
                <Value>com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource</Value> 
            </Property> 
            <Property> 
                <Name>Password</Name> 
                <Type>java.lang.String</Type> 
                <Value></Value> 
            </Property> 
            <Property> 
                <Name>User</Name> 
                <Type>java.lang.String</Type> 
                <Value>root</Value> 
            </Property> 
            <DataSourceType>ConnectionPoolDataSource</DataSourceType> 
            <ConnectionPool> 
                <MinPoolSize>4</MinPoolSize> 
                <MaxPoolSize>4</MaxPoolSize> 
                <IncreasingStep>1</IncreasingStep> 
                <ResizingPeriod>10</ResizingPeriod> 
                <OperationTimeout>30000</OperationTimeout> 
                <WaitForFreeConnection> 
                    <WaitingTime>10000</WaitingTime> 
                </WaitForFreeConnection> 
            </ConnectionPool> 
        </Database> 
  </DataSource>
--------------------------------------------------------------------------------------
* Oracle 커넥션풀 샘플 (JEUSMain.xml의 </node>하단에 추가)
    <resource>
        <data-source>
            <database>
                <vendor>oracle</vendor>
                <export-name>오라클UID</export-name>
                <data-source-class-name>oracle.jdbc.pool.OracleConnectionPoolDataSource</data-source-class-name>
                <data-source-type>DataSource</data-source-type>
                <database-name>디비명</database-name>
                <data-source-name>oracle.jdbc.pool.OracleConnectionPoolDataSource</data-source-name>
                <network-protocol>tcp</network-protocol>
                <user>scott</user>
                <password>tiger</password>
                <port-number>1521</port-number>
                <server-name>아이피 또는 127.0.0.1</server-name>
                <driver-type>thin</driver-type>
                <connection-pool>
                    <pooling>
                        <max>20</max>
                        <step>1</step>
                        <period>500000</period>
                    </pooling>
                </connection-pool>
            </database>
        </data-source>
    </resource>
--------------------------------------------------------------------------------------
* DB2
  1) JEUS 3.x ($JEUS_HOME/config/<NODENAME>/JeusMain.xml
        <Database> 
            <Vendor>db2</Vendor> 
            <ExportName>db2local</ExportName> 
            <DatabaseName>SAMPLE</DatabaseName> 
            <DataSourceClassName>COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource</DataSourceClassName>
            <DataSourceName/> 
            <ServiceName/> 
            <Description/> 
            <NetworkProtocol/> 
            <Password>jeus2013</Password> 
            <PortNumber>포트번호</PortNumber> 
            <ServerName>DB서버 IP</ServerName> 
            <User>db2inst1</User> 
            <DataSourceType>LocalXADataSource</DataSourceType> 
            <ConnectionPool> 
                <MinPoolSize>2</MinPoolSize> 
                <MaxPoolSize>4</MaxPoolSize> 
                <IncreasingStep>1</IncreasingStep> 
                <ResizingPeriod>600000</ResizingPeriod> 
                <OperationTimeout>30000</OperationTimeout> 
                <WaitForFreeConnection> 
                    <WaitingTime>10000</WaitingTime> 
                </WaitForFreeConnection> 
            </ConnectionPool> 
        </Database>  
  2) JEUS 4.x ($JEUS_HOME/config/<NODENAME>/JEUSMain.xml
           <database>
                <vendor>db2</vendor>
                <export-name>db2XADatasource1</export-name>
<data-source-class-name>COM.ibm.db2.jdbc.DB2XADataSource</data-source-class-name>
                <data-source-type>XADataSource</data-source-type>
                <database-name>sample</database-name>
                <description>Customer DB</description>
                <password>db2inst1</password>
                <encryption>false</encryption>
                <port-number>포트번호</port-number>
                <server-name>DB서버 IP</server-name>
                <user>db2inst1</user>
                <connection-pool>
                    <pooling>
                        <min>2</min>
                        <max>4</max>
                        <step>1</step>
                        <period>600000</period>
                    </pooling>
                    <wait-free-connection>
                        <enable-wait>false</enable-wait>
                        <wait-time>10000</wait-time>
                    </wait-free-connection>
                    <operation-to>30000</operation-to>
                </connection-pool>
            </database>
--------------------------------------------------------------------------------------

 
### TIPS ###
--------------------------------------------------------------------------------------
* 파일경로설정
1) 파일 실제경로 (기본값)
- servlet : 제우스홈webhomeservlet_homewebappsexamplesWEB-INFclasses
- jsp : 제우스홈webhomeservlet_homewebappsexamples
2) 기존의 examples 컨텍스트 이외에 새로운 aaa라는 컨텍스트를 추가하는 방법 (컨텍스트 설정법)
- WEBMain.xml에서 다음 부분을 추가한다. 
  <context> 
    <context-name>aaa</context-name> 
    <context-path>/aaa</context-path> 
  </context> 
- aaa 컨텍스트의 DD(deployment descriptor)파일을 작성 
  제우스홈config노드명[SERVLET_ENGINE_NAME]jeus-web-dd_examples.xml 파일을 jeus-web-dd_aaa.xml 파일로 복사  
  하여 편집. context-name, docbase 만 설정하면 됩니다. WEBMain.xml의 이름과 동일해야 함. 
  <?xml versi?> 
  <!DOCTYPE jeus-web-dd PUBLIC "-//Tmax Soft., Inc.//DTD JEUS WEB Deployment Info 4.0//EN" 
                             "http://www.tmaxsoft.com/jeus/dtd/4.0/jeus-web-dd.dtd"> 
  <jeus-web-dd> 
    <context> 
        <context-name>aaa</context-name> 
        <docbase>서버의 물리적 절대경로</docbase> 
        <auto-reload> 
            <enable-reload>true</enable-reload> 
            <check-on-demand>true</check-on-demand> 
        </auto-reload> 
    </context> 
  </jeus-web-dd> 
- WebtoB의 환경설정파일(http.m)의 URI 절에 aaa 컨텍스트 경로를 다음과 같이 추가한다. 
  *URI 
  uri8 Uri = "/aaa/",Svrtype = JSV 
- WebtoB의 환경파일 수정 후에는 반드시 환경파일 컴파일 후 WebtoB를 재기동 : wscfl -i http.m 
- JEUS 를 재기동
 
--------------------------------------------------------------------------------------
* index.jsp를 자동으로 인식시키려면
- 제우스홈config노드명[SERVLET_ENGINE_NAME]webcommon.xml 파일에 index.jsp추가
  <welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
    <welcome-file>index.html</welcome-file>
    <welcome-file>index.htm</welcome-file>
  </welcome-file-list>
--------------------------------------------------------------------------------------
* jspwork 디렉토리 변경
1. JEUS 3.x
$JEUS_HOME/config/<HOSTNAME>/<SERVLET_ENGINE_NAME>/container.xml의
<JSPEngine> 태그 안에 JspWorkDir을 설정하면 됩니다.
<Container>
  ...
  <ContextGroup>
    ...
    <JSPEngine ... 
      JspWorkDir="/app/jwork" 
      ...
    />
2. JEUS 4.x
$JEUS_HOME/config/<HOSTNAME>/<SERVLET_ENGINE_NAME>/WEBMain.xml의
<jsp-engine> 태그 안에 <jsp-work-dir>를 설정하면 됩니다.
<web-container>
  <context-group>
    ...
    <jsp-engine>
      ...
      <jsp-work-dir>/app/jwork</jsp-work-dir>
      ...
    </jsp-engine>
--------------------------------------------------------------------------------------
* 폴더관리 (webtob, jeus 연동시)
- image, js, css, html 등은WebToB홈docs 에 폴더로 관리해서 WEBTOB가 처리
- jsp, servlet은 context를 별도 설정 (컨텍스트 설정법 참조)해서 JEUS가 처리
--------------------------------------------------------------------------------------
* 오라클 데이터베이스 사용시 C:/jeus/lib/datasource 폴더에 classes12.zip 복사
--------------------------------------------------------------------------------------
* trouble shooting
- Out Of Memory 에러
  JVM에서 사용할 수 있는 memory가 부족할 때 발생합니다. 
  이것을 해결하는 방법으로는 버전별로 다음과 같이 JEUS 환경 파일에서
  추가하면 됩니다. -Xms가 min 값이고 -Xmx가 max 값입니다.
  1) JEUS 3.x ($JEUS_HOME/config/<HOSTNAME>/JeusMain.xml)
  <JeusSystemConfig>
      <NodeConfig>
          ...
          <EngineContainer>
              ...
              <CommandOption>-Xms256m -Xmx256m<CommandOption>
  2) JEUS 4.x ($JEUS_HOME/config/<HOSTNAME>/JEUSMain.xml)
  <jeus-system>
      <node>
          ...
          <engine-container>
             ...
              <command-option>-Xms256m -Xmx256m<command-option>
- 노드명에 '-' 문자를 썼을 경우 또는 노드명에 공백이 있는 경우
  wscfl -i http.m 부분에서 오류 -> 노드명을 ""으로 묶어준다.
- 8080포트 사용하려고 할때 XDB 인증창이 뜬다면... 
  =====> 오라클의 XDB포트와 충돌하는 경우이므로 오라클의 XDB포트를 아래와 같이 변경해준다.
  [시작] -> [프로그램] -> [Oracle - OraHome92] -> [Configuration and Migration Tools] 
  -> [Database Configuration Assistant]   선택
  프로그램이 실행이되면.....
  [다음] 버튼을 Click -> [데이터베이스의 데이이터베이스 옵션구성] 선택 -> [사용 가능한 데이터베이스] 선택 
  -> [표준데이터베이  스 기능...] 버튼을 Click -> Oracle XML DB 의 [사용자 정의 ...] 버튼을 Click 
  -> [포트 번호 구성] 항목의 [사용자 정의 값 지정] 을 선택하셔서 HTTP 포트를 바꿔줍니다. 
  그리고 FTP 및 WebDAV 포트는 기본 설정인 2100 을 사용합니다. -> [확인] 버튼을 Click 하시고 
  [다음] 버튼을 Click 하셔서 데이터베이스를 실행할 기본모드를 선택하시고 [완료] 버튼을 눌러주시면 
  요약 메세지창이 뜨고 [확인] 버튼을 눌러주시면 XDB 의 Port 설정이 끝나게 됩니다.
- 다음과 같은 nullpointer exception 발생시
  <<__Exception__>>
  java.lang.NullPointerException
          at javax.servlet.GenericServlet.getServletContext(GenericServlet.java:20
  5)
          at javax.servlet.GenericServlet.log(GenericServlet.java:300)
          at javax.servlet.GenericServlet.init(GenericServlet.java:257)
          at jeus.servlet.common.WebContainerManager.startContainer(WebContainerMa
  nager.java:538)
          at jeus.servlet.syscontext.SystemContext.startup(SystemContext.java:64)
          at jeus.servlet.deployment.SystemWebContainer.startup(SystemWebContainer
  .java:35)
          at jeus.server.SystemEngineController.startEngine(SystemEngineController
  .java:26)
          at jeus.server.JeusServer.boot(JeusServer.java:720)
          at jeus.server.ControlThread.acceptRequests(ControlThread.java:181)
          at jeus.server.ControlThread.run(ControlThread.java:86)
  java.lang.NullPointerException : null
  [SystemEngineController] fail to start System Engine [devserver_system_engine] :
   jeus.server.JeusServerException
  <<__!Exception__>>
  [2005.05.26 10:30:05][2] [ControlThread] command (210.117.198.62:1063) : disconn
  ect()
 =====> j2sdk1.4.1_07 이하 버젼으로 jdk를 다시 설치한 수 jeus/webtob 다시설치 해보세요.
- C:Program FilesJavaj2re1.4.1_07binserverjvm.dll 파일을 찾지 못할때
  =====> C:j2sdk1.4.1_07jrebinserver 폴더를 카피해서 
             C:Program FilesJavaj2re1.4.1_07bin 폴더에 복사하세요.
--------------------------------------------------------------------------------------
* 클래스파일 변경시 실시간으로 변경 반영
소스가 WEB-INF/classes 아래에 있으면 리부팅이 필요 없습니다. 
단, 확인 하실 것이 container.xml(WEBMain.xml)에 context 태그 내에 AutoReload="true"가 설정되어 있으면 됩니다.
WEB-INF/lib/*.jar는 라이브러리와 같이 수정하지 않는다는 의미를 포함하고 있으므로(J2EE 스펙에 준하면...) 
jar 파일 내의 수정은  반드시 제우스를 리부팅 해야 적용됩니다.
--------------------------------------------------------------------------------------
* 인클루드된 파일 변경시 즉시 적용(<%@ include 자동 반영하기)
JSP의 include의 방식에는 <%@ include (action), <jsp:include (directive) 가 있다.
이 중 <jsp:include (action) 는 include하는 JSP(a.jsp)와 include되는 JSP(b.jsp)가 각각 별도의 servlet으로 변환된다.
a.jsp가 수행 도중 b.jsp의 include 구문을 만나면 b.jsp로 제어권이 넘어가서 수행된 후 다시 a.jsp로 제어권이 넘어와서 계속 수행된다.
그래서 b.jsp가 변경된 경우 변경사항이 자동으로 반영된다.
그리고 <%@ include (directive)는 include하는 JSP(a.jsp)와 include되는 JSP(b.jsp)가  하나의 servlet으로 변환되어서 a.jsp 내에 b.jsp가 완전히 포함되는 형태로 변환된다.
<%@ include (directive)의 목적은 JSP가 Servlet으로 변환되어 컴파일 될 때에
특정 코드나 text를 포함하기 위해서 이다.
따라서 b.jsp가 변경된 경우 a.jsp는 b.jsp가 변경되었는지 모르기 때문에 include 된 JSP의 변경시 이것을 인지하지 못한다.
<%@ include (directive) 를 사용하는 경우 JSP container가 include된 파일이 변경된 경우 자동으로 반영해 주기 위해서는 include하는 파일이 수행될 때 마다 include된 파일의 변경 여부를 검사해서 변경되었다면 include 하는 파일을 recompile 해 주어야 한다.
이것은 JSP container에게는 상당히 부하를 주는 작업이다.
그래서 JSP Spec에서는 include된 파일의 변경시 반영 여부는 명시하지 않고 있다.
JEUS에서는 개발과 운영의 편의성을 위해서 이것을 옵션으로 지정하여 변경시 자동 반영이 되게 설정할 수 있다.
하지만 이 옵션을 true로 설정하는 경우 불필요한 검사가 들어가게 되므로 수행 속도에 지장을 주게됩니다. 반드시 JSP 파일의 변경이 빈번한 경우에만 설정하면 된다.
1. JEUS 3.x
$JEUS_HOME/config/<HOSTNAME>/<SERVLET_ENGINE_NAME>/container.xml에 설정
---------------------------------------------------------
<Container>
    ...
    <ContextGroup>
        ...
        <JSPEngine ...
            CheckIncludedJspFile="true"
            ... />
2. JEUS 4.x
$JEUS_HOME/config/<HOSTNAME>/<SERVLET_ENGINE_NAME>/WEBMain.xml에 설정
---------------------------------------------------------
<web-container>
    ...
    <context-group>
        ...
        <jsp-engine>
            ...
            <check-included-jspfile>true</check-included-jspfile>
            ...
        </jsp-engine>
        ...
    </context-group>
    ...
</web-container>
--------------------------------------------------------------------------------------
* http.m 샘플
*DOMAIN
WebtoB
*NODE
devserver WEBTOBDIR="C:/webtob", 
  SHMKEY = 54000,
  DOCROOT="C:/tmax/webdocs",
  IndexName="index.jsp,index.html,index.htmm",
  PORT = "80", 
  LOGGING = "log1",
  ERRORLOG = "log2",
  HTH = 1,
  JSVPORT = 9900
*SVRGROUP
htmlg  NODENAME = devserver, SvrType = HTML
cgig  NODENAME = devserver, SVRTYPE = CGI
ssig  NODENAME = devserver, SVRTYPE = SSI
jsvg  NODENAME = devserver, SVRTYPE=JSV
*SERVER
html  SVGNAME = htmlg, MinProc = 3, MaxProc = 10
cgi  SVGNAME = cgig, MinProc = 3, MaxProc = 10
ssi  SVGNAME = ssig, MinProc = 3, MaxProc =10
MyGroup  SVGNAME=jsvg, MinProc=10, MaxProc=10
*URI
uri1  Uri = "/cgi-bin/", Svrtype = CGI
uri2  Uri="/examples/", Svrtype=JSV
uri3  Uri="/", Svrtype=JSV
*ALIAS
alias1  URI = "/cgi-bin/", RealPath = "C:/webtob/cgi-bin/"
*LOGGING
log1  Format = "DEFAULT", FileName = "C:/webtob/log/access.log", Option = "sync"
log2  Format = "ERROR", FileName = "C:/webtob/log/error.log", Option = "sync"
*EXT
htm  MimeType = "text/html", SvrType = HTML
--------------------------------------------------------------------------------------
* JEUSMain.xml 샘플
<?xml versi?>
<!DOCTYPE jeus-system PUBLIC "-//Tmax Soft, Inc.//DTD JEUS Main Config 4.0//EN"
                             "http://www.tmaxsoft.com/jeus/dtd/4.0/jeus-main-config.dtd">
<jeus-system>
    <node>
        <name>devserver</name>
        <class-ftp>true</class-ftp>
        <sequential-start>true</sequential-start>
        <enable-webadmin>true</enable-webadmin>
        <system-log>
            <level>debug</level>
        </system-log>
        <engine-container>
            <name>container1</name>
            <engine-command>
                <type>servlet</type>
                <name>engine1</name>
                <startup-mode>xml</startup-mode>
            </engine-command>
            <tm-config>
                <pooling>
                    <min>10</min>
                    <max>20</max>
                    <step>2</step>
                    <period>600000</period>
                </pooling>
                <active-timeout>300000</active-timeout>
                <commit-timeout>120000</commit-timeout>
                <capacity>20000</capacity>
            </tm-config>
        </engine-container>
    </node>
</jeus-system>
--------------------------------------------------------------------------------------
* WEBMain.xml 샘플
<?xml versi?>
<!DOCTYPE web-container PUBLIC "-//Tmax Soft., Inc.//DTD WEB Main Config 4.0//EN"
                               "http://www.tmaxsoft.com/jeus/dtd/4.0/web-main-config.dtd">
<web-container>
    <context-group>
        <group-name>MyGroup</group-name>
        <group-docbase>webapps</group-docbase>
        <session-config>
            <timeout>20</timeout>
            <shared>true</shared>
        </session-config>
        <logging>
            <error-log>
                <target>stdout</target>
                <level>information</level>
                <buffer-size>0</buffer-size>
                <valid-day>1</valid-day>
            </error-log>
            <user-log>
                <target>file</target>
                <buffer-size>0</buffer-size>
                <valid-day>1</valid-day>
            </user-log>
            <access-log>
                <target>file</target>
                <buffer-size>0</buffer-size>
                <valid-day>1</valid-day>
                <log-format>
                    <time-format>default</time-format>
                </log-format>
            </access-log>
        </logging>
        <context>
            <context-name>examples</context-name>
            <context-path>/examples</context-path>
        </context>
  <context> 
   <context-name>ngi</context-name> 
   <context-path>/</context-path> 
  </context> 
        <webserver-connection>
            <webtob-listener>
                <listener-id>webtob1</listener-id>
                <port>9900</port>
                <hth-count>1</hth-count>
                <webtob-address>127.0.0.1</webtob-address>
                <registration-id>MyGroup</registration-id>
                <thread-pool>
                    <min>4</min>
                    <max>10</max>
                    <step>2</step>
                    <max-idle-time>30000</max-idle-time>
                    <max-wait-queue>4</max-wait-queue> 
                </thread-pool>
            </webtob-listener>
        </webserver-connection>
    </context-group>
</web-container>
--------------------------------------------------------------------------------------
### 실무 적용 예 (버츄얼호스팅 사용) ###
-------------------------------------------------------------------------------------- 
프로젝트 실제환경을 로컬에서 구현해 작업해야 하는 상황에서...
두대의 IBM서버로 돌아가는 JEUS/WEBTOB의 환경설정 입니다.
<<< 실제환경 >>>
---------------------------------------------------------------------------
- 서버1 : WindowsServer2003Standard, 웹서버 (WEBTOB)
- 서버2 : WindowsServer2003Standard, 웹컨테이너 (JEUS), DB(Oracle9i)
- 두 서버는 9999포트를 통해 연동한다.
- images,css,js는 서버1에 jsp,java는 서버2에 위치시킨다.
- 서버구조는 1 WEBSERVER, 2 CONTAINER (원래 4개에서 필요한 두개만 가동)
- 윈도우 hosts파일에 localhost2, localhost3 추가
----------------------------------------------------------------------------
<<< sample.m >>>
*DOMAIN
WebtoB
*NODE
realchokyCompaq
  WebtobDir="C:/webtob",
  Shmkey=54000,
  Docroot="C:/center",
  HTH=1,
  port="9900",
  JSVPort=9999,
  IndexName="index.jsp,index.htm,index.html",
  Logging="log1",
  ErrorLog="log2"
*VHOST
center
  NodeName="realchokyCompaq",
  HostName="localhost2",
  DocRoot="C:/center",
  Port="9900",
  SSLFlag=N,
  IndexName="index.jsp,index.htm,index.html"
admin
  NodeName="realchokyCompaq",
  HostName="localhost3",
  DocRoot="C:/admin",
  Port="9900",
  IndexName="index.jsp,index.htm,index.html"
*SVRGROUP
htmlg
  NodeName="realchokyCompaq",
  SvrType=HTML
jsvg
  NodeName="realchokyCompaq",
  SvrType=JSV,
  VHostName=center
jsvg2
  NodeName="realchokyCompaq",
  SvrType=JSV,
  VHostName=admin
*SERVER
html
  SvgName=htmlg,
  MinProc=30,
  MaxProc=60
Center
  SvgName=jsvg,
  MinProc=30,
  MaxProc=30,
  HttpInBufsize=0,
  HttpOutBufsize=0
Admin
  SvgName=jsvg2,
  MinProc=10,
  MaxProc=10,
  HttpInBufsize=0,
  HttpOutBufsize=0
*URI
images
  Uri="/images/",
  SvrType=HTML
center
  Uri="/",
  SvrType=JSV,
  VhostName=center
admin
  Uri="/",
  SvrType=JSV,
  VhostName=admin
*LOGGING
log1
  FileName="C:/webtob/log/access.log",
  Format="DEFAULT",
  Opti
log2
  FileName="C:/webtob/log/error.log",
  Format="ERROR",
  Opti
*EXT
htm
  Mimetype="text/html",
  Svrtype=HTML
jsp
  Mimetype="application/jsp",
  Svrtype=JSV
<<< JEUSMain.xml >>>
<?xml versi?>
<!DOCTYPE jeus-system PUBLIC "-//Tmax Soft, Inc.//DTD JEUS Main Config 4.0//EN"
                             "http://www.tmaxsoft.com/jeus/dtd/4.0/jeus-main-config.dtd">
<jeus-system>
    <node>
        <name>realchokyCompaq</name>
        <class-ftp>true</class-ftp>
        <sequential-start>true</sequential-start>
        <system-log>
            <level>debug</level>
        </system-log>
        <engine-container>
            <name>container1</name>
            <engine-command>
                <type>servlet</type>
                <name>engine1</name>
                <startup-mode>xml</startup-mode>
            </engine-command>
            <tm-config>
                <pooling>
                    <min>10</min>
                    <max>20</max>
                    <step>2</step>
                    <period>600000</period>
                </pooling>
                <active-timeout>300000</active-timeout>
                <commit-timeout>120000</commit-timeout>
                <capacity>20000</capacity>
            </tm-config>
        </engine-container>
        <engine-container>
            <name>container2</name>
            <engine-command>
                <type>servlet</type>
                <name>engine2</name>
                <startup-mode>xml</startup-mode>
            </engine-command>
            <tm-config>
                <pooling>
                    <min>10</min>
                    <max>20</max>
                    <step>2</step>
                    <period>600000</period>
                </pooling>
                <active-timeout>300000</active-timeout>
                <commit-timeout>120000</commit-timeout>
                <capacity>20000</capacity>
            </tm-config>
        </engine-container>
    </node>
    <resource>
        <data-source>
            <database>
                <vendor>oracle</vendor>
                <export-name>오라클UID</export-name>
                <data-source-class-name>oracle.jdbc.pool.OracleConnectionPoolDataSource</data-source-class-name>
                <data-source-type>DataSource</data-source-type>
                <database-name>디비명</database-name>
                <data-source-name>oracle.jdbc.pool.OracleConnectionPoolDataSource</data-source-name>
                <network-protocol>tcp</network-protocol>
                <user>아이피</user>
                <password>패스워드</password>
                <port-number>1521</port-number>
                <server-name>아이피 혹은 127.0.0.1</server-name>
                <driver-type>thin</driver-type>
                <connection-pool>
                    <pooling>
                        <max>20</max>
                        <step>1</step>
                        <period>500000</period>
                    </pooling>
                </connection-pool>
            </database>
        </data-source>
    </resource>
</jeus-system>
<<< WEBMain.xml (컨테이너 1) >>>
<?xml versi?>
<!DOCTYPE web-container PUBLIC "-//Tmax Soft., Inc.//DTD WEB Main Config 4.0//EN"
                               "http://www.tmaxsoft.com/jeus/dtd/4.0/web-main-config.dtd">
<web-container>
    <context-group>
        <group-name>Center</group-name>
        <group-docbase>webapps</group-docbase>
        <servlet-home>c:</servlet-home>
        <context>
            <context-name>Cen



출처 : [WebToB]와 [JEUS]의 설치및 연동

# cat a b c d e > dvd.iso

윈도우에서는 

C:\> copy /b a + /b b + /b c + /b d + /b e dvd.iso