Ias problem in admin tool login.

Hi,
When i try to deploy a 9MB J2EE application on iAS6.0SP2, the process
goes fine, but my iAS Admin tool doesnt work. It gives timeout error.
But if the same application's size is cut down to 7MB, the admin tool
works fine. Can you please suggest me the reason for this?
Thanks and Regards.
shivaram.

Hi,
That was a known bug in iAS-Sp2, which has been fixed in iAS-Sp3.
Sanjeev.
Super-User wrote:
Hi,
When i try to deploy a 9MB J2EE application on iAS6.0SP2, the process
goes fine, but my iAS Admin tool doesnt work. It gives timeout error.
But if the same application's size is cut down to 7MB, the admin tool
works fine. Can you please suggest me the reason for this?
Thanks and Regards.
shivaram.

Similar Messages

Admin tool: login.jsp

When we access the admin tool login page login.jsp
we only get an empty page (with just the body html tags)
Nothing else.
The jsp examples in our 9.2 database installation
(not iAS) seem to work OK.
We have made the post-installation tasks as described
in "Installing the Ultra search Middle Tier ... "
Thanks for any hints.
Per Thernquist

I have now found the cause of the problem.
During the installation [in Linux Redhat 7.3]
the file login.uix ends up the the folder
$ORACLE_HOME/ultrasearch/webapp/isearch_admin/control
where the login scripts doesn't find it.
Moving login.uix to the folder
$ORACLE_HOME/ultrasearch/webapp/isearch_admin/include
makes things work OK.
/Per
Thanks for a prompt reply
I have followed the configuration instructions in
the Ultra Search Online Documentation/Part 1/
Installing the U S Middle Tier Component .../
Editing the ultrasearch.properties file
The jserv.log says
java.io.FileNotFoundException: Could not find login.uix
login.uix does exist, in the folder
<oracle home>/ultrasearch/webapp/isearch_admin/control alongside with i.a. login.jsp.

Admin tool: login.jsp (blank page)

I have a problem similar to a recent posting.
I have a 9i Release 2 database installation, server works, sample jsps work, database is up.
Updated the file $ORACLE_HOME/ultrasearch/webapp/config/ultrasearch.properties with our info.
When I try to access the admin page (http://rockfish:7778/ultrasearch/admin/index.jsp) I get to the login page, but it is blank (html body tags, but nothing to display).
The .class and .java file are created in ultrasearch/webapp/isearch_admin/_pages
Is that right? should they be under htdocs/_pages?
Is single sign-on possibly a source of my problem?
Any help would be greatly appreciated,
John

Hi, John:
Does anybody know how to correctly set "AdminConstants.JSP_SRC_HOME" ? Yes.
in ultrasearch.properties file, you need to set the correct admin.srchome variable ->
"Do not use $ORACLE_HOME for admin.srchome , please enter the real file path"
So your ultrasearch.properties file should look like:
=====================================================
connection.driver=oracle.jdbc.driver.OracleDriver
connection.url=jdbc:oracle:thin:@localhost:1521:swims9i
admin.srchome=C:\\oracle\\ora9i\\ultrasearch\\webapp\\isearch_admin
=====================================================
Here is a webIV note explain this problem in details: (you can also find this note in metalink)
http://webiv/cgi-bin/webiv/do.pl/GET?WwwID=Note.202949.1&List=ARTICLES&ARTICLES.Idx=4
Hope this is a clear,
Cindy

Admin tool problem

Hi,
When i try to deploy a 9MB J2EE application on iAS6.0SP2, the process
goes fine, but my iAS Admin tool doesnt work. It gives timeout error.
But if the same application's size is cut down to 7MB, the admin tool
works fine. Can you please suggest me the reason for this?
Thanks and Regards.
shivaram.

Unfortunatly a known problem with iasdeploy tool
Use j2eeappreg on the iAS server itself and this will work
(ignore the deprecated msg)
regards
Tom
Super-User wrote:
Hi,
When i try to deploy a 9MB J2EE application on iAS6.0SP2, the process
goes fine, but my iAS Admin tool doesnt work. It gives timeout error.
But if the same application's size is cut down to 7MB, the admin tool
works fine. Can you please suggest me the reason for this?
Thanks and Regards.
shivaram.--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tom Fonteyne
EMEA Technical Support
SUN/iPlanet E-Commerce Solutions
http://www.iPlanet.com

Restrict OBIEE developers to login into OBIEE admin tool withAdministrator

I have developers with their own id's but with admin role assigned to them and If I remove the admin role from their id's they cannot login into OBIEE via admin tool in online mode to make any changes to the RPD.
Q is) Developers make changes to the rpd file in online mode but at the same time I dont want them to have the admin privileges like making changes to the security/connection pool entries so on. But they can make changes to the presentation layer or business model. If I remove the administrator role from their id's they cannot even open the rpd in online mode i.e they can't even login. How do I give the developers the control they need and at the same time lock down the admin related stuff from changes?
Also they cannot make the changes offline and they need to login and open the rpd online.

Hi,
I think you can resolve this issue, by setting up a different application role for all of your developers (yes, with BIAdministrator privileges too). However, in the .rpd you could restrict the access to this role to the physical layer. Briefly, the steps are below
1. Set up a new application role.
2. In the .rpd Manage Identity -> application roles -> New role -> Properties -> Permissions -> Object Permissions.
3. Set 'No Access' to all of your physical layer objects.
Hope this is what you are looking for.
Thank you,
Dhar

Cant login to admin tool

Hi all
I am using Oracle ultra searc on oracle 9i database
I followed all the intallation and post installations Instrustions and I made the user with the specified role
but always displaying wrong password/username
please somebody help me its very ergent
Mostafa Hashem

Hi
To login in the admin tool you have to enter a valid user/password of the database.
Try with WKSYS, if the database was correctly installed you should be able to login.
Did you check the DB-URL, e.g. in ultrasearch.properties.
Chris

Problem starting visual admin tool

HI
I have recently installed SAP ENTERPRISE PORTAL
Now,I need to do some changes in the visual admin tool
I browsed to following loaction in my personal computer where I have installed SAP EP
c:\usr\sap\CE1\J00\j2ee\JSPM
There I See the file go.bat Once I click on that I see blank command prompt window being get displayed.
What are the settings I need to perform inorder to open the VISUAL ADMIN TOOL
Thanks in advance

HI
Once I browse to the following path
c:\usr\sap\CE1\J00\j2ee I do not see admin folder being displayed I see the following folders
cluster,configtool,console,deployement,jpa,jspm,j2eeclient,migration,objectprofilertool,temp,rmic,os_libs,rdbg.proxy
thanks in advance

Administration Tool login via 10817 failed

Hi,
Have a problem for a long time on login issue to the administration tool via ksvradmin in iAS 6.5. Lived with it until recently as need to change some parameter thru the admin tool.
Does anyone has had this problem and got it solved? When attempting to register a server using the default info as below, it keep prompted me login failure:
Name: iAS1
Hostname: localhost
Port: 10817
Username: admin
Password: xxxxxxxxxxxx
I do not have any problem connecting to the iDS or startup any of the services just that I cannot login and register an server. Please share your experience/solution to the above issue if you have resolved such issue before. Thank you.

Hi,
This is interesting!! After running through the thread, I suspect there is some issue with your configuration not the .rpd. Taking your words that replacing your old .rpd does not work too and of course the your old .rpd would have worked, here are my prime suspects
1. Some clustering setup running behind scenes. I not get any other instance, when a .rpd could be shared except when a master .rpd is shared with cluster servers. So is the "Sharing violation" error.
2. Some Init blocks in your .rpd with "Required for Authentication" set. For example, an init block with "required for authentication" is bound to fail and not let you in online mode, when the underlying source/ DSN etc has issues.
So, check on these guys and see if you nail them down first.
Hope this helps.
Dhar

Open and connect in OBI 11.1.1.5 admin tool fowwoling OBE Upgrade

I installed OBI11.1.1.5 on Redhat 5.2 and the admin tool on a windows. In this two machine I have OBI 10 server and admin tool installed as well. The OBI 11 components are all up running as I can access them such as EM and represention service.
Following OBEhttp://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm?print=preview#t3 .I upgraded our 10g rpd and catalog and see the repository saved in instance_home, and verified that the default is RPD sh20110903_BI002.
Next step in the OBE, I verify Reposiotory Metadata. I launched the admin tool, opened inline. In the generated dialog box, I entered the password in defined in the update script as Repository Password, and used weblogic login in User/Password. All other fields are blank. That is all I can do in the dialog box, but the Open buttone is always grey. I think at least one available repository should be listed in the list box at the bottom, but it was empty.
Then I tried to create a new repository. In step 2 Select Data Source, I choose ODBC 3.5 and use a valid system DSN, but got Error : The connection has failed.
I tried also use Connection Type OCI 10g/11g. IN the Data Source Name I used a valid netservice name defined in a Oracle client's Oracle_HOME. But still got Error : The connection has failed.
Questions
1) How can make the Open button active in the Open inline RPD dialog box?
2) Why the valid System DSN failed to connect in 11g admin tool. It is OK in 10g admin tool and ODBC configure
3) How to make Admin Too; sees the tnsnames definition. Should I copy the tnsnames.ora file to somewhere under Admin Tool installation directory?
Many thanks.

Thanks. The post appares make sense. I opened my user.sh file and has 2 questions:
1) There are 32bit section and 64 bit section, and it states that 32 bit server must work with 32 bit client, so is for 64 bit. In my case, the clients are most likely 32 bit windows (browsers and admin tool), but the server is installed on Redhat 64 bit. Is this a problem? How do I know if my OBIEE iis running 64 or 32 bit?
2) All entries in the user.sh file are commented out. Then what file is used to in the current OBI11, it is started automatically after the installation.

Admin Tool

Hi All,
I tried to change my system in Abap Stack to Java Stack.By unfortunatly i have done some settings.Present i have a problem tha is "i am unable to open the Visual Admin Tool" What is the reason.can you pls any body help me.When ever i was trying to logon to the admin tool it showings one warning massege that is "SAP* user open.no bady canot logon".
regards ,
sai

SAP * user activated means no one can login except sap* user.
Before deactivating sap* , make sure atleast one super admin role is available. ( unlock users if any users locked )
check the below procedure to deactivate sap* user.
How deactivate SAP* after inital logon and creation of new users
http://help.sap.com/saphelp_nw04/helpdata/en/3e/cdacecedc411d3a6510000e835363f/frameset.htm
Koti Reddy

J2EE Visual Admin Tool stops at 99%

Hello everyone,
I have a problem with the Visual Admintool for the J2EE of an EP 6.0 SPS12 Installation on W2k. The tool worked properly before I installed TREX 6.1.
After I connect sucessfully with the admin tool it runs slowly up to 99% and stops here. The Tree of dispatcher and his services are viewable but I cannot expand the server node.
The TREX is running fine, all services are green. The Portal is available and the MMC of Portal shows all green (all services/intances started successfully). I can login and administrate the portal. But I can't configure the TREX for the portal because I can't access the Servernode in Visual Admin.
I checked the logs for the admin tool but there are no errors. The info in admin tool shows no error too. Maybe some additional traces and logs must be first activated.
On the system is a second EP and TREX running but I stopped all other applications, restarted the portal and tried to connect with visual Admin. It stops again at 99%.
Saw some threads with a solution to modify the hosts file or change the heap size of J2EE but no one confirmed that this has helped.
Does someone has an idea what I could check next?
Regards
Alex

Hello Praveen,
thanks for your hint. I checked the note which is very old and only for release 6.20 (I'm on 6.40). I found a similar error in my logs but this error was produced by a failed login and was not releted to my problem. I checked again my logs after but could not find any helpful entry here.
Some more ideas? Looks like a candidate for a OSS message to SAP again.
Regards
Alex

SSO between Portal Application and Portal Admin Tool

Hi All,
We have a requirement for implementing SSO between a Portal application and
Portal admin tool.
We are using WL Portal 8.1 SP4.
Here is the reason for this requirement -
A user logged-into Portal Application needs to login to Portal Admin tool to
do some admin activity. We want to provide a link in the portal application
using which the user can directly login to the Portal Admin tool without
having to enter the credentials again.
If someone has any info on how to implement this, can you please point me in
the right direction.
Thanks,
~Deepak

Hi,
When creating PP you have 2 options
PP used for compiling and PP used for Building
You create PP with all the libraries into Developing/Compiling Other DCs
And another PP with all the libraries into can be packaged into other build results (SDAs).
Once you have these 2 PP in place you add the DC as used DC.
And this should resolve the issue.
Hope this helps.
Cheers-
Pramod

Xserve RAID Admin Tool 1.5.1 not quite working

I have an Xserve RAID that's currently at firmware 1.3.2/1.26a according to Xserve RAID Admin Tool 1.5.1. However, when I try to upgrade the firmware to 1.5.1 via the RAID Admin Tool 1.5.1, it just doesn't do anything--it accepts the .xfb file and then...nothing. Quitting out of the the Admin Tool and restarting still shows the firmware at 1.3.2/1.26a. Same thing if I shut down and restart the Xserve RAID from the RAID Admin tool. Any tips? There's nothing stored on the RAID system yet (the array hasn't even been created--it's a blank system) and nothing is attached to it either (I've just plugged in the ethernet links to format it first before I start attaching an Xserve G5 to it). Also, even though the lower controller is showing green and I have an ethernet cable plugged into it, I can't get any info out of it nor can I configure it with an IP address. Only the top controller seems to allow some configuration such as IP address.

Okay, I've solved the problem.
Basically, the issue was that the lower controller wasn't seated right despite it showing a green light in RAID Admin. When I went to visually inspect it, I noticed that despite what RAID Admin 1.5.1 claimed, its light wasn't even on, let alone green. And since the lower controller handles slots 8-14 of an Xserve RAID and my slots 8-14 are totally unpopulated (empty) at the moment, it was never noticed. Now that I've reseated the lower controller, everything is visually showing green across the board and the firmware upgrade is proceeding as expected and it has upgraded the firmware from 1.3.2/1.26a to 1.5.1/1.5.1c complete with autorestart of both upper and lower controller modules.
Basic lesson learned: RAID Admin lies. If possible, visually inspect the box itself!
Thanks to all who responded.

Admin Tool can not create any new database or model [nqserror 46131]

Hi everyone!
I can not create anything new in each layer on the admin tool. It marks unknown error.
When I try to import metadata it send the message: [nqserror 46131] unresolved hostname, everything in online mode. I can modify everything offline, then replace the rpd and I can create reports in Answers. But I need to do all of these online mode.
Everything else works well (Answers, Dashboards, Publisher). The server name is correctly put in the instanceconfig.xml.
OBIEE Version: 11.1.1.6.0 (upgrade recently from 11.1.1.5). The scheduler does not start since migration.
Server OS: Red hat enterprise edition
Regards,
Edgar Tercero
Edited by: 958457 on 11-sep-2012 12:04
Edited by: 958457 on 11-sep-2012 14:13

Thanks but it not solve my problem.
I detect no problem in my enviroment variables in the bi-init.sh
This is what my admin tool log says:
[OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 690] [nQSError: 43113] Message returned from OBIS. [[
[nQSError: 46131] Unresolved host name: vrnmobiee. Could not get details about the specified host]]

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.

Ias problem in admin tool login.

Similar Messages

Maybe you are looking for