All The Claims

1. A method comprising:
using firmware to abstract error information for an operating system (OS) within a computer system, the error information from disparate sources in the computer system, the error information abstracted from platform specific error registers of various different platforms, wherein the disparate sources comprise a central processing unit, memory controller, and inputoutput controller, and wherein the error information is abstracted from different platform error record formats based on different vendor formats for the central processing unit, memory controller, and inputoutput controller;
constructing an error record using the error information, the error record in a common error record format useable by the operating system;
depositing the error record into two or more abstracted error access registers comprising memory buffers visible to the OS;
making the error information available to the OS by the firmware presenting to the OS, the two or more abstracted error access registers comprising memory buffers visible to the OS;
the operating system accessing the error record from the two or more abstracted error access registers, without platform specific knowledge of the platform specific error registers;
using the firmware to intercept error log access request from the OS; and
fulfilling the error log access request by the firmware in a manner transparent to the OS.
2. The method according to claim 1, further comprising:
using the firmware to support platform error injection, wherein a request to inject errors from the OS is trapped and is fulfilled by the firmware transparently to the OS.
3. The method according to claim 1, further comprising:
trapping error access to hardware within the computer system; and
using the error access to provide an abstraction in a common error record format.
4. The method according to claim 1, further comprising:
trapping access to hardware within the computer system using the firmware; and
in response to the access trapped, returning the error information in a predetermined format.
5. The method according to claim 1, wherein the firmware:
creates the abstract error information by identifying the error and gathering error information from various platform and silicon-specific registers to construct an error record in a common error record format;
deposits the error record into the memory buffers; and
notifies the operating system to access the error record and correct the error without providing the operating system with platform specific knowledge in the abstracted error access registers.
6. The method of claim 1, wherein constructing an error record comprises translating the error information into the error record; wherein abstracting, constructing, depositing, and presenting are performed only by the firmware; and wherein the computer system is coupled to an external printer.
7. An apparatus comprising:
platform firmware executable on a trap to abstract an interface for error information to an operating system (OS), the error information from disparate sources in the computer system, the error information abstracted from platform specific error registers of various different platform, wherein the disparate sources comprise a central processing unit, memory controller, and inputoutput controller, and wherein the error information is abstracted from different platform error record formats based on different vendor formats for the central processing unit, memory controller, and inputoutput controller; and
two or more platform abstracted error access registers to trap to the platform firmware, wherein the platform firmware is executable to abstract error information for the OS and to make the error information available to the OS by:
constructing an error record using the error information, the error record in a common error record format useable by the operating system;
depositing the error record into two or more platform abstracted error access registers comprising memory buffers visible to the OS;
presenting to the OS, the two or more platform abstracted error access registers comprising memory buffers visible to the OS;
the operating system accessing the error record from the two or more abstracted error access registers, without platform specific knowledge of the platform specific error registers;

using the firmware to intercept error log access request from the OS; and
fulfilling the error log access request by the firmware in a manner transparent to the OS.
8. The apparatus of claim 7, wherein the trap is implemented using system management interrupt (SMI).
9. The apparatus of claim 7, wherein the interface comprises an error injection interface having error injection capabilities and an error injection control.
10. The apparatus of claim 7, further comprising:
a service processor, wherein the platform firmware is operable to invoke a system management interrupt (SMI) to log an error to the service processor.
11. The apparatus of claim 7, wherein the platform firmware:
identifies the error and gathers error information from various platform and silicon-specific registers to construct an error record in a common error record format;
deposits the error record into the memory buffers; and
notifies the operating system to access the error record and correct the error without providing the operating system with platform specific knowledge in the abstracted error access registers.
12. The apparatus of claim 7, wherein constructing an error record comprises translating the error information into the error record; wherein abstracting, constructing, depositing, and presenting are performed only by the platform firmware; and wherein the computer system is coupled to an external printer.
13. A non-transitory machine-accessible medium that provides instructions that, if executed by a processor, will cause the machine to perform operations comprising:
using firmware to abstract error information for an operating system (OS) within a computer system, the error information from disparate sources in the computer system, the error information abstracted from platform specific error registers of various different platforms, wherein the disparate sources comprise a central processing unit, memory controller, and inputoutput controller, and wherein the error information is abstracted from different platform error record formats based on different vendor formats for the central processing unit, memory controller, and inputoutput controller;
constructing an error record using the error information, the error record in a common error record format useable by the operating system;
depositing the error record into two or more abstracted error access registers comprising memory buffers visible to the OS;
making the error information available to the OS by the firmware presenting to the OS, the two or more abstracted error access registers comprising memory buffers visible to the OS;
the operating system accessing the record from the two or more abstracted error access registers, without platform specific knowledge of the platform specific error registers;
using the firmware to intercept error log access request from the OS; and
fulfilling the error log access request by the firmware in a manner transparent to the OS.
14. The machine-accessible medium according to claim 13, wherein the operations further comprise:
using the firmware to support platform error injection, wherein a request to inject errors from the OS is trapped and is fulfilled by the firmware transparently to the OS.
15. The machine-accessible medium according to claim 13, wherein the operations further comprise:
using the firmware to intercept error log access request from the OS; and
fulfilling the error log access request by the firmware in a manner transparent to the OS.
16. The machine-accessible medium according to claim 13, wherein the operations further comprise:
trapping error access to hardware within the computer system; and
using the error access to provide an abstraction in a common error record format.
17. The machine-accessible medium according to claim 13, wherein the operations further comprise:
trapping access to hardware within the computer system using the firmware; and
in response to the access trapped, returning the error information in a predetermined format.
18. The machine-accessible medium according to claim 13, wherein the firmware:
creates the abstract error information by identifying the error and gathering error information from various platform and silicon-specific registers to construct an error record in a common error record format;
deposits the error record into the memory buffers; and
notifies the operating system to access the error record and correct the error without providing the operating system with platform specific knowledge in the abstracted error access registers.
19. The method according to claim 5, wherein the operating system accesses the error record and corrects the error without platform specific knowledge from the abstracted error access registers.
20. The apparatus of claim 11, wherein the operating system accesses the error record and corrects the error without receiving platform specific knowledge from the abstracted error access registers.
21. The machine-accessible medium according to claim 18, wherein the operating system accesses the error record and corrects the error without platform specific knowledge from the abstracted error access registers.
22. The machine-accessible medium according to claim 13, wherein constructing an error record comprises translating the error information into the error record; wherein abstracting, constructing, depositing, and presenting are performed only by the firmware; and wherein the computer system is coupled to an external printer.
23. A method comprising:
using firmware to abstract error information for an operating system (OS) within a computer system, the error information from at least two disparate sources in the computer system, the error information abstracted from platform specific error registers of various different platforms, wherein the different platform error record formats comprise different vendor formats for each of the at least two disparate sources;
constructing an error record using the error information, the error record in a common error record format useable by the operating system;
depositing the error record into two or more abstracted error access registers comprising memory buffers visible to the OS;
making the error information available to the OS by the firmware presenting to the OS, the two or more abstracted error access registers comprising memory buffers visible to the OS;
the operating system accessing the error record from the two or more abstracted error access registers, without platform specific knowledge of the platform specific error registers;
using the firmware to intercept error log access request from the OS; and
fulfilling the error log access request by the firmware in a manner transparent to the OS.
24. The method of claim 23, wherein constructing an error record comprises translating the error information into the error record; wherein abstracting, constructing, depositing, and presenting are performed only by the firmware; and wherein the computer system is coupled to an external printer.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A method for the modular deployment of a integration component, comprising:
bundling an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for connecting to an enterprise information system;
deploying the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;
adding a Java archive file that packages the common class to class paths for any non-system domains; and
re-cycling a server on which the integration component is deployed if a Java archive file is added to the class path for a non-system domain.
2. A method according to claim 1, further comprising:
recycling a server for the valid system domain.
3. A method according to claim 1 wherein the resource adapter carries out request interaction with the enterprise information system.
4. A method according to claim 3 wherein the application view bean maps service requests to interactions with the resource adapter.
5. A method according to claim 1, wherein:
bundling the integration component allows the integration component to be backward compatible with existing integration systems.
6. A method according to claim 1, wherein:
deploying the integration component allows the integration component to utilize JMS resources available to the valid system domain.
7. A method according to claim 1, further comprising:
configuring parameters for the integration component using a management console.
8. A computer-readable medium, comprising:
means for bundling an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for connecting to an enterprise information system;
means for deploying the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;
means for adding a Java archive file that packages the common class to class paths for any non-system domains; and
means for re-cycling a server on which the integration component is deployed if a Java archive file is added to the class path for a non-system domain.
9. A computer program product stored in a computer readable medium for execution by a server computer for deploying an adapter, comprising:
computer code for bundling an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for connecting to an enterprise information system;
computer code for deploying the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;
computer code for adding a Java archive file that packages the common class to class paths for any non-system domains; and computer code for re-cycling a server on which the integration component is deployed if a Java archive file is added to the class path for a non-system domain.
10. A computer system comprising:
a processor;
object code executed by said processor, said object code configured to:
bundle an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for connecting to an enterprise information system;
deploy the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;
add a Java archive file that packages the common class to class paths for any non-system domains; and
re-cycle a server on which the integration component is deployed if a Java archive file is added to the class oath for a non-system domain.
11. A computer system stored in a computer-readable medium for modular deployment of a integration component, comprising:
an integration component including an application view and a resource adapter for connecting to an enterprise information system wherein the integration component is bundled as an enterprise archive file; and
a valid system domain including a class path wherein the integration component is deployed by using the enterprise archive file;
wherein the re-cycling of a server is necessary only if a Java archive file is added to the class path for non-system domains.
12. A computer readable medium having instructions thereon which when executed by one or more processors cause a system to:
bundle an integration component as an enterprise archive file wherein the integration component includes an application view bean and a resource adapter for allowing a user to connect to an enterprise information system;
deploy the integration component to a valid system domain from the enterprise archive file wherein the system domain includes a class path that contains a common class shared by the application view bean and the resource adapter;
add a Java archive file that packages the common class to class paths for any non-system domains; and
re-cycle a server on which the integration component is deployed if a Java archive file is added to the class path for a non-system domain.

1. A method of managing user authorization levels for access to a plurality of applications, the method comprising:
receiving a request from a user to establish a user profile,
establishing an employment indicator for said user;
retrieving a user authorization level template in response to said employment indicator, said user authorization level template identifying a plurality of applications and a user authorization level for each application;
associating said user authorization levels with said user.
2. The method of claim 1 wherein:
said employment indicator distinguishes an employee from a contractor.
3. The method of claim 1 wherein:
said employment indicator is job title.
4. The method of claim 1 wherein:
said user authorization levels indicate an access level for each of said applications.
5. The method of claim 4 wherein:
said user authorization levels indicates a permission level for each of said applications.
6. The method of claim 1 wherein:
said user authorization level includes administration level permitting or denying said user an ability assign an authorization level to said application to other users.
7. The method of claim 1 wherein:
said user profile includes user personal information, said user personal information being retrieved from an auxiliary database.
8. The method of claim 7 wherein:
said user personal information being retrieved from a human resources database.
9. A computer program for managing user authorization levels for access to a plurality of applications, the computer program including instructions for causing a computer to implement:
receiving a request from a user to establish a user profile,
obtaining an employment indicator for said user;
retrieving a user authorization level template in response to said employment indicator, said user authorization level template identifying a plurality of applications and a user authorization level for each application;
associating said user authorization levels with said user.
10. The computer program of claim 9 wherein:
said employment indicator distinguishes an employee from a contractor.
11. The computer program of claim 9 wherein:
said employment indicator is job title.
12. The computer program of claim 9 wherein:
said user authorization levels indicate an access level for each of said applications.
13. The computer program of claim 12 wherein:
said user authorization levels indicates a permission level for each of said applications.
14. The computer program of claim 9 wherein:
said user authorization level includes administration level permitting or denying said user an ability assign an authorization level to said application to other users.
15. The computer program of claim 9 wherein:
said user profile includes user personal information, said user personal information being retrieved from an auxiliary database.
16. The computer program of claim 15 wherein:
said user personal information being retrieved from a human resources database.
17. A system for managing user authorization levels for access to a plurality of applications, the system comprising:
a user system generating a request from a user to establish a user profile,
an applications system coupled to said user system by a network; said applications system receiving said request and obtaining an employment indicator for said user;
said applications system retrieving a user authorization level template in response to said employment indicator, said user authorization level template identifying a plurality of applications and a user authorization level for each application;
said applications system associating said user authorization levels with said user.
18. The computer program of claim 17 wherein:
said employment indicator distinguishes an employee from a contractor.
19. The computer program of claim 17 wherein:
said employment indicator is job title.
20. The computer program of claim 17 wherein:
said user authorization levels indicate an access level for each of said applications.
21. The computer program of claim 20 wherein:
said user authorization levels indicates a permission level for each of said applications.
22. The computer program of claim 17 wherein:
said user authorization level includes administration level permitting or denying said user an ability assign an authorization level to said application to other users.
23. The computer program of claim 17 wherein:
said user profile includes user personal information, said user personal information being retrieved from an auxiliary database.
24. The computer program of claim 23 wherein:
said user personal information being retrieved from a human resources database.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A system for managing memory space in a mobile device, comprising:
a plurality of data storage locations;
a plurality of software applications, each software application being operable to store data files to a different storage location; and
a data store management system configured to access and delete data files in the plurality of data storage locations,
the data store management system providing a plurality of memory retention algorithms, wherein one of the plurality of memory retention algorithms is selected by a user to determine a criteria used to select data files for deletion from the plurality of data storage locations,
the data store management system further providing a plurality of control levels, the plurality of control levels providing threshold levels for selecting data files for deletion according to the selected memory retention algorithm, wherein a control level is selected to set a threshold level for the selected memory retention algorithm so data files at or above the threshold level are deleted,
wherein the data store management system is further configured to receive an initial control level and delete one or more data files according to the initial control level and the selected memory retention algorithm, and if sufficient memory space is not available after deleting data files according to the initial control level and the selected memory retention algorithm, then increment the initial control level and delete one or more additional data files according to the incremented control level,
wherein the threshold level associated with the control level becomes progressively lower as the selected control level is incremented.
2. The system of claim 1, wherein the plurality of memory retention algorithms include a least recently used algorithm, a first in-first out algorithm and a largest file size algorithm.
3. The system of claim 1, wherein the data store management system is further configured to provide a plurality of selectable groups of control levels, wherein the plurality of control levels are translated to different threshold levels dependant upon the selected control level group.
4. The system of claim 3, wherein the plurality of selectable groups of control levels include a group having threshold levels relating to file size.
5. The system of claim 3, wherein the plurality of selectable groups of control levels include a group having threshold levels relating to the amount of time since a data file has been accessed.
6. The system of claim 1, wherein the plurality of data storage locations include at least one of a browser cache, a message store, an address book, a browser bookmarks store, a calendar data store, a notes store, and an electronic messaging store.
7. The system of claim 1, wherein the plurality of software applications include at least one of an electronic messaging system, an Internet browser application and a calendar application.
8. A computer implemented method for managing memory space in a mobile device, comprising:
storing data flies in memory;
selecting one of a plurality of memory retention algorithms for deleting sufficient data in memory to yield sufficient free memory space in the memory; and
setting a control level to provide a threshold level used by the selected memory retention algorithm to select data files for deletion according to the selected memory retention algorithm, wherein the control level is selected to set the threshold level for the selected memory retention algorithm so data files at or above the threshold level are deleted;
receiving an initial control level;
deleting one or more data files according to the initial control level and the selected memory retention algorithm;
determining if sufficient free memory space is available; and
if sufficient free memory space is not available after deleting data files according to the initial control level and the selected memory retention algorithm, then incrementing the initial control level and deleting one or more additional data files according to the incremented control level and the selected memory retention algorithm,
wherein the threshold level associated with the control level becomes progressively lower as the control level is incremented.
9. The method of claim 8, wherein the plurality of memory retention algorithms include a least recently used algorithm, a first in-first out algorithm and a largest file size algorithm.
10. The method of claim 8, further comprising:
selecting one group of control levels from a plurality of groups of control levels, wherein the control level is set from the selected group of control levels, and wherein the control level is translated to a different threshold level dependant upon the selected control level group.
11. The method of claim 10, wherein the plurality of selectable groups of control levels include a group having threshold levels relating to file size.
12. The method of claim 10, wherein the plurality of selectable groups of control levels include a group having threshold levels relating to the amount of time since a data file has been accessed.