Define tomcat 5.5.15 features
pls kindly detail the features the tomcat 5.5.15 have.
i confusing about the features and if can, pls help me define the differences between[b] tomcat 3 and tomcat 5.
cos i cant find it detail through the internet.
thanks and regards,
Lawrence
pls kindly detail the features the tomcat
5.5.15 have.
i confusing about the features and if can, pls help
me define the differences between[b]
tomcat 3 and tomcat 5.cos i cant find it detail through the internet.
thanks and regards,
Lawrence
This forum is not the correct place for questions about Tomcat. Tomcat has a site, and a mailing list. The features of each release can be seen in the documentation:
http://tomcat.apache.org/
Kaj
Similar Messages
-
JAVA_HOME var not defined , Tomcat launch error
hi Friends ,
i just installed Tomcat 4.1 on my new m/c
when i go to browser and
write http://localhost:8080/
i see the Tomcat welcome page means tomcat has been set up successfully
however when i select 'Start Tomcat' from program files , the tomcat window opens and closes in 2 seconds
and when i launch Tomcat using catalaina run command i get the msg
The JAVA_HOME environment variable is not defined correctly
This environment variable is needed to run this program
Using CATALINA_BASE: ..
Using CATALINA_HOME: ..
Using CATALINA_TMPDIR: ..\temp
Using JAVA_HOME: C:\jdk1.3\bin;
'-Dsun.io.useCanonCaches' is not recognized as an internal or external command,
operable program or batch file.
how do i resolve the isue?i Have defibed path & JAVA_HOME as
C:\Java1.4\j2sdk1.4.0-rc;
this is where ihave my jdk installed
i m still unable to resolve the issue
pls help -
Defining a Background | Adobe Muse Feature Tour | Adobe TV
Fill your background with repeating images or any image you choose. Muse will handle optimization when you publish.
http://adobe.ly/I5cS02Here is a preview of my site http://wyomingclublambs.businesscatalyst.com/index.html
I will be adding several pictures with comments on this page so it will be quite long. How do I anchor the background so that just the pictures scroll up and down?
Thanks! -
How to deploy EAR file in Tomcat?
Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
* /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
* /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation -
Email notification and SAP Script feature M0001
Hi All,
I have posted this questions in HCM forum but am posting again in ABAP forum since SAP script is related to ABAP development also. I will appreciate your help on this.
I am trying to send a notification to a distribution list whenever there is a specific Action (MASSN). I have two issues while trying to do so -
1 - I have defined the dynamic action and feature M0001 and a SAP script in SO10. I am getting the message in my inbox but with the variables from IT0000 only. In my sap script I have defined fields from IT0002/ IT0041 etc but those fields are coming as blank in my notification. Is this because I have configured dynamic action for IT0000 only. This is how my dynamic action looks like -
0000 06 1 P **SEND IF CHANGE IN MASSN -IT0000*****
0000 06 2 P T001P-MOLGA='10'
0000 06 4 P P0000-MASSN='UP'
0000 06 6 P P0000-MASSG='02'
0000 06 8 M M0001
Do I have to define these configurations for each and every infotype (that I have used in my SAP script) in table T588Z ?
2 - I want to include the position text instead of the Position no. in my notification. How can I do that? Since position text is stored in T582 table and not in P0000 or P0001.
Thank you for reading and I will appreciate your suggestions.
SanghamitraHi Kjetil,
Do you know how the problem was finally solved in your former company?
I already had a look to your post before, but for me the question is still opened. We have a corporate (non SAP) portal which users see by default when they open their browser and from where they can navigate to the SAP portal, in which we do not have single sign on.
So our users will definitely not login to the SAP Portal by themselves (nor to go to UWL, nor to display the homepage).
Maybe that an applet running on the corporate portal and doing RFC calls on the different back-ends would solve it, but I believe that might be quite a burden to develop, especially if we start talking to various non SAP systems as well. A better approach would probably be to query the portal db to look at what is in each user's UWL. But I have no idea of how the UWL data is structured in the portal and how it is updated (i.e. is the delta pull mechanism also running when a user is not logged in the portal?). I am also not sure whether there is an API in the portal to query this easily (i.e. similar to SAP_WAPI_COUT_WORKITEMS). Has anyone tried this approach before?
Cheers,
Patrick -
Netbeans 6.9.1 and bundled tomcat
I have installed a clean version of netbeans 6.9.1 bundled with tomcat and glassfish. We have moved to netbeans from eclipse. All was working fine until about a week ago. We can start tomcat fine, from within netbeans. But when it comes to restarting or stopping the tomcat server from within netbeans, netbeans attempts to stop it for about 2 minutes and then reports: Stopping of tomcat failed. This means that everytime we want to stop tomcat we have to tell netbeans to stop tomcat and then end java.exe from task manager. No config files have changed, as far as I am aware.
Any ideas are appreciated!
P.S. Tomcat is 6.0.26hi;
I am mexican and sorry for english, well lets see, there are a botton then you select a server, click on it "add" then appear alist off servers for default, down appear a textbox called Name, set tomcat 4, then click next select catalina home fo tomcat 4 and other features, most work but, I have just used it to configure firts time the tomcat 6, dont know if that works to tomcat 4.
thanks on advance
Miguel Villalobos -
Hello, I've been trying to find some information about this online but it seems there is almost nothing out there or in here.
I need to maintain an old tomcat 4 webapp (the hosting server has only that version of tomcat), but when you try to add an older version of Tomcat as a server in NetBeans, the option is not present (only 5, 5.5 and 6).
Is there any possibility to configure Tomcat 4 as a server inside the NetBeans 6.5.1 IDE??
Thanks!hi;
I am mexican and sorry for english, well lets see, there are a botton then you select a server, click on it "add" then appear alist off servers for default, down appear a textbox called Name, set tomcat 4, then click next select catalina home fo tomcat 4 and other features, most work but, I have just used it to configure firts time the tomcat 6, dont know if that works to tomcat 4.
thanks on advance
Miguel Villalobos -
Does Designer9i support new DB features from 9iR2
Hi,
I am using Designer6i and was wondering if Designer9i supports new Database features of Oracle 9iR2.
So it is possible to define the following new DB features:
- Table Compression
- List Partitioning
- Composit Range List Partitioning
- Bitmap Join Indexes
- External Tables
Thanks for any feedback
MauriceMaurice,
Designer does not support these features of the 9i database. We have no plans to add this functionality to Designer.
Please refer to the Tools Statement of Direction, the Designer maintenance release document and the related FAQ on OTN (http://otn.oracle.com/products/designer/index.html)
Regards
Sue Harper
Designer Product Management -
NetBeans 4.1, JWSDP 1.6, Tomcat 5.0-JWSDP
Hello,
I installed JWSDP 1.6 and Tomcat 5.0-JWSDP.
Then with Netbeans 4.1 created Web application with very simple WebService (by NB "wizard", name of WS was ChristmasService) and after small patch I built war succesfully.
(There is needed to specify jaxrpc-impl.jar and jaxrpc-api.jar (JWSDP distribution) into wscompile.classpath in project.properties file ).
When I now copy this war into webapps, I get next error:
Marking servlet WSServlet_ChristmasService as unavailable
Servlet /EasyWebService threw load() exception
Class my.easywebservice.ChristmasServiceImpl is not a Servlet
When I copy this war into Jboss it looks OK.
At least wsdl is displayed..
What is wrong ?
L.There are two articles, for NB 4.0:
First article:
http://www.netbeans.org/kb/articles/tutorial-webservice-40.html
It worked with Tomcat50-jwsdp. Worked fine in 4.1 too.
This is "manual" work.
Second article:
http://testwww.netbeans.org/kb/41/tutorial-webservice.html
It (possibly) worked with Sun AS but when I deploy builded WAR to Tomcat50-jwsdp
then it does not work.
Will be very nice to have document with knowledge how to deploy web application into Tomcat with new WS features in NB 4.1.
L. -
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. -
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.
-
Ann: SuperScheduler: a new member of Super 1.80
Announcement: Super 1.8 - an EJB/J2EE monitoring/admin tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperReport
SuperStress
has got a new member: SuperScheduler
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based 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/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A PeekPoke tool to read/write attributes from EJBs.
* A Stress test tool.
* A global environment tool.
* A report tool.
* A Scheduler tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1, 6.0
* Weblogic 6.1 with EJB 2.
What is new:
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.Not if they are being manually added, you could look at automating the process usIng the outlineload utility or ODI if they are classic applications.
Cheers
John
http://john-goodwin.blogspot.com/ -
Product replication from R/3 to CRM
Hi Experts,
<u>Project:</u> I'm implementing a Sales and Marketing project and the scope involves Activity, Lead & Opportunity Management
<u>Background:</u> I've successfully done all the configurations. I've also migrated all the Business Partners and Products successfully from R/3. All the customizing objects have been migrated and are in the done state. All the queues are working fine and are empty. Even the heirarchies and categories have been migrated from R/3.
<u>Problem:</u> Though the Products have been replicated from R/3 are not visible in the transaction <b>commpr01</b>.
<u>Business Impact:</u> The project is stuck due to this issue and i have missed the GoLive.
Would request all to share their expertise and rescue me out of this problem.
In Anticipation
ArvindHi
Pls go through following note, it might help you
"Before data can be transferred from the ERP material master to the product master, certain Customizing information must be transferred. Once this information has been transferred without errors, the material master records can be transferred. The data is transferred using middleware. The Customizing information transferred determines, for example, how the product ID is stored in the product master and which product data can be created.
Unless indicated otherwise, the information contained in this info object is relevant to the ERP material master for industries and to the ERP article master for retail. Retail users are requested to substitute:
● Article for material
● Merchandise category for material group
Prerequisites
If a product hierarchy is used in the ERP system:
● You have created the numbering scheme R3PRODHIER in the CRM system for the product hierarchy from the ERP system, making sure that the numbering scheme precisely corresponds to the structure for the product hierarchy in the ERP system (that is, structure PRODHS). This numbering scheme is essential for the data to be created correctly.
● The number of levels in the numbering scheme must be the same as the number of fields in structure PRODHS, and the number of digits for each level must be the same as the length of the corresponding field in structure PRODHS.
For more information, see in the Implementation Guide (IMG) Cross-Application Components ® SAP Products ®Product Category ® Define Category Numbering Schemes.
Features
The following information is transferred:
● Information for converting the ERP material number to the product ID
This is whether the material number is stored lexicographically in the ERP system and the length of the product ID in the database of the ERP system.
● ERP material groups
This information is transferred to the hierarchy R3MATCLASS.
● Information in the ERP material type that determines which data can be created for a product
This is transferred to the hierarchy R3PRODSTYP (product subtype). The hierarchy has two levels. The first level contains the categories MAT_ for materials and SRV_ for services. In the case of materials, the second level is a sublevel of MAT_ and contains the material types imported from ERP, each with the prefix MAT_. For example, the ERP material type HAWA (trading goods) is created as the category MAT_HAWA.
In addition, the SAP-defined CRM set types are assigned to the categories of the hierarchy R3PRODSTYP as follows:
○ The following set types are assigned to the category MAT_:
■ COMM_PR_MAT (basic data on materials)
■ COMM_PR_SHTEXT (description)
■ COMM_PR_UNIT (conversion of units of measure)
■ COMM_PR_LGTEXT1 (basic texts)
As a result, these set types are inherited by all material types.
○ The following set types are also assigned to the category MAT_ if the status Sales is assigned to the material type in the ERP system:
■ CRMM_PR_SALES (sales: distribution chain)
■ CRMM_PR_SALESA (sales: control fields, units of measure, and quantities)
■ CRMM_PR_SALESG (sales: groupings)
■ CRMM_PR_TAX (sales: taxes)
■ CRMM_PR_LGTEXT2 (sales: texts)
■ CRMM_PR_LGTEXT (texts)
● ERP product hierarchies
This information is transferred to the CRM hierarchy R3PRODHIER.
Activities
1. Using transaction R3AS, transfer the following middleware objects for the class CUSTOMIZING:
○ DNL_CUST_PROD0 (storage form of material numbers in sending system)
○ DNL_CUST_PROD1 (material types, material groups, and product hierarchy)
○ DNL_CUST_PROD3 (material statuses in sales and distribution)
2. Using transaction COMM_HIERARCHY, check whether the corresponding hierarchies have been created in CRM.
3. Check in Customizing for Cross-Application Components whether the storage form (lexicographical or not) is correct for the material number transferred, by choosing SAP Products ® Basic Settings ®Define Output Format and Storage Form of Product IDs.
reward points if helps
Regards
Kushal -
Ann: SuperPatrol as SuperScheduler job
Announcement: Super 1.9 - an EJB/J2EE monitoring/admin tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperReport
SuperScheduler
SuperStress
has got a new member: SuperPatrol, as a schedule job.
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based 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/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A PeekPoke tool to read/write attributes from EJBs.
* A Stress test tool.
* A global environment tool.
* A report tool.
* A Scheduler tool.
* A Business patrol tool.
It is written in pure Java.
The current version support:
* JOnAS 2.4
* Universal servers.
* Weblogic 6.0 and 6.1
* Websphere 4.0
* jBoss 2.4.4
What is new:
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 1.9 - an EJB/J2EE monitoring/admin tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperReport
SuperScheduler
SuperStress
has got a new member: SuperPatrol, as a schedule job.
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based 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/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A PeekPoke tool to read/write attributes from EJBs.
* A Stress test tool.
* A global environment tool.
* A report tool.
* A Scheduler tool.
* A Business patrol tool.
It is written in pure Java.
The current version support:
* JOnAS 2.4
* Universal servers.
* Weblogic 6.0 and 6.1
* Websphere 4.0
* jBoss 2.4.4
What is new:
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.
Maybe you are looking for
-
Report for forecast, currenct stock, sales orders, confirmed production
Follwing is the mail from user. Please confirm what are the report should I refer to to fulfill user requirement. I don't want to download the data from the tables directly. Can I please request for a report to be compiled and extracted from SAP show
-
SAP Work Manager customization - adding a new field to equipment details screen (Syclo Agentry)
Hi Experts, I am trying to add a field (NAME1) on the Equipment details screen under work orders in work manager 5.3 application. I have performed the following steps, but I am getting an error while connecting to the application. 1) Create extension
-
Need Query to that generate count of rows of all tables
Hi i need a query which gives the result of no.of rows in talbe and coresponding table name. And then i need to compare the same with other DB schema Thanks in advance
-
How to get the PERNR & TRIPNO(REINR) in T&E Webdynpro Component
Hi Experts, We are Implementing T&E Module. We are using Webdynpro ABAP to create iviews in portal. I want to know in which webdynpro component i can able to get the PERNR & TRIPNO(REINR), means if i want to create a Expense Report for a approved tra
-
Can not install CS6 Extended. Receive error that I need Adobe Air it won't install
I can not install I am running Windows 7, Service Pack 1. Installer starts but sits for hours not doing anything. I have uninstalled Adobe Air, reboot the computer and tried to install again with same error. Any suggestions? I was on hold for 2+ hrs