Automator 3.6.x GettingStarted allOS en PDF

GETTING STARTED
Axway Automator
Version 3.6
11 March 2013
Copyright Axway Software, 2013
All rights reserved.
This documentation describes the following Axway software: Axway Automator 3.6
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 S.A.
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 functions of this product. Axway Software
S.A. may change this publication, the product described herein, or both. These changes will be incorporated in new versions of this
document. Axway Software S.A. does not warrant that this document is error free.
Axway Software S.A. recognizes the rights of the holders of all trademarks used in its publications.
The documentation may provide hyperlinks to third-party web sites or access to third-party content. Links and access to these sites are
provided for your convenience only. Axway Software S.A. does not control, endorse or guarantee content found in such sites. Axway
Software S.A. is not responsible for any content, associated links, resources or services associated with a third-party site.
Axway Software S.A. shall not be liable for any loss or damage of any sort associated with your use of third-party content.
Contents
1 Introduction ............................................................................................................................................................ 4
2 Presentation ........................................................................................................................................................... 5
Axway Automator ...................................................................................................................................... 5
About Automator ....................................................................................................................................... 5
Features ................................................................................................................................................... 6
3 Architecture ............................................................................................................................................................ 7
External architecture .................................................................................................................................. 7
Internal software architecture ..................................................................................................................... 8
Modeling server module .......................................................................................................................... 8
Production server module ........................................................................................................................ 9
GUI module (Workstation) ....................................................................................................................... 9
Domain server module ............................................................................................................................ 9
Network protocol compatibility .................................................................................................................. 10
4 Database management ........................................................................................................................................ 11
MySQL 11
Configuration ....................................................................................................................................... 11
Connection parameters ......................................................................................................................... 11
Changing the connection of the MS to the database................................................................................. 12
Oracle 12
Prerequisites ........................................................................................................................................ 12
Configuration ....................................................................................................................................... 12
Changing the connection database ......................................................................................................... 14
Recommendation .................................................................................................................................. 15
MS SQL................................................................................................................................................... 15
Prerequisites ........................................................................................................................................ 15
ODBC configuration for the Modeling Server connection ........................................................................... 15
Configuration ....................................................................................................................................... 17
Changing the connection of the MS to the database................................................................................. 17
XDBM & Automator ............................................................................................................................... 18
API Usage ............................................................................................................................................... 18
Cleaning the database........................................................................................................................... 19
5 Local security settings ........................................................................................................................................ 20
Required Rights ....................................................................................................................................... 20
Users who launch Automator ................................................................................................................. 20
Submit users ........................................................................................................................................ 20
Submitting job with UAC activated............................................................................................................. 21
opspserver started in interactive mode ................................................................................................. 21
opspserver started in service mode ...................................................................................................... 22
6 User interface ....................................................................................................................................................... 23
User Identification ................................................................................................................................... 23
Axway Automator Getting Started 2

Workstation main window ........................................................................................................................ 23
Main steps .............................................................................................................................................. 25
Defining the basic building blocks .............................................................................................................. 25
Specifying calendars (Scheduling rules) .................................................................................................. 27
Focus on: Modeling ............................................................................................................................... 27
Focus on: Tracking ............................................................................................................................... 27
7 In practice ............................................................................................................................................................. 28
Modeling ................................................................................................................................................. 28
Planning and plotting ............................................................................................................................... 28
Creating a chart....................................................................................................................................... 28
Step 1- Creating the chart ..................................................................................................................... 28
Step 2 - Creating an archive of the chart ................................................................................................ 29
Step 3 - Creating an instance from an archive ......................................................................................... 29
Step 4 - Putting the chart into production ............................................................................................... 29
Applications executable as Jobs ................................................................................................................ 30
Production Tracking ................................................................................................................................. 30
Forward Planning ..................................................................................................................................... 31
8 User interface icons............................................................................................................................................. 33
Using icons ............................................................................................................................................. 33

1 Introduction
What do you want to do?
This guide helps you get started with Axway Automator.
This document is intended for people who set up or use Axway Automator.
What do you learn about?

In this guide, we assume that you have a good understanding of Axway Automator.

2 Presentation
This chapter introduces you to Automator.
Axway Automator
Axway Automator offers an event driven process scheduling solution providing centralized administration for
distributed systems.
Axway Automator Batch process automation and Integration solution provides every functionality required for
optimum process management:
Process planning, organization, activation and monitoring
Automatic workstation monitoring and handling system and applications messages.
Activity monitoring through simple supervision views and reports
Tasks are executed according to a multi-facetted calendar, dependencies and inter-job/system exclusivity rules.
With Automator, you can plan and automate repetitive tasks, ensuring their correct and timely execution.
About Automator
Automator is software that lets you:
Schematically diagram the applications in your information system.
Specify the order, timing and nature of (batch) jobs for execution anywhere in the information system.
These jobs can work with the applications, on input or on output or on both
Track the execution of those jobs
In practical terms, that means that Axway Automator is a production automation system that is used to:
Implement production based on graphic modeling features; processing diagrams are defined dynamically
Schedule periodic or ad-hoc processing, that is processing that cannot be scheduled in advance
Synchronize all constraints (environment, applications, jobs, etc.); Automator processes the actions and
schedule to be implemented in real time
Prepare processing automatically
Centralize administration using a driver to provide an overall view of how operations are progressing
(ready, failed, rescheduled processing, etc.)
Provide a simulation feature to test production scheduling rules
Generate operation-based control panels and control statuses

Presentation
Features
Automator has a number of features designed to provide you with the advantages described above:
Guaranteed portability in multi-platform environments (UNIX, NT, AS/400, VMS GCOS7, GCOS8,
UNISYS 2200)
Suitable for all types of organization (centralized or distributed)
Completely autonomous production servers, requiring optimum security and minimum consumption of
network resources
Graphical user interface providing work planning and scheduling capabilities, making it easier to
monitor and control your production folder design
Provides solutions to all your complex planning and scheduling problems
Guarantees the reliability of your production environment by automating tasks, including fault
management and restart procedures
Optimizes your resources via a specialized scheduling engine designed around an event-based design
philosophy to optimize production planning and interactive simulation
Simplifies upgrade operations (visual object programming, inheritance mechanism)
No limit to the number of systems and jobs managed by Automator
A Chart archiving system allows you to change the versions of your Charts, if required
Forward planning controls scheduled operations and allows you to intervene on planned tasks
(reschedule, activate, and so on)
A simulation mode checks your work sequencing
Automator has a thin user interface that allows you to log in from a Web browser to monitor and act
on your production environment from anywhere
Automator contains a module that can generate your production documents automatically
Interfaces with the major ERPs: SAP R/3, JD Edwards One World, People Soft, Pericles
Special AS/400 features: Spool management, job interception

3 Architecture
This chapter describes the Automator architecture.
External architecture
Automator is suitable for all types of configurations. Individual sites can develop and define their own jobs and
scheduling. But a major advantage of Automator is that it supports distributed operation.
Implement in specific domains
Production Server
Production Site
Export Charts (Region 2)
to Production Sites
Modeling Server
(Centralized Chart creation)
Export Charts
to Production Sites Production Site
(Region 2)
Production Server
Figure 1: Decentralized Architecture

Architecture
The drawing above shows decentralized operation distributed over multiple sites, with each
site supporting multiple departments. Each site can create its own Charts and export them
directly to the other sites. The drawing below schematically illustrates the decentralized,
distributed architecture possible with Automator. This drawing shows two regions, but in
principle, there are no particular limitations on the number of regions that can be input with
Charts exported from a central definition point.
Test Environment
Export Charts
Export Charts
Modeling Server
(Chart creation)
Pre-Production Environment
Export Charts
Production Environment
Figure 2: Multiple Environments
Internal software architecture

The Automator product is divided into the modules described in this section.
Modeling server module

Use the Automator server to configure all scheduling rules (calendars, resources, etc.) for the jobs to be
scheduled. It also enables a link to be established between the GUIs and the production servers to track
processing.
The server is used to develop all Charts, applications and jobs, on which production is based. The Charts
created are put into production via the server when requested by the users of the tracker module GUI.
The server continues to listen to the production servers to synchronize their databases when they start up.

Architecture
Production server module

The production server is a small-scale, standalone server. It controls all constraints required for jobs to be run
on the system (scheduling rules, calendars, formulae, resources, etc.), and executes and tracks the jobs:
Start-execute mode production server: A conventional, standalone production server managing the
Chart, and starting, executing and tracking jobs
Start mode production server: A conventional, standalone production server managing the Chart; to
execute jobs, it sends a request to the relevant execute mode production server
Execute mode agent: A passive agent executing and tracking jobs exclusively; scheduling is performed
by the start mode production server
The production server has its own database, which is updated at the server's request when a Chart goes live.
The production server automatically updates the database from the server on each startup to take into account
any new Charts that went live while it was not running.
Charts
Multi-system Chart: Jobs defined in this Chart can be executed on different systems; for this Chart, the
production server may be a:
o Main agent: A production server is considered to be the main agent (it is the focal point guaranteeing
resource synchronization); the selection of the main server is automatic and transparent
o Secondary agent: Here, the production server is independent and only starts the elements that
require a series of jobs to be run on its system
Standalone Chart: All jobs defined in this Chart are to be executed on the same system; the production
server is then independent for this Chart; a standalone Chart may be assigned to a production group,
enabling it to be broadcast to a set of systems
Resources
Global resources are common to all product Charts; they are managed directly by the server; however, global
production server resources are managed by the main Chart server; refer to the explanations provided in the
Axway Automator Configuration manual.
Local resources are local to the Chart; they are managed by the main Chart production server
GUI module (Workstation)

This workstation is reserved for configuring the various objects and tracking production activities in real time.
Note: The Questionnaire module is a product option. Access to Questionnaires requires a specific key. This
module is used to define questionnaires for the configuration of scripts and database files for jobs
scheduled in Automator.
Domain server module

The domain server is a front-end server written in Java. It is used to connect to different ERP's on the market,
including JD Edwards, SAP, PeopleSoft, and Pericles. It also provides connection to other Axway products, in
particular, Axway Transfer CFT. This module can in some cases create jobs, submit them, and monitor them. It
relieves the production server from the need to supply these activities. The domain server is completely self-
contained and includes a database of jobs to launch and monitor.

Architecture
Network protocol compatibility

From version 3.6.0, all product servers are able to listen through IPv4 and IPv6 protocols.
Configuration example:
IPV4 PServer1
MServer IPV4
PServer2
IPV6
If the communication mode selected is the dual mode, the communication is opened on IPv6 by default with
this combined mode.
If an error occurs on one network, the product does not continue in degraded mode but the server does not
start and an error message is generated.
For a server, you can force restricted communications on IPv4 only: set the preference variable
TO_COM_MODE_IPV6=0 in the OPSchedule.ini configuration file.
For a server, you can force restricted communications on IPv6 only: set the preference variable
TO_COM_MODE_IPV6=1 in the OPSchedule.ini configuration file.

4 Database management
This chapter describes the supported database management.The database support for Automator has been
changed. The previous database, CodeBase, is no longer available. Automator supports MySQL, Oracle or MS
SQL databases.
MySQL
For information on installing MySQL, refer to the Axway Installation and Prerequisites Guide.
Configuration
The database must use the MySQL innoDB engine and the parameter transaction-isolation must be set to
READ-COMMITTED.
It is highly recommended that you use the Axway Database because the MySQL properties are automatically
configured. You can use an external MySQL database (version 5.0.68 or higher), but you must create the
database schema and user manually.
To create database and users of Automator you must use root user of MySql:
Generate and launch scripts
Generate scripts only
o Customer must create the tables and insert default manually, using the generated scripts
o The scripts to use can be found in <Automator>/MServer/database/mysql/scripts/
Only one modeling server can be connected to the same database at the same time, like it was with Codebase.
In order to keep product integrity, it is strongly recommended that you do not manually update the tables in
the database.
The modeling server can be installed on a different machine than the one with a database management system,
unlike the previous version using Codebase.
Connection parameters
The database connection parameters are in the OPSchedule.ini file in the config directory of the modeling
server. The default values are:
TO_DATABASE_NAME=AxwayAutomator_MS
TO_DATABASE_HOST=localhost
TO_DATABASE_PORT=3306
TO_DATABASE_USER=AutomatorMS
TO_DATABASE_USER_PWD= AutomatorMS (crypted with AES128 decoding)
TO_INSTALLER_CRYPT=AES128
The connection password is encrypted for security purposes. The property named TO_INSTALLER_CRYPT
specifies the type of decoding. Possible values for this property are: AES128, AES256, or DES.
To deactivate encoding, the property TO_INSTALLER_CRYPT must be set to 0 (TO_INSTALLER_CRYPT=0).
When you type the password it appears on the screen and is not hidden.

Database management
Changing the connection of the MS to the database

When you change the Automator database user password, you need to change it in MySQL.
Change the password in MySQL from the MySQL administrator GUI with the database administrator user (root
default password is axway).
Axway XDBM & Automator

XDBM (AXway DataBase Manager) is a tool for initializing and modifying Axway databases. It is located in the
<AXWAY_HOME>/Tools/XDBM directory.
You have to run the Axway configure mode for Automator Modeling Server. First, you need to stop the
Modeling Server:
Select Start > Programs > Axway Software > Axway_Installer (LogicalName) > Configure.
Configure mode changes password both in XDBM and Automator OPSchedule.ini file.
If there are differences between the password in the MySQL environment and in the OPSchedule.ini file, the
Modeling server fails to start.
If the password in the Axway environment is not the same as in MySQL, the patches that fix the Automator
tables cannot be applied.
Oracle
For information on installing an Oracle database, refer to the Axway Installation and Prerequisites Guide.
Prerequisites
On Windows 2008 R2 64-bit and on Windows 7 64-bit the Oracle client library version level must be at least
10.2.0.5.
Configuration
The Database Administrator has to create an instance/port/schema/users/password before the
execution of the installation.
Choice between automatic or manual execution of sql scripts that create the tables of the database and insert
master datas.
The scripts can be found in
$AUTOMATOR_INSTALL_DIR/Automator/MServer/database/oracle/scripts.

Database management
They can be started (if you select Generate scripts only during the installation) at the end of the installation
using XDBM tools.
The Modeling Server can be installed on a different machine than the one with a database management
system, but an Oracle client must be installed on the same machine. The tnsnames.ora file must be correctly
configured to resolve the SID of the database.
The local connection name is the connect descriptor or net service name in the tnsnames.ora on the
machine where the Modeling Server is installed.
Caution: The TO_DATABASE_NAME matches the connection service name and not the SID (files
OPSchedule.ini and tnsnames.ora):
[tnsnames.ora]
Dynamic link library:

On Windows environments:
During the first Windows installation, there can be a problem when starting opsmserver where
MSVCR71.dll is not always found. This is due to a Windows version that is installed without Windows
framework.
Whatever the database configuration is, it is recommended that you set the NLS_LANG variable in the
environment so that the modeling server can correctly handle accented characters.
Example
For a database with the following parameters:
NLS_LANGUAGE=FRENCH
NLS_TERRITORY=France
NLS_ISO_CURRENCY=France
NLS_CHARACTERSET=WE8MSWIN1252
You must set the NLS_LANG variable to FRENCH_France.WE8MSWIN1252.
On UNIX environments, the Oracle dynamic client library libclntsh.so.10.1. must be present
(<ORACLE_HOME>/lib/libclntsh.so.10.1 or <ORACLE_HOME>/lib32/libclntsh.so.10.1,
depending on the version).

Database management
You must then set the environment variables in the set_env.sh shell provided in the mserver/scripts/default of
the modeling server:
ORACLE_HOME to add the link to the Oracle dynamic library.
NLS_LANG set (depending on the of the database setup) so that the modeling server can correctly process
accented characters.
Once set, copy the set_env.sh shell into the mserver/scripts directory so that it is taken into account
the next time the modeling server starts (check that it has execution rights).
###############################################################
# For Oracle database character set #
###############################################################
#NLS_LANG=FRENCH_FRANCE.WE8ISO8859P15; export NLS_LANG

#ORACLE_HOME=/oracle/product/10.2.0.4
# Fix the Oracle lib 32 or 64 bits

if [ ! -z "${ORACLE_HOME}" ]
then
ORACLE_NLS10=${ORACLE_HOME}/nls/data
OS_TYPE=`/bin/uname`
if [ "${OS_TYPE}" = "SunOS" ]
then

Uncomment the #NLS_LANG=FRENCH_FRANCE.WE8ISO8859P15; export NLS_LANG line and indicate the
correct value (Example: SPANISH_SPAIN.WE8ISO8859P15).
The database connection parameters are registered in the OPSchedule.ini file in the config directory of
the Modeling Server. The default values are:
TO_DATABASE_NAME=AxwayAutomator_MS
TO_DATABASE_USER_PWD= AutomatorMS (crypted with AES128 decoding)
TO_INSTALLER_CRYPT=AES128
The connection password is encrypted for security purposes. The property named TO_INSTALLER_CRYPT
specifies the type of decoding. Possible values for this property are: AES128, AES256, or DES.
To deactivate encoding, the property TO_INSTALLER_CRYPT must be set to 0 (TO_INSTALLER_CRYPT=0).
Changing the connection database

When you change the Automator database user password, you need to change it in Oracle.
Change the users password in the Oracle environment using sqlplus or a GUI client
XDBM & Automator
Change the password in the Automator OPSchedule.ini file and XDBM environment using the Axway
Installer in configure mode:
From command line:
setupWIN32.exe Configure
setupUNIX.sh Configure
From the GUI:
Select Start > Programs > Axway Software > Axway_Installer
(LogicalName) > Configure.
Configure mode changes the password in both the XDBM and Automator
OPSchedule.ini files.

Database management
Recommendation
When the database is stopped, the modeling server tries to re-establish the connection. In the case of a
MS/Oracle configuration, we recommend however to restart the modeling server after a database shutdown.
MS SQL
Prerequisites
For the MS SQL database the supported version must be at least 2008 R2 64 bits.
It is recommended that you create a case-sensitive server collation
Example French_CS_AS (CS (Case Sensitive) AS (Accent Sensitive)).
ODBC configuration for the Modeling Server connection

On the modeling server machine you must create an ODBC data source (Open Database Connectivity) for your
mssql database via the odbc administrator in the Windows system panel.
1. Open the OBDC Data Source Administrator window and the System DSN tab.
2. Click Add.
3. Select an SQL Server driver.

4. Enter the name used for DSN and then choose the SQL Server to which you want to
connect.
5. If the SQL Server is not located on the same machine, enter the domain name or IP
Address and click Next.

Database management
6. Enter your Login ID and Password to connect to the SQL Server and click Next.
Warning: For the login user, the default database is suggested. Remember to change the database
name to use.

Database management
7. Enter Client Configuration

The client Configuration enables you to configure the server, client network protocols and connectivity
options:
o Server Alias Server alias used for the computer to which the client is connecting.
o Protocol Network protocol used for the configuration entry (TCP/IP).
o Connection Parameters Parameters associated with the connection address for the network protocol
configuration.
8. Click Finish.
Configuration
You must use the administration user of MS SQL to create Automator database and users via:
Generating and launching scripts.
Generating scripts only:
o Customers must create the tables and insert default values manually, using the generated scripts.
o The scripts are available in the directory
<Automator>/MServer/database/sqlserver/scripts/
Restriction: Only one modeling server can be connected to the same database at the one time, as it was for
Codebase.
To protect product integrity, it is strongly recommended that you do not update the tables manually in the
database.
The modeling server can be installed on a different machine than the one with a database management system,
provided that this is a Windows platform.
The database connection parameters are located in the OPSchedule.ini file in the config
directory of the modeling server. Default values are:
OPSchedule]
TO_INSTALL_DIR=C:\Axway\ 4.4_MSSQL\Automator\MServer
TO_SERVER_HOST=ITEM-55289
TO_SERVER_PORT=50500
TO_SERVER_MSG_LANG=_en
TO_DATABASE_HOST=svmwinautdb1.dhcp.ancy.fr.sopra
TO_DATABASE_USER_PWD=AutomatorMS
TO_DATABASE_NAME=AutomatorMS
TO_DATABASE_PORT=1433
TO_INSTALLER_CRYPT=0
KEY_VALUE=9PGH6KQKBWJXJN9LQI6FM1Q1SSQ9S4H65Y9P6FAGW0S9
The connection password is encrypted for security purposes. The TO_INSTALLER_CRYPT property specifies
the type of decoding. Possible values for this property are: AES128, AES256, or DES.
To deactivate encoding, the TO_INSTALLER_CRYPT property must be set to 0 (TO_INSTALLER_CRYPT=0).
Changing the connection of the MS to the database

When you change the Automator database user password, you must change it in MS SQL via the Microsoft SQL
Server Management Studio with the database administrator user (sa).

Database management
XDBM & Automator

XDBM (AXway DataBase Manager) is a tool for initializing and modifying Axway databases. It is located in the
<AXWAY _HOME>/Tools/XDBM directory.
Before you run the Axway configure mode for Automator Modeling Server, you must stop the Modeling Server
then select Start > Programs > Axway Software > Installer (LogicalName) > Configure.
The configure mode changes passwords both in XDBM and Automator OPSchedule.ini files.
If there are differences between the password in the MS SQL environment and in the OPSchedule.ini file,
the Modeling server fails to start.
If the password in the Axway environment is not the same as in MS SQL, the patches that fix the Automator
tables cannot be applied.
API Usage
Use the API dbtools to verify database integrity.
Example:
D:\automator\bin>dbtools check -h item-29620
Axway Automator Connexion database:
Database name <axwayautomator>
Database port <3306>
Server name <item-29620>
User name <automator>
No error found in the database

Database management
Cleaning the database

The dbtools clean API must be used with caution.
Use the command dbtools clean to delete data from all tables, except the default ones. After performing
this command, the data is irretrievable. You receive a message to confirm the deletion.
Example:
D:\automator\bin>dbtools check -h item-29620
Axway Automator Connexion database:
Database name <axwayautomator>
Database port <3306>
Server name <item-29620>
User name <automator>
Delete the database (y/n)? Y

5 Local security settings
This chapter describes the prerequisite user permissions (Automator side).
WARNING: Windows prerequisites regarding the secondary logon service.
The settings recommended in this chapter are valid for whichever version of Windows you have if the service is
started with the LocalSystem account.
If the service is started with another account, see if the Windows Secondary Logon service is enabled.
Secondary Logon Service (Run As):
This service enables starting processes under alternative credentials. It is enabled by default by Microsoft but
can be disabled by an Adminstrator to minimize security risks.
The Automator production servers require it. It must not be disabled and
must remain in manual start mode for whichever version of Windows you have.
The first submission processing via Automator will start the service on the machine.
Required Rights
Users who launch Automator
Right name Description
SE_INCREASE_QUOTA_NAME Increase quotas
/ SeIncreaseQuotaPrivilege (XP only)
SE_ASSIGNPRIMARYTOKEN_NAME Replace a process level token
/ SeAssignPrimaryTokenPrivilege (XP only)
SE_SERVICE_LOGON_NAME Log on as a service
/ SeServiceLogonRight (Only for service mode)
The user must be an administrator or the LocalSystem account.
Submit users
Right name Description
SE_INTERACTIVE_LOGON_NAME/SeInteractiveLogonRight Log on locally
(Only for XP & 2003)
SE_BATCH_LOGON_NAME /SeBatchLogonRight Log on as a batch job
2008, 2008 R2, Seven
SE_IMPERSONATE_NAME/SeImpersonatePrivilege Impersonate a client after authentication
Required when UAC is set on 2008, 2008 R2 and Seven.

Local security settings
Submitting job with UAC activated

Automator production server is designed to work with any UAC level.
On Windows 7 the UAC level is set by default to the third level:
opspserver started in interactive mode
Using an administrator user

The UAC Windows splash screen: blue shield icon with an ? and editor Axway Inc is mentioned as Certified
editor with a two year validity certificate from Thawte Code Signing CA G2.
Just click on Yes and the program is launched (privilege elevation not needed). A window is opened on the
desktop at when each job starts.

Local security settings
Using a standard user

The UAC windows asks for an elevation of privilege: blue shield icon with an ? and editor Axway Inc is
mentioned as Certified editor with a two year validity certificate from Thawte Code Signing CA G2 .
You have to set the fields of user/ password with an admin user/password.
opspserver started in service mode

Connected as an administrator user, start the service of the production server. By default, the process
opspserver is executed with SYSTEM user and the service is configured with the Interact with the desktop
option set.
You can also change the execution properties of the service and force it to be executed with another
administration user and then set or not set the Interact with the desktop option.
Forcing the service to run with a standard user is unsupported. Submitting a job may not work.
It is important to note that:
When the Production Server is executed in service mode, jobs that are submitted using the
user __default__ may cause unexpected behavior
After some changes in Local Security Parameters, a reboot is required
For 2008, 2008 R2 and Seven you must start the installer using the option Run as Administrator in the
Start menu

6 User interface
This chapter describes the user interface.
User Identification
The Authentication window displays the Server Parameters.
Complete the fields as show in the table below.

Field Description
User Login user, declared within the product.
Password Enter the password.
Server Host Name Modeling server name
TCP Port Automator server login port.
Workstation main window

The main screens in Automator have the following layout:
Menu bar
Icon bar
Left pane Right pane - Diagram area O I
b c
j o
e n
c s
t

User interface
From the icon bar, you can access the menus:
Menu Content
Configuration menu Configuration consists of setting the parameters for various objects
(servers, calendars, users, and so on).
Modeling menu Modeling consists of defining and designing charts.
Questionnaire menu Questionnaires allow you to define automatic modification rules, which
are used to process script files or JCLs and update external files used
during execution by the jobs.
Processing Menu Processing consists of managing and tracking chart processing in real
time.
The right pane is the working area used to create, modify or view Automator object definitions.
The left pane of the window lists the different types of Automator objects.
Double-click an object type to open the list of associated objects. Double-click an object to edit it, so that it can
be queried or modified.
For example, the left pane can display the list of Charts. Double-click a Chart to open the list of all its archives
and the Chart graph in the right pane.
Click the button to toggle between displaying and hiding the left pane.
Use the Help function to access the About panel and display general information on the product.

User interface
Main steps
Automator usage involves the following workflow:
Field Description
Configuration Use Configuration to define the elements that are included in your information system
(servers, users, user groups, etc.), and the elements involved in scheduling jobs in that
information system (calendars, scheduling rules, etc.).
Modeling Use the modeling function to create Charts, which are schematic diagrams of jobs and
their scheduling in your information system. Charts illustrate the relationship between
jobs and applications.
Tracking Once a Chart has been defined, and an instance of it created and posted to a
production server, it can be used to direct the scheduling of jobs. The tracking function
of Automator monitors the execution of the Chart designed in the modeling phase.
Note: A fourth possibility exists as a subset of Modeling. The optional Questionnaire function is used to
define automatic modification rules, which are used to process script and JCLs, as well as to update
external files used during execution by the jobs. The Questionnaire function is not described in this
manual.
Defining the basic building blocks

Use Configuration to define the elements included in your information system, and the elements involved in
scheduling jobs in that information system.
The available types of objects are as follows:
Type of object Meaning
Modeling Server Use the Automator modeling server to configure all scheduling rules
(calendars, resources, etc.) for the jobs to be scheduled. It also enables a link
to be established between the GUIs and the production servers to track
processing.
Production Servers The production server is a small-scale, standalone server. It controls all
constraints required for jobs to be run on the system (scheduling rules,
calendars, formulae, resources, etc.), and executes and tracks those jobs.

User interface
Type of object Meaning

Users Automator works with three types of users:
Submit users who can submit jobs
Login users who can login to the GUI
AS/400 users who can be intercepted (name, *ALL)
User profile This object is designed to define rights on the Automator object types.
User group User groups let you group users with the same User Profile, simplifying their
access rights management. A user group is defined by its name, description
and one or more profiles from which will result a main profile.
Context Contexts are used to group and to secure some Automator objects inside the
global scheduling environment.
Contexts are created to group objects with some common characteristics.
Giving users access to the context only allows the definition of a security policy
to restrict access. For example, a user can be allowed to delete any calendar
object. But, calendars that do not belong to the users context will be grayed
out in the GUI.
Calendars Calendars define the workdays and holidays. You can define an unlimited
number of calendars, which can be renewed for subsequent years.
Macros A macro is a stored and named formula. A formula is used to describe complex
scheduling cases and is written in a natural language comprising of keywords
and arithmetic operators.
Scheduling Rules You can define rules associated with the calendar to apply restrictions when
scheduling the jobs to be executed.
Date Variables Date variables can be passed to jobs as parameters.
Global Resources Used in Charts, Resources enable you to:
Determine how applications or jobs are started up
Pass values to the applications or jobs as parameters
The set of Global resources are common to all charts, and are grouped as
follows:
Numerics
Texts
Weights
FIFO lists
A similar set of parallel resources can be applied locally to a single Chart: the
Local Resources.
Chart Views Chart views are full or partial logical groups of all charts, so that users can only
work on relevant graphs.
Execution group The execution group concept is used to dissociate the various execution
instances in the same chart.
For example, a user associates all chart or application objects with two
execution groups (Morning and Evening). The groups were defined when chart
execution was requested (instance creation). You can define two actions:
Execute the chart instance with the Morning execution group
according to a scheduling rule (everyday) and with a start time of
H1 = 9:00 a.m.
Execute the same chart with the Evening execution group
according to the same scheduling rule, but with a start time of
H2 = 8:00 p.m.
Consequently, these actions are used to start all or part of the same chart on
the same day, but with two different execution groups.
Example: a user defines a chart with an execution group object (MONTHLY),
which is different from the other group objects (DAY).

User interface
Specifying calendars (Scheduling rules)

You can create multiple calendars, each with different workdays and holidays. These days can be carried
forward automatically from one year to the next (Perpetual calendar).
Calendar-based scheduling rules are associated with Charts, with Applications and with all jobs. They are
entered graphically or, for complex scheduling, via keywords (text).
Focus on: Modeling

Once the various elements and building blocks have been designed and their parameters assigned, the next
step involves assembling those elements to describe the processing in your information system.
Modeling is used to create Charts and define all elements associated with them (resources and parameters).
Modeling includes four steps:
Definition
Graph
Parameters
Resources
Focus on: Tracking

This option consists of processing Charts and tracking them in real time. In addition, it is used to define action
objects containing the entire configuration for several instances.
Processing includes two steps:
Add Instance to create a new Chart instance or action
Processing Table to view the instance statuses for each day

7 In practice
This chapter provides a practical overview of how to use Automator.
Modeling
All the scheduling features can be used for:
Applications
Processing
The applications and processing operations can be interconnected by scheduling links and run concurrently
and/or sequentially.
Different types of links (mandatory, conditional, failed, etc.) can be used to schedule the applications and
processing, allowing you to associate processing operations of different recurrences or conditions, specify
degraded paths in the event of an incident, associate jobs on one system with those on another system, etc.
These links can be associated using the AND and OR operators.
Planning and plotting

The fundamental working space for the software is an object referred to as a Chart. The Chart is an open
graphic area where you can plot, graph, position, and define the sequence of jobs and detail the links between
them.
Each Chart can represent different layers or levels of abstraction from the technical behavior of the processes.
Each Chart can also represent another Chart. From one Chart, you can drill-down to the definition of the
elements and information that make up that Chart.
Creating a chart
The definition of a Chart involves four major steps:
1. Create the Chart.
2. Designate the reference version of that Chart (the Archive).
3. Create an Instance of the reference version.
4. Put the Instance into production (execution).
Step 1- Creating the chart

The following diagram schematically illustrates a chart showing three interdependent jobs. In an overview like
this, this simple description is sufficient, but keep in mind that much of the documentation for Automator
revolves around the creation and elaboration of these Charts.

In practice
Step 2 - Creating an archive of the chart

Though selected (and maintained) for historical reasons, the word archive does not have its standard
significance of a version that is no longer current.
Instead, the description should use the words reference version of the Chart. You cannot run or execute a
Chart directly; you can only run an instance of a Chart. You can create as many instances as desired, but the
instances are all created with reference to a single archive version of the Chart.
Thus, this step involves creating a Chart Archive and storing that Archive for duplication in the form of
instances, as illustrated.
Step 3 - Creating an instance from an archive

The next logical step involves duplicating the Archived Chart in the form of an Instance.
Multiple instances with different parameters can be produced from the same archive. These instances can be
executed in a completely independent way on the production servers. To rollback to a previous version of a
graph, you just have to de-archive this version.
Step 4 - Putting the chart into production

These instances can be executed in a completely independent way on the production servers. In the illustrated
case above, three instances were created one each for Development, Testing, and Production environments.

In practice
Applications executable as Jobs

License verification: the ERP job should be an authorized connector for the Modeling Server.
Field Description
File Transfer Automation Automator can directly launch and track Transfer file transfers from a
Connectors: Transfer job stream. Via the Axway Transfer object, you can define the
characteristic of the transfer and insert the defined transfer object into
the operation at any point, linking it to other tasks and processes.
ERP Connectors: SAP SAP job management is fully integrated in Automator. SAP jobs are
considered exactly like other jobs and include the same features. It is
possible to create links between SAP jobs and non-SAP jobs in the
same Chart or application. An SAP job is completely integrated in the
operations with other tasks and processes. The same scheduling
rules could be applied while preserving its SAP specific
characteristics.
Steps, ABAPs and Variants are part of the configuration in
Automator. All SAP jobs are verified by the server, ABAP and variants
have to be valid to be launched on the SAP System.
ERP Connectors: JD Edwards A JDE job is completely integrated in the operations with other tasks
One World and processes. The same scheduling rules could be applied while
preserving its JDE specific characteristics.
All interfacing to (and execution of) JD Edwards logic is performed by
calling standard JD Edwards interoperability APIs. This coupled with
a proprietary interface between JD Edwards and Automator provides
seamless integration.
ERP Connectors: PeopleSoft Automator enables scheduling, job tracking, and getting statuses on a
PeopleSoft system.
A PeopleSoft process is completely integrated in the operations with
other tasks and jobs. The same scheduling rules could be applied
while preserving its PeopleSoft specific characteristics.
ERP Connectors: Pericles Automator provides the same functionalities for job scheduling and
tracking using Pericles.
Web Services Connectors During the Automator job configuration, the WDSL file is retrieved.
Each job is able to query a single operation of a Web Service.
This version of the Web Service job supports the security
management by certificate or authentication in the header of the soap
message.
The Domain Server is used to communicate with the Web Service to
submit tasks.
ERP Connectors: Movex Automator provides the same functionalities for job scheduling and
tracking.
Process Manager Connectors: Automator can directly send/receive events to/from Axway Process
Axway Process Manager (XPM) Manager via the Axway Process Manager Event Objects. You can
define the characteristics of the event and insert the defined event
object into the operation at any point, linking it to other tasks and
processes.
Production Tracking
Automator allows you to track the processing status in real time and view your remote systems from the focal
system (or supervisor), which refreshes the displayed data automatically.
Activity tracking is presented graphically and the interdependencies are also indicated together with the
following information for each process:
Its status (executing, ready, terminated, failed, etc.)
The reasons why it is pending (time not reached, resources, etc.)
The previous processes and their status

In practice
The monitoring screen allows you to perform the following actions locally or remotely on the jobs that are
scheduled:
Suspend a processing operation
Force a processing operation, including or ignoring the previous processes
Force job execution, including or ignoring its dependencies
Delete a processing operation from the schedule
Cancel a job in progress
Restart a processing operation
Force a normal or abnormal end of processing status
Forward Planning
Automator forward planning allows you to organize your production processing in advance (for example,
reschedule, defer or force your schedules).
You can access your schedules from the production table showing all the Charts that are terminated, executing
or ready.

In practice

8 User interface icons
This chapter describes the user interface icons.
Using icons
Most of your use of Automator will involve locating, viewing, and clicking graphic elements on your desktop.
Automator provides a visually rich environment, but that richness can sometimes become confusing. To help,
this section illustrates the most important icons in Automator, with brief explanations of their meaning.
Access Configuration Access Modeling Access Processing Access Questionnaires
Processing Tracker
Processing Tracker Snapshot View properties
Revert from forecast

Default view mode Schedule planning
Statistics Deschedule Instance
/
Start paused Restart tracking Add / delete instance
Tracker ready Ready Request object
/ /
Play mode / Play pause Ready, paused Hold / release object
mode
Stop tracking Replay Stop object
Save modifications
Stop scheduling Scheduling ok (forecast planning)
/ /
Show history / Show Resource available / Not New
resource history available

User interface icons
Configuration
/ / /
Production server / Disabled Select day / month / deselect Modeling server
Domain server Connection object
Calendar Synchronize configuration Date variable
Macros Hierarchical view Scheduling rule
/
Charts / Chart views Execution group Context
/
Initiate new object Add / delete redirection for
AS400
Icons in Common
/. / /
Help Zoom / Zoom out / Zoom in Resize window / Resize
explorer
Close current window Refresh display Create new objects
Print Delete object Save object
Cut object Copy object Paste object
Edit object XCopy object Find
Information about properties Set preferences

User objects
Calendar Colors User
Workday Involuntary non-workday User profile
Non-workday (holiday) Involuntary workday User group
Partial workday Uncategorized day

XChart objects Operation objects Applications
XChart object Abort object Application object
Enter in an XChart Test object Exit from an application
Exit from an XChart AND object Enter in an application
Notification
Archive Icons
OR object Objects
Archive a Chart INIT object Wait for a notification
Unarchive a Chart (action) END object Automator notification
Archive Add Comment object OPMonitor notification
Working archive version Add Command object Sentinel Message
Questionnaire
Reference archive version Expression object icons
Working and reference Questionnaire

Link object
archive version
Spool Icons Wait object Data file for questionnaire
Spool object Environment variable Reply card for questionnaire
Delete spool Job data file Update reply card
Add spool Assignment object Response form for reply card

Resource Icons Numeric operators Job Icons
/
Global resource Equal to / Different from Standard job object
/ /
Global / Local numerical Greater than / Greater than or
Add Standard job object
resource equal to
/ /
/
Less than / Less than or AS400 / Intercepted AS400
Global / Local text resource
equal to job
/
/
Global / Local weight Axway Transfer job
Multiply / Divide
resource
/ /
Global / Local FIFO resource Add / Subtract JD Edwards job
/
Click to test resources Absent Pericles / Intercepted Pericles
job
Parameter Icons Set range

/
SAP / Intercepted SAP job
/
Generic parameter Push / Pop WebService job
Scheduling rule parameter Present in

Spool icons
/
Host parameter Maximum / Upper limit Designates target in spool list
/ /
Regular Expression Adds / deletes target user in
In / Not in value set
parameter spool list
Test parameter
/ /
Free / Clear / Allocate
Work on Charts
/
Reinitialize Reorganize Chart top to
User parameter
bottom / left to right
Numeric parameter Set graphic quality Add grid-lines
Path parameter Designates Action or Instance Date variable

Domain server parameter
Designates Action or Instance

Connection object parameter

Automator 3.6.x GettingStarted allOS en PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Automator 3.6.x GettingStarted allOS en PDF

Hochgeladen von

Copyright:

Verfügbare Formate

GETTING STARTED

Axway Automator Getting Started 2

Axway Automator Getting Started 3

What do you learn about?

Axway Automator Getting Started 4

Axway Automator Getting Started 5

Axway Automator Getting Started 6

Implement in specific domains

Implement in specific domains

Figure 1: Decentralized Architecture

Axway Automator Getting Started 7

Implement in specific domains

Figure 2: Multiple Environments

Internal software architecture

Modeling server module

Axway Automator Getting Started 8

Production server module

GUI module (Workstation)

Domain server module

Axway Automator Getting Started 9

Network protocol compatibility

Axway Automator Getting Started 10

Axway Automator Getting Started 11

Changing the connection of the MS to the database

Axway XDBM & Automator

Axway Automator Getting Started 12

Dynamic link library:

Axway Automator Getting Started 13

#NLS_LANG=FRENCH_FRANCE.WE8ISO8859P15; export NLS_LANG

# Fix the Oracle lib 32 or 64 bits

Changing the connection database

Axway Automator Getting Started 14

ODBC configuration for the Modeling Server connection

3. Select an SQL Server driver.

Axway Automator Getting Started 15

Axway Automator Getting Started 16

7. Enter Client Configuration

Changing the connection of the MS to the database

Axway Automator Getting Started 17

XDBM & Automator

Axway Automator Getting Started 18

Cleaning the database

Axway Automator Getting Started 19

Axway Automator Getting Started 20

Submitting job with UAC activated

opspserver started in interactive mode

Using an administrator user

Axway Automator Getting Started 21

Using a standard user

opspserver started in service mode

Axway Automator Getting Started 22

Complete the fields as show in the table below.

Workstation main window

Axway Automator Getting Started 23

From the icon bar, you can access the menus:

Axway Automator Getting Started 24

Defining the basic building blocks

Axway Automator Getting Started 25

Type of object Meaning

Axway Automator Getting Started 26

Specifying calendars (Scheduling rules)

Focus on: Modeling

Focus on: Tracking