ES2 best practice for how much stuff should be in one application?

I'm wondering if there is a best practice/recommended amount of the maximum amount of forms/processes/etc that you should have contained within one application in ES2? I have an application which has about 5 processes, and has over 300 xdp forms. When "deploying" the application it takes probably over 5 minutes or longer. It seems to be working fine but i'm curious if this will cause any problems and if there is a recommended threshold?

I don't think there is a limit on the number of processes & forms to be used within an application.
However there is recommendation for not having more than 20 variable in a single process.
Each process created within you application will become a service. So it doesn't matter having 500 processes in one application or 50 processes in 10 applications. You will endup with 500 services deployed into Java Runtime.
Forms also doesn't bother about the count as it just stay within repository (not in Java Runtime).
The only issue with enormous resources within an application is the response time to Deploy to application server (which you already mentioned here).
So, if you can split your resources into manageable units, that will reduce your checkin/deploy time.
Nith

Similar Messages

Best practice for how to access a set of wsdl and xsd files

I've recently beeing poking around with the Oracle ESB, which requires a bunch of wsdl and xsd files from HOME/bpel/system/xmllib. What is the best practice for including these files in a BPEL project? It seems like a bad idea to copy all these files into every project that uses the ESB, especially if there are quite a few consumers of the bus. Is there a way I can reference this directory from the project so that the files can just stay in a common place for all the projects that use them?
Bret

Hi,
I created a project (JDeveloper) with local xsd-files and tried to delete and recreate them in the structure pane with references to a version on the application server. After reopening the project I deployed it successfully to the bpel server. The process is working fine, but in the structure pane there is no information about any of the xsds anymore and the payload in the variables there is an exception (problem building schema).
How does bpel know where to look for the xsd-files and how does the mapping still work?
This cannot be the way to do it correctly. Do I have a chance to rework an existing project or do I have to rebuild it from scratch in order to have all the references right?
Thanks for any clue.
Bette

Best practice for keeping a mail session open in web application?

Hello,
We have a webmail like application where users login with their IMAP credentials, then are taken to an authenticated area of the site where they can manage different things about their email account.
Right now the application is opening and closing a mail store connection (via a new javax.mail.Session) for each page load based on the current logged in user credentials. To me this seems like it would be a bad practice to keep opening and closing a connection each page load.
Are there any best practices for this situation? It would be nice to be able to open the connection to the mail server on login, then keep that connection open until the person logs out, session expires, etc.
I can probably put the javax.mail.Session into the HTTP session, but that seems like it would break any clustering functionality of tomcat. This would be fine if the machine the user is on didn't fail, but id assume if they failed over to another the mail session would be gone. Maybe keeping the mail session in the http session, checking for a connection, then first attempting to reconnect with the logged in credentials before giving up would be a possiblity?
Any pointers would be appreciated

If you keep the connection open across pages, you're going to need to deal with
timeouts - from the http session and from the mail server.
If you don't keep the connection open, you're going to need to "resynchronize"
your view of the store/folder with each operation, in case the folder is modified
by another session.
The former is easier in the common cases, especially if you don't care how gracefully
you handle failures. The latter is more difficult in the common cases, but handles
failure better, and in particular handles clustering better. You'll need to measure it to
see if it meets your performance and scalability requirements. You may need to mix
the two approaches to get acceptable performance.

Best Practice for enhancing the SAP delivered standard WD ABAP application

Hi,
I am new to WebDypro ABAP.
To enhance the SAP delivered Standard WebDynpro Component (complex component with Business objects & powl).
Kindly let me know the best practice for enhancing the Standard WD ABAP from the below 1 or 2.
1) To copy & create a "Z" of the component & make changes in that (or)
2) to enhance directly on the same standard component without making "Z".
Regards,
NS

Hi NS,
If it is a standard component its better we go for enhancing the component rather than copying it into Z component.
If there is any issue with in the standard component , SAP supports it through notes and OSS messages. If it is a Z component, SAP doesn't support it.
If there is any up gradation of business packages, changes will be done to standard , but not the Z components, wherein we could miss it.
Further, since it is a standard component it might have been used at many places, changes that has to done to reflect all changes might be difficult in this case if it is a z component.
Regards,
Harsha

Best Practice for initialising class variables, should they be null?

class Person
private String name, address;
public String getName()
return name
public void main()
Person me = new Chris()
..........loads of code........
if(me.getName==null)
do something
else
do something else
So my question is : whats the best behaviour when declaring variables? In this case should I have initialized the Strings to the empty string?
I think i need to make a decision because I'm constantly unsure if the method should return null or empty string. So i find myself doing this occasionally :
if(person.getName()==null || person.getName().equalIgnoreCase(""))
Thanks
Chris

I believe that when you create an object it should be 100% ready for use. That means all private member variables set to a non-null, sensible value.
You shouldn't force clients to know what's safe and what's not:
public class Person
    private String name;
    private Date birthDate;
    public static void main(String [] args)
        Person p = new Person();
        System.out.println("age: " + p.getAge());
    public Person() { // do nothing; name is null }
    public String getName() { return name; }
    public void setName(String newName) { name = newName; }
    public Date getBirthDate() { return birthDate; }
    public void setBirthDate(Date newBirthDate) { birthDate = new Date(newBirthDate.getTime()); }
    public int getAge()
        int age = 0;
        // calculating age with a null birth date will be a problem.
        return age;
}You might argue that it's perfectly reasonable to expect a user to call setters to initialize an object after it's created, but I don't like that idiom. There's no guarantee that it'll be done properly.
%

Best Practice for mail connectors

I am setting up connectors for exchange and groupwise and am testing auto-provisioning. I am running into an issue with groupwise where the GroupWise connector attempts to provision before the E-Directory account is established. Is there a best practice for how to avoid this from happening? should I add a hidden OIM field that populates when E-dir is provisioned correctly and put a rule in place to catch it and then provision groupwise or is there an easier way?
rkimbal45

You can put a task on the create user of the email that validates the directory exists. And you can set the retry counter, so that if your email connectors runs first, it will not continue. Then when retry happens, it will see it exists, and then your next tasks can trigger. Just create it as an unconditional task and set it as a preceding to your Create User task. This will keep the create user task in a pending state until your check completes.
-Kevin

How much room should be partitioned for Windows XP?

Alright, I have a different install disc for XP with SP3 which should work. Since I'll only be using XP for a couple of things (mainly small programs, but also for office and such), how much room should I leave for XP on my 320 gig HD so that both OSs have some breathing room (most of my other stuff like music and pictures are on the Leopard side of things)?

But I hear that it has better compatibility to run FAT32 than NTFS. Does it really matter too much?
While OSX is able to read and write to FAT32 partition, it can only read from NTFS partitions.
With the help of apps like NTFS-3G http://www.ntfs-3g.org/ and/or NTFS for Mac http://www.paragon-software.com/home/ntfs-mac/ OSX can also write to NTFS partitions.
To me personally this is no problem, since I want OSX and Windows to seperated (I even have Windows on a harddisk of its own in my Mac Pro) and for file exchange between OSX and Windows I use an external FAT32 HD.
But the advantage of the newer, better and more robust NTFS file system outweighs these 'disadvantages'.
And FAT32 has a file-size limitation for single-files of 4GB.
Also, not to be pessimistic, but what if something goes wrong with the partition or install? Can I restart my Mac and would it be unaffected? This disc should work, but I want to know just in case...
Before 'fumbling' with any kind of partitioning on a harddisk I always make a backup of my important files, or better said I use SuperDuper to make a bootable clone of my OSX.
While the chances that something goes wrong are quite slim (I have made the partitioning with the BootCamp Assistant for about 10 times now), the possibility is always there.
Stefan

How can i get best practice for SD and MM

Please, can any body tell me how can i get best practices for SD and MM for functional approach?
Thanks
Utpal

Hello Utpal,
I am really surprised, in just 10 minutes you searched that site and found it not useful. <b>Check out my previous reply "you will not find screen shot in this but you can add it in this"</b>
You will not find readymade document, you need to add this as per your requirement.
btw, the following link gives you some more link for new SAP guys, this will be helpful. <b>Check out HOW to BASIC transaction</b>
New to Materials Management / Warehouse Management?
Hope this helps.
Regards
Arif Mansuri

I'm trying to update iOS 7 and it says I need 3.4 GB of storage to update.. I currently have on my storage 797 MB and 12,6 GB used. How much storage should it write for me to be able to update?

I'm trying to update iOS 7 and it says I need 3.4 GB of storage to update.. I currently have on my storage 797 MB and 12,6 GB used. How much storage should it write for me to be able to update?

If your ipad has only 797 MB free and it tells you that you need 3.4 GB to update, then you need to begin deleing files, whatever it takes to free up space.
Consider...
Delete apps you don't use.
Delete videos you don't want (these take up a lot of space).
Do you have a lot of emails stored on the device?
Are there apps that store data files, like a PDF reader? If there are a lot of these, you need to delete some.
The bottom line is that you need to remove data and/or apps on your device to make more storage available.
But for videos and photos, always sync them to a computer first to archive them.

How much RAM should I install for new iMAC ?

Hi,
How much RAM should I install for new iMAC* running Logic Studio? It comes with 4 GB - is that enough? (can you run in 64 bit mode..)
*(The 21.5" 3.06GHz Intel Core 2 Duo)
Also, I was planning to get the stock 1 TB Hard Drive & save projects to an external drive.
Does that sound reasonable?
Any other recommendations?
Thanks,
Wm Heart

Unless you plan on running huge projects with enormous sampled instruments, 4 GB will do (very) fine. And your disk plan is sound. Choose an external Firewire drive, rather than USB. FW is easier on the CPU and can handle more tracks than USB.
What you should get, instead of more memory, is a (24 bit) external audio interface, if you want to do serious recording and playback.
What type of audio interface you'ld need, depends on what you want to do with it and of course your budget. From decent to brilliant costs from roughly 100 to several 1,000's of europounddollars. Avoid the 16 bit ones, they're worse than the inbuilt audio chip of your iMac. You can recognize 16 bit Audio Interfaces (in webshops) by their prize (often under 100€£$) and the lack of mention of their bitrate.
HTH
Regards, Erik.

If I have a new ipad should I use it until the battry runs out and then charge it... or first charge it for how much hours?

If I have a new ipad should I use it until the battry runs out and then charge it... or first charge it for how much hours?

saida123456 -
Here is some info on battery/charging for apple products.
~ They normally come 2/3 charged, so you would want to charge it right away if you want a 100% battery.
~ Keep it out of the sun because the sun will take away battery life.
- See link below for a lot of information on Apple products and batery life.
http://www.apple.com/batteries/ipad.html
I will look around for more information on this.

I need to publish a magazine in arabic and english - what should I buy - for how much to use 15 mac books for my students to use indesign?

I need to publish a magazine in arabic and english - what should I buy - for how much to use 15 mac books for my students to use indesign?

You can only return the machine if you're within 14 days of purchase - otherwise you're just 'stuck' with what you purchased (unless you sell it, of course).
I always recommend that Retina owners order 16GB of RAM as the RAM is not upgradable - it's soldered onto the logic board.
Your call - if you're with 14 days of purchase, take it back and exchange for a 16GB model. Or sell it and buy a model with 16GB. The higher amount of memory will allow you to run far more memory-hungry apps concurrently.
Good luck,
Clinton

Best Practices for Using Photoshop (and Computing in General)

I've been seeing some threads that lead me to realize that not everyone knows the best practices for doing Photoshop on a computer, and in doing conscientious computing in general. I thought it might be a good idea for those of us with some exprience to contribute and discuss best practices for making the Photoshop and computing experience more reliable and enjoyable.
It'd be great if everyone would contribute their ideas, and especially their personal experience.
Here are some of my thoughts on data integrity (this shouldn't be the only subject of this thread):
Consider paying more for good hardware. Computers have almost become commodities, and price shopping abounds, but there are some areas where spending a few dollars more can be beneficial. For example, the difference in price between a top-of-the-line high performance enterprise class hard drive and the cheapest model around with, say, a 1 TB capacity is less than a hundred bucks! Disk drives do fail! They're not all created equal. What would it cost you in aggravation and time to lose your data? Imagine it happening at the worst possible time, because that's exactly when failures occur.
Use an Uninterruptable Power Supply (UPS). Unexpected power outages are TERRIBLE for both computer software and hardware. Lost files and burned out hardware are a possibility. A UPS that will power the computer and monitor can be found at the local high tech store and doesn't cost much. The modern ones will even communicate with the computer via USB to perform an orderly shutdown if the power failure goes on too long for the batteries to keep going. Again, how much is it worth to you to have a computer outage and loss of data?
Work locally, copy files elsewhere. Photoshop likes to be run on files on the local hard drive(s). If you are working in an environment where you have networking, rather than opening a file right off the network, then saving it back there, consider copying the file to your local hard drive then working on it there. This way an unexpected network outage or error won't cause you to lose work.
Never save over your original files. You may have a library of original images you have captured with your camera or created. Sometimes these are in formats that can be re-saved. If you're going to work on one of those files (e.g., to prepare it for some use, such as printing), and it's a file type that can be overwritten (e.g., JPEG), as soon as you open the file save the document in another location, e.g., in Photoshop .psd format.
Save your master files in several places. While you are working in Photoshop, especially if you've done a lot of work on one document, remember to save your work regularly, and you may want to save it in several different places (or copy the file after you have saved it to a backup folder, or save it in a version management system). Things can go wrong and it's nice to be able to go back to a prior saved version without losing too much work.
Make Backups. Back up your computer files, including your Photoshop work, ideally to external media. Windows now ships with a quite good backup system, and external USB drives with surprisingly high capacity (e.g., Western Digital MyBook) are very inexpensive. The external drives aren't that fast, but a backup you've set up to run late at night can finish by morning, and if/when you have a failure or loss of data. And if you're really concerned with backup integrity, you can unplug an external drive and take it to another location.
This stuff is kind of "motherhood and apple pie" but it's worth getting the word out I think.
Your ideas?
-Noel

APC Back-UPS XS 1300. $169.99 at Best Buy.
Our power outages here are usually only a few seconds; this should give my server about 20 or 25 minutes run-time.
I'm setting up the PowerChute software now to shut down the computer when 5 minutes of power is left. The load with the monitor sleeping is 171 watts.
This has surge protection and other nice features as well.
-Noel

Best practices for setting up projects

We recently adopted using Captivate for our WBT modules.
As a former Flash and Director user, I can say it’s
fast and does some great things. Doesn’t play so nice with
others on different occasions, but I’m learning. This forum
has been a great source for search and read on specific topics.
I’m trying to understand best practices for using this
product. We’ve had some problems with file size and
incorporating audio and video into our projects. Fortunately, the
forum has helped a lot with that. What I haven’t found a lot
of information on is good or better ways to set up individual
files, use multiple files and publish projects. We’ve decided
to go the route of putting standalones on our Intranet. My gut says
yuck, but for our situation I have yet to find a better way.
My question for discussion, then is: what are some best
practices for setting up individual files, using multiple files and
publishing projects? Any references or input on this would be
appreciated.

Hi,
Here are some of my suggestions:
1) Set up a style guide for all your standard slides. Eg.
Title slide, Index slide, chapter slide, end slide, screen capture,
non-screen capture, quizzes etc. This makes life a lot easier.
2) Create your own buttons and captions. The standard ones
are pretty ordinary, and it's hard to get a slick looking style
happening with the standard captions. They are pretty easy to
create (search for add print button to learn how to create
buttons). There should instructions on how to customise captions
somewhere on this forum. Customising means that you can also use
words, symbols, colours unique to your organisation.
3) Google elearning providers. Most use captivate and will
allow you to open samples or temporarily view selected modules.
This will give you great insight on what not to do and some good
ideas on what works well.
4) Timings: Using the above research, I got others to
complete the sample modules to get a feel for timings. The results
were clear, 10 mins good, 15 mins okay, 20 mins kind of okay, 30
mins bad, bad, bad. It's truly better to have a learner complete
2-3 short modules in 30 mins than one big monster. The other
benefit is that shorter files equal smaller size.
5) Narration: It's best to narrate each slide individually
(particularly for screen capture slides). You are more likely to
get it right on the first take, it's easier to edit and you don't
have to re-record the whole thing if you need to update it in
future. To get a slicker effect, use at least two voices: one male,
one female and use slightly different accents.
6) Screen capture slides: If you are recording filling out
long window based databse pages where the compulsory fields are
marked (eg. with a red asterisk) - you don't need to show how to
fill out every field. It's much easier for the learner (and you) to
show how to fill out the first few fields, then fade the screen
capture out, fade the end of the form in with the instructions on
what to do next. This will reduce your file size. In one of my
forms, this meant the removal of about 18 slides!
7) Auto captions: they are verbose (eg. 'Click on Print
Button' instead of 'Click Print'; 'Select the Print Preview item'
instead of 'Select Print Preview'). You have to edit them.
8) PC training syntax: Buttons and hyperlinks should normally
be 'click'; selections from drop down boxes or file lists are
normally 'select': Captivate sometimes mixes them up. Instructions
should always be written in the correct order: eg. Good: Click
'File', Select 'Print Preview'; Bad: Select 'Print Preview' from
the 'File Menu'. Button names, hyperlinks, selections are normally
written in bold
9) Instruction syntax: should always be written in an active
voice: eg. 'Click Options to open the printer menu' instead of
'When the Options button is clicked on, the printer menu will open'
10) Break all modules into chapters. Frame each chapter with
a chapter slide. It's also a good idea to show the Index page
before each chapter slide with a progress indicator (I use an
animated arrow to flash next to the name of the next chapter), I
use a start button rather a 'next' button for the start of each
chapter. You should always have a module overview with the purpose
of the course and a summary slide which states what was covered and
they have complete the module.
11) Put a transparent click button somewhere on each slide.
Set the properties of the click box to take the learner back to the
start of the current chapter by pressing F2. This allows them to
jump back to the start of their chapter at any time. You can also
do a similar thing on the index pages which jumps them to another
chapter.
12) Recording video capture: best to do it at normal speed
and be concious of where your mouse is. Minimise your clicks. Most
people (until they start working with captivate) are sloppy with
their mouse and you end up with lots of unnecessarily slides that
you have to delete out. The speed will default to how you recorded
it and this will reduce the amount of time you spend on changing
timings.
13) Captions: My rule of thumb is minimum of 4 seconds - and
longer depending on the amount of words. Eg. Click 'Print Preview'
is 4 seconds, a paragraph is longer. If you creating knowledge
based modules, make the timing long (eg. 2-3 minutes) and put in a
next button so that the learner can click when they are ready.
Also, narration means the slides will normally be slightly longer.
14) Be creative: Capitvate is desk bound. There are some
learners that just don't respond no matter how interactive
Captivate can be. Incorporate non-captivate and desk free
activities. Eg. As part of our OHS module, there is an activity
where the learner has to print off the floor plan, and then wander
around the floor marking on th emap key items such as: fire exits;
first aid kit, broom and mop cupboard, stationary cupboard, etc.
Good luck!

What are the best practices for using the enhancement framework?

Hello enhancement framework experts,
Recently, my company upgraded to SAP NW 7.1 EhP6. This presents us with the capability to use the enhancement framework.
A couple of senior programmers were asked to deliver a guideline for use of the framework. They published the following statement:
"SAP does not guarantee the validity of the enhancement points in future releases/versions. As a result, any implemented enhancement points may require significant work during upgrades. So, enhancement points should essentially be used as an alternative to core modifications, which is a rare scenario.".
I am looking for confirmation or contradiction to the statement "SAP does not guarantee the validity of enhancement points in future releases/versions..." . Is this a true statement for both implicit and explicit enhancement points?
Is the impact of activated explicit and implicit enhancements much greater to an SAP upgrade than BAdi's and user exits?
Is there any SAP published guidelines/best practices for use of the enhancement framework?
Thank you,
Kimberly
Edited by: Kimberly Carmack on Aug 11, 2011 5:31 PM

Found an article that answers this question quite well:
[How to Get the Most From the Enhancement and Switch Framework as a Customer or Partner - Tips from the Experts|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0f0373e-a915-2e10-6e88-d4de0c725ab3]
Thank you Thomas Weiss!

ES2 best practice for how much stuff should be in one application?

Similar Messages

Maybe you are looking for