Table of Contents

1.

Overview

2.

Why we need

3.

Architecture

4.

Features of Application Manager

5.

Job Scheduling

6.

Automic (UC4) Tool :a. How to connect to UC4 V-9 Tool

b. Creating a job using UC4 tool
c. Creating a workflow using UC4 tool

7.

Terminologies used

8.

Advantages

9.

Conclusion

Automic (UC4) Tool Overview

The primary focus of the document is to explain the basic features like job scheduling,
managed file transfer, and workload automation.
Efficient job scheduling is becoming one of the focus areas for all those companies which
are operating across geographies and have to run almost the same set of jobs in every
business unit. The task has become far more complex due to the use of multiple
computing platforms, several business processes and the 24 X 7 operating environment.
More and more corporations have started to look beyond the traditional batch job
scheduling.
There comes the Automic system, which is a global provider of intelligent service
automation solutions and the leading vendor on job scheduling. Its enterprise utility can
handle basic and complex scheduling and allows for automated, event-driven decisions
and/or responses.
The enterprise utility handles basic and complex scheduling and allows for automated,
event-driven decisions and/or responses.

Why to adopt UC4 solution?

Automic system offers several fundamental benefits in two important areas of Scheduling
and Automation. Some of these benefits are as follows:
Automic system handles complex scheduling, pre-validation & event-driven activities that
are not feasible in Oracle Concurrent Manager.
Automic streamlines & automates repetitive, labor-intensive & complex tasks making it
easier to handle.
It prevents errors caused by manual processes
UC4 provides quick visibility, immediate job or process documentation access and
advanced operations reporting to monitoring team from a single, centralized console

UC4 is capable of orchestrating tasks across multiple platforms, databases, applications &
computing environments at an enterprise level

It has a robust notification system capable of intelligently emailing, texting, &/or

paging resources when necessary

Through practice and experience, our key takeaway from working with UC4 was that
developers practices also affect how well the application supports our goals and how
well/efficient the solution may be maintained. The intent of this document is to present
developer best practices and standards that will maximize the return we get from the
system.

It enables connectivity to any application, databases, operating system and capable to support the
business. It integrate all business applications. Its feature such as forecasting, reporting, error
detection and correction, audit and Load balancing make it more powerful and reliable.
Architecture of this automation tool is object oriented which allows you to easily reuse
existing task and process. Build once and use many times across departments, teams and
individual use cases. It also has powerful set of object types such as Calendar which helps
to reuse existing keyword to fulfill complex scheduling requirement. It is capable to deliver
file transfers between your application, your external partners and suppliers.

UC4 have load balancing feature by which zero down time can be achieved. Not only
applications but day to day operation related task can be automated in the tool which helps
to reduce operational cost and human errors.

UC4 Architecture:

UC4 platform can be used to automate processes across all environments of your
information system. This is possible through the definition of multiple logical environments
from a single UC4 infrastructure, reducing the cost of installation and ownership of your
automation infrastructure.UC4 Automation engine communicates with the target machine
through TCP/IP.

Remote Agent: On each target machine, UC4 agent is establishes communication with
automation engine.
Operation Manager: This is the administrative console which monitors activities of all
scheduled batches as well as automation engine Health status.
Service Manager: Service manager console gives the communication status with each
agent by heart beating with remote agent through Communication processes.

Features of UC4 Application Manager

UC4 is a powerful application job scheduling tool that meets the needs of operators,
programmers, and system administrators throughout the life cycle of an application. UC4
allows operators to submit jobs on an ad-hoc basis, view the output online, and print the
output to a system printer or a local Windows printer. UC4 provides programmers the tools
to set up sophisticated job scheduling without writing scripts. Instead, users can create
logical conditional statements with a few mouse clicks. System administrators will find UC4
roles and security are powerful tools for managing access to UC4.

UC4 Job Scheduling is a service that enables the enterprise to schedule and monitor
computer batch jobs. The scheduler is able to initiate and manage jobs automatically by
processing prepared job control scripts and statements.

Applications that utilize the UC4 scheduling service benefit from a single point of control for
administration and automation of operator activities to ensure a more consistent and
reliable operations. This service offers better control for job processing across multiple ITS
managed applications and platform in a distributed environment.

The UC4 scheduling service enables ITS to control jobs across managed applications so they
run at the right time, in the proper order of execution (including parallel and sequential
processing) with monitoring services to ensure jobs terminate normally and provide problem
management with error reports for those that do not.

End users can be granted view access for their application environment in the UC4
scheduling system to monitor job status and progress.

UC4 Job Scheduling:

Objects are combined to define jobs. Jobs are combined with other objects to create process
flows that run batch processes. All of this is accomplished without the use of scripts.

There are various UC4 objects available to fulfill your Scheduling requirement.

Jobs: Jobs-are the basic building block in UC4. For each program that needs to run
(for example: FTP, database load), a job must be created. A job contains all the
information required to execute a program or script on the server and handle its
output. When a job is created, it will specify the program location, input and output
parameters. Jobs are run both individually and as components of UC4 process flows.
Furthermore, a job can be a component of any number of process flows. If a job
definition is changed, the change is applied to every process flow that includes it.

Job plans (process flows): Jobs are combined to create process flows. Process
flows are equivalent to job streams and run any number of jobs. Process flows
include scheduling and exception handling information. When jobs and process flows
are added to a process flow, these objects are referred to as process flow
components

Events: Jobs/job plans can be triggered based on time or existence of file. There are
two types of event object

File event: This is file watcher objects which senses for file and if true triggers the
actions.

Time event: This is used to trigger job/job plan multiple times a day.

Schedule: Schedule is Parent for all objects, the objects which are to be scheduled
needs to placed in schedule object where frequency of job/job plan can be added.
Schedule loads every midnight and loads the objects are to be triggered. Schedule
runs for 24 hours a day and gets auto reload at 00:00 midnight for next day
execution.

Calendar: This is featured object of UC4 in which we can create the statics as we as
dynamic calendar condition and use it to schedule objects. We can create Static,
group, weekly, monthly, Roll on key words in calendar object to fulfill scheduling
requirement.

To schedule the workflow to run on every Wednesday, create the weekly calendar keyword
in Calendar object.

How to connect to UC4 V-9 tool:

To connect to the UC4 tool we should have UC4 client installed on the machine.

Fill in the required details for connecting to the UC4 client.

Once connected to the UC4 client, the below screen appears.

Explorer Window:
It is the central window in the User Interface where objects can be edited, displayed,
managed and executed. The structure and handling of Explorer is basically identical to
Windows Explorer.

Activities Window:

Serves to inform about tasks that have either been activated manually or by a super
ordinate Job.

Message Window:
The Message Window displays all information and error messages of all the jobs.

Creating a job using UC4 tool:

1) On the Explorer Window click on New Object new

2) The popup box will appear as shown below. Highlight JOBS and expand it to select the
job type (i.e. UNIX, WIN, etc.)

3) Basic Required Tabs to be updated for creating a Job in UC4_V9 and navigate to each
tab for filling in the required details.

We will be discussing about the highlighted tabs briefly.

Header

Attribute
Window
Process

(a) The Header Tab:

Its important to briefly describe what the job is being used for and where the job runs
to be able to identify the purpose of the job

(b) THE ATTRIBUTES TAB:

Select Agent name from the host drop down menu

 Select the login object

Runtime Parameters should be identified if the job set to run as part of schedule
Enter the Time Zone if needed
Max number applies mostly for database backup.

(c) THE PROCESS TAB

The process tab is the actual script or the location of the script as to what the job
executes and also job parameters could be defined at the process tab.
(d) THE WINDOWS TAB:

The Windows tab is used to define the initial directory path where the script starts from.

(e) THE DOCUMENTATION TAB

Within the Documentation tab there are 2 additional tabs at the bottom.

The Restart and Recovery information should be defined here for our own use within the
team.
Version Management tab displays the stored object versions if this function has been
activated.
By filling these, job can be created and this job will be used in work flows. The work flow
is the constitution of many jobs.

Creating a workflow using UC4 tool:

A Workflow groups multiple UC4 jobs/objects for executing in a single flow .These
objects are linked to each other through defined conditions and dependencies.
1) Right click on new object on the explorer window.
2) Select JOBP and click on the side arrow then select standard.

Take a look at the window below. Within the workflow tab you will have a Start and End
box.

3) Jobs/Objects can be added within the workflow (which has been created as per 3.3:
Creating a job using UC4 tool) by drag and drop the objects to the workflow or using add
task function on workflow tool bar.

Object Task Properties:

Right click on the job and select Task properties (as shown below) for updating the
details for the execution of workflow

Once it is selected, the below tabs will appear which needs to be updated as per our
requirements.

General tab- To set time checkpoint

Earliest tab- To specify the earliest time
Preconditions tab Conditions that are checked before a task is executed.
Dependencies tab- To define dependencies to other tasks and the latest starting point
Variables & Prompts tab- To modify object or Prompt Set variables.
Calendar tab- To specify Calendar conditions.
Runtime tab- To monitor the minimum and /or maximum runtime.
Post Conditions tab- Conditions that are checked after a task has ended. Here the alert
mail has been configured to be triggered during any task failure to the concerned person
or team.
Solution tab- To overwrite the specific attributes of the RA Jobs (only available in RA
Jobs)
External Dependency tab- To define dependencies to external tasks.
After filling all these details, workflow will be created. These workflows are very much useful
in automation of FTP, Backups, SFTP and so on.

Terminologies
Process flows
Process flows are used to schedule and execute one or more jobs and other process flows.
The Applications Manager process flow is similar to a script that runs multiple jobs. The
user can create schedules for a process flow as a whole and also the eligibility settings can
be specified for each component belonging to it.
A whole process like period end closing can be automated.
Job
A job gets triggered as a single request or program in Applications Manager. To create a
job, the user has to specify a library, application, program type, program, queue, login
and output device. The program or script it runs is at the heart of the job.
For end users, this is the concurrent program which they need to launch in Oracle.
Subvar
The Substitution variables (Subvar) are used to store values which can be used in jobs
and process flows. The values may be stored in a database table or can be generated by
a SQL statement at the same time when a task is submitted.
For example one very frequently used parameter is the inventory organization id.
This parameter is used on several reports. So, the inventory org value can be
stored in a
subvar and then the variable can be dynamically provided to the program at the time of
execution. Some other logical subvars could be

Operating unit id
Email delivery list
Responsibility name
Output file path

Prompt
You can create prompts for process flows to define values that will be used by the
components added to the process flows. You can pass prompts from a process flow to
one or more components in the process flow using numeric substitution variables. The
values can be used in prompts, conditions and aliases. The user can enter values in one
place and have them automatically used in one, several or all of the components in a
process flow. You can also specify prompt values within the process flows at the
individual job level.

While users may see nicely displayed parameters, what is actually sent to the program
could likely be something quite different. Automic is capable of passing the parameter
string directly to the job. The parameter string can be extracted from an actual job and
the same can be used to schedule jobs. There is no need to enter parameters one by one.
It also leverages on the various subvars defined earlier.
User
Access to Applications Manager is controlled with user logins. The Automic (UC4) user
name is the name the user will enter on the Applications Manager Login window. The
entry can be 30 characters long. The user name should be the same name as that used
in the Oracle Applications.
For simplicity and tracking of the request logs and runs, all the requests are scheduled
through a generic user created to identify the UC4 user.
Queue
Any task which is submitted to the system from the Applications Manager has to pass
through an Applications Manager queue. A queue is nothing but a pipeline which can be
used to regulate the flow of tasks to the server. By defining the appropriate set of
queues, you can set a limit on the number of concurrent tasks that can be processed at
any one time for different periods during the day.
This functionality is similar to the concurrent request queues defined in Oracle.
Conditions
Conditions govern the execution of modules, chains or chain components. Conditions can
be assessed before, during, and after a job gets executed, or after a job gets deleted.
One can add, update or delete conditions for the specific running of a job from the
backlog. By adding conditions to chain components, the user can use a module
differently in numerous chains or even the same chain.
Conditions control the execution of jobs and process flows. They can apply to jobs,
process flows or process flow components. When a condition is met, Automic (UC4) takes
action as defined by the condition.
Conditions cannot be named by the developer. They are made available by Automic
(UC4) in their software.
Automic (UC4) recommends NOT using the wait until met condition because it is too
resource intensive. Instead use a condition to delay 5 minutes and then try again.
Calendar
A Calendar is used to schedule the jobs and process flows whether it is to run or not to
run. A calendar identifies a list of dates such as off days or holidays, month end
processing dates and fiscal quarter end processing dates. Sometimes there are days
when information is handled in special ways. In Automic (UC4), you can specify days by
creating calendars. You can schedule jobs and process flows to run or not run on the
days specified by a calendar.
Some of the calendars for this user are as follows:

Fiscal Year End

First Monday of fiscal period
First Saturday of fiscal period
Second Saturday of fiscal period
Fiscal period end calendar first day
Exception rule for first Saturday of fiscal year

Message Template
Automic generally uses message templates to specify text contents to include in
notification output files. Message templates permit the use of substitution variables and
replacement values for variable text.
For example a substitution variable can be defined to store text for each of conditions like

LAUNCH_ERROR
ORACLE_ABORT

(used for the Application objects)

(used for Oracle jobs)

These substitution variables can be used by message templates to generate message in

case any of the underlying condition is met.

Request set
A Request set for UC4 is not treated as a normal request set as in the case of Oracle. UC4
treats each request set as a bunch of multiple individual requests or separate jobs. Each
request is scheduled as an independent request. So unlike standard Oracle, requests from a
request set can be scheduled through multiple responsibilities and multiple users. But the
dependency conditions such as if Request-A gets completed successfully then Request-B
gets triggered, etc. can be set outside of Oracle so that for a user the requests get
completed similar to a request set in Oracle

Agent: An Agent enables the execution of Jobs, Console and File System events,
thereby allowing the processing of various operation steps in a target system. An Agent
is where UC4 submits the jobs to be executed (i.e. the host).

Job: Used to define processing steps in a target system. It can be used independently,
in a Group, or within a Workflow.

Work Flow: Groups multiple UC4 objects to execute for defined conditions and
dependencies.

Schedule: A Schedule is used for defined time/date start of UC4 objects on repeated
bases.

Advantages of UC4

Improves current data processes, such as automating processes that are currently
manual. Improves job handling across disparate systems, especially those that have
specific input/output dependencies, sequence, etc.

Provides the ability to check and validate jobs and notify on failures.

Extends services by providing the ability to securely move data from one system to
another that cant easily be completed today

Provides reporting capability.

Provides monitoring of jobs.

Provides ability to schedule multiple jobs with flexibility and complexity.

Allows for more informed and calculated decisions of maintenance schedules and
impact analysis on scheduled jobs.

Ability to create and better manage business rules across disparate systems.

Conclusion:
It is now common for global enterprises to possess thousands of application and application
servers rely on extensively globalized networks and store more data than ever before.
Therefore, it is more important than ever to have single enterprise-wide automation solution

that will help you efficiently manage this complex IT landscape-a solution that delivers what
uc4 refer to ONE Automation.

The UC4 Automation Platform responds to this need, providing single intelligent automation
solution that automates both processing and decision making across hybrid computing
environments-Physical, virtual and cloud. UC4 delivers event based as well as time based
automation and it supports this most operating systems, databases, applications and
services of any automation solution available today. By eliminating silos and removing
manual steps that slow execution time, decrease productivity and introduce human error,
the UC4 Automation Platform will enhance your efficiency, accuracy and agility and will
lower your operational costs. And it will enable you to deliver the promised services on time,
every time.