Edition March 2002 -J2ME IN A NUTSHELL-O'Reilly
I have book
J2ME IN A NUTSHELL
Publisher:O'Reilly
Edition March 2002
Can this book help me to develop Android apps (or games) or is necessary to bye new book?
I like book from this format.please suggest me some book to learn
Java
Android SDK 2.2+
Unit Test Framework
I am most intrested to learn
Java
Android SDK 2.2+
Nope. Weird question, you already have the book and then you come here to ask what is in it. Open it up and read the index you silly goose.
As for a book on Android, I suggest you go to Amazon and ask it the question you're trying to ask here.
Similar Messages
-
Can I Edit SD and HDV footage at the same time in CS4?
I have a Sony PD 150 camcorder and I'm looking at buying a Sony HDR-HC# HDV 1080i camcorder to use as a second camera on video shoots. Can I edit footage from both cameras on the same timeline in CS4? I'm using a PC, running Windows XP Home Edition, Version 2002 with an Intel (R) Pentium (R) 2.80 GB processor with 2.5 GB of RAM. Thanks!
Lewis B.Do you already have CS4 ?
CS5 is days away. 9 Days for the first look.
I have a Windows XP 2005 with 3.4GHz with 4GB of ram and it cant handle HDV for HD video.
I have a Sony HVR Z1U and use the in camera down-rez and edit in SD just fine.
Like said before you really need a new computer to edit the HDV but if your going to DVD then your only using SD anyway.
But to answer you question you can mix formats with CS4.
As you can see my system ranks second from last on Bills Benchmark tests.
http://ppbm4.com/Benchmark.html
Take the test to see how your system stacks up.
ENjoy: Glenn -
Posting only possible in periods 2002/03 and 2002/02 in company code 0001
All
This is in the ongoing sequence where I am creating everything from the scratch(customers, material, prices etc).So far, I have been able to create and save the salesorder>deliver it>pick the items and then I was going to carry out the PGI and then this happened.
when I use the date i.e(Planned GI) 27-09-2006, I receive the following error
****************snip********************
Goods movement: Error log
Item Material Description Delivery qty UoM Batch
000010 9 T-AS1_MATERIAL__9 10 PC
E M7 053
Posting only possible in periods 2002/03 and 2002/02 in company code 0001
************End snip*********************
If I use a date as R/3 wants ,say 27.02.2002(Planned GI),I get:-
"Picking date is after goods issue date"...which is obvious.
any day after 27-09-2006, say 28-09-2006(Planned GI), I get :-
"Goods issue date is later than delivery date"...makes sence too
one thing was clear here to me, I can only post in Feb/March 2002, while my delivery date is 27 Sept 2006 . So I am in a classic chicken-egg situation.
where and who is giving this "Posting only possible in periods 2002/03 and 2002/02 in company code 0001" message ? How can I override this thing from the past ?
I thought of playing it smart and change my system date to the year Feb. 2002 , but in the fear that a lot of other things will fall as a result of that, I did refrain from doing so.
Could someone make this PGI succesful for me
Thanks for any lessons.Thanks Mr. Srinivas
MMPV was indeed the magic wand.
PGI was successful.
this is my overall document flow as of now :-
Standard Order 2 27.09.06 Completed
. Outbound delivery 80000000 27.09.06 Completed
.. WMS transfer order 1 29.09.06 Completed
.. GD goods issue:delvy 4900000020 30.09.06 complete
.. Invoice 90000000 30.09.06 Missing export data
As I understand, my invoicing is not yet complete , it's got a number and got saved, but how shall I get rid of that red line message "Missing export data"(foriegn trade data incomplete...was the message while saving the billing document).I would be darn happy if I could just get rid of the foreign data part completely(just want to complete the invoice).Would this be checking off a mandatory rqmt. somewhere in the master data?
and would this also be the reason, why I see no accounting document which should have been on status 'open' by now ?
Thanks in advance , -
How to set classpath in WinXP Home edition
Hello everyone,
Recently I have try to run the HelloWorld java code, but it come up with a error. (Exception in thread �main� java.lang.NoClassDefFoundError: HelloWorld)
Java programming Code:
public class HelloWorld {
public static void main (String args[]) {
System.out.println("Hello World!");
I also try to compile another simple program, and it come up with the simpler error, (Exception in thread �main� java.lang.NoClassDefFoundError: Add16And23)
Java programming Code:
public class Add16And23
public static void main (String[] args)
int sum;
sum=16+23;
System.out.println("The sum of 16 and 23 is " + sum);
HOW CAN I FIX THIS, I read other threads before, it say some about class path.
Do anyone know how to set it, in winXP?
Do anyone know the whole path that I should put in, in winXP?
What should I type in the (User variables for windows) and (System variables).
I have :
* (j2eesdk-1_4-dr-windows-eval) downloaded and installed;
*WinXP Home edition Version 2002 Service Pack 1
* My current Java path are (C:\Sun\AppServer\jdk\bin) in the (User variables for windows).
Please help!!!
Thank you all!!!I'm also windows xp.
fllowing example:
java_home=c:\j2sdk1.4.2_03\bin
classpath=c:\j2sdk1.4.2_03\dt.jar;c:\j2sdk1.4.2_03\tool
.jarThis won't fix a thing.
When you run, do it like this:
java -classpath . HelloWorldNote the "dot" after -classpath. That tells the class loader to look in the current directory for the .class files it needs.
Read about how to run the javac.exe and java.exe tools in your javadocs. You'll have to learn about CLASSPATH. - MOD -
I do not get a readable or editable PDF file that has been converted to Microsoft Word.
In the past I have been able to convert PDF files to MicroSoft Word, and Edit and Save the Documents. Now, the converted files are unreadable and uneditable. How do I correct this problem?
Thanks for the email, Stacy!
I don't have an old PDF file that I converted to MicroSoft Word, however the new file that I am trying to convert and edit is the same kind of file that I've converted and edited before; An Invoice from the same Company. Is there a possibility that a download, MicroSoft Compatibility Pack for the 2007 Office System, onto MicroSoft Windows XP Home Edition Version 2002 computer might be causing the problem? Should I download to (.doc) or (.docx)? Any help will be greatly appreciated!
Thanks,
Joseph Renn Little
Date: Fri, 21 Mar 2014 08:48:32 -0700
From: [email protected]
To: [email protected]
Subject: I do not get a readable or editable PDF file that has been converted to Microsoft Word.
Re: I do not get a readable or editable PDF file that has been converted to Microsoft Word.
created by StacySison in Adobe ExportPDF - View the full discussion
Hi Joseph,
I'd like to assist!
Have you tried converting one of your old PDF's that have worked in the past to see if it still works?
Are these files scanned to PDF files?
You may want to try utilizing the OCR solution.
Let me know if that works.
Looking forward to hearing back from you!
Kind regards, Stacy
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6231210#6231210
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6231210#6231210
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6231210#6231210. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Adobe ExportPDF at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0. -
OPINIONS PLEASE - Is my computer to slow to edit HDV in Premier Pro CS4 ?
Got the system new in 2005
Dell XPS
Windows XP
Media Center Edition
Version 2002
Service Pack 3
Dual Core Pentium 4 CPU 3.4 GHz
3 GB of RAM
NVIDIA GeForce 9800 GT 1024MB
I just put a new hard drive in and did a fresh install of windows XP so the system is clean.
When I play SD clip in the preview window my CPU Usage in the Task Manager reads 50-60%
When I play a HDV clip the CPU Usage pegs out at 100%
Is there any tweaks I can make to edit HDV or do I need a new computer ?
Any other options of hardware add-ons I could get ?
Thanks: GlennUpdate on HDV inside CS4
I tried running the same HDV mpeg file with my laptop that is a Duel Core and it still was choppy and pegged the CPU out at 100% inside CS4
Then I tried using Bridge and the HDV played fine with the CPU running at 50-60% just like the .avi file from the SD timeline. So its a Premiere problem.
That got me thinking that maybe it was a codec issue.
I took the same HDV file and started a CS3 project. Worked PERFECT CPU at 50-60% no problems.
It must be a CS4 problem inside Premier.
I captured the file using Premier CS4 capture software and had no dropped frames.
Anyone have any ideas on what would be the next step ?
Is this one of those cases that I have to wait for ADOBE to update the premiere software. I have the current updates on all software.
Is there anyway to get the CS3 HDV codec and put inside CS4. Its probably not even a codec issue.
So for now CS3 works but not CS4
P.S. System is a Dual Core. Both cores show up in device manager and the task manager.
I still want a new system but it looks like its not my computer. ( we all want faster computers )
Thanks for the ideas everyone. -
Downloaded Digital Editions but won't install?
We are trying to use our Ebooks from our library.
Using our Home computer- which has Microsoft Windows XP, Home Edition, Version 2002, Service pack 2.
We have a Pentium 4CPU 1500MHz, 1.49GHz. 512 MB of Ram.
We use "avast" and have a "firewall" as well.
The EXE.file wouldn't run.
We had Adobe already in our system previously, however thought it might have upgraded by using the link our library provided. We also had the flash player.
So we went to the link that was provided by our Library see below.
http://hpl.lib.overdrive.com/5DE8E161-0C85-4862-B995-5FF6BE2E4895/10/3 81/en/Default.htm
Downloaded:Download Adobe Digital Editions
WE FOLLOWED THIS:
Getting Started
Follow these steps to get started with the Adobe Digital Editions:
· Download Adobe Digital Editions ›
· Run the installer and follow the on-screen instructions.
· Once installed, open the Getting Started eBook for an overview of the application.
THEN WE DID THIS:
Adobe Digital Editions 2.0 Installers
Locate your preferred platform and click on it to download the installer. Then run the installer on your machine to install Adobe Digital Editions.
Download Windows (5.61 MB)
AND THEN WE DID THIS:
Additional Downloads
Getting Started with Adobe Digital Editions eBook
The Getting Started eBook is pre-installed with Adobe Digital Editions 2.0; however, it will not be installed if you install as a standard user (non-admin user). If it is not installed or if you happen to remove it, you can download it using the following link.
Download Getting Started with Adobe Digital Editions (EPUB, 55 KB)
THEN WE TRIED TO RUN THE PROGRAM AND GOT THIS RESPONSE:
"Adobe reader could not open [(I've tried a few samples before trying the book I ordered from you)] because it is either
not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't
correctly decoded)".
I did find out that we must have the Digital Editions working "BEFORE" the library sends us the download for the book we
requested.
However, we still should have been able to "TEST" using the "Sample books".
What are we missing???
Can you help????
Joanne.It will be a bit slow, but you will probably find the older version v 1.7.2 of ADE will run fine on your old Pentium
if that is more convenient than using the other one.
Version 1.7.2, it is a little difficult to find, available on Adobe site for Windows and for Mac.
http://helpx.adobe.com/digital-editions/kb/cant-install-digital-editions.html
The forum software is sometimes corrupting the link above. There shouldn't be a blank in 'editio ns.html'. The following redirects to the same page: http://tinyurl.com/diged172 -
Java Forte CE and J2ME Wireless Toolkit configuration
I installed Sun Java Forte V3.0 Community Edition and the J2ME Wireless Toolkit 1.0.3.
I not able to run a MIDlet for the PALM OS Emulator. Wen I execute the MIDLet suite, the output windows returns: "Error could not find a JVM"
- Does any body knows how to properly configure Java Forte to run application on the Palm OS Emulator (POSE).
- Does any body knows how to attach Sun Forte debugger for MIDLet applications ?
Thankshi,
First Install the forte and then install the j2mewtk.While installating j2mewtk chose integrated option.
For Palm OS emulator you have to set the POSE location.
Try out this.
Open ktolbar.
OpenProject.
select an application.(examples)
set device PalmOS_device.
Now run the application.
A window pop for u.
This may help you
good luck.
koka -
Can anyone recommend a good J2ME book?
Hi folks
I'm on the look out for a good book on J2ME. I'd like to know what books you guys have bought and which ones you think is worth buying. I'm considerig purchasing Wireless Java Programming with J2ME by Yu Feng and Dr Jun Zhu. Is this a good book on J2ME or are there better ones? Thanks for your advice.Hi
Thanks for the good advice guys. It looks like Jonathan Knudsen's "Wireless Java: Developing with J2ME" is one of the best books around. I'll probably buy that one or this one that seems to be quite good. The book is called "J2ME In A Nutshell" by Kim Topley:
http://www.amazon.co.uk/exec/obidos/ASIN/059600253X/qid=1064919774/sr=1-1/ref=sr_1_3_1/202-0023835-2590247
What do you guys think about this book?
Steve -
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/ -
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. -
Ann: Super 2.20 - a suite of J2EE tools
Announcement: Super 2.20 - a suite of EJB/J2EE monitoring/admin tools 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.0, 6.1 and 7.0
* Websphere 4.0
* jBoss 2.4.4 and 3.0
********** What is new:
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 get the error message: Server object error 'ASP 0177 : 800401f3' Server.CreateObject Failed /x-objects-new/dbconnect/DatabaseConnect.inc, line 588 800401f3 and the download url is http://resources.businessobjects.com/labs/cal/quark_platform_1.2.0_133.zip -- should that be 135?
Maybe you are looking for
-
Dear Forum, I am trying to put together a SQL such that it lists my Invoices in aging bucket depending upon when I run the report For eg : inv number , 0-1 , 1-2, 2-3 , 3-4 and so on months. For given report run date and invoice date , it should put
-
My iMac (27-Inch, 2012) is randomly shutting down
Hello, Wanted to ask here before I bring my iMac in. I'm having an issue with my iMac randomly shutting down from what seems like a KERNEL PANIC. I haven't been able to pin down what is causing the shutdowns/kernel panic. We usually leave this iMac o
-
I lost my XS key on an old version of Logic Gold. What can I do?
Hello, I have been using an old version of Logic Gold 5 on a G4 tower since 2003. I recently moved and as it goes with any move, things got lost, including my old blue eMagic XS key! I'm wondering what I can do to get my program to open now. I am not
-
Plant to plant subcontracting(Under one company code)
Hi, I need a help on one issue. We are having multiple plants under one company code. Material goes with 57F4 challan for subcontracting plant to plant. How to do the subcontracting process for plant to plant. Please explain step by step. I know the
-
Regarding XK02 transaction in SAP ECC 6.0 Version
Hi All, I am working with an object which calls a transaction <b>XK02</b> to modify the name and contact details fields in Version <b>SAP ECC 6.0</b>. The problem is that, when the transaction is run manually and saved or when an SHDB Recording is c