J2ee - EJB

Hi.. i hav my session beans deployed in my J2ee1.4 server.. and i have a standalone CORBA client.. i dont know how to access the EJB's from the CORBA client.. Pls help!!

I think the following links wil help you
http://java.sun.com/j2se/1.4.2/docs/guide/rmi-iiop/interop.html
http://www.javaworld.com/javaworld/jw-03-2002/jw-0329-corba.html
http://192.87.31.188/docs/easpg/easpg49.htm

Similar Messages

  • ERROR J2EE EJB-03027 with OC4J 10.1.3.3

    Hi,
    we have an application that works fine in iAS 9i (9.0.3).
    Now, we have to migrate the platform to 10G and we are testing with OC4J 10.1.3.3.
    But when the OC4J works... we see this message:
    2008-03-06 16:10:12.737 ERROR J2EE EJB-03027 [prueba] Se ha producido un error al desplegar el módulo EJB: java.lang.InstantiationException: Internal server error: oracle.classloader.util.AnnotatedClassFormatError (Bad version number in .class file
         Clase no válida: UPHome_EntityHomeWrapper1
         Cargador: prueba.root:0.0.0
         Origen de Código: /C:/OC4J 10.1.3.3/j2ee/home/application-deployments/prueba/MGU-1.0/deployment-cache.jar
         Configuración: <ejb> in wrappers
         Clase Dependiente: com.evermind.server.ejb.deployment.EntityBeanDescriptor
         Cargador: oc4j:10.1.3
         Origen de Código: /C:/OC4J 10.1.3.3/j2ee/home/lib/oc4j-internal.jar
         Configuración: <code-source> in META-INF/boot.xml in C:\OC4J 10.1.3.3\j2ee\home\oc4j.jar
    08/03/06 16:10:12 ADVERTENCIA: Application.setConfig Application: prueba is in failed state as initialization failed.
    java.lang.InstantiationException: Error initializing ejb-modules: Internal server error: oracle.classloader.util.AnnotatedClassFormatError (Bad version number in .class file
         Clase no válida: UPHome_EntityHomeWrapper1
         Cargador: prueba.root:0.0.0
         Origen de Código: /C:/OC4J 10.1.3.3/j2ee/home/application-deployments/prueba/MGU-1.0/deployment-cache.jar
         Configuración: <ejb> in wrappers
         Clase Dependiente: com.evermind.server.ejb.deployment.EntityBeanDescriptor
         Cargador: oc4j:10.1.3
         Origen de Código: /C:/OC4J 10.1.3.3/j2ee/home/lib/oc4j-internal.jar
         Configuración: <code-source> in META-INF/boot.xml in C:\OC4J 10.1.3.3\j2ee\home\oc4j.jar
    We have looked for information about the 'Bad version number' error, and we have recompile all our code with the JDK 1.5 (the same JDK for the OC4J). But we still have the error...
    Which may be the problem?...
    Thanks.

    The only thing you can do is to make sure that you recompile everything you're using.
    --olaf                                                                                                                                                                                           

  • Using J2EE EJB Container and Oracle 8.1.7

    I am trying to setup the J2EE EJB container to use and Oracle 8.1.7 database instead of Cloudscape. So far I have done the following
    0. Created the table for the Savings Account tutorial in the Oracle Database.
    1. Added the Classes12.jar (Oracle's latest JDBC thin drivers) to my CLASSPATH
    2. Under "Server Configuration" I added the standard/jdbc drivers value: "oracle.jdbc.driver.OracleDriver".
    3. Under "Server Configuration" I added the standard/datasource value: JNDI name "jdbc/Oracle" and JDBC URL "jdbc:oracle:thin:@10.1.1.254:1521:DEV".
    4. For the savings account tutorial, when deploying I specified "jdbc/Oracle" for the reference "jdbc/SavingsAccountDB".
    I have gotten this tutorial to work using the Cloudscape database. After I did the previous steps and tried to run the client, I get no valid driver available, unable to connect to Oracle.
    What else to I need to do?
    My setup is:
    Windows 2000 Professional
    J2EE (JDK 1.3.1)
    Oracle 8.1.7
    Thank you in advance.

    Exactly which classpath did you add the Oracle JDBC library jar to ?
    The thing that works for me is to have the following line in the file %J2EE_HOME%\bin\userconfig.bat
    set J2EE_CLASSPATH=D:\DownLoad\Oracle\classes12_01.zip;

  • Using DAO without J2EE/EJB

    Can I implement the DAO pattern in my 2-tiered application without using J2EE/EJB? My reason for using DAO is simply to insulate database changes from interface/business code and to make interface/business code easier to write.

    Sure, go ahead.

  • How do I use the J2EE EJB container with the FULL version of Tomcat

    The version of Tomcat integrated in J2EE is really cut-down. I want to be able to run the standard Tomcat 4.0.1 to give the full JSP facilities, but I also want to be able to use EJBs from the J2EE.
    If I copy the j2ee.jar, j2ee-ri-svc.jar and home interface to the "lib" directory they do not appear to be loaded, as I cannot resolve the javax.ejb.EJBHome.class.
    If I copy the same library into the application's WEB-INF/lib directory then the naming jaxax.naming.InitialContext gives a context without the java:/comp/env entries.
    I do not want to use another EJB contrainer after having got used to deploying apps with J2EE.
    If anyone can help I would be greatful, and post a thanks message with duke dollars!
    Chris
    10 Duke Dollars available

    I have done it before and basically it is not that difficult, but in practice not that easy ;-)
    All you need to do is see Tomcat as a client to the EJBs. This means deploying the application in two parts: the webapp as a WAR to Tomcat 4.0.1, and the EJBs to J2EE. Both running and started independantly.
    This ofcourse means that the WAR file must have the stubs of the EJBs to be able to communicate and access to j2ee.jar to get the InitialContext.
    So:
    - compile the EJBs
    - create the EAR (containing only EJBs)
    - deploy the EAR
    - copy the stubs to the libs directory of the webapp
    - compile the webapp
    - create the WAR
    - deploy the WAR
    Off you go.
    Tom

  • Oracle and J2EE EJB

    Hi all,
    I am novice in the develpment of applications using EJB's. I have created the table and inserted the records in the oracle database using the J2EE where by the J2EE creates the table autometically. The application is working fine. But my main concern is that I am not able to access any records of this table when I give "select * from SportscarBeanTable" querry in the sql prompt of the oracle for which I get "no such table". But if I give the querry "Select table_name from user_tables", the table created by me is displayed. Can anybody clarify my doubt. Any help will be greatly appreciated.
    deepak

    Hi,
    Yes it is listing the table. The table is created by the J2EE server in the oracle database. Can u please specify the schema under which the J2EE server creates the tables in the oracle database.
    Thank you,
    deepak

  • Compliant J2EE/EJB class file packaging...

    Hi,
    I've just come across some commerical components which are packaged slightly strangely and I'd like to find out if their approach is J2EE compliant.
    The components are EJBs which are packed into several EJB module archives (.jars) inside a main application archive (.ear). The interesting thing is, inside each EJB module .jar, they have packaged the .class files into several ordinary .jar files and added those .jars into the EJB .jar, rather than simply adding the classes to the EJB .jar itself. My question is, is this compliant?
    Are application server classloaders suppsed to automatically open such embedded .jars and make the classes available to the container at runtime? I don't think so but I have been assured by the vendor in question that this is compliant (and runs in the J2EE 1.2 RI which I havn't tested).
    There are no directives, either in the J2EE deployment descriptors or .jar Manifests which can be used to indicate that the 'inner' .jar files should be unpacked. The Class-Path Manifest attribute can be used to point to other jars using a relative URI but I don't believe it can be used to point to .jars inside the referencing .jar. (In any case, this vendor isn't using a Class-Path attribute)
    Any thoughts appreciated!
    Regards,
    John.

    >
    Nesting .jar's has always been perfectly proper, It has? I've certainly never seen anything like this in my past java programming experience. Can you give me some examples or references to the J2SE or J2EE specifications that back up this assertion?
    I believe J2SE doesn't allow you to simply place different classes in different jars, then nest those jars inside each other and expect a standard ClassLoader to be able to load the classes from the correct location at runtime. Try it, you'll see that doesn't work. I can see nothing in the J2EE spec that says that a J2EE appserver has to go looking into these nested jars.
    why
    do you believe that ejb-jar do not support this ?Quite simply because there are no references to "nesting" jars in the specification, beyond
    a) nesting J2EE modules (.jar, .war and .rar files) inside J2EE application .ear files
    and
    b) nesting required libraries in "WEB-INF/lib" location of a .war file.
    Both of these cases are explicitly defined in the specification but I don't believe there is any support for "general" nesting or Jars.

  • J2EE-EJB-Deploying an Enterprise JavaBean-deployment failure

    I am unable to deploy a simple EJB application . I am using j2skee1.3.1 and J2SDK1.4.0
    The related files and error messages are reproduced.
    The java files and ear files are in d:\myjava\ejb
    class path is .;d:\j2sdkee1.3.1\lib\j2ee.jar;D:\forte_jdk\j2sdk1.4.0\lib;d:\myjava
    j2ee_home= d:\j2sdkee1.3.1
    java_home=D:\forte_jdk\j2sdk1.4.0
    path=%SYSTEMROOT%;%SYSTEMROOT%\command;c:;d:\j2sdkee1.3.1\bin;%SYSTEMROOT%\system32;%SYSTEMROOT%\system32\WBEM;C:\Program Files\Common Files\Adaptec Shared\System;D:\forte_jdk\j2sdk1.4.0\bin;d\j2sdkee1.3.1\javaservlets;d:\MSSQL7\BINN;D:\forte_jdk\j2sdk1.4.0\bdk1_1\beans\beanbox
    Can any one suggest a solution.
    ************calculatorHome**********
    import java.io.Serializable;
    import java.rmi.RemoteException;
    import javax.ejb.CreateException;
    import javax.ejb.EJBHome;
    public interface calculatorHome extends EJBHome
         calculator create() throws RemoteException, CreateException;
    ************calculator***************
    import javax.ejb.EJBObject;
    import java.rmi.RemoteException;
    public interface calculator extends EJBObject
         public double dollorToRs (double dollars) throws RemoteException;
    **********calculatorEJB***********************
    import java.rmi.RemoteException;
    import javax.ejb.SessionBean;
    import javax.ejb.SessionContext;
    public class calculatorEJB implements SessionBean
         public double dollarToRs (double dollars)
              return dollars * 48.15;
         public calculatorEJB() {}
         public void ejbCreate() {}
         public void ejbRemove() {}
         public void ejbActivate() {}
         public void ejbPassivate() {}
         public void setSessionContext (SessionContext sc) {}
    ***********************************descriptor*************
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <display-name>newcalculatorjar</display-name>
    <enterprise-beans>
    <session>
    <display-name>calculatorEJB</display-name>
    <ejb-name>calculatorEJB</ejb-name>
    <home>calculatorHome</home>
    <remote>calculator</remote>
    <ejb-class>calculatorEJB</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Bean</transaction-type>
    <security-identity>
    <description></description>
    <use-caller-identity></use-caller-identity>
    </security-identity>
    </session>
    </enterprise-beans>
    </ejb-jar>
    ***************************error message*****
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <display-name>newcalculatorjar</display-name>
    <enterprise-beans>
    <session>
    <display-name>calculatorEJB</display-name>
    <ejb-name>calculatorEJB</ejb-name>
    <home>calculatorHome</home>
    <remote>calculator</remote>
    <ejb-class>calculatorEJB</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Bean</transaction-type>
    <security-identity>
    <description></description>
    <use-caller-identity></use-caller-identity>
    </security-identity>
    </session>
    </enterprise-beans>
    </ejb-jar>
    STATIC VERIFICATION RESULTS
         NUMBER OF FAILURES/WARNINGS/ERRORS
         # of Failures : 3
    # of Warnings : 0
         # of Errors : 0
         RESULTS FOR EJB-RELATED TESTS
         FAILED TESTS :
         Test Name : tests.ejb.intf.remoteintf.RemoteInterfaceMatchMethodArgs
         Test Assertion : Remote interface business methods have matching method arguments test
         Test Description : For [ calculatorEJB ]
    For Remote Interface [ calculator ] method [ dollorToRs ]
    Error: No corresponding business method with matching arguments was found for method [ dollorToRs ].
         Test Name : tests.ejb.intf.remoteintf.RemoteInterfaceMatchMethodException
         Test Assertion : Remote interface business methods have matching method exceptions test
         Test Description : For Remote Interface [ calculator ] method [ dollorToRs ]
    Error: No corresponding business method with matching exceptions was found for method [ dollorToRs ].
         Test Name : tests.ejb.intf.remoteintf.RemoteInterfaceMatchMethodReturn
         Test Assertion : Remote interface business methods have matching method return type test
         Test Description : For [ calculatorEJB ]
    For Remote Interface [ calculator ] method [ dollorToRs ]
    Error: No corresponding business method with matching return type was found for method [ dollorToRs ].
    Thanks in advance.
    Nagarajan

    In EJB home you have -
    public double dollorToRs (double dollars) throwsIn EJB you have -
         public double dollarToRs (double dollars)There is a spelling difference in the function name

  • J2EE EJB stateless session bean lifecycle

    Hi all,
    I've developed a stateless session bean to manage starting/stopping a JCo server.
    What should I do in order to achieve these goals:
    1. The stateless session bean should be created when the SAP J2EE server is started.
    2. The stateless session bean may NEVER 'die'.
    Thanks,
    Jeroen

    hi
    good
    1-
    go through these links, which ll give you the idea how to crea the stateless bean.
    http://edocs.bea.com/wle/ejbsamp/stateles.htm
    http://www.sitepoint.com/print/implement-first-ejbs
    2-
    http://home.tiscali.nl/illuminate/scbcd/My%20SCBCDE%20Study%20Notes%20-%204%20Session%20Bean%20Lifecycle.htm
    thanks
    mrutyun^

  • What is the best way of integrating rules to a J2EE (EJB 3) application ?

    We are working in a J2EE(EJB3) project which we plan to validate business logic using rule engine(JBoss rule). What is the best way of integrating the rule engine to the application ?
    Does rule engine good for validating a large no of data volume ? (asserted as an objects)

    I don't see a big switch construct. How about trying the following:
    Call this method from your original method by passing the resultset obtained.
    public String[] convert(ResultSet rs) {
         int col = ((ResultSetMetaData) rs.getMetaData()).getColumnCount();
         String[] record = new String[col];
         int i=0;
         while(rs.next()) {
              if(rs.wasNull()) record[i] = new String();
              else record[i] = rs.getString(i);
              i++;
         return record;
    iDriZ

  • J2ee Ejb specification 2.0

    Hi,
    The latest Specifications for EJB 2.0 available on Sun's site talks about Entity Bean - bean managed persistance in Chapter 12 (page 257 - 258), where it states that
    Bean Method bean method can
    perform operations
    -------------------------------------------------------ejbLoad/ejbStore Entity Context method :
    getEJBHome, getEJBObject,
    getcallerPrinciplal, getPrimaryKey,
    getRollBackOnly, setRollBackOnly...
    Business Method Entity Context method :
    getEJBHome, getEJBObject,
    getcallerPrinciplal,
    getPrimaryKey, getRollBackOnly,
    setRollBackOnly...
    As per the above table, getRollBackOnly and setRollBackOnly methods can be used in different bean methods and container callback methods in Entity bean - Bean-Managed Persistence.
    But as per our knowledge, the above methods can ONLY be used with Container Managed persistance beans.
    Could you help me out in clearing the above confusion?
    Thanks,
    Gauri Tendulkar
    Patni Computer Systems Ltd.
    Sr. Software Engineer.

    Hi!
    getRollBackOnly and setRollBackOnly affects transactions of this bean, and transactios are handled by the container in any case (although you may begin and end usertransactions in the bean yourself). In the deployment-descriptor you specify how transacions should be handled for this bean (TX_REQUIRED, TX_SUPPORTED, ...)
    I think even if you perform no transaction at all in the bean, you may use setRollBackOnly to mark the transaction currently open for rollback.
    Hope this helps, ciao
    Martin
    Hi,
    The latest Specifications for EJB 2.0 available on
    on Sun's site talks about Entity Bean - bean managed
    persistance in Chapter 12 (page 257 - 258), where it
    states that
    Bean Method bean method can
    perform operations
    jbLoad/ejbStore Entity Context method :
    getEJBHome,
    getEJBHome, getEJBObject,
    getcallerPrinciplal,
    getcallerPrinciplal, getPrimaryKey,
    getRollBackOnly,
    getRollBackOnly, setRollBackOnly...
    Business Method Entity Context method :
    getEJBHome,
    getEJBHome, getEJBObject,
    getcallerPrinciplal,
    getcallerPrinciplal,
    getPrimaryKey,
    getPrimaryKey, getRollBackOnly,
    setRollBackOnly...
    As per the above table, getRollBackOnly and
    setRollBackOnly methods can be used in different bean
    methods and container callback methods in Entity bean
    - Bean-Managed Persistence.
    But as per our knowledge, the above methods can ONLY
    be used with Container Managed persistance beans.
    Could you help me out in clearing the above
    confusion?
    Thanks,
    Gauri Tendulkar
    Patni Computer Systems Ltd.
    Sr. Software Engineer.

  • Any documents on Oracle J2EE/EJB NLS support

    Hi,
    Do you know where I might find more information about the NLS supporting Oracle EJB/BC4J areas?
    Michael

    Michael,
    Try the Oracle Application Server documentation on OTN at:
    http://otn.oracle.com/documentation/appserver10g.html
    There is a globalization guide for the Oracle Application Server that may have the information you are looking for.

  • Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.

              Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
              Acelet is the leader in J2EE tools area. If you google "j2ee tools",
              "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
              is at the top of the result.
              Super 4.00 comes with:
              SuperEnvironment
              SuperLogging
              SuperPeekPoke
              SuperReport
              SuperScheduler
              SuperStress
              and SuperPatrol, as a schedule job.
              The evaluation edition can be anonymously downloaded from:
              http://www.ACElet.com.
              Super is a component based monitor and administration tool
              for EJB/J2ee. It provides built-in functionality as well as
              extensions, as SuperComponents. Users can install
              SuperComponents onto it, or uninstall them from it.
              Super has the following functions:
              * A J2EE monitor.
              * A gateway to J2EE/EJB servers from different vendors.
              * A framework holding user defined SuperComponents.
              * A full-featured J2EE logging and J2EE tracing tool for centralized,
              chronological logging.
              * An EJB tool for Peeking and Poking attributes from EJBs.
              * An EJB Stress test tool.
              * A J2EE global environment tool.
              * A J2EE report tool.
              * A J2EE Scheduler tool.
              * A J2EE Business patrol tool.
              It is written entirely in the Java(TM) programming language.
              The current version support:
              * JOnAS 2.4 and 2.6
              * SunONE 7.0
              * Universal servers.
              * Weblogic 6.1, 7.0 and 8.1
              * Websphere 4.0 and 5.0.2
              * jBoss 3.0 and 3.2
              ********** What is new:
              Version 4.00 November, 2003
              Enhancement:
              1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
              (with/without proxy) protocol mode for SuperEnvironment,
              SuperLogging, SuperReport and SuperScheduler.
              2. SuperLogging 4.00: tracing can work on both live database and retired database.
              3. SuperReport 3.00: works for both live database and retired database.
              4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
              Panel.
              Bug fix:
              1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
              Version 3.00 July, 2003
              Enhancement:
              1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
              scope,
              with enhancements and bug fixes.
              2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
              password.
              Add MenuTreePanel.
              3. Improved GUI and document.
              4. Add support to WebLogic 8.1.
              Bug fix:
              1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
              2. SuperScheduler 2.0: Startup should never be reported as missed.
              3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
              Version 2.20 Jan. 2003
              Enhancement:
              1. Add desktop and start menu shortcuts for MS-Windows.
              2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
              3. SuperLogging 2.40: Add new sendAlarmEmail() method.
              4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
              direct database is not practical; Allow user to choose
              favorite logging software; Add Last day as Monthly
              repeating attribute.
              Change:
              1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
              Bug fix:
              1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
              open Environment Manager.
              2. SuperLogging client 1.52: Annoying exception thrown when you use
              JDK 1.4 (the program runs okay).
              3. SuperPeekPoke 1.61: Fix bug where input object contains
              java.lang.Double and alike.
              4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
              PatrolAlarm for SuperPatrol; Composite task with members;
              Non-scheduled run on other host; Around edges of last
              days in Monthly with holiday policy.
              Version 2.10 July 2002
              Enhancement:
              1. SuperScheduler 1.3: Add Future View to check future schedule in
              both text and Gantt-chart mode.
              2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
              activities.
              3. SuperEnvironment 1.3: uses new graphic package adding print and
              preference facilities.
              4. SuperPeekPoke 1.6: uses new graphic package adding print and
              preference facilities.
              5. SuperStress 1.21: uses new graphic package.
              Bug fix:
              1. SuperStress 1.21: fixed graphic related bugs.
              Version 2.01 June 2002
              Enhancement:
              1. Add options for Look & Feel.
              2. Preference is persistent now.
              Bug fix:
              1. Installation for WebLogic 7.0: extEnv may not be installed on the
              right place, so SuperLibrar on the server side was not loaded and
              causes other problems.
              Version 2.00 June 2002
              Enhancement:
              1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
              when any Doer causes things to change.
              2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
              3. SuperReport 1.2: Support default HTML browser for reading HTML document.
              4. Support WebLogic 7.0.
              5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
              6. SuperEnvironment 1.21: New SuperEnvironment tour.
              Bug fix:
              1. WebSphere Envoy did not always list all JNDI names.
              Version 1.90 May 2002
              Enhancement:
              1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
              2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
              effective period. Add Patrol job type as SuperPatrol.
              3. Add support for both JOnAS and jBoss.
              4. Add more elements on Report criteria.
              Change:
              1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
              and descend.
              2. New log database.
              Bug fix:
              1. Alert email should be sent once in the interval, regarding number of servers
              in the clustering.
              2. Minor bug fixes to make errors handled better on SuperLogging.
              3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
              them.
              4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
              Version 1.80 March 2002
              Enhancement:
              1. Add new component: SuperScheduler
              Bug fix:
              1. SuperLogging: Verbose should ignore class registration.
              2. SuperLogging-tracing: an exception was thrown if the java class without package
              name.
              Version 1.70 January 2002
              Enhancement:
              1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
              weblogic 6.1, need download an application).
              2. Add alias names for log threshold as new Java suggests.
              3. New component: SuperReport.
              Change:
              1. SuperLogging: Log database parameters are specified in a properties file, instead
              of EJB's deployment descriptor. It is more convenient and it avoids some potential
              problems. No change for development, easier for administration.
              Bug fix:
              1. Add Source Path Panel now accepts both directory and jar file.
              2. Bug in SuperEnvironment example (for version 1.60 only).
              Version 1.60 December 2001
              Enhancement:
              1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
              2. Add timeout parameter to logging access.
              3. New installation program with A). Easy install. B). Remote command line install.
              4. Support EJB 2.0 for Weblogic 6.1.
              5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
              was supported since version 1.5).
              Change:
              1. Poke: argument list is set at define time, not invoke time.
              2. Default log database change to server mode from web server mode, booting performance
              to 10-20 times.
              Bug fix:
              1. If the returned object is null, Peek did not handle it correctly.
              2. If the value was too big, TimeSeries chart did not handle it correctly. Now
              it can handle up to 1.0E300.
              3. Help message was difficult to access in installation program.
              4. Source code panel now both highlights and marks the line in question (before
              it was only highlight using JDK 1.2, not JDK 1.3).
              5. Delete an item on PeekPoke and add a new one generated an error.
              Version 1.50 August, 2001
              Enhancement:
              1. Source code level tracing supports EJB, JSP, java helper and other
              programs which are written in native languages (as long as you
              write correct log messages in your application).
              2. Redress supports JSP now.
              3. New installation with full help document: hope it will be easier.
              4. Support WebSphere 4.0
              Version 1.40 June, 2001
              Enhancement:
              1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
              and PieView for GlobalProperties.
              GlobalProperties is an open source program from Acelet.
              2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
              Changes:
              1. The structure of log database changed. You need delete old installation and
              install everything new.
              2. The format of time stamp of SuperLogging changed. It is not locale dependent:
              better for report utilities.
              3. Time stamp of SuperLogging added machine name: better for clustering environment.
              Bug fix:
              1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
              Style Panel may not show up.
              Version 1.30 May, 2001
              Enhancement:
              1. Add ConnectionPlugin support.
              2. Add support for Borland AppServer.
              Version 1.20 April, 2001
              Enhancement:
              1. Redress with option to save a backup file
              2. More data validation on Dump Panel.
              3. Add uninstall for Super itself.
              4. Add Log Database Panel for changing the log database parameters.
              5. Register Class: you can type in name or browse on file system.
              6. New tour with new examples.
              Bug fix:
              1. Redress: save file may fail.
              2. Install Bean: some may fail due to missing manifest file. Now, it is treated
              as foreign beans.
              3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
              on the original file, do not need copy to a temporary directory anymore.
              4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
              Now it pick up all availble ones and give warning messages.
              5. Stress: Launch>Save>Cancel generated a null pointer exception.
              Changes:
              1. installLogDatabase has been changed from .zip file to .jar file.
              2. SuperLogging: If the log database is broken, the log methods will not try to
              access the log database. It is consistent with the document now.
              3. SuperLogging will not read system properties now. You can put log database
              parameters in SuperLoggingEJB's deployment descriptor.
              Version 1.10 Feb., 2001
              Enhancement:
              1. Re-written PeekPoke with Save/Restore functions.
              2. New SuperComponent: SuperStress for stress test.
              3. Set a mark at the highlighted line on<font size=+0> the Source Code
              Panel (as a work-a-round for JDK 1.3).</font>
              4. Add support for WebLogic 6.0
              Bug fix:
              1. Uninstall bean does physically delete the jar file now.
              2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
              Version 1.00 Oct., 2000
              Enhancement:
              1. Support Universal server (virtual all EJB servers).
              2. Add Lost and Found for JNDI names, in case you need it.
              3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
              for Envoys which do not support JNDI list).
              Version 0.90: Sept, 2000
              Enhancement:
              1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
              and alike) as input values.
              2. Reworked help documents.
              Bug fix:
              1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
              further time-out.
              2. MDI related bugs under JDK 1.3.
              Version 0.80: Aug, 2000
              Enhancement:
              1. With full-featured SuperLogging.
              Version 0.72: July, 2000
              Bug fix:
              1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
              Version 0.71: July, 2000
              Enhancement:
              1. Re-worked peek algorithm, doing better for concurent use.
              2. Add cacellable Wait dialog, showing Super is busy.
              3. Add Stop button on Peek Panel.
              4. Add undeploy example button.
              Bug fix:
              1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
              1.2 and 1.3
              Version 0.70: July, 2000
              Enhancement:
              1. PeekPoke EJBs without programming.
              Bug fix:
              1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
              Changes:
              1. All changes are backward compatible, but you may need to recompile monitor
              windows defined by you.
              Version 0.61: June, 2000
              Bug fix:
              1. First time if you choose BUFFER as logging device, message will not show.
              2. Fixed LoggingPanel related bugs.
              Version 0.60: May, 2000
              Enhancement:
              1. Add DATABASE as a logging device for persistent logging message.
              2. Made alertInterval configurable.
              3. Made pace for tracing configurable.
              Bug fix:
              1. Fixed many bugs.
              Version 0.51, 0.52 and 0.53: April, 2000
              Enhancement:
              1. Add support to Weblogic 5.1 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Context sensitive help is available for most of windows: press F1.
              2. Fix installation related problems.
              Version 0.50: April, 2000
              Enhancement:
              1. Use JavaHelp for help system.
              2. Add shutdown functionality for J2EE.
              3. Add support to Weblogic 4.5 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Better exception handling for null Application.
              Version 0.40: March, 2000
              Enhancement:
              1.New installation program, solves installation related problems.
              2. Installation deploys AceletSuperApp application.
              3. Add deploy/undeploy facilities.
              4. Add EJB and application lists.
              Change:
              1.SimpleMonitorInterface: now more simple.
              Version 0.30: January, 2000
              Enhancement:
              1. Add realm support to J2EE
              2. Come with installation program: you just install what you want
              the first time you run Super.
              Version 0.20: January, 2000
              Enhancement:
              Add support to J2EE Sun-RI.
              Change:
              1. Replace logging device "file" with "buffer" to be
              compliant to EJB 1.1. Your code do not need to change.
              Version 0.10: December, 1999
              Enhancement:
              1. provide SimpleMonitorInterface, so GUI experience is
              not necessary for developing most monitoring applications.
              2. Sortable table for table based windows by mouse
              click (left or right).
              Version 0.01 November., 1999:
              1. Bug fix: An exception thrown when log file is large.
              2. Enhancement: Add tour section in Help information.
              Version 0.00: October, 1999
              Thanks.
              

  • Announcement: Super 5.10 - a suite of J2EE tools

    Announcement: Super 5.10 - a suite of J2EE tools.
    Super 5.10 comes with:
    SuperEnvironment
    SuperLogging
    SuperPeekPoke
    SuperReport
    SuperScheduler
    SuperStress
    SuperWatchdog
    and SuperPatrol, as a schedule job.
    The evaluation edition can be anonymously downloaded from:
    http://www.ACElet.com.
    Super is a component based monitor and administration tool
    for EJB/J2ee. It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE monitor.
    * A gateway to J2EE/EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A full-featured J2EE logging and J2EE tracing tool for centralized,
    chronological logging.
    * An EJB tool for Peeking and Poking attributes from EJBs.
    * An EJB Stress test tool.
    * A J2EE global environment tool.
    * A J2EE report tool.
    * A J2EE Scheduler tool.
    * A J2EE Business patrol tool.
    It is written entirely in the Java(TM) programming language.
    The current version support:
    * JOnAS 2.4 and 2.6
    * SunONE 7.0
    * Universal servers.
    * Weblogic 6.1, 7.0 and 8.1
    * Websphere 4.0, 5.0.2 and 5.1
    * jBoss 3.0 and 3.2
    ********** What is new:
    Version 5.10 January, 2004
    Enhancement:
    1. SuperScheduler 4.1: Multiple holiday set is an advanced feature now.
    This arrangement is convenient for most of users.
    2. Support WebSphere 5.1.
    Change:
    1. SuperScheduler 4.1: Repeating "At specified times" changes from "all
    things considered" algorithm to POSIX cron compatible implementation.
    Bug fix:
    1. SuperScheduler 4.1: Repeating Daily did not consider "Day time saving",
    so there were one hour shift in April and October.
    Version 5.00 January, 2004
    Enhancement:
    1. SuperScheduler 4.00: Rewritten SuperScheduler with bug fixes and enhancements,
    including: 1. Add task duration. 2. Add Email, JMS Queue and Topic jobs.
    3. Add Retry tasks. 4. Add GUI version of Unix cron repeating.
    5. Rewritten holiday facilities.
    2. SuperWatchdog 1.00 with File, JMS Queue, JMS Topic and User triggers and
    the same group of actions as SuperScheduler.
    3. SuperLogigng 4.01: Improved Alarm/Alert GUI.
    Version 4.00 November, 2003
    Enhancement:
    1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
    (with/without proxy) protocol mode for SuperEnvironment,
    SuperLogging, SuperReport and SuperScheduler.
    2. SuperLogging 4.00: tracing can work on both live database and retired database.
    3. SuperReport 3.00: works for both live database and retired database.
    4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
    Panel.
    Bug fix:
    1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
    Version 3.00 July, 2003
    Enhancement:
    1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
    scope,
    with enhancements and bug fixes.
    2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
    password.
    Add MenuTreePanel.
    3. Improved GUI and document.
    4. Add support to WebLogic 8.1.
    Bug fix:
    1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
    2. SuperScheduler 2.0: Startup should never be reported as missed.
    3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
    Version 2.20 Jan. 2003
    Enhancement:
    1. Add desktop and start menu shortcuts for MS-Windows.
    2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
    3. SuperLogging 2.40: Add new sendAlarmEmail() method.
    4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
    direct database is not practical; Allow user to choose
    favorite logging software; Add Last day as Monthly
    repeating attribute.
    Change:
    1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
    Bug fix:
    1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
    open Environment Manager.
    2. SuperLogging client 1.52: Annoying exception thrown when you use
    JDK 1.4 (the program runs okay).
    3. SuperPeekPoke 1.61: Fix bug where input object contains
    java.lang.Double and alike.
    4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
    PatrolAlarm for SuperPatrol; Composite task with members;
    Non-scheduled run on other host; Around edges of last
    days in Monthly with holiday policy.
    Version 2.10 July 2002
    Enhancement:
    1. SuperScheduler 1.3: Add Future View to check future schedule in
    both text and Gantt-chart mode.
    2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
    activities.
    3. SuperEnvironment 1.3: uses new graphic package adding print and
    preference facilities.
    4. SuperPeekPoke 1.6: uses new graphic package adding print and
    preference facilities.
    5. SuperStress 1.21: uses new graphic package.
    Bug fix:
    1. SuperStress 1.21: fixed graphic related bugs.
    Version 2.01 June 2002
    Enhancement:
    1. Add options for Look & Feel.
    2. Preference is persistent now.
    Bug fix:
    1. Installation for WebLogic 7.0: extEnv may not be installed on the
    right place, so SuperLibrar on the server side was not loaded and
    causes other problems.
    Version 2.00 June 2002
    Enhancement:
    1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
    when any Doer causes things to change.
    2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
    3. SuperReport 1.2: Support default HTML browser for reading HTML document.
    4. Support WebLogic 7.0.
    5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
    6. SuperEnvironment 1.21: New SuperEnvironment tour.
    Bug fix:
    1. WebSphere Envoy did not always list all JNDI names.
    Version 1.90 May 2002
    Enhancement:
    1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
    2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
    effective period. Add Patrol job type as SuperPatrol.
    3. Add support for both JOnAS and jBoss.
    4. Add more elements on Report criteria.
    Change:
    1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
    and descend.
    2. New log database.
    Bug fix:
    1. Alert email should be sent once in the interval, regarding number of servers
    in the clustering.
    2. Minor bug fixes to make errors handled better on SuperLogging.
    3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
    them.
    4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
    Version 1.80 March 2002
    Enhancement:
    1. Add new component: SuperScheduler
    Bug fix:
    1. SuperLogging: Verbose should ignore class registration.
    2. SuperLogging-tracing: an exception was thrown if the java class without package
    name.
    Version 1.70 January 2002
    Enhancement:
    1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
    weblogic 6.1, need download an application).
    2. Add alias names for log threshold as new Java suggests.
    3. New component: SuperReport.
    Change:
    1. SuperLogging: Log database parameters are specified in a properties file, instead
    of EJB's deployment descriptor. It is more convenient and it avoids some potential
    problems. No change for development, easier for administration.
    Bug fix:
    1. Add Source Path Panel now accepts both directory and jar file.
    2. Bug in SuperEnvironment example (for version 1.60 only).
    Version 1.60 December 2001
    Enhancement:
    1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
    2. Add timeout parameter to logging access.
    3. New installation program with A). Easy install. B). Remote command line install.
    4. Support EJB 2.0 for Weblogic 6.1.
    5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
    was supported since version 1.5).
    Change:
    1. Poke: argument list is set at define time, not invoke time.
    2. Default log database change to server mode from web server mode, booting performance
    to 10-20 times.
    Bug fix:
    1. If the returned object is null, Peek did not handle it correctly.
    2. If the value was too big, TimeSeries chart did not handle it correctly. Now
    it can handle up to 1.0E300.
    3. Help message was difficult to access in installation program.
    4. Source code panel now both highlights and marks the line in question (before
    it was only highlight using JDK 1.2, not JDK 1.3).
    5. Delete an item on PeekPoke and add a new one generated an error.
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
    and PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
    Changes:
    1. The structure of log database changed. You need delete old installation and
    install everything new.
    2. The format of time stamp of SuperLogging changed. It is not locale dependent:
    better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clustering environment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
    Style Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, it is treated
    as foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
    on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
    Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods will not try to
    access the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put log database
    parameters in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
    for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
    1.2 and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompile monitor
    windows defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message will not show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: press F1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

    i use the adobe creative suite (indesign) for all print
    documentation...i use captivate for online tutorials, but from what
    i'm hearing the captivate team has been disbanded by adobe and
    they've outsourced the 'development' of future releases to india.
    buyer beware.

  • Super 5.40 - a suite of J2EE tools. It is free.

    Announcement:
    Super 5.40 - a suite of J2EE tools. It is free.
    Standard license can be freely anonymously downloaded.
    Super 5.40 comes with:
    SuperEnvironment
    SuperLogging
    SuperPeekPoke
    SuperReport
    SuperScheduler
    SuperStress
    SuperWatchdog
    and SuperPatrol, as a schedule job.
    Most of enhancements of this release are for
    SuperScheduler at http://www.acelet.com/super/SuperScheduler/index.html
    SuperWatchdog at http://www.acelet.com/super/SuperWatchdog/index.html
    Super is a component based monitor and administration tool
    for EJB/J2ee. It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE monitor.
    * A gateway to J2EE/EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A full-featured J2EE logging and J2EE tracing tool for centralized,
    chronological logging.
    * An EJB tool for Peeking and Poking attributes from EJBs.
    * An EJB Stress test tool.
    * A J2EE global environment tool.
    * A J2EE report tool.
    * A J2EE Scheduler tool.
    * A J2EE Business patrol tool.
    It is written entirely in the Java(TM) programming language.
    The current version support:
    * Universal servers.
    * Weblogic 8.1
    * Websphere 5
    It can be anonymously downloaded from:
    http://www.ACElet.com.
    ********** What is new:
    Version 5.40 Aug., 2004
    1. SuperScheduler 4.40 and SuperWatchdog 1.40: Add new tasks and chores:
    scp (Secure CoPy) and ssh (Secure SHell).
    2. SuperWatchdog 1.40: fixed bug for slow grow file trigger.
    3. SuperLogging 4.11: Add timeout for LogAgent; bug fix: Attribute did
    not show correct values for the first call.
    4. SuperArch 2.00: Add Deployment and ServerShutdown.
    5. Introduce SuperEjbGateway to replace SuperServlets.
    Version 5.31 Aug, 2004
    1. Bug fix: Triggering missing for SuperWatchdog.
    2. Bug fix: Websphere 5.1 license did not working due to new IBM java.
    Version 5.30 May, 2004
    1. Provides Auto login and Hibernation features with SuperEnvironment 3.1,
    SuperPeekPoke 2.1, SuperScheduler 4.30 and SuperWatchdog 1.30.
    2. SuperLogging 4.1: Add timeout for client site logging facility LogAgent.
    3. SuperScheduler 4.30 and SuperWatchdog 1.30: Add new Deploy (deploy,
    redeploy, start, stop, undeploy, ...) jobs.
    4. Bug fixes.
    Version 5.20 February, 2004
    1. Both SuperScheduler 4.20 and SuperWatchdog 1.20 use own alarm facilities.
    2. SuperScheduler 4.20: Bug fix: in some conditions, nextRunTime may equals
    to lastRunTime and the task will not run anymore (for HypersonicSQL
    database only, we did not find this problem for Oracle, nor DB2).
    3. SuperLogging 4.02: With better error handling; better Alert/Alarm Email.
    Version 5.10 January, 2004
    Enhancement:
    1. SuperScheduler 4.1: Multiple holiday set is an advanced feature now.
    This arrangement is convenient for most of users.
    2. Support WebSphere 5.1.
    Change:
    1. SuperScheduler 4.1: Repeating "At specified times" changes from "all
    things considered" algorithm to POSIX cron compatible implementation.
    Bug fix:
    1. SuperScheduler 4.1: Repeating Daily did not consider "Day time saving",
    so there were one hour shift in April and October.
    Version 5.00 January, 2004
    Enhancement:
    1. SuperScheduler 4.00: Rewritten SuperScheduler with bug fixes and enhancements,
    including: 1. Add task duration. 2. Add Email, JMS Queue and Topic jobs.
    3. Add Retry tasks. 4. Add GUI version of Unix cron repeating.
    5. Rewritten holiday facilities.
    2. SuperWatchdog 1.00 with File, JMS Queue, JMS Topic and User triggers and
    the same group of actions as SuperScheduler.
    3. SuperLogigng 4.01: Improved Alarm/Alert GUI.
    Version 4.00 November, 2003
    Enhancement:
    1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
    (with/without proxy) protocol mode for SuperEnvironment,
    SuperLogging, SuperReport and SuperScheduler.
    2. SuperLogging 4.00: tracing can work on both live database and retired database.
    3. SuperReport 3.00: works for both live database and retired database.
    4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table Panel.
    Bug fix:
    1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
    Version 3.00 July, 2003
    Enhancement:
    1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart" scope,
    with enhancements and bug fixes.
    2. SuperLoggingLibrary 3.00: Support mail server which requires user name and password.
    Add MenuTreePanel.
    3. Improved GUI and document.
    4. Add support to WebLogic 8.1.
    Bug fix:
    1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
    2. SuperScheduler 2.0: Startup should never be reported as missed.
    3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
    Version 2.20 Jan. 2003
    Enhancement:
    1. Add desktop and start menu shortcuts for MS-Windows.
    2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
    3. SuperLogging 2.40: Add new sendAlarmEmail() method.
    4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
    direct database is not practical; Allow user to choose
    favorite logging software; Add Last day as Monthly
    repeating attribute.
    Change:
    1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
    Bug fix:
    1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
    open Environment Manager.
    2. SuperLogging client 1.52: Annoying exception thrown when you use
    JDK 1.4 (the program runs okay).
    3. SuperPeekPoke 1.61: Fix bug where input object contains
    java.lang.Double and alike.
    4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
    PatrolAlarm for SuperPatrol; Composite task with members;
    Non-scheduled run on other host; Around edges of last
    days in Monthly with holiday policy.
    Version 2.10 July 2002
    Enhancement:
    1. SuperScheduler 1.3: Add Future View to check future schedule in
    both text and Gantt-chart mode.
    2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
    activities.
    3. SuperEnvironment 1.3: uses new graphic package adding print and
    preference facilities.
    4. SuperPeekPoke 1.6: uses new graphic package adding print and
    preference facilities.
    5. SuperStress 1.21: uses new graphic package.
    Bug fix:
    1. SuperStress 1.21: fixed graphic related bugs.
    Version 2.01 June 2002
    Enhancement:
    1. Add options for Look & Feel.
    2. Preference is persistent now.
    Bug fix:
    1. Installation for WebLogic 7.0: extEnv may not be installed on the
    right place, so SuperLibrar on the server side was not loaded and
    causes other problems.
    Version 2.00 June 2002
    Enhancement:
    1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
    when any Doer causes things to change.
    2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
    3. SuperReport 1.2: Support default HTML browser for reading HTML document.
    4. Support WebLogic 7.0.
    5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
    6. SuperEnvironment 1.21: New SuperEnvironment tour.
    Bug fix:
    1. WebSphere Envoy did not always list all JNDI names.
    Version 1.90 May 2002
    Enhancement:
    1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
    2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy, effective period. Add Patrol job type as SuperPatrol.
    3. Add support for both JOnAS and jBoss.
    4. Add more elements on Report criteria.
    Change:
    1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend and descend.
    2. New log database.
    Bug fix:
    1. Alert email should be sent once in the interval, regarding number of servers in the clustering.
    2. Minor bug fixes to make errors handled better on SuperLogging.
    3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save them.
    4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
    Version 1.80 March 2002
    Enhancement:
    1. Add new component: SuperScheduler
    Bug fix:
    1. SuperLogging: Verbose should ignore class registration.
    2. SuperLogging-tracing: an exception was thrown if the java class without package name.
    Version 1.70 January 2002
    Enhancement:
    1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for weblogic 6.1, need download an application).
    2. Add alias names for log threshold as new Java suggests.
    3. New component: SuperReport.
    Change:
    1. SuperLogging: Log database parameters are specified in a properties file, instead of EJB's deployment descriptor. It is more convenient and it avoids some potential problems. No change for development, easier for administration.
    Bug fix:
    1. Add Source Path Panel now accepts both directory and jar file.
    2. Bug in SuperEnvironment example (for version 1.60 only).
    Version 1.60 December 2001
    Enhancement:
    1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
    2. Add timeout parameter to logging access.
    3. New installation program with A). Easy install. B). Remote command line install.
    4. Support EJB 2.0 for Weblogic 6.1.
    5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging was supported since version 1.5).
    Change:
    1. Poke: argument list is set at define time, not invoke time.
    2. Default log database change to server mode from web server mode, booting performance to 10-20 times.
    Bug fix:
    1. If the returned object is null, Peek did not handle it correctly.
    2. If the value was too big, TimeSeries chart did not handle it correctly. Now it can handle up to 1.0E300.
    3. Help message was difficult to access in installation program.
    4. Source code panel now both highlights and marks the line in question (before it was only highlight using JDK 1.2, not JDK 1.3).
    5. Delete an item on PeekPoke and add a new one generated an error.
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView and PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
    Changes:
    1. The structure of log database changed. You need delete old installation and install everything new.
    2. The format of time stamp of SuperLogging changed. It is not locale dependent: better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clustering environment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and Style Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, it is treated as foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabase can be worked on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6. Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods will not try to access the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put log database parameters in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both 1.2 and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompile monitor windows defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message will not show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: press F1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

    Adrain,
    Its a very good thought and reorganisation might help most of them with their critical issues in 2004s.Its not that the critical issues are not taken care off in the present system but definetly the new names might bring in more attraction and meaning.
    I would vote for renaming.
    thanks.

Maybe you are looking for

  • How  to import raw files from canon550D into PSE9 ?

    I have just purchased PSE9. I have downloaded Camera Raw 5.7 and 6.2 update and installed both...but still I cannot see/open my raw files from canon 550D - any suggestions...??

  • Multiple process start with terminal?

    How do I open multiple programs at one? I need it to open an executable, leave it running, open another executable. I'm not sure how to do this branch thing in the terminal I want to use this for an .sh script Last edited by caelestis (2009-04-29 22:

  • Capturing DVD On FCE-HD

    I'm trying to capture self generated DVD video into FCE-HD. In "Easy Setup" which category should I choose? DV-NTSC? I'm attempting to ingest the DVD video out of my DVD player in my MacBook. Thanks. MacBook   Mac OS X (10.4.9)  

  • Clob or XML

    Hello, I need to store product specifications and definitions to display on the internet. These definitions are very long and detailed. Moreover, they include imagery. I need to develop queries on these products, too. Should I store all the descripti

  • How I use swf in swf (nested) ?

    Flash is case-sensitive in naming(symbols,form fields,components) ? How I use ScrollPane ? How I use swf in swf (nested) ?