| ì¥ 1 | | | | (TM) ì ì±ì |
| ìê°: - | | | | ë³´ì¥í-ëS" ì무를 |
| í´ë¼ì´ì-¸íS¸ | | | | ê°ì ¸ì¨ë¤. |
| ìë² ê°ì¥ | | | | í´ë¼ì´ì-¸íS¸ |
| ìë¡ì´ ì»´í"¨í° | | | | ìë² ë¯¸ë"¤ì¨ì-´: - |
| ì°ì-... ë° ê°ì¥ | | | | ì°ë¦¬ëS" |
| ë¨ê±°ì´ ì 문ì ì | | | | í´ë¼ì´ì-¸íS¸ |
| í-ì-´ì í-ê°ëS" | | | | ìë² |
| ì´ë¤. ì±ê²©, ë°ì , | | | | 미ë"¤ì¨ì-´ë¥¼ |
| ë° anticipateologiesì depist | | | | ë¤ìê³¼ ê° (TM) ì ì |
| ì ì¬ì©ë ëë¡ | | | | -ìí-ë¤: |
| í´ë¼ì´ì-¸íS¸ | | | | í´ë¼ì´ì-¸íS¸ |
| ìë²ì ì¼ë°ì | | | | ìë² ì- |
| ì¸ ì -ìê° ì-ë¤. | | | | í"리ì¼ì´ì... |
| ê·¸ë¬ë ì¼ë° | | | | ìí"íS¸ì¨ì-´ì |
| ì-ì´ë""ì-´ëS" | | | | ë¶ë¦¬ëëS" |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | ë¶ë¶ì ì§ìí-ê³ |
| ìë²ê° ì-...무를 | | | | í-¨ê» ì¼í-ëS" |
| ë¬ì±í-기 ìí-ì-¬ | | | | ê°ëS¥í-ê² í-ëS" |
| ë¤íS¸ìí¬ì- | | | | í¬ì¥ë |
| 주ì를 í-¨ê» ì'ë | | | | ìí"íS¸ì¨ì-´. |
| (TM) í-ëS" ë¶ë¦¬ëëS" | | | | ì´ê²ì í¨ì"¬ |
| ë...¼ë¦¬ | | | | í´ë¼ì´ì-¸íS¸ |
| ì-"í°í°ì´ë¤ | | | | ìë² ê¸°ì ì |
| ì´ë¤. | | | | ê°ì¥ ë³µì¡í- |
| í´ë¼ì´ì-¸íS¸ | | | | ì§ì-ì´ë¤. |
| ìë²ëS" ì-주 ì í- | | | | ì-¬ê¸°ì-ì |
| ì´ë¤. ë"±ê³¼ ê° (TM) | | | | ë³µí-©ì±ì- |
| ì, ë¤ë§ ììì | | | | ì§'ì¤'í-´ì ì°ë¦¬ëS" |
| ì¸ ì¼ìì ì | | | | ë¤ë¥¸ ì§ì-ì |
| í-ì¼ì§ë | | | | ê´ê³ë ê°ë¨í- |
| 모르ë¤; ê·¸ë¬ë | | | | ì ì§í- ì ìë¤. |
| 기본 ì ì´ê³ | | | | ê·¸ê² ìì²´ |
| ê´'ë²"ìí- | | | | ê°ê°ì´ ë°°ë¶ë |
| 무ì-¸ê°ì´ë¤ | | | | ì§ë 모른ë¤, |
| ì¼ë°ì ì¸ | | | | ê·¸ë¦¬ê³ |
| ìS¹ì¸ì´ ìë¤; | | | | ìµëëì´ ìë¡ |
| ì를 ë"¤ë©´, Gartner | | | | ê´ê³ë¥¼ ê°ì§ëS" |
| 그룹ì ì´ | | | | í¬í-¨í-ë¤ ê¸°ëS¥ì |
| ë¶ì-¼ì- ìëS" 주ì" | | | | ë§ì ì¢...ë¥ë¥¼. |
| ì°ì-... ë¶ìê°ì¸, | | | | ì-´ë-¤ìì 주ì" |
| ì ê²ì ìì-¸í-ë¤ | | | | ì§ì-: |
| "1995ë... | | | | ⢠ë¤íS¸ìí¹ |
| í´ë¼ì´ì-¸íS¸ | | | | ìë¹ìS¤ |
| ìë²ê¹ì§ | | | | ⢠ë¶ì° ì- |
| ì´ììì¤ | | | | í"리ì¼ì´ì... |
| ê³ì°ì ìí- ë (TM) | | | | ìë¹ìS¤ |
| ìì-´." ì²ì | | | | ⢠ë¶ì° ììS¤í... |
| í´ë¼ì´ì-¸íS¸ | | | | ê´ë¦¬ |
| ìë² ì±ê³µë´ì | | | | â¢ëS" ì-ì ì |
| ëë¶ë¶ì ì ì° | | | | ë°°ë¶í-ë¤ |
| ì²´ê³ì- ìëS" | | | | â¢ëS" 목í' |
| ì²ë¦¬ ìë£ì- ì§ì | | | | ê´ë¦¬ë¥¼ |
| ' ì ì´ê³ ê°ì ' | | | | ë°°ë¶í-ë¤ |
| ì-¡ì¸ìS¤ë¥¼ ì | | | | ⢠ì¬ì©ì |
| ê³µí-ëS" ìê·ëª¨ | | | | ì¸í°íì´ìS¤ |
| ì ì²ì | | | | ê´ë¦¬ |
| í¬í-¨í-ë¤. ê²°ì - ì | | | | ⢠ì¸ì ê´ë¦¬ |
| ì'ìì- ë°ì´í ì | | | | ⢠ë°ì´í° ê´ë¦¬ |
| 'ê·¼ì, | | | | ⢠거ë ê´ë¦¬ |
| í´ë¼ì´ì-¸íS¸ | | | | ⢠ì'ì-... íë¦ |
| ìë² ê³µêµ¬ ë° | | | | ê´ë¦¬ ì«ì 4ëS" |
| 기ì ì ê´ê³ëëS" | | | | í´ë¼ì´ì-¸íS¸ |
| 미ì (TM) ì ê³µí-ëS", | | | | ìë² ì- |
| ì¬ì-... í-ì" ê´'ì- | | | | í"리ì¼ì´ì... |
| ë¤íS¸ ìí¬ì ì§í | | | | ìí"íS¸ì¨ì-´ë¥¼ |
| (TM) " ì¬ì© ë° | | | | ìí- ì´ |
| í´ë¼ì´ì-¸íS¸ | | | | 미ë"¤ì¨ì-´ |
| ìë² ì 문 기ì | | | | ì§ìì ìì§- |
| ì ë¶ì¡±ì ì´ | | | | ëí'ì´ë¤. |
| ë§¤ë ¥ ê·¸ë¬ë ì | | | | ê·¸ê²ì |
| ìí- ì-ë´í-ëS" | | | | í´ë¼ì´ì-¸íS¸ |
| í-©ì'ì ë§ë" ë¤. | | | | ìë² ê¸°ì ì |
| ì¡°ì§ì´ ì±ê³¼ | | | | ì¬ì©ìì |
| ì¤'ì ì ì²ì¼ë¡ | | | | ì-...무ì- ì ë¹í- ì |
| ì´ ìê·ëª¨ í"ë¡ì | | | | ì²´ ì¬ì-... ë²"ìì |
| íS¸ì-ì í- (TM) ìSµ | | | | ë§ìí¸ì- ì'ë (TM) |
| 곡ì ì ìë¡ | | | | í-ëS" ê°ëS¥í-ê² |
| ì´ë (TM) í-ê³ ê¸° | | | | í-기ì- ìëS" |
| ë-문ì-, ì±ê³¼ | | | | 미ë"¤ì¨ì-´ì |
| 기ë, ê°ë (TM) | | | | ì¤'ì"ì±ì |
| ìê° | | | | ê°-ì¡°í-ë¤. |
| í-ì"ì¡°ê±´ê³¼ ê°ë | | | | ì´ê²ì 기ì-... |
| (TM) ê°ëS¥í-기ë | | | | ê²½ê³ì |
| í-ê³ ì¤ë¥¼ ì ì | | | | ë§ìí¸ì- |
| ë¨ì- ìëS" | | | | ë¶ë¬¸ê³¼ 기ëS¥ì |
| í-ì"ì-ì ëì' | | | | ì¸ ê²½ê³ì |
| ì¦ê°ê° ìë¤. | | | | ë§ìí¸ì- ìí¸ |
| ê·¸ë° ì§ëì¹ê² | | | | ì'ì©ì, ê·¸ë¦¬ê³ |
| ì"구í-ëS" | | | | ì-ë§ í¬í-¨í- ì§ë |
| ë본ì-ìëS", ì | | | | 모른ë¤. |
| í-©í- ê±´ì¶-ì ì ì | | | | ì«ì 4 |
| í ê·¸ë¦¬ê³ | | | | í´ë¼ì´ì-¸íS¸ |
| ì¤ìëS" 긴ì"í-ê² | | | | ìë² ë¯¸ë"¤ì¨ì-´ |
| ëë¤. ì¤ì ë¡ | | | | í´ë¼ì´ì-¸íS¸ |
| ê°ì-...ìê° ê±´ì¶-ì | | | | ìë²ëS" ëêµ¬ë¡ |
| ì´ ì´ í"ë¡ì | | | | ë§ë"¤ê³ |
| íS¸ë¥¼ ìí-´ ë" ì | | | | ìë¹ìS¤í-ë¤: - |
| ë¹í- ê° | | | | í´ë¼ì´ì-¸íS¸ |
| í´ë¼ì´ì-¸íS¸ | | | | ìë² ì²´ê³ëS" |
| ìë² í"ë¡ì íS¸ì | | | | ë³µì¡í- ê²ì´ |
| ìì'ì-ì (TM) | | | | ì§ë 모르ì§ë§, |
| ì¸ìì-¼ í-ëS" | | | | ì íµí-© ì²´ê³ ë° |
| 기본ì ì¸ | | | | ì ì¤ê³ëëS" |
| ì§ë¬¸ì í-ê° - "- | | | | ì¬ì©ì |
| 2ì¤' ëëS" 3 층ì?" | | | | ì¸í°íì´ìS¤ë¡ |
| ì´ë¤. ì¬ë¯¸ì, | | | | 기ì ì ì¸ |
| 모ë" ì±ê³¼ ì¤'ì | | | | ë³µí-©ì±ì |
| í´ë¼ì´ì-¸íS¸ | | | | ì¬ì©ìì-ê² |
| ìë² ì ì²ì 17%ëS" | | | | ë³´ì´ë©´ ì-ëë¤; |
| 층층 3ì´ê³ ë (TM) | | | | 근본ì ì¼ë¡ |
| í-¥ì Standish Group | | | | ì'ì© í"ë¡ê·¸ë¨ |
| International, Inc. ì ìì¥ | | | | ê°ë°ì ë° |
| ì¡°ì¬ ë¨ì²´ì- | | | | ìë¹ìS¤ ì |
| ë"°ë¥´ë©´, ì±ì¥í-ê³ | | | | ê³µì를 ìí- |
| ìë¤. ê±´ì¶-ì ì | | | | 문ì ì´ë¤. |
| ìí"íS¸ì¨ì-´ | | | | ê·¸ë"¤ì |
| ë""ìì¸ê³¼ 기ì | | | | ìí"íS¸ì¨ì-´ ê°ë° |
| ì¤ê³ì 모ë" | | | | 공구ì (TM) ì 문ì |
| ì-'ìì- ìí-¥ì | | | | ì¸ ì-...무를 ì´ |
| 미ì¹ë¤. | | | | ë³µí-©ì±ì |
| ê±´ì¶-ê°ëS" ì ì²ì | | | | ì²ë¦¬í-ê³ ì¨ê¸°ëS" |
| ë³µí-©ì±, | | | | ê²ì ë-ëS" í-ì"ë¡ |
| ì-í¤í...ì² ì í-ì- | | | | í-ë¤. í-ì"ë¡ í- |
| ê²°ì -í-기 ì ì-, | | | | ì-¸ì ë 공구 ë° |
| ì¬ì©ìì ì, | | | | ìë¹ìS¤ì ë§ì |
| ë¤íS¸ìí¬ì | | | | ê²ì ë (TM) ì¼í-, |
| ê·¸ë"¤ì ì§ë¦¬ì | | | | ê·¸ë¬ë ëí- |
| ì¸ ë¶ì°, ë³¸ì§ | | | | í´ë¼ì´ì-¸íS¸ |
| ë° ì ì²ì ì ë°ì | | | | ìë² ì²´ê³ì- |
| ì¸ ì²ë¦¬ í-ì"를 | | | | í-ì"ë¡ í-ë¤ |
| ì"구ë íµí-©ê³¼ | | | | íS¹ì±ì ìë¤. |
| ì¡°í (TM) "ìí¤ê¸°ì | | | | ì¤'ì"í- ì¼ë°ì ì¸ |
| ìì¤ ê³ ë ¤í-ë¤. | | | | ì ì í¬ì¥í- |
| ë¶ì ë¹í- ê±´ì¶- | | | | ("shrink-wrapped") ì'ì© |
| ì¤ê³ ëëS" | | | | ìí"íS¸ì¨ì-´, |
| ììëëS" ì¤ìëS" | | | | 기ì-...ì´ |
| 쯤ì°í- ì'ëµ | | | | í"ë¡ê·¸ë¨ ê±´ì¶- |
| ìê° ê·ì°©ë ì | | | | 공구를 í-ì"ë¡ |
| ìì-ë¤. ê±´ì¶-ì | | | | í-ì§ ì-SëS" |
| ì ì íì ëí- | | | | ì¬ì©ì를 ìí-´ ì |
| ì ì²ì ê°ë° | | | | ê²ì´ë¤. í¬ì¥í- |
| ìê°ì- ë° ë¯¸ë | | | | í´ë¼ì´ì-¸íS¸ |
| ìµíµì± ë° ì -ë¹ | | | | ìë² ì- |
| ìí-¥ì 미ì¹ë¤. | | | | í"리ì¼ì´ì... ì |
| íì¬ ë¬¸í- (TM) ì | | | | í'ì ì§ê¸ ë"ê² |
| 충ë¶í-ê² | | | | ì í¨í-ê² ëê³ |
| í´ë¼ì´ì-¸íS¸ | | | | ìë¤ (ì를ë"¤ë©´ |
| ìë² ê±´ì¶-ì ì | | | | ë¶ë°°ë |
| ì´ ì-'ìì 모ë" | | | | ì¬ë¬´ì¤ê³¼ |
| ë¤ë£¨ì§ ì-SëS"ë¤. | | | | 그룹ì¨ì-´ ì ì², |
| ì´ ìë¥ëS" | | | | ì¬ì-... íê³ ì ì², |
| í´ë¼ì´ì-¸íS¸ | | | | ì¸ì ë° ê¸ì-¬ë¶ |
| ìë² ê±´ì¶-ì ì | | | | ì ì²). ë ë¤ë¥¸ |
| 기본 ê°ë...ì ì | | | | ì¤'ì"í- ë (TM) í-¥ì |
| -ìí-ê³ , 2ì¤' 3 층 | | | | ë¤ë¥¸ 공구 (ë° |
| ê±´ì¶-ì ì 기ì | | | | ì-¸ì-´) 모ë"ë¼ |
| í-ê³ ê·¸ë"¤ì | | | | ì'ì© ììS¤í...ì |
| ê°ê° ì´ë" ë° ì | | | | ë¤ë¥¸ ë¶ë¶ì |
| í-ì ë¶ìí-ë¤. | | | | ìí-´ í-ì"í-ë¤ëS" |
| ì¬ì¬ì©ì ê°ë° | | | | ê²ì ì´ë¤. 주ì" |
| ë...¸ë ¥, ìµíµì± ë° | | | | 구ë³ì: |
| ì©ì´í-¨ì- ìëS" | | | | ⢠ì¬ì©ì |
| ë¤ë¦ì ëí- | | | | ì¸í°íì´ìS¤: |
| ì-´ë-¤ 주ì-´ì§ | | | | ê·¸ëí"½ ì¬ì©ì |
| í"ë¡ì íS¸ë" ì§ë¥¼ | | | | ì¸í°íì´ìS¤ì |
| ìí- ì í-©í- | | | | ê±´ì¶- ë° ì-´ë-¤ ì |
| ê±´ì¶-ì ì ì í | | | | ì² ë...¼ë¦¬ë" ì§ë¥¼ |
| ë"를 ë³´ì¡°í-기 | | | | ìí- ì-¸ì-´ ê·¸ë¦¬ê³ |
| ìí-ì-¬ | | | | 공구ëS" ê·¸ë"¤ |
| ë¹êµëë¤. | | | | ì¹ë°í-ê² ê´ë |
| ì¥ 2 | | | | ¨ìì¼°ë¤; |
| ì-ì¬ & defintion: - | | | | ì를ë"¤ë©´ GUI |
| ì-ì¬ëS" ìí¸ë£¨ì | | | | 공구ì (TM) Visual Basic. |
| ëí- (TM) 1996ë...ì | | | | ⢠ë°ì´íë² |
| 5ì"ì-ì Oracle ì -ë¶ | | | | ì´ìS¤: ì ì² |
| ê¸ìµ (OGF)를 | | | | ë...¼ë¦¬ì |
| ì¤í-í-ë¤. Solaris | | | | ë°ì´íë² ì´ìS¤ì |
| ëëS" ì ëìS¤ í (TM) | | | | ê±´ì¶-ì ìí- ì-¸ì-´ |
| ê²½ì- ê·¸ë¦¬ê³ | | | | ê·¸ë¦¬ê³ ê³µêµ¬ëS", |
| ë©ë¦¬ IBM/VMì- | | | | íì¼ ììS¤í... ë° |
| íì§ì- ê°ë°ë | | | | 목í' ìì ë° |
| í¬ì¥ì-ì | | | | ê±´ì¶- ê·¸ë"¤ |
| ë©í'ì-...ì | | | | ì¹ë°í-ê² ê´ë |
| ì§ìë í¬ì¥ì- | | | | ¨ìì¼°ë¤; |
| ì´ë (TM) ë UWì | | | | ì를ë"¤ë©´ ìë£ |
| ì¤'í-µ íê³ ì ë. | | | | ì¡°ì' ì-¸ì-´ì (TM) |
| ê³íì ê·¸ë- (ê·¸ë | | | | ê´ê³í- ë°ì´íë² |
| ì§ ì-Sì¼ë©´ 모ë" ) | | | | ì´ìS¤ 4GLs. |
| ì¬ì-... ì²´ê³ë¥¼ ë" | | | | ⢠ë¹ì¦ëìS¤ |
| ë¨ í-ë | | | | ë¡ì§: ì¬ì©ì |
| ë©í'ì-...ìë¡ ì´ë | | | | ì¸í°íì´ìS¤ì (TM) |
| (TM) í-ê³ ë¨ í-ë | | | | ë°ì´íë² |
| ë°ì´íë² ì´ìS¤ | | | | ì´ìS¤ì-ì |
| í"ëíS¸í (TM) (ë' | | | | ë¶ë¦¬ëì-´ ë...¼ë¦¬ì |
| ë¤ë¥¼ ìí- Oracle)ì- | | | | ì¼ë¡ ì¸ ì ì² |
| í'ì¤í (TM) "í-기 | | | | ë...¼ë¦¬ì ê±´ì¶-ì |
| ìí- ê²ì´ì-ë¤. | | | | ìí- ì-¸ì-´ ê·¸ë¦¬ê³ |
| ì-주 í° ìµì ì | | | | 공구; ì를ë"¤ë©´ |
| Solaris ì²´ê³ëS" OGF를 | | | | COBOL. |
| ê°ì§ ë (TM) ì¼í- | | | | ⢠ë¶ì° ì²ë¦¬: |
| ì²´ê³ì- ì´ ë¤ë¥¸ | | | | ì-¸ì-´ì (TM) 공구ëS" |
| Oracleì- ìí-ì-¬ | | | | ë¶ì° ì²ë¦¬ |
| ê³µê¸ë ìë¹ìS¤ CO | | | | ê·¸ë¦¬ê³ ëª¨ë" |
| ìì¹ì ë...¸ë | | | | ì기 기ëS¥ |
| ¥ì¼ë¡ | | | | ì-ì-´ë¦¬ì-´ ì 문í (TM) |
| 구매ëì-ë¤. í-ì - | | | | "í-ë¤ (ì (TM) ë¤ë¥¸ |
| ë¤íS¸ìí¬, ìì | | | | ê³¼í- (TM) 기ì ê³¼ |
| -ì ì-¬ê³¼ê¸°ì (TM) í | | | | ì¡°ì§ ê²½ê³ë¥¼) |
| (TM) ë (TM) ì ì¸ | | | | ë¼ì¼ë¡ ì¬ê¸°ë¥¼ |
| ìíµë ê°ì를 | | | | ìí-´; ì를ë"¤ë©´ |
| ê°ì§ ê·¸ | | | | ì격 í"ë¡ìì |
| ë¤íS¸ìí¬ë¥¼ | | | | í¸ì¶ (RPC) 공구. |
| ë²½ì¼ë¡ ë§ëS" | | | | ⢠ììS¤í... ê´ë¦¬: |
| ë¶ì ê³ ë¦½ìí¤ëS" | | | | ìí"íS¸ì¨ì-´ì ì |
| í¬í-¨í- ë¤íS¸ìí¬ | | | | ì ë°°ê¸ì ìí- |
| ë³´ì- ì-í¤í...ì²ëS" | | | | ë°©ë²- ë° ê³µêµ¬, ë° |
| ê³íëì-ë¤. | | | | í´ë¼ì´ì-¸íS¸ |
| ì²´ê³ëS" ì ë³´ì- | | | | ìë² ì²´ê³ì |
| ì-í¤í...ì²ë¥¼ | | | | ê°ë (TM) ë° ì¡°ì -. |
| ì¤í-í-기 ìí-ì-¬ | | | | ì´ ê³µêµ¬ì |
| 구매ëê³ | | | | ëë¶ë¶ì |
| ë°°ì¹ëì-ë¤. | | | | 미ë"¤ì¨ì-´ì ëì' |
| ë¤ëì ê·¸ë (TM) ì- | | | | ì§ì-ê³¼ |
| ë³í (TM) "í-ë¤. 모ë" | | | | ì-°ê´ëë¤. |
| ì¬ì-... ì²´ê³ë¥¼ | | | | ì¥ 6 |
| ì´ë (TM) í-ëS" | | | | í´ë¼ì´ì-¸íS¸ |
| ìí-ì-¬ OGFê° ì§ê¸ | | | | ìë² ê±´ì¶-ì : ì´ì |
| 1996ë... í- ë² ì | | | | ì¹ì...ì-ì 기ì |
| 쪽ì- ìë¹ìS¤ë¥¼ | | | | ë 기ì ì-, |
| ë" ê³í í¬í-¨í-ëS" | | | | í´ë¼ì´ì-¸íS¸ |
| ë (TM) ì- ì¤í¨í-ë¤. | | | | ìë² ê±´ì¶-ì ì |
| 주목í- ë§í-ê², | | | | 3ê°ì ì¢...ë¥ëS" - |
| ì°ë¦¬ëS" (4ë¶ê¸° | | | | íì- ë´ì - |
| 1998ë...ì-ì | | | | ìë³ë ì ìë¤. |
| ë°°ì¹ëëS") | | | | 기본ì ì¸ |
| ì¬ëë"¤ Soft/SIS (í- (TM) | | | | í´ë¼ì´ì-¸íS¸ |
| ì ì-ë´ë¶)ì (TM) | | | | ìë²: - 기본ì ì¸ |
| ê°ì§ ê¸ì-¬ë¶ë¥¼ | | | | í´ë¼ì´ì-¸íS¸ |
| ìí-´ ì¬ëë"¤ Soft/HRMS | | | | ìë² ê±´ì¶-ì , |
| (ì¸ì ìì ê´ë¦¬ | | | | ê°ì¸ ì§'ê¶ë ì |
| ì²´ê³)ê° | | | | ì²ì-ì - 2ê° |
| ê·¸ë¬ë¯ë¡ Oracleê° | | | | ë¶í'ì¼ë¡ |
| ì°ë¦¬ì ì¬ì-...ì | | | | ëëë¤: ê°ì¸ |
| ìí- ì´ ì£¼ì" | | | | í"ëíS¸í (TM) ì- |
| ì±ë¶ì ì ë¬í- | | | | í´ë¼ì´ì-¸íS¸ |
| ì ì-ìSµëë¤ ëª | | | | ë¶ì, ë° ìë² |
| ë...ì ë"°ë¥¼ ê²ì | | | | í"ë«í¼ì- ìë² |
| ì"구í-ë¤. ëí- | | | | ë¶ì. íìëS" |
| ì°ë¦¬ëS" ë¤ë¥¸ ì | | | | ììë¡ ê³µì |
| ì²ì´ ì§ì -ë ë- | | | | ìì íì¼ |
| ë°ì´íë² ì´ìS¤ë¡ | | | | ìë¹ìS¤ì (TM) ê° (TM) |
| Oracle를 ì"구í-ëS" | | | | ì ì¸ì ìë¹ìS¤, |
| ê²ì´ ì ë¹í-, | | | | ë°ì´íë² ì´ìS¤, |
| ê·¸ê² Oracle | | | | ëëS" ì-´ë-¤ |
| ë°ì´íë² ì´ìS¤ | | | | application-specific |
| ë° ëëS" ë°'ì- ìëS" | | | | 기ëS¥ì´ë¤. ê¸°ê° |
| ì´ì ì²´ê³ì ë | | | | í´ë¼ì´ì-¸íS¸ì (TM) |
| (TM) ì¼í- ë²ì ì¼ë¡ | | | | ìë²ëS" í-ë"ì¨ì-´ |
| ì¦ëª...ë | | | | í"ëíS¸í (TM) ë° |
| ê²ì´ë¼ê³ | | | | ì'ì© ìí"íS¸ì¨ì-´ |
| ììí-ëS" ê²ì´ | | | | ë¶ë를 ì-¸ê¸í-ëS" |
| 무리í-ë¤ | | | | ì´ì©ëë¤ |
| ê·¸ë¬ë, | | | | (ììë¡ ì-½ê° ì- |
| ë°ê²¬í-ë¤. 기ì | | | | 매í-ê²). 기본ì |
| ì ë무 빨리 | | | | ì¸ í´ë¼ì´ì-¸íS¸ |
| ë³í (TM) "í-ë¤: ìµì | | | | ìë² ê±´ì¶-ì ì |
| ì Solaris ì²´ê³ëS" ë" | | | | ì«ì 9ì-ì |
| ì´ì íì¬ê° | | | | ì¤ëª...ëë¤ (ì´ë¯¸ |
| ì-ëë¤. | | | | ì«ì 6ì-ì ë" |
| ë¤íS¸ìí¬ëS" | | | | ìì¸í ë³´ì´ê³ ). |
| "ë¹¨ê° ë°©"ì- ìëS" | | | | ì«ì 9 기본ì ì¸ |
| í-ì - ì²´ê³ ë° êµì | | | | í´ë¼ì´ì-¸íS¸ |
| -ì íµí-ì-¬ í-ì - | | | | ìë² ê±´ì¶-ì |
| ì¬ì©ì를 ê³ | | | | 기본ì ì¸ |
| 립ìí¤ê¸° | | | | í´ë¼ì´ì-¸íS¸ |
| ìí-ì-¬ | | | | ìë² ì¤ê³½ì |
| ê°ì¡°ëì-ë¤. | | | | 근거리 ë¤íS¸ì |
| ê·¸ë¬ë, í-ì - | | | | (근거리 íµì |
| ë°©í¸ë²½ ë° í (TM) ë | | | | ë§)ì 주ìì- |
| (TM) ì ì¸ ìíµë | | | | ì¼ë°ì ì¼ë¡ |
| ê°ììëS" ê²°ì½" | | | | í¸ì±ëë¤. ì ì²´ |
| ì¤í-ëì§ ì-Sì-ë¤ | | | | ì§'í-©ì- ìí-ì-¬ |
| - ìµê·¼ì- ì² | | | | PC-LANë¡ ë³´íµ ê¸°ì |
| ê±°ëì-ë¤. | | | | ëê³ , í-ê° ì´ì |
| ì -ì: í´ë¼ì´ì-¸íS¸ | | | | ê³µë (TM) PC (ìë² |
| ìë² ê³ì°ì | | | | í"ë«í¼) í"ë¬ìS¤ |
| ë¤ë ë³´ë | | | | ê°ì¸ ì¬ì© (ê°ì¸ |
| ë²"ìì-ë | | | | í"ëíS¸í (TM) )를 |
| ë¶êµ¬í-ê³ , ì¸ | | | | ìí- ë§ì PCê°, |
| í´ë¼ì´ì-¸íS¸ | | | | ì´ë£¨ì-´ì ¸ ìë¤. |
| ìë² ì§ì§ë¡ | | | | ì´ì- ì§ì- ìë² |
| 무ìS¨ ì -ìì | | | | í"ëíS¸í (TM) ì |
| 주ìì- ë¤ë | | | | ê·¸ë"¤ì- enterprise-wideì (TM) |
| í¼ëì´ ìë¤. | | | | ì (TM) ¸ë¶ |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | ë¤íS¸ìí¬ë¡, |
| ìë²ëS" | | | | ê·¸ë¦¬ê³ ìë²ì- PC |
| ìí"íS¸ì¨ì-´ì (TM) | | | | LANs ë³´íµ |
| 기ê³ì¤ë¹ | | | | ì¶ì...구를 ì |
| ì¤ì¬ë¬¼ ì-ë (TM) | | | | ê³µí-ë¤. ì´ê²ì |
| ëë¤ì´ë¤. | | | | ì«ì 10ì-ì |
| í´ë¼ì´ì-¸íS¸ | | | | ì¤ëª...ëë¤. |
| ìë² ê·¸ê²ì | | | | PCì (TM) PC LANsì ì |
| 기본ì ì¸ | | | | ì-ì 1 ì°¨ë¡ |
| 모ì-'ì-ìëS" | | | | í'íí-´, ì´ ê¸°ë³¸ì |
| ì±ì·¨ëëS" ë¤ë¥¸ | | | | ì¸ í´ë¼ì´ì-¸íS¸ |
| ìí"íS¸ì¨ì-´ | | | | ìë² ê°ë... ì«ì |
| ì¤ì¬ë¬¼ (ìë²)ì- | | | | 10ëS" ì í-ì ì¸ PC-LAN |
| ìí-ì-¬ 구체ì ì¸ | | | | ì¨ê°- ì»´í"¨í° ë° |
| ì"구를 ë§ë"ëS" | | | | ë¤íS¸ìí¬ |
| ìí"íS¸ì¨ì-´ | | | | (ì를ë"¤ë©´ PC, ì |
| ì¤ì¬ë¬¼ | | | | ëìS¤, 주ì"골격, |
| (í´ë¼ì´ì-¸íS¸)를 | | | | LANs ë° WANs)ì- ì ì© |
| í¬í-¨í-ë¤. ì«ì | | | | ê°ëS¥í-ë¤. |
| 1ëS" í´ë¼ì´ì-¸íS¸ | | | | ê¸°ì´ ì 쪽ì-: - |
| ìë² êµí (TM) ì | | | | 기본ì ì¸ |
| ì¤ëª...í-ë¤. | | | | í´ë¼ì´ì-¸íS¸ |
| í´ë¼ì´ì-¸íS¸ ê³¼ì | | | | ìë² ì 쪽ì- - |
| -ì ìë²ì- | | | | ê°ê³µí-ê³ , í'ë ¥ |
| ì"구를 ë³´ë¸ë¤. | | | | ê°ê³µí-ê³ ë...립 |
| ìë²ëS" ë©"ìì§ë¥¼ | | | | ê°ê³µ ë (TM) ë£ ì- ë |
| í-´ìí-ê³ ê·¸ íì- | | | | (TM) ë£ê° ìë¤. |
| ì"구를 ì±ì·¨í-ëS" | | | | ê¸°ê° ë (TM) ë£ ì- ë |
| ê²ì ìëí-ë¤. | | | | (TM) ë£ ê°ê³µì |
| ì"구를 | | | | ìë² í"ë«í¼ì´ |
| ì±ì·¨í-기 | | | | ì-ê³ , ì ì²ì |
| ìí-ì-¬ëS", ìë²ëS" | | | | ìë² ë¶ìì´ |
| ì§ì ê·¼ì | | | | ê°ì¸ í"ëíS¸í (TM) |
| (ë°ì´íë² ì´ìS¤), | | | | ì- ìëS" ì¤ê³½ì |
| ê°ê³µ ìë£ë¥¼ | | | | ì-¸ê¸í-ëS" |
| (ê³ì°ì | | | | ì´ì©ëë¤. ì´ |
| ì¤í-í-ììì¤) | | | | 기ì´ì- ì'ë (TM) |
| ì-¸ê¸í-ê±°ë, | | | | í-ëS" ë¤íS¸ìí¬ëS" |
| ì£¼ë³ ì¥ì¹ë¥¼ íµì | | | | ë (TM) ë£ ì- ë (TM) ë£ |
| í-ê±°ë, ë¤ë¥¸ | | | | ë¤íS¸ìí¬ë¡ |
| ìë²ì ì¶"ê°ì | | | | ë¶ë¦°ë¤. ì´ê²ì |
| ì¸ ì"구를 | | | | ì'ì PC LANs, ë"±ë"± |
| ë§ë"¤ì-´ì-¼ í- ì§ë | | | | ì¤í-ì ê°'ì´ ì¼ |
| 모른ë¤. ë¤ë | | | | ë°©ë²-ì´ë¤; |
| ê±´ì¶-ì ì-ìëS", | | | | ê·¸ë¬ë |
| í´ë¼ì´ì-¸íS¸ëS" | | | | ë¶ë¦¬ëëS" ìë² |
| ë¤ì ìë²ì | | | | í"ë«í¼ì |
| ì"구를 ë§ë"¤ê³ | | | | ë¶ì¡±ì ì²´ê³ ì (TM) |
| ìë²ëS" ë¤ì | | | | ì ì±ì |
| í´ë¼ì´ì-¸íS¸ë¥¼ | | | | ê°ììí¤ê³ |
| ìë¹ìS¤í- ì | | | | ììS¤í... ê´ë¦¬ ì-´ë |
| ìë¤. | | | | ¤ìì¼ë¡ ì´ëì-´ |
| ì«ì 1 - | | | | ë¸ë¤. ê¸°ê° í'ë ¥ |
| í´ë¼ì´ì-¸íS¸ | | | | ê°ê³µì ì'ì© |
| ìë² ê±°ë | | | | ìí"íS¸ì¨ì-´ê° |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | ë¶ë°°ë ì -ì |
| ìë² ì¬ì´ | | | | ë¶ë¦¬ëëS" ìë² |
| ê´ê³ê° ëª...ë ¹ | | | | í"ë«í¼ì¸ |
| ëëS" íµì | | | | ì¤ê³½ì ì-¸ê¸í-ëS" |
| ê´ê³ë¤ëS" ê²ì | | | | ì´ì©ëë¤, ìí¸ |
| ì´í-´í-ëS" ê²ì´ | | | | ì'ì©ì |
| ì¤'ì"í-ë¤. ì-´ë-¤ | | | | í´ë¼ì´ì-¸íS¸ì (TM) |
| 주ì-´ì§ êµí (TM) ë" | | | | ìë² ëì ìë² |
| ì§ì-ìëS", | | | | í"ë«í¼ì- ë' ë¤ |
| í´ë¼ì´ì-¸íS¸ëS" | | | | ìë¤. ì´ê²ì ë |
| ì"구를 ê°ìí-ê³ | | | | (TM) ì¼í- ì ì²ì |
| ìë²ëS" | | | | ë¶ë¶ ì¬ì´ |
| ê·¸ë¬ë¯ë¡ | | | | ë¶ë¦¬ëëS" ì ì² |
| ë°ì'í-ë¤. ìë²ëS" | | | | ì¬ì´ ìí¸ |
| í´ë¼ì´ì-¸íS¸ë¥¼ | | | | ì'ì©ì, ë¤ë§ |
| ê°ì§ ëí (TM) "를 | | | | í¬í-¨í-ë¤. ê¸°ê° |
| ê°ìí- ì ì-ë¤. | | | | ë...립 ê°ê³µì ì |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | ì²ì 모ë" |
| ìë²ê° | | | | ë¶ë¶ì´ 1ê°ì |
| ìí"íS¸ì¨ì-´ | | | | í"ëíS¸í (TM) (ë³´íµ |
| ì¤ì¬ë¬¼ì´ê¸° | | | | ê°ì¸ í"ëíS¸í (TM) |
| ë-문ì- ì-´ë-¤ ì | | | | )ì- ìëS" ì¤ê³½ì |
| í-©í- 기ê³ì¤ë¹ë" | | | | ì-¸ê¸í-ëS" |
| ì§ì- ìì ì | | | | ì´ì©ëë¤. ë¶ì |
| ìë¤. | | | | ì¬ì´ ì-´ë-¤ |
| í´ë¼ì´ì-¸íS¸ ê³¼ì | | | | í´ë¼ì´ì-¸íS¸ |
| -ì, ì를 ë"¤ë©´, | | | | ìë² ê´ê³ë ì (TM) |
| ë¤íS¸ìí¬ ìë² | | | | ¸ë¶ì- ë³´ì´ì§ |
| 기ê³ì¤ë¹ì- | | | | ì-Së¤. ì¬ëë"¤ì |
| ìì ì ìê³ , | | | | ëí- ì-¬ë¬ê°ì§ |
| ë¤ë¥¸ ìë² | | | | ë¤ë¥¸ ì미ì (TM) |
| 기ê³ì¤ë¹ì- ëëS" | | | | í-¨ê» êµí (TM) í- ì |
| PCì- ë¬ë¦¬ëS" ìë² | | | | ì ê¸°ê° ë (TM) ë£ |
| í"ë¡ì¸ìS¤ì-ì | | | | ì- ë (TM) ë£ì (TM) í'ë |
| ìë£ë¥¼ | | | | ¥ ê°ê³µì, ê·¸ë¦¬ê³ |
| ì"구í-ë¤. ë¤ë¥¸ | | | | ì¬ì©í-ë¤. |
| ë본ì-ìëS", | | | | ì´ê²ì í¼ëê³¼ |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | ì¤í-´ë¥¼ ì¼ì¼í¤ëS" |
| ìë² ê³¼ì -ì ë (TM) | | | | ìì¸ì´ ëë¤. |
| ì¼í- ì¡ì²´ì ì¸ | | | | ëí- ìë²ì (TM) ê° |
| 기ê³ì¤ë¹ | | | | (TM) ì ì-¬ë¬ê°ì§ |
| ììì- ìì ì | | | | ë¤ë¥¸ ë³´ë¤ ì ê² |
| ìë¤. ì¤ì ë¡, | | | | ì ëª...í- ì -ë¦½ì´ |
| prototyping ë¨ê³ì-ì, | | | | ëëS" ì뢰ì ë° |
| ê°ë°ìì-ëS" ë (TM) | | | | ìì°ì ëëS" |
| ì¼í- PC | | | | ìë¹ì ìë¤. |
| í-ë"ì¨ì-´ì- ë°í' | | | | 모ë" 주ì" ì -립ì |
| í´ë¼ì´ì-¸íS¸ | | | | ì«ì 11ì-ì í-¨ê» |
| ê·¸ë¦¬ê³ ë°ì´íë² | | | | ì¤ëª...ëë¤. |
| ì´ìS¤ ìë²ê° ë' | | | | ì§ì§ë¡ 기본ì |
| ë¤ ìëS" ê²ì ì | | | | ì¸ í´ë¼ì´ì-¸íS¸ |
| íí- ì§ë | | | | ìë²ë¥¼ |
| 모른ë¤. ìë²ëS" | | | | ì미í-ëS"ì§ ì-´ëS |
| ì ì² ë...¼ë¦¬ì | | | | ê²ì´ë¼ê³ ì- |
| ëë¶ë¶ íì- | | | | ìí-ì-¬) ì«ì 11 |
| ìí-í-ëS" ë" ì | | | | ë¶ì´í-ì |
| ìì°ì ìí- | | | | í´ë¼ì´ì-¸íS¸ |
| ëí- ì ëì- | | | | ìë² ììS¤í... |
| ëì¤'ì- (ë°°ë¶í-ëS") | | | | 구조ì ê°ì¢... ì |
| ì´ë (TM) í- ì ìê³ | | | | -립ì, ë§ì |
| ìë£ êµ¬ì¡° | | | | ì¬ëë"¤ |
| ë°ë¬ì ì (TM) ì | | | | ì리í-ê² |
| í-ë¤. | | | | í´ë¼ì´ì-¸íS¸ |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | ìë²ì-ì ë¤ë¥¸ |
| ìë²ê° ë (TM) ì¼í- | | | | ê°ë...ì ë¶í (TM) |
| 기ê³ì- ìì ì | | | | "í-ë¤ (. ì´ê²ì |
| ìë"ë¼ë, ì´ | | | | 모ë'ê° 1ê°ì |
| ìë¥ëS" ë¶ì° ì- | | | | íµì¼í- 구조 |
| í"리ì¼ì´ì...ì, | | | | ë´ì ì´ì²´ì´ë¤ |
| i.e ê·¸ë"¤ 창조í-기 | | | | ìëª... ì ì |
| ìí-ì-¬ ì´ì©ë | | | | ì-´ë'¡ê² í-ë¤: |
| ê±´ì¶-ì ì- | | | | í´ë¼ì´ì-¸íS¸ |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | ìë² ê±´ì¶-ì . |
| ìë²ê° | | | | ê·¸ê²ì ëí- |
| ë¶ë¦¬ëëS" ì¡ì²´ì | | | | ì¤í-´í-기 ì¬ì´ |
| ì¸ ì¥ì¹ì- ìëS" | | | | ê³ì°ìë¡ |
| ê³³ì- 1 ì°¨ë¡ ì-¼ë | | | | í´ë¼ì´ì-¸íS¸ |
| ¤í-ë¤. í-´ë¦¬ì- | | | | ìë² (ì미 |
| ë"°ë¥´ë©´ (ê·¸ ì (TM) ¸ | | | | 기본ì ì¸ |
| ì-¬ë¬ë¶), | | | | í´ë¼ì´ì-¸íS¸ |
| ë¤íS¸ìí¬ì | | | | ìë²)ëS" |
| ë¤ë¥¸ ë§ë""ì- | | | | ì멸í-ë¤ ì´ë¼ëS" |
| ìí-í-ê³ ê³µë (TM) | | | | ì·¨ì§ì ì´ëì-´ |
| 목í'를 | | | | ë´ê³ , í'ë ¥ |
| ë¬ì±í-기 ìí-ì-¬ | | | | ê°ê³µê³¼ ê° (TM) ì |
| í'ë ¥í-ëS" | | | | ë¤ë¥¸ 기ì ë¡ |
| ë¶ë¦¬ëëS" | | | | ëì ëê³ ìë¤. |
| ë¶ìì´ ë¶ì° ì- | | | | ì¼ë°ì ì¸ |
| í"리ì¼ì´ì...ì- | | | | í´ë¼ì´ì-¸íS¸ |
| ìí-ì-¬ ì´ë£¨ì-´ì ¸ | | | | ìë² ê±´ì¶-ì : - |
| ìë¤. ì§ì | | | | 기본ì ì¸ |
| 기ë°ì ëí- | | | | í´ë¼ì´ì-¸íS¸ |
| ë¶ì° ì²ë¦¬ì ê³ | | | | ìë²ì (TM) 3.1ì (TM) |
| ì í- ë³µí-©ì±ì | | | | 3.2ì- ìëS" 모ë" ì |
| ìµì¢... | | | | -립ì 기본ì ì¸ ì |
| ì¬ì©ìì-ê² | | | | í-ì ê·¸ë"¤ì´ |
| ë³´ì´ì§ ì-SëS" | | | | í-ë"ì¨ì-´ 구ì±ì- |
| ë§ë"¤ì-´ì-¼ í-ë¤. | | | | ìì¡´í-ëS" ë°©ë²-ì- |
| í´ë¼ì´ì-¸íS¸ | | | | ìëS" ìí"íS¸ì¨ì-´ |
| ìë² ê±´ì¶-ì ì- | | | | 구ì±ì ì -ìí-ë¤ |
| ìëS" | | | | ì´ë¤. ê²ë¤ê°, |
| í´ë¼ì´ì-¸íS¸ëS" | | | | ê·¸ê²ì |
| ê·¸ëí"½ ì¬ì©ì | | | | ìí"íS¸ì¨ì-´ ëëS" |
| ì¸í°íì´ìS¤ | | | | 기ê³ì¤ë¹ê° |
| (GUI)를 í-ì"ì-ë¤, | | | | 기ê°ì- ìí-ì-¬ |
| ê·¸ë¬ë, | | | | í´ë¼ì´ì-¸íS¸ì (TM) |
| í´ë¼ì´ì-¸íS¸ | | | | ìë² |
| ìë²ì ì§ë | | | | ì-¸ê¸í-ã´ë¤ëS" |
| ìí'í (TM) "ëS" GUI | | | | ê²ì ììë¡ ì- |
| í´ë¼ì´ì-¸íS¸ì í | | | | 매í-ë¤. ì´ ì í- |
| (TM) -ì° ë-문ì- í° | | | | ë° ì- 매í-¨ì-ì |
| ë¶ë¶ì-ì ëëµ ì | | | | ë주í-기 |
| (TM) "ë¤. ì¸ì (i.e | | | | ìí-ì-¬ëS", |
| ë¤íS¸ìí¬ ì¸ì | | | | ìí"íS¸ì¨ì-´ì- |
| ë기ì-´) ê°ê³ ëS" | | | | ìëS" í´ë¼ì´ì-¸íS¸ |
| ëëS" ë°í' (i.e X ì°½)ì | | | | ìë² ê´ê³ëS" |
| (TM) ê° (TM) ì | | | | í´ë¼ì´ì-¸íS¸ ëëS" |
| í´ë¼ì´ì-¸íS¸ | | | | ìë²ë¡ |
| ìë² ììS¤í... | | | | ìí"íS¸ì¨ì-´ ìì¹ |
| ì§ì ë'ê² íS¹ì -í- | | | | ê·¸ë¦¬ê³ ê·¼ë³¸ì |
| 기ëS¥ ìë¹ìS¤. ì´ | | | | ì¸ ê¸°ê³ì¤ë¹ì |
| íS¹ì 목ì | | | | ì-´ë-¤ ë¶ë¥ë" ì§ì |
| ì¤ìê° ì¤'ì"í- ë | | | | ë³ëë¡ ì |
| (TM) ì-, ì´ ìë¥ëS" | | | | -ìëì-´ì-¼ í-ë¤. |
| 기ëS¥ì- ìëS" | | | | 근본ì ì¸ ì -í (TM) |
| ìµíµì±ì | | | | "ëS" í´ë¼ì´ì-¸íS¸ì |
| ì"구í-ëS" ë¶ë°°ë | | | | (TM) ìë²ê° |
| í´ë¼ì´ì-¸íS¸ | | | | ìë¹ìS¤ê° (ê°ê°) |
| ìë² ê±´ì¶-ì ì- | | | | ì¬ì©ëê³ ì |
| ì°ìí-ê² | | | | ê³µëëS" ì-í- ì´ë¤ |
| ê´ì§í-ë¤ | | | | ì´ë¤, ì´ ì-í- ì |
| ì¥ 3 | | | | ìì¹ ë¹ë"© ë¸"ë¡ |
| í´ë¼ì´ì-¸íS¸ | | | | ì¬ì´ ê´ê³ì-ì |
| ìë²ì ì미: - | | | | ì긴ë¤. ê·¸ë° |
| í´ë¼ì´ì-¸íS¸ | | | | ê´ê³ì-ìëS", |
| ìë²ì ì¬ì-... | | | | ì°¸ê°ìì í-ê°ëS" |
| ì미: - | | | | ìë¹ìS¤ (ê·¸ê² |
| í´ë¼ì´ì-¸íS¸ | | | | ìë¤ |
| ìë²ëS" ì¬ì-... ì -ë³´ | | | | í´ë¼ì´ì-¸íS¸ ì-í- |
| ììS¤í...ì | | | | ì´)를 ì¬ì©í-ë¤ |
| ì¡°ì'ì | | | | ë ë¤ë¥¸ í-ê°ëS" |
| í¨ê³¼ì-ì ë¤ì | | | | ìë¹ìS¤ (ìë² ì-í- |
| ë¨ê³ì´ê³ ì¼ë°ì | | | | ì´ ìë¤)를 ì |
| ì¼ë¡ ì-ì¼ë¡ | | | | ê³µí-ê³ . ì´ê²ì |
| ê°ì§ëë¤. | | | | í´ë¼ì´ì-¸íS¸ |
| ì´ê²ì íì ì | | | | ìë² ê´ê³ì´ë¤. |
| ìS¹ê³ì-ì ëì ë | | | | í° ì ì-°í- ì¤ì -ì |
| ì´ìµì | | | | ì´ ê°ë¨í- |
| ëíë´ëS" ì«ì | | | | ê°ë...ì ì¡°í-©ì- |
| 1ì-ì ì¤ëª...ëë¤. | | | | ìí-´ ì"ì- ì¬ë¦´ |
| ë¹ì¦ëìS¤ | | | | ì ìë¤. ì´ê²ì |
| ì»´í"¨í...ì ì¼ê´ | | | | ì«ì 12ì-ì |
| ì²ë¦¬ë¥¼ ê°ì§ 1960 | | | | ì¤ëª...ëë¤. |
| ë...ëì-ì | | | | ëí'ì |
| ìì'í-ë¤. 1970 | | | | ì¤ë¥¸ìª½ì-ì |
| ë...ëì- ìëS" | | | | ëíëëS" ê²ê³¼ ê° |
| 주ì" íì ì | | | | (TM) ì´ í´ë¼ì´ì-¸íS¸ |
| ì¨ë¼ì¸ | | | | ìë² ê±´ì¶-ì ì |
| íS¸ëìì... ì²ë¦¬ | | | | ì«ì 12 ì리ëS", |
| (OLTP) 2 ë°"í- í (TM) "ë©´ì- | | | | ë¹ë"© ë¸"ë¡ |
| ì -ë³´ 기ì | | | | ìë¹ìS¤ì |
| (ê·¸ê²)를 ê°ì ¸ì¨, | | | | ì¬ì©ì ê·¸ë¦¬ê³ |
| ê·¸ê²ì-ê² | | | | ê³µê¸ì ë' |
| ë¶ê°ê²°í- | | | | ë¤ì¼ì§ë |
| ë¶ë¶ì ì¬ì-... ê³¼ì | | | | 모른ë¤. |
| -ì ë§ë"¤ì-´ì´ê³ . | | | | ê·¸ë¬ë¯ë¡, |
| ì¡°í-©ì- ìëS" ì¼ê´ | | | | ê·¸ê²ì-ëS" |
| ì²ë¦¬ ê·¸ë¦¬ê³ OLTPëS" | | | | í´ë¼ì´ì-¸íS¸ì (TM) |
| ìµë 기ì-...ì ì | | | | ìë² ì-í- ì´ ìê³ |
| -ë³´ ììS¤í...ì | | | | ìì§ë ë¤ë¥¸ |
| ì¤'í-µì- ìëS" ê²ì | | | | ë¹ë"© ë¸"ë¡ì |
| ê³ìí-ë¤. ê·¸ ë- | | | | ê°ì§ ë§ì |
| 1980ë...ë ê°ì¸ 측ì | | | | í´ë¼ì´ì-¸íS¸ |
| -ìì-ì ê·¸ê²ì | | | | ìë² ê´ê³ì- |
| ë³´í¸ì ì¼ë¡ | | | | ì°¸ê°í- ì§ë |
| 기ì-...ì íµí-ì-¬ | | | | 모른ë¤. ê³ ë ¤ë |
| ê·¸ê²ì´ë¼ê³ ì | | | | íS¹ì -í- ê´ê³ì |
| ë¹í-´ë ë° | | | | 문맥ì-ììë§ |
| ì´ì°í-ëS" í- ì (TM) | | | | í´ë¼ì´ì-¸íS¸ ëëS" |
| "ë¤. ì§ê¸ 1990 | | | | ìë² ì´ë¤. |
| ë...ëì-ì, | | | | ìí"íS¸ì¨ì-´ì- |
| í´ë¼ì´ì-¸íS¸ | | | | ìëS" í´ë¼ì´ì-¸íS¸ |
| ìë²ëS" ì -ë³´ | | | | ìë² ê±´ì¶-ì ì |
| ììS¤í...ì | | | | íì¤í (TM) "ëS" ì«ì |
| ë¶ë¦¬ëëS" ë¶ë¶ | | | | 12ì-ì ë³´ì´ì§ |
| íì- íµí-©ì | | | | ì-SëS" () í"ë¡ê·¸ë¨ |
| ë°©ë²-ì´ê³ ì¼ë°ì | | | | ì-¸ì-´ ë° |
| ì¼ë¡ í-¨ê» | | | | 미ë"¤ì¨ì-´ë¥¼ íµí-´ |
| ê°ì§ëë¤. ì | | | | ì´ë¤. ë¶ë¦¬ëëS" |
| ê²ì ê·¸ê²ì | | | | ì»´í"¨í°ì |
| ì-í- ë° ê·¸ê²ì | | | | ë¤íS¸ìí¬ê° |
| ì¤'ì"ì±ì´ë¤. | | | | í´ë¼ì´ì-¸íS¸ |
| ì«ì 1 ê°ì§ë | | | | ìë² ê±´ì¶-ì ì |
| í´ë¼ì´ì-¸íS¸ | | | | ì¡ì²´ì ì¸ íì¤í |
| ìë² ì´ë¬í- ìí | | | | (TM) "ì- ìí-ì-¬ |
| (TM) ©ì-ì | | | | ì´ë£¨ì-´ì ¸ ìë¤; |
| í´ë¼ì´ì-¸íS¸ | | | | í-ì-°ì ì¼ë¡ ê¸°ê° |
| ìë²ì ì¬ì-... | | | | í´ë¼ì´ì-¸íS¸ |
| 충격ì (ëëS" | | | | ìë²ëS" ë¶ì° |
| í´ë¼ì´ì-¸íS¸ | | | | ì²ë¦¬ë¥¼ ìí- ë (TM) |
| ìë²) ì¬ì-... ë° | | | | ìì-´ê° ëì-´ |
| 기ì ì ì¸ íµì°°ë ¥ | | | | ê²½í-¥ì´ ìë¤. |
| ë° ë§¤ë§¤ | | | | í´ë¼ì´ì-¸íS¸ |
| ë©"ìì§ì 모ë" | | | | ìë² ê±´ì¶-ì ì |
| ë°©ë²-ì- ì í'ì | | | | 기ì ì ë¤ë¥¸ |
| ê±°ì ê° ì¢...ë¥ì- | | | | ì-´ë-¤ íS¹ì - ì¢...ë¥ì |
| ì ì©ëëS" ëì¤'ì | | | | PC, ëëS" ì¬ì©ì- |
| ì¸ ì ëª... ìí'ê°, | | | | ê´í-ì-¬ìë§ |
| ë° ëì-ë¤. | | | | ë¶ìì ì¼ë¡ |
| ì´ê²ì íS¹ì -í- | | | | ì´ë¤. ê·¸ë¬ë, |
| ì미ì ê·¸ê²ì | | | | íì¬ ìí (TM) |
| ë°°ìí-´ ê²½í-¥ì´ | | | | ©ì-ì, |
| ìë¤; ê·¸ë¬ë | | | | í´ë¼ì´ì-¸íS¸ |
| ê·¸ë ê² | | | | ìë²ê° PC 기ì |
| í-ë¯ë¡ì¨, ì¤ì | | | | ì´ì©ì ì ì-ì |
| ë¡ ê·¸ê²ì ê°ê¹ | | | | ì£¼ë¡ ì ë§ëë¤ |
| ë³´í¸ì ì¸ | | | | ë³´íµ ì í-©í-ë¤ |
| ì'ì©ì±ì í (TM) | | | | (ì°ë¦¬ê° ì ìì- |
| -ì¸í-ë¤. | | | | ì-ì¼ë¡ 1.2ì-ì |
| í´ë¼ì´ì-¸íS¸ | | | | ìì'í-) Gartner ì |
| ìë²ì 기ì ì | | | | -ìì-ì ê²ê³¼ ê° |
| ì¸ ì미: - ì´í-´ | | | | (TM) ì´. ìì¹ |
| í´ë¼ì´ì-¸íS¸ | | | | í´ë¼ì´ì-¸íS¸ |
| ìë²ë¥¼ ìí- ì | | | | ìë² ê±´ì¶-ì ì |
| ì©í- ì¶ë°ì ì | | | | ì´ ì¼ë°ì ì¸ |
| Gartner ê·¸ë£¹ì´ | | | | 모ì-'ì (ì |
| ì¬ì©í- ì-½ì ì | | | | í´ë¼ì´ì-¸íS¸ |
| -ìì´ë¤: | | | | ìë² ê´ê³, |
| "í´ë¼ì´ì-¸íS¸ | | | | í´ë¼ì´ì-¸íS¸ ì-í- , |
| ìë² ë¶ë¦¬ëëS" | | | | ìë² ì-í- 건물 |
| ì»´í"¨í°ì- | | | | ë§ëS"ë¤) ê°ë°©í- |
| ì´í-ëëS" | | | | í"ë ììí¬ ì ì² |
| ì-...무ë¡ì´ë¤ ì | | | | ê±´ì¶-ì ì 기본ì |
| ì², ê·¸ì¤' í-ëì | | | | ì¸ ì±ë¶ì´ë¤. |
| ëëëS"ì´ë¤ | | | | Assumptions:- |
| í'그릴 | | | | 1.One client is connected to at most one |
| ìí¬ìS¤í...ì´ì... | | | | server at a time. [The customer later |
| (ì를ë"¤ë©´ PC)."ëS" | | | | refuted this assumption.] |
| ì´ ì -ìëS" | | | | 2.Replication is a secondary effect of |
| í´ë¼ì´ì-¸íS¸ | | | | the existing fat-client architecture; we |
| ìë²ê° ë¶ë°°ë | | | | assume that updates to one server are |
| ê³ì° ê·¸ë¦¬ê³ | | | | automatically propagated in a timely |
| ìí"íS¸ì¨ì-´ 구조 | | | | fashion. |
| (ì ì²ì | | | | 3.A single client may have more than one |
| ë¶ë¦¬ëëS" | | | | session. [Replaced Assumption 1.] |
| ì»´í"¨í°ì- | | | | 4.All calculated columns (columns that |
| ììì§ë | | | | represent behavior rather than aspects) |
| 모른ë¤) | | | | are easily & quickly calculated on the |
| ì-...무ë¡ì- ê´í-ì-¬ | | | | server. |
| ëëë¤ ë¤ëS" | | | | 5.Deletion or insertion of a row forces |
| ê²ì ë°íë¤. | | | | a window update on the client. |
| ê·¸ê²ì | | | | 6.Transmission of client-server traffic |
| í´ë¼ì´ì-¸íS¸ | | | | is out of scope.chapter-7 |
| ìë²ê° ì¨ê°- ì | | | | Architecture Types:- |
| -ë³´ ììS¤í...ì¼ë¡ | | | | When considering a move to client/server |
| PC를 íµí-©í-ëS" | | | | computing, whether it is to replace |
| ë°©ë²- ì´ë¤ ìëª... | | | | existing systems or introduce entirely |
| ì ì ë°í-¥í-ë¤. | | | | new systems, practitioners must |
| ì ê°ì 3ë§ë¦¬ì | | | | determine which type of architecture |
| ë°ì: | | | | they intend to use. The vast majority of |
| í¸ìS¤íS¸ 기본 | | | | end user applications consist of three |
| ê±´ì¶-ì | | | | components: presentation, processing, |
| (í´ë¼ì´ì-¸íS¸ | | | | and data. The client/server |
| ìë² ê±´ì¶-ì ì-ë | | | | architectures can be defined by how |
| (TM) ëë¤): | | | | these components are split up among |
| 주ì"골격 | | | | software entities and distributed on a |
| ìí"íS¸ì¨ì-´ | | | | network. There are a variety of ways for |
| êµ¬ì¡°ë¡ ëª¨ë" ì | | | | dividing these resources and |
| -ë³´ëS" ì¤'ì- (TM) 주ì | | | | implementing client/server |
| ì°ê¸° ì-ì- ìë¤. | | | | architectures. This paper will focus on |
| ì¬ì©ìëS" | | | | the most popular forms of implementation |
| í¤ìS¤íS¸ë¡í¬ë¥¼ ë¶ | | | | of two-tier and three-tier client/server |
| (TM) ì¡ê³ 주ì¸ì- ì | | | | computing systems. Two-tier |
| ì -보를 ë³´ë´ëS" | | | | Architecture:- Although |
| 맨ëì íµí-´ì | | | | there are several ways to architect a |
| 주ì¸ê³¼ ìí¸ | | | | two-tier client/server system, we will |
| ì'ì©í-ë¤. | | | | focus on examining what is |
| 주ì"골격 | | | | overwhelmingly the most common |
| ìí"íS¸ì¨ì-´ | | | | implementation. In this implementation, |
| 구조ëS" í-ë"ì¨ì-´ | | | | the three components of an application |
| í"ëíS¸í (TM) ì- | | | | (presentation, processing, and data) are |
| 묶ì´ì§ ì-SëS"ë¤. | | | | divided between two software entities |
| ì¬ì©ì ìí¸ | | | | (tiers): client application code and |
| ì'ì©ì PCì (TM) ì | | | | database server (Figure 2). A robust |
| ëìS¤ | | | | client application development language |
| ìí¬ìS¤í...ì´ì...ì | | | | and a versatile mechanism for |
| ì¬ì©í-ì-¬ ëë | | | | transmitting client requests to the |
| ì ìë¤. | | | | server are essential for a two-tier |
| 주ì"골격 | | | | implementation. Presentation is handled |
| ìí"íS¸ì¨ì-´ | | | | exclusively by the client, processing is |
| 구조ì ì í-ì | | | | split between client and server, and |
| ê·¸ë"¤ì´ ì½ê² | | | | data is stored on and accessed via the |
| ê·¸ëí"½ ì¬ì©ì | | | | server. The PC client assumes the bulk |
| ì¸í°íì´ìS¤ë¥¼ | | | | of responsibility for application |
| ì§ìí-ì§ ì-Sê±°ë | | | | (functionality) logic with respect to |
| ì§ë¦¬ì ì¼ë¡ | | | | the processing component, while the |
| ì´ì°í- | | | | database engine - with its attendant |
| ìì¹ì-ì ë¤ì | | | | integrity checks, query capabilities and |
| ë°ì´íë² ì´ìS¤ì- | | | | central repository functions - handles |
| ì 'ê·¼í-ì§ ì-SëS"ë¤ | | | | data intensive tasks. In a data access |
| ì´ë¤. ì§ë | | | | topology, a data engine would process |
| ëªë...ê°ì-ìëS", | | | | requests sent from the clients. |
| 주ì"골격ì | | | | Currently, the language used in these |
| ë¶ë°°ë | | | | requests is most typically a form of |
| í´ë¼ì´ì-¸íS¸ | | | | SQL. Sending SQL from client to server |
| ìë² ê±´ì¶-ì ì- | | | | requires a tight linkage between the two |
| ìëS" ìë²ë¡ | | | | layers. To send the SQL the client must |
| ìë¡ì´ ì¬ì©ì | | | | know the syntax of the server or have |
| ì°¾ì-ëë¤ | | | | this translated via an API (Application |
| 근거리 íµì ë§ | | | | Program Interface). It must also know |
| íì¼ ê³µì ê±´ì¶-ì | | | | the location of the server, how the data |
| (í´ë¼ì´ì-¸íS¸ | | | | is organized, and how the data is named. |
| ìë² ê±´ì¶-ì ì-ë | | | | The request may take advantage of logic |
| (TM) ëë¤): - ìë PC | | | | stored and processed on the server, |
| ë¤íS¸ìí¬ëS" | | | | which would centralize global tasks such |
| ìë²ê° ê³µë (TM) | | | | as validation, data integrity, and |
| ìì¹ì-ì | | | | security. Data returned to the client |
| íìì© í (TM) ê²½ì- | | | | can be manipulated at the client level |
| íì¼ì | | | | for further sub selection, business |
| ë¤ì´ë¡ë"í-ëS" | | | | modeling, "what if" analysis, reporting, |
| íì¼ ê³µì ê±´ì¶-ì | | | | etc. |
| ì- 근거í-ë¤. | | | | Figure 2 - Data Access Topology for |
| ì"구ë ì¬ì©ì | | | | two-tier architecture. Majority of |
| ì¼ì íìì© í (TM) | | | | functional logic exists at the client |
| ê²½ì-ì ê·¸ ë- (를 | | | | level The most |
| í¬í-¨í-ì-¬ ë...¼ë¦¬ | | | | compelling advantage of a two-tier |
| ë° ìë£) ë¬ë¦°ë¤. | | | | environment is application development |
| íì¼ ê³µì ê±´ì¶-ì | | | | speed. In most cases a two-tier system |
| ì ê³µë (TM) | | | | can be developed in a small fraction of |
| ê²½ì°ì- | | | | the time it would take to code a |
| ì¬ì©ë²-ì´ | | | | comparable but less flexible legacy |
| ë(R)ì¼ë©´, ê°±ì | | | | system. Using any one of a growing |
| ë...¼ì ë(R)ë¤ ì'ë | | | | number of PC-based tools, a single |
| (TM) í-ê³ , ì(R)ê²¨ì§ | | | | developer can model data and populate a |
| ìë£ëì ë(R)ë¤. | | | | database on a remote server, paint a |
| 1990 ë...ëì-ìëS", | | | | user interface, create a client with |
| íì¼ ê³µì ì | | | | application logic, and include data |
| ìì©ëì´ | | | | access routines. Most two-tier tools are |
| ë-문ì- ì¨ë¼ì¸ | | | | also extremely robust. These |
| ì¬ì©ìì ì | | | | environments support a variety of data |
| ì±ì¥í-기 | | | | structures, including a number of built |
| 긴ì¥ë기 | | | | in procedures and functions, and |
| ë-문ì- ë°"ë PC | | | | insulate developers from many of the |
| 근거리 íµì ë§ | | | | more mundane aspects of programming such |
| (근거리 ë¤íS¸ì) | | | | as memory management. Finally these |
| ê³ì°ì (ë¨ì§ | | | | tools also lend themselves well to |
| ëëµ 12ëª...ì | | | | iterative prototyping and rapid |
| ì¬ì©ìë§ ë (TM) | | | | application development (RAD) |
| ìë¡ ë§ì¡±ìí¬ | | | | techniques, which can be used to ensure |
| ì ìë¤) ê·¸ëí"½ | | | | that the requirements of the users are |
| ì¬ì©ì | | | | accurately and completely met. |
| ì¸í°íì´ìS¤ (GUIs) | | | | Tools for developing |
| ëì¤'ì ëê³ | | | | two-tier client/server systems have |
| (주ì"골격과 ë ì | | | | allowed many IS organizations to attack |
| ì를 ë§ë"¤ì-´ì | | | | their applications backlog, satisfying |
| 구ìì¸ ê²ì²ë¼ | | | | pent-up user demand by rapidly |
| ë³´ì´ììì¤). PCëS" | | | | developing and deploying what are |
| ì§ê¸ | | | | primarily smaller workgroup-based |
| í´ë¼ì´ì-¸íS¸ | | | | solutions. Two-tier architectures work |
| ìë² ê±´ì¶-ì ì-ì | | | | well in relatively homogeneous |
| ì¬ì©ëê³ ìë¤ | | | | environments with fairly static business |
| ì¸í°ë· | | | | rules. This architecture is less suited |
| í´ë¼ì´ì-¸íS¸ | | | | for dispersed, heterogeneous |
| ìë² ê±´ì¶-ì : - ì´ | | | | environments with rapidly changing |
| ì¢...ë¥ë¥¼ ìí- | | | | rules. As such, relatively few IS |
| 목í'ëS" ê³¼ì -ì | | | | organizations are using two-tier client |
| ë머ì§ë¥¼ ë°'ì- | | | | server architectures to provide |
| ìì ë°°ê²½ | | | | cross-departmental or cross-platform |
| ì§ìì 기ì´ë¥¼ | | | | enterprise-wide solutions |
| ê±´ì¤í-기 ìí- | | | | Since the bulk of |
| ê²ì´ë¤. 기ì ì | | | | application logic exists on the PC |
| ë§ì ì§ì-ì-ìëS" | | | | client, the two-tier architecture faces |
| ì¬ëì ê·¸ê²ì | | | | a number of potential version control |
| íì¬ ëª¨ì-'ì-ì | | | | and application re-distribution |
| í-ì ì¡´ì¬ëëS" | | | | problems. A change in business rules |
| ê²ê³¼ ê° (TM) ì´ | | | | would require a change to the client |
| ëSëì 기ì | | | | logic in each application in a |
| ì-»ëS"ë¤. ê·¸ë¬ë, | | | | corporation's portfolio, which is |
| ë¹ì-°í, 기ì ì-ëS" | | | | affected, by the change. Modified |
| ë¤ë¥¸ ì-´ë-¤ ìì-° ì | | | | clients would have to be re-distributed |
| ì´ê³ | | | | through the network - a potentially |
| ë¶ìì-°ìS¤ë¬ì´ | | | | difficult task given the current lack of |
| íì ê° (TM) ì´ | | | | robust PC version control software and |
| ì-ì¬ê° ë¤ë§ | | | | problems associated with upgrading PCs |
| ìë¤. ê·¸ê²ì | | | | that are turned off or not "docked" to |
| ì¸í°ë· ë° ì"ë" ì | | | | the network. System |
| (TM) ì´ë" ì¹ì | | | | security in the two-tier environment can |
| ìí-´ ì´ë ê² | | | | be complicated since a user may require |
| ì´ë¤. ì´ ë©´ë´ ë | | | | a separate password for each SQL server |
| (TM) ì-ì-, ì°ë¦¬ëS" | | | | accessed. The proliferation of end-user |
| ì¤ëSì¸ ë¬´ì-ì | | | | query tools can also compromise database |
| ì¸í°ë·ì ë§ë" | | | | server security. The overwhelming |
| 과거 30 ë... ë´ë´ | | | | majority of client/server applications |
| ì¼ì-´ë ì-´ë-¤ì | | | | developed today are designed without |
| ì¤'ì"í- ë°ë¬ì | | | | sophisticated middleware technologies, |
| ì²«ì§¸ë¡ ë³¼ | | | | which offer increased security. Instead, |
| ê²ì´ë¤. ì´ | | | | end-users are provided a password, which |
| ë...ë기를 ê²í | | | | gives them access to a database. In many |
| í- íì-, ì°ë¦¬ëS" | | | | cases this same password can be used to |
| ì¸í°ë·ì | | | | access the database with data-access |
| ì§ìí-ëS" 근본ì | | | | tools available in most commercial PC |
| ì¸ ê¸°ì ì 2ê°ë¥¼ | | | | spreadsheet and database packages. Using |
| ë³¼ ê²ì´ë¤. | | | | such a tool, a user may be able to |
| 첫ë²ì§¸ ìë¡ì | | | | access otherwise hidden fields or tables |
| ëªë°±ëª... ì-¼ë" | | | | and possibly corrupt data. |
| ì-ì- ìëS" | | | | Client tools and the SQL |
| ì»´í"¨í°ë¥¼ | | | | middleware used in two-tier environments |
| ì-°ê²°í-기 ìí-ì-¬ | | | | are also highly proprietary and the PC |
| ì´ì©ë ê°ì¥ | | | | tools market is extremely volatile. The |
| ë리 í¼ì§ íµì | | | | client/server tools market seems to be |
| ë§ì ì´ë"ë¤íS¸, | | | | changing at an increasingly unstable |
| ìë 근거리 | | | | rate. In 1994, the leading client/server |
| ë¤íS¸ì (근거리 | | | | tool developer was purchased by a large |
| íµì ë§) 기ì ë° | | | | database firm, raising concern about the |
| ì-ì§ë í-ê° | | | | manufacturer's ability to continue to |
| ì´ë¤. ì 2ëS" TCP/IP ì | | | | work cooperatively with RDBMS vendors, |
| ë©"ìì§ë¥¼ | | | | which compete with the parent company's |
| ìë¡ì-ê² | | | | products. The number two-tool maker lost |
| ì§ìí-ê³ | | | | millions and has been labeled as a |
| 견ì¤í-ê² | | | | takeover target. A firm also in the |
| êµíµí-기 ìí-ì-¬ | | | | midst of severe financial difficulties |
| ì ì¸ê³ ìëS" | | | | and management transition supplies the |
| ì»´í"¨í°ë¥¼ | | | | tool, which has received some of the |
| ê°ëS¥í-ê² í-ëS" | | | | brightest accolades in early 1995. This |
| ìí"íS¸ì¨ì-´ | | | | kind of volatility raises questions |
| 기ì¤ì´ë¤. | | | | about the long-term viability of any |
| ì¸í°ë·ì í ë¡ í- | | | | proprietary tool an organization may |
| íì-, ì°ë¦¬ëS" ê·¸ | | | | commit to. All of this complicates |
| ë- ì"ë" ì (TM) ì´ë" | | | | implementation of two-tier systems - |
| ì¹ì- ì°ë¦¬ì | | | | migration from one proprietary |
| 주ì, ì체를 ë | | | | technology to another would require a |
| ê²ì´ë¤. ë©´ë´ì | | | | firm to scrap much of its investment in |
| 1ëì ì»´í"¨í°ì- | | | | application code since none of this code |
| ë¬ë¦¬ëS" | | | | is portable from one tool to the next. |
| í´ë¼ì´ì-¸íS¸ | | | | Three tier:- Most |
| í"ë¡ê·¸ë¨ì´ | | | | sophisticated Web based applications, |
| ì-½ê° íS¹ì -í- ì | | | | which involve data entry, are based on a |
| -보를 ì"구í-기 | | | | 3 tier client server architecture. The 3 |
| ìí-ì-¬ ë ë¤ë¥¸ | | | | tiers are |
| í-ê°ì- ë¬ë¦¬ëS" | | | | ⢠The Client (Web Browser) |
| ìë² | | | | ⢠The Web Server/Application |
| í"ë¡ê·¸ë¨ê³¼ | | | | Server |
| ì-°ë½í-ëS" ê·¸ê²ì | | | | ⢠The Database Server |
| 기본ì ì¸ | | | | The tree tier |
| í´ë¼ì´ì-¸íS¸ | | | | architecture (Figure 3) attempts to |
| ìë² ê±´ì¶-ì ì | | | | overcome some of the limitations of the |
| ê²í ë¡ ëëS" ì-½ê° | | | | two-tier scheme by separating |
| ìë¹ìS¤ëS" | | | | presentation, processing, and data into |
| ì´í-ëë¤ | | | | separate, distinct software entities |
| ìì'ëë¤. ì¹ì ì | | | | (tiers). The same types of tools can be |
| -ë³´ì íì´ì§ë¥¼ | | | | used for presentation as were used in a |
| ì"구í-기 ìí-ì-¬ | | | | two-tier environment, however these |
| ì¹ ë¸ë¼ì°ì | | | | tools are now dedicated to handling just |
| (í´ë¼ì´ì-¸íS¸)ê° | | | | the presentation. When the presentation |
| ê°ì¢... ì¹ ìë²ì (TM) | | | | client requires calculations or data |
| ì-°ë½í-ëS" | | | | access, a call is made to a middle tier |
| í´ë¼ì´ì-¸íS¸ | | | | functionality server. This tier can |
| ìë² ê±´ì¶-ì ì | | | | perform calculations or can make |
| ì¬ì©í-ì-¬ ëëS" | | | | requests as a client to additional |
| í"ë¡ê·¸ë¨ì | | | | servers. The middle tier servers are |
| ìë²ì ì¼ë° | | | | typically coded in a highly portable, |
| ì¶ì...구 | | | | non-proprietary language such as C. |
| ê³µì©ìì- (CGI)를 | | | | Middle-tier functionality servers may be |
| íµí-´ì | | | | multi-threaded and can be accessed by |
| ì¤í-ëë¤ | | | | multiple clients, even those from |
| ê±´ì¤ëì-ë¤. Internet | | | | separate applications. |
| WWWê° ì¼ë°ì ì¸ | | | | Although three-tier systems can |
| ê³ì° ê·¸ë¦¬ê³ | | | | be implemented using a variety of |
| íµì ì¸í"ë¼ê° | | | | technologies, the calling mechanism from |
| ëëS" ë-, ì´ | | | | client to server in such as system is |
| ì¤ì-í- | | | | most typically the remote procedure call |
| í´ë¼ì´ì-¸íS¸ | | | | or RPC. Since the bulk of two-tier |
| ìë² ê´ê³ëS" í (TM) | | | | implementations involve SQL messaging |
| -ì¥ëê³ ìë¤. | | | | and most three-tier systems utilize |
| 1ê°ì ê·¸ë° í (TM) | | | | RPCs, it is reasonable to examine the |
| -ì¥ì ìë°"를 | | | | merits of these respective request |
| í¬í-¨í-ë¤. ê³¼ì | | | | response mechanisms in a discussion of |
| -ì-ì ëì¤'ì- ì´ | | | | architectures. RPC calls from |
| ì ê°ë°ì- ê´í-ì-¬ | | | | presentation client to middle-tier |
| ë" ë§ì ê², | | | | server provide greater overall system |
| ê·¸ë¬ë ë¹ë¶ê°, | | | | flexibility than the SQL calls made by |
| ì°ë¦¬ëS" ì¹ì ê³ ì | | | | clients in the two-tier architecture. |
| ì ì¸ | | | | This is because in an RPC, the |
| í´ë¼ì´ì-¸íS¸ | | | | requesting client simply passes |
| ìë² ë""ìì¸ì- | | | | parameters needed for the request and |
| ì§'ì¤'í- ê²ì´ë¤. | | | | specifies a data structure to accept |
| ì-¸ì-´ ì¹ | | | | returned values (if any). Unlike most |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | two-tier implementations, the three-tier |
| ìë²ëS" ìë¡ | | | | presentation client is not required to |
| ë¶ë¦°ë¤ HTTP | | | | "speak" SQL. As such, the organization, |
| (í-ì´í¼ í...ìS¤íS¸ ì | | | | names, or even the overall structure of |
| ì¡ í"ë¡í | | | | the back-end data can be changed without |
| ì½)ì-ê² ë§í-ë¤. | | | | requiring changes to PC-based |
| ë¹ì ì HTTP를 | | | | presentation clients. Since SQL is no |
| ìì¸í ë°°ì¸ | | | | longer required, data can be organized |
| í-ì"ì-ì | | | | hierarchically, relationally, or in |
| ê²ì´ë¤, ê·¸ë¬ë | | | | object format. This added flexibility |
| ë¹ì ì 기본ì | | | | can allow a firm to access legacy data |
| ì¸ HTTP | | | | and simplifies the introduction of new |
| í"ë¡ê·¸ë¨í-ëS" | | | | database technologies. |
| CGI를 í-기 ìí-ì-¬ | | | | Figure 3 - Three-Tier Architecture. |
| ë©"ìì§ë¥¼ | | | | Functionality servers handle most of the |
| ê±´ì¤í-´ì-¼ í-ê³ | | | | logic processing. Middle-tier code can |
| ê·¸ê²ì 근본ì | | | | be accessed and utilized by multiple |
| ì¸ ì² í- (TM) ë° | | | | clients In |
| ê·¸ê²ì 기본í- | | | | addition to the openness stated above, |
| ë° ê¸°ëS¥ ì´í-´í-´ì-¼ | | | | several other advantages are presented |
| í-ë¤. | | | | by this architecture. Having separate |
| ì¥ 4 | | | | software entities can allow for the |
| ê³¼ì -: - | | | | parallel development of individual tiers |
| í´ë¼ì´ì-¸íS¸ ê³¼ì -: | | | | by application specialists. It should be |
| - í´ë¼ì´ì-¸íS¸ | | | | noted that the skill sets required to |
| ì´ë¤ ê³¼ì - | | | | develop c/s applications differ |
| (ìë²ê° ì-...무 | | | | significantly from those needed to |
| (ìë¹ìS¤)를 | | | | develop mainframe-based character |
| ì´í-í-ã´ë¤ëS" | | | | systems. As examples, user interface |
| ê²ì ì"구í-ëS" | | | | creation requires an appreciation for |
| í"ë¡ê·¸ë¨) ìë² | | | | platform and corporate UI standards and |
| í"ë¡ì¸ìS¤ | | | | database design requires a commitment to |
| (í"ë¡ê·¸ë¨)ì- | | | | and understanding of the enterprise's |
| ë©"ìì§ë¥¼ | | | | data model. Having experts focus on each |
| ë³´ë´ëS". | | | | of these three layers can increase the |
| í´ë¼ì´ì-¸íS¸ | | | | overall quality of the final |
| í"ë¡ê·¸ë¨ì | | | | application. |
| ë³´íµ ì ì²ì | | | | The three-tier architecture also |
| ì¬ì©ì | | | | provides for more flexible resource |
| ê³µì©ìì- | | | | allocation. Middle-tier functionality |
| ë¶ë¶ì ì²ë¦¬í-ê³ | | | | servers are highly portable and can be |
| , ì¬ì©ìê° ì...ë | | | | dynamically allocated and shifted as the |
| ¥í- ìë£ë¥¼ ì | | | | needs of the organization change. |
| í¨í-ê² í-ê³ , | | | | Network traffic can potentially be |
| ìë² | | | | reduced by having functionality servers |
| í"ë¡ê·¸ë¨ì- | | | | strip data to the precise structure |
| ì"구를 í견í-ê³ | | | | required before distributing it to |
| , ë-ë-ë¡ | | | | individual clients at the LAN level. |
| ë¹ì¦ëìS¤ | | | | Multiple server requests and complex |
| ë¡ì§ì | | | | data access can emanate from the middle |
| ìí-í-ë¤. | | | | tier instead of the client, further |
| í´ë¼ì´ì-¸íS¸ | | | | decreasing traffic. Also, since PC |
| 근거í- ê³¼ì -ì | | | | clients are now dedicated to just |
| ì¬ì©ìê° ë³´ê³ | | | | presentation, memory and disk storage |
| ìí¸ ì'ì©í-ëS" ì | | | | requirements for PCs will potentially be |
| ì²ì ì | | | | reduced. |
| ë¶ì©ì´ë¤. | | | | Modularly designed middle tier code |
| í´ë¼ì´ì-¸íS¸ ê³¼ì | | | | modules can be re-used by several |
| -ì í-´ê²°ì±... íS¹ì | | | | applications. Reusable logic can reduce |
| -í- ë...¼ë¦¬ë¥¼ | | | | subsequent development efforts, minimize |
| í¬í-¨í-ê³ ì'ì© | | | | the maintenance workload, and decrease |
| ììS¤í...ì | | | | migration costs when switching client |
| ì¬ì©ìì (TM) | | | | applications. In addition, |
| ëë¨¸ì§ ì¬ì´ | | | | implementation platforms for three tier |
| ê³µì©ìì-ì ì | | | | systems such as OSF/DCE offer a variety |
| ê³µí-ë¤. | | | | of additional features to support |
| í´ë¼ì´ì-¸íS¸ ê³¼ì | | | | distributed application development. |
| -ì ëí- | | | | These include integrated security, |
| ì¬ì©ìê° | | | | directory and naming services, server |
| ê°ììì (TM) ê° (TM) | | | | monitoring and boot capabilities for |
| ì´ í¤ë³´ë", | | | | supporting dynamic fault-tolerance, and |
| ìí¬ìS¤í...ì´ì... | | | | distributed time management for |
| CPU ë° ì£¼ë³ ì¥ì¹ì | | | | synchronizing systems across networks |
| (TM) ìí¸ | | | | and separate time zones. |
| ì'ì©í-ë¤ íì§ | | | | There are of course drawbacks |
| ììì | | | | associated with a three-tier |
| ì²ë¦¬í-ë¤. | | | | architecture. Current tools are |
| í´ë¼ì´ì-¸íS¸ | | | | relatively immature and require more |
| ìí¬ìS¤í...ì´ì...ì | | | | complex 3GLs for middle tier server |
| ì¤'ì"í- ì±ë¶ì | | | | generation. Many tools have |
| í-ê°ëS" ê·¸ëí"½ | | | | under-developed facilities for |
| ì¬ì©ì | | | | maintaining server libraries - a |
| ì¸í°íì´ìS¤ | | | | potential obstacle for simplifying |
| (GUI)ì´ë¤. ì¼ë°ì | | | | maintenance and promoting code re-use |
| ì¼ë¡ ì´ì | | | | throughout an IS organization. More code |
| ì²´ê³ì ë¶ë¶ì | | | | in more places also increases the |
| i.e ì°½ 매ëì | | | | likelihood that a system failure will |
| ì¬ì©ì ì-¡ì...ì | | | | effect an application so detailed |
| ê²ì¶í-ê³ , ì ìì- | | | | planning with an emphasis on the |
| ì°½ì ì²ë¦¬í-ê³ | | | | reduction/elimination of critical-paths |
| ì°½ì- ìëS" | | | | is essential. Three tiers brings with it |
| ìë£ë¥¼ | | | | an increased need for network traffic |
| í'ìí-ë¤. | | | | management, server load balancing, and |
| ìë² í"ë¡ì¸ìS¤: - | | | | fault tolerance. |
| ìë² í"ë¡ì¸ìS¤ | | | | For technically strong IS organizations |
| (í"ë¡ê·¸ë¨)ëS" | | | | servicing customers with rapidly |
| ì"구ë ì-...무를 | | | | changing environments, three tier |
| ì´í-í-´ì | | | | architectures can provide significant |
| í´ë¼ì´ì-¸íS¸ | | | | long-term gains via increased |
| ì"ì²ì | | | | responsiveness to business climate |
| ì±ì·¨í-ë¤. ìë² | | | | changes, code reuse, maintainability, |
| í"ë¡ê·¸ë¨ì | | | | and ease of migration to new server |
| í´ë¼ì´ì-¸íS¸ | | | | platforms and development environments. |
| í"ë¡ê·¸ë¨ì-ì | | | | Comparing two and three tire development |
| ì¼ë°ì ì¼ë¡ | | | | efforts:- The |
| ì"구를, | | | | graphs in Figures 4-6 illustrate the |
| ìí-í-ë¤ | | | | time to deployment for two tiers vs. |
| ë°ì´íë² ì´ìS¤ | | | | three tier environments. Time to |
| 복구를 ë°ê³ | | | | deployment is forecast in overall |
| ê°±ì ì, | | | | systems delivery time, not man-hours. |
| í´ë¼ì´ì-¸íS¸ | | | | According to a Deloitte & Touche study, |
| ì"ì²ì- ë°ì´í | | | | rapid application development time is |
| 무결ì±ê³¼ í견 | | | | cited as one of the primary reasons |
| ì'ëµì | | | | firms chose to migrate to client/server |
| ì²ë¦¬í-ë¤. | | | | architecture. As such, strategic |
| ë-ë-ë¡ ìë² | | | | planning and platform decisions require |
| í"ë¡ê·¸ë¨ì | | | | an understanding how development time |
| ì¼ë° ì ì´ê³ | | | | relates to architecture and how |
| ë³µì¡í- | | | | development time changes as an IS |
| ë¹ì¦ëìS¤ | | | | organization gains experience in c/s. |
| ë¡ì§ì | | | | Figure 4 - Initial Development Effort |
| ìí-í-ë¤. ìë² | | | | Figure 4 shows the |
| 근거í- ê³¼ì -ì | | | | initial development effort forecast to |
| ë¬ë¦´ì§ë | | | | create comparable distributed |
| "ë¤íS¸ìí¬ì- | | | | applications using the common two tier |
| ë¤ë¥¸ 기ê³ì- | | | | and three tier approaches discussed |
| 모른ë¤". ì´ | | | | above. The three tier application takes |
| ìë²ëS" ì£¼ì¸ | | | | much longer to develop - this is due |
| ì´ì ì²´ê³ ëëS" | | | | primarily to the complexity involved in |
| ë¤íS¸ìí¬ íì¼ | | | | coding the bulk of the application logic |
| ìë²ì¼ ì | | | | in a lower-level 3GL such as C and the |
| ìì-ë¤; ìë²ëS" | | | | difficulties associated with |
| ê·¸ ë- ì ê³µí- ë' | | | | coordinating multiple independent |
| ë¤ íì¼ ììS¤í... | | | | software modules on disparate platforms. |
| ìë¹ìS¤ ë° ì ì² | | | | In contrast, the two-tier scheme allows |
| ìë¹ìS¤ì´ë¤. | | | | the bulk of the application logic to be |
| ëëS" ì-´ë- í- | | | | developed in a higher-level language |
| ê²½ì°ì-ëS", ë¤ë¥¸ | | | | within the same tool used to create the |
| íìì© ê¸°ê³ëS" ì | | | | user interface. |
| ì² ìë¹ìS¤ë¥¼ ì | | | | Figure 5 - Subsequent Development |
| ê³µí-ë¤. ìë² | | | | Efforts Subsequent |
| í"ë¡ì¸ìS¤ëS" | | | | development efforts may see three-tier |
| ë°ì´íë² ì´ìS¤ | | | | applications deployed with greater speed |
| ì¸ì 기ê³, íµì | | | | than two tier systems (Figure 5). This |
| ì-°ê²°, ëëS" ë'ì | | | | is entirely due to the amount of |
| ê°-í (TM) "í- | | | | middle-tier code, which can be re-used |
| ê°ê³µì-...ìì (TM) ê° | | | | from previous applications. The speed |
| (TM) ì ê³µì | | | | advantage favoring the three-tier |
| ììì ì²ë¦¬í-ëS" | | | | architecture will only result if the |
| ìí"íS¸ì¨ì-´ | | | | three-tier application is able to use a |
| ì-"ì§ì¼ë¡ ì'ë (TM) | | | | sizable portion of existing logic. |
| í-ë¤. ìë² | | | | Experience indicates that these savings |
| í"ë¡ì¸ìS¤ëS" ì | | | | can be significant, particularly in |
| ì¬í- ì ì²ì- | | | | organizations, which require separate |
| ì¼ë°ì ì¸ íë¶ | | | | but closely related applications for |
| ì-...무를 | | | | various business units. Re-use is also |
| ì´í-í-ë¤. | | | | high for organizations with a strong |
| ê³ì°í-ëS" | | | | enterprise data model because |
| í´ë¼ì´ì-¸íS¸ | | | | data-access code can be written once and |
| ìë²: - | | | | re-used whenever similar access needs |
| â¢ ë¨ í-ë | | | | arise across multiple applications. The |
| í´ë¼ì´ì-¸íS¸, ë¨ | | | | degree of development time reduction on |
| í-ë ìë² | | | | subsequent efforts will grow as an |
| ⢠ë¤ì | | | | organization deploys more c/s |
| í´ë¼ì´ì-¸íS¸, ë¨ | | | | applications and develops a significant |
| í-ë ìë² | | | | library of re-usable, middle-tier |
| í´ë¼ì´ì-¸íS¸ | | | | application logic. |
| ìë² | | | | Figure 6 - Client Tool Migration |
| í´ë¼ì´ì-¸íS¸ | | | | Figure 6 makes the |
| ìë² ê³ì°ì´ | | | | important case for code savings when |
| 모ë"ë³ | | | | migrating from one client development |
| í"ë¡ê·¸ë¨ì | | | | tool to another. It was stated earlier |
| ë...¼ë¦¬ì ì¸ | | | | that client tools are highly proprietary |
| ì-°ì¥ì¸ ìë² | | | | and code is not portable between the |
| í"ë¡ì¸ìS¤ì-ì | | | | major vendor packages. The point was |
| ìë¹ìS¤ë¥¼ | | | | also made that the PC tools market is |
| ì"구í-ëS" | | | | highly volatile with vendor shakeouts |
| í´ë¼ì´ì-¸íS¸ ê³¼ì | | | | and technical "leapfrogging" |
| -ì í¬í-¨í-ëS" | | | | commonplace. In a two-tier environment, |
| ì»´í"¨í° ê±´ì¶-ì ì | | | | IS organizations wishing to move from |
| ì´ë¤. 모ë"ë³ | | | | one PC-based client development platform |
| í"ë¡ê·¸ë¨ì | | | | to another will have to scrap their |
| ê·¸ê²ì êµ¬ì± | | | | previous investment in application logic |
| ë¶ë¶ ("ë¨ì")ë¡ | | | | since most of this logic is written in |
| ìí"íS¸ì¨ì-´ì í° | | | | the language of the proprietary tool. In |
| ì¡°ê°ì ë³ê±°ê° | | | | the three-tier environment this logic is |
| ë" ì¬ì´ ë°ë¬ ë° | | | | written in a re-usable middle tier, thus |
| ë" ëì ì | | | | when migrating to the new tool, the |
| ì§ê°ëS¥ì±ì | | | | developer simply has to create the |
| ìí- ê°ëS¥ì±ì | | | | presentation and add RPC calls to the |
| 창조í-ã´ë¤ëS" | | | | functionality layer. |
| ê²ì ê·¸ê²ì | | | | Flexibility in re-using existing |
| 기본ì ì¸ ê°ì | | | | middle-tier code can also assist |
| -ì¼ë¡ ìë¤. | | | | organizations developing applications |
| í´ë¼ì´ì-¸íS¸ | | | | for various PC client operating system |
| ìë² ê³ì°ì ê·¸ | | | | platforms. Until recently there were |
| ë¨ìê° ë (TM) ì¼í- | | | | very few cross-platform client tool |
| 기ì-µ ì¥ì ê³µê° | | | | development environments and most of |
| ì-ì- 모ë'를 | | | | today's cross-platform solutions are not |
| ìí-ëã´ë¤ëS" | | | | considered "best-of-breed". In a |
| ê²ì í-ì"ë¡ | | | | three-tier environment separate client |
| í-ì§ ì-SëS"ë¤ëS" | | | | tools on separate platforms can access |
| ê²ì ì¸ìí-´ì | | | | the middle tier functionality layer. |
| ì´ê²ì-ê² | | | | Coding application logic once in an |
| ì¡°ì¹ë¥¼ ë©ë¦¬ | | | | accessible middle tier decreases the |
| ì·¨í-ë¤. ì´ | | | | overall development time on the |
| ê±´ì¶-ì ë¡, ë¶ë¥´ëS" | | | | cross-platform solution and it provides |
| ë¨ìëS" | | | | the organization greater flexibility in |
| "í´ë¼ì´ì-¸íS¸"ì- | | | | choosing the best tool on any given |
| (ìë¹ìS¤ë¥¼ | | | | platform. |
| ì"구í-ëS" ì ê²) | | | | The characteristics of client/server |
| ì-´ì¸ë¦¬ê³ , ë¶ë¦° | | | | architecture:- |
| ë¨ìëS" "ìë²"ê° | | | | The basic characteristics of client |
| ëë¤ (ìë¹ìS¤ë¥¼ ì | | | | server architectures are: |
| ê³µí-ëS") ì ê². | | | | 1) Combination of a client or front-end |
| ì´ê²ì ë...¼ë¦¬ì | | | | portion that interacts with the user, |
| ì¸ ì-°ì¥ì | | | | and a server or back-end portion that |
| ê·¸ë"¤ì 기ëS¥ì | | | | interacts with the shared resource. The |
| ìí- ì í-©í- | | | | client process contains |
| í-ë"ì¨ì-´ì (TM) | | | | solution-specific logic and provides the |
| ìí"íS¸ì¨ì-´ | | | | interface between the user and the rest |
| í"ëíS¸í (TM) ì- ë¬ë | | | | of the application system. The server |
| ¤ í´ë¼ì´ì-¸íS¸ì (TM) | | | | process acts as a software engine that |
| ìë²ë¥¼ | | | | manages shared resources such as |
| ë¹ì¹í-ëS"ì´ë¤. | | | | databases, printers, modems, or |
| ì를 ë"¤ë©´, ì²ë¦¬ | | | | high-powered processors. |
| íì¼ì ìí- | | | | 2) The front-end task and back-end task |
| íS¹ë³í- | | | | have fundamentally different |
| ì±ë¶ì¼ë¡ ì§ë¬¸, | | | | requirements for computing resources |
| ëëS" í"ëíS¸í (TM) | | | | such as processor speeds, memory, disk |
| ì- ë¬ë¦¬ëS" íì¼ | | | | speeds and capacities, and input/output |
| ìë²ë¥¼ | | | | devices. |
| ì¤í-í-기 ìí-ì-¬ | | | | 3) The environment is typically |
| íS¹ë³í-ê² | | | | heterogeneous and multiFinder. The |
| ë""ìì¸ëê³ | | | | hardware platform and operating system |
| í-ì±ëëS" í"ëíS¸í | | | | of client and server are not usually the |
| (TM) ì- ë¬ë¦¬ëS" | | | | same. Client and server processes |
| ë°ì´íë² ì´ìS¤ | | | | communicate through a well-defined set |
| ê´ë¦¬ ì²´ê³ ìë². | | | | of standard application program |
| ë¤íS¸ìí¬ ê³ì° | | | | interfaces (API's) and RPC's. |
| ê±´ì¶-ì : - | | | | 4) An important characteristic of |
| Oracleì ë¤íS¸ìí¬ | | | | client-server systems is scalability. |
| ê³ì° ê±´ì¶-ì (NCA)ëS" | | | | They can be scaled horizontally or |
| 3ê°ì ê°ë...ì- | | | | vertically. Horizontal scaling means |
| ìí-´ ë¶ (TM) ì¡ì | | | | adding or removing client workstations |
| ì ìë¤: | | | | with only a slight performance impact. |
| 1.The ì"ë" ì (TM) ì´ë" | | | | Vertical scaling means migrating to a |
| ì¹ì ì -ë§ | | | | larger and faster server machine or |
| í¸ì¬í-ëS" | | | | multiservers. |
| ìë¹ìS¤ì´ë¤. | | | | Client-server applications:- |
| 2.The Java ê°ì 머ì | | | | We define a client-server application |
| ì (ëëS" 곧 ë | | | | as: |
| ê²ì´ë¤) ì¹ | | | | An application system in which logically |
| ë¸ë¼ì°ì ì-ì-ì | | | | separate software components are |
| 묻í ì -ë§ | | | | integrated together via client-server |
| í¸ì¬í-ëS" | | | | relationships. In a |
| ìë¹ìS¤ì´ë¤. | | | | client-server relationship, one part of |
| Oracle ë°ì´íë² | | | | an application (the client end) uses a |
| ì´ìS¤ ì-"ì§ì | | | | service provided by the other part (the |
| ê°ì§ ì ì² ë©í' | | | | server end). The latter is often a |
| (ì ëìS¤ í° | | | | shared resource, used by many clients. |
| ìë²ì-), | | | | Although integrated together via the |
| í´ë¼ì´ì-¸íS¸ì- | | | | client-server relationship, the parts |
| ê²½ë Java ì- | | | | remain separate. We refer to them as |
| í"리ì¼ì´ì..., ë° | | | | being logically separate because they |
| ì¤'ì- (TM) 층ì ìí- | | | | need not be physically remote from one |
| 3.A 3 층층 모í-ì 2 | | | | another (they might be in the same |
| ì¬ì´ ì¶ì...구를 | | | | computer). We describe |
| ì ê³µí-기 ìí-ì-¬ | | | | client-server application software here |
| ìë²ë¥¼ | | | | in three steps: splitting an |
| "í-ì±í-ë¤". | | | | application, joining separate |
| OracleëS" 1998ë...ì | | | | applications together, and distributed |
| 1ì"ì-ì 릴리ìS¤ 10.7 | | | | application structure |
| NCA (ì¹ ë°°ì¹ë ì | | | | Splitting an application:- |
| ì²)를 ë°ì¡í-ëS" | | | | Figure 5 Application software modularity |
| ìì'ëì-ë¤â¦. | | | | There are many ways of |
| 2000ëS" ì"구í-ë¤ | | | | partitioning application software into |
| ë°©ì¶ 10.7 NCAë¡, OracleëS" | | | | separate components. However, the |
| ë'ë'í- | | | | content of most applications can usually |
| í´ë¼ì´ì-¸íS¸ì-ì | | | | be classified under three different |
| ê¹ê¸°ì ì-´ë ¤ìì- | | | | technical headings: data management, |
| ê³ ê° í"¼ë"ë°±ì- | | | | application logic and presentation. This |
| ë°ì'í-ë¤. | | | | is illustrated in figure 5. |
| 기ëS¥ì´ 10 SCì (TM) 10 NCA | | | | If the application is to be split into |
| ì¬ì´ì-ì ë (TM) ì¼ | | | | two parts (one part on a client |
| ìë"ë¼ë, OracleëS" | | | | platform, the other on a server |
| 과립ì ê¹ëS" ì | | | | platform), the split can be made at |
| ëµì- ì¹ ë°°ì¹í- | | | | either of the two boundaries between |
| 릴리ìS¤ì-ì ëë | | | | functions, or inside one of the three |
| ¤ë³´ëë¤. ì´ ì | | | | functions. Consequently there are five |
| ëµì ëí- ë³´ì¡´ | | | | main ways of splitting a centralized or |
| ìí' 주문í (TM) "를 | | | | personal application into two parts |
| ëì-ì§ë¤. í-ê²S | | | | between which there is a client-server |
| ì¡°ê°ì ì | | | | relationship. This is the basis of the |
| ì©í-기 íì- | | | | popular classification into five |
| íìì´ ì§ê¸ ë" | | | | client-server styles, which is promoted |
| ì½ê¸° 모ì-' 기ì | | | | by the Gartner Group. It is illustrated |
| ì´ ì-ê°ì | | | | in figure 6. |
| ê°ì-ë기 ì¹ | | | | Figure 6 Five generic styles of basic |
| ë°°ì¹í-기 | | | | client-server structure |
| 릴리ìS¤ì- ìëS" | | | | The details need not concern us here. |
| ìë²ì- ë¬ë¦¬ê³ | | | | The important point is that different |
| 기 ë-문ì-. ê¹ëS" ì | | | | styles suit different needs and |
| ëµì- ìëS" ë¤ë¦ | | | | circumstances: |
| ë-문ì-, OracleëS" ê³ ê° | | | | ⢠The two styles on the left of |
| ì¬ì© ë'ë'í- | | | | the diagram are typical of centralized |
| í´ë¼ì´ì-¸íS¸ë¥¼ | | | | interactive applications that have been |
| ì-ë (TM) ëë¤ | | | | adapted to client-server by means of |
| ì¶"ì²í-ê³ ë (TM) | | | | graphical interface technology, terminal |
| ì¼í- ê²½ì°ì- ìëS" | | | | emulation, etc. |
| 10.7 NCA를 í'ì-´ | | | | ⢠The style in the middle of the |
| ë"ëS"ë¤. OracleëS" ê·¸ë° | | | | diagram is typical of object-oriented |
| ì¤ê³½ì | | | | distributed applications and distributed |
| ì§ìí-ì§ ì-Sì | | | | TP applications in which data and |
| ê²ì´ë¤. | | | | function are encapsulated together |
| Customerncharactermode | | | | behind application interfaces |
| ìëª...ì ì¹ | | | | ⢠The two styles on the right of |
| ë°°ì¹í- 릴리ìS¤ì- | | | | the diagram are typical of data-centered |
| ì§ì 'ì ì¼ë¡ ì´ë | | | | applications using client-server 4GL |
| (TM) í-´ì-¼ í-ë¤ | | | | development tools and relational |
| ì¥ 5 | | | | database products Some |
| í´ë¼ì´ì-¸íS¸ | | | | applications combine all three areas of |
| ìë² ê¸°ì : - | | | | function (presentation, application |
| í´ë¼ì´ì-¸íS¸ | | | | logic and data management) at the |
| ìë² ê¸°ì ì ì | | | | personal platform. Also, different |
| ì°ë¦¬ê° 4ê°ì | | | | styles may occur in combination at the |
| ì§ì-ì-ì | | | | same platform. |
| ê·¸ê²ì í ë¡ í-ëS" | | | | Joining applications together:- |
| ê²½ì°ì- | | | | One of the great strengths of |
| ì´í-´ëë¤: | | | | client-server is the ability to join |
| 1.Personal í"ëíS¸í (TM) | | | | separate applications together. This can |
| 2.Server í"ëíS¸í (TM) | | | | be done in many ways; but upon the |
| 3.Client ìë² | | | | principles used in 2.4.1, there are |
| 미ë"¤ì¨ì-´ | | | | essentially three levels at which |
| 4.Client ìë² ê³µêµ¬ì | | | | applications can interface with one |
| (TM) ìë¹ìS¤ | | | | another. This is illustrated in figure |
| ì´ ì§ì-ì | | | | 7. |
| ê°ê°ì ê·¸ë"¤ | | | | Figure 7 Three levels at which |
| ì¬ì´ ì¤ë²ë©ì´ | | | | applications can be joined together |
| ìì ì | | | | The main characteristics and advantages |
| ìë"ë¼ë, íS¹ì | | | | and disadvantages of these three |
| í-ë¤. | | | | approaches are: |
| ê¸°ê° í"ëíS¸í (TM) | | | | ⢠At presentation level: |
| ì í-ë"ì¨ì-´ì (TM) | | | | Interaction at this level is achieved |
| ì´ì ì²´ê³ | | | | via direct data exchange (DDE) within a |
| ìí"íS¸ì¨ì-´ì ì | | | | window management system, or via |
| (TM) ì í- ì¡°í-©ì¸ | | | | scripting; see [Duxbury, 1994], in which |
| ì»´í"¨í° í"ëíS¸í | | | | software uses an application's user |
| (TM) ì ì-¸ê¸í-ëS" | | | | interface by simulating a human user. |
| ì-¬ê¸°ì-ì | | | | This kind of technique is often referred |
| ì¬ì©ëë¤. | | | | to as screen scraping. It is very useful |
| ê°ì¸ í"ëíS¸í (TM) : | | | | for accessing legacy applications, but |
| - ê°ì¸ í"ëíS¸í (TM) | | | | leads to software maintenance problems |
| ì ì-ë§ | | | | if the user interfaces need to change. |
| í´ë¼ì´ì-¸íS¸ | | | | ⢠At application function level: |
| ìë² ê¸°ì ì | | | | Interaction at this level is in terms of |
| ê°ì¥ íS¹ì í- | | | | business functions. Therefore, the |
| ì§ì-ì´ë¤. | | | | inter-application requests are about the |
| ì°ë¦¬ëS" ê°ì¸ | | | | business meanings of the application |
| í"ëíS¸í (TM) ì | | | | (and not its presentation or database |
| ë¤ìê³¼ ê° (TM) ì ì | | | | encoding). This has the advantage of |
| -ìí-ë¤: | | | | keeping their internal designs separate |
| ë¤íS¸ìí¬ì- | | | | from their external interactions. There |
| ì-°ê²°ëëS", ì»´í"¨í° | | | | are fewer software maintenance problems. |
| í"ëíS¸í (TM) ì | | | | ⢠At data management level: |
| ì¼ê´ë ì§ê´ì | | | | Interaction at this level is by direct |
| ì¸ ì¬ì©ì | | | | access to the other application's |
| ì¸í°íì´ìS¤ ë° | | | | database. This is common practice, but |
| 기ì-...ì ëì | | | | leads to software maintenance problems |
| ì¼ë¡ ì-...무를 | | | | when application data structures change. |
| ë¬ì±í-기 ìí-ì-¬ | | | | The first and third approaches inhibit |
| ê°ì¸ ì¬ì©ì | | | | potential for change, the second does |
| ìì¡°í-기 ì | | | | not. Further distinctions can be made |
| ê³µí-ë¤. ì´ | | | | between direct and indirect interaction |
| íS¹ì±ì ì«ì | | | | between applications, synchronous and |
| 2ì-ì ì¤ëª...ëë¤. | | | | asynchronous interaction, and externally |
| ê°ì¸ í"ëíS¸í (TM) | | | | programmed interaction and internally |
| ì ê´ê³ë ì¸ê³ | | | | programmed interaction. |
| êµëí-ê² ê°-ë ¥í-, | | | | Distributed application structure:- |
| ê³µê¸ìì ë"ì | | | | Distributed applications |
| ì íì´ ìë¤. | | | | are evolving towards richly connected |
| ì»´í"¨í°ì ë§ì | | | | network structures of the kind |
| ë¤ë¥¸ ì¢...ë¥ëS" | | | | illustrated in figure 8. The circles |
| ê°ì¸ í"ëíS¸í (TM) | | | | represent separate software components, |
| (ì를ë"¤ë©´ MS/DOS PC, | | | | and the lines represent client-server |
| ì°½ PC, OS/2 PC, ì ëìS¤ | | | | relationships between them. This is |
| ìí¬ìS¤í...ì´ì..., | | | | typical of the kind of structure that |
| Apple 매í¨í ì, ë° | | | | results from use of object-oriented |
| ê°ì¢... ìí- | | | | design and distributed object |
| ì¥ì¹)ì¼ ì ìë¤; | | | | management. |
| ê·¸ë¬ë ì¼ë°ì | | | | Figure 8 Complex distributed application |
| ì¸ ì¼ì´ìS¤ëS" | | | | There is also |
| ì¤ëS Microsoft Windows | | | | large-scale structure of distributed |
| ì´ì ì²´ê³ë¥¼ | | | | application systems (within which the |
| ê°ì§ IBM í¸í (TM) ì© | | | | individual client-server relationships |
| PCì´ë¤. ê·¸ë° | | | | occur). Typically, three tiers of |
| í"ëíS¸í (TM) ì | | | | application software can be discerned in |
| ì§ê¸ í-ì"í-ë¤ | | | | the large-scale structure: |
| ì-´ë""ë" ì§ ë³´í¸ì | | | | ⢠Front tier: Application |
| ì¼ë¡ ì ë¹í-ë¤. | | | | software (and databases) at personal |
| ì´ê²ì ì»´í"¨í° | | | | platforms, providing all kinds of |
| ììS¤í... ì-ì | | | | application services, using local |
| ê±´ì¶-ì ì ë°-ì¼ë¡ | | | | resources and remote resources. |
| ëì-ë¤: ì¤ëë | | | | Typically, the platforms are PCs. This |
| ì´ì ì ê·¸ê² | | | | tier is where the greatest amount of |
| ì¬ì©ìì-ê²ì | | | | computer power and of new application |
| ë©ì-ë ì¤'ì- (TM) | | | | software is now being deployed. |
| 기ê³ì- ìëS" | | | | ⢠Middle tier: Application |
| ë¶ì¡±í- ìì | | | | software (and databases) at server |
| ì´ì-ë¤; ìë¡ì´ | | | | platforms, providing the back-end of |
| ì´ì ì ê° ë¨ë... | | | | personal applications, shared workgroup |
| ì¬ì©ì ìê°ë½ | | | | services and task-oriented services. |
| ëì- ì§ê¸ | | | | Typically, the platforms are UNIX or PC. |
| í'ë¶í- ê°ì¸ | | | | This tier provides rapid adaptation to |
| ììì´ë¤. PC | | | | business process change, without needing |
| ê°ê²©/ì±ëS¥ | | | | changes to the back tier. It puts |
| ë¹ì¨ì´ì ëëS" | | | | boundaries around the turbulence and |
| ì´ë ê² ì"ì¸ | | | | uncertainty generated in the volatile |
| 2ê°ì 매 18 ë¬ì- | | | | world at the first tier, where all the |
| ìí-ì-¬ í-¥ìí-기 | | | | users are. It also provides lateral |
| ê²ì ê³ìí-기 | | | | linkage across the enterprise (e.g. |
| ë-문ì-, ì´ ë (TM) | | | | electronic mail services). |
| í-¥ì-ëS" ê³ì | | | | ⢠Back tier: Application |
| ì¦ê°í-ëS" íì´ | | | | software and databases at server |
| ìë¤. ì´ì ì ì´ | | | | platforms providing corporate |
| ë³í (TM) "ëS" ì¬ì-... | | | | information services. These are usually |
| 구조ì- ìëS" ë³í | | | | functionally partitioned (e.g. accounts, |
| (TM) "를 ë§ì¶ë¤: | | | | manufacturing, personnel). Typically, |
| ì¡°ì§ ìì-´ì | | | | the platforms are mainframes. This tier |
| ííí-ê² í-ê³ | | | | provides the core of shared and |
| ìë¤, ì -ì±... ì...ì- | | | | long-lived information assets that |
| ê¶ìëS" ì-'ëëê³ | | | | everything else depends on. There are |
| ìë¤, ê·¸ë¦¬ê³ | | | | strong guarantees of data integrity, and |
| ê·¸ê² ê°ëS¥í-ê² | | | | the applications and databases are |
| ë ê³¼ì -ì ì§ê¸ | | | | stable, and their design changes rather |
| ì¬ë¬´ì¤ ì§ìì- | | | | slowly. |
| ìí-´ ì´ì ì- ì | | | | This structure separates different kinds |
| ê³µë ê³¼ì -ì ì | | | | of concerns, which used to be bundled |
| ê³µí- ì ìë¤. | | | | together in centralized |
| ì´ì ê²°í-©í- í¨ë | | | | computingchapter-8 |
| ¥ì ì±...ìì- | | | | Important of client server:- |
| ì¬ì-...ê³¼ 기ì ì | | | | Advantages of Client-Server:- |
| ì¸ ë (TM) í-¥ | | | | ÃPotential of reduced cost |
| ê°ì¸ì ê°ì¸ | | | | ÃImproved performance |
| í-ê°ì´ë¤. PCëS" | | | | ÃIncreased security |
| ê°ì¸ ìì°ë ¥ ë° | | | | ÃMore GUI application |
| ë...립ì ì | | | | ÃGives people the opportunity to make |
| ê³µí-ë¤, ê·¸ë¬ë | | | | change for better |
| PCì ê±°ëí- ìì- | | | | ÃBetter SW development tools once |
| ìí-´ ê³±í- ì´ | | | | established |
| ê°ì²´ëS" ëí-, 무ì | | | | ÃExploits existing H/W, S/W |
| -ë¶ë¥¼ 창조í- ì | | | | configurations |
| ìë¤. | | | | ÃMatches distributed business models |
| í´ë¼ì´ì-¸íS¸ | | | | ÃScalable |
| ìë²ëS" ì´ ë¬¸ì | | | | ÃFlexibility and cost saving |
| 를 ê²°ì¬í-ëS" | | | | ÃFlexibility business modeling |
| ê²ì ë-ëS"ë¤. | | | | ÃMaximum technology component choice |
| (ìë² í"ë«í¼ì- ì | | | | ÃEfficient use of computing resources |
| ê³µëëS") | | | | ÃData interchangeability and |
| í´ë¼ì´ì-¸íS¸ì | | | | interoperatability |
| ì¬ì© ê³µì ìì, | | | | ÃEnhanced data sharing |
| ì -ë¹í-ì§ ì-Sì | | | | ÃIntegrated services |
| ê°ì¸ ìì; | | | | ÃSharing resources among devices |
| í´ë¼ì´ì-¸íS¸ | | | | platforms |
| ìë² êµ¬ì¡°ëS" 모ë" | | | | ÃLocation independence data and |
| ìí"íS¸ì¨ì-´ì (TM) | | | | process |
| í-ë"ì¨ì-´ ììì | | | | ÃTechnology revolution |
| ê±´ì¶-ê³¼ ê´ë¦¬ íµì | | | | ÃFuture technology |
| ì ë°'ì- ìëS" | | | | ÃRelational databases |
| ê°ëS¥í-ê² í-ë¤. | | | | ÃDisadvantages of Client-Server:- |
| ê·¸ê²ì ê°ì¸ê° | | | | ÃHeavy up-front cost |
| ê³ì°í-ê³ enterprise-wide | | | | ÃInitial performance decline |
| ê³ì°ì¼ë¡ ê°ì¸ | | | | ÃLack of skilled professionals |
| 측ì -ì | | | | ÃNeed of rewrite a lot of software |
| ë³í-ìí¨ë¤. ì´ | | | | ÃNeed for retraining user |
| íS¹ì±ì ì¬ì-... ê³¼ì | | | | ÃDependability- when the server goes |
| -ì ìì, | | | | down, operational cases |
| ìí¬ê·¸ë£¹ ë¨ê²°ë | | | | ÃLack of mature tools |
| ¥, ìì°ë ¥ ë° | | | | ÃLack of the scalability-network |
| ìµíµì±ì | | | | operating system (e.g. novel NetWare, |
| 창조í-ëS" ê²ì | | | | window NT server) are not very scalable |
| ë-ëS"ë¤. ê°ì¸ | | | | ÃHigher then anticipated costs |
| í"ëíS¸í (TM) ì´ | | | | ÃHarder to build |
| í´ë¼ì´ì-¸íS¸ | | | | ÃLess stable |
| ìë²ì- | | | | ÃSusceptible to network load |
| ìì§ìì ìí- | | | | ÃLacking in the specialists |
| 주ì" ê²½ì ì (TM) | | | | ÃDifficult to debug |
| 기ì ì ì¸ ìë (TM) | | | | ÃDifficult to test |
| ë ¥ì´ë"ë¼ë, | | | | Client/Server Business Application |
| ë¨ë©´ë 2ì | | | | Architectures: |
| ìì'ì- í (TM) -ì¸ë | | | | Traditional applications architectures |
| 5ê°ì 기ì ì ì¸ | | | | have been based on function today, to |
| ì±ë¶ì ë¨ì§ | | | | meet the needs of the business an |
| 첫ë²ì§¸ì´ë¤. | | | | application architecture should reflect |
| ìë² í"ë«í¼: - | | | | the complete range of business |
| ì°ë¦¬ëS" ìë² | | | | requirements. |
| í"ë«í¼ì | | | | Therefore, client/server computing |
| ë¤ìê³¼ ê° (TM) ì ì | | | | demands a three layer view of |
| -ìí-ë¤: | | | | theorganization. |
| ìí"íS¸ì¨ì-´ê° | | | | 1 The user interface layer, which |
| ê·¸ê²ì ì ê³µí-ëS" | | | | implements the functional model |
| ì»´í"¨í° í"ëíS¸í | | | | 2 The business function layer, which |
| (TM) ì ì²´ê³ì-ì | | | | implements the process model |
| ì¬ì©ì ìí-´ | | | | 3 The data layer, which implements the |
| ë¤ë¥¸ ê³³ì- | | | | information model |
| ìë¹ìS¤í-ë¤. | | | | It should be noted that this application |
| ìë¹ìS¤ëS" ê°ì¸ | | | | architecture does not demand multiple |
| í"ëíS¸í (TM) ì- | | | | hardware platforms, although such |
| ê¶ê·¹ì ì¼ë¡ | | | | technology can be utilised,if the |
| ì¬ì©ëë¤; | | | | environment is robust and reliable |
| ê·¸ë¬ë ìë¹ìS¤ëS" | | | | enough and the business is prepared to |
| ëí- ë¤ë¥¸ ìë² | | | | pay the additional costs associated with |
| í"ë«í¼ì- | | | | workstation and LAN technology. |
| ì¬ì©ì ì | | | | Business Benefits: - There is a |
| ê³µëë¤. ìë² | | | | perceived need for vendor independence. |
| í"ë«í¼ì ê°ì¸ | | | | This includes application development |
| í"ëíS¸í (TM) ì¼ë¡ | | | | methodologies, programming paradigms, |
| ì격ì ì£¼ì§ ì-SëS" | | | | products and architectures. - |
| ìì¡´í-ëS" 맨ëì | | | | Organization have changed from steep |
| íµí-´ ìë¹ìS¤ë¥¼ ì | | | | hierarchies to flattened hierarchies - |
| ê³µí- ì§ë | | | | Network management is replacing vertical |
| 모른ë¤. ê±°ì | | | | management - There is a change to team |
| ì¨ê°- ì»´í"¨í° | | | | based management - The customer should |
| í"ëíS¸í (TM) ì | | | | have a single point of contact for all |
| ìë² | | | | business with the |
| í"ë«í¼ì¼ë¡ ì'ë | | | | organization - The customer should deal |
| (TM) í- ì ìë¤. | | | | with the same person over multiple |
| ê·¸ë¬ë¯ë¡, ìµê³ | | | | contacts. - The user will perform as |
| ì»´í"¨í°ì-ì PCì- | | | | much processing as possible during |
| ìë² í"ë«í¼ì | | | | customer contact time - The time |
| ë§ì ë¤ë¥¸ | | | | required to complete the work will be |
| ê³µê¸ì ë° ë§ì | | | | minimized - There is a need for |
| ê°ëS¥í- ì¢...ë¥ê°, | | | | empowerment of staff and audit trail of |
| ìë¤. ê°ê°ì | | | | actions - Multi-skilled and |
| í'ì¤ ë...¸ë (TM) | | | | multi-function teams need access to |
| ëì íS¹ì - ì¢...ë¥, | | | | multiple applications |
| ë¤ë¥¸ í'ì§ | | | | Different types of servers:- |
| í-ì"ì¡°ê±´, ë° | | | | The simplest form of servers are |
| ê°ê²©ê³¼ ì±ê³¼ | | | | disk servers and file servers. With a |
| ìS¤í (TM) íS¸ë¼ì | | | | file server, the client passes requests |
| ë¤ë¥¸ ì§ì-ì-ì | | | | for files or file records over a network |
| ì¢ë¤. ì¬ì©ì | | | | to the file server. This form of data |
| 기ì-...ì ë¤ë¥¸ | | | | service requires large bandwidth and can |
| ë¤ë¥¸ í-ì"ì (TM) | | | | slow a network with many users down |
| ì¼ì¹í-기 ìí-ì-¬ | | | | considerably. Traditional LAN computing |
| í"ëíS¸í (TM) ì ì ì | | | | allows users to share resources, such as |
| -í- ì ìë¤. ì | | | | data files and peripheral devices, by |
| íì ì´ íì | | | | moving them from standalone PCUs onto a |
| ë³´ì-¬ì£¼ëS" ì«ì | | | | Networked File Server (NFS). |
| 3ì-ì ê°ì¸ | | | | The more advanced form of servers |
| í"ëíS¸í (TM) ì- | | | | are database servers, transaction server |
| ì¬ì©ìëS" ë§ì | | | | and application servers (Orfali and |
| ìë² í"ë«í¼ì- | | | | Harkey 1992). In database servers, |
| ìë¹ìS¤ì- ì 'ê·¼ì´ | | | | clients pass SQL (Structured Query |
| ììì§ë | | | | Language) requests as messages to the |
| ëª¨ë¥¸ë¤ | | | | server and the results of the query are |
| ì¤ëª...ëë¤. | | | | returned over the network. The code that |
| ì´ê²ì ëí- | | | | processes the SQL request and the data |
| ì§ê¸ ì»´í"¨í° | | | | resides on the server allowing it to use |
| íµì ë§ì-ì | | | | its own processing power to find the |
| ë§ì ë¤ë¥¸ | | | | requested data, rather than pass all the |
| ê·¼ìì-ì ë¤ë¥¸ | | | | records back to a client and let it find |
| ê³³ì- ìë¹ìS¤í-ëS" | | | | its own |
| ê·¸ê²ì ì íí- | | | | Data as was the case for the file |
| ì§ë ëª¨ë¥¸ë¤ | | | | server. In transaction servers, clients |
| ê°ì¸ í"ëíS¸í (TM) | | | | invoke remote procedures that reside on |
| ì- ë¨ë... ì¬ì©ì- | | | | servers, which also contain an SQL |
| ì´ì ì êµë를 | | | | database engine. There are procedural |
| ì¤ëª...í-ë¤. | | | | statements on the server to execute a |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | group of SQL statements (transactions), |
| ìë² í"ëíS¸í (TM) | | | | which either all succeed or fail as a |
| ì¼ë¡ ì²´ê³ì | | | | unit. The applications based on |
| ë¶ê·¹ì ê°ì¸ìì | | | | transaction servers are called On-line |
| (TM) ê³µì ìì | | | | Transaction Processing (OLTP) and tend |
| ì¬ì´ 구ë³ì | | | | to be mission-critical applications, |
| ì¸ìí-ë¤. ê° | | | | which require 1-3 second response time, |
| ê°ì¸ í"ëíS¸í (TM) | | | | 100% of the time and require tight |
| ì ì´ë (TM) í- ì | | | | controls over the security and integrity |
| ìì ì§ë | | | | of the database. The communication |
| ëª¨ë¥´ê³ ë¤ ì°ì-°í- | | | | overhead in this approach is kept to a |
| ìì¤ ììì | | | | minimum as the exchange typically |
| ìí-ì- ë"ë¬ë´ëS" | | | | consists of a single request/reply (as |
| ë...립ì ì¸ ê°ì¸ | | | | opposed to multiple SQL statements in |
| ììì´ë¤. | | | | database servers). Application servers |
| ì-ì¼ë¡, ìë² | | | | are not necessarily database centered |
| í"ë«í¼ì ê³µì | | | | but are used to server user needs, such |
| ììì ë³´í¸í-ê³ | | | | as. |
| , ê³ ì¹ê³ , | | | | Download capabilities from Dow Jones or |
| 주ìê¹Sê² | | | | regulating a electronic mail process. |
| ì²ë¦¬í- í (TM) ê²½ì | | | | Basing resources on a server allows |
| ì ê³µí-ë¤. | | | | users to share data, while security and |
| ì«ìì-ì ì íí- | | | | management services, which are also |
| ê²ì´ë¤ 3ê°ì | | | | based in the server, ensure data |
| ë§ì ìë² | | | | integrity and security. |
| í"ë«í¼ ë (TM) | | | | Special types of Architecture: IBM's |
| ì¼í- 기ì ì´ë¥¼ | | | | System Application Architecture: |
| ìí-´ | | | | SAA is a collection of |
| í´ë¼ì´ì-¸íS¸ì (TM) | | | | selected software interfaces, |
| ìë² í"ëíS¸í (TM) | | | | conventions, and protocols that are used |
| (기ê³ì¤ë¹ì ë | | | | as a framework for developing |
| (TM) ì¼í- ì¢...ë¥ë¥¼ | | | | consistent, integrated applications |
| ê°ì§ ì를ë"¤ë©´ | | | | across the major IBM computing |
| PCì (TM) ì´ì ì²´ê³) | | | | environments. |
| ì¬ì©ëë¤ | | | | Four major components of this |
| ì-´ë""ë¼ë, | | | | architecture are: - Common User Access |
| ê°ì¸ê³¼ ê³µì | | | | (CUA) defines conventions for GUI look |
| ìì ì¬ì´ ì´ | | | | and feel. - Common Programming |
| êµ¬ë³ ë§ë"¤ì-´ì ¸ì-¼ | | | | Interface (CPI) provides languages, |
| í-ë¤. í-ê³ì-ìëS", | | | | tools, and APIs that give |
| ë (TM) ì¼í- 기ê³ëS" | | | | |
| ê°ì¸ í"ëíS¸í (TM) | | | | |
| ë° ìë² í"ë«í¼ | | | | applications greater portability and |
| ë' ë¤ì¼ì§ë | | | | more consistent user interfaces across |
| ëª¨ë¥¸ë¤ | | | | multiple platforms. - Common |
| (ì를ë"¤ë©´ ë (TM) | | | | Communication Support (CCS) supports |
| ë£ ì- ë (TM) ë£ | | | | existing communications standards, such |
| ë¤íS¸ìí¬ì-ì; | | | | as LU 6.2. - Common Applications, |
| 3.2를 ë³´ììì¤). | | | | written by IBM, will serve as |
| ì-¸ì ë, ìë² ì-í- | | | | demonstrations of SAA concepts and make |
| ì ê³µì ììì | | | | it easy for users to migrate between |
| ê°ì©ì± ê·¸ë¦¬ê³ ì | | | | systems. |