README for the Java(TM) 2 Platform, Enterprise Edition (J2EE(TM)) Management Reference Implementation (RI), Version 1.0 Revised: June 21, 2002 Overview -------- The J2EE Management Reference Implementation, Version 1.0 integrates the the management functionality proposed by JSR-77 into the Sun ONE Studio Community Edition 3.0 product using the Open API model provided by Netbeans(TM)/Forte. The goal of this Reference Implementation (RI) is to provide a tool for managing any J2EE application on any J2EE server that has implemented the J2EE Management interfaces. Starting the J2EE Management RI ------------------------------- To start the J2EE Management RI, go to the bin directory immediately below the current directory and enter the command runide.exe (on Windows) runide.sh (on Solaris or Linux) NOTE: Do *not* accept the automatic IDE updates when running the J2EE Management RI. Click No in this dialog box. After the IDE starts, you will see several new menu items that are related to J2EE Management -- File->Connect to J2EE Management Server, for example. Documentation ------------- There is online help on how to use the features of this RI. After you start the RI, choose Help Sets->JSR77-JSR88 J2EE IDE Toolkit Software Help from the Help menu. The online help also contains 3 tutorials on distributing, starting, and managing a J2EE application: one for an application consisting only of an enterprise bean and an application client, another more complete application consisting of an enterprise bean and web components, and another exercise that illustrates managing a J2EE application. Comments -------- We welcome your comments and suggestions regarding this RI. Please send them to j2ee-management-comments@sun.com. Known Problems List ------------------- Here is the list of known problems with the RI. We have also listed workarounds if they are available. Since this RI is dependent on Forte CE, you may encounter other known problems that pertain to that tool. We'll try to let you know if a problem you report falls into that category. 1. SQL will not be generated properly for entity beans that are defined in a one-to-one relationship when either bean's "prim-key-class" value is defined to be anything other than "java.lang.Object." This issue has been reported as Bug ID 4706419. 2. If you see the error message "java.lang.NoClassDefFoundError: com/sun/tools/javac/Main" when you distribute an application, the JAVA_HOME variable is pointing to a J2SE JRE directory, not a J2SE SDK directory, as it should be. This module requires the JAVA_HOME variable to point to a J2SE SDK directory to resolve all library JAR file references. 3. The $ffjuser30/system/DeployObjTemp directory doesn't always get properly cleaned up. Extraneous files that result from the processing of EAR files during runtime should be removed when the Forte IDE is shut down, but some META-INF files remain. After you shut down the IDE, you can safely remove these files. 4. If you try to undeploy an application that consists of multiple modules when the Management Server and the Deployment Manager are connected, you may see an InstanceNotFoundException in the terminal window in which the J2EE server was started. Ignore this exception. The Management node refreshes itself and the view may not reflect the right view. Refresh either "DeployedObjects" node or the Management node. This issue has been reported as Bug ID 4703883. 5. After you install Forte for Java, CE, the sampledir directory is already mounted. The directory contains an EJB.jar file. If you go through Tutorial #1 and mount the j2ee_samples directory after previously opening the sampledir directory, you will be prompted to update the EJB.jar file from disk when you expand the j2ee_samples directory. When you are prompted, you should respond "Yes" and update the file. If you say "No" and don't update the file from disk, you will see a bad node structure for the EJB.jar file. The workaround for this problem is to unmount the j2ee_samples directory, then remount the j2ee_samples directory. When you are then asked about updating from disk, answer "Yes" to restore the file from disk. 6. If you are restoring a deployment plan from an earlier version of the sun-j2ee-ri.xml file, you may notice that some of the information for Web modules is missing. For example, some details, like the JNDI name for resource references, might be blank. Once you fill in these empty fields and save, you should see the information the next time you try to restore from the saved file. 7. The Forte IDE will not let you blank out the EJB bundle name. If you try to set it to "", the IDE will always resets the value back to "Ejb1" to ensure that the EJB name is always set. 8. If you unmount a directory using Forte's "Unmount directory" action, you will lose the deployment settings node view from any applications for which you have created deployment settings. Use the "Restore from File" action to reattach the node view with the deployment settings appropriately attached. 9. If you enter any value for the context root in an Inspector window, which is open to inspect an Application node, that value will take precedence over the context root value that has been entered in the deployment settings for the Web module. In order for the value that was entered in the deployment settings to take effect, the context root field in the Inspector window should be kept empty. 10. Occasionally, while distributing, starting, or stopping simple modules, the Progress dialog does not display any messages. This can occur if a simple module is distributed or started before the progress dialog can be shown. If this occurs, close the window and refresh the Deployment Factory node to see the changes. 11. Managed objects are not created for resources, which have been added using the Server Configuration option under the Tools menu, until the server is restarted. This issue has been reported as Bug ID 4696408. ----