Essbase Applications through EPMA - Advantages and Disadvantages over EAS

Hi,
Does anybody has any documentation highlighting the Advantages/Disadvantages of EPMA over EAS Console for Essbase Applications.
Thank you
Ashok

Hi,
my advice is to go for CSV anytime compared to XML.
XML is first made available to the BW system via  SOAP ( Simple Object Acess protocol) interface. Next it is updated into the required data targets as before , Via a data source for the myself source system.
SOAP = XML+HTTP.
XML cannot be used for mass data. It is only to load small data into SAP BW on a single document level.
BW provides flat file interface so, there is no all these hassles in case of CSV. go for CSV

Similar Messages

  • Advantages and disadvantages of SOAP over Http

    Hi!
    Can any one explain about advantages and disadvantages of SOAP over HTTP.
    Thanks
    Sreenath

    Hi,
    Yes you can use RMI to communicate to your soa suite server allthough i could not get it to work from weblogic 10.3, there is a conflict with certain other libraries. From any other 10.1.3 oracle application server there should not be any problem. The biggest advantage of RMI over SOAP is performance. The soap client also generates lots of logging which can not be disabled, ... i already logged a bug on that. The advantage of SOAP over RMI is its underlying HTTP protocol which is, in some cases, the only protocol allowed by network engineers to pass through firewalls.
    Kind Regards,
    Andre

  • Advantages and Disadvantages of  Applet over JSP/servlet

    Can some one please let me know what are the major advantages and disadvantages of using Applets over JSP/Servlet technology?

    Well, a servlet / jsp is generated on the server, an applet on the client side. That's the most important difference.
    Appelt's usually are for little applications like games and stuff, you can run in a browser.
    Servlets are for dynamic pages, for example database-viewing and stuf...

  • Advantage and Disadvantages of 64 bit over 32 bit

    Hi,
    Can anyone please let me know the advantages and disadvantages of 64 bit over 32 bit Essbase. The version i am currently using is 9.3.1 on 32 bit.
    Will appreciate your help.
    Thanks in advance
    RG

    Thanks Giri for high level infromation.
    Can you please provide me information that is there any matrix available provide the comparision on 32 bit over 64 bit. Like the comparision on maximum dimensions and members, Maximum number of parallel calc threads ( BSO) OR Maximum number of parallel loads ( ASO), Maximum number of user threads on Analytics access via smart view, excel add in or EAS console, etc.
    It would be really helpful if you could provide the same.
    Many Thanks
    Suman

  • Advantage and disadvantage of view over physical table

    Hi,
    Can you explain me Advantage and disadvantage of view over physical table

    Hi Nitin,
    A view can be thought of as either a virtual table or a stored query. The data accessible through a view is not stored in the database as a distinct object. What is stored in the database is a SELECT statement. The result set of the SELECT statement forms
    the virtual table returned by the view. A user can use this virtual table by referencing the view name in Transact-SQL statements the same way a table is referenced.
    For more information about the advantages and disadvantages of views in SQL Server, please refer to the following two articles:
    http://www.c-sharpcorner.com/Blogs/10575/advantages-and-disadvantages-of-views-in-sql-server.aspx
    http://www.toadworld.com/platforms/sql-server/w/wiki/10274.views-advantages-and-disadvantages.aspx
    Regards,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Advantages and Disadvantages of OIM11gR2 over 11gR1

    Hello experts,
    I would like to list out the advantages and disadvantages of OIM 11g R2 over R1. Can you guys please help me in completing the list??
    Advantages:
    1. Shopping cart experience / request catalog model / interactive user interface
    2. UI customisations made easy
    3. Secure access to cloud, mobile and social networks
    I am not sure of the disadvantages but heard that its a lenghty process (risky) to upgrade from R1 to R2.
    Can any of you have ideas on the changes to workflows, provisioning and reconcilation and other procesess.
    Thanks,
    Bob

    http://rajivdewan.blogspot.com/2012/08/oracle-identity-manager-11g-r2-oim-11g.html
    anyone come across any cons with R2Some known and unknown issues are there but those you'll find with each and every product and version.
    http://docs.oracle.com/cd/E27559_01/relnotes.1112/e35820/id_mgr.htm#CHDDGDCC

  • Advantages and disadvantages of Internet Sales R/3 Edition over ITS

    Hello,
          I want to know what are the Advantages and disadvantages of Internet Sales R/3 Edition over ITS? If we shift from ITS to  Internet Sales R/3 Edition, what would be added advantages?
    Note: Here ITS is used only for Sales Transactions.
    Thanks & Regards,
    Pratik Gandhi.

    Hi
      E-Service&E-Marketing is not part of the R/3 Internet sales edition.
    Cheers

  • Advantages and disadvantages of BAPI_PO_CREATE1 over BAPI_PO_CREATE.

    Advantages and disadvantages of BAPI_PO_CREATE1 over BAPI_PO_CREATE. Please provide details.

    Hi,
      see this
    Re: PGI in vl01n
    Regards
    Kiran Sure

  • Advantages and Disadvantages of webdynpro JAVA over J2ee?

    Hi,
       Can anybody provide me the advantages and disadvantages of webdynpro java over the J2EE?
    Regards,
    Harish.

    Hi,
    Webdynpro is the SAP standard technology for developing business user intrefaces.
    Webdynpro is like the frame work which follows the MVC Design pattern.
    Webdynpro uses most of the UI developement as declarative approach , i.e. most of the code will generated by the framework. so it will reduce the developement efforts.
    Adaptive RFC model to connect with SAP systems.
    All these are advantages over than the J2ee.
    Regards,
    Naga

  • Advantages and disadvantages of statefull stateless applications

    Hello, can you tell e some advantages and disadvantages of statefull or stateless applications? When should i use a statefull and when a stateless application ?
    Thank you

    Hi,
    Pls check things like
    /people/mark.finnern/blog/2003/09/24/bsp-in-depth-confusion-between-stateless-stateful-and-authentication
    http://help.sap.com/saphelp_nw04/helpdata/en/88/9dc53a87728677e10000000a11405a/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/e0/1bc1a3ccf511d4990800508b6b8b11/frameset.htm
    Stateful and Stateless BSP Application
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/16f69790-0201-0010-6ba1-b73bb3f7b0e8
    Eddy

  • Reg : Advantages and Disadvantages of WAD over Bex in Reporting

    Hi BW Gurus,
                I wish to know the advantages and disadvantages of using WAD Over BEx .Please reply back with some strong points, as I have to project the same to our customer.
    Thanks in Advance,
    Krishna

    Hi Krishna,
    Here are some:
    - User friendly access (less educational cost).
    - Web reporting is faster, less overhead in executing Web reports.
    - Learning curve for NEW users in BW is lower on Web Reporting.
    - Accessibility of reports to a wider audience.
    - No SAP front-end is needed anymore to execute reports.
    Hope it helps,
    David.

  • Advantages and Disadvantages of XML over CSV

    Hi friends,
    We have a requirement in our implimentation project. We are implimenting HR module. The company is using SABA for Education and Certification.
    We are implimenting Education and certification in BW and the data for BW will be comming from SABA.
    We had a discussion on thursday about the integration of SABA to BW. We can do it through DBconnect or by using XI and for this there is time and cost involved.
    The techical team has come with some idea where there will give the data in the form of XML or in CSV format.
    I would like to know the advantages and disadvantages of each and also please consider the performance point in view.
    I would also like to know about the things that need to be  considered if we process the data in multiple files.
    Please give me inputs and the answers will be appreciated with valuable points.
    Regards
    Raghav Reddy

    Hi,
    my advice is to go for CSV anytime compared to XML.
    XML is first made available to the BW system via  SOAP ( Simple Object Acess protocol) interface. Next it is updated into the required data targets as before , Via a data source for the myself source system.
    SOAP = XML+HTTP.
    XML cannot be used for mass data. It is only to load small data into SAP BW on a single document level.
    BW provides flat file interface so, there is no all these hassles in case of CSV. go for CSV

  • Advantages and Disadvantages of JMS Queue over Fabric

    HI,
    I want to know both the advantages and disadvantages of using JMS queue over the default Fabric queue in B2B adapter.
    Is it ok if I configure all my inbound and outbound transactions across all the trading partners to communicate with their respective SOA composite via the default JMS Queues(B2B_IN_QUEUE and B2B_OUT_QUEUE)?
    Please advise.
    Thanks in advance.
    Regards,
    Monica

    Hi Monica,
    But the size of the payload which I am using is unpredictable, it can differ from 1 MB to 40MB in future.This is not a problem. B2B can handle MB's of file if server has enough resources.
    all other payloads greater than 3MB, it is getting faulted with the message:
    "SAX Exception in translator. SAX Exception raised while trying to SAX Parse InputStream . Please make sure that the xml data is valid."Please remember that when B2B will find a large payload then it will write the large payload into the "Large Payload Directory" (defined in Administration--> Configuration) and pass it's reference to the middleware. So at middleware, you will not receive the actual payload but you will receive it's reference. Using File adapter sync read option, you may read the large file from "Large Payload Directory" at SOA layer.
    If you are using PS5 (11.1.1.6) then you will see that for large payload, B2B passes the JMS header LARGE_PAYLOAD to the back-end so in your composite, you may build logic around this. If this header (LARGE_PAYLOAD) is not coming at SOA layer then payload will be available in the body and if it is populated then payload will be available in the "Large Payload Directory" and it's reference will be available in the message body.
    Regards,
    Anuj

  • Advantages and disadvantages among Timer, ScheduledExecutorService, Thread

    Hi, what are the exact advantages and disadvantages among using Timer, using ScheduledExecutorService and just using Thread (Thread.sleep(...))?
    For the simple task which needs to poll some values by some interval (the interval is not supposed very accurate, maybe about 5 seconds just ok), is it ok for just using Thread, like:
    run() {
      while(isRunning) {
         Thread.sleep(5000);
         //do something
    }?

    jiangyc wrote:
    Why using Timer and TimerTask is simpler and better than using Thread directly? Because it handles the rote stuff that's not directly part of your application. Ideally, your code should just be the marginal stuff that's specific to your app; anything else should be in the library you use. The less code the better.
    I feel just using Thread doesn't make my code hard to maintain and by far I don't find any performance issue raised by using Thread (in our swing application, there are maybe less than 10 Thread objects which take care of the different polling tasks). It's not a performance issue; it's a code management issue. (Although the chances are good that Timer will have been well-tuned.) The less code you have, the less code you have to wade through to fix bugs, make changes, etc. This might not seem like much when it's a small program, but it adds up. In a business environment where you have huge codebases worked on by dozens of people (many of whom don't work there anymore) it becomes really important to only write what you have to and no more. Maybe if you're doing a small project it's not important, but keeping your code clean a good habit to get into.
    And I wonder the base implementation of Timer and TimerTask is not using Thread?Of course it is. That's not the point. The point is that it keeps your code cleaner.
    When you use Thread directly, probably the only part that's directly relevant to your program (as opposed to any other program that uses Thread) is the value you're sticking in Thread.sleep() -- the delay. You specify that in the schedule() call to the Timer.
    If you keep your use of Thread minimal, then it might not be much bigger than using Timer/TimerTask, but the latter does more, including stuff you'll probably need to add (like ways to cancel the task).
    Also, when you do this using Thread, you're exposing the implementation, but when you use Timer.schedule, you're exposing the intent. The latter makes for clearer code.

  • Advantages and Disadvantages of Soap

    Advantages and Disadvantages of Soap
    Hi Firends,
                  Could you please tell me the Advantages and Disadvantages of using Soap adapter, i need them urgently.
    Note: High reward points will be given for each answer

    Hello
    SOAP is an XML-based protocol for exchanging information in a decentralized, distributed environment. It was made for Web, a combination of XML and HTTP opens up new options for distributed data exchange and interaction in a loosely coupled web environment. SOAP is a technology that allows XML to move easily over the Web. SOAP does this trough an XML envelope for delivering XML content and specifying a set of rules for services to follow when they receive a SOAP message.
    The fundamental change brought about by SOAP has been the ability to move data anywhere across the Web. Before SOAP there were only two main options for moving data between partners.
    One was to build a wide area network spanning a broad geographic region and let the partners plug into it. This was the approach taken by EDI, which defined messages and protocols for data transfer but left the network details up to the partners. The result was a collection of networks that pretty much locked the partners in and made it difficult and expensive to reach out to other EDI networks and costly to bring in new partners.
    The second approach for moving data between partners was to build a distributed object infrastructure than ran over the internet. This was the approach taken by Common Object Request Broker (CORBA), Remote Method Invocation (RMI) and Distributed Component Object Model (DCOM). The problem was that each had to decide on a protocol that could sit on top of TCP/IP and handle inter object communication. CORBA Chose Internet Inter-ORB Protocol (IIOP), DCOM chose object Remote Procedure Call (ORPC), and RMI chose Remote Method Protocol (JRMP). While this approach reduced the need to share the same underlying network, the drawback was that CORBA could talk to CORBA, RMI to RMI and DCOM to DCOM, but they neither could talk to each other nor directly to the web except through special sockets that required adding extra layers to an already complex architecture.
    SOAP the third option, combines the data capabilities of XML with the transport capabilities of HTTP, there by overcoming drawbacks of both EDI and tightly coupled distributed object system such as CORBA, RMI and DCOM. It does this by breaking dependence between data and transport and in doing so opens up a new era of loosely coupled distributed data exchange.
    SOAP Carries an XML RPC tradition by defining an XML language for packaging arbitrarily XML inside an XML envelope. Although SOAP does not depend on HTTP, the momentum behind SOAP is attributable to the fact that HTTP will usually be used for transfer protocol for SOAP messages.
    SOAP is a transport protocol similar to IIOP for CORBA, ORPC for DCOM or JRMP for RMI.
    SOAP differs from CORBA, RMI or DCOM in several ways.
    IIOP, ORPC and JRMP are binary protocols, while SOAP is a text based protocol that uses XML. Using XML for data encoding makes SOAP easier to read than a binary stream.
    1) Because SOAP is text based, it is able to move more easily across the firewalls than IIOP, ORPC or JRMP.
    <p2) SOAP is based on XML, which is standard driven rather than vendor driven. Potential adaptors are less likely to fear vendor lock in with SOAP. </p2>
    The net effect is that SOAP can be picked up by different transport protocol and delivered in different ways. For example, when used with HTTP it can be delivered to a web server, when used over FTP it can be deposited directly into a file system and when used with SMTP it can be delivered to a user's mailbox.
    Many companies exchange data between established partners is proving totally satisfactory way to leverage the benefits of XML and the web. In this scenario the required are an agreed upon schema either DTD or an XML schema, for XML data being exchanged and the SOAP server capable of handling the incoming XML as it arrives over the web. Details about what kind of schemau2019s to expect and who will check the XML conforms to the schema are decided offline by individuals participating in the process. On the software side senderu2019s needs to be involved in packaging their data in an XML document. For those companies already storing data in XML, this should require only minimal effort. If the stored XML data is not in the form required by the agreement, an XSL Transformation(XSLT) style sheet can be programmed to automate the transformation.
    SOAP messages define one way data transmission from sender to the receiver. However SOAP messages are often combined to implement patterns such as request-response. When using HTTP binding with SOAP, SOAP messages can use the same connection as the inbound request.
    Regard's
    CHETAN AHUJA

Maybe you are looking for