MXE - Best practise document

Hi All,
I was wondering if there is any "best practise" guide for MXE in terms of downgrading video formats for use in SnS?
For example, suggested dimensions,bit rate,sound compression etc...?
Thank you

Hi
The show and share and MXE can be integrated and when you add a new video to SnS it will automatically transcode it to the DMP profile created during the MXE integration.  The transcoded file by default has the following format:
•Format: Flash video 8 (.flv)
•Bitrate: 400 bps
•Frame rate: 30 fps
•Maximum height: 268 pixels
•Maximum width: 480 (for 16x9 ratio), 360 (for 4:3 ratio)
You can see more details in the link below:
http://www.cisco.com/en/US/partner/docs/video/digital_media_systems/5_x/5_2/showandshare/admin/guide/mxe.html
Thank you
Rubens

Similar Messages

  • Best practise documents for Aerospace & Defense (A&D)

    Hi Gurus,
    I'm unable to find the SAP A&D best practice documents in the list of best practices for industry solutions. Has it been moved to a new industry package? Also, please let me know where I can find some SAP PP A&D documents for reference.
    Thanks in advance for all your help!

    Owais,
    You don't seem to be giving this much effort.  You were in the Best Practices section of help.sap.com reviewing expert Mariano's answer, and you were unable to locate any PP configuration?
    Try
    then
    then
    and hunt until you find what you want.
    Best Regards,
    DB49

  • Best Practise Documents for Oil & Gas Industries

    Dear Experts,
    I am looking for SAP Best Practice documents on Oil & Gas Industry.
    Any useful link or file will be highly appreciated!
    Regards,
    Zain M. Bashir

    Hi Zain,
    Apparently there are no such documents available. You may refer the SAP documentation on IS OIL
    which is exhaustive and elaborated.
    http://help.sap.com/saphelp_oil46csp2/helpdata/en/67/bfa73ad9ccf101e10000000a11402f/frameset.htm
    Regards,

  • Transport landscape best practise

    I'm wondering if SAP has a best practise document on transport landscape planning.
    SAP Help has pretty clear description about a standard 3 system landscape. But not document is found describing complext transport landscape considerations --- multiple ABAP development/test systems, conflict resolution between project landscape and maintenance landscape.
    Any feedback is greatly appreciated.

    Hi. GO to http://help.sap.com/bp/initial/index.htm
    There you find all about BP.
    Regards, Award if helpful

  • Best practise for SAP users who leave the company

    Hi
    Could anyone reccommend a best practise document or give advice on how to deal with SAP user ID's when employee's/contractors/consultants leave? I am the basis admin just starting an SAP implementation and we have no dedicated authorisation team at the moment, so I have been asked to look into this :
    Currently we set the validity date in SU01 to the termination date.
    We chack there are no background jobs scheduled under that user id, if there are, we change the job owner to a valid user (we try to run all background jobs under an admin account).
    We do not delete the user as from an audit point of view I believe it restricts information you can report on and there are implications on change documents etc, so best to lock it with validity dates.
    Can anyone advise further?
    We are running SAP ECC 5.0 on Windows 2003 64 Bit/MS SQL 2000.
    Thanks for any help.

    Hi,
    Different people will tell you different versions of what they believe is best practice, but in my opinion you are already doing reasonably well.
    What I prefer is
    1. Lock ID & set validity date.
    2. Assign user to user group LEAVER or EXPIRED or something similar (helps with reporting) out of SUIM/S_BCE* reports.
    3. Delete role assignment (should you need it, the role assignment will be in the change history docs anyway).
    4. Check background jobs & act accordingly.
    For ease of getting info I prefer not to delete the ID though plenty of people do.

  • Best practise around handling time dependency for flat file loads

    Hi folks,
    This is a fairly common situation - handling time dependency for flat file loads. Please can anyone share their experience around handling this. One common approach is to handle the time validity changes within the flat file where it is easily changeable by the user but then again is prone to input errors by the user. Another would be to handle this via a DSO. Possibly, also have this data entered directly in BI using IP planning layouts. There is a IP planning function that allows for loading flat file data but then again, it only works without the time dependency factor.
    It would be great to hear thoughts or if anyone can point to a best practise document for such a scenario.
    Thanks.

    Bump!

  • Best Practises doc..

    Is the any best practises document for BPC consolidation?
    Can some one give me the link or let me know where it is available

    hope below docs would help you
    http://www.sap.com/solutions/sapbusinessobjects/large/enterprise-performance-management/planningandconsolidation/index.epx
    http://www.maxima.co.uk/budgeting_planning_financial_consolidation_SAPBPC
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b25a12-7082-2b10-5c86-c227b9397fb3
    you can go for
    http://service.sap.com/pam
    regards
    nag

  • Best Practises on SMART scans

    For Exadata x2-2 is there a best practises document to enable SMART scans for all the application code on exadata x2-2?

    We cover more in our book, but here are the key points:
    1) Smarts scans require a full segment scan to happen (full table scan, fast full index scan or fast full bitmap index scan)
    2) Additionally, smart scans require a direct path read to happen (reads directly to PGA, bypassing buffer cache) - this is automatically done for all parallel scans (unless parallel_degree_policy has been changed to AUTO). For serial sessions the decision to do a serial direct path read depends on the segment size, smalltable_threshold parameter value (which is derived from buffer cache size) and how many blocks of a segment are already cached. If you want to force the use of a serial direct path read for your serial sessions, then you can set serialdirect_read = always.
    3) Thanks to the above requirements, smart scans are not used for index range scans, index unique scans and any single row/single block lookups. So if migrating an old DW/reporting application to Exadata, then you probably want to get rid of all the old hints and hacks in there, as you don't care about indexes for DW/reporting that much anymore (in some cases not at all). Note that OLTP databases still absolutely require indexes as usual - smart scans are for large bulk processing ops (reporting, analytics etc, not OLTP style single/a few row lookups).
    Ideal execution plan for taking advantage of smart scans for reporting would be:
    1) accessing only required partitions thanks to partition pruning (partitioning key column choices must come from how the application code will query the data)
    2) full scan the partitions (which allows smart scans to kick in)
    2.1) no index range scans (single block reads!) and ...
    3) joins all the data with hash joins, propagating results up the plan tree to next hash join etc
    3.1) This allows bloom filter predicate pushdown to cell to pre-filter rows fetched from probe row-source in hash join.
    So, simple stuff really - and many of your every-day-optimizer problems just disappear when there's no trouble deciding whether to do a full scan vs a nested loop with some index. Of course this was a broad generalization, your mileage may vary.
    Even though DWs and reporting apps benefit greatly from smart scans and some well-partitioned databases don't need any indexes at all for reporting workloads, the design advice does not change for OLTP at all. It's just RAC with faster single block reads thanks to flash cache. All your OLTP workloads, ERP databases etc still need all their indexes as before Exadata (with the exception of any special indexes which were created for speeding up only some reports, which can take better advantage of smart scans now).
    Note that there are many DW databases out there which are not used just only for brute force reporting and analytics, but also for frequent single row lookups (golden trade warehouses being one example or other reference data). So these would likely still need the indexes to support fast single (a few) row lookups. So it all comes from the nature of your workload, how many rows you're fetching and how frequently you'll be doing it.
    And note that the smart scans only make data access faster, not sorts, joins, PL/SQL functions coded into select column list or where clause or application loops doing single-row processing ... These still work like usual (with exception to the bloom filter pushdown optimizations for hash-join) ... Of course when moving to Exadata from your old E25k you'll see speedup as the Xeons with their large caches are just fast :-)
    Tanel Poder
    Blog - http://blog.tanelpoder.com
    Book - http://apress.com/book/view/9781430233923

  • Best Practise to find the Calculations from BRD

    Hi Experts,
    I am facing lot of difficulties to find the required calculations and the required Business Rules as I am new to the Hyperion Planning Implementation.
    Could any one please suggest me the best practise to find the calculations from the Business Requirement Document.
    Thanks In advance..
    Chinna.

    Many Thanks Rahul..As of now we are done with the Metadata Load..We need to create the Dataforms now..
    The Main problem started now..need to find the related calculations to attach with dataforms..I am struck there to find the calculations..
    anyway will get back to you if i need any further help..
    Thanks again.

  • Best Practises for Email Addresses?

    Hi Guys,
    Are there any best practise guides / documents / etc. for configuring user's E-mail addresses? We have a large turnaround of users and obviously sometimes they have the same name as previous/current employees (we
    do not delete any old accounts / mailboxes.) My question is whether or not it is OK to use numbers in an email address (i.e. [email protected])?
    Thanks
    Stephen

    Hi,
    It's OK to use numbers in an email address.
    The format of email addresses is local-part@domain where the local-part may be up to 64 characters long and the domain name may have a maximum of 253 characters.
    The local-part of the email address may use any of these ASCII characters RFC 5322
    Uppercase and lowercase English letters (a–z, A–Z) (ASCII: 65-90, 97-122)
    Digits 0 to 9 (ASCII: 48-57)
    Characters !#$%&'*+-/=?^_`{|}~ (ASCII: 33, 35-39, 42, 43, 45, 47, 61, 63, 94-96, 123-126)
    Character . (dot, period, full stop) (ASCII: 46) provided that it is not the first or last character, and provided also that it does not appear two or more times consecutively (e.g. John..[email protected] is not allowed.).
    Special characters are allowed with restrictions. They are:
           Space and "(),:;<>@[\] (ASCII: 32, 34, 40, 41, 44, 58, 59, 60, 62, 64, 91-93)
           The restrictions for special characters are that they must only be used when contained between quotation marks, and that 3 of them (The space, backslash \ and quotation mark " (ASCII: 32, 92, 34)) must also
    be preceded by a backslash \ (e.g. "\ \\\"").
    For more information, please refer to this similar thread.
    https://social.technet.microsoft.com/Forums/exchange/en-US/69f393aa-d555-4f8f-bb16-c636a129fc25/what-are-valid-and-invalid-email-address-characters
    Best Regards.

  • 4400 Controllers - Best Practise for connecting to wired network

    At one time the best practise recommendation for wireless was to treat the traffic as untrusted and separate it from the wired network by firewalls and intrusion detection. A lot of the reason for this was the weakness of WEP. Now with strong authentication and encryption (e.g., WPA2 and EAP-TLS) in use, and the use of wireless controllers, I'm wondering what the industry is recommending (and doing in case the actions aren't the same as the recommendations).
    Are organizations connecting the wireless controllers directly to the internal network or are they separating them with a firewall and IDS infrastructure? If the latter, what does the architecture look like? Are there documents on the Cisco site or on the Internet that show how the controllers could be firewalled? Everthing I've seen shows connections directly to the internal network. Is firewalling the controller an overreaction to the historical paranoia from the WEP days?

    The argument would be that regardless of what security you put on the wireless, you still don't have the physical security - i.e. someone doesn't need to walk into your building to use your network.
    Beyond that if you're using strong auth/enc you can currently be considered safe, we have customers using that direct into their LANs (but then, we also have customers with WEP direct into their LANs!)...
    If you are concerned or really need belt 'n' braces security, then go down the firewall/IDS route - there's no harm in it if you have the money. It really depends how much functionality and ease of use you need to balance against it.
    Aaron
    Please rate helpful posts

  • Best practise BW Query design for Crystal Reports integration

    Hi all,
    I am looking for a guide on best practices when designing a BW Query to be used as data foundation for a Crystal Report.
    The scenario is that I am responsible for developing the Crystal Reports part, but not the BW Query part, therefore I would like to provide a list of best practises to the person who is responsible for the Query, this way make sure that the integration will work as good as possible. The setup is of course using BO Integration Kit for SAP.
    An example is how to use authorization variables in the query to provide data security. This is just one example, there are problably a number of other things to be aware of. A document containing suggestions for best practices is what I am looking for, or if the document does not exist, input to what should be on such a list.
    Thank you in advance.
    Regards,
    Rasmus

    Hi Rasmus,
    in regards to the Best Practices for Crystal Reports you can leverage all the knowledge you have on the Query Design today already. if you not the person for designing the query I think it is important to make sure people designing the queries do understand how Crystal Reports is leveraging the elements from the BI Query.
    /people/ingo.hilgefort/blog/2008/02/19/businessobjects-and-sap-part-2
    You should try to put as much as possible into the BI query from the logic point of view.
    and you can also build common BI queries - there is no need to build a BI query for each report.
    ingo

  • Best practise - Domain model design

    Hello forum,
    we're writing an application divided into three sub projects where one of the sub projects will be realized using J2EE and the other two sub projects are stand alone fat client applications realized using Swing. So that's the background...
    And now the questions:
    After doing some research on J2EE best practise topics I found the TransferObject-Pattern (http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObject.html) which we certainly want to apply to the J2EE sub project and to one of the standalone client applications also. To avoid code duplications I like the "Entity Inherits Transfer Object Strategy" approach outlined in the document referenced above. But why does the entity bean inherit from the transfer object class and not vice versa? In my opinion the tranfer object adds additional functionality (coarse grained getData()-method) to the class and isn't it a design goal in OO languages that the class that extends a base class has more functionality than the base class?
    For the standalone application we want to use a similar approach and the first idea is to desgin the entitys and let the TO classes extend these entitys.
    When I get it right the basic idea behind all of these design schemes is the "Proxy pattern" but when I design it using the previously mentioned way (Entity <-- EntityTO) I will have a very mighty prox beeing able to execute all operations the base class is able to execute.
    Any tips and comments welcome!
    Thanks in advance!
    Henning

    Hello Kaj,
    at first - thanks for your fast response and sorry for coming back to this topic so late.
    After reading a bit more on patterns in general what about avoiding inheritance
    completely and using the proxy pattern instead (As explained eg.
    http://www.javaworld.com/javaworld/jw-02-2002/jw-0222-designpatterns.html here) - so moving the design to a "has a" relationship rather than an "is a" relationship.
    In the previous post you said that the client shouldn't be aware that there are entity beans and therefore the mentioned implementation was chosen - But if I implement it vice versa (Entity is base class, TO extends entity) and do not expose any of the methods of the entity bean I would achieve the same effect, or not? Clients are only able to work with the TOs.
    I have some headaches implementing it in SUN's recommended way because of the Serialization support necessary within the TOs. Implemented in SUN's way the Entity bean would also have serialization support which isn't necessary because they're persisted using Hibernate.
    Thanks in advance
    Henning

  • Best Practices Document for Creating/Designing Queries/Reports

    Hello all,
    I hope I am not posting my very first question in a wrong forum. I am looking for any document(s) related to Best Practises for Designing Queries/Reports using BeX Query Designer (or any other tool for that matter). I did some searching, but could not find anything related to what I am looking for.
    Thanks in advance!
    Amit

    Hi Amit:
       The documentation below might help.
    Regards,
    Francisco Milán.
    Chapter 6 of "Performance Tuning for SAP BW"
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10fb4502-111c-2a10-3080-df0e41d44bb3?QuickLink=index&overridelayout=true&15882789067966
    "30 technical tips and tricks to speed query, report, and dashboard performance" by Dr. Bjarne Berg
    http://www.google.ca/url?sa=t&rct=j&q=30%20technical%20tips%20and%20tricks%20to%20speed%20query%2C%20report%2C%20and%20dashboard%20performance&source=web&cd=2&ved=0CFQQFjAB&url=http%3A%2F%2Fcsc-studentweb.lr.edu%2Fswp%2FBerg%2Farticles%2FNW2010%2FBerg_NW2010_30_tips_for_SAP_BI_performance_v4.pptx&ei=oVIYULT3HIOJ6AHUuICADw&usg=AFQjCNGZnqACv5u3ai81xvKH1Kq-qckavg
    "Improving Query Performance by Effective and Efficient Maintenance of Aggregates" paper by Naween Kumar Yadav.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/906de68a-0a28-2c10-398b-ef0e11ef2022?QuickLink=index&overridelayout=true&43426414363758
    "Summary of BI/BW 7.0 performance improvements" blog by Jens Gleichmann.
    http://scn.sap.com/people/jens.gleichmann/blog/2010/10/12/summary-of-bibw-70-performance-improvements
    "BEx Front end Performance"
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40955430-dc1c-2a10-349a-fa181307d7df?QuickLink=index&overridelayout=true&15882789070879
    "Performance Optimization of Long Running Queries Using OLAP Cache" paper by Raghavendra Padmanaban T.S. and Ananda Theerthan J.
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f048c590-31a4-2c10-8599-bd01fabb93d4&overridelayout=true
    "BW Performance Tuning" paper by Dr. Thomas Becker and Alexander Peter
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/701382b6-d41c-2a10-5f82-e780e546d3b6?QuickLink=index&overridelayout=true&15878494103977
    "Performance Tuning for SAP Business Information Warehouse" paper by Alexander Peter and Uwe Heinz
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4c0ab590-0201-0010-bd9a-8332d8b4f09c?QuickLink=index&overridelayout=true&5003637415559
    "How to… Performance Tuning with the OLAP Cache"
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9f4a452b-0301-0010-8ca6-ef25a095834a?QuickLink=index&overridelayout=true&5003637412341
    Queries section of "Performance Tuning Massive SAP BW Systems - Tips & Tricks" paper by Jay Narayanan.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94?QuickLink=index&overridelayout=true&5003637414215

  • Best practises for install BPEL

    We are planning to start to use BPEL, but we are having problems finding any documents on best practise on the install of the product.
    1. Sould we install in Lunix or Windows.
    2. In prodcution we will need fault tollerance can BPEL do this well.
    3. Does the BPEL monitoring work well.
    We want to install this right first time rather than just install from the CD's then try to fix the issues we wrong design later, we have been burnt by do this way before.
    Regards
    Sean Bell

    Hi,
    1) install it on the platform you know best. because
    2) you can only get fault tolerance or high availability on a platform you know how to administer.
    for HA look at
    http://www.oracle.com/technology/products/ias/bpel/pdf/bpel-admin-webinar.pdf
    3) BAM is the word you are searching for:
    http://www.oracle.com/technology/products/integration/bam/index.html

Maybe you are looking for