REG : in which memory area BackGround process will execute??

hi everyone,
             in which memory area , background process will be executed ?
Thanks and Regards,
Nikhil K

Hi,
i want to know if both SAP memory and ABAP memory are not present then in which area Background processes will be executed.
erm, they are always present. Processes do not execute "in" these 2 memories. I advise you to read some reference documentation: [SAP library: Functions of the SAP Memory Management System|http://help.sap.com/saphelp_nw70/helpdata/en/02/96279d538111d1891b0000e8322f96/frameset.htm]
The only difference I know between dialog and background is the sequence in which the roll, extended and heap memories are allocated.
Sandra

Similar Messages

  • Where (which folder) are BPEL processes deployed?

    As far as I know BPEL processes are deployed into the folder
    <APPSERVERHOME>\bpel\domains\default\deploy
    But much to my surprise there are NO processes inside.
    On the contrary I found my searched process in the folder
    <APPSERVERHOME>\bpel\domains\default\tmp
    What is the difference between these folders?
    Can I just delete singel processes from these folders in order to manually undeploy them?
    Or is there no such "hot undeployment" but only the official one through
    the BPEL console?
    Peter

    Hi,
    The deploy directory is used only to deploy the BPEL process. Then the deployment is finished, the jar file is removed.
    The tmp directory is used to store local copy of the build BPEL process. It contains all the bpel source and class files of your BPEL process.
    If you delete the process from the tmp directory (.bpel_xxxx), the bpel engine will create it again at the next startup of your domain (when all the processes are loaded).
    You have two ways to undeploy processes.
    - The first one is from the BPEL console, but it is bit tricky when you have lots of processes.
    - The second is from the BPEL API. Check the API for the IBPELDomainHandle Interface (http://download.oracle.com/docs/cd/E11036_01/integrate.1013/b28986/com/oracle/bpel/client/IBPELDomainHandle.html).
    There is an undeployProcess() method which takes an IBPELProcessHandle. You can get this handle by using the listProcesses() method.
    Hope this can help.
    Raphaël
    http://bpelsoa.blogspot.com/

  • SAP BI 7 - Background process performance Issue

    This question is about efficiency of dialog process compared to inefficiency of the background process and I want suggestions from SAP Basis/BI experts on this.
    We have observed that our background processes on BI server are not running as efficiently as we would like them to run.
    For example
    DSO activation:
    When I use Dialog mode for DSO Activation with 3 parallel processes, I can activate a certain DSO with in 15 seconds. But the same DSO and the same data package when activated using background mode with 3 parallel process takes about 15 minutes.(there are plenty of background processes available on the system when this activation is running). So dialog process runs 60 times faster than background process.
    In BI 7 most of the operations can be executed only in the background parallel mode. And from the activation example we know that our background processes are not as efficient as dialog processes. It
    is understood that in general the background processes will not be as efficient as dialog processes, but in our case the difference is a factor of 60. We want help to identify, why the background processes are not as efficient as dialog processes. What SAP Basis settings need to be changed to make them as efficient as we can. Any suggestion or help will be highly appreciated.

    Hello Eswaran
    Generally a dialog process is not faster by any means than a background workprocess. Nevertheless i trust you on your observations, so there must be some difference. I just did a small test, i ran SE16 chose a big table and selected 10000 rows, i did 3 tries in dialog and 3 in background. The results:
    dialog: 10.2s, 9.4s, 9.6s
    background: 26s, 24s, 24s
    So even in my simple example the background execution took more time. The issue here is, that the resulting output (which is pretty large) had to be saved additionally in a spool (a total of 167 pages) when executed in background. The selection of the data certainly did not take more time in either case.
    The most important difference between dialog and batch processes is the memory management. Dialog processes work with a shared memory segment (extended memory). Background processes have their private heap memory.
    Nevertheless, background processes are not "slower" in general, not at all. You will need to observe closer, what your processes are doing. Maybe watching SM50 while running the DSO activation is enough to see it, maybe you need to trace a process. If you see large spools generated, or huge amounts of memory consumed, we might already have an answer.
    Regards
    Michael

  • Measure optimal values of background processes (RMON,PMON,RECO)?

    Hi buddy's,
    I am facing issue to determin optimal values of oracle EBS R12 background processes like (RMON,PMON,SMON,RECO)?
    I want to determine and find it's maximum optimal values of each process with step by step guide because i am new in oracle.
    My purpose is that if i found the optimal values of all background process then while during tuning it is clear for me to what i want to achieve.
    Kindly help me and clarify this scenario how is it possible ?
    Best Regards,
    Waqar Arif

    Hi,
    You should learn some concepts first because you seem very very very new. RMON,PMON,SMON,RECO are background processes of Oracle database and there isn't anything called "value" associated with them. you can't control them or set any value for them. These are background processed which will rung when your instance will start.
    See bellow for some concepts
    http://docs.oracle.com/cd/B28359_01/server.111/b28318/memory.htm
    Salman
    Edited by: Salman Qureshi on Apr 10, 2013 2:45 PM

  • Background process going to " abap/heap limit"

    Hi All,
    When i check the trace file of the workprocess which is a background process it shows that the
    " WP has reached abap/heap limit"
    Does this trigger the dialog process into PRIV mode? or is it OK for a background process to reach the heap limit.
    Please advise.
    Best Regards,
    DVRK

    Hi Ramakrishna,
    The trace you are seeing is for the background process  and is no longer related to dailog process.
    Some times we can see the abap/heaplimit issues due to background jobs running parallely on the same host.
    When the abap/heaplimit reaches max. the job gets cancels
    Try to trigger the job on low load instance
    (or).
    If this occurs on a regular basis. Try to find out the jobs which are failing and tune them accordingly
    (or)
    Take the help of Basis in fine tuning the abap heap memory parameters.
    Hope I answered your query.
    Regards
    Sandy

  • Background Processing & Update Task

    Are "background processing" and "update task" processing the same? I have a function which is timing out and I need to have it run in the background.  If I used the CALL FUNCTION <name> IN UPDATE TASK, would that provide the same resource level and time allowance as having the logic run via a SUBMIT?

    Hi,
    This is the F1 documentation for calling a FM in Update task
    Flags the function module func for execution in the update task. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task.
    This is the F1 documentation for calling a FM in background task
    Flags the function module func to be run asynchronously. That is, it is not executed at once. Instead, the data passed using EXPORTING or TABLES is placed in a database table and the next COMMIT WORK executes it in another work process.
    Hope this helps
    Regards,
    San

  • Servlet background process on tomcat 4.0.2

    i have 1 servlet which will run a thread, background process, whenever the init() on that servlet called. i tried on tomcat 3.3a and tomcat 3.2.3, and both tomcat will run my servlet's background process, will run the thread. but, when i run the servlet using tomcat 4, tomcat 4 will run the init(), but when it do not start the thread. what happen?... i used the same code, servlet, on tomcat 3.2.3, 3.3a and 4....
    can anyone explain it to me?.....

    my code look like this:
    public class Discover extends HttpServlet implements Runnable
    Thread t = null;
    boolean running = false;
    public void init()
    t = new Thread(this);
    t.start();
    System.out.println("thread start");
    public void doPost(HttpServletRequest request, HttpServletResponse response) throws
    ServletException, IOException
    response.setContentType("text/html");
    PrintWriter out = response.getWriter();
    out.println("discover=" + running);
    public void run()
    running = true;
    System.out.println("thread running...");
    * do some stuff here....
    running = false;
    System.out.println("thread stopped...");
    i tried this servlet on tomcat 3.2.3 and 3.3a and the thread run. i can see the 'thread start', 'thread running' and 'thread stopped' on the tomcat console. but, when i use tomcat 4, i can only see 'thread start' on the console, which show that the run() is not execute...... y?... please help me.......

  • SAP Profile Parameters which controls the [ Background Jobs ]

    Hi,
    Is there any SAP Profile Parameters which controls the [ Background Jobs ] getting executed.
    Also I would like to know especially if there are any Timeout Parameters for Background jobs getting executed in the ABAP System.
    Thanks in advance.
    Regards,
    L Raghunahth

    Hi
    Thanks for your reply..
    based on your reply , I searched and found a parameter called rdisp/max_wprun_time
    The description given for the parameter is "Maximum work process run time"
    Do you have any idea about what is this parameter for ?
    Thanks again
    Best Regards
    L Raghunahth

  • Shared Memory Areas not accessible in background processing

    Hi there
    We're using Shared Memory Areas to share data between an on-line transaction and a background program. The on-line transaction collects the data, creates the Shared Memory Area and submits a background job to process it. So, after the detach_commit, it performs submit program via job_name xxxx number nnnn.
    It works OK in our dev and quality systems, but does not work in our production system. The memory area is created OK, but the job cannot access it. In the background program, we get the message:
    "The read lock on the instance 'ZNNNNNNN' in the client '100' of the shared objects memory area 'ZCL_XXX' cannot be set, since there is no active version of this area instance. However, the area constructor for the automatic construction of the area instance was started."
    On the SMA side, we've tried seemingly every combination, even "propagate_instance".
    The job seems to be running on the same application server as the SMA.
    Any ideas about what we're doing wrong, anyone?
    Thanks
    Ged

    Hello Ged,
    Please remember that SHM is accessible across one App Server(AS) only.
    If your SAP landscape has multiple AS's then it might pose a problem. When you're scheduling the background job, i guess that the Bgd work process is started in a different AS(load balancing ) and hence SHM is no accessible.
    If this is the case, then you've no other option but to store the data persistently in DB clusters viz., INDX-type tables (EXPORT TO/IMPORT FROM DATABASE).
    BR,
    Suhas
    Message was edited by: Suhas Saha

  • Why may any user leave background processes running at will?

    Hi all,
    yesterday, I encountered a rather strange problem with linux in common, at least
    I think so.
    In my .xinitrc, I'm starting offlineimap - a console-based mail synchronization
    tool - in the background. Being naive, I expected it to be killed along with the
    gui applications started in that file. Yet, that assumption proved wrong and I
    started asking for help on how to kill that process on #archlinux.
    The guys there (again, thanks for your help and patience!) all came up with
    plenty of ideas on how to avoid starting more than once instance of the program,
    but that wasn't really what I was looking for. The only usable option came from
    anrxc, who suggested killing the program from awesome's logout hooks.
    Not fully satisfied with the solutions, I started thinking and came up with the
    following question:
    Why is every user allowed to leave background processes on the machine
    just as he pleases, even if he logs out?
    I even tried this over ssh, where the launched commands have some sort of
    "parent" process, but even in this circumstance it was possbible to leave
    background processes behind after logging out.
    I mean, on my desktop system, this is not a big issue... I shut it down once
    every day at the least and there are no users on it besides my girlfriend and
    me. But this seems like a fundamental problem to me. Why is this allowed at all?
    Does it make sense to do it that way? What are the consequences?
    Let's discuss!

    JohannesSM64 wrote:Really, you need to find a better way to manage offlineimap than starting it in xinitrc. Automatically killing any background processes on any logout will not make linux better.
    Hmm... to me, .xinitrc is the place to start apps which should live just as long
    as the graphical user login lasts. On #archlinux, several other places were
    discussed, but none of them were "the thing":
    .bashrc
    Doesn't work, because a) the process would only get started when I open a shell,
    not when I log in and b) because finding a place to stop the process would be
    even harder.
    .bash-profile
    Only gets executed for a login shell, which I wouldn't account for a graphical
    login at all.
    wm startup script (in this case awesome's rc.lua)
    Possbile, but not much better. Would fork the process all the same, merely
    moving the problem. If X got killed, not even awesome's logout hooks would
    apply.
    Also, this approach isn't wm-agnostic, so trying out / switching to another wm
    would have the problem occur all over again.
    So what do you suggest? Do you have a good idea?
    pseudonomous wrote:
    As to the question of "why" things act this way:
    I believe this is linux display it's heritage as a mulit-user operating system that people used terminals to log into to run program on.  A big place where unix used to be (and is, to some degree, still used) was in universities where a professor or graduate student might have logged onto the system to run some program to process some large set of data.  You wouldn't want to sit around and wait for this program to finish; you'd want to run it in the background, leave, and come back and look at the results a week later, when the program finished running.  One of my friends doing applied math research still does this sort of thing.  I'd imagine it's relatively common.
    Process management was largely handled be systems administrators, and commonly you were being billed for CPU time, so it was in your interest not to leave programs that you didn't want to run running when you logged out.
    Hmmm... that seems like a rational explanation. But in the case that is the
    reason for linux' behavior: Why isn't there some kind of a mode setting? Like
    one which allows any user to keep processes alive and another one that doesn't?

  • The memory on my MAC is full. It holds 4GB of RAM of which 79GB are photos. I would like to back up my photos to an external drive but just don not know how. I do not wish to use time machine. How do I back up my photo library, then delete the them t

    The memory on my MAC is full. It holds 4GB of RAM of which 79GB are photos. I would like to back up my photos to an external drive but just do not know how. I do not wish to use time machine. How do I back up my photo library, then delete them from my MAC to free up that 79GB? Thank you.

    Hi
    Just to clarify a couple of points in your post.
    RAM (memory) is different from hard drive space. You have 4GB of RAM, but that has no bearing on the amount of drive space you have, of which we know that 79GB are photos.
    If those photos are in iPhoto, you should be able to move the entire iPhoto Library, from the Pictures folder, to your external hard drive. You can just drag and drop. Do not have iPhoto open while you're doing this. Once it's done, you can double-click on the moved iPhoto Library file to associate it with iPhoto, so that the app remembers where the library is for next time.
    One more thing. When you move a file to a different location, and then delete the original, you don't have a backup. You still only have one copy. So if that external drive dies, you will lose all your photos. Time Machine is a very good way to prevent this from happening. You should dedicate a different drive for Time Machine backups.
    Matt

  • CC background processes are locking my CPU since updates for CC 2104 released

    Two hours with Apple points to background processes of Creative Cloud consistently locking up my iMac CPU around 5 min and 45 secs after booting up. 
    Issues stated last week Thursday after updates released, progressed Friday to the point of not being able to perform any tasks on my workstation after the 5:45s time window.
    Attempted to upgrade CC apps to 2014 and was able to get CC Illustrator 14 installed but CC Photoshop 14 fails around 42% everytime I try. Have not updated any other apps (indesign, etc).
    Have seen mention of others having same CPU lock up now.
    Tried phone support - discounted when transferred to a busy signal after 17 min and two operators.
    Can NOT work this way - need answers.

    Anthony,
    IMHO, locking by task id is not advisable because effectively you are going to allow only one instance of the task type to execute at a time. What if an instance of the task has different materials?
    If you still want to play with your idea, the code below in your object method will get the current task id.
    DATA:
      workingwi       type swc_object,
      TASK            type SWWWIHEAD-WI_RH_TASK.
    swc_get_element container '_Workitem' workingwi.
    swc_get_property workingwi 'WorkitemTask' task.
    Cheers,
    Ramki.

  • When will Apple allow background processes for the iPhone?

    Can't find a suitable subforum so I'll post it here, please refer me to the correct Apple forum otherwise.
    When will Apple allow background processes for the iPhone?
    When will Apple allow Alerts from 3rd party apps?
    Even my first Palm Pilot allowed developers to use Alert beeps.
    Why is Apple crippling the iPhone?
    If they continue this, Android will be the winner.
    Or will the next SDK allow this?

    Background processing, simply won't. They already said they won't and explained why.
    However, they are currently adding "Push" ability to developers (soon). Originally they did say they were shooting for Sept (but obviously that has passed). Nobody can say "why" it is late or when it will come. Just know it is coming.
    Push in case you don't know will let a service (one service) run in the background that apple makes for the phone. that service will ping apple's servers. Apps that want to "run" in the background have to register with that service thus lets say AIM is on your phone, you send a message and close...somebody responds. AIM's servers will send notification to the push service...then the phone will alert you of a notification in the AIM app, you open (thus starts the app again) and it gets the message.

  • Which background process writes date into alert log file in oralce

    which background process writes date into alert log file in oralce

    Hi,
    AFAIK, all the background process are eligible for writing information to alert log file. As the file name indicates to show the alerts, so background process have the access rights in terms of packages (dbms), to write to alert log.
    I might be wrong also..
    - Pavan Kumar N

  • How can I get rid of the dark area on top one third of my iphone screen which spoils my background image?

    How can I get rid of the dark area on top one third of my iphone screen which spoils my background image?
    It seems this problem is caused by the software to increase the readibility of upper letters (clock battery etc.) It be nice to leave us the control of choosing background letter color too if we are using brighter images or darker images.
    I'm using iphone 4s and it appeared after I updated to new patch. 7.1.1.
    Thanks,
    Cem
    I do not know how to move topics from sections of forum so I apologise for duplicate post.
    https://discussions.apple.com/message/25594879#25594879

    Photo added.

Maybe you are looking for