Opportunity import without other admin tools

Is there a way for me to enable the opportunity import in addition to the typical Marketing Import without the full
admin privilege? When I enable the 'Admin Import' privilege even Oracle Migration Tool On Demand and Oracle Dataloader On Demand
are enabled, which I don't want.

Not at this time. I would recommend that you submit an enhancement request to CRM On Demand customer care.

Similar Messages

  • Metadata export/import to other BI tools?

    Metadata export/import to other BI tools?
    Hi ,
    I am using SQL DM 3.0.0.665. I need your thoughs on following.
    As we build our logical/physical models in SQL data Modeler, we create our metadata for our attributes/columns.
    After creating our physical model, other BI and reporting tools acquire access to the physical tables. Each tool has a process of creating their reporting layer and able to bring the tables/columns into reporting layer. It shows the column names as it is. It is not business friendly.
    Do we have a mechanism to export attribute business names as meta data of DB tables?
    If we define the meta data as part of physical model using modeling tools such as Oracle SQL Developer or ERWIN, will we able to import those into BI tools as report elements meta data?
    Where can I find details?
    How do we do that?
    Thanks in helping us out.

    Hi,
    there is no problem if you are building reports on top of our reporting repository - table DMRS_MAPPINGS holds information for pairs - (entity- table), (attribute-column)...., and you can take implementation and business name.
    Exchange to BI tools - you need to know how particular BI tool can recognize and link implementation and business names and then you can use transformation script in order to provide required information. There are examples on this forum how to deal with files and database connection using transformation script.
    Philip

  • On Import Metadata in Admin Tool get "Connection has failed" error

    Hello,
    I am attempting to import Metadata in Oracle BI Administration Tool v.11.1.1.5 and i get " "Connection has failed" error.
    What is the solution? Thank you in advance, Sonya

    Hi ,
    My server is on Linux 64bit and client is on windows xp
    i m facing the same error as connection has failed.
    below steps are done:
    1.Copy the tnsnames.ora from Oracle Database home (ORACLE_HOME\NETWORK\ADMIN\) to the following locations.
    \OracleBI1\network\admin (Example: C:\OBI\Oracle_BI1\network\admin)
    \oracle_common\network\admin (Example: C:\OBI\oracle_common\network\admin)
    2.Set the TNS_ADMIN environment variable value with one of the copied locations in the step 1 in user.cmd or user.sh file depending on your OS. This file will be found under \instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup (Example : C:\OBI\instances\instance2\bifoundation\OracleBIApplication\coreapplication\setup)
    Can u just me furthere steps for linux server.
    Thanks

  • Hot deploying servlets without the admin tool

              Hey, all! I was wondering if there is a way to hot-deploy
              servlets without using the weblogic admin console.
              With ejbs, this is done through weblogic.deploy
              standalone. Thanks for your help!
              Alex Kagan
              

    WMarks,
    We've done something similar for one or two low-profile apps.
    You can use a tool such as wget ( Wget for Windows ) to download the installer to a known location on the user's workstation, and then run that installer as either a dynamic administrator or the system account in order to perform the installation.
    As others have mentioned, there will always be applications you'll need to find workarounds for if the vendor didn't code their application to be launched as a non-administrative user.
    Along with the least privilege solutions (mostly AD-based), you could investigate options such as VMware ThinApp or ZENworks Application Virtualization for apps that you absolutely have to have run as a non-admin, but remember there is always overhead introduced into the management and deployment process by re-packaging.
    pitcherj

  • About essbase import to admin tool ,at logic layer have not the total layer

    i have import admin tool with a essbase . in the physical layer eg, a demention 'seg' it have the total layer then detail layer.
    but when i drag them to logic layer , demention 'seg' it have not the total layer just only detail layer. i must manual add the total layer
    why ,how can i self-motion have total layer

    i do it myself

  • BI Admin Tool crashes when importing from Essbase

    Hi folks,
    I'm trying to import an Essbase cube into my OBIEE RPD and it is causing the Admin Tool to crash with a generic Windows error msg that "BI Admin Tool has stopped working and Windows is looking for a solution"..
    I'm using OBIEE 10.3.1.4 with all components, including BI Server installed on my local machine which is Windows 7 32-bit. The Essbase server is on a different machine. The RPD is working fine for several other data sources, and crashes only when I try to import from Essbase. The Essbase server is also working fine. The crash happens regardless of whether I'm in online or offline mode. I even tried to create a new RPD in case the other one was corrupted, but even the new one crashes.
    I have Essbase client installed on the same machine as BI Server and my environment variables seem fine. All ports on the Essbase server machine are open and I can ping it from the BI Server machine, so it is not a network issue. I know this version of OBI is not officially supported on Windows 7, but it's working fine in all other respects. Has anyone had a similar problem in the past?
    Appreciate any advise.
    thanks,
    Axe
    Edited by: axe1 on Oct 19, 2010 5:54 AM

    I wonder if cube import only works when using a 32-bit Essbase client?

  • Unable to import metadata using OBI 11g Admin tool

    Hello folks,
    I am new to OBI. I am trying to build a RPD. For that purpose I am trying to import some tables from database but I am unable to. I created DSN and also tried using OCI but no help. The OBI Admin tool client and database is installed under other user's account. Is that the reason I am unable to import tables?
    I am getting this error:
    Internal Error-Unable to initialize NLS during driver load - When I try to use ODBC &
    Connection failed --When I try to use OCI.
    Can someone shed some light on this issue.
    Thanks,
    Edited by: 950330 on Jan 21, 2013 11:17 AM

    Use Call Interface: Default (OCI 10g/11g)
    Data source Name->hostname:port/ServiceName or TNS name
    like
    localhost:1521/XE
    make sure you able to ping connect the database using tnsentry or
    tnsping <tnsname>
    from command prompt.
    Let me know for issues if helps pls mark
    Edited by: Srini VEERAVALLI on Jan 21, 2013 1:17 PM

  • Import metadata from BI Admin tool -OBIEE 11g

    Hi,
    I am trying to import metadata from BI Admin tool 11g (offile- did not start BI services) but it always showing "Connection has failed". I tried ODBC 2.0, ODBC 3.5, OCI11g/10g with different schemas .. But still no luck... I checked all those from Toad and DSN Tests.. then all are successfulll... But in BI Admin Tool only I can not connect to those Datasources.. Where Iam wrong..? any workarounds would be appreciated...
    Thanks and Regards,
    Sri.
    (OBIEE 11.1.1.5, Oracle 11g R2 EE Database, MS Windows XP Professional Edition SP2)

    ORACLE FOLDER
    C:\Oracle\product\11.2.0\client_1\network\admin\sample
    We have tnsnames.ora file in this oracle folder coppy that and save it in
    C:\Oracle\product\11.2.0\client_1\network\admin
    Tnsnames.ora
    This tnsname.ora file should contain the details of
    Data Source name – ORCL
    Host name – xxxx.xxxxxx.com
    Portno - 1531 (This port no is default port in oracle)
    Service Name – ORCL
    OBIEE FOLDER
    C:\OBIEE\oraclebi\orainst\config\OracleBIServerComponent\coreapplication
    Tnsname.ora (need to have this file in the above path which is same in ORACLE FOLDER)
    GOTO – Start – Control panel – Administrative Tool – Data Source(ODBC) in this
    1.     Goto System DSN tab
    2.     Select Add at right side
    3.     A new pop-up window opens – ‘Create New Data Source’
    4.     Select from the list – Oracle in OraClient11g_Home
    5.     A pop-up window opens –‘Oracle ODBC Driver Configaration’ in that
    6.     Data Source name – Mandatory (You can give any name) e.g –ORACLE DSN
    7.     Description – Optional (you can give r leave it blank).
    8.     TNS Service Name – HOST:PORT/Data Source Name e.g –xxxx.xxxxxxx.com:1531/ORCL (xxxx.xxxxxx.com may be IP Address also)
    9.     User ID – Give Database USERID (If you are going to take data from SERVER you have to give Server Data Base USER ID / If you are going to take data from Local Machine use your Local machine database User id ) e.g –USER id – ‘system’ where password is – ‘Manager’

  • Not able to import metadata using BI Admin tool

    Hi folks,
    I've installed OBIEE 11g server(Version 11.1.1.6.0) in my local machine which is lying on Windows 7 environment. Tried importing metadata(Oracle Database) using BI Admin tool, it throws "The Connection has failed" error.
    I've copied TNSNAMES.ora file to the path D:\Oracle\Middleware\Oracle_BI1\network\admin and D:\Oracle\Middleware\oracle_common\network\admin(In D:\Oracle\Middleware\oracle_common\network, admin was not there, I've created a new folder with name admin and placed the TNSNAMES.ora file over there).
    Have modified the user.cmd and bi_init.cmd files in the below path D:\Oracle\Middleware\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup
    Any help would be appreciated
    Regards,
    Arun

    Hi,
    The problem was your tnsnames.ora file your not please in the right path.
    Check this steps:
    Copy the tnsnames.ora from Oracle Database home (ORACLE_HOME\NETWORK\ADMIN\) to the following locations.
    Step 1 - <obiee11g_home>\OracleBI1\network\admin
    Step 2 - <obiee11g_home>\oracle_common\network\admin
    Set the TNS_ADMIN environment variable value with one of the copied locations in the step 1 in user.cmd or user.sh file depending on your OS.
    This file will be found under <obiee11g_home>\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup
    Solution:
    Copy the tnsnames.ora from Oracle Database home (ORACLE_HOME\NETWORK\ADMIN\) to the following locations.
    Step 1 - <obiee11g_home>\OracleBI1\network\admin
    Set the TNS_ADMIN environment variable value with one of the copied locations in the step 1 in user.cmd or user.sh file depending on your OS.
    This file will be found under <obiee11g_home>\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup
    Run User.cmd or User.sh
    Recheck below steps also.
    ORACLE FOLDER
    C:\Oracle\product\11.2.0\client_1\network\admin\sample
    We have tnsnames.ora file in this oracle folder coppy that and save it in
    C:\Oracle\product\11.2.0\client_1\network\admin
    Tnsnames.ora
    This tnsname.ora file should contain the details of
    Data Source name – ORCL
    Host name – xxxx.xxxxxx.com
    Portno - 1531 (This port no is default port in oracle)
    Service Name – ORCL
    OBIEE FOLDER
    C:\OBIEE\oraclebi\orainst\config\OracleBIServerComponent\coreapplication
    Tnsname.ora (need to have this file in the above path which is same in ORACLE FOLDER)
    GOTO – Start – Control panel – Administrative Tool – Data Source(ODBC) in this
    1. Goto System DSN tab
    2. Select Add at right side
    3. A new pop-up window opens – ‘Create New Data Source’
    4. Select from the list – Oracle in OraClient11g_Home
    5. A pop-up window opens –‘Oracle ODBC Driver Configaration’ in that
    6. Data Source name – Mandatory (You can give any name) e.g –ORACLE DSN
    7. Description – Optional (you can give r leave it blank).
    8. TNS Service Name – HOST:PORT/Data Source Name e.g –xxxx.xxxxxxx.com:1531/ORCL (xxxx.xxxxxx.com may be IP Address also)
    9. User ID – Give Database USERID (If you are going to take data from SERVER you have to give Server Data Base USER ID / If you are going to take data from Local Machine use your Local machine database User id ) e.g –USER id – ‘system’ where password is – ‘Manager’
    Note: If still not yer resloved Please read below threds.
    Re: Error in Importing Metadata in OBIEE 11G
    [46028] Unable to get the DLL path for the CLI xx from the NQSConfig.ini
    Award points it is useful.
    Thanks,
    satya

  • SSO between Portal Application and Portal Admin Tool

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

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

  • 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 error: Physical database already exists

    Hello Gurus,
    I am using OBIEE 11.1.1.3 and trying to import a new Essbase ASO cube into my RPD using the Admin Tool. I am getting the error message "Physical database already exists, but it is not of the same provider type". The cube is new and not in my rpd yet so why is it saying it exists? Is there a way to search for it in case it is in there?
    Thanks very much for your help.
    Regards,
    JennC
    Edited by: user754680 on May 13, 2011 5:06 PM

    You can search for the Tables, Cubes, Databases etc that are already in the repository. Just click on tools in the admin tool and select query repository. Here you can select from the drop down list what you are looking for and leave the name as * if you want to search for everything.
    Hope this helps.
    Thanks,
    -Amith.

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

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

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

  • Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.

              Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
              Acelet is the leader in J2EE tools area. If you google "j2ee tools",
              "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
              is at the top of the result.
              Super 4.00 comes with:
              SuperEnvironment
              SuperLogging
              SuperPeekPoke
              SuperReport
              SuperScheduler
              SuperStress
              and SuperPatrol, as a schedule job.
              The evaluation edition can be anonymously downloaded from:
              http://www.ACElet.com.
              Super is a component based monitor and administration tool
              for EJB/J2ee. It provides built-in functionality as well as
              extensions, as SuperComponents. Users can install
              SuperComponents onto it, or uninstall them from it.
              Super has the following functions:
              * A J2EE monitor.
              * A gateway to J2EE/EJB servers from different vendors.
              * A framework holding user defined SuperComponents.
              * A full-featured J2EE logging and J2EE tracing tool for centralized,
              chronological logging.
              * An EJB tool for Peeking and Poking attributes from EJBs.
              * An EJB Stress test tool.
              * A J2EE global environment tool.
              * A J2EE report tool.
              * A J2EE Scheduler tool.
              * A J2EE Business patrol tool.
              It is written entirely in the Java(TM) programming language.
              The current version support:
              * JOnAS 2.4 and 2.6
              * SunONE 7.0
              * Universal servers.
              * Weblogic 6.1, 7.0 and 8.1
              * Websphere 4.0 and 5.0.2
              * jBoss 3.0 and 3.2
              ********** What is new:
              Version 4.00 November, 2003
              Enhancement:
              1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
              (with/without proxy) protocol mode for SuperEnvironment,
              SuperLogging, SuperReport and SuperScheduler.
              2. SuperLogging 4.00: tracing can work on both live database and retired database.
              3. SuperReport 3.00: works for both live database and retired database.
              4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
              Panel.
              Bug fix:
              1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
              Version 3.00 July, 2003
              Enhancement:
              1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
              scope,
              with enhancements and bug fixes.
              2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
              password.
              Add MenuTreePanel.
              3. Improved GUI and document.
              4. Add support to WebLogic 8.1.
              Bug fix:
              1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
              2. SuperScheduler 2.0: Startup should never be reported as missed.
              3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
              Version 2.20 Jan. 2003
              Enhancement:
              1. Add desktop and start menu shortcuts for MS-Windows.
              2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
              3. SuperLogging 2.40: Add new sendAlarmEmail() method.
              4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
              direct database is not practical; Allow user to choose
              favorite logging software; Add Last day as Monthly
              repeating attribute.
              Change:
              1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
              Bug fix:
              1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
              open Environment Manager.
              2. SuperLogging client 1.52: Annoying exception thrown when you use
              JDK 1.4 (the program runs okay).
              3. SuperPeekPoke 1.61: Fix bug where input object contains
              java.lang.Double and alike.
              4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
              PatrolAlarm for SuperPatrol; Composite task with members;
              Non-scheduled run on other host; Around edges of last
              days in Monthly with holiday policy.
              Version 2.10 July 2002
              Enhancement:
              1. SuperScheduler 1.3: Add Future View to check future schedule in
              both text and Gantt-chart mode.
              2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
              activities.
              3. SuperEnvironment 1.3: uses new graphic package adding print and
              preference facilities.
              4. SuperPeekPoke 1.6: uses new graphic package adding print and
              preference facilities.
              5. SuperStress 1.21: uses new graphic package.
              Bug fix:
              1. SuperStress 1.21: fixed graphic related bugs.
              Version 2.01 June 2002
              Enhancement:
              1. Add options for Look & Feel.
              2. Preference is persistent now.
              Bug fix:
              1. Installation for WebLogic 7.0: extEnv may not be installed on the
              right place, so SuperLibrar on the server side was not loaded and
              causes other problems.
              Version 2.00 June 2002
              Enhancement:
              1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
              when any Doer causes things to change.
              2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
              3. SuperReport 1.2: Support default HTML browser for reading HTML document.
              4. Support WebLogic 7.0.
              5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
              6. SuperEnvironment 1.21: New SuperEnvironment tour.
              Bug fix:
              1. WebSphere Envoy did not always list all JNDI names.
              Version 1.90 May 2002
              Enhancement:
              1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
              2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
              effective period. Add Patrol job type as SuperPatrol.
              3. Add support for both JOnAS and jBoss.
              4. Add more elements on Report criteria.
              Change:
              1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
              and descend.
              2. New log database.
              Bug fix:
              1. Alert email should be sent once in the interval, regarding number of servers
              in the clustering.
              2. Minor bug fixes to make errors handled better on SuperLogging.
              3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
              them.
              4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
              Version 1.80 March 2002
              Enhancement:
              1. Add new component: SuperScheduler
              Bug fix:
              1. SuperLogging: Verbose should ignore class registration.
              2. SuperLogging-tracing: an exception was thrown if the java class without package
              name.
              Version 1.70 January 2002
              Enhancement:
              1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
              weblogic 6.1, need download an application).
              2. Add alias names for log threshold as new Java suggests.
              3. New component: SuperReport.
              Change:
              1. SuperLogging: Log database parameters are specified in a properties file, instead
              of EJB's deployment descriptor. It is more convenient and it avoids some potential
              problems. No change for development, easier for administration.
              Bug fix:
              1. Add Source Path Panel now accepts both directory and jar file.
              2. Bug in SuperEnvironment example (for version 1.60 only).
              Version 1.60 December 2001
              Enhancement:
              1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
              2. Add timeout parameter to logging access.
              3. New installation program with A). Easy install. B). Remote command line install.
              4. Support EJB 2.0 for Weblogic 6.1.
              5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
              was supported since version 1.5).
              Change:
              1. Poke: argument list is set at define time, not invoke time.
              2. Default log database change to server mode from web server mode, booting performance
              to 10-20 times.
              Bug fix:
              1. If the returned object is null, Peek did not handle it correctly.
              2. If the value was too big, TimeSeries chart did not handle it correctly. Now
              it can handle up to 1.0E300.
              3. Help message was difficult to access in installation program.
              4. Source code panel now both highlights and marks the line in question (before
              it was only highlight using JDK 1.2, not JDK 1.3).
              5. Delete an item on PeekPoke and add a new one generated an error.
              Version 1.50 August, 2001
              Enhancement:
              1. Source code level tracing supports EJB, JSP, java helper and other
              programs which are written in native languages (as long as you
              write correct log messages in your application).
              2. Redress supports JSP now.
              3. New installation with full help document: hope it will be easier.
              4. Support WebSphere 4.0
              Version 1.40 June, 2001
              Enhancement:
              1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
              and PieView for GlobalProperties.
              GlobalProperties is an open source program from Acelet.
              2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
              Changes:
              1. The structure of log database changed. You need delete old installation and
              install everything new.
              2. The format of time stamp of SuperLogging changed. It is not locale dependent:
              better for report utilities.
              3. Time stamp of SuperLogging added machine name: better for clustering environment.
              Bug fix:
              1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
              Style Panel may not show up.
              Version 1.30 May, 2001
              Enhancement:
              1. Add ConnectionPlugin support.
              2. Add support for Borland AppServer.
              Version 1.20 April, 2001
              Enhancement:
              1. Redress with option to save a backup file
              2. More data validation on Dump Panel.
              3. Add uninstall for Super itself.
              4. Add Log Database Panel for changing the log database parameters.
              5. Register Class: you can type in name or browse on file system.
              6. New tour with new examples.
              Bug fix:
              1. Redress: save file may fail.
              2. Install Bean: some may fail due to missing manifest file. Now, it is treated
              as foreign beans.
              3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
              on the original file, do not need copy to a temporary directory anymore.
              4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
              Now it pick up all availble ones and give warning messages.
              5. Stress: Launch>Save>Cancel generated a null pointer exception.
              Changes:
              1. installLogDatabase has been changed from .zip file to .jar file.
              2. SuperLogging: If the log database is broken, the log methods will not try to
              access the log database. It is consistent with the document now.
              3. SuperLogging will not read system properties now. You can put log database
              parameters in SuperLoggingEJB's deployment descriptor.
              Version 1.10 Feb., 2001
              Enhancement:
              1. Re-written PeekPoke with Save/Restore functions.
              2. New SuperComponent: SuperStress for stress test.
              3. Set a mark at the highlighted line on<font size=+0> the Source Code
              Panel (as a work-a-round for JDK 1.3).</font>
              4. Add support for WebLogic 6.0
              Bug fix:
              1. Uninstall bean does physically delete the jar file now.
              2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
              Version 1.00 Oct., 2000
              Enhancement:
              1. Support Universal server (virtual all EJB servers).
              2. Add Lost and Found for JNDI names, in case you need it.
              3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
              for Envoys which do not support JNDI list).
              Version 0.90: Sept, 2000
              Enhancement:
              1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
              and alike) as input values.
              2. Reworked help documents.
              Bug fix:
              1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
              further time-out.
              2. MDI related bugs under JDK 1.3.
              Version 0.80: Aug, 2000
              Enhancement:
              1. With full-featured SuperLogging.
              Version 0.72: July, 2000
              Bug fix:
              1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
              Version 0.71: July, 2000
              Enhancement:
              1. Re-worked peek algorithm, doing better for concurent use.
              2. Add cacellable Wait dialog, showing Super is busy.
              3. Add Stop button on Peek Panel.
              4. Add undeploy example button.
              Bug fix:
              1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
              1.2 and 1.3
              Version 0.70: July, 2000
              Enhancement:
              1. PeekPoke EJBs without programming.
              Bug fix:
              1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
              Changes:
              1. All changes are backward compatible, but you may need to recompile monitor
              windows defined by you.
              Version 0.61: June, 2000
              Bug fix:
              1. First time if you choose BUFFER as logging device, message will not show.
              2. Fixed LoggingPanel related bugs.
              Version 0.60: May, 2000
              Enhancement:
              1. Add DATABASE as a logging device for persistent logging message.
              2. Made alertInterval configurable.
              3. Made pace for tracing configurable.
              Bug fix:
              1. Fixed many bugs.
              Version 0.51, 0.52 and 0.53: April, 2000
              Enhancement:
              1. Add support to Weblogic 5.1 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Context sensitive help is available for most of windows: press F1.
              2. Fix installation related problems.
              Version 0.50: April, 2000
              Enhancement:
              1. Use JavaHelp for help system.
              2. Add shutdown functionality for J2EE.
              3. Add support to Weblogic 4.5 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Better exception handling for null Application.
              Version 0.40: March, 2000
              Enhancement:
              1.New installation program, solves installation related problems.
              2. Installation deploys AceletSuperApp application.
              3. Add deploy/undeploy facilities.
              4. Add EJB and application lists.
              Change:
              1.SimpleMonitorInterface: now more simple.
              Version 0.30: January, 2000
              Enhancement:
              1. Add realm support to J2EE
              2. Come with installation program: you just install what you want
              the first time you run Super.
              Version 0.20: January, 2000
              Enhancement:
              Add support to J2EE Sun-RI.
              Change:
              1. Replace logging device "file" with "buffer" to be
              compliant to EJB 1.1. Your code do not need to change.
              Version 0.10: December, 1999
              Enhancement:
              1. provide SimpleMonitorInterface, so GUI experience is
              not necessary for developing most monitoring applications.
              2. Sortable table for table based windows by mouse
              click (left or right).
              Version 0.01 November., 1999:
              1. Bug fix: An exception thrown when log file is large.
              2. Enhancement: Add tour section in Help information.
              Version 0.00: October, 1999
              Thanks.
              

  • BI Admin Tool and XSLT transformation for XML data source - How it works ?

    Hello,
    There is a possibility to import data from XML data source using BI Admin Tool.
    In the import window we can point XSLT file. What is the purpose of that XSLT field?
    Why I am asking ?
    I thought it is smth like XSLT processor, but simply it doesnt work.
    What I did:
    - I pointed XML data source file
    - I pointed XSLT transformation file
    - Click OK, and still get the message that the XML file structure is not supported
    After that I transformed that XML file with some desktop XSLT processor using the same XSLT file, and I tried to connect that file directly using BI Admin tool.Then it works. So it means that the transformation is ok.
    So basically one question comes to my mind in that situation:
    What is the purpose of XSLT field in BI Admin Tool when it comes to XML data source ?
    (it doesnt look like XSLT processor)
    Greetings
    /Michal

    Hi Mariano
    Why you need to use XSLT for transforming XML file into ABAP table
    Code is a part of some ABAP report. Looks like it is reading a file from file system and updating table after transformation
    If you have requirement like you need to read XML file and then insert the data into a SAP table
    You can use
    File to RFC
    File to Proxy scenario using SAP PI.
    Please provide more inputs on requirement to help
    Thanks
    Gaurav

Maybe you are looking for