Oracle concurrent program run alone

Concurrent, in English means, simultaneous, happening at the same time. Likewise in Oracle E-Biz, a concurrent program can be termed as a program that runs simultaneously with the application without disturbing the later.

So our application is live, and hundreds of thousands of users are accessing our system, and our business needs some reports or some updates at the same time, then how are we going to do that? Oracle E-Biz gives a dedicated server to run Concurrent Programs, which is capable to run the requests without impacting the performance of the actual application.

The Concurrent programs can be designed, defined and deployed to help business with these kinds of requirements. There are four distinct processes involved with the definition of a Concurrent Program.

Logical databases ensure that this does not happen. A Standard logical database can be assigned to every Oracle E-Business Suite product so that every concurrent program, if incompatible with any other program, does not run concurrently with that program, regardless of which ORACLE schema those two programs connect to. You must define new logical databases only if you build a custom application whose data do not interact with data found in existing logical databases.

As a general rule, you should define a logical database for each custom application, and assign that application's ORACLE schema s to the corresponding logical database.

However, if a custom application's data interacts with another application's data, you should assign the two applications' ORACLE schemas to the same logical database. Registering your custom application's tables ensures that the table names appear as QuickPick values in the Define Alerts form.

This report documents concurrent program definitions, including executable file information, execution method, incompatible program listings, and program parameters. If a concurrent program generates a report, column and row information, as well as print output and print style, are also documented.

Use this report when considering concurrent program modifications, such as modifying program incompatibility rules. Caution: If you do not enter any parameters, the report returns values for all concurrent programs, and may be very lengthy. Choose the application name associated with the concurrent program whose program definition details you wish to report on.

Choose only an application name, without a program name, if you wish to run a program definition details report on all concurrent programs associated with an application. Choose the name of a concurrent program whose program definition details you wish to report on. You must enter a value for Application Name before entering a value for Program. The report headings display the specified report parameters and provide you with general information about the contents of the report.

This report shows which concurrent programs are currently enabled nand which programs are disabled. Use this report to record the execution method, argument method, run alone status, standard submission status, request type, and print style information associated with your concurrent programs.

Choose the application name associated with the concurrent programs whose program information you wish to report on. If you do not enter an application name, the report will return values for all concurrent programs.

Use this window to define a request group. A request security group is the collection of requests, request sets, and concurrent programs that a user, operating under a given responsibility, can select from the Submit Requests window. Assign a request security group to a responsibility when defining that responsibility. A responsibility without a request security group cannot run any requests using the Submit Requests window. Can add any request set to a request security group.

Adding a private request set to a request security group allows other users to run that request set using the Submit Requests window. Can create their own private request sets using the Request Sets window. In a private request set, users can include only the requests you assign to their request security group.

Use the request group's name to assign the request group to a responsibility on the Responsibilities window. An application name and request group name uniquely identify a request group.

Select the name of the application you wish to associate with your request group. An application name and a request security group name uniquely identify a request security group. This application name does not prevent you from assigning requests and request sets from other applications to this request group. Assign a code to this request group. Some products use the request group code as a parameter that identifies the requests a customized standard submission form can select. Choose program or set to add one item, or choose application to include all requests in an application.

Define a concurrent program executable for each executable source file you want to use with concurrent programs. The concurrent program executable links your source file logic with the concurrent requests you and your users submit to the concurrent manager. Important: You cannot add new immediate programs to a concurrent manager program library.

We recommend that you use spawned concurrent programs instead. The combination of application name plus program name uniquely identifies your concurrent program executable. Enter a name for your concurrent program executable. In the Concurrent Programs window, you assign this name to a concurrent program to associate your concurrent program with your executable logic.

The concurrent managers use the application to determine in which directory structure to look for your execution file. The execution method cannot be changed once the concurrent program executable has been assigned to one or more concurrent programs in the Concurrent Programs window. Enter the operating system name of your execution file. Some operating systems are case sensitive, so the name entered here should match the file name exactly.

Do not include spaces or periods. Do not use spaces or periods. Enter a name for the Parameter. Use the Concurrent Program Executables window to define a concurrent program executable for your operating system program. The combination of application name plus program name uniquely identifies your concurrent program. You see this longer, more descriptive name when you view your requests in the Requests window.

If this concurrent program runs through Standard Request Submission, you see this name in the Submit Requests window when you run this program.

Enter a brief name that Oracle E-Business Suite can use to associate your concurrent program with a concurrent program executable. The program's application determines what ORACLE username your program runs in and where to place the log and output files. Indicate whether users should be able to submit requests to run this program and the concurrent managers should be able to run your program.

Disabled programs do not show up in users' lists, and do not appear in any concurrent manager queues. You cannot delete a concurrent program because its information helps to provide an audit trail. Select the concurrent program executable that can run your program. You define the executable using the Concurrent Program Executables window.

You can define multiple concurrent programs using the same concurrent program executable. See: Concurrent Program Executables. Some execution methods, such as Oracle Reports, support additional execution options or parameters.

You can enter such options in this field. The syntax varies depending on the execution method. For example, to generate a report with landscape orientation, specify the following option in the Options field:. Do not put spaces before or after the execution options values. The parameters should be separated by only a single space. For example:. The units for your width and height are determined by your Oracle Reports definition. You can switch between Spawned and Immediate, overriding the execution method defined in the Concurrent Program Executable window, only if either method appears when the executable is selected and both an execution file name and subroutine name have already been specified in the Concurrent Program Executable window.

You can assign this program its own priority. The concurrent managers process requests for this program at the priority you assign here. If you do not assign a priority, the user's profile option Concurrent:Priority sets the request's priority at submission time.

If you want to associate your program with a predefined request type, enter the name of the request type here. The request type can limit which concurrent managers can run your concurrent program. For use by Oracle E-Business Suite internal developers only. The incrementor function is shown here. The Multilingual Concurrent Request feature allows a user to submit a request once to be run multiple times, each time in a different language.

If this program utilizes this feature, the MLS function can be used to determine which installed languages are needed for the request. Beginning with Release Check this box to indicate that users can submit a request to run this program from a Standard Request Submission window.

If you check this box, you must register your program parameters, if any, in the Parameters window accessed from the button at the bottom of this window. If you check the Use in SRS box, you can also check this box to allow a user to enter disabled or outdated values as parameter values. These value sets normally allow you to query disabled or outdated values but not enter them in new data. For Standard Request Submission, this means that a user would not normally be allowed to enter disabled values as report parameter values when submitting a report, even if the report is a query-only type report.

Indicate whether your program should run alone relative to all other programs in the same logical database. If the execution of your program interferes with the execution of all other programs in the same logical database in other words, if your program is incompatible with all programs in its logical database, including itself , it should run alone. Use this option to indicate that this concurrent program should automatically be restarted when the concurrent manager is restored after a system failure.

This box is checked if the program allows for a user to submit a request of this program that will reflect a language and territory that are different from the language and territory that the users are operating in. For example, users can enter orders in English in the United Kingdom, using the date and number formats appropriate in the United Kingdom, then generate invoices in German using the date and number formats appropriate to their German customers.

If this box is left blank then a user can associate any installed language with the request, but the territory will default to the territory of the concurrent manager environment. Note that this option should be set only by the developer of the program. The program must be written as NLS Compliant to utilize this feature. Indicate whether to automatically save the output from this program to an operating system file when it is run.

This value becomes the default for all requests submitted for this program. The output of programs with Save set to No is deleted after printing. If this is a Standard Request Submission program, users can override this value from the Submit Requests window. Enter the minimum column and row length for this program's report output. Oracle E-Business Suite uses this information to determine which print styles can accommodate your report.

Your list is limited to those styles that meet your program's columns and row length requirements. If your program requires a specific print style for example, a checkwriting report , use this check box to enforce that print style.

If you want to restrict your program's output to a single printer, enter the name of the printer to which you want to send your output. If your program has minimum or maximum columns or rows defined, your list of values is limited to those printers that can support your program's requirements.

Business events can be raised at key points of the life cycle of a request to run a concurrent program. Users can subscribe to the business events and create their own business processes interacting with the concurrent programs. Create another concurrent program using the same executable, request and report information as the current program. You can optionally copy the incompatibility and parameter details information as well. Use this window to specify options for the database session of the concurrent program when it is executed.

Optionally specify a rollback segment to be used with the concurrent program. This rollback segment will be used instead of the default and will be used up until the first commit. Optionally specify an optimizer mode. You would specify an optimizer mode only for a custom program that may not perform well with the default cost-based optimizer CBO and needs tuning. You can use a different optimizer mode until your program is tuned for CBO.

When requests for this program are submitted, they run on this node if possible. If no specification is made for the concurrent program, a request will be picked up by any manager able to run it. When requests for this program are submitted, they run on this instance if possible. Identify programs that should not run simultaneously with your concurrent program because they might interfere with its execution.

You can specify your program as being incompatible with itself. Although the default for this field is the application of your concurrent program, you can enter any valid application name.

Your list displays the user-friendly name of the program, the short name, and the description of the program. Enter Set or Program Only to specify whether your concurrent program is incompatible with this program and all its child requests Set or only with this program Program Only.

Enter Domain or Global. If you choose Domain, the incompatibility is resolved at a domain-specific level. If you choose Global, then this concurrent program will be considered globally incompatible with your concurrent program, regardless of which domain it is running in.

Enter and update the program parameters that you wish to pass to the program executable. Program parameters defined here should match the variables in your execution file. Enter the parameter which will hold the value of the conflict domain of the program. For information on conflict domain parameters, see Concurrent Conflict Domains. This field is for HRMS security only. Choose the sequence numbers that specify the order in which your program receives parameter values from the concurrent manager.

Disabled parameters do not display at request submission time and are not passed to your execution file. Enter the name of the value set you want your parameter to use for validation. You can only select from independent, table, and non-validated value sets. Important: If you are using a value set of dates, this value set should have a format type of either Standard Date or Standard DateTime if you are using the Multilingual Request feature.

You can enter a default value for the parameter. This default value for your parameter automatically appears when you enter your parameter window. You determine whether the default value is a constant or a context-dependent value by choosing the default type.

Your default value should be a valid value for your value set. Otherwise you see an error message when you enter your parameter window on the Run Request window and your default value does not appear. If the program executable file requires an argument, you should require it for your concurrent program.

If the value set for this parameter does not allow security rules, then this field is display only. Otherwise you can elect to apply any security rules defined for this value set to affect your parameter list. Choose either Low or High if you want to validate your parameter value against the value of another parameter in this structure.

Parameters with a range of Low must appear before parameters with a range of High the low parameter must have a lower number than the high parameter. For example, if you plan two parameters named "Start Date" and "End Date," you may want to force users to enter an end date later than the start date. In this example, the parameter you name "Start Date" must appear before the parameter you name "End Date. If you choose Low for one parameter, you must also choose High for another parameter in that structure and vice versa.

Otherwise you cannot commit your changes. Indicate whether to display this parameter in the Parameters window when a user submits a request to run the program from the Submit Requests window. Enter the field length in characters for this parameter. The user sees and fills in the field in the Parameters window of the Submit Requests window. You should ensure that the total of the value set maximum sizes not the display sizes for all of your parameters, plus the number of separators you need number of parameters minus one , does not add up to more than If your program values' concatenated length exceeds , you may experience truncation of your data in some forms.

Enter the display length in characters for the parameter value description. Your window may show fewer characters of your description than you specify here if there is not enough room determined by the sum of your longest prompt plus your display size for this parameter plus seven.

However, your window does not display more characters of the description than you specify here. A user sees the prompt instead of the parameter name in the Parameters window of the Submit Requests window.

The Parameter Description field concatenates all the parameter values for the concurrent program. Tip: We recommend that you set the Concatenated Description Size for each of your parameters so that the total Concatenated Description Size for your program is 80 or less, since most video screens are 80 characters wide.

For a parameter in an Oracle Reports program, the keyword or parameter appears here. The value is case insensitive. For other types of programs, you can skip this field. Note: Data groups are no longer supported. This section is provided for reference only.

Use this window to define data groups. All data groups automatically include an entry for Application Object Library. A concurrent manager running reports or programs under Oracle E-Business Suite refers to a data group to identify the ORACLE username it uses to access an application's tables in the database.

Transaction managers running synchronous programs can only run programs submitted from responsibilities assigned the same data group as the transaction manager. If you create custom data groups, you should create new transaction managers for the applications that use transaction managers. Consult your product documentation to determine if your application uses transaction managers.

During the installation or upgrading of Oracle E-Business Suite, a standard data group is defined, pairing each installed application with an ORACLE username note: a standard data group is defined for each set of books.

However, you may:. A data group is uniquely identified by its name. You cannot create a data group with a name already in use. Use this button to copy an existing data group, then add or delete application-ORACLE username pairs to create a new data group. Concurrent conflicts domains ensure that incompatible concurrent programs are not allowed to run simultaneously using related information. For example, a conflict domain could be a range of numbers.

Two concurrent programs could be incompatible if they used the same range of numbers, but compatible if they used different ranges of numbers. Concurrent managers use concurrent conflicts domains to determine which concurrent programs cannot run at the same time. When concurrent program A is defined as incompatible with concurrent program B, then A and B cannot run at the same time using the same concurrent conflict domain.

If, for example, the programs A and B are assigned to the concurrent conflicts domains Standard when they are submitted, then programs A and B will not run together at the same time.

Enter a unique Domain name. The name you enter here may be used as a value for a parameter in the Submit Requests window. Use this page to search for defined concurrent programs. The following are prerequisites to defining a concurrent program:.

Purge - for concurrent programs listed in the Oracle Applications Manager dashboard used for purging data. Parameters for the concurrent program are listed here. To add a parameter, click on the Create button. For information on incompatibility types, see Incompatible and Run Alone Programs.

If this program utilizes this feature, the MLS function determines which installed languages are needed for the request. It returns a list of table names and rows to be purged.

Concurrent programs that produce data for a portlet can call a function to refresh the portlet's data. The value for Refresh Portlet indicates when the function should be called. If this box is checked, multiple pending requests are allowed; otherwise, only one pending request is allowed. The NLS National Language Support box is checked if the program allows for a user to submit a request of this program that will reflect a language and territory that are different from the language and territory that the users are operating in.

The format that you select here is used by the concurrent manager to determine how to display your report output. You must ensure that the output format you choose matches the format generated by your report, unless the report is an Oracle Reports report in which case the format you select, determines the output generated. The default layout template for the program.

Values for this field are available only if the concurrent program has been registered as a data definition with XML Publisher and templates have been loaded to the Template Manager. At the time of request submission, the default template is presented to the user. The user can override this value when submitting the request. This field indicates how many days the system should retain data for a request of this concurrent program after the request completes.

The log level is used in diagnostics. If a request to run this concurrent program fails, the failure may be recorded in a log file with the specified log level. Enables the collection of timed statistics, such as CPU and elapsed times, by the SQL trace facility, as well as the collection of various statistics in the dynamic performance tables.

By default, a log file is created for each concurrent request. If such log files are not necessary for requests for this concurrent program, you can specify that the log file is automatically deleted for each request of this program. If no specification is made for the concurrent program, the request will be picked up by any manager able to run it.

Use this region to specify options for the database session of the concurrent program when it is executed. Optionally specify the resource consumer group for the concurrent program. For example, if you plan two parameters named "Start Date" and "End Date", you may want to force users to enter an end date later than the start date.

In this example, the parameter you name "Start Date" must appear before the parameter you name "End Date". The following types of "instance sets" can be used for assignment but administrators can create new instance sets based on their needs : All programs in a particular request security group All request sets in a particular request security group To enable this functionality, the following are seeded: Permission "Submit Request" Permission "View Request" Permission Set "Request Operations" containing the permissions "Submit Request" and "View Request" Object "Concurrent Programs" Object Instance Set "Programs that can be accessed" Object Instance Set "Request sets that can be accessed" To grant access to a request security group to a role, follow these steps: Define your role User Management responsibility.

Define your request security group System Administrator responsibility. Define your grant Functional Administrator responsibility. Enter a Name and Description optional for the grant. Enter the Security Context for the grant. Choose "Request Operations" as the permission set under "Set". Review the grant information and save your work. Seeded "instance sets" allow administrators to grant: All requests submitted by a user All requests submitted by a user for a given application All requests belonging to a program submitted by a user All requests belonging to a request set submitted by a user irrespective of the constituent programs' owning application to another user or a group of users - via a role.

Then the following approach, to grant specific programs' requests to a group of users, can be used: Create an instance set that selects all the requests belonging to the particular program irrespective of which user submitted it.

See the detail descriptions of the iStore concurrent programs. For a summary of the programs available, see: the section, "Overview of Oracle iStore Concurrent Programs", below.

Several concurrent jobs are seeded in the Oracle Applications Forms iStore concurrent program manager setup. These include:. Run this batch job after you have loaded Oracle Inventory items and set the Inventory organizations. This program populates Oracle iStore's category search table with product information from the Oracle Inventory tables. Typically, you should not run the iStore Search Insert concurrent program more than once. However, you may need to rerun this program under one of the following three conditions:.

To switch from category-level to section-level search, run only the iStore Section Search Refresh program. If you have enabled a section-level search, rerun this concurrent program whenever you change the setting of the fuzzy search functionality. If you need to duplicate a section having more than 1, child sections, use the iStore Duplicate Section concurrent program.

See the "Creating and Maintaining Sections" section in the chapter, Implementing the Catalog, for more information. To copy the layout mappings from a parent section to all of the children sections underneath it, use the iStore Section Layout Mapping Concurrent Program. See the "Creating and Maintaining Sections" section in the chapter, Implementing the Catalog , for more information.

Note: This concurrent program only works with sections using Configurable Layout. The concurrent managers process requests for this program at the priority you assign here. If you do not assign a priority, the user's profile option Concurrent:Priority sets the request's priority at submission time.

Request Type If you want to associate your program with a predefined request type, enter the name of the request type here. The request type can limit which concurrent managers can run your concurrent program. You can define a concurrent manager to run only certain types of concurrent requests.

See: Concurrent Request Types. If you check this box, you must register your program parameters, if any, in the Parameters window accessed from the button at the bottom of this window. Allow Disabled Values If you check the Use in SRS box, you can also check this box to allow a user to enter disabled or outdated values as parameter values. These value sets normally allow you to query disabled or outdated values but not enter them in new data.