Define Your Workload › Define an Application

Define an Application

To set up the scheduling scenario in this tutorial, you will first define an Application. When you have defined this Application, you will schedule an Event to run the Application at 4 p.m. daily. Then, you will define the six jobs in the Application.

An Application consists of one or more jobs. A job can be an executable file, a task representing a manual process, or a database query. Two examples of executable files are command files and UNIX scripts.

Usually, jobs in an Application are related. For example, all of your payroll jobs may be in one Application. An Application may contain jobs that run on the same platform or it may have jobs that run on different platforms.

To define a new Application

1. Open the Define perspective.
2. Right-click your server connection in the Application Workspace view, and select New from the pop-up menu.

   The Basic page of the Application properties dialog opens.

3. Enter a name for your Application in the Name field. For this tutorial, enter quick_name where name is your first name.

   Usually, you will choose a name to reflect the line of business, such as Payroll, Inventory, Housekeeping, or Order_Processing.

   There are few limitations on Application names. For security reasons, your server administrator can restrict the Application names you can use.

   • The name is not case-sensitive; the name automatically enters in uppercase letters.
   • Do not use special characters (such as punctuation marks, brackets, and spaces). To enter a name with more than one word, you can use an underscore to separate the words.
   • You can choose a name with up to 128 characters.

   Note: Fields marked with an asterisk (*) are mandatory.

4. Select the Wait for previous generation check box.

   Each time an Application runs, the server creates a unique instance named a generation and assigns the next sequential generation number for that Application. In many cases, you may want one generation to complete before the next one begins. For example, you may not want to process Tuesday’s payroll until Monday’s payroll is complete.

   In this tutorial, each time your Application is scheduled, it must wait for all previous generations of the Application to complete before it starts processing.

5. Verify that the Agent option button is selected in the Default agent section.
6. Select the agent that will run all jobs in the Application in the Agent drop-down list.

   For this tutorial, if you are using the default agent installed with the server, select AGENT. If your server administrator specified another name for the default agent, select that name instead.

   If you are using an agent other than the default, select that agent name.

7. Click OK.

   The Application appears in the workspace.

More information:

Setting Application and Job Properties