Return to components.dxx CVS log | Up to [Pegasus] / pegasus / doc / DevManual |
File: [Pegasus] / pegasus / doc / DevManual / components.dxx
(download)
Revision: 1.3, Sun Feb 25 17:28:39 2001 UTC (23 years, 3 months ago) by karl Branch: MAIN CVS Tags: version_1_01, version_0_99_1, version_0_99, version_0_97_3, version_0_97_2, version_0_97_1, version_0_97, version_0_96, version_0_95, version_0_8, version_0_79_4, test, stable_0_95, stable, pep_88, pegasus25BeforeLicenseUpdate, merge_of_dev, mday-merge-start, mday-merge-pegasus/src/Pegasus/Server, mday-merge-pegasus/src/Pegasus/Common, mday-2-0-patches, main, local, dev_dead, dev, VERSION_2_1_RELEASE_HEAD, VERSION_2_1_RELEASE_BRANCH, VERSION_2_1_RELEASE, VERSION_2_1_1_RELEASE, VERSION_2_01_01, VERSION_2_00_RC_4, VERSION_2_00_RC_3, VERSION_2_00_RC_2, VERSION_2_00_RC_1, VERSION_2_00_BRANCH, VERSION_1_10, VERSION_1_09, VERSION_1_08, VERSION_1_07, TEST, SNAPSHOT_1_04, SLPPERFINST-root, SLPPERFINST-branch, RELEASE_2_5_0-RC1, RELEASE_2_5_0, RELEASE_2_4_FC_CANDIDATE_1, RELEASE_2_4_3, RELEASE_2_4_2, RELEASE_2_4_1-BETA3, RELEASE_2_4_1-BETA2, RELEASE_2_4_1-BETA1, RELEASE_2_4_1, RELEASE_2_4_0-RC3, RELEASE_2_4_0-RC2, RELEASE_2_4_0, RELEASE_2_4-root, RELEASE_2_4-branch, RELEASE_2_3_2-testfreeze, RELEASE_2_3_2-root, RELEASE_2_3_2-releasesnapshot, RELEASE_2_3_2-branch-freeze, RELEASE_2_3_2-branch, RELEASE_2_3_1-root, RELEASE_2_3_1-branch, RELEASE_2_3_0-root, RELEASE_2_3_0-msg-freeze, RELEASE_2_3_0-branch, RELEASE_2_2_1-snapshot, RELEASE_2_2_0_0-release, RELEASE_2_2_0-root, RELEASE_2_2_0-branch, RELEASE_2_2-root, PRE_LICENSE_UPDATE_2003, POST_LICENSE_UPDATE_2003, PEP217_PRE_BRANCH, PEP217_POST_BRANCH, PEP217_BRANCH, PEP214ROOT, PEP214BRANCH, PEP214-root, PEP214-branch, PEP213_SIZE_OPTIMIZATIONS, PEP-214B-root, PEGASUS_FC_VERSION_2_2, PEGASUS_2_5_0_PerformanceDev-string-end, PEGASUS_2_5_0_PerformanceDev-rootlt, PEGASUS_2_5_0_PerformanceDev-root, PEGASUS_2_5_0_PerformanceDev-r2, PEGASUS_2_5_0_PerformanceDev-r1, PEGASUS_2_5_0_PerformanceDev-lit-end, PEGASUS_2_5_0_PerformanceDev-buffer-end, PEGASUS_2_5_0_PerformanceDev-branch, PEGASUS_2_5_0_PerformanceDev-AtomicInt-branch, PEG25_IBM_5_16_05, NPEGASUS_2_5_0_PerformanceDev-String-root, NNPEGASUS_2_5_0_PerformanceDev-String-branch, MONITOR_CONSOLIDATION_2_5_BRANCH, LOCAL_ASSOCPROV-ROOT, LOCAL_ASSOCPROV-BRANCH, IBM_241_April1405, CQL_2_5_BRANCH, CHUNKTESTDONE_PEP140, BUG_4225_PERFORMANCE_VERSION_1_DONE Changes since 1.2: +30 -25 lines delete graphic |
/* $Log: components.dxx,v $ Revision 1.3 2001/02/25 17:28:39 karl delete graphic Revision 1.2 2001/02/25 15:01:40 karl Add frames to manual Revision 1.1 2001/01/24 14:18:49 karl import Dev Doc Files $Author: karl $ */ /** @name Pegasus Components This section defines the major components that make up the Pegasus environment, the architectureal components, the built components, and the supporting directory structure. */ //@{ /** @name Component Descriptions The major components of Pegasus are: <B>Pegasus Server</B> - WBEM/CIM CIM_Server with interfaces for providers and Clients <B>Pegasus Repository </B>- Today Pegasus provides a defined class repository interface and a simple file based class repository. Future will include the object repository <B>Pegasus Client SDK</B> - Tools for building Pegasus clients based on the Pegasus C++ interfaces and using the WBEM HTTP/XML protocols or directly interfacing with Pegasus <B>Pegasus Test Clients</B> - Simple test clients being developed as part of the Pegasus development process <B>Pegasus HTML Test Client</B> - To aid some testing we created a test client for Pegasus that uses a WEB server (ex. Apache) with a set of CGI modules and HTML to allow the entry of Pegasus operations from a WEB browser as forms and the recept of the response as WEB pages. This has proven useful as a test tool and can be used for a wide variety of demonstrations. <B>Pegasus Providers</B> - Pegasus providers are build as separate components that can be dynamically loaded by the Pegasus server. <B>Pegasus Service Extensions</B> - Future (version 1.0) <B>Pegasus MOF Compiler</B> - The Pegasus MOF compiler compiles MOF files and installs them into the Pegasus repository. ATTN: Define the files that make up these components and their structure. */ /** @name Pegasus Directory Structure Pegasus is distributed as a complete directory structure that should be installed either from one of the snapshots or from CVS. This structure is generally as follows: <PRE> Pegasus - Root directory bin build Destination for all intermediate files from build if no alternative is specified see PEGASUS_HOME cgi-bin Source and make for the Pegasus WEB Based Test client software doc Miscelaneous Pegasus Documents. Includes the DMTF XML for CIM 2.4 html HTML files for the Browser test client. mak General make files (used by the root make and other makes) Repository This Directory containes the created repository src All Pegasus Source Files ACEExamples Test directrory with examples of the use of ACE (developers) Clients Top level directory for Pegasus Client Programs CGI_Client Source for the Pegasus client for the WEB demo Pegasus CGI CGI files for the WEB test client CGIClient Client Pegasus Client SDK and Test client using the SDK tests Test programs for the client software Common Pegasus Common Functions (C++ source and headers tests Test programs for the common functions Protocol Pegasus Client HTTP/XML Protocol Modules tests Repository Pegasus Repository Interfaces and Simple Repository tests Tests for Repository Functions Server Pegasus Server Modules tests Unit tests defined for the server functions Providers Top Level Directory for Pegasus written Providers Generic Non-system oriented providers Windows Providers defined for the Windows environment Unix Providers defined for the Unix environment Services To-be-defined. Utils manual Pegasus User/developer manual source modules HTML Output from the Pegasus Manual compilartion. </PRE> */ //@}
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |