User manual SONY VAIO VGN-SZ740N

[. . . ] Hewlett-Packard Company 3000 Hanover Street Palo Alto, CA 94304 U. S. A. Government Departments and Agencies are as set forth in FAR 52. 227-19(c)(1, 2). Use of this manual and flexible disc(s), compact disc(s), or tape cartridge(s) supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. [. . . ] Thus, they also require the Security Token. Security Token Handling Alternatively, SONY provides a library with a security token-generating procedure and a security token validation procedure. Management applications can use these procedures to secure access to protected attribute values. Additionally, SONY provides a library to management application writers that wish to retrieve protected attributes from SONY's implementation of the Unix Standards Group Definition (Unix MIF). This library contains the security token-generating procedure. These two procedures are: · GenerateToken() · ValidateToken() For detailed information, see the generateToken(3X) and validateToken(3X) manpages. Chapter 3 31 Component Interface Concepts Group-Level Security 32 Chapter 3 4 Writing Component MIF Files Management Information Format (MIF) Files Within DMI, information about all components is defined in a language called the Management Interface Format (MIF) and stored by the DMI SP in a MIF database. Each component has a unique MIF file which describes its manageable characteristics. Each MIF file describes one, and only one component. However, there may be multiple instances of the component on a single system. When a management application or component instrumentation asks the SP to add a component, the SP compiles the associated MIF file containing schema description data, checks it for adherence to the DMI MIF format and installs it in the MIF database. The MIF database is then accessed when a management application asks the SP to list, get or set the attributes of installed components. Attributes, within the group specified by GroupId, that use the Direct Interface. A value of zero indicates that all attributes within this group use the Direct Interface. attributeId typedef struct DmiAccessData { DmiId_t groupId; DmiId_t attributeId; } DmiAccessData_t; 38 Chapter 5 Component Interface Data Structures DmiAccessDataList DmiAccessDataList This data structure describes an array of DmiAccessData. Table 5-2 Field Name size list DMIAccessDataList Description Array elements Array data typedef struct DmiAccessDataList { DmiUnsigned_t size; DmiAccessData_t* list; } DmiAccessDataList_t; Chapter 5 39 Component Interface Data Structures DmiRegisterInfo DmiRegisterInfo This data structure identifies entry points for registering CI Direct Interface code. Table 5-3 Field Name componentId ciGetAttribute ciGetNextAttribute ciReserveAttribute ciReleaseAttribute ciSetAttribute ciAddRow ciDeleteRow accessData DmiRegisterInfo Description Identifier assigned by the service provider on component installation Address of the CiGetAttribute entry point Address of the CiGetNextAttribute entry point Address of the CiReserveAttrribute entry point Address of the CiReleaseAttrribute entry point Address of the CiSetAttribute entry point Address of the CiAddRow entry point Address of the CiDeleteRow entry point Array containing the groups and/or individual attributes that use the Direct Interface componentId; ciGetAttribute; ciGetNextAttribute; ciReserveAttribute; ciReleaseAttribute; ciSetAttribute; ciAddRow; ciDeleteRow; *accessData; typedef struct DmiRegisterInfo { DmiId_t CiGetFunc CiGetFunc CiResRelFunc CiResRelFunc CiSetFunc CiAddDelFunc CiAddDelFunc DmiAccessDataList_t }DmiRegisterInfo_t; 40 Chapter 5 6 Component Interface Functions There are three classes of functions in the SONY-UX DMI 2. 0 Component Interface, they are as follows: Service Provider Functions for Implemented by the DMI SP and may be Components invoked by component developers. These include registration and indication origination functions. Component Provider Implemented by component developers and Functions may be invoked by the DMI SP. Optional Component Authorization techniques for the security Interface Support Functions provided by the DMI SP. The following sections list and provide a brief description of each CI function call. For detailed information on a function, see the function man pages included with this SDK, or see the DMTF DMI Version 2. 0 Specification. · "Service Provider Functions for Components" on page 42 · "Component Provider Functions" on page 44 · "Optional Component Interface Support Functions" on page 47 41 Component Interface Functions Service Provider Functions for Components Service Provider Functions for Components Using the following Service Provider Functions for Components, component instrumentation code can register with the SP to override its current access mechanism for the registered attributes. Instead of manipulating the data in the MIF database or invoking programs, the SP calls the entry points provided in the registration call. Once the component unregisters, the SP returns to its normal method of processing requests for the data as defined in the SP's MIF. In this manner, component instrumentation temporarily interrupts normal processing to perform special functions. · "DmiMainLoop()" on page 42 · "DmiOriginateEvent()" on page 42 · "DmiRegisterCi()" on page 43 · "DmiUnregisterCi()" on page 43 DmiMainLoop() Waits on the socket communication thread for component instrumentation or the Indication Server thread for management applications. int DmiMainLoop() DmiOriginateEvent() Originates an event for filtering and delivery. [. . . ] Figure A-3 Example Component Component instrumentation for the dynamic data in this example is handled in the ci_systemExample. h file. Instrumentation provided by the developer is identified as following between headers and footers like those illustrated below. The corresponding ci_systemExample. c file does not need to be modified. Appendix A 117 An SONY-UX DMI 2. 0 Example Code The Example Component /*================================================ START OF DEVELOPER DEFINED CODE ================================================= */ /* =============================================== END OF DEVELOPER DEFINED CODE. ================================================= */ Component functions are defined in the ci_cpfc. c file. [. . . ]