How Do I Configure Jobs and Job Definitions to Meet My Needs?
Based on the analysis you did for your plan for scheduled processes, you might need custom jobs and job definitions to meet your organization’s requirements. Remember, you must test all custom jobs in your test environment before deploying to the production environment.
Here are some best practices to follow when you configure jobs and job definitions.
Follow Oracle Analytics Publisher Best Practices When Creating Custom Jobs
When you create a custom Oracle Analytics Publisher report as the basis for a custom job, make sure to follow best practices for creating reports so that the custom scheduled process doesn't take too long to run.
If you properly design and create the reports, you ensure maximum performance and scalability, and you minimize the performance impact on resources for scheduled processes.
Use Care When Duplicating Predefined Job Definitions
If you're duplicating a predefined job definition on the Manage Job Definitions tab, here are some best practices to consider:
- It's best if you have technical knowledge of Oracle Application Development Framework business components, and a basic understanding of what these are: view objects, view criteria, view accessors, bind variables, list of value definitions, return values from the list of values, and so on.
- Open every parameter and make sure that all the required parameters are populated properly.
- Make sure not to delete any predefined parameters that are copied over.
- Test the duplicate carefully because it might not work exactly like the original.
Avoid Deleting List of Values Sources
Lists of values sources are used for parameters in job definitions. The sources determine the values that users can choose from when setting parameters as part of submitting a scheduled process.
On, the Manage List of Values Sources tab of the Manage Enterprise Scheduler Job Definitions and Job Sets page, when you delete a list of values source, you won't be able to find it and manage it anymore. But, it's not really gone. Any job definitions using that source can continue using it.
So after you delete a source, you can't create another one later with the same name, because the deleted one is technically still there, even though you won't be able to find it. To avoid confusion, it's recommended that you don't ever delete any list of values source. Just create values source as needed, with unique names.
Use Appropriate Page Element for Parameters
On the Manage Job Definitions tab, when you define parameters for job definitions and select String as the data type, you can select a page element that gives users a list of options to choose from for the parameter.
- Select Choice list only if the list for the parameter will have 10 or fewer options, and test it out to make sure that would be the case. In fact, users would get an error if it turns out there are more than 500 options.
- Select List of values if there will be more than 10 options for the parameter. There's no limit to the number of possible options. But, if you know that there will be fewer than 10, use the choice list instead. The list of values includes a search, which doesn't make sense if there are only a few choices and they're already displayed.