Welcome to the Lutris EAS CIMOM Service Technology Preview!
The Lutris EAS CIMOM Service is a platform service that adds CIMOM (Common Information Model Object Manager) capabilities to Lutris EAS. For the CIMOM Tech Preview, Lutris is incorporating code from the http://wbemservices.sourceforge.net/ project, as well as code from the http://www.snia.org/ CIMOM project, whose original contributor is a Lutris employee. The original source is available from these respective web sites, and the most restrictive license for the source is covered by the Sun Industry Standards Source License - Version 1.2 license (see http://wbemservices.sourceforge.net/sissl_1-2.html).
The CIMOM runs as a daemon thread inside Lutris EAS. This allows the CIMOM to take advantage of all the capabilities that EAS provides, such as Logging, Security, JNDI namespace, and Management. The CIMOM Service uses the Lutris EAS logging capabilities to provide consolidated display of results and status information. It uses the EAS JAAS (Java Authentication and Authorization Service) API to provide user authentication via a pluggable datastore. Management is provided using the JMX (Java Management Extensions) API through MBeans (Management Beans).
This service essentially provides a wrapper around the CIMOM. Fewer than 50 lines of code in the CIMOM itself have been changed to allow the CIMOM to function optimally inside of EAS. Essentially, all the CIMOM functionality is unchanged. One goal of this project was to import the CIMOM code with as few changes to it as possible. That said, the CIMOM brings with it bugs that were not addressed by Lutris, and it is provided "as is."
The main changes made to the source were to change the directory paths that the CIMOM uses to be more flexible instead of being hard-coded.
More information on why Lutris EAS should be used with CIMOM can be found in the technology brief Lutris EAS as a WBEM platform.
Note: As with all field test software, the CIMOM Service Technology Preview is not production quality. It's licensed for field test use only and it shouldn't be used in a production environment.
Getting Started
To provide an overview of the Lutris EAS CIMOM Service. To use the CIMOM Service, install it using ant as described in the 'doc/install.txt' file)
- Install the CIMOM service.
- Run the CIM Workshop client application.
- Login from the client to the CIMOM host using the HTTP protocol.
- Manipulate the objects viewed through the CIM Workshop client.
Future Enhancements
Potential future enhancements for the CIMOM Service. (Please provide feedback on which are most important for you.)
- Provide thread and socket resource management via EAS's thread and socket services.
- Provide more sophisticated CIMOM management.
- Provide more fine-grained logging (since the CIMOM itself does this rather crudely).
- Provide clean shutdown of the CIMOM.
- Fix bugs in the CIMOM.
Discussion
The CIMOM code itself has several requirements on the environment in which it runs. First, it reads and creates files in specific directories. The ANT installation script creates these files and directories in the "cim" subdirectory in the user's home directory. This home directory is determined via the Java call to System.getProperty("user.home"). Second, the CIMOM uses the IDBUserRegistry service to perform its JAAS authorization of users. This service is installed using the ANT installation script as well. It ha been altered very slightly but the original source code for this service is under <EAS Home>/examples/IDBUserRegistry. This service creates an InstantDB database to provide the persistence for its JAAS authentication implementation. Finally, related to JAAS, the CIMOM installation instructions describe the creation of a "realm" inside of EAS, within which the IDBUserRegistry service performs JAAS-based authorization. If this realm has not been created properly, the user will not be able to log in to the CIMOM and will receive error messages that say "user is not guest" in the log output inside EAS.
We are especially interested in these areas for your feedback:
- How you are or would like to use the CIMOM Service
- Functionality of existing capabilities
- Specific management capabilities you would like to see
- Favorite items from the 'Future Enhancements' section
- General comments and suggestions
The Lutris EAS CIMOM Service requires Lutris EAS to be pre-installed on your system and has been tested to work on Windows 2000, Solaris, and Linux machines.
Installation
Refer to the doc/install.txt file for installation instructions.
How to undeploy
From the command line:
- 'undeploy CIMOM-Service'
- 'undeploy IDBUserRegistry'
From the Lutris Management Console (LMC):
- Select the 'Deployer Tab'
- Expand the entry for the desired server
- Select 'Services'
- Select 'CIMOM-Service'
- From the menu, select 'Tools | Deployer | Undeploy Object'
- Select 'IDBUserRegistry'
- From the menu, select 'Tools | Deployer | Undeploy Object'
This section summarizes common issues with this release and any available workarounds.
Issue Workaround If there is an error during login,
there is a bug in the CIM client code in that it will never discard a username and password once they are provided, even if login is attempted.In this release, The only workaround is to stop and restart the client. The EAS server can remain running since the CIMOM server code is working properly. When logging into the CIMOM it is also normal to see a stack trace in the log output like:
2001.11.08 21:26:02: stderr,ERROR: CIM_ERR_NOT_FOUND:
2001.11.08 21:26:02: stderr,ERROR+ test
2001.11.08 21:26:02: stderr,ERROR: at
com.sun.wbem.cimom.CIMOMImpl.getClass(CIMOMImpl.java:830)
2001.11.08 21:26:02: stderr,ERROR: at
com.sun.wbem.cimom.adapters.client.http.CIMOMXMLImpl.getClass(CIMOMXMLImpl.java:557)This is normal. It occurs upon successful login from the CIMWorkshop client and is not a fatal error in the CIMOM. The CIMOM Service is not displayed in LMC Browser under 'By Type|Services'. On some systems, one needs to refresh the MBeans (Server|Refresh Server|<server name>) in order for the service MBean to be displayed. Choosing Help | About crashes in the CIM Workshop client program. Don't choose the help feature. The help is available in HTML format with the distribution on disk at <cimom_root>\client\help\cimworkshop\default The CIMOM service is pre-release and does not include clean shutdown of the CIMOM. The CIMOM code itself is structured such that there is no central programmatic way to stop the CIMOM server without killing the process directly via a System.exit() call. The System.exit() code has been excised since this would kill the whole EAS process itself. The upshot is that, even if you undeploy the CIMOM service in EAS, the CIMOM will still be running, although it is not manageable in LMC anymore. The CIMOM listens on port 5988, which you can see on Windows using "netstat -a" and on Linux using "netstat -l". Since there is no way to stop the CIMOM, EAS will need to be restarted if you want to redeploy the CIMOM. None at this time. The CIMOM needs to be undeployed and EAS then needs to be restarted before replying the CIMOM.
We encourage you to submit feedback/bugs and ask questions concerning your experience with the Lutris EAS product and documentation. You can post questions and participate in the Lutris EAS email Forum by sending email to the lutriseas@eas.lutris.com mailing list. You can browse the Lutris EAS email Forum at http://www.lutris.com/lutrisEASmail/lutriseas/maillist.html.
Note: You must first subscribe to the mailing list before posting. To subscribe, send email to mailto:majordomo@eas.lutris.com?subject=subscribe&body=subscribe lutriseas with '
subscribe lutriseas'
in the body of the email message (automatically added if you click the preceding mailto link).If you believe that you have encountered a defect in the product, please follow these guidelines:
- Before posting your problem report, please review the Known problems and workarounds section in the Release Notes and mailing list archives to see if your problem has already been reported along with a solution or workaround.
- Submit your bug report to lutriseas@eas.lutris.com. Please include your operating system and JDK versions as well as detailed steps necessary to reproduce the problem.
Note: Bug reports that cannot be reproduced by Lutris will not be reviewed by Lutris Engineering.
Copyright © 2001 by Lutris Technologies Inc. All rights reserved.