Visula admin tool, remote configuration

Hi all ,
Planned to configure Visual admin tool on local PC for SOLMAN 7.0 with the same network.
Note 758298 - Offline Installation of J2EE Engine Visual Administrator
Do i need to follow the same note  If yes,
Im getting stucked in downloading  the following
tc_sec_java_crypto_signed_fs_lib.sda
as for the above not or if the complete process is also not correct, pls advice.

Hi Guys,
I have resolved the issue, i was using a look up type of connection, i have changed to direct connection to the dispatcher and selected the transport layer of type default.
Thanks,
k s reddy

Similar Messages

  • BI Server - Solaris - Admin tool security configuration

    Hi,
    I have a BI server running on Solaris. I want to use the admin tool to configure users/groups which are configured in an LDAP database.
    Is this possible? Sifting through the forums, I can see that the admin tool is used to construct an offline rpd file before exporting it to the BI server. I need an online connectivity to do the same
    Any pointers would be helpful
    Thanks...Vijay

    I want to use the admin tool to configure users/groups which are configured in an LDAP database.You can configure RPD user/groups in online mode although that's not the best practice. The Admin tool is only supported on Windows.

  • Can not access sample & admin tools after configuring Oracle8.1.7

    Hi all,
    I am using WLS6.1(sp2) and WLPortal4.0(sp1).
    I changed the default database(i.e. Cloudscape) to Oracle by following the doc
    http://edocs.bea.com/wlp/docs40/deploygd/oraclnew.htm
    But, after setting up the Oracle8.1.7, when i try to access the sample stock portal
    from the homepage, i am getting the following exception
    PortalPersistenceManager: portal 'portal/stockportal' not found
    <Feb 20, 2002 12:33:19 PM EST> <Error> <HTTP> <[WebAppServletContext(1467076,stockportal,/stockportal)]
    Servlet failed with S
    ervletException
    javax.servlet.ServletException: Received a null Portal object from the PortalManager.
    at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalRequest(PortalWebflowServlet.java:194)
    at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWebflowServlet.java:99)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
    at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at jsp_servlet.__index._jspService(__index.java:92)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    even i can not access the admin tools.....i get the follwing error when i try
    to access the portalTools/index.jsp
    <Feb 20, 2002 12:38:18 PM EST> <Warning> <Webflow> <Webflow could not resolve
    a destination given: appname [tools], namespace
    [admin_main], origin [begin], event [defaultEvent] with request id [3121877];
    Attempting to load Configuration-error-page.>
    <Feb 20, 2002 12:38:18 PM EST> <Error> <Webflow> <Error while parsing uri /portalTools/application,
    path null, query string n
    amespace=admin_main - Webflow XML does not exist, is not loaded properly, or you
    do not have a configuration-error-page defin
    ed.
    Exception[com.bea.p13n.appflow.exception.ConfigurationException: The configuration-error-page
    node was not found in the webfl
    ow xml file. for webapp [tools], namespace [admin_main]. While trying to display
    CONFIGURATION ERROR: [Exception[com.bea.p13n
    .appflow.exception.ConfigurationException: Bad Namespace - namespace [admin_main]
    is not available for webflow execution. Mak
    e sure the [admin_main.wf] file is deployed in webapp [tools].]],]
    at com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processConfigurationError(WebflowExecutorImpl.java:786)
    at com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebflowRequest(WebflowExecutorImpl.java:484)
    at com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebflowRequest(WebflowExecutorImpl.java:419)
    at com.bea.p13n.appflow.webflow.servlets.internal.WebflowServlet.doGet(WebflowServlet.java:132)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
    at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at jsp_servlet.__index._jspService(__index.java:92)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    Am i missing any step here???
    can anybody help me????
    thanks
    Vijay

    oops...i missed step5.
    it is working now after doing the sync.
    thanks
    Vijay
    "Daniel Selman" <[email protected]> wrote:
    Did you sync the applications and load the sample data?
    Sincerely,
    Daniel Selman
    "vijay bujula" <[email protected]> wrote in message
    news:[email protected]...
    Hi all,
    I am using WLS6.1(sp2) and WLPortal4.0(sp1).
    I changed the default database(i.e. Cloudscape) to Oracle by followingthe
    doc
    http://edocs.bea.com/wlp/docs40/deploygd/oraclnew.htm
    But, after setting up the Oracle8.1.7, when i try to access the samplestock portal
    from the homepage, i am getting the following exception
    PortalPersistenceManager: portal 'portal/stockportal' not found
    <Feb 20, 2002 12:33:19 PM EST> <Error> <HTTP><[WebAppServletContext(1467076,stockportal,/stockportal)]
    Servlet failed with S
    ervletException
    javax.servlet.ServletException: Received a null Portal object fromthe
    PortalManager.
    atcom.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalReq
    uest(PortalWebflowServlet.java:194)
    atcom.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWe
    bflowServlet.java:99)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    atweblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
    l.java:241)
    atweblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at jsp_servlet.__index._jspService(__index.java:92)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2495)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    even i can not access the admin tools.....i get the follwing errorwhen i
    try
    to access the portalTools/index.jsp
    <Feb 20, 2002 12:38:18 PM EST> <Warning> <Webflow> <Webflow could notresolve
    a destination given: appname [tools], namespace
    [admin_main], origin [begin], event [defaultEvent] with request id[3121877];
    Attempting to load Configuration-error-page.>
    <Feb 20, 2002 12:38:18 PM EST> <Error> <Webflow> <Error while parsinguri
    /portalTools/application,
    path null, query string n
    amespace=admin_main - Webflow XML does not exist, is not loaded properly,or you
    do not have a configuration-error-page defin
    ed.
    Exception[com.bea.p13n.appflow.exception.ConfigurationException: The
    configuration-error-page>> node was not found in the webfl>> ow xml file. for webapp [tools, namespace [admin_main]. While tryingto
    display
    CONFIGURATION ERROR: [Exception[com.bea.p13n
    appflow.exception.ConfigurationException: Bad Namespace - namespace[admin_main]
    is not available for webflow execution. Mak
    e sure the [admin_main.wf] file is deployed in webapp [tools].]],]
    atcom.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processConfigurati
    onError(WebflowExecutorImpl.java:786)
    atcom.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebflowRequ
    est(WebflowExecutorImpl.java:484)
    atcom.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processWebflowRequ
    est(WebflowExecutorImpl.java:419)
    atcom.bea.p13n.appflow.webflow.servlets.internal.WebflowServlet.doGet(WebflowS
    ervlet.java:132)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    atweblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
    l.java:241)
    atweblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
    at jsp_servlet.__index._jspService(__index.java:92)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2495)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    Am i missing any step here???
    can anybody help me????
    thanks
    Vijay

  • Starting visual administrator tool remotely

    Hello guyz , how can we start Visual Admin tool remotely i.e. I had a server but i want to start it from my laptop. (Server and Laptop in the same network). Similarly can we start Config tool remotely

    Hi swapnil chitre,
    Can you send the document to my id <email address deleted by moderator>
    Regards,
    Vamshi.

  • 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

  • Configuration error when open admin tool in BIEE 11g client

    Hi All,
    I have installed BIEE 11g client in my laptop,the version is 11.1.6.2 ,it has show one error in the installation log :
    <action name="Custom Action" target="oracle.bi.CustomIAActionGetInstanceNumber" status="error">
    - <AdditionalNotes>
    <error>class oracle.bi.CustomIAActionGetInstanceNumber.install() runtime exception:</error>
    </AdditionalNotes>
    After installation,when I try to open the admin tool in start menu,it show configuration error , but I can open the admin tool through installation directory.
    And when I try to import metadata,it also shows connection has failed.
    Can any body give some helps on this,thanks a lot.
    Ryan.
    Edited by: 997662 on Apr 5, 2013 1:39 AM

    Hi,
    Let me know which version you are using (OBIEE) ?
    you are trying to install Client (Admin Tool) and OBIEE server in same machine ?
    Thx,

  • Admin tool could not load the essbase driver.Please check the configuration

    Hi All,
    I have obiee11g installed machine and want to connect that machine with essbase.
    For that I have installed Essbase Client [11.1.2.1] by downloading the following files,
    *1>Oracle Hyperion Enterprise Performance Management System Installer Fusion Edition Release 11.1.2.0.0 for Microsoft Windows (32-bit)*
    *2>Hyperion Enterprise Performance Management System Foundation Services Release 11.1.2.0 for Microsoft Windows (32-bit) Part 1 of 4*
    *3>Oracle Essbase Clients Release 11.1.2.0.0 for Microsoft Windows (32-bit)*
    After that I manually added the ESSBASEPATH and ARBORPATH as Environment Variables (USER).
    And also I manually added the essbasepath in bi-init.cmd file.
    Finally I tried to connect essbase with BI through BI Admin Tool, I get the following Error
    "*Admin tool could not load the essbase driver.Please check the configuration*."
    kindly guide me to overcome this issue.
    Thanks and Regards
    sai
    Edited by: 923924 on Apr 24, 2012 5:20 AM

    Until you perform the configuration on the AD server, the following message will appear:
    Error: Could not start the SSO service. Please check the configuration.
    So configure the AD server so that the error message will not appear again.

  • Advanced Configuration in Admin tool

    Hello All,
    Can anybody point me to any documentation or white paper on how to do some advance configurations in the OBI EE Admin tool,like partitioning.
    Basically how can you improve performance by doing partitioning (in database ) in BI EE.

    You can imporve the performance by Creating Indexes, Materialized Views, Partitioning etc...
    Materialized Views: [http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14223/basicmv.htm#g1028195]
    Partitioning: [http://www.oracle.com/technology/oramag/oracle/06-sep/o56partition.html]

  • "Configuration Error" message on launching Admin tool

    Hi
    I installed OBIEE 11g 11.1.1.6 client on windows 7 machine and created a DSN also. When I launch the admin tool. I get "configuration error" message.
    Can someone help in identifying what it is and how to resolve it.
    Regards
    Sunil

    For future readers, I was able to resolve this problem.  Here's how:
    For the "Configuration Error" dialog when doing a stand-alone 64-bit Windows client install, you need to go to the "C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client\oraclebi\orahome\bifoundation\server\bin" directory, change the permissions to the "bi_init.cmd" file so you can edit it, and comment out the line that starts "set ORACLE_INSTANCE".  You'll get a new error dialog when you try to open the tool complaining that the ORACLE_INSTANCE variable is not set, but you can click through it and the tool will work fine.
    For the issue of RPD version 318 vs 320, you need to download the 11.1.1.6.2 version of the client, which has been released as a patch (it's really just a full install).  It's patch 13794002. 
    Good luck!
    Rick

  • 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.
              

  • 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

  • Mac OS X Server 10.4 - connect admin tools from one network to another?

    Hi,
    This may seem quite strange, but I have to do some administration of a server one one network, while being within another one. It seems that if I am able to connect to the internet utside of the office network (e.g. on a public network using wireless), I can just fire upp the mac admin tools and do my work perfectly.
    However, if I try to do the same while connected to the company network (which is governed by a OS X Server), I get nowhere. Can't even get a connection.
    Is there a way to get around this?
    /Fredrik

    I've run the Server Admin tool over a VPN; from a Mac OS X client (with the tools installed) on a remote LAN to a firewall-based VPN end-point. Worked fine; this configuration can work.
    It's possible here that you're encountering subnet routing, as various of the VPN solutions need either send all traffic over the VPN (there's a setting for that), or the local and the target LANs need be in separate and unique subnets. (As is my wont, I typically configure and use an outboard firewall. Not a host-based firewall.)
    So this could be a firewall port or three that need be opened (as mentioned in in earlier reply), or this could be subnet routing.

  • Admin Tools Over Internet

    Is there a way to use the server admin tools to manage a server over the internet when i am not connected to my local network. I use server admin tools while i am on my network, but if i am away i would like to still be able to manage the server. If so what ports do i need to open up to allow this remote connection?

    No problem. To set up an ssh tunnel from a shell, you need to execute ssh like this:
    ssh [email protected] -L 5901:127.0.0.1:5900
    That will tunnel port 5901 on your local host to port 5900 on the remote host through an ssh connection. Once you're logged in (as with a normal ssh connection), you need to start up the vnc server (I don't leave mine running all the time). With OSXvnc installed, this command sets it up in a relatively safe way:
    sudo /Applications/OSXvnc.app/Contents/MacOS/OSXvnc-server -dontdisconnect -swapButtons -nevershared -localhost
    The sudo is not necessary if you are already logged in to the GUI on the remote machine, but otherwise you need root permission to start the VNC service. The -nevershared and -localhost options keep others out of the VNC, and the other options "fix" the mouse inputs and prevent timeout. I've got an alias in my shell configuration for this command, as well as the ssh tunnels.
    That done, open up any VNC client on your local machine (I use chicken of the vnc), and connect to the port you mapped to 5900 on the remote machine. If your client is talking about "Display 0", that's 5900. Display 1 is 5901, and so on. Both can be 5900, but I used 5901 in the example to show which port was remote and which was local.
    If this doesn't do it for you, let me know.

  • 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.

  • 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.

Maybe you are looking for