J2EE Visual Admin tool

Hi fellow XI'ers,
I want to install J2EE Visual Admin tool on my laptop, but all information I can find is that I have to go to C drive \usr\sap\C11\JC00\j2ee\admin and run go.bat but...this folder does not exists on my laptop...I guess I have to install locally Netweaver or WAS? And where do I find installation files?
Best Regards,
Margaret

hi,
no:)
all you have to do is to copy the folder:
usr\sap\C11\JC00\j2ee\admin
to your laptop and you can use it
maybe you just have to change one path
in one of he files but try with copying first
Regards,
michal

Similar Messages

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

Visual admin tool&configer tool

whta is main difference of visual admin tool&configer tool

Hi Raghava,
This is a post by some gentleman, I tried figuring out the thread but could not succeed.
VISUAL ADMINISTRATOR
The J2EE Engine Visual Administrator is a graphical user interface (GUI) that enables administration of the whole cluster, all cluster elements, and all modules running on them. It provides remote monitoring and management of managers, services, libraries, and interfaces working on each element in a single GUI
Visual Administrator includes functions for:
a) Obtaining general information about a service, manager, interface, or library (for example, its name, group, and so on).
b) Logging on to the J2EE Engine via the Visual Administrator tool
c) Administrating and changing the properties either specific or common for each service or manager
d) Configuring the global properties
e) Runtime administration and control.
Read out more about its features on VISUAL ADMINISTRATOR.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
CONFIG TOOL :-
The Config Tool enables offline configuration of the J2EE Engine cluster elements. It is XML-based and allows exporting the system configuration for later use.
When you run the J2EE Engine Config Tool via a GUI or text-only interface, it connects to the database and scans the server configuration. The information provided is passed to the corresponding interface that is used for configuration.
Each change you can perform corresponds to a particular task in the Batch Config tool.
All modifications made using the J2EE Engine Config Tool can be exported to an XML file for later use.
two types:-
a) GUI Config tool :- The J2EE Engine GUI Config Tool enables offline configuration of J2EE Engine cluster elements concerning serviceu2019s and manageru2019s properties, adding new server processes, changing Java parameters, exporting the system configuration to an XML file, and so on.
After installing the SAP Web AS Java, a configtool directory is created, containing a configtool script file. Double clicking on this file starts the Config Tool.
b) Text Only Config tool:- The text-only Config Tool enables you configuration of J2EE Engine cluster elements using a text-only based interface. It enables you to change the cluster element properties, JVM settings, add new elements, export the system configuration to an XML file, and so on.
After installing SAP Web AS Java, a configtool directory is created under <SAP_install_dir>/<system_name>/<instance_name>/j2ee, containing a consoleconfig script file. Double clicking on this file starts the text-only Config Tool.
Read more about config tool on CONFIG TOOL
http://help.sap.com/saphelp_erp2005vp/helpdata/en/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm
Hope this helps.
Cheers,
Sandeep Tudumu

Unable to find the Visual Admin Tool Nw 7.3 Ehp1

Hi Experts,
We have Installed the Portal System (NW 7.3 Ehp 1) in that we are unable to find the visual admin Tool in the path drive:\usr\sap\\J00\j2ee. Can you please suggest me how to rectify the error..
Thanks in Advance...
Regards,
Krishna.M

Dear Krishna,
Visual admin is no longer supported in NW 7.3. Please find the below link to see all the changes in NW 7.3:
Nice Blog For All the changes in NW 7.3
Hope its helpful.
Regards,
Deeraj Shetty

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 Rev,
1> Your Visual admin tool is located in folder
"C:\usr\sap\CE1\JC00\j2ee\admin".
JSPM is another tool used for upgrade or appling *.SDA or *.SCA files.
2> There is also web based tool called NetWeaverAdministrator located under alias http://<hostname>:<port no.>/nwa .
3> Also set the path for JAVA_HOME in environment variable.
4> If the locked account is the only administrators account, follow the instructions in note 669848.
5> If you no longer connect to the Visual admin it is better change the password of the user j2ee_admin as mentioned bellow
You have to change the J2EE Engine administrator password in the secure store as follows:
a. Start the Config Tool by executing the /usr/sap/<SID>/<Instance name>/j2ee/configtool/configtool script file.
b. Select secure store.
c. Select the admin/password/<SID> entry.
d. Enter the J2EE Engine administrator user new password in the Value field and choose Add.
e. Choose File -> Apply to save the data.
f. Restart the J2EE Engine
Regards,
Manomeet
Award points if helpful **

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

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 the Source Code
 Panel (as a work-a-round for JDK 1.3).
 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.

Canu00B4t see log with J2EE Visual Admin or Standalone Log Viewer

Bom dia!
When logging on Log Viewer, it shows de error message: Unable to invoke LogControllerFacadeMBean method:"getMetaDataOfReaders" In J2EE Visual Admin the error message after click in the item Log Viewer is Error while loading service Log Viewer
When I click in defaultTrace.trc nothing appears. The same for the others log archives listed in Log Viewer.
Can someone help me with this?
Very thanks from Spain.
In the console I see the following java exception:
Exception in thread "AWT-EventQueue-0" com.sapmarkets.bam.util.BAMRuntimeExcepti
on: Unable to invoke LogControllerFacadeMBean method: "getMetaDataOfReaders".
 at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeFacade
Method(AbstractLogDepot.java:225)
 at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getMetaDataO
fReaders(AbstractLogDepot.java:303)
 at com.sapmarkets.bam.view.config.AbstractViewConfiguration.getColumnInf
oFromServer(AbstractViewConfiguration.java:218)
 at com.sapmarkets.bam.view.config.AbstractViewConfiguration.readSetting(
AbstractViewConfiguration.java:126)
 at com.sapmarkets.bam.view.config.AbstractViewConfiguration.getColumnSet
tingForLogType(AbstractViewConfiguration.java:247)
 at com.sapmarkets.bam.view.buffertable.ContentPane.obtainColumnSettings(
ContentPane.java:915)
 at com.sapmarkets.bam.view.buffertable.ContentPane.<init>(ContentPane.ja
va:127)
 at com.sapmarkets.bam.view.AbstractLogViewerAppplication.makeTablePane(A
bstractLogViewerAppplication.java:423)
 at com.sapmarkets.bam.view.AbstractLogViewerAppplication.displayLogs(Abs
tractLogViewerAppplication.java:474)
 at com.sapmarkets.bam.view.overview.OverviewFilePathTreeWrapper.openLog(
OverviewFilePathTreeWrapper.java:334)
 at com.sapmarkets.bam.view.overview.OverviewFilePathTreeWrapper$TreeMous
eListener.mousePressed(OverviewFilePathTreeWrapper.java:359)
 at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
3)
 at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
2)
 at java.awt.AWTEventMulticaster.mousePressed(AWTEventMulticaster.java:26
2)
 at java.awt.Component.processMouseEvent(Component.java:6038)
 at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
 at java.awt.Component.processEvent(Component.java:5806)
 at java.awt.Container.processEvent(Container.java:2058)
 at java.awt.Component.dispatchEventImpl(Component.java:4413)
 at java.awt.Container.dispatchEventImpl(Container.java:2116)
 at java.awt.Component.dispatchEvent(Component.java:4243)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322
 at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3983)
 at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
 at java.awt.Container.dispatchEventImpl(Container.java:2102)
 at java.awt.Window.dispatchEventImpl(Window.java:2440)
 at java.awt.Component.dispatchEvent(Component.java:4243)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
 at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThre
ad.java:273)
 at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.
java:183)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
ad.java:173)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Caused by: java.lang.reflect.UndeclaredThrowableException
 at $Proxy0.invoke(Unknown Source)
 at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeMBeanM
ethod(AbstractLogDepot.java:163)
 at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.invokeFacade
Method(AbstractLogDepot.java:206)
 ... 33 more
Caused by: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.sapmarkets.bam.jmx.connector.AbstractLVServer.invoke(AbstractLVSe
rver.java:184)
 at com.sapmarkets.bam.jmx.connector.rmi.IntegratedConnectorClient.invoke
(IntegratedConnectorClient.java:107)
 ... 36 more
Caused by: javax.management.ReflectionException: No such operation: getMetaDataO
fReaders
 at com.sun.jmx.mbeanserver.PerInterface.noSuchMethod(PerInterface.java:1
52)
 at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:94)
 at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
 at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:836)
 at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761
 ... 42 more
Caused by: java.lang.NoSuchMethodException: getMetaDataOfReaders()
 at com.sun.jmx.mbeanserver.PerInterface.noSuchMethod(PerInterface.java:1
50)
 ... 46 more

Hello Ivan,
Make sure that you are using a supported JDK version as per note below:
723909 Java VM settings for J2EE 6.40/7.0
And also, make sure that the necessary environment variables are pointing to the correct JDK version.
Regards,
Rafael

Visual Admin tool in Read only mode?

HI
is it possible to access the Visual Admin tool in Read only mode. if Yes then How? if No then why?
Regards
Shridhar Gowda

Hi,
check with links, you may get some info, but i am not sure.
Check some VC roles and assign those roles for perticular users for full and read only.
1. http://help.sap.com/saphelp_nw70/helpdata/EN/7a/a0e84240857076e10000000a1550b0/content.htm
2. https://admin.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/659c082e-0c01-0010-2e9f-ac674cfff2d2
3. https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0bf413a-66a6-2a10-8eb7-91b9e99c4a97
Regards,
Srini Nookala
Edited by: Srini Nookala on Aug 26, 2008 4:02 PM

Virsa application components not found in Visual Admin tool (GRC AC 5.3)

Hi experts,
I have this weird issue. I was trying to run the background job to synch the backend roles, users and profiles in CC. But when I checked the background job deamon through this link
http://209.207.245.71:50000/sap/CCADStatus.jsp , the screen was blink.
I searched and found this note #999785.
When I looked for the " virsa/ccxsysbgear application" through the Visual Administrator, I could not find any of the Virsa components application in our GRC server under this path:
Visual Admin --> cluster tab --> deploy folder --> virsa/* (all components)
We have AE, FF configured and running in our development server. Now I am configuring the CC and found all the virsa application services are missing.
We are implemented GRC Access control 5.3 . Any ideas how to get these components deployed and running in the Visual Admin tool??
Some of the sample deployed components are
1. virsa/ccxsysbgear application '
2. virsa/ccume
3. virsa/AEume
4. virsa/ccxsysbher etc
Greatly appreciate your help!
Thanks
Siri

I found these files with the new name.. There is no virsa tag for these files.

Runtime Tab missing -J2ee Visual Admin

Hi
We want to maintain the PIRWBUSER in the PMIstore (j2ee visual admin )
under
Cluster ® Server ® Services ® Destinations.
but we are not able to see the "runtime " tab as mentioned in the following help doc.
http://help.sap.com/saphelp_nw2004s/helpdata/en/30/60084136b5f423e10000000a155106/content.htm
kindly advice
regards
krishna

Thanks Barry
The second times we fired it open, we were able to see the tab
thanks
regards
krishna

Locked out of J2EE Visual Admin and other problems

I recently tried to install some Java PDK components using the SDM tool. However it failed when trying to deploy the javadoc component. Since then the following has occurred:
1. My enterprise portal website is unavailable (ERROR: 'Details: Web container not available!').
2. I can't login into the J2EE admin tool (ERROR: 'the object does not exist') using either the initially reset Admin password (as part of the original install) or 'admin'.
3. In the SAP MMC, the Server 0 instance displays yellow, with the jcontrol.exe status (under Process List) as 'some processes running' and server0 (under Process Table) status as 'starting applications'.
4. The log file on the J2EE database is 100% (not sure if this is relevant or not).
I've tried to undeploy the java components in case they are the cause of the above issues but get the following error in SDM:
Info: ***** Begin of SAP J2EE Engine Online Undeployment (J2EE) *****
No information about the J2EE engine cluster is available. The online undeployment process is continuing.
Info: ***** End of SAP J2EE Engine Online Undeployment (J2EE) *****
Error: Undeployment of SDA executed with errors.
Error: See below for details:
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running. com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [server] with user name: [Administrator]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineAppOnlineUndeployerImpl.checkLoginCredentials.DMEXC)
Error: Result: error
In summary, assuming the new java components broke the EP and J2EE I can't undeploy them (because J2EE is broken) in order to fix J2EE. Damned if I do and damned if I don't.
Does anyone know why I can't login to J2EE VA, why the J2EE server only partials starts up, why the EP is not working, or how I can truncate the database log file?
I'm running EP 6.4 SP9 on W2K3.
Mike D.

Hi Mike,
May be the following link will help you.
J2EE Engine start error: Database initialization failed!
Moreover, make sure that your port no to which connecting through visual admin is around 50000.
Regards,
Bharath

Error access J2EE Visual Admin

I've just completed installing the SAP NetWeaver 04 Sneak Preview. Unfortunately, TREX is not running (or maybe even installed). I've tried to login to the J2EE admin tool to specify the TREX server but I get the following message:
Unable to lookup connection default
http://server:50004/msgserver/test/logon returned empty list of connection parameters.
Port 50004 is the P4 port for the Java install. I've tried port 50000 but get the same message. Does anyone have any idea?

Hi Robert,
Just so there is no confusion - there is no TREX included with the Sneak Preview packages currently available on SDN.
Regards,
Kathy Meyers
SDN

Visual admin tool not working

hii guys,
in my netweaver system visula admin tool not working .when ever im trying to connect with user id and password its showing like this.how can i solve this issue.plz help me

Hi,
Try to login to system info page with administrator or j2ee_admin for java and dual stack respectively to check if the password is correct.
If the password is incorrect, then check if you have any alternate admin ID. Change the administrator or j2ee_admin password, then try to login with the new password. Change the password of SDM and securestore to the new one.
If this is not the case, then check the log files in visual admin directory. Please post the same.
Cheers...,
Raghu

Creation of Properties file in j2ee visual admin

Hi,
I have followed the exact steps mentioned in the MI 2.5 installtion document for editing the entries in the <System ID>.prop files. but it is not generationg the files in the required folder in the server and sync is failing with log as " unable to open the property file".
But it worked if I copied the file manually to teh server, System_Properties file.
have you faced the same problem ever?
Thanks
Satya

Hi Satya,
 If you are talking about the steps that should be completed
before testing the configuration with the url...
http://<Server>:<Port>/meSync/servlet/meSync?~sysid=<System
ID>&~login=<User
name>&password=<Password>&client=<Client>&language=<Language>&ackno
wledge=X&~test=true&
then i think version:sp14 document is very clear...
1. In the J2EE visual administrator, choose the
service Configuration Adapter from the
server --> services menu.
2. Choose RunTime tab(Default).
4. Navigate to....
configurations --> apps
 --> sap.com
 --> com.sapmarkets.mesyncjco
 --> appcfg
5. Change it to edit mode. choose yes for the popup.
6. Right Click on appcfg .
7. Select create subnode
8. Select the File Entry from the drop down box.
9. Give the name as <sysid>.props
<sysid>= Your System id.
10. Enter the two enter each in a line in the display.
For eg.
ashost=<myserver>
sysnr=<sn>
<myserver>=Hostname.
<sn>=System Number.
Hope it helps.
Regards,
Maheswaran.B

J2EE Visual Admin tool

Similar Messages

Maybe you are looking for