TREX Admin Tool (Stand-Alone)

Hello-
I am new to the forums, so if I am posting in a wrong area please let me know so I can correct this; thanks in advance for your patience.
Now the question.  I am interested in using the TREX Admin Tool (Stand-Alone) to manage our multiple TREX 7.0 and TREX 7.1 systems.  Can anyone tell me where I go in the market place to download this tool and any links to the documentation on this tool. 
I have already found SAP Note 766516 and the following link on help.sap.com on the subject:
http://help.sap.com/saphelp_nw04s/helpdata/en/40/1726d3aef809b8e10000000a114cbd/content.htm
Any and all input, suggestions, help, flames, etc. are greatly appreciated.
Kind Regards,
Nathan Sunderman
SAP Enterprise Team
Dept of Information Services
State of Washington
Computer Services Division
[email protected]
~~

Hi Nathan,
the Python based TREX admin tool (stand-alone) is part of the TREX 7.0/7.1 installation. You do not need to download it seperately, when you have downloaded and installed TREX.  Note that also a transaction TREXADMIN exist by which you can start the ABAP based version of the TREX admin tool in the SAP System if you are using TREX by an ABAP application via RFC.
For docu how to start and how to use the TREX 7.0 admin tools see:
http://help.sap.com/saphelp_nw70/helpdata/en/3f/fcb705c1ce131fe10000000a114cbd/frameset.htm
There will be also an admin docu about using TREX 7.1 by NW 7.0 applications. This docu will be available on SAP Help Portal as of NW 7.0 SP14 during January.
For the most current info + docu about TREX and TREX configuration see also:
SAP Service Marketplace:
https://service.sap.com/instguides
--> SAP NetWeaver --> SAP NetWeaver 7.0 (2004s) -->  Installation -->  3 - Installation - Standalone Engines --> SAP NetWeaver Search and Classification TREX
There you find the Installation & Implementation Documentation Center for TREX 7.0 and TREX 7.1 with links to the TREX install guides for installing and configuring single host as well as multiple hosts landscapes. Note the prerequisites for using TREX 7.1 by NW 7.0 applications.
See also the SAP internal TREX Portal
http://trex.wdf.sap.corp:1080
for most current info about TREX.
Regards,
Ralph Schroeder/TREX documentation

Similar Messages

  • Standalone Trex Admin Tool

    How do I access SA Treax Admin tool. I'm in a sandbox env.
    Thanks

    Hi,
    Check the links below.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/fcb705c1ce131fe10000000a114cbd/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/40/1726d3aef809b8e10000000a114cbd/content.htm
    Regards.

  • Can the Admin Tool be run as a standalone app?

    Can the Admin Tool run without logging into a Dispatch Workstation?

    Yes it can.
    In fact you actually side step licensing issues by doing this because "technically" you are
    not running a dispatcher workstation and therefore don't need to pay for another license.
    The file to run is usually located in: DispatchStation\AdminTools and is called: ResourceManager.exe
    You would need to take EVERYTHING from the AdminTools directory to run the tool.
    You'd also want to make sure that the config file: ResourceManager.exe.config still makes
    sense for the machine that you are on.
    One word of caution: Running the Admin tool stand-alone is not really encouraged. Not a lot
    of testing has been done in this regard and you may run into issues that have not been
    seen when the admin tool is run as part of the dispatcher workstation.
    I'm not sure if the stand-alone admin tool is even officially supported.
    I CAN say that much of the functionality that you see from the too when it is run as part of the DW
    does work when it is stand-alone, just don't expect 100%.

  • Is it possible to install admin tool alone in windows 7 64 bit software

    hi,
    is it possible to install admin tool alone in windows 7 64 bit software. if so please let me knw where to get the software.thanks in advance

    Aswin,
    Yes, it is possible.
    You may download the Oracle bi 11g client tools here,
    http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/bus-intelligence-11g-165436.html
    ...you'll simply need the Oracle Business Intelligence Developer Client Tools Installer (11.1.1.5.0)
    Please award points if this was helpful or the correct answer to your question.

  • JNDI lookup of stand alone Entity Bean?

    Hi,
    I am attempting to lookup an Entity EJB from within a web app that was deployed as a separate EJB Module. (As far as I understand, multiple web applications should be able to reference EJB's that are deployed independantly within their own EJB modules.)
    To verify this works, I am using the sample "simple CMP EJB" sample that is pacakged with the App Server install.
    First, I deployed the 'cmp-simpleEjb.jar' as a stand alone EJB-Module using the web admin tool. It loads/deploys with no problem.
    Next, I create my own simple web app, and include the following relevant code in my Servlet:
    InitialContext ctx = new InitialContext();
    Object obj = ctx.lookup("ejb/MyProduct");
    ProductHome pHome = (ProductHome)PortableRemoteObject.narrow(obj,ProductHome.class);
    My web.xml includes an ejb-ref:
    <ejb-ref>
    <ejb-ref-name>ejb/MyProduct</ejb-ref-name>
    <ejb-ref-type>Entity</ejb-ref-type>
    <home>samples.ejb.cmp.simple.ejb.Product</home>
    <remote>samples.ejb.cmp.simple.ejb.ProductHome</remote>
    </ejb-ref>
    My sun-wevb.xml incudes an ejb-ref:
    <ejb-ref>
    <ejb-ref-name>ejb/MyProduct</ejb-ref-name>
    <jndi-name>ejb/MyProduct</jndi-name>
    </ejb-ref>
    When I deploy my web app and call the Servlet from a browser, an Excpetion is thrown with a message "null". Can anyone please help me understand what is going on here?

    I added the Remote/Home interfaces into my web app's /WEB-INF/lib folder (jar-ed up of course) and now the Servlet fails with the following stack trace:
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: java.lang.ClassCastException
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at com.etango.testejb.struts.HomeAction.perform(Unknown Source)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1787)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:723)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:444)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:123)
    [25/Mar/2003:23:27:32] WARNING ( 527): CORE3283: stderr: at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:138)
    Are you supposed to package the Home/Remote interface classes with the web app if referencing a independantly deployed EJB?

  • How do I reuse the existing stand-alone CFM application codes on J2EE CF9

    Hi all,
    Our ColdFusion installation runs on a stand-alone ColdFusion server. Now we would like to upgrade to ColdFusion 9 with J2EE configuration. Is there a way to 'reuse' the existing ColdFusion application codes on the ColdFusion J2EE, WITHOUT moving these codes into a location under the J2EE?
    To clarify my question:
    The existing CFM application structure looks like this:
    D:\MyCFApp\folder1\....
    Under J2EE, the folder structure looks like this:
    D:\MyJ2EEHomeDirectory\Adobe_ColdFusion_9.ear\cfusion.war\...
    I would like to keep the CF application codes under D:\MyCFApp\folder1\....
    I can bring up the CF9 Admin Console just fine. What I would like to see is if there's a way for CF9 to recognize the folders OUTSIDE the J2EE directory structure.
    I tried the adding some Mappings on the CF9 Admin Console but no luck.
    Any advice/input is greatly appreciated!

    The solution is not in CF Admin mappings, but rather in web server mappings. You need to tell your web server how/where to find the CFML files, and then configure the web server (using the CF web server configuration tool) to have it hand CF pages to CF for processing.
    You may find helpful information in 2 of the CF docs, the Installation guide, and the Administration and Configuration guide. If you visit any page of the CF9 docs, you'll see all the manuals listed on the left.
    That said, the J2EE configuration is the least well-documented of them all, since things can change from app server to app server. You've not even said which app server you're using: jboss, tomcat, glassfish, resin, weblogic, websphere? And each of those have different support for various web servers. So there's a limit to how much Adobe will document about getting such things working.
    Also, relatively few in the CF community use the J2EE deployment--and many who do only "play with it", so may only use the built-in dev web servers that many app servers come with. When it comes to configuring things for production and integration with real web servers, they may not have any experience to share.
    But if after reading the above you have more specific questions, fire away and perhaps some here can help.
    /charlie

  • Starting Oracle 8i listener when under stand alone Windows NT 4.0 workstation.

    Hi,
    I am finding it difficult to start oracle listener under a stand alone Windows NT4.0 workstation. My NT machine is stand alone and not connected to any n/w. Since I was not able to bring up listener, I was not able to create any database. I have installed Oracle8i Enterprise Edition on my machine. Please help.
    -- Shesha

    Dear Philip,
    I have attached the listener.ora and tnsnames.ora.
    listener.ora
    # LISTENER.ORA Network Configuration File: D:\Oracle\Ora81\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    (ADDRESS = (KEY = EXTPROC0))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = ASHWIN)(PORT = 1521))
    (DESCRIPTION =
    (PROTOCOL_STACK =
    (PRESENTATION = GIOP)
    (SESSION = RAW)
    (ADDRESS = (PROTOCOL = TCP)(HOST = ASHWIN)(PORT = 2481))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\Oracle\Ora81)
    (PROGRAM = extproc)
    (SID_DESC =
    (GLOBAL_DBNAME = ashwin.sheernali)
    (ORACLE_HOME = D:\Oracle\Ora81)
    (SID_NAME = ashwin)
    tnsnames.ora
    ASHWIN.SHEERNALI =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = ASHWIN)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = ashwin.sheernali)
    Also, I am getting the following error messages when tried with "lsnrctl start" command at command prompt.
    TNSLSNR for 32 bit Windows version 8.1.6.00 - Production
    System parameter file is D:\Oracle\Ora81\network\admin\listener.ora
    Log Message written to D:\Oracle\Ora81\network\log\listener.log
    Listening on (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC0IPC)))
    Attempted to listen on (DESCRIPTION=(ADDRESS=(KEY=EXTPROC0)))
    TNS-12538: TNS: no such protocol adapter
    TNS-12560: TNS: protocol adapter error.
    TNS-00508: No such protocol adapter.
    Thanks for everything.
    I will use the simplest forms of listener.ora and tnsnames.ora, as suggested in your mail and try tonight.
    -Shesha
    null

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

  • Shutting Down CF8 Stand-Alone Version on Windows

    I have installed CF8 Developer Version with Stand-Alone
    server on WXP. Would like to upgrade to 8.0.1. During upgrade,
    updater tells me I needs to shut down server and Windows services
    to perform upgrade. Looked around in CFIDE Admin for instructions
    on how to shut down. Couldn't find any.
    How to do?
    Thanks in advance.

    You should start or stop Coldfusion as a Windows service. You
    do so in the Control Panel. Navigate to
    Administrative Tools => Services. Right-click on
    Coldfusion 8 Application Server. To shut down, select
    Stop.

  • SAP PI Installation on Stand alone machine

    Hi,
    Thanks to one and all for having such a nice forum as it has answer to all the questions which I have posted.
    I have been given a very interesting work for anlying if SAP PI could be installed on a standalone machine without having any SAP box. My requirement is to install SAP PI tool for non SAP integration.
    I will distribute my question in 2 parts
    1. Can I install SAP PI in a stand alone desktop?
    2. Is is important to have a SAP R/3 system to install SAP PI tool?
    Please do share your thoughts and if possible please share the document which could be used as proof.
    Thanks in advance.
    Gautam

    1. Can I install SAP PI in a stand alone desktop?
    Yes.
    2. Is is important to have a SAP R/3 system to install SAP PI tool?
    No.
    If you are trying to install 7.1 then have a look at the video blog (easily available on SDN) for the same....will help you.
    Regards,
    Abhishek.

  • Calling a web service through SSL via a stand alone java class

    HI,
    I am trying to call a web service through SSL via a simple stand alone java client.
    I have imported the SSL certificate in my keystore by using the keytool -import command.
    Basically I want to add a user to a group on the server. Say I add a user user 1 to group group 1 using an admin userid and password. All these values are set in an xml file which I send to the server while calling the server. I pass the web service URL, the soap action name and the xml to post as the command line arguments to the java client.
    My xml file(Add.xml) that is posted looks like :
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope
    xmlns:xsi = "http://www.w3.org/1999/XMLSchema-instance"
    xmlns:SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd = "http://www.w3.org/1999/XMLSchema"
    SOAP-ENV:encodingStyle = "http://schemas.xmlsoap.org/soap/encoding/">
    <SOAP-ENV:Body>
    <namesp1:modifyGroupOperation xmlns:namesp1 = "/services/modifyGroup/modifyGroupOp">
    <auth>
    <user>adminUser</user>
    <password>adminPassword</password>
    </auth>
    <operationType>ADD</operationType>
    <groupName>group1</groupName>
    <users>
    <userName>user1</userName>
    </users>
    </namesp1:modifyGroupOperation>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    I call the client as:
    java PostXML https://com.webservice.com/services/modifyGroup "/services/modifyGroup/modifyGroupOp" Add.xml
    I my client, I have set the following:
    System.setProperty("javax.net.ssl.keyStore", "C:\\Program Files\\Java\\jre1.5.0_12\\lib\\security\\cacerts");
    System.setProperty("javax.net.ssl.keyStorePassword", "password");
    System.setProperty("javax.net.ssl.trustStore", "C:\\Program Files\\Java\\jre1.5.0_12\\lib\\security\\cacerts");
    System.setProperty("javax.net.ssl.trustStorePassword", "password");
    But when I try to execute the java client, I get the following error:
    setting up default SSLSocketFactory
    use default SunJSSE impl class: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
    class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl is loaded
    keyStore is : C:\Program Files\Java\jre1.5.0_12\lib\security\cacerts
    keyStore type is : jks
    keyStore provider is :
    init keystore
    init keymanager of type SunX509
    trustStore is: C:\Program Files\Java\jre1.5.0_12\lib\security\cacerts
    trustStore type is : jks
    trustStore provider is :
    init truststore
    adding as trusted cert:
    init context
    trigger seeding of SecureRandom
    done seeding SecureRandom
    instantiated an instance of class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
    main, setSoTimeout(0) called
    main, setSoTimeout(0) called
    %% No cached client session
    *** ClientHello, TLSv1
    RandomCookie: GMT: .....
    Compression Methods: { 0 }
    [write] MD5 and SHA1 hashes: len = 73
    main, WRITE: TLSv1 Handshake, length = 73
    [write] MD5 and SHA1 hashes: len = 98
    main, WRITE: SSLv2 client hello message, length = 98
    [Raw write]: length = 100
    [Raw read]: length = 5
    [Raw read]: length = 58
    main, READ: TLSv1 Handshake, length = 58
    *** ServerHello, TLSv1
    %% Created: [Session-1, SSL_RSA_WITH_RC4_128_MD5]
    ** SSL_RSA_WITH_RC4_128_MD5
    [read] MD5 and SHA1 hashes: len = 58
    [Raw read]: length = 5
    [Raw read]: length = 5530
    main, READ: TLSv1 Handshake, length = 5530
    *** Certificate chain
    chain [0] = ...
    chain [1] = ...
    chain [2] = ...
    chain [3] = ...
    main, SEND TLSv1 ALERT: fatal, description = certificate_unknown
    main, WRITE: TLSv1 Alert, length = 2
    [Raw write]: length = 7
    0000: 15 03 01 00 02 02 2E .......
    main, called closeSocket()
    main, handling exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    main, called close()
    main, called closeInternal(true)
    main, called close()
    main, called closeInternal(true)
    main, called close()
    main, called closeInternal(true)
    Exception in thread "main" javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.c
    ertpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source)
    at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source)
    at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(Unknown Source)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source)
    at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
    at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(Unknown Source)
    at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source)
    at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
    at java.io.BufferedOutputStream.flush(Unknown Source)
    at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:506)
    at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2110)
    at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1088)
    at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
    at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
    at PostXML.main(PostXML.java:111)
    Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find v
    alid certification path to requested target
    at sun.security.validator.PKIXValidator.doBuild(Unknown Source)
    at sun.security.validator.PKIXValidator.engineValidate(Unknown Source)
    at sun.security.validator.Validator.validate(Unknown Source)
    at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
    at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(Unknown Source)
    ... 18 more
    Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source)
    at java.security.cert.CertPathBuilder.build(Unknown Source)
    ... 23 more
    I do not know where I have gone wrong. Could someone point out my mistake.
    Thanks In advance!

    Hi jazz123,
    There's an example in the [*Java Web Services Tutorial*|http://java.sun.com/webservices/docs/2.0/tutorial/doc/] : see Chapter 1: Building Web Services with JAX-WS - A Simple JAX-WS Client.

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

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

  • Help needed in Authenticating Users via A Stand-Alone Web_Application

    Hi all,
    I've just begun to explore the Human Workflow Services in the Oracle SOA Suite...
    I want to create a BPEL Process with a Human Workflow involving 2 users say, P1 & P2 ( which i have configured to be in the default "realm", say..)
    Could Anyone please help me in the Steps to be followed to implement a Stand-Alone Web-Application (or a Web-Service for that matter) that i can use to Authenticate P1 & P2...!
    It's Just like the WorkList Application...but i'm stuck with issues of HOW to Use the IWorkflowContext interface in an External web-application...say deployed on TomCat..?!?
    Once P1 or P2 logs-in...i then plan to show them their tasks (like the WorkList)...& then try & Invoke/trigger a Human task by making a call to the WebService representing the BPEL process...!
    Awaiting a Speedy guidance from Some one...
    [I'm wondering if i can develope some OTHER kind of a UI for a Human Workflow...that's Why..?! :)]
    Thanks in advance...

    I create soft links via ln -s to the environment scripts:
    lrwxrwxrwx 1 oracle dba 43 2005-02-10 20:29 vis9.env -> /lv03/oracle/vis9db/9.2.0/vis9_socrates.env
    lrwxrwxrwx 1 applmgr appl 33 2005-02-10 20:27 vis9.env -> /lv03/oracle/vis9appl/APPSORA.env
    So in oracle user home directory, I type ln -s /lv03/oracle/vis9db/9.2.0/vis9_socrates.env vis9.env
    Then just type . vis9.env to take on the database environment as the oracle user.
    In the applmgr home directory, I type ln -s /lv03/oracle/vis9appl/APPSORA.env vis9.env
    Then just type . vis9.env as applmgr, to assume the applications environment. You will need to be in this environment to start/stop the applications.
    cd to $OAD_TOP/admin/scripts/*
    to stop:
    ./adstpall.sh apps/apps
    to start:
    ./adstrtal.sh apps/apps
    .

  • Etherchannel showing down (SD) and ports are in "I" stand alone state

    Hi,
    Netapp server is connected to switch 6500 via trunk.
    I configured a portchannel but it showing as down.take a look ar below output..
    interface Port-channel248
    description Netapp-server-1 po248
    switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 903
    switchport mode trunk
    switchport nonegotiate
    no ip address
    no shut
    interface GigabitEthernet3/33
    description server-1
      switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 903
    switchport mode trunk
    switchport nonegotiate
    no ip address
    speed 1000
    udld port aggressive
    spanning-tree portfast
    channel-group 248 mode active
    no shut
    interface GigabitEthernet4/33
    description cnndcfasp002a-e5d
      switchport
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 903
    switchport mode trunk
    switchport nonegotiate
    no ip address
    speed 1000
    udld port aggressive
    spanning-tree portfast
    channel-group 248 mode active
    no shut
    Switch-6500#sh etherchannel summary
    Flags:  D - down        P - bundled in port-channel
            I - stand-alone s - suspended
            H - Hot-standby (LACP only)
            R - Layer3      S - Layer2
            U - in use      f - failed to allocate aggregator
            M - not in use, minimum links not met
            u - unsuitable for bundling
            w - waiting to be aggregated
    Number of channel-groups in use: 5
    Number of aggregators:           5
    Group  Port-channel  Protocol    Ports
    ------+-------------+-----------+-----------------------------------------------
    248    Po248(SD)       LACP      Gi3/33(I)  Gi4/33(I) 
    #sh etherchannel detail
    Group: 248
    Group state = L2
    Ports: 2   Maxports = 16
    Port-channels: 1 Max Port-channels = 16
    Protocol:   LACP
    Minimum Links: 0
                    Ports in the group:
    Port: Gi3/33
    Port state    = Up Sngl-port-Bndl Mstr Not-in-Bndl
    Channel group = 248         Mode = Active      Gcchange = -
    Port-channel  = null        GC   =   -         Pseudo port-channel = Po248
    Port index    = 0           Load = 0x00        Protocol =   LACP
    Flags:  S - Device is sending Slow LACPDUs   F - Device is sending fast LACPDUs.
            A - Device is in active mode.        P - Device is in passive mode.
    Local information:
                                LACP port     Admin     Oper    Port        Port
    Port      Flags   State     Priority      Key       Key     Number      State
    Gi3/33    SA      indep     32768         0xF8      0xF8    0x321       0x7D 
    Age of the port in the current state: 0d:02h:04m:58s
    Port: Gi4/33
    Port state    = Up Sngl-port-Bndl Mstr Not-in-Bndl
    Channel group = 248         Mode = Active      Gcchange = -
    Port-channel  = null        GC   =   -         Pseudo port-channel = Po248
    Port index    = 0           Load = 0x00        Protocol =   LACP
    Flags:  S - Device is sending Slow LACPDUs   F - Device is sending fast LACPDUs.
            A - Device is in active mode.        P - Device is in passive mode.
    Local information:
                                LACP port     Admin     Oper    Port        Port
    Port      Flags   State     Priority      Key       Key     Number      State
    Gi4/33    SA      indep     32768         0xF8      0xF8    0x421       0x7D 
    Age of the port in the current state: 0d:02h:04m:58s
                    Port-channels in the group:
    Port-channel: Po248    (Primary Aggregator)
    Age of the Port-channel   = 7d:16h:30m:16s
    Logical slot/port   = 14/3          Number of ports = 0
    Port state          = Port-channel Ag-Not-Inuse
    Protocol            =   LACP
    Any one please let me know what is the issue here...
    Thanks
    Gautham

    Exactly, the 6500 config is fine, probably the NETAPP is not active or passive and it's just ON that won't work
    show lacp 248 neighbor will show if you have a neighbor and if the LACP id is the same on both ports
    Core1#sh lacp 2 neighbor
    Flags:  S - Device is requesting Slow LACPDUs
            F - Device is requesting Fast LACPDUs
            A - Device is in Active mode       P - Device is in Passive mode
    Channel group 2 neighbors
    Partner's information:
              Partner Partner   LACP Partner  Partner   Partner  Partner     Partner
    Port      Flags   State     Port Priority Admin Key Oper Key Port Number Port State
    Gi1/7/10  SA      bndl      32768         0x0       0x1      0x11A       0x3D
    Gi2/7/10  SA      bndl      32768         0x0       0x1      0x31D       0x3D
    cheers

Maybe you are looking for