HP

HP Systems Insight Manager 5.1 »ç¿ë ¼³¸í¼­

Çѱ¹¾î
  °ü¸® È®Àå µµ±¸  |  »ç¿ëÀÚ Á¤ÀÇ µµ±¸  |  »ç¿ëÀÚ Á¤ÀÇ µµ±¸ ÂüÁ¶   

»ç¿ëÀÚ Á¤ÀÇ µµ±¸ ÂüÁ¶

¸ñÂ÷
»öÀÎ
¾Ë¸²
¼Ò°³
Á¦Ç° °³¿ä
½ÃÀÛ
°Ë»ö ¹× ½Äº°
»ç¿ëÀÚ ¹× ±ÇÇÑ
µð·ºÅ丮 ¼­ºñ½º
³×Æ®¿öÅ· ¹× º¸¾È
½Ã½ºÅÛ, Ŭ·¯½ºÅÍ ¹× À̺¥Æ® ¸ð´ÏÅ͸µ
ÀúÀå¼Ò ÅëÇÕ
ÀÛ¾÷À» »ç¿ëÇÏ¿© °ü¸®
°ü¸® È®Àå µµ±¸
Ŭ·¯½ºÅÍ ¸ð´ÏÅÍ
¸í·ÉÁÙ µµ±¸
¿¡ÀÌÀüÆ® ±¸¼º ¶Ç´Â º¹±¸ °³¿ä
»ç¿ëÀÚ Á¤ÀÇ µµ±¸
»õ ¿ø°Ý µµ±¸ ¸¸µé±â
»õ CMS µµ±¸ ¸¸µé±â
»õ À¥ ÆäÀÌÁö µµ±¸ ¸¸µé±â
»ç¿ëÀÚ Á¤ÀÇ µµ±¸ °ü¸®
¿ø°Ý µµ±¸ ÆíÁý
CMS µµ±¸ ÆíÁý
À¥ ÆäÀÌÁö µµ±¸ ÆíÁý
»ç¿ëÀÚ Á¤ÀÇ µµ±¸ »èÁ¦
µµ±¸ Á¤ÀÇ ÆÄÀÏ º¸±â
»ç¿ëÀÚ Á¤ÀÇ µµ±¸ Á¦°Å ¹× º¹¿ø
»ç¿ëÀÚ Á¤ÀÇ µµ±¸ÀÇ È¯°æ º¯¼ö
»ç¿ëÀÚ Á¤ÀÇ µµ±¸¿¡ ¸Å°³ º¯¼ö ¹®ÀÚ¿­À» »ç¿ëÇÏ´Â ¿¹
»ç¿ëÀÚ Á¤ÀÇ µµ±¸ ÂüÁ¶
DMI ¾×¼¼½º ±¸¼º
SNMP ¾×¼¼½º ±¸¼º
ÀåÄ¡ Ping
µð½ºÅ© ÀÓ°è°ª
License Manager
°ü¸® ÇÁ·Î¼¼¼­ µµ±¸
MIB °ü¸®
OpenSSH ¼³Ä¡
PMP µµ±¸
Replicate Agent ¼³Á¤
RPM Package Manager
Server Migration Pack
System Management Homepage
½Ã½ºÅÛ ÆäÀÌÁö
Version Control
Virtual Machine Management Pack
WBEM ±â¹Ý µµ±¸
»ç¿ë °¡´ÉÇÑ MSA µµ±¸
ÆÄÆ®³Ê ÀÀ¿ë ÇÁ·Î±×·¥
º¸°í
½Ã½ºÅÛ ¹× À̺¥Æ® °ü¸®
¹®Á¦ ÇØ°á
ÂüÁ¶ Á¤º¸
Àμâ¿ë ÆäÀÌÁö
¿ë¾î
µµ¿ò¸» »ç¿ë¹ý
 µµ±¸ À¯Çü
 ¸Å°³ º¯¼öÈ­µÈ ¹®ÀÚ¿­
 µµ±¸ ÇÊÅ͸µ
 ¹öÀü ¹øÈ£
 ´Ù¸¥ ¿ä±¸ »çÇ×
 ¹®¼­ À¯Çü Á¤ÀÇ

µµ±¸ À¯Çü

¼¼ °¡Áö ±âº» À¯ÇüÀÇ HP SIM(HP Systems Insight Manager) µµ±¸·Î SSA(´ÜÀÏ ½Ã½ºÅÛ ÀνÄ) µµ±¸, MSA(´ÙÁß ½Ã½ºÅÛ ÀνÄ) µµ±¸ ¹× WLA(À¥ ½ÃÀÛ ÀνÄ) µµ±¸°¡ ÀÖ½À´Ï´Ù.

SSA µµ±¸´Â ´ë»ó ½Ã½ºÅÛ¿¡¼­ ½ÇÇàµÇ°í ´ë»ó ½Ã½ºÅÛ È¯°æ¸¸ ÀνÄÇÕ´Ï´Ù. µû¶ó¼­ SSA µµ±¸¸¦ ½ÇÇàÇÒ ¶§ DTF(ºÐ»ê ÀÛ¾÷ ±â´É)´Â µµ±¸¸¦ ½ÇÇàÇÒ °¢ HP SIM ¿¡ÀÌÀüÆ®¿¡ µµ±¸ Á¤º¸¸¦ º¸³À´Ï´Ù. SSA µµ±¸ÀÇ ¿¹·Î´Â ls, cat ¶Ç´Â cp °°Àº ÀϹÝÀûÀÎ UNIX ¸í·ÉÀ» ·¡ÇÎÇÏ´Â µµ±¸¸¦ µé ¼ö ÀÖ½À´Ï´Ù.

MSA µµ±¸´Â Áß¾Ó ½Ã½ºÅÛ, ¶§¶§·Î CMS(Áß¾Ó °ü¸® ¼­¹ö)¿¡¼­ ½ÇÇàµÇ¸ç ´ë»ó ½Ã½ºÅÛ ¸ñ·ÏÀ» ó¸®ÇÒ ¼ö ÀÖ½À´Ï´Ù. MSA µµ±¸ÀÇ ¿¹·Î´Â HP-UX ½Ã½ºÅÛ¿¡¼­ Ignite-UX ±â´ÉÀ» ·¡ÇÎÇÏ´Â µµ±¸¸¦ µé ¼ö ÀÖ½À´Ï´Ù.

WLA µµ±¸´Â ÀϹÝÀûÀ¸·Î ºê¶ó¿ìÀú¿¡¼­ ½ÇÇàµÇ¸ç URL·Î ÁöÁ¤µË´Ï´Ù.

¸Å°³ º¯¼öÈ­µÈ ¹®ÀÚ¿­

µµ±¸ °³¹ßÀÚ´Â µµ±¸¸¦ ¿Ã¹Ù¸£°Ô ¸¸µé±â À§ÇØ URL°ú ¸í·ÉÁÙÀÌ ±¸¼ºµÇ´Â ¹æ¹ýÀ» ÀÌÇØÇØ¾ß ÇÕ´Ï´Ù. µµ±¸ °³¹ßÀÚ´Â ¸Å°³ º¯¼öÈ­µÈ ¹®ÀÚ¿­À» »ç¿ëÇÏ¿© TDEF(µµ±¸ Á¤ÀÇ ÆÄÀÏ)¸¦ ¸¸µé ¶§ »ç¿ëÇÒ ¼ö ÀÖ´Â ¿É¼ÇÀ» Å©°Ô Çâ»ó½Ãų ¼ö ÀÖ½À´Ï´Ù.

¸Å°³ º¯¼öÈ­µÈ ¹®ÀÚ¿­Àº ±³Ã¼ Çʵ带 Æ÷ÇÔÇÏ´Â ¹®ÀÚ¿­·Î, Ç¥ÁØ C ¶óÀ̺귯¸®ÀÇ printf() ÇÔ¼ö¿¡ »ç¿ëµÇ´Â Çü½Ä ¹®ÀÚ¿­°ú ºñ½ÁÇÕ´Ï´Ù. ÀÌ·¯ÇÑ Çʵå´Â ·±Å¸ÀÓ ½Ã µµ±¸ ¸Å°³ º¯¼ö ¼Ó¼º¿¡ Á¤ÀÇµÈ ´ë·Î »ç¿ëÀÚ°¡ ÀÔ·ÂÇÑ °ª, ÀÛ¾÷ ÄÁÆ®·Ñ·¯¿¡¼­ Á¦°øÇÑ ¸î °¡Áö Ç¥ÁØ ÀÛ¾÷ µî·Ï Á¤º¸, ¼±ÅÃÇÑ ´ë»ó ½Ã½ºÅÛÀ̳ª ½Ã½ºÅÛ ±×·ì°ú °ü·ÃµÈ °ª, ¶Ç´Â Àü¿ª µµ±¸ µî·Ï Á¤º¸ ÆÄÀÏ¿¡¼­ °Ë»öÇÑ µî·Ï Á¤º¸ °ªÀ¸·Î ±³Ã¼µÉ ¼ö ÀÖ½À´Ï´Ù. ÀÌ·¸°Ô ÇÏ¿© URLÀ̳ª ¸í·ÉÁÙÀ» ¸Å¿ì ±¸Ã¼ÀûÀ¸·Î »ý¼ºÇÒ ¼ö ÀÖ½À´Ï´Ù.

¸Å°³ º¯¼öÈ­µÈ ¹®ÀÚ¿­ ´ëü Å×À̺í

´ÙÀ½ ¸Å°³ º¯¼ö´Â Àü¿ª ¼Ó¼º °ªÀ» ´ëüÇÕ´Ï´Ù.

¸Å°³ º¯¼ö¼³¸í
%t ½ÇÇàµÉ ÀÛ¾÷ÀÇ ÀÛ¾÷ ID
%uÀÌ µµ±¸¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚÀÇ À̸§
%eÀÌ µµ±¸¸¦ ½ÇÇàÇÒ ¶§ »ç¿ëÇÒ »ç¿ëÀÚÀÇ À̸§
%sµµ±¸¸¦ ½ÇÇàÇÏ´Â ÄÚ¾î CMSÀÇ °ü¸® ¼­¹ö È£½ºÆ® À̸§
%#(¿©±â¼­ #Àº ¾çÀÇ Á¤¼ö) ¸ñ·Ï »öÀÎ À§Ä¡·Î Á¦°øµÈ ¼ýÀÚ(#)°¡ ÂüÁ¶ÇÏ´Â ¸Å°³ º¯¼ö¸¦ »ç¿ëÀÚ°¡ ÀÔ·ÂÇÑ °ªÀ¸·Î ´ëü(1 ±âÁØ... %1, %2, %3 µî)
%ySOAP ´ÜÀÏ »çÀο À¥ ÀÀ¿ë ÇÁ·Î±×·¥¿¡ »ç¿ëÇϱâ À§ÇÑ SOAP(Simple Object Access Protocol) ·Î±×¿Â ÅäÅ«

´ÙÀ½ ¸Å°³ º¯¼ö´Â ÇöÀç ¼±ÅÃµÈ ´ë»óÀ» ´ëüÇÕ´Ï´Ù.

¸Å°³ º¯¼ö¼³¸í
%f´ë»ó ½Ã½ºÅÛ(¶Ç´Â ¹®ÀÚ¿­¿¡ %x Åä±ÛÀÌ ÀÖ´Â °æ¿ì ½Ã½ºÅÛ ±×·ì)ÀÇ ½Ã½ºÅÛ À̸§ ¶Ç´Â IP ÁÖ¼Ò
%n³×Æ®¿öÅ© À̸§(È£½ºÆ® À̸§, IP ÁÖ¼Ò ¶Ç´Â °°Àº ¼ø¼­·Î µÈ ½Ã½ºÅÛ À̸§)
%a³×Æ®¿öÅ© ÁÖ¼Ò(IP ÁÖ¼Ò)
%l½Ã½ºÅÛ ¸µÅ© ±¸¼º ¼³Á¤¿¡¼­ ÁöÁ¤ÇÑ Çü½ÄÀÇ ¸µÅ© À̸§(À̸§, IP ÁÖ¼Ò ¶Ç´Â Àüü DNS À̸§)
%pÀÌ ´ë»ó¿¡ ´ëÇÑ WBEM ÇÁ·Ï½ÃÀÇ IP ÁÖ¼Ò(<ip address>:<port#></port#></ip> Çü½Ä)
%g´ë»ó ½Ã½ºÅÛ(¶Ç´Â ¹®ÀÚ¿­¿¡ %x Åä±ÛÀÌ ÀÖ´Â °æ¿ì ½Ã½ºÅÛ ±×·ì)ÀÇ µ¥ÀÌÅͺ£À̽º GUID
%b´ë»ó ½Ã½ºÅÛÀÇ ½Ã½ºÅÛ À¯Çü
%c´ë»ó ½Ã½ºÅÛÀÇ ½Ã½ºÅÛ ÇÏÀ§ À¯Çü
%r% (rt[.attribute]%)"rt" ¸Å°³ º¯¼ö¿¡ ÁöÁ¤µÈ °ü°è À¯ÇüÀ» °¡Áø °ü·Ã ½Ã½ºÅÛÀ» ´ëü. [.attribute]°¡ ÁöÁ¤µÈ °æ¿ì ¸í¸íµÈ ½Ã½ºÅÛ ¼Ó¼º Áß Çϳª°¡ °ü·Ã ½Ã½ºÅÛ¿¡ ´ëÇØ ¹ÝȯµË´Ï´Ù. ¶ÇÇÑ ³×Æ®¿öÅ© À̸§(.a) °°Àº ÀÏ¹Ý ¼Ó¼ºµµ ÀÛµ¿ÇÕ´Ï´Ù. ¿¹¸¦ µé¾î ¼­¹öÀÇ °ü¸® ÇÁ·Î¼¼¼­ IP ÁÖ¼Ò¸¦ °¡Á®¿À·Á¸é %r{MgmtProcToServer.a%}¸¦ »ç¿ëÇϰí, ¿¬¶ôó¸¦ °¡Á®¿À·Á¸é %r{MgmtProcToServer.Contact%}¸¦ »ç¿ëÇÕ´Ï´Ù. °ü·Ã ½Ã½ºÅÛ ¼Ó¼ºÀÌ »ý·«µÈ °æ¿ì °¢ ½Ã½ºÅÛ¿¡ ´ëÇØ ³×Æ®¿öÅ© À̸§°ú IP ÁÖ¼Ò°¡ ¹ÝȯµË´Ï´Ù. ³×Æ®¿öÅ© À̸§°ú IP ÁÖ¼Ò´Â "³×Æ®¿öÅ© À̸§|ip ÁÖ¼Ò" Çü½ÄÀ¸·Î ¹ÝȯµË´Ï´Ù. µÑ ÀÌ»óÀÇ ½Ã½ºÅÛÀÌ ¹ÝȯµÇ´Â °æ¿ì ½°Ç¥·Î ºÐ¸®µË´Ï´Ù. °ü°è À¯Çü "MgmtProcToServer"´Â ¸ðµç °ü¸® ÇÁ·Î¼¼¼­ °ü°è À¯Çü¿¡ ´ëÇÑ °ü·Ã ½Ã½ºÅÛ Á¤º¸¸¦ ¹ÝȯÇÏ´Â µ¥ »ç¿ëÇÒ ¼ö ÀÖ½À´Ï´Ù.
%(attribute]%)´ë»ó ½Ã½ºÅÛÀÇ ¸í¸íµÈ ¼Ó¼º °ª

´ÙÀ½ ¸Å°³ º¯¼ö´Â ¼±ÅÃµÈ ¿©·¯ ´ë»ó ½Ã½ºÅÛÀ» Áö¿øÇϱâ À§ÇÑ ¹Ýº¹À» Á¦°øÇÕ´Ï´Ù.

¸Å°³ º¯¼ö¼³¸í
%( ... %)¹Ýº¹µÇ´Â ÆÐÅÏ(ÇöÀç ¼±Åà Ç׸ñÀÌ ÀÖ´Â °æ¿ì¿¡¸¸ ¹Ýº¹) ÇöÀç ´ë»ó ¼±ÅÃÀÌ ¾øÀ¸¸é È®Àå ½Ã ±¸ºÐ ±âÈ£ »çÀÌÀÇ ÅØ½ºÆ®°¡ Á¦°ÅµË´Ï´Ù. ÀÌ ±â´ÉÀ¸·Î ÅØ½ºÆ®¸¦ ¿É¼ÇÀ¸·Î ÁöÁ¤ÇÏ°í ´ë»ó ¼±Åà ¸ñ·Ï¿¡ Á¾¼ÓµÇµµ·Ï ÇÒ ¼ö ÀÖ½À´Ï´Ù.
%i¼±Åà »öÀÎ(1 ±âÁØ)
%z¾Æ¹« °Íµµ ´ëüÇÏÁö ¾Ê°í ¼±Åà »öÀÎÀ» ´ÙÀ½ Á¤¼ö·Î Áõ°¡½Ã۰í ÂüÁ¶µÈ ´ë»ó ½Ã½ºÅÛÀ» ¼±ÅÃµÈ ´ë»ó ¸ñ·ÏÀÇ ´ÙÀ½ ´ë»óÀ¸·Î Áõ°¡½Ãŵ´Ï´Ù.
%⇚< ... >l¾ÏȣȭµÈ ÅØ½ºÆ®(´Ù¸¥ ¸ðµç ¸Å°³ º¯¼ö¸¦ ´ëüÇÑ ÈÄ ¾Ïȣȭ)
%%´ëü ÈÄ ¸í·É/URL¿¡ %¸¦ À¯ÁöÇÒ ¼ö ÀÖ½À´Ï´Ù.

µµ±¸ ÇÊÅ͸µ

µµ±¸ ÇÊÅ͸µÀº ¼±ÅÃÇÑ ½Ã½ºÅÛ¿¡¼­ µµ±¸ ÀÛ¼ºÀÚ°¡ µµ±¸¸¦ ½ÇÇàÇØ¾ß ÇÏ´ÂÁö ¿©ºÎ¸¦ Á¦¾îÇÒ ¼ö ÀÖ°Ô ÇÏ´Â ±â´ÉÀÔ´Ï´Ù. ´ëºÎºÐÀÇ µµ±¸´Â ÀϺΠÇ÷§Æû¿¡ Á¦°øµÇ´Â ¸í·É¿¡ ´ëÇØ¼­¸¸ ¼º°øÀûÀ¸·Î ½ÇÇàµÇ°í ´Ù¸¥ ¸í·É¿¡ ´ëÇØ¼­´Â ½ÇÇàµÇÁö ¾Ê´Â´Ù´Â Á¡¿¡¼­ Ç÷§Æû Á¾¼ÓÀûÀÔ´Ï´Ù. ¿¹¸¦ µé¾î bdf µµ±¸´Â HP-UX Ç÷§Æû¿¡¼­ Á¦°øÇÏ´Â bdf ¸í·É¿¡ Á¾¼ÓµÇ¸ç Linux Ç÷§Æû¿¡¼­´Â ÇØ´ç À̸§À¸·Î »ç¿ëÇÒ ¼ö ¾ø½À´Ï´Ù. µµ±¸´Â ÇÊÅÍ ¿ä±¸ »çÇ×À» Åë°úÇÑ Çϳª ÀÌ»óÀÇ °Ë»öµÈ ½Ã½ºÅÛÀÌ ÀÖ´Â °æ¿ì¿¡¸¸ µµ±¸ ¸Þ´º¿¡ Ç¥½ÃµË´Ï´Ù. °Ë»öµÈ ½Ã½ºÅÛÀº ÇÊÅÍ ¿ä±¸ »çÇ×À» Åë°úÇØ¾ß ÇÏ°í ¸ðµç ÇÊÅÍ ¿ä±¸ »çÇ×À» Åë°úÇÑ ÈÄ¿¡¸¸ ½ÇÇàµË´Ï´Ù. À̸¦ À§ÇØ µµ±¸¿¡¼­´Â µµ±¸°¡ ½ÇÇàµÉ ¼ö ÀÖ´Â ¸ðµç ½Ã½ºÅÛÀÌ °¡Á®¾ß ÇÒ ½Ã½ºÅÛ ¼Ó¼ºÀ» ½Ã½ºÅÛ ÇÊÅÍ ½Ä¿¡ ÁöÁ¤ÇÕ´Ï´Ù.

¼±ÅÃµÈ ½Ã½ºÅÛ¿¡ ´ëÇØ µµ±¸¸¦ ½ÃÀÛÇÒ ¼ö ¾ø´Â °æ¿ì¿¡´Â µµ±¸¸¦ ½ÃÀÛÇÒ ¼ö ¾ø´Â ÀÌÀ¯¿¡ ´ëÇÑ Á¤º¸¿Í ÇÔ²² ¿À·ù ¸Þ½ÃÁö°¡ Ç¥½ÃµË´Ï´Ù.

µµ±¸¸¦ ½ÇÇàÇÏ´Â µ¥ ÇÊ¿äÇÑ ½Ã½ºÅÛ ¼Ó¼ºÀº ´ÙÀ½°ú °°Àº Çü½ÄÀÇ ½Ã½ºÅÛ ÇÊÅÍ ½Ä¿¡ ÀÇÇØ ÁöÁ¤µË´Ï´Ù.

				
<node-filter name="attribute-name" operator="eq" 
   value="attribute-value" />
      or
<node-filter name="attribute-name" operator="ge" 
   value="attribute-value" />
      or
<node-filter name="attribute-name" operator="lt" 
   value="attribute-value" />
      or
<node-filter name="attribute-name" operator="ct" 
   value="attribute-value" />
      or
<node-filter name="attribute-name" operator="neq" 
   value="attribute-value" />
      or
<node-filter name="attribute-name" operator="nct" 
  value="attribute-value" />
			

eq ¿¬»êÀÚ´Â µµ±¸¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Â ½Ã½ºÅÛÀÌ ÁöÁ¤µÈ ¼Ó¼º °ª°ú Á¤È®ÇÏ°Ô °°Àº °ªÀ» °¡Á®¾ß ÇÑ´Ù´Â °ÍÀ» ÁöÁ¤Çϸç, ½Ã½ºÅÛ ÇÊÅÍ ½Ä¿¡ Çã¿ëµÇ´Â ¸ðµç ¼Ó¼º À̸§¿¡ Àû¿ëµË´Ï´Ù. ge ¿¬»êÀÚ´Â µµ±¸¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Â ½Ã½ºÅÛÀÌ ÁöÁ¤µÈ ¼Ó¼º °ªÀ» Çϳª ÀÌ»ó °¡Á®¾ß ÇÑ´Ù´Â °ÍÀ» ÁöÁ¤ÇÕ´Ï´Ù. lt ¹× ge ¿¬»êÀÚ´Â °³Á¤ ¼Ó¼º¿¡¸¸ »ç¿ëÇÒ ¼ö ÀÖÀ¸¸ç, ƯÈ÷ OS À¯Çü ÇÊÅÍÀÇ OS °³Á¤ ¼Ó¼º ¹× ÇÁ·ÎÅäÄÝ À¯Çü ÇÊÅÍÀÇ ¸ðµç ¼Ó¼º°ú ÇÔ²² »ç¿ëÇÒ ¼ö ÀÖ½À´Ï´Ù. ÀÌ·¯ÇÑ ¼Ó¼º °ªÀº ¼ýÀÚÀ̰ųª ¹®ÀÚ¿­ÀÏ ¼ö ÀÖ½À´Ï´Ù. ct ¿¬»êÀÚ´Â µµ±¸¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Â ½Ã½ºÅÛÀÌ ÁöÁ¤µÈ °ªÀ» Æ÷ÇÔÇÏ´Â ¼Ó¼ºÀ» °¡Á®¾ß ÇÑ´Ù´Â °ÍÀ» ÁöÁ¤ÇÕ´Ï´Ù. neq ¿¬»êÀÚ´Â µµ±¸¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Â ½Ã½ºÅÛÀÌ ÁöÁ¤µÈ ¼Ó¼º °ªÀ» °¡Áö¸é ¾È µÈ´Ù´Â °ÍÀ» ³ªÅ¸³»¸ç, ½Ã½ºÅÛ ÇÊÅÍ ½Ä¿¡ Çã¿ëµÈ ¸ðµç ¼Ó¼º À̸§¿¡ Àû¿ëµË´Ï´Ù. nct ¿¬»êÀÚ´Â µµ±¸¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Â ½Ã½ºÅÛÀÌ ÁöÁ¤µÈ °ªÀ» Æ÷ÇÔÇÏÁö ¾Ê´Â ¼Ó¼ºÀ» °¡Á®¾ß ÇÑ´Ù´Â °ÍÀ» ÁöÁ¤ÇÕ´Ï´Ù. ½Ã½ºÅÛÀÇ °æ¿ì ÇÊÅÍ ½Ä¿¡¼­ ÁöÁ¤ÇÒ ¼ö ÀÖ´Â ¼ýÀÚ °ª ¼Ó¼º¿¡´Â ¹öÀü ¹øÈ£¸¦ °ªÀ¸·Î ÇÏ´Â OS °³Á¤ ¹× ÇÁ·ÎÅäÄÝ Áö¿ø ¼Ó¼ºÀÌ ÀÖ½À´Ï´Ù. ¹öÀü ¹øÈ£¿¡ Çã¿ëµÇ´Â °ª°ú ¹öÀü ¹øÈ£¸¦ ºñ±³ÇÏ´Â ¹æ¹ý¿¡ ´ëÇØ¼­´Â ´ÙÀ½ ÀýÀÇ ¹öÀü ¹øÈ£¿¡¼­ ¼³¸íÇÕ´Ï´Ù. ¼Ó¼º À̸§Àº ´ÙÀ½ ÀýÀÇ Å×ÀÌºí¿¡ ³ª¿­µÈ °ª Áß ÇϳªÀ̰ųª ½Ã½ºÅÛÀÇ ÇÁ·ÎÅäÄÝ Áö¿ø ¼Ó¼º¿¡¼­ °¡Á®¿Â ÇÁ·ÎÅäÄÝ À̸§ÀÔ´Ï´Ù. ¼Ó¼º °ªÀº ¼Ó¼º À̸§¿¡ »ç¿ëÇÒ ¼ö ÀÖ´Â ½Ã½ºÅÛ ¼Ó¼º °ª Áß ÇϳªÀÔ´Ï´Ù.

¼Ó¼º °ªÀº DMTF(Distributed Management Task Force) CIM(Common Information Model)À» ±â¹ÝÀ¸·Î ÇÕ´Ï´Ù. ÀÌ·¯ÇÑ °ªÀº ÀϹÝÀûÀ¸·Î ½Ã½ºÅÛ ½Äº° ÇÁ·Î¼¼½º Áß Á¤ÀǵǸç, ÀÌ °úÁ¤¿¡¼­´Â WBEM ¹× SNMP¸¦ »ç¿ëÇÏ¿© ½Ã½ºÅÛ ¼Ó¼ºÀ» È®ÀÎÇÕ´Ï´Ù. ÀÌ ¸±¸®Áî¿¡¼­ À¯È¿ÇÑ OS À̸§ °ªÀº HP-UX ¹× LinuxÀÔ´Ï´Ù. HP-UXÀÇ OS À̸§ °ª¿¡ ´ëÇØ OS °³Á¤ ¼Ó¼º °ªÀº ¸Ç ¾ÕÀÇ ¹®ÀÚ Çʵ带 Á¦°ÅÇÕ´Ï´Ù(¿¹: B.11.11Àº 11.11·Î ÀúÀåµÊ).

½Ã½ºÅÛ ÇÊÅÍ ½ÄÀº Æ÷ÇÔ ÇÊÅÍ ½ÄÀÇ ÀϺηΠ»ç¿ëµË´Ï´Ù. Æ÷ÇÔ ÇÊÅÍ ½Ä¿¡´Â ¼¼ °¡Áö À¯ÇüÀÌ ÀÖÀ¸¸ç, °¢ À¯Çü¿¡ µû¶ó ÇÊÅ͸µÇÒ ¼Ó¼º À̸§ ¹üÁÖ°¡ ´Ù¸¨´Ï´Ù.

¹üÁÖÇÊÅÍ À¯ÇüÇã¿ëµÇ´Â ¼Ó¼º À̸§
¿î¿µ üÁ¦osOS À̸§, OS °ø±Þ¾÷ü, OS °³Á¤
Çϵå¿þ¾îÇϵå¿þ¾îÀåÄ¡ À¯Çü, ÀåÄ¡ ÇÏÀ§ À¯Çü, ¸ðµ¨
ÇÁ·ÎÅäÄÝ Áö¿øÇÁ·ÎÅäÄÝHTTP¸¦ Á¦¿ÜÇÑ ¸ðµç ÇÁ·ÎÅäÄÝ À̸§
±âŸ±âŸ¹Ì¸® Á¤ÀÇµÈ ½Ã½ºÅÛ ¼Ó¼ºÀ̰ųª »ç¿ëÀÚ Á¤ÀÇ ½Ã½ºÅÛ ¼Ó¼ºÀÏ ¼ö ÀÖÀ½

Æ÷ÇÔ ÇÊÅÍ¿¡´Â Çã¿ëµÇ´Â ¼Ó¼º À̸§À» »ç¿ëÇÏ´Â Çϳª ÀÌ»óÀÇ ½Ã½ºÅÛ ÇÊÅÍ ½ÄÀÌ µé¾î ÀÖ½À´Ï´Ù. ¿¹¸¦ µé¾î os ÇÊÅÍ´Â ´ÙÀ½°ú °°ÀÌ ±¸¼ºµÉ ¼ö ÀÖ½À´Ï´Ù.

				
<include-filter type="os">
	      <node-filter name="OSName"     
		    operator="eq" value="LINUX"  />
	      <node-filter name="OSVendor"   
            operator="eq" value="RedHat" />
	      <node-filter name="OSRevision" 
            operator="ge" value="7.2"	  />
</include-filter>
			

Æ÷ÇÔ ÇÊÅÍ¿¡ Çã¿ëµÇ´Â ¸ðµç ¼Ó¼ºÀ» Æ÷ÇÔÇÒ ÇÊ¿ä´Â ¾ø½À´Ï´Ù. ¼Ó¼ºÀ» µÑ ÀÌ»ó Æ÷ÇÔÇϸé Á¶°Ç °£¿¡ ³í¸® AND°¡ ¼öÇàµË´Ï´Ù. ¼Ó¼ºÀº Æ÷ÇÔ ÇÊÅÍ¿¡ µÎ ¹ø ÀÌ»ó ³ªÅ¸³¯ ¼ö ¾ø½À´Ï´Ù. ¹öÀü ¹øÈ£ °ªÀ» °®´Â ¼Ó¼ºÀÇ ¿¬»êÀÚ°¡ Çϳª´Â ltÀÌ°í ´Ù¸¥ Çϳª´Â geÀÎ °æ¿ì¿¡´Â ¿¹¿ÜÀûÀ¸·Î µÎ ¹ø ³ªÅ¸³¯ ¼ö ÀÖ½À´Ï´Ù. ¿¹¸¦ µé¸é ´ÙÀ½°ú °°½À´Ï´Ù.

				
<include-filter type="protocol">
	      <node-filter name="WBEM" 
            operator="lt" value="2.6" />
          <node-filter name="WBEM" 
            operator="ge" value="2.4" />
</include-filter>
			

ÀÌ ÇÊÅÍ ½ÄÀº 2.4 ÀÌ»ó, 2.6 ¹Ì¸¸ÀÇ WBEM ÇÁ·ÎÅäÄÝ ¹öÀüÀ» Áö¿øÇÏ´Â ¸ðµç ½Ã½ºÅÛ ¸ðÀ½¿¡ ´ëÇØ µµ±¸¸¦ Ç¥½ÃÇØ¾ß ÇÑ´Ù´Â °ÍÀ» ÁöÁ¤ÇÕ´Ï´Ù.

µµ±¸¿¡ ¼­·Î ´Ù¸¥ À¯ÇüÀÇ Æ÷ÇÔ ÇÊÅͰ¡ µÑ ÀÌ»ó µé¾î ÀÖÀ¸¸é ÇÊÅÍ Á¶°Ç °£¿¡ ³í¸® AND°¡ ¼öÇàµË´Ï´Ù. ¿î¿µ üÁ¦ ¹× Çϵå¿þ¾î Á¾¼Ó¼ºÀ» ¸ðµÎ °¡Áö´Â µµ±¸¿¡¼­´Â ´ÙÀ½°ú °°Àº ÇÊÅ͸¦ »ç¿ëÇÒ ¼ö ÀÖ½À´Ï´Ù.

				
<include-filter type="os">
	      <node-filter name="OSName"     
	        operator="eq" value="LINUX"  />
 </include-filter>
 <include-filter type="hardware">
	      <node-filter name="DeviceSubType" 
	        operator="eq" value="HPVectra" />
 </include-filter>
			

µµ±¸¿¡ °°Àº À¯ÇüÀÇ Æ÷ÇÔ ÇÊÅͰ¡ µÑ ÀÌ»ó µé¾î ÀÖÀ¸¸é ÇÊÅÍ Á¶°Ç °£¿¡ ³í¸® OR°¡ ¼öÇàµË´Ï´Ù. ¼­·Î ´Ù¸¥ µÎ °³ ¿î¿µ üÁ¦¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖ´Â µµ±¸¿¡¼­´Â ´ÙÀ½°ú °°Àº ÇÊÅ͸¦ ÁöÁ¤ÇÒ ¼ö ÀÖ½À´Ï´Ù.

				
<include-filter type="os">
	      <node-filter name="OSName"     
	        operator="eq" value="LINUX"  />
</include-filter>
<include-filter type="os">
	      <node-filter name="OSName"     
	        operator="eq" value="HPUX"	 />
</include-filter>
			

ÀÌ µµ±¸´Â Linux ¶Ç´Â HP-UX¸¦ »ç¿ëÇÏ´Â ¸ðµç ½Ã½ºÅÛ ¸ðÀ½¿¡¼­ ½ÃÀÛÇÒ ¼ö ÀÖ½À´Ï´Ù.

µµ±¸ ÇÊÅ͸µÀº ÇÊÅ͸µµÇ´Â ¼Ó¼º¿¡ µû¶ó ´Ù¸£°í ¼±ÅÃµÈ ½Ã½ºÅÛ¿¡ °ªÀÌ Á¤ÀǵǾî ÀÖ½À´Ï´Ù. os ÇÊÅÍ À¯ÇüÀÇ °æ¿ì ÇÊÅ͸µµÇ´Â ¼Ó¼ºÀÌ ½Ã½ºÅÛ¿¡ Á¤ÀǵǾî ÀÖÁö ¾ÊÀ¸¸é ½Ã½ºÅÛÀÌ ÇÊÅÍ¿¡¼­ ÇÊ¿ä·Î ÇÏ´Â °ªÀ» °®´Â °ÍÀ¸·Î °¡Á¤ÇÕ´Ï´Ù. µû¶ó¼­ µµ±¸ ÇÊÅÍ¿¡¼­ ÁöÁ¤ÇÑ os ¼Ó¼ºÀÌ ¾ø´Â ½Ã½ºÅÛÀº µµ±¸¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Â °ÍÀ¸·Î °¡Á¤ÇÕ´Ï´Ù. Çϵå¿þ¾î ÇÊÅÍ À¯ÇüÀº ¸ðµ¨ ¼Ó¼ºÀÇ °æ¿ì¿¡´Â À§ÀÇ ¼³¸íÀÌ ¿Ã¹Ù¸£Áö¸¸ ÀåÄ¡ À¯Çü ¹× ÀåÄ¡ ÇÏÀ§ À¯Çü ¼Ó¼ºÀÇ °æ¿ì¿¡´Â ¼±ÅÃÇÑ ½Ã½ºÅÛÀÇ ¾Ë·ÁÁø °ª¿¡ ´ëÇØ¼­¸¸ µµ±¸ ÇÊÅͰ¡ Àû¿ëµË´Ï´Ù. ÇÁ·ÎÅäÄÝ ÇÊÅÍ À¯ÇüÀÇ °æ¿ì ¿¬»êÀÚ¸¦ Àû¿ëÇϱâ Àü¿¡ ½Ã½ºÅÛ¿¡ ÇÁ·ÎÅäÄÝÀÌ ÀÖ¾î¾ß ÇÕ´Ï´Ù. Áï, neq ¹× nct ¿¬»êÀÚµµ ½Ã½ºÅÛÀÇ ÇØ´ç ÇÁ·ÎÅäÄÝ¿¡ Á¾¼ÓµË´Ï´Ù. ±âŸ ÇÊÅ͵µ ÇÁ·ÎÅäÄÝ ÇÊÅÍó·³ ÀÛµ¿ÇÏ¿© ¿¬»êÀÚ¸¦ Àû¿ëÇϱâ Àü¿¡ ÇÊÅ͸µµÇ´Â ¼Ó¼ºÀÌ ½Ã½ºÅÛ¿¡ ÀÖ¾î¾ß ÇÕ´Ï´Ù. µµ±¸¿¡¼­ ±âŸ ¹×/¶Ç´Â ÇÁ·ÎÅäÄÝ ÇÊÅ͸¦ »ç¿ëÇÏ´Â °æ¿ì GUI¿¡ Ç¥½ÃµÉ µµ±¸¿¡ ´ëÇÑ ÇÊÅÍ °¡´ÉÇÑ ¼Ó¼ºÀÌ Çϳª ÀÌ»óÀÇ ½Ã½ºÅÛ¿¡ Æ÷ÇԵǾî ÀÖ¾î¾ß ÇÕ´Ï´Ù.

¹öÀü ¹øÈ£

OS °³Á¤ ¹× ÇÁ·ÎÅäÄÝ Áö¿ø ½Ã½ºÅÛ ¼Ó¼º¿¡´Â °¡´ÉÇÑ °æ¿ì ¹öÀü ¹øÈ£·Î ÇØ¼®µÇ´Â °ªÀÌ µé¾î ÀÖ½À´Ï´Ù. ¹öÀü ¹øÈ£´Â Á¡(.)À¸·Î ±¸ºÐµÈ À½ÀÌ ¾Æ´Ñ ½ÊÁø¼öÀÔ´Ï´Ù. ¹öÀü ¹øÈ£¸¦ ºñ±³ÇÒ ¶§ ´ÙÀ½ ±ÔÄ¢À» »ç¿ëÇÕ´Ï´Ù.

  • °¡Àå ¿ÞÂÊ¿¡ ÀÖ´Â ¼ýÀÚ°¡ °¡Àå Áß¿äÇÑ ¼ýÀÚÀ̹ǷΠ1.0ÀÌ 0.1º¸´Ù Å®´Ï´Ù.

  • ¼ýÀÚ ¾Õ¿¡ ÀÖ´Â 0(¿µ)Àº ¹«½ÃµÇ¹Ç·Î 003Àº 3°ú °°½À´Ï´Ù.

  • ¿¬¼ÓµÈ µÎ Á¡Àº ¼ýÀÚ 0À» ±¸ºÐÇÏ´Â °ÍÀ¸·Î ÇØ¼®µÇ¹Ç·Î 1.0.3Àº 1..3°ú °°½À´Ï´Ù.

  • Á¡À¸·Î ½ÃÀÛµÇ¸é ¾Õ¿¡ 0ÀÌ ÀÖ´Â °ÍÀ¸·Î °£ÁÖÇϹǷΠ.9´Â 0.9¿Í °°½À´Ï´Ù.

  • ¼ýÀÚ µÚ¿¡ ¿À´Â 0Àº ¹«½ÃµÇ¹Ç·Î 1.0.0Àº 1°ú °°½À´Ï´Ù.

´Ù¸¥ ¿ä±¸ »çÇ×

SSA ¸í·É µµ±¸¿¡´Â ½ÇÇà ¸í·É(execStmt) ¶Ç´Â ÆÄÀÏ º¹»ç ¸í·É(copyStmt)ÀÌ Æ÷ÇԵǾî Àְųª µÑ ´Ù Æ÷ÇԵǾî ÀÖ¾î¾ß ÇÕ´Ï´Ù. ½ÇÇà ¸í·É¸¸ ÁöÁ¤µÇ¾î ÀÖÀ¸¸é ¸í·ÉÀ» ½ÇÇàÇϱâ Àü¿¡ ¾î¶² ÆÄÀϵµ º¹»çµÇÁö ¾Ê½À´Ï´Ù. ÆÄÀÏ º¹»ç ¸í·É¸¸ ÁöÁ¤µÇ¾î ÀÖÀ¸¸é ÆÄÀÏÀ» º¹»çÇÑ ÈÄ ¾î¶² ¸í·Éµµ ½ÇÇàµÇÁö ¾Ê½À´Ï´Ù. µÑ ´Ù ÁöÁ¤µÈ °æ¿ì¿¡´Â ÆÄÀÏÀ» ¸ÕÀú º¹»çÇÑ ´ÙÀ½ ¸í·ÉÀ» ½ÇÇàÇÕ´Ï´Ù.

MSA ¸í·É µµ±¸´Â ¸í·É ¹× ÇØ´ç ¸í·ÉÀ» ½ÇÇàÇÒ ½Ã½ºÅÛÀ» ÁöÁ¤ÇØ¾ß ÇÕ´Ï´Ù.

µµ±¸ À̸§Àº 1ÀÚ ÀÌ»ó 256ÀÚ ¹Ì¸¸À̾î¾ß ÇÕ´Ï´Ù. ù ÀÚ´Â ¹®ÀÚ¿©¾ß Çϰí ù ÀÚ ÀÌÈÄ¿¡´Â ¹®ÀÚ, ¼ýÀÚ, °ø¹é ¶Ç´Â - . ( ) _ µîÀ» »ç¿ëÇÒ ¼ö ÀÖ½À´Ï´Ù.

À¥ ½ÃÀÛ ÀÎ½Ä µµ±¸´Â ±âº» URLÀ» ÁöÁ¤ÇØ¾ß ÇÕ´Ï´Ù.

ÆÄÀÏ º¹»ç ½ÖÀ» ÁöÁ¤ÇÒ ¶§ ´ÜÀÏ TDEF ³»¿¡¼­´Â °¢ ÆÄÀÏ º¹»ç ½Ö¿¡ ´ëÇÑ ´ë»ó ÆÄÀÏ °æ·Î°¡ °íÀ¯ÇØ¾ß ÇÕ´Ï´Ù. ¿©·¯ ¿øº» ÆÄÀÏ °æ·Î¿¡ ´ëÇØ µ¿ÀÏÇÑ ´ë»ó ÆÄÀÏ °æ·Î¸¦ ÁöÁ¤ÇÏ¸é ÆÄÀÏ ±¸¹® ºÐ¼® ¿À·ù°¡ ¹ß»ýÇÕ´Ï´Ù.

ÆÄÀÏÀ» º¹»çÇÏ´Â µµ±¸¸¦ ½ÇÇàÇÒ ¶§ ÆÄÀÏÀÌ ¾ø°Å³ª ÀÐÀ» ¼ö ¾ø´Â »óÅÂÀÌ¸é ¿À·ù°¡ ¹ß»ýÇÕ´Ï´Ù. µµ±¸¸¦ ¸¸µé°Å³ª ¼öÁ¤ÇÒ ¶§ ¿øº» ÆÄÀÏ °æ·Î¸¦ È®ÀÎÇÏÁö´Â ¾ÊÁö¸¸ µµ±¸¸¦ ½ÇÇàÇÒ ¶§ ÇØ´ç °æ·Î°¡ ÀÖ¾î¾ß ÇÕ´Ï´Ù.

log ¿ä¼Ò°¡ true·Î ¼³Á¤µÇ¾î ÀÖÀ¸¸é µµ±¸ ½ÇÇà ½ÃÀÇ Ç¥ÁØ Ãâ·Â ¹× Ç¥ÁØ ¿À·ù Ãâ·ÂÀÌ Áß¾Ó °ü¸® ¼­¹ö (CMS) ·Î±× ÆÄÀÏ /var/opt/mx/logs/mx.log¿¡ ±â·ÏµË´Ï´Ù. ÀÌ ¿ä¼Ò°¡ false·Î ¼³Á¤µÈ °æ¿ì¿¡´Â ½ÃÀÛ ¹× Á¾·á ½Ã°£, ÀÛ¾÷ »óÅÂ¿Í °°Àº ÀÛ¾÷ ¿ä¾à ·Î±× Á¤º¸¸¸ ±â·ÏµË´Ï´Ù.

¹®¼­ À¯Çü Á¤ÀÇ

DTD(¹®¼­ À¯Çü Á¤ÀÇ) ÆÄÀÏÀº XML ÆÄÀÏ¿¡ ´ëÇÑ Á¦¾à Á¶°ÇÀ» Á¤ÀÇÇÕ´Ï´Ù. ÀÌ·¯ÇÑ Á¦¾à Á¶°ÇÀº XML ÆÄÀÏ¿¡ ¿Ã¹Ù¸¥ ¿ä¼Ò ű×, ¼Ó¼º ¹× ¿ä¼ÒÀÇ Ä«µð³Î¸®Æ¼¸¦ Æ÷ÇÔÇÕ´Ï´Ù. µµ±¸ DTD ÆÄÀÏÀÇ À̸§Àº toollist.dtdÀÌ°í ´ÙÀ½ ´Ü¶ô¿¡ Æ÷ÇԵǾî ÀÖ½À´Ï´Ù. ¸ÇÆäÀÌÁö Çü½Ä ¶§¹®¿¡ DTD ³»¿ëÀÌ ÆÄÀÏ¿¡¼­¿Í´Â ´Ù¸£°Ô Ç¥½ÃµÉ ¼ö ÀÖ½À´Ï´Ù.

				
<?xml version="1.0" encoding="UTF-8" ?>

<!-- The tool-list element can contain zero or more of 
      ssa-command-tool elements, msa-command-tool elements,
      web-launch-tool elements, automation-tool elements or
      app-launch-tool elements.-->
      
<!ELEMENT tool-list ( ssa-command-tool |
      msa-command-tool |
      web-launch-tool  |
      automation-tool  |
      app-launch-tool )* >

<!-- The ssa-command-tool element specifies a single-system aware
      tool. The ssa-command-tool element can optionally specify a
      category element, a description element, a comment element, an
      owner element, a default-target element, an execute-as-user
      element, a job-display-handler element, a toolbox-enabled
      element, zero or more toolbox elements, zero or more
      include-filter elements, or zero or more env-variable elements.
      (NOTE: The role-enabled and role elements are deprecated
      elements and should not be used with this product. These
      are provided for backward compatibility with previous
      products. The toolbox-enabled element and the toolbox
      element should be used in their stead.)
      If more than one of these elements are specified, the element
      must appear in the order as listed in this definition. The
      ssa-command-tool element must contain an ssa-block element. The
      ssa-block element must appear after the previously described
      optional elements, if any of the optional elements are
      specified. Following the ssa-block element, one can specify zero
      or more attribute elements.-->
	  
 <!ELEMENT ssa-command-tool (category?, description?, comment?,
      owner?, default-target?, execute-as-user?,
      job-display-handler?,
      toolbox-enabled?, toolbox*,
      role-enabled?, role*,
      include-filter*, env-variable*,
      ssa-block, attribute* ) >

<!-- In addition to the previously described elements, the
      ssa-command-tool element specifies the following attributes. The
      name attribute specifies the tool name and must be specified in
      the ssa-command-tool element. The visible attribute specifies
      whether the tool is visible for running. By default tools are
      visible. The max-targets attribute specifies the maximum number
      of targets against which a tool can run. The revision attribute
      allows a tool author to specify a revision for the tool. Âü°í:
      that this is for information only. The job-log attribute
      specifies whether the results of the command will be kept in this
      system's job log. This attribute applies only to tools when they
      are run as scheduled tasks, not when they are run as "run now"
      tasks. When job-log="true" the job and target status for the tool
      will be kept for a relatively lengthy system-defined period in
      the database after the job completes. When job-log="false" only
      the last completed copy of the job and target status for the task
      will be kept in the cache for a much shorter period of time, and
      will not be written to the database.	 Job logging is enabled by
      default. The schedulable attribute specifies whether the tool can
      be run as a schedulable task. When scheduled="false" the tool can
      only run as a "run now" task.  Tools are scheduled by default.
      The GUID attribute specifies a globally unique identifier (GUID)
      for the tool. Because the system generates a GUID for a tool
      during the add operation, this field should only be specified
      during a modify operation. The accepts-targets attribute specifies
      whether the tool accepts targets for execution. The
      accepts-targets attribute is true by default. -->

<!ATTLIST ssa-command-tool name	     CDATA   #REQUIRED
      visible     (true | false) "true"
      max-targets NMTOKEN #IMPLIED
      revision    CDATA   #IMPLIED
      job-log     (true | false) "true"
      schedulable (true | false) "true"
      guid	     NMTOKEN #IMPLIED
      accepts-targets (true|false) "true" >

<!-- The ssa-block specifies the elements specific to a single-system
      aware tool. The ssa-block can specify a command or copy-block or
      both. Only one command should be specified but up to 16 multiple
      copy-blocks can be specified. After the command and/or
      copy-blocks, one can specify the parameters for the command
      and/or copy-block. -->
  
<!ELEMENT ssa-block (( command | copy-block )+, parameter*) >

<!-- The copy-block specifies a source file path and a destination
      file path for a copy operation. -->

<!ELEMENT copy-block ( source, destination )+ >

<!-- The source element specifies the source file path for a copy
      operation. -->

<!ELEMENT source (#PCDATA) >

<!-- The destination element specifies the destination file path for a
      copy operation. -->
     
<!ELEMENT destination (#PCDATA) >

<!-- The msa-command-tool element specifies a multiple-system aware
      tool. The msa-command-tool element can optionally specify a
      category element, a description element, a comment element, an
      owner element, a default-target element, an execute-as-user
      element, a job-display-handler element, a toolbox-enabled
      element, zero or more toolbox elements, zero or more
      include-filter elements, or zero or more env-variable elements.
      (NOTE: The role-enabled and role elements are deprecated
      elements and should not be used with this product. These
      are provided for backward compatibility with previous
      products. The toolbox-enabled element and the toolbox
      element should be used in their stead.)
      If more than one of these elements are specified, the element
      must appear in the order as listed in this definition. The
      msa-command-tool element must contain an msa-block element. The
      msa-block element must appear after the previously described
      optional elements, if any of the optional elements are
      specified. Following the msa-block element, one can specify zero
      or more attribute elements.-->
      
<!ELEMENT msa-command-tool (category?, description?, comment?, owner?,
      default-target?, execute-as-user?,
      job-display-handler?,
      toolbox-enabled?, toolbox*,
      role-enabled?, role*,
      include-filter*, env-variable*,
      msa-block, attribute* ) >

<!-- In addition to the previously described elements, the
      msa-command-tool element specifies the following attributes. The
      name attribute specifies the tool name and must be specified in
      the msa-command-tool element. The visible attribute specifies
      whether the tool is visible for running. By default tools are
      visible. The max-targets attribute specifies the maximum number
      of targets against which a tool can run.  The revision attribute
      allows a tool author to specify a revision for the tool. Note
      that this is for information only. The job-log attribute
      specifies whether the results of the command will be kept in this
      systems job log. When job-log="true" the job and target status
      for the tool will be kept for a relatively lengthy system-defined
      period in the database after the job completes. When
      job-log="false" only the last completed copy of the job and
      target status for the tool will be kept in the cache for a much
      shorter period of time, and will not be written to the database.
      Job logging is enabled by default. The schedulable attribute
      specifies whether the tool can be run as a scheduled task. When
      schedulable="false" the tool can only run as a "run now" task.
      Tools are schedulable by default.  The guid attribute specifies a
      globally unique identifier (GUID) for the tool. Because the
      system generates a GUID for a tool during the add operation, this
      field should only be specified during a modify operation.  The
      accepts-targets attribute specifies whether the tool
      accepts targets for execution. The accepts-targets attribute is
      true by default. -->

<!ATTLIST msa-command-tool name	     CDATA   #REQUIRED
      visible     (true | false) "true"
      max-targets NMTOKEN #IMPLIED
      revision    CDATA   #IMPLIED
      job-log     (true | false) "true"
      schedulable (true | false) "true"
      guid	     NMTOKEN #IMPLIED
      accepts-targets (true|false) "true" >

<!-- The msa-block specifies the elements specific to a
      multiple-system aware (MSA) tool. The msa-block can specify an
      MSA command, the parameters for the command and an execution system
      on which the command executes. -->
      
<!ELEMENT msa-block ( command, parameter*, execution-system ) >

<!-- The command element specifies the command for an SSA or an MSA
      tool. If the command accepts parameters, it must be specified as
      a parameterized string. -->
     
<!ELEMENT command ( #PCDATA ) >

<!-- The command element can have two attributes. The command-type
      attribute specifies whether the command is an x-window, stdout,
      restart, launch, or an unknown command type. The default command
      type is stdout. The log attribute specifies whether the results
      of the command will be output to this system's audit log. When
      log="true" the stdout and stderr results of the command will be
      output to the system's audit log. Command output is not logged
      by default. -->
      
<!ATTLIST command command-type (x-window |
      stdout   |
      restart  |
      launch   |
      unknown) "stdout"
      log (true | false) "false" >

<!-- The execution-system element specifies the system on which an MSA
      tool will execute. -->
      
<!ELEMENT execution-system ( #PCDATA ) >

<!-- The web-launch-tool element specifies a web launch tool. The
      web-launch-tool element can optionally specify a category
      element, a description element, a comment element, an owner
      element, a default-target element, an execute-as-user element, a
      job-display-handler element, a toolbox-enabled element, zero or
      more toolbox elements,  zero or more include-filter elements, or
      zero or more env-variable elements.
      (NOTE: The role-enabled and role elements are deprecated
      elements and should not be used with this product. These
      are provided for backward compatibility with previous
      products. The toolbox-enabled element and the toolbox
      element should be used in their stead.)
      If more than one of these elements are specified, the element
      must appear in the order as listed in this definition. The
      web-launch-tool element must contain a web-block element. The
      web-block element must appear after the previously described
      optional elements, if any of the optional elements are
      specified. Following the web-block element, one can specify zero
      or more attribute elements.-->
      
<!ELEMENT web-launch-tool (category?, description?, comment?, owner?,
      default-target?, execute-as-user?,
      job-display-handler?,
      toolbox-enabled?, toolbox*,
      role-enabled?, role*,
      include-filter*, web-block, attribute* ) >

<!-- In addition to the previously described elements, the
      web-launch-tool element specifies the following attributes. The
      name attribute specifies the tool name and must be specified in
      the web-launch-tool element. The visible attribute specifies
      whether the tool is visible for running. By default tools are
      visible. The max-targets attribute specifies the maximum number
      of targets against which a tool can run.  The revision attribute
      allows a tool author to specified a revision for the tool. Note
      that this is for information only. The job-log attribute
      specifies whether the results of the command will be kept in this
      systems job log. When job-log="true" the job and target status
      for the tool will be kept for a relatively lengthy system-defined
      period in the database after the job completes. When
      job-log="false" only the last completed copy of the job and
      target status for the tool will be kept in the cache for a much
      shorter period of time, and will not be written to the database.
      Job logging is enabled by default.  The schedulable attribute
      specifies whether the tool can be run as a scheduled task. When
      schedulable="false" the tool can only run as a "run now" task.
      Tools are schedulable by default. The guid attribute specifies a
      globally unique identifier (GUID) for the tool. Because the
      system generates a GUID for a tool during the add operation, this
      field should only be specified during a modify operation. -->

<!ATTLIST web-launch-tool name	    CDATA #REQUIRED
      visible	    (true | false) "true"
      max-targets NMTOKEN #IMPLIED
      revision    NMTOKEN #IMPLIED
      job-log	    (true | false) "true"
      schedulable (true | false) "true"
      guid	    NMTOKEN #IMPLIED >

<!-- The web-block specifies the elements specific to a web launch
      tool. The web-block must specify a main-url element. Optionally,
      the web-block can specify a side-url element, a status-url
      element, and a current-url element. Additionally, the web-block
      can specify the parameters for the URLs. Finally, the web-block
      can optionally specify a target format to describe how targets
      are passed to a Web-launch aware tool. -->
      
 <!ELEMENT web-block (main-url, (side-url?, status-url?, current-url?),
      parameter*, target-format? ) >

<!-- In addition to the above elements, the web-block element has one
      attribute. The accepts-targets attribute specifies whether the
      web launch tool accepts targets for execution. The
      accepts-targets attribute is true by default. -->
      
<!ATTLIST web-block accepts-targets (true|false) "true">

<!-- The main-url specifies the URL to launch the tool. If the URL
      accepts parameters, the URL must be specified as a parameterized
      string. -->
      
<!ELEMENT main-url ( #PCDATA ) >

 <!-- The status-url specifies a URL at which one might find the status
      of this web launch tool during execution. -->
      
<!ELEMENT status-url ( #PCDATA ) >

<!-- The current-url specifies the current URL. -->

<!ELEMENT current-url ( #PCDATA ) >

<!-- The side-url specifies a set-aside URL. -->

<!ELEMENT side-url ( #PCDATA ) >

<!-- The target-format defines the format of targets in a web launch
      tool and is specified as a parameterized string.-->
      
<!ELEMENT target-format ( #PCDATA ) >

<!-- The automation tool performs an action on the CMS which
      involves accessing the target systems. The automation-tool element
      can optionally specify a category element, a menu-category
      element, a description element, a comment element, an owner
      element, a default-target element, an execute-as-user element, a
      job-display-handler element, a default-parameter element, a
      role-enabled element, zero or more  role elements,  zero or more
      include-filter elements, or zero or more env-variable elements.
      If more than one of these elements are specified, the element
      must appear in the order as listed in this definition. The
      automation-tool element must contain an automation-block element.
      The automation-block element must appear after the previously
      described optional elements, if any of the optional elements are
      specified. Following the automation-block element, one can
      specify zero or more attribute elements. -->
      
<!ELEMENT automation-tool (category?, description?, comment?, owner?,
      default-target?, execute-as-user?,
      job-display-handler?,
      toolbox-enabled?, toolbox*,
      role-enabled?, role*,
      include-filter*, automation-block,
      attribute* ) >

<!-- In addition to the previously described elements, the
      automation-tool element specifies the following attributes. The
      name attribute specifies the tool name and must be specified in
      the automation-tool element. The visible attribute specifies
      whether the tool is visible for running. By default tools are
      visible. The max-targets attribute specifies the maximum number
      of targets against which a tool can run. The revision attribute
      allows a tool author to specify a revision for the tool. Note
      that this is for information only.  The job-log attribute
      specifies whether the results of the command will be kept in this
      systems job log. When job-log="true" the job and target status
      for the tool will be kept for a relatively lengthy system-defined
      period in the database after the job completes. When
      job-log="false" only the last completed copy of the job and
      target status for the tool will be kept in the cache for a much
      shorter period of time, and will not be written to the database.
      Job logging is enabled by default. The schedulable attribute
      specifies whether the tool can be run as a scheduled task. When
      schedulable="false" the tool can only run as a "run now" task.
      Tools are schedulable by default.  The guid attribute specifies a
      globally unique identifier (GUID) for the tool. Because the
      system generates a GUID for a tool during the add operation, this
      field should only be specified during a modify operation. The
      accepts-targets attribute specifies whether the tool
      accepts targets for execution. The accepts-targets attribute is
      true by default. -->
      
!ATTLIST automation-tool	 name	     CDATA   #REQUIRED
      visible     (true | false) "true"
      max-targets NMTOKEN #IMPLIED
      revision    CDATA   #IMPLIED
      job-log     (true | false) "true"
      schedulable (true | false) "true"
      guid	     NMTOKEN #IMPLIED
      accepts-targets (true|false) "true" >

<!-- The automation-block specifies the elements specific to an
      automation tool. The automation-block must specify a
      message-id. -->
      
<!ELEMENT automation-block (message-id) >

<!-- The message-id is the internal string representation of the message
      sent by the Automation engine to cause the tool to run. -->
      
<!ELEMENT message-id ( #PCDATA ) >

<!-- The app-launch-tool element specifies an application launch
      tool. The app-launch-tool element can optionally specify a
      category element, a menu-category element, a description element,
      a comment element, an owner element, a default-target element, an
      execute-as-user element, a job-display-handler element, a
      default-parameter element, a role-enabled element, zero or more
      role elements,  zero or more include-filter elements, or zero or
      more env-variable elements. If more than one of these elements
      are specified, the element must appear in the order as listed in
      this definition. The app-launch-tool element must contain an
      app-launch-block element. The app-launch-block element must
      appear after the previously described optional elements, if any
      of the optional elements are specified. Following the
      app-launch-block element, one can specify zero or more attribute
      elements. -->

<!ELEMENT app-launch-tool (category?, description?, comment?, owner?,
      default-target?, execute-as-user?,
      job-display-handler?,
      role-enabled?, role*,
      toolbox-enabled?, toolbox*,
      include-filter*,  env-variable*,
      app-launch-block, attribute* ) >

<!-- In addition to the previously described elements, the
      app-launch-tool element specifies the following attributes. The
      name attribute specifies the tool name and must be specified in
      the app-launch-tool element. The visible attribute specifies
      whether the tool is visible for running. By default tools are
      visible. The max-targets attribute specifies the maximum number
      of targets against which a tool can run. The revision attribute
      allows a tool author to specify a revision for the tool. Note
      that this is for information only.  The job-log attribute
      specifies whether the results of the command will be kept in this
      systems job log. When job-log="true" the job and target status
      the tool will be kept for a relatively lengthy system-defined
      period in the database after the job completes. When
      job-log="false" only the last completed copy of the job and
      target status for the tool will be kept in the cache for a much
      shorter period of time, and will not be written to the database.
      Job logging is enabled by default. The schedulable attribute
      specifies whether the tool can be run as a scheduled task. When
      schedulable="false" the tool can only run as a "run now" task.
      Tools are schedulable by default.  The guid attribute specifies a
      globally unique identifier (GUID) for the tool. Because the
      system generates a GUID for a tool during the add operation, this
      field should only be specified during a modify operation. The
      accepts-targets attribute specifies whether the tool
      accepts targets for execution. The accepts-targets attribute is
      true by default. -->

<!ATTLIST app-launch-tool	 name	     CDATA   #REQUIRED
      visible     (true | false) "true"
      max-targets NMTOKEN #IMPLIED
      revision    CDATA   #IMPLIED
      job-log     (true | false) "true"
      schedulable (true | false) "true"
      guid	     NMTOKEN #IMPLIED
      accepts-targets (true|false) "true" >

<!-- The app-launch-block specifies the elements specific to an
      application launch tool. The app-launch-block specifies a
      required command element. -->
      
<!ELEMENT app-launch-block (command, app-parameters?) >

<!-- In addition to the previously described elements, the
      app-launch-block element specifies the following attribute. The
      alert-driven attribute specifies whether the alert list or the
      system list is used to determine the target systems to run the tool
      on. -->

<!ATTLIST app-launch-block alert-driven (true | false) "false" >

<!-- The app-parameters element is an application parameters
      definition string whose value is a string -->
      
<!ELEMENT app-parameters ( #PCDATA ) >

<!-- The env-variable element is an environment variable definition
      string whose value is a string -->
      
<!ELEMENT env-variable ( #PCDATA ) >

<!-- In addition to the previously described elements, the
      env-variable element specifies the following attribute. The
      name attribute specifies the name of the environment variable.-->
      
<!ATTLIST env-variable name CDATA #REQUIRED >

<!-- The owner element specifies the tool owner. When the owner field
      is specified, the tool is only associated with the All Tools toolbox.
      When the owner field is not specified, tool is enabled in all
      of its associated toolboxes. When a limited-rights user adds or
      modifies a tool, the owner field contains the name of the
      limited-rights user. Only a full-rights user can add or modify a
      tool without the owner specified. -->
      
<!ELEMENT owner ( #PCDATA ) >

 !-- The comment field specifies additional information about the
      tool. It is usually more verbose that the description. -->

<!ELEMENT comment ( #PCDATA ) >

<!-- The parameter element specifies the first to the tenth parameter
      of a tool. -->
     
<!ELEMENT parameter EMPTY >

<!-- The parameter element has three attributes. The index attributes
      specifies which argument in a parameterized string this parameter
      substitutes. Parameters can be indexed from 1 to 10 with a
      default index of 1. Tools cannot contain parameters with
      duplicate indexes. If more than one parameter in a tool
      definition contains the same index, only the first parameter added
      to the tool with the duplicate index remains in the tool. The
      prompt attribute provides information about the parameter that
      can be displayed in a GUI for assistance. The required attribute
      specifies whether this parameter must be specified when the tool
      is executed. By default, parameters are not required.  The private
      attribute specifies whether this parameter is encoded and stored
      securely.  By default, parameters are not private. -->
<!ATTLIST parameter index	 (1|2|3|4|5|6|7|8|9|10) "1"
     prompt CDATA #REQUIRED
      required (true|false) "false"
      private (true|false) "false" >

<!-- The toolbox-enabled element specifies whether the toolboxes
      associated with a tool are enabled. -->

<!ELEMENT toolbox-enabled EMPTY >

<!-- The toolbox-enabled element has one attribute. The value
      attribute specifies whether the tool within the toolboxes is enabled.
      This allows a full-rights user to explicitly disable the tools in
      a toolbox though the tool is always enabled in the All Tools
      toolbox.  By default, the tool is enabled in all the toolboxes that
      it is in.  If a tool is disabled within a toolbox, it cannot be
      executed. -->
      
<!ATTLIST toolbox-enabled value (true|false) "true">

<!-- The role-enabled element specifies whether the roles associated
      with a tool are enabled. This is an obsolete element. The
      toolbox-enabled element should be used instead.-->
      
<!ELEMENT role-enabled EMPTY >

<!-- See description of toolbox-enabled element attributes. -->

<!ATTLIST role-enabled value (true|false) "true">

<!-- The default-target element specifies a target on which the tool
      can run if no targets are specified at run time. One can specify
      a system, &cms2; to run on the &cms2; by default, or ALL to run on all
      authorized systems by default. -->
      
<!ELEMENT default-target ( #PCDATA ) >

<!-- The category element specifies the category with which to
      associate the tool. By default, tools are associated with the
      "Local Tools" category. -->

<!ELEMENT category ( #PCDATA ) >

<!-- The description element specifies a simple description of the
      tool. To specify more verbose information such as how to run the
      tool, use the comment element. -->

<!ELEMENT description ( #PCDATA ) >

<!-- For SSA and MSA command tools, the execute-as-user element
      specifies the user name that the tool runs as or under whose
      account the tool runs on the target systems. For Web-launch
      tools the execute-as-user is passed to the URL for its use. -->

<!ELEMENT execute-as-user ( #PCDATA ) >

<!-- The job display hander element specifies the fully-qualified
      name of a class implementing the JobDisplayHander interface,
      used to display the results of a job created by running this
      tool. -->

<!ELEMENT job-display-handler ( #PCDATA ) >

<!-- The toolbox element specifies a toolbox to associate with the
      tool. To run a tool the user must be authorized with one of the
      specified toolboxes. -->

<!ELEMENT toolbox EMPTY >

<!-- The toolbox element has one attribute to specify the toolbox
      name. -->

<!ATTLIST toolbox toolbox-name CDATA #REQUIRED >

<!-- The role element specifies a role to associate with the tool. To
      run a tool the user must be authorized with one of the specified
      roles. This element is obsolete. The toolbox element should be
      used instead. -->

<!ELEMENT role EMPTY >

<!-- See the toolbox element attribute description. -->

<!ATTLIST role role-name CDATA #REQUIRED >

<!-- The include-filter element specifies system attributes against
      which to filter a tool for execution. A specified include-filter
      element must contain one or more system-filter elements. When
      filtering a tool each include-filter block is OR'd together to
      get the final filter result. Each system-filter element within an
      include-filter block is AND'd together. -->
      
<!ELEMENT include-filter (system-filter)+ >

<!-- The include-filter elements has one attribute. The type attribute
      specifies the type of include filter to execute. Four types are
      currently recognized.  Three of them are os (operating system), 
      hardware, protocol filtering. The fourth type is called other which 
      will allow all other system attributes to be filtered upon.-->

<!ATTLIST include-filter type (os | hardware | protocol | other) "os" >

<!-- The system-filter element is an empty element that contains
      attributes used to specify the system attributes against which to
      filter a tool for execution. -->
      
<!ELEMENT system-filter EMPTY >

<!-- The system-filter element is specified with three attributes. The
      name attribute specifies the system attribute name to filter
      against. The operator attribute specifies whether to filter
      against an equal value, a less than value, a greater than or
      equal value, a contains value, a not equals value or a not
      contains value. The operator name is case-insensitive. The
      value attribute specifies the value of the system attribute to
      filter against. -->
      
<!ATTLIST node-filter name CDATA #REQUIRED
      operator (EQ | GE | LT | CT | NEQ | NCT |
      eq | ge | lt | ct | neq | nct |
      Eq | Ge | Lt | Ct | Neq | Nct |
      eQ | gE | lT | cT | nEQ | nCT ) "EQ"
      value CDATA #REQUIRED >

<!-- The attribute element specifies the name value pairs that
      comprise client attributes. The client attribute name is
      specified using the name attribute and the client attribute value
      is specified as the PCDATA of the element. -->

<!ELEMENT attribute ( #PCDATA ) >

<!ATTLIST attribute name CDATA #REQUIRED >
			

°ü·Ã ÀýÂ÷

 »ç¿ëÀÚ Á¤ÀÇ µµ±¸ - »ç¿ëÀÚ Á¤ÀÇ µµ±¸ Á¦°Å ¹× º¹¿ø
 »ç¿ëÀÚ Á¤ÀÇ µµ±¸ - CMS µµ±¸ ÆíÁý
 »ç¿ëÀÚ Á¤ÀÇ µµ±¸ - ¿ø°Ý µµ±¸ ÆíÁý
 »ç¿ëÀÚ Á¤ÀÇ µµ±¸ - À¥ ÆäÀÌÁö µµ±¸ ÆíÁý

°ü·Ã Ç׸ñ

 °ü¸® È®Àå µµ±¸ - ¸í·ÉÁÙ µµ±¸