axway automation through xos -...

w w w . a x w a y . c o m

Axway Integration Platform

Axway Automation through XOS

An Axway Paper 22 August, 2005

1 Axway Automation through XOS

Batch process management and integration: what is it? .......................................................... 2

Real-time and Batch processing 2

Automation Painpoints: Heterogeneity, Events, and Efficiency 2

IT production: Take over the controls ..................................................................................... 4

Axway Batch Process Automation 4

The issues 5

The solution 5

Automate, Control, Supervise 6

Production automation functions ........................................................................................... 7

Work with an IT production line 7

An “open” Architecture 7

Advanced scheduling functions 10

Global Batch Process Management (ERP, Transfers, Exchanges, Integration, ...) 11

Working with the XOS scheduler 13

IT production Supervision with Axway Automation 14

Inform and Alert 18

Standards and platforms .................................................................................................... 19


BATCH PROCESS MANAGEMENT AND INTEGRATION: WHAT IS IT?

Real-time and Batch processing

Much of what it means to be a real-time, or even a near real-time enterprise revolves around the word timing. No matter how complex the infrastructure, no matter how many systems, applications, users, sites, are involved – events must happen when they are supposed to happen; data must arrive when it should arrive; triggers must launch jobs when those jobs will use resources most efficiently, or their results are most necessary.

Between –

the rapid, speed-oriented, real-time, event-driven applications in the enterprise, on the one hand, and

on the other hand, the back office processes that operate in the background of those applications, updating data stores, aligning data for consistency, and carrying out the steps in multi-step processes

lies the scheduler: the essential link, the gateway (if you will) that provides facilities for co-existence of all the technologies on both sides. The scheduler provides the technology that acts as the backbone for cross-platform / cross-OS operations, including all requirements for end-to-end processing: constraints on triggering, checks on the environment, and the possibility of exiting the cycle in case of exception or error.

The technology behind this automation helps “tone up” the entire Information System, improving reactivity, robustness, reliability and scalability.

Automation Painpoints: Heterogeneity, Events, and Efficiency

MMuullttiippllee aapppplliiccaattiioonnss

In spite of (or perhaps in part, because of) the wide adoption of increasingly well defined standards in the computing industry, heterogeneity is increasing in both platforms and applications. Dependencies between applications are increasingly complex. One way of reducing that complexity and making it more manageable involves using a single scheduling program to control the operational relationships between those applications. This approach depends on the simple, almost inescapable fact that most mission-critical applications are linked through batch processing.

EEvveenntt--ddrriivveenn

However, over the years, as batch processing – and the applications that it connects – have matured together, the nature of batch processing operations has changed. Time-based scheduling (the classic “launch all batch processing at one minute after midnight”) no longer provides the flexibility needed to manage the modern technologies developed for Application Servers. This complexity and the flexibility needed to manage it are only available by basing processing on logical events.


Event-based processing can link across a variety of operating system platforms and applications in a way that time-based processing cannot. Exception handling, for example, cannot be either hard-coded or managed manually.

EEffffiicciieennccyy –– ddooiinngg mmoorree wwiitthh lleessss

Automation not only means solving the standard, expected problems, but the exceptional problems as well – as and when they occur. By making it possible for the system to achieve the potential that it already has, automation can itself provide the reaction to certain events.

In a constantly changing economic environment, every business needs to increase its capacity to react quickly. Environmental changes often disrupt both business itself, but also the associated business processing. A simple and efficient batch process automation solution can help reduce costs and at the same time minimize organizational changes in enterprise IT services.


IT PRODUCTION: TAKE OVER THE CONTROLS

Axway Batch Process Automation

The Axway batch process automation and integration solution provides all the functionalities required for complete application integration. A comprehensive automation solution with a high-level graphical interface enhances the ability to mange a heterogeneous IT environment, by providing cross-platform, cross-application control.

Axway provides a solution that is easy to use, intuitive, and built to reduce complexity through its robust capabilities, a solution that minimizes the downtime of information availability.

AA rreessppoonnssee eeqquuaall ttoo tthhee pprroobblleemm

Whether the process is ERP (SAP, JD Edwards, PeopleSoft...), or another Axway solution (XFB, XRDJ...), or any other application, jobs are modelled and represented the same way in Axway‘s batch process Automation solution.

Single batch process template Applications, and dependencies between applications, and the integration between those applications – all these are viewed and modelled logically, without reference to the physical production servers. No matter what type of machine, OS, or application, Axway Automation it in the same way.

Single view of processing Only one way of visualizing the sequence of the treatments – whatever:

the links between chains


the number of servers involved

the type of network

It is only at the time of implementing the chart in production that the various parameters and definition of jobs are distributed onto the servers.

In the same way, the operations result is seen in a global way independent of the platforms.

Single rule-creation procedure The solution imposes a single way to create scheduling rules, whatever:

the complexity of the rules

the application, the software, or the process chain to be automated

Creation of scheduling rules is based on standard calendars, defined only once no matter what level of complexity. Each rule can then be applied to an unlimited number of jobs.

The issues

It is vital for a company to be able to ensure high availability of its IT production. High availability favors:

improved response times

faster detection of errors or incidents

faster and more complete data recovery in the event of loss

reduced production costs

But to state a goal is not necessarily to achieve it. The difficulty here is controlling an IT infrastructure that refuses to stay still:

constantly growing number of heterogeneous systems

distributed administration

new technologies (SAN network, Cluster, etc.)

The complexity of production, and hence, of control over production is always increasing. The result is that it takes longer to define, execute, and track processes. The result is that omissions and errors become more likely. The result is higher training and monitoring costs. The result is that change management becomes ever more costly and time-consuming.

The solution

Axway Automation automates and monitors the IT production chain, providing global supervision that allows genuine, end-to-end management.

Axway Automation is built around two components:

XOS (Axway Open Schedule), the heart of the solution, acts as the scheduler

Axway Sentinel provides global monitoring

Axway Automation is a comprehensive automation solution that helps you live with the heterogeneity of your IT environment. For example, it reduces administration and training costs, the identical solution runs on all platforms.

User-friendly, scalable and easy to implement, readily adapted to new IT infrastructures, the solution schedules and plans batch processing and optimizes the resources in the corporate information system. It is designed to improve and maintain a high level of IT service quality.


Automate, Control, Supervise

Axway Automation automates according to one or more charts, the launch of batch processes on the various machines from various applications, which could be legacy applications or standard ERP (SAP, JD Edwards, PeopleSoft...)

With Axway Automation, you can:

Reduce planning, scheduling and work monitoring costs

Increase the security of production tasks

Plan and automate repetitive tasks

Reduce operators' workload

Optimize system workload

Control all multi-platform system tasks (Unix, Windows NT, GCOS7/8, UNISYS 2200, VMS, AS/400) from a focal point

Axway Automation adds to the scheduling functions, the insurance of a successful operations completion by a full control of the scheduler and a system component monitoring.

With the tasks and system components control, you can:

Ensure that the scheduler is still running correctly

Supervise in real time the operations (with the statistics and events sent from the scheduler)

Detect the inactivity of network components and processes

Design scenarios to react automatically to the various events

Alert the adequate people though email, GSM, voice synthesis... according to on call support provisional planning.

Then, Axway Automation provides high-level supervision of the various stages of operations, including:

Graphical tracker with each significant stage of the IT production

Customizable, geographical views of the infrastructure

Message and event lists by application or server

Automatic procedure triggering on receipt of specific messages


PRODUCTION AUTOMATION FUNCTIONS

Work with an IT production line

OObbjjeeccttiivveess

To launch and trigger batch processing chains on various production servers using advanced scheduling rules or event receptions.

AAddvvaanncceedd aauuttoommaattiioonn ffuunnccttiioonnss

Directly apply operations diagrams (or graphs, or charts) in the scheduler through a user-friendly graphical modeling interface. The charts are defined simply and dynamically.

Schedule periodic tasks (or jobs) or prepare “on request” jobs that are by definition non foreseeable.

Planning is taken into account in real time, ensuring the tasks execution right on time.

Before any job execution, XOS evaluates and synchronizes the constraints related to this job, including the constraints between production servers, tasks, etc.

To validate scheduling rules before starting a chart in production, you can simulate the rules.

At any time you are able to display with a Java graphical interface or an Internet explorer (Thin Web client) a summary view of the progress of the operations (job ready, in error, de-scheduled...).

Print dashboards and report on the operations status.

It is also possible at any time to apply and launch a new or an older version of a chart. All charts can be archived.

An “open” Architecture

AA rroobbuusstt AArrcchhiitteeccttuurree,, ooppeenneedd ttoo hheetteerrooggeenneeoouuss eennvviirroonnmmeennttss

XOS is based on an architecture that guarantees users optimum security and performance levels, and fits any type of organization.


Centralized or Distributed

Cooperative

XOS architecture ensures complete autonomy for the production servers. Modeling and tracking is done on an independent modeling server.

The Modeling Server is used principally to create the production model (charts, parameters, resources, scheduling rules, ...), though it is also used for tracking operations. It provides full chart version management (Archives), distributing the chart and all required corresponding objects to the different machines where jobs must be launched (the Production Servers, described next).

The Production Server executes the process chains, taking account of all defined dependencies. It is completely autonomous (unless the chain runs over several production servers).

The Java Graphical Interface is always the same for all operating systems. It allows connections to the modeling server or directly to the production server, if necessary.

The Web interface tracks operations from any workstation through an Internet/intranet browser (no download necessary).

Production servers

4- Control and supervision

Production sites

Modeling server

GUI

1- reationChart c

Deployment on 2


AAuuttoommaattiioonn aapppplliieedd ttoo vvaarriioouuss pprroodduuccttiioonn oorrggaanniizzaattiioonnss

Create and modify charts in a single reference location to centralize modeling operations and production. Then distribute them to any site or server: The production instances are then applied to the different servers which become completely autonomous.

Decentralized operations with the same chart on every production site: XOS solves this case through the concept of the production group. When creating a production instance, you can specify the production group where instance will be distributed. Then this instance is automatically installed on all the production servers of that group.

Decentralized management of the operations with a different chart for each production site: In this case, several modeling servers have to be installed. With the Import/Export functions, one main site by area can manage several departments. Those sites can redefine their own charts, based on charts imported from a central site.

SSiimmppllee eennvviirroonnmmeenntt mmaannaaggeemmeenntt

For fast environment changes (from test to integration or production,...), the modeling can be entirely defined with parameters

The scheduling rules, the users, the production servers, the paths (for scripts or data base),and so on, are not fixed names. Instead, they are parameters. The real values of those parameters are defined only when creating the production instance.

DDyynnaammiicc aaddjjuussttmmeenntt ttoo ooppeerraattiioonnaall ccoonntteexxtt

XOS provides a number of techniques for adjusting to the context where it is operating, including:

Variable execution parameters

Commands can be applied to any XOS process or job


Interactive Questionnaires: Operators reply to questions on customizable cards. Jobs starts only when replies are valid. Replies can be considered as job execution parameters.

Global (managed by the modeling server) or Local (managed by the production server or the chart) Resources are used to exchange information between jobs (or between charts or servers) or to allow the start of a job (depending on its value or status).

Advanced scheduling functions

SSiimmppllee sscchheedduulliinngg rruulleess aanndd mmuullttiippllee ccaalleennddaarrss

To schedule jobs, XOS uses simple scheduling rules based on calendars, where business and non-business days can be defined.

Creation of a calendar is fast and simple, with the graphical user interface.

Then Scheduling rules allows the definition of days where jobs will be launched.

The number of calendars and rules is not limited. To define various execution dates, it is possible to define several calendars which will contain different worked days and the non working days. In the same charts, jobs can be linked to different calendar.

International, by default, XOS integrates the public holidays of many countries.

CCoommpplleexx sscchheedduulliinngg rruulleess

If the graphical definition of rules is not sufficient, XOS proposes the use of key words close to the natural language for complex scheduling rules.

CCyycclliicc jjoobbss ((CCRROONNTTAABB ttyyppee))

For the cyclic job execution (for example all X minutes) and to support the integration of Unix scripts previously based on the Unix command CRON, XOS can start jobs according to "CRON" syntax.

FFoorreeccaasstt ppllaannnniinngg

To manage exceptions or unforeseen events, the forecast planning allows you to work in the future. For instance it is possible to forced the status of a job for tomorrow or a day next week (de-scheduled, pause, ...). It is also possible to modify the calendar parameters for the chart for a particular job.


Global Batch Process Management (ERP, Transfers, Exchanges, Integration, ...)

MMaannaaggiinngg SSAAPP bbaattcchh jjoobbss

In addition to the identical functionalities of the "SAP" scheduler (creation, scheduling, tracking of SAP jobs), XOS supplies powerful features in its own right, such as powerful scheduling rules.

SAP jobs are completely integrated in the XOS standard chains with all other tasks. An SAP job has the same functions as a normal job while preserving its SAP-specific characteristics.

For a perfect synchronization, the validity of SAP jobs is checked by the XOS server before being launched on the SAP machine

It is possible to reach directly a "step" inside an SAP job and to schedule ABAP and external programs in a chart.

To automate data import in SAP with the "batch input".

Access to the SAP JOBLOG, directly from the tracker XOS.

MMaannaaggiinngg JJDD EEddwwaarrddss aanndd PPeeoopplleeSSoofftt iinntteeggrraatteedd jjoobbss

XOS replaces the principal JDE or PeopleSoft planning functions, it then becomes possible to act on the execution of "reports", exactly as for a normal XOS job.

For JD Edwards: the UBE/Reports

For all types of PeopleSoft jobs: application and optimization engine, COBOL SQL, Crystal, cube builder, SQR,...

The job submission is done specifying on which system UBE/Report must run or by letting JD Edwards choose the "enterprise server".

XOS supervises in real time the execution of the reports.

Directly from the tracker XOS, you can apply actions such as Pause, Release, stop, etc. are possible to XOS, JD Edwards or PeopleSoft, as well as access the ERP job log.


FFiillee TTrraannssffeerrss –– XXFFBB ((AAxxwwaayy FFiillee BBrrookkeerr)) --mmaannaaggeemmeenntt

File transfers are directly integrated to the other operations in XOS. They are seen in the GUI exactly like other jobs.

Tracking in real time of the transfer state. Actions are possible on the transfer (stop, restart, pause...)

The steps, before or after transfer are seen as XOS jobs.

XOS allows transfers to have the same functions than any other job (Dependencies, resources, parameters, etc.)

Only one graphical access for all the operations (backups, transfers, computing, ...).


Working with the XOS scheduler

Step 1: Chart creation Define the jobs and links.

Step 2: Archive the chart This checks the chart, and creates a version of it that is ready to be executed. Several versions of the same chart could be created.

Step 3: Create an Instance Create an instance from an archive. The chart is automatically dispatched to the production servers defined in the job definition.

Step 4: Execution On the production server, the chart is ready for execution at the scheduled date and time.


CChhaarrtt vveerrssiioonn mmaannaaggeemmeenntt

Operations keep changing, every day, every month, there is something new. Chart should be able to manage these changes. It should be easy to create a new version of a chart, and it should be also easy to come back to a previous version.

From one archive, several instances can be created with different parameters. This allows operations to adapt dynamically to the infrastructure changes.

To return to a previous version, you just need to “de-archive” a chart, modify it and “re-archive “ it.

TThhee cchhaarrtt,, aa rreepprreesseennttaattiioonn ooff tthhee IITT pprroodduuccttiioonn lliinnee

A chart is a group of jobs, processes and applications. An application is a second level of a chart, it is also a group of jobs or processes.

Applications allows to group the batch jobs by business processes.

Applications and jobs can be linked together and can be launch in parallel and/or the ones after the others (depending on the definition of the links).

Various types of links exist (mandatory, conditional, error...) to schedule the applications and the jobs. It possible for example that jobs with different scheduling rules or different conditions are dependent from each other. This allows you to define alternate paths or to define dependencies with other systems.

These links could be associated with operators AND or OR.

XOS allows external links such as sending alerts or messages, interfacing with a backup, etc.

IT production Supervision with Axway Automation

Axway provides real-time tracking of all IT operations, either from the XOS operations tracker or from Sentinel dashboards.

You can go even further and use Sentinel historical data to build comparative or correlations dashboards. Just as you can set up a BAM (Business Monitoring


Application) while repatriating business information in Sentinel. This amalgam of technical and business data, related to precise management rules, provides the sensitive indicators that let you react in real or near real time.

EEnndd--ttoo--eenndd mmaannaaggeemmeenntt

An automated management of the processes and events

Technical and business data

Process instances (history & audit trail)

Process and business (monitoring events).

FFlleexxiibbllee aanndd ccoonnffiigguurraabbllee

Two databases, one for current events, one for historical data

A request manager.

An indicator builder (Event correlation, threshold definition and exceptions)

Graphical dashboards and lists.

A complete alert management.

OOppeennnneessss

Availability of all necessary interfaces to access to external data or BI (Business Intelligence) tools.

XXOOSS –– AA rreeaall--ttiimmee aanndd ddeettaaiilleedd ooppeerraattiioonnss ttrraacckkeerr

From the chart, XOS lets you monitor jobs and the status of applications in real time.

Activity tracking is presented in graphical mode. Depending on the status, the icons have different colors.

It is possible to display:

♦ job status (active, waiting, executing, in error...) ♦ job dependencies ♦ the reason for delays (time, period, resources...) ♦ preceding jobs, with their status

It is possible to interactively do an action on a chart or a job:

♦ Hold a job ♦ Force the execution of a job ♦ Delete a job from the schedule ♦ Stop a running job ♦ Re-launch a job


♦ Force the status of a job (completed, in error,...)

SSeennttiinneell –– AA gglloobbaall pprroodduuccttiioonn ssuuppeerrvviissiioonn

To provide a summary overview of production, and to display received messages in real time, Axway Automation provides supervision through Sentinel.

With Sentinel, users model with graphical objects, only the relevant elements of the production.

Those dashboards can offer several levels of views and sub-views, making it possible to bring a zoom on certain stages of the production chain.

AA ppoowweerrffuull ggrraapphhiiccaall ddeessiiggnneerr

Each graphical object is positioned on a map or an image (bitmap).

From the graphical object libraries, the user can use gauges, graphs, meters, LEDs, etc, or create objects as desired.


FFiilltteerr aanndd ddiissppllaayy iimmppoorrttaanntt mmeessssaaggeess

To reduce “flooding” from repetitive alerts in message lists, Sentinel provides filters and dashboards that make sure you only view relevant information.

Depending on the severity of the message, the user be required to acknowledge it. An automatic process can also be started at the reception of the message.


Inform and Alert

CCoonnttaacctt tthhee rriigghhtt ppeerrssoonn aatt tthhee rriigghhtt ttiimmee

Individual definition of on-call support people, with specific calendars and media.

Alerts can be sent in cascade mode or in general broadcast mode.

On-call forecast planning: by system and application, for each group of user, time periods are defined. When a message is sent, Sentinel Alert checks the person or the people that have to be contacted and their corresponding media (phone, Pager...).

NNoottiiffyy uussiinngg aannyy mmeeddiiuumm

Sentinel Alert is a vocal server able to send messages to: telephone (mobile or fixed, text or vocal)

message (Internet, Exchange, Notes, ...)

pop-up window

GSM

pager

Speakers

Pop Up GSM / WAP


STANDARDS AND PLATFORMS

Operating Systems Windows NT/200x, XP, NetWare

AIX, HP-UX, Solaris, Tru 64, Linux ...

OS/400, VMS

Bull GCOS7 & 8, VME, Unisys

ERP SAP

JD Edwards

PeopleSoft

Other applications XFB (Axway File Broker)

XRDJ

XMS (Axway Messaging System)


Copyright © Axway Software, 2005 All rights reserved. No part of this publication may be reproduced, transmitted, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of the copyright owner, Axway Software. This document, provided for informational purposes only, may be subject to significant modification. The descriptions and information in this document may not necessarily accurately represent or reflect the current or planned functionalities of this product. Axway Software may change this publication, the product described herein, or both. These changes will be incorporated in new versions of this document. Axway Software does not warrant that this document is error free.

AXWAY SOFTWARE RECOGNIZES THE RIGHTS OF THE HOLDERS OF ALL TRADEMARKS USED IN ITS PUBLICATIONS.

axway automation through xos -...

Documents