Regarding job scheduling

hi gurus,
Im trying to schedule a job. everything is going right but the problem is that in the backgroung job i'm exporting an internal table in the memory id. this internal table, in the memory id, im importing in my background programm. but im not able to get the imported data from the memory id.
how to over come this condition.

You must have the same structure for both the internal tables.
Check out are they same? IF they don't have same definition then you have to make then with the same structure.
Can you please paste your code which does the Import / Export. ?
Regards,
Naimesh Patel

Similar Messages

  • Help requested regarding job scheduling for an action

    Hi Gurus,
    I have created an action with a custom method. This method is used to change the status of all the subsequent tasks from that transactions. In case if any of the tasks is opened while the action is executing then the action would error out. To reprocess such action I created a job for the variant created in CRMC_ACTION_MONITOR. But it doesnt seems to work. Please suggest how to go about it.
    Thanks and Regards,
    Jai

    Did you set processing time for an action as "Processing Using Selection Report"?
    Did you create variant in SPPFP and defined "Processing without dialog"?
    Did you schedule job for program RSPPFPROCESS and your variant of report?

  • Regarding Job Schedule

    Hi,
    I need to execute a Report u2018YBu2019 on a next day (If I execute a report u2018YAu2019  today, then Report u2018YBu2019 in u2018YAu2019  should get executed on next day at 10.00 AM).
    REPORT YA
    jobname = 'YSAUs_JOB'.
    Open Job
    CALL FUNCTION 'JOB_OPEN'
    EXPORTING
    jobname = jobname
    IMPORTING
    jobcount = w_jobcount.
    SUBMIT YB VIA JOB jobname NUMBER w_jobcount AND RETURN USER sy-uname.
    Schedule and close job.
    CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
    jobcount = w_jobcount
    jobname = jobname
    sdlstrtdt = lv_start_dat u201C sy-datum +1
    sdlstrttm = '100000'.
    But My job is not getting scheduled. I get an error saying use job step not given correctly so unable to start job. It is suggesting to use JOB_SUBMIT FM.
    Please provide your valuable inputs on this.
    Thanks in advance.

    Hi,
    Try like this:
      DATA: I_VARID  TYPE STANDARD TABLE OF VARID,
            WA_VARID TYPE VARID.
      DATA: V_REPO TYPE RALDB_REPO,
            V_VART TYPE RALDB_VARI.
      RANGES: R_REPO FOR VARID-REPORT,
              R_VARI FOR VARID-VARIANT.
      R_REPO-SIGN = 'I'.
      R_REPO-OPTION = 'EQ'.
      R_REPO-LOW = 'RMMMPERI'. " Name of Program
      APPEND R_REPO.
      R_VARI-SIGN = 'I'.
      R_VARI-OPTION = 'EQ'.
      R_VARI-LOW = 'ZMMPV'. " Name of Varient
      APPEND R_VARI.
      SELECT * FROM VARID
             INTO TABLE I_VARID
             WHERE REPORT IN R_REPO
             AND VARIANT IN R_VARI.
      LOOP AT I_VARID INTO WA_VARID.
        V_REPO = WA_VARID-REPORT.
        V_VART = WA_VARID-VARIANT.
    ENDLOOP.
        CONCATENATE SY-UNAME
                      SY-DATUM
                      SY-UZEIT
                              INTO W_JOBNAME .  " Assign unique jobname
        CALL FUNCTION 'JOB_OPEN'
         EXPORTING
          JOBNAME                = W_JOBNAME
        IMPORTING
         JOBCOUNT                = W_JOBCOUNT
       EXCEPTIONS
         CANT_CREATE_JOB        = 1
         INVALID_JOB_DATA       = 2
         JOBNAME_MISSING        = 3
         OTHERS                 = 4
        IF SY-SUBRC <> 0.
          MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
        CALL FUNCTION 'JOB_SUBMIT'
          EXPORTING
          AUTHCKNAM                         = SY-UNAME
          JOBCOUNT                          = W_JOBCOUNT
          JOBNAME                           = W_JOBNAME
          REPORT                            = V_REPO
          VARIANT                           = V_VART
         EXCEPTIONS
           BAD_PRIPARAMS                     = 1
           BAD_XPGFLAGS                      = 2
           INVALID_JOBDATA                   = 3
           JOBNAME_MISSING                   = 4
           JOB_NOTEX                         = 5
           JOB_SUBMIT_FAILED                 = 6
           LOCK_FAILED                       = 7
           PROGRAM_MISSING                   = 8
           PROG_ABAP_AND_EXTPG_SET           = 9
           OTHERS                            = 10
        IF SY-SUBRC <> 0.
          MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
    jobcount = w_jobcount
    jobname = w_jobname
    sdlstrtdt = lv_start_dat u201C sy-datum +1
    sdlstrttm = '100000'.
    Regards,
    Bhaskar

  • NWA Job scheduler, how to change parameters?

    Dear guys,
    moving to AEX (java-only) the ABAP Stack is gone.
    Regarding job scheduling there is no more transaction sm37, but Job scheduler within NWA to be used for scheduling jobs.
    I configured a job for the predefined job definition AlertConsumerJob to get emails in case of alerts.
    Doing this the questions arises how to change parameters once a job is scheduled e.g. add additional email receiver.
    So far is seems you have to stop the configured job and define a NEW one from scratch by providing all job parameters. It seems not possible to adjust a job.
    This is not very comfortable?
    Is there an workaround / solution for this?
    Best regards
    Jochen

    Hello Gaurav
    thanks for your reply.
    It's a pity, but shows that there is still some room of improvement regarding AEX functionality (java only)
    Best regards
    Jochen

  • Regarding Background Job scheduling for file to file scenario

    Hi Guru's
    Good morining all of u
    I have one doubt on ...
    can we do background job scheduling for file to file scenario?
    Please give me response as early as possible.
    thanks and regards
    sai

    background jobscheduling for file adapter...
    you can schedule the file adapter according to your requirement as follows:
    In the  Communication Channel Monitoring Locate the link Availability Time Planning,  In Availability Time Planning, choose the Availability time as daily and say create, give the time details, select the communication channel in your case file adapter , goto the Communication Channels tab and filter and add the respective channel, save it
    /people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

  • This is regarding back ground job scheduling

    Hi to all...........
    1....here iam using background job scheduling for a report to run under background.I difine the backgorund job at sm36 and i had given the job name and time ,date in sm37.
                            With this details the report executed sucessfully.Now i want to see the output list for that report.Please tell that where i have to see the output list.
    what is the transaction code for displaying that output list?????????????????
    Thanks and regards,
    k.swaminath

    Go to SM36.. select ownjobs..
    List will come.. Select your job (check box) and click SPOOL ...
    Output will come like this..
      Spool no.  Type Date       Time  Status  Pages Title
           16501      24.10.2007 11:25 Waiting    7  LIST1S LOCA Z00_SELECT_S
    Press the Icon under Type...
    Output will get displayed..
    Message was edited by:
            Rama Jyothi

  • Regarding automatic job scheduling

    hi experts,
    i have done automatric job scheduling with the help of tc-SM36,so that the my report will run on every morning at 9oclock but in the development server i did it n it is working fine what i want to know that i have to do the same thing in the production server will i have to do it directly on the production server or will it be stored in the request number and then i have to transport it to the production server........
    plz help me....

    Hello Rajat,
    You might want to look into SAP Central Process Scheduling by Redwood. This might solve your problems as SM36/37 is in maintanace mode and will not be developed any further this is a good step to make.
    The link is:
    Scheduling
    The product can be downloaded from the SWDC under Application Group SAP Netweaver, Netweaver 7.0, SAP Central Process Scheduling.
    if you have any questions do not hesitate to give me a call 031306354598
    Regards,

  • Background Job Scheduling

    Hi,
      I am scheduling a report to run in background.
    In this report it is creating background jobs automatically for different company codes.
    It submits the 1st background job and waits until it finishes.
    Then 2nd job starts in background and continues with other jobs.
    At end it finishes all the jobs and closes.
    Now my problem is.
    1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
    2.       If possible how can we do that.
    What I have written is
    loop at companycode.
    Create job name.
    call fun 'Job_Open'.
    submit xxxx user sy-uname via job job_name numer job_count
    to sap-spool
    spool parameters l_spool_parameter
    without spool dynpro
    with companycode
    with ......
    and return.
    endloop.
    Please help ASAP, urgent.

    hi praveen,
    Job Scheduling Explained
    Definition
    Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the job’s definition. There are several ways to schedule jobs:
    From Transaction SM36 (Define Background Job)
    With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
    Through the background processing system’s own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
    Through an external interface.
    Scheduling Background Jobs   
    Use
    You can define and schedule background jobs in two ways from the Job Overview:
    ·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
    ·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
    Procedure
           1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
           2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
           3.      Set the job’s priority, or “Job Class”:
    ·         High priority:      Class A
    ·         Medium priority: Class B
    ·         Low priority: Class C
           4.      In the Target server field, indicate whether to use system load balancing.
    ·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
    ·         To use a particular application server to run the job, enter a specific target server.
           5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
           6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
           7.      Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
           8.      Save the fully defined job to submit it to the background processing system.
           9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
    Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
    Specifying Job Start Conditions
    Use
    When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
    Procedure
    Choose the Start condition button at the top of the Define Background Job screen.
    Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
    For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
    Once you’ve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
    No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
    Managing Jobs from the Job Overview
    Use
    The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
    Procedures
    To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
    To copy a single existing job, choose Job ® Copy.
    To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
    To repeat a single job, choose Job ® Repeat scheduling.
    To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
    You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
    To review information about a job, choose Job ® Job details. Details displayed can include:
    current job status
    periodicity, or the repetition interval
    other jobs linked to the current job, either as previous or subsequent jobs
    defined job steps
    spool requests generated by the current job
    To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
    To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
    To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
    To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
    To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
    To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
    regards
    karthik
    reward me points if helpfull

  • Job Scheduling in Solution Manager - Error creating Periodic Job

    Hi all,
    I am in the process of testing the Job Scheduling functionality using the Solution Manager.  I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well. 
    I am able to successfully setup up a 'on-time' job.
    it's only when I try to setup a periodic job, I end up getting following error
    Any thoughts?  Is there any piece of config that's missing?  All the SICF services needed for this functionality are running fine.
    Thanks for the help.
    500 Internal Server Error
    Error when processing your request
    What has happened?
    The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
    Note
    The following error text was processed in the system PSM : Message was not created
    The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
    The termination type was: ERROR_MESSAGE_STATE
    The ABAP call stack was:
    Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
    Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
    Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
    Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
    Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
    Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
    Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

    Hello,
    This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
    Have you performed the IMG Activiteis in SPRO?
    See the following Help link:
    http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
    Change a job
    You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
    Make changes.
    Note
    When you change a periodic job, the system searches for the changeable successor and only changes this successor.
    If there is more than one changeable job with the same name, the system does not change any of these jobs.
    End of the note.
    Save your entries.
    To release the job in the target system, select Release.
    You go to the transaction SM37 in the target system.
    You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
    Regards,
    Paul

  • About Background job scheduling

    One file will be coming from oracle system. it would be stored at a particular path.
    I want to schedule for background job processing. how to do.

    Hi,
    You need to write a Program to place the file in the Application server, then only you can schedule a background job, you need to use the OPEN dataset, CLOSE DATASETS to do this one, then you can schedule the job .
    To schedule a job in the background job, look at the below links
    Re: background job schedule
    http://aspalliance.com/1129_Background_Processing_SAP_R3_System
    Regards
    Sudheer

  • Background job scheduling edit

    Hi
    i have a program which executing as a background job for every 3 minuts. but some times the job which is in process is taking a long time like up to 5 minuts and as per job scheduling after 3 minuts of first scheduled job, it is starting another same job. like that sometimes it is going upto 4 to 5 same job is processing. 
    Is there any solution like :  only one of that  job should be in the job execution process . but once the job is running the same job should not start. but if it is completed with in 3 minuts the job should be start as scheduled.
    Thanks in advance

    Hi,
    I think there is a way in Job scheduling itself to define the next job only when the current one is complete (irrespective of how the execution takes place).
    I recently recd help on this topic.. if you are triggering jobs from a program, you can add the foll code to make the second job (or further progm processing) to wait till the current job is over..
            WHILE v_fin IS INITIAL.
                  CALL FUNCTION 'SHOW_JOBSTATE'
                    EXPORTING
                      jobcount         = l_jobcount
                      jobname          = l_jobname
                    IMPORTING
                      finished         = v_fin
                    EXCEPTIONS
                      jobcount_missing = 1
                      jobname_missing  = 2
                      job_notex        = 3
                      OTHERS           = 4.
                  IF sy-subrc <> 0.
                    ERROR_JOB = '1'.
                    v_fin = 'X'.
                  ENDIF.
             ENDWHILE.
    Hope this helps.. Regards, Liz

  • Background job schedule and mail triggering

    Hi Experts,
    I schedule a background job to run a custom program for project closure.The job is running successfully. But,the mail I am getting from this job run is same all the time (means it's showing same project closure again and again though I am running job for different projects). Is it some bug in our custom program or any parameters required to be check in job schedule?
    Kindly suggest.
    Thanks & Regards
    Saurabh

    Yes. That is the point I am missing. Just one 'date' is checked and project is taken into account for the custom program and after its successful run the mail is sent to users.
    And when the same program I am assigning in SM36,it is actually running the program accurately for project/s but sending the same mail which it send for very first project earlier.
    Can you please guide me on the way to create these variants? 
    You will need to Save different variants for different projects and then assign the variants with your job.
    Will it be required to create variant again and again and assign different projects individually? As, we are not sure that which project is gonna be created in future. So, need guideline how these variants can help me to sort out the e-mail issue.
    Regards
    Saurabh

  • Error in tabstrip control progtram while in Background job scheduling

    Hi ABAPer's,
    I need some help...I developed one tabstriip control program with 3 tabs. while excute it in foregroung it is executing nice..but while i am job scheduling the same program in background it was getting error's like .........
    Control Framework: Fatal error - GUI cannot be reached      
    SET SCREEN not allowed in subscreens (screen: <Report Name> 0100)
    so..if any body know the solution ...plz help me...
    Thanks & Regards
    Srinivas-SAP,

    Hi,
    please go through the functionality of tabstrips.
    basically they are placed on tabstrips.
    so they dont have their own ok codes and call screen and set screen ( to best of my knowledge )
    can not be used.
    if you are using set screen remove them.
    even without using set screen if you are gettig the error, please let us know.
    regards
    Ramchander rao.K

  • Creation of batch job Schedule

    How to create new batch job Schedule ?
    Regards,
    Sridhar

    Hi,
    For more details about background processing go through the link provided.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7ede505211d189550000e829fbbd/frameset.htm
    Hope it helps you.
    Regards
    CSM Reddy

  • SSIS Package compiled successful, in SQL Server Integration Service package executed sucessful, But fail to run in MS SQL Job Scheduler

    Hi Everyone,
    I having a problem to transfer data from MS SQL 2005 to IBMAS400. Previously my SSIS was running perfectly but there is some changes I need to be done in order for the system to work well. Considers my changes are minimal & just for upgrades (but I did
    include DELETE statements to truncate AS400 table before I insert fresh data from MS SQL table to the same AS400 table), so I compile my SSIS package & it run successfully & I passed it into MS SQL Integrated Service as 1 of the packages & manually
    executed the package & the result is the same, that mean it was successful again but when I try to run it in a MS SQL Job Scheduler, the job failed with these message shown below as extracted from the job View history. 
    Date today
    Log Job History (MSSQLToAS400)
    Step ID 1
    Server MSSQLServer
    Job Name MSSQLToAS400
    Step Name pumptoAS400
    Duration 00:00:36
    Sql Severity 0
    Sql Message ID 0
    Operator Emailed
    Operator Net sent
    Operator Paged
    Retries Attempted 0
    Message
    Executed as user: MSSQLServer\SYSTEM. ... 9.00.4035.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    
    Started:  today time  
    Error: on today time     
    Code: 0xC0202009     Source: SSISMSSQLToAS400 Connection manager "SourceToDestinationOLEDB"     
    Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. 
    Error code: 0x80004005.  An OLE DB record is available.  
    Source: "IBMDA400 Session"  
    Hresult: 0x80004005  
    Description: "CWBSY0002 - Password for user AS400ADMIN on system AS400SYSTEM is not correct ".  End Error  
    Error: today     
    Code: 0xC020801C     
    Source: Data Flow Task OLE DB Destination [5160]     
    Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "DestinationClearData" failed with error code 0xC0202009.  There may be error messages posted before
    this with more information on why the AcquireConnection method ca...  The package execution fa...  The step failed.
    So I hope somebody can shed some hints or tips for me to overcome time problem of mine. Thanks for your help in advance. As I had scoured thoroughout MSDN forums & found none solution for my problem yet. 
    PS: In the SQL Integrated Services when I deployed the package I set the security of the packages to Rely on server... 
    Hope this will help.

    Hi Ironmaidenroxz,
    From the message “Executed as user: MSSQLServer\SYSTEM”, we can see that the SQL Server Agent job ran under the Local System account. However, a Local System account doesn’t have the network rights natively, therefore, the job failed to communicate with
    the remote IBMAS400 server.
    To address this issue, you need to create a proxy account for SQL Server Agent to run the job. When creating the credentials for the proxy account, you can use the Windows domain account under which you executed the package manually.
    References:
    How to: Create a Credential
    How to: Create a Proxy
    Regards,
    Mike Yin
    TechNet Community Support

Maybe you are looking for

  • How to get a host-name representing a WebLogic cluster

    Hi guys, We are using weblogic to deploy a service. Service uses the below property to connect on managed port and get datasource informations PROVIDER_URL=t3://abc.com:20005 Now this is fine but in PRODUCTION we have cluster who have 2 machines-mang

  • Is the purchased version of Lightroom 4 the same as the free trial version?

    When I watch the tutorial videos about LR4 they show things I can't find on my trial version. I'm wondering if there's a difference or if I just don't know how to use it correctly.

  • Installing Netbeans on RedHat Enterprise 5 Linux

    Hello, After installing both the jre-6u2 and jdk-6u2 RPMs I have had no problems getting netbeans to work... However what caused me to stay up rather late trying to get this thing installed originally was the fact that the installer asks specifically

  • UWL Configuration for KM Resources

    We are creating XML documents in KM folders using custom PAR file based iViews.  These XML documents do go through approval process.  When a notification received by an approver in UWL, the link the task is opening XML document in browser.  Instead,

  • BAM 11g Moving External Object Data to Internal Data Object

    Hi I'm working with external data objects in our dashboards, this objects are updated every 30 minutes. It's posible to update Internal Data objects at same time using triggers in BAM schema for use Active Data? I need to autorefresh the Dashboard ev