Automator_3.6.x_ConfigurationGuide_allOS_en.pdf

March 25, 2018 | Author: Ayman AniKed | Category: Server (Computing), Graphical User Interfaces, User (Computing), Icon (Computing), Hyperlink
Share
Report this link


Comments



Description

CONFIGURATION GUIDEAxway 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 ............................................................................................................................................................ 5 2 Axway Automator .................................................................................................................................................. 6 Presentation .............................................................................................................................................. 6 3 Introduction to configuration ................................................................................................................................ 7 Configuration Options ................................................................................................................................ 7 Menu Bar ........................................................................................................................................... 7 Hierarchy ........................................................................................................................................... 8 Preferences ........................................................................................................................................... 9 Synchronize ......................................................................................................................................... 10 Rights management (Using LDAP) .......................................................................................................... 10 Console Management ............................................................................................................................ 12 4 Configuring the modeling server ........................................................................................................................ 25 Modeling Server screen ............................................................................................................................ 25 Using LDAP ............................................................................................................................................. 26 Internal mechanisms............................................................................................................................. 26 Behavior ......................................................................................................................................... 26 Configuration ....................................................................................................................................... 27 Example for Active Directory management .............................................................................................. 29 5 Configuring production servers ......................................................................................................................... 31 Production server screen .......................................................................................................................... 31 Advanced Tab ......................................................................................................................................... 31 AS/400 production server ......................................................................................................................... 32 Redirection Tab .................................................................................................................................... 33 Accounting Integrator connector ............................................................................................................ 33 Questionnaires Tab .................................................................................................................................. 34 6 Configuring domain servers ............................................................................................................................... 35 Domain server screen .............................................................................................................................. 35 Connectors Tab ....................................................................................................................................... 35 Audit ................................................................................................................................................... 36 7 Configuring connection objects ......................................................................................................................... 37 Connection Objects tab ............................................................................................................................ 37 JDE Connector......................................................................................................................................... 37 Movex M3 Connector ............................................................................................................................... 38 PeopleSoft Connector ............................................................................................................................... 38 Rules ......................................................................................................................................... 39 Pericles Connector ................................................................................................................................... 39 SAP Connector ........................................................................................................................................ 39 Multiple-Instance Principle ..................................................................................................................... 39 Load Balancing and Direct Connection .................................................................................................... 39 Submitting an SAP Job .......................................................................................................................... 41 Web Services Connector ........................................................................................................................... 42 Axway Automator Configuration Guide 2 .............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. 48 User group ...................................................................................................................................................... 43 Process Manager Event Connector................................................................................................................................................................................. 55 What the calendar shows ................................................................................................................................................................... 55 Open Periodic column ................................................................................................................................................................................................................................................ 43 Process Manager Connector ....................................................................................................................................................................................................... 49 User ............................................................................................................. 44 8 Configuring users .......................................................................................................... 50 User Group box .............................................................................................................................. 50 Setting Basic Fields ...................................................................................................................................................................................................................................................... 49 Definition ................... 48 Object type rights ....................................................................................... 53 opscmd API ...................................................................................................................................... 60 Axway Automator Configuration Guide 3 ............................................... 58 11 Configuring scheduling rules ............................................................................................................................................................................................ 46 Context usage ...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... 45 Users .................................. 46 How to associate a context and an object ........................................................................................................................................................................................................................................................................................................................................................................................... 53 9 Configuring calendars ....... 59 Formula editing tab ............................................................................ 51 Context tab ..................................................................... 53 Principle of operation .......... 47 Profiles 47 Main rights .................................................................................................................................................................................................... 48 Updating profiles .................................................................................................................................. 52 User rights in Modeling.................................................................................................................... 55 Closed days ............................................................................................................................................................................... 59 Rule Editing Tab ......... 50 Default View box ............................................................................... 55 10 Configuring macros .................... 47 Profile object ................................................................................................................................................. 46 Context usage example ................................................. 59 Initial Rules tab .............................................................................................................................. 55 Modifying multiple days .................................... 50 Changing the group ............................................................................................................................................................................ 52 User rights in the Processing Tracker ......................................................................................................................................... 54 Modifying the calendar .................................................................... 57 Introduction to macros .......................................................................................................... 51 Rules ...... 49 User group update .................................................................................................................. 57 Keywords ............. 57 Entering the Formula ............................................................................................................................................... 54 Displaying the calendar ......................................................................................................................................... MFT Connector ...... 45 Context object and user rights ............... 46 Rules .......................................... 47 Context audit messages ........... 49 Object user group ................................................................................................................................. 43 Audit ..................................... ............................ 64 Global production server resources ................................................................ 71 Execution group ...................................................................................................................... 66 Creating a global production server resource ............ 68 14 Configuring chart views ........................................ 65 Weight resources .......................................................................................................................................... 71 Axway Automator Configuration Guide 4 ......................................................................................................................................................... 61 12 Configuring date variables .................................................................................................................................................................................... 61 Examples ................................................................................................................................................................................ 66 Modifying the value of a global production server resource . 64 Numeric resources ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ Define the working area ............................................................................................................................. 69 Chart views ...................................................... 63 13 Configuring global resources .. 60 Formula syntax................................................................................................................................................................... 65 FIFO List resources ........................................................................ 65 Global production server resources ....................................................................................................... 69 15 Configuring the execution group .................................................................................................................................................................................. 64 Global resources .... 63 Date variables ............................................................................................................................................. 64 Text resources................................... 66 Operation of global production server resources ..................................... Axway Automator Configuration Guide 5 . we assume that you have a good understanding of Axway Automator. What do you learn about? In this guide. This document is intended for people who need to configure Axway Automator. 1 Introduction What do you want to do? This document describes the procedures for configuring Axway Automator. Presentation Axway Automator is a production automation system that is used to:  Implement production based on graphic modeling features.). 2 Axway Automator This chapter gives a brief overview of the Axway Automator product. etc. jobs. processing diagrams are defined dynamically  Schedule periodic or ad-hoc processing. Automator processes the actions and implements the schedule in real time  Prepare processing automatically  Centralize administration using a driver to provide an overall view of how operations are progressing(ready. applications. rescheduled processing. failed. etc)  Provide a simulation feature to test production scheduling rules Axway Automator Configuration Guide 6 . that is processing that cannot be scheduled in advance  Synchronize all constraints (environment. Double-click an object type to open the list of associated objects. so that it can be queried or modified. and Console Management. (Also available from the toolbar. Double-click an object to edit it. from the menu bar. Hierarchy. This guide describes each of these options. (Also available from the toolbar. 1.) [Save] Save changes to an object in the Configuration module or a chart in the Modeling module. (Also available from the toolbar. Axway Automator Configuration Guide 7 . (Also available from the toolbar. Configuration Options To access the configuration. The right pane is the working area used to create. Synchronize. select Exploration > Exploration Pane > Configuration.) [Print] Print the object configuration. The different types of objects are as follows:  Modeling Server  Production Servers  Domain Servers  Connection Objects  User Groups  Users  Profiles  Calendars  Macros  Scheduling Rules  Date Variables  Global Resources  Chart Views  Execution group The icon is used to mask or redisplay the left pane of the window.) [New] Create a new object. You can then create a new object. 2. modify or view Axway Automator object definitions. click the Configuration icon or. Preferences. This chapter describes the options from this menu that can be selected for and from any object.) [Refresh] Cancel current changes and return to the initial status. 3 Introduction to configuration This chapter describes the basics of configuring Axway Automator. The left pane of the window lists the different types of Axway Automator objects. Menu Bar Action [Reinit] Reset a current modification/query by clearing the data in the fields. [Exit] Exit the application. Date Variables. Global Resources. [Right management] LDAP – Access the lists of login users and user groups. You can search for an element by specifying its name in the text area located in the toolbar. for example). [Close screen] Close the current screen when configuring a specific object (Also available from the toolbar). Modeling or Processing modules. [Console management] List information for servers. Calendars. [Fullscreen] Set the display to full screen size [Exploration Pane] Access the Configuration. [Hierarchy] Access the hierarchical view of the objects used. The link structure is then expanded until the required information is found in the working area. Connected GUIs. Execution Group and Charts. Macros. [Modify my password] Set the password for the connection user. From the V360 version. [Disable Server] Disable a production server. [Open Ref. [About…] Obtain general information on the product. Help [Technical Support] Obtain the contact details for the Technical Support team. [Synchronize] Synchronize the modeling server data with the production servers. Define the specific rights. Users. Exploration [Show/Hide Browser] Display or mask the left pane to obtain a larger window. [Enable Server] Enable a production server. possibilities to have a hierarchical view from a Domain server or a Connection object: Axway Automator Configuration Guide 8 . Hierarchy The Hierarchy menu gives a hierarchical view of the objects defined in Axway Automator and can be accessed from all menus in the configuration module. [Preferences] Modify the look & feel and language of the GUI. Chart locks. and its occurrence. This menu is used to view all the relationships between the elements defined for the Production Server. [Duplicate] Duplicate a resource. [Set my default view] Set the default view for the connection user. Network. Subsequently. an element is selected in the left pane (scheduling rules. Scheduling Rules. Then click the Find Next icon to locate the next element or the Find Previous icon for the previous element. Introduction to configuration Action [Open] Open an existing object. [Delete] Delete an object. Database information and Keys.] Open the reference object. Axway Automator Configuration Guide 9 . Object Color Click to modify the color. General tab In the General tab. you can modify the following general parameters. Parameter Location: Select the user language. you can modify the following parameters. Tracker tab In the (Tracker) Graph tab. Toolbar Displays the icons in the toolbar with or without text. Grid Y-Spacing Distance between two points along the Y axis in the grid. Parameter Position Grid Display or mask Grid X-Spacing Distance between two points along the X axis in the grid. Parameter Automatic scrolling Enable or disable automatic scrolling Display color Select the display color for the objects. CDE/Motif or Microsoft Windows). you can modify the display parameters of the objects in the graph. Introduction to configuration Preferences The Preferences menu is used to manage the preferences of the user logged in and can be accessed from all menus in the configuration module. Modeling tab In the Modeling Graph tab. Any changes you make to the preferences are only applied when you restart the GUI. Look & Feel Selects the type of graphical user interface to be used (JAVA™. When you request synchronization. The Synchronize menu can be accessed from all menus in the configuration module. Use the Rights management to execute a search request in LDAP and obtain the lists of Users and User groups. Rights management (Using LDAP) This requires you to activate the use of the LDAP plug in and set the configuration parameters in the Modeling server definition panel (LDAP tab). You have to associate one or more profiles to a user group Axway Automator Configuration Guide 10 . Refer to Chapter 3. If LDAP is activated. macro. Introduction to configuration Synchronize Synchronization is run on request to update the objects that were modified after at least one instance was created (user password. calendar. which are processed when the schedule is next accessed (subsequent session). User groups From the list of user groups. except for the scheduling rules. the parameters of the objects to be synchronized are sent to the relevant production servers in real time to be applied immediately. select one to retrieve the groups attributes (description) set in LDAP. are preceded by the pencil icon. so that they can be applied. the old configuration is lost: all existing login users and groups are removed (Except OPADMIN). The edition of profiles and contexts for the group allows the connection of the associated users. scheduling rules and date variables). You can find an element by specifying its name in the text area or with search criteria based on the name then click the “Search in ldap …” button to the right of the filter field. Note: The names of objects that have been modified and are to be synchronized. Users Axway Automator Configuration Guide 11 . Contexts tab: the association of contexts to a group makes it possible to restrict the perimeter of action. Introduction to configuration The Inherited contexts tab allows defining contexts which will be inherit by the users of this group. The user inherits all the rights given to all the profiles and contexts associated with the groups allowed in Automator (with icon). description and user groups. a user has to be in a group with at least one profile. Introduction to configuration From the list of users. locked charts. Contexts tab: the Inherited context list displays contexts which are defined for the user groups. Axway Automator Configuration Guide 12 . Console Management Use the management console to locate information about the following sections: list of known and connected servers. Set these rights read and/or write when configuring Profiles. network. To be allowed to connect. select one to retrieve the user attributes.The association of contexts to a user primarily makes it possible to restrict that user’s perimeter of action. set in LDAP. list of interfaces connected to the modeling server. The login users need rights to access the Console management.  File transfer (file $HOME/lists/transfert_tcp. The Production Servers are not automatically synchronized when you access to this console. if we must restart or not the server to take into account the modification. The new values updated in the files are notified to the object instances. Introduction to configuration The list of known and connected servers From this tab. there is a name. icons allow you to synchronize a specific server or all servers. pid. To set or unset a bank holiday. For each line there is ‘no autonomous server’. we can add and delete countries (if not used). From this window. You can configure the production server and the modeling server as follows:  Set the log level and the maximum log size.  Bank holidays: Only on modeling server.  Configure the properties (file $HOME/config/OPSchedule. the real server name.lst): Only on production server. Some information is returned about the server (port. version. and the description with the accepted values. Axway Automator Configuration Guide 13 . the login and the password of the user. just click above. the script used.ini): For each property. the actual value (that we can modify).). we can check if the production servers and domain servers are available. Access and update properties files for ERP connector types used by this Domain Server. add and delete ‘years’ and synchronize the new configuration to the production servers. You can configure the bank holidays. log level. etc.  You can configure the domain server as follows:  Access and update properties files for technical configuration of the Domain Server. In main menus of Automator an alert represented by the icon is displayed if UDP problems are detected (UDP not sent after 5 minutes). From version 3. you can verify the Network activity between a reference server and a specific server chosen from the list.0 with IPv6 compatibility.6. Introduction to configuration Network From the Network tab. Axway Automator Configuration Guide 14 .  List the waiting UDP on servers. use the management console to verify the network activity whatever the protocol version:  Resolve a name (ping in ipv4 and ipv6)  Transaction verification (DCX): alert in case of communication errors. Symbol appears on the left of the servers which have UDP not sent after 5 minutes.  Verify UDP. Axway Automator Configuration Guide 15 . Introduction to configuration Click the button to list the UDP for the selected server. These messages can be activated from the configuration panel of the modeling server.  XOS_ACT_PS_UDP_ALR: problem with UDP sent on production server. Example of UDP in wait on the Modeling Server: The Server name column contains the target server. Audit messages can be generated:  XOS_ACT_MS_UDP_ALR: problem with UDP sent on modeling server. Select a specific Production Server to display the list of waiting UDP: Through this console it is possible for users to delete UDP if they are blocked due to network issue: Right click the UDP to delete. Introduction to configuration To modify the order of display for UDP: Right click the header of the column that you want to sort. Axway Automator Configuration Guide 16 . Introduction to configuration This operation can be dangerous for the production; a dialog box is displayed to confirm your choice: With:  No button to abort.  Yes button to delete the selected UDP. List of locked Charts The OPADMIN user can unlock a chart if it has a bad lock. List of interfaces connected to the modeling server The ‘OPADMIN’ user can disconnect an interface. Database Information You change the database connection parameters in Automator as the OPADMIN user. You have to update the OPSchedule.ini file. The modeling server must be started. You need to have the same username and password in the database environment. It is better to use the Axway Installer in configure mode because that is the only way to update both Automator and XDBM. If there is a difference between the password in the database environment and the password in the OPSchedule.ini file, the modeling server does not start. For more information, refer to the Database Management chapter in the Automator Getting Started Guide. The user’s password is encoded in the file. Do not manually modify the TO_DATABASE_USER_PWD variable in OPSchedule.ini. Database information is only available for the MySQL or MS SQL server database types. Key Management You can display the detail of the key for the specific modeling server:  Date of validity  Activated options  Number of licenses (production servers max) Axway Automator Configuration Guide 17 Introduction to configuration Update center From this tab, you can schedule and trigger update actions for any type of servers. More precisely, you can:  Upload the different service packs or patches required for any server to update (production servers, domain servers or modeling server).  Schedule when (date/time) the update of the various servers will take place; take care to update the servers in the right order : first the domain server(s), then the production server(s) and finally the modeling server. It is not possible to update of GUIs by the update center. The update operations will take place according to the schedule predefined in this step. Warning: in order to update servers in the Windows environment, there are two prerequisites :  The servers must be installed in service mode.  The variable TO_SERVICE_NAME=MyServiceName describing the service name of the server must be set in its configuration file: the file OPSchedule.ini for the Modeling and the Production server and the file server.properties located in the DServer/config directory for the Domain server. Figure 1: the update center tab Use the button corresponding to the action to perform on the selected server: Button Action Schedule a new update Delete the selected update pencil Edit selected update Start/Resume the selected update Hold the selected update Stop the selected update The set of actions you can perform on the update depends on the status of the update, as shown on the following table: When the update has the status Then you can select this Action In Progress Hold - Stop Not Ready Delete – Edit - Stop Scheduled Delete – Edit - Stop Paused Start/Resume Canceled Delete Axway Automator Configuration Guide 18 Introduction to configuration To schedule a new update, follow the steps below: 1. Use the button to schedule a new update 2. Use the icon to select an update file 3. Locate the directory where the Service Packs (.jar) are stored. Axway Automator Configuration Guide 19 Introduction to configuration 4. Click Open to select the file or click Cancel to abort. The list in the column on the left represents the servers associated with the current update. To remove one or more servers from the update: o Select the relevant server(s) in the list on the left. The uploaded files are stored in a specific directory of the modeling server environment (Patchs) 5. To add one or more servers to the update: o Select the relevant server(s) in the list on the right. o Click the Remove button. o Click the Add button. o To add all servers. the list in the column on the right shows all the available servers. Click Upload file to upload the selected file or click Cancel to abort. Axway Automator Configuration Guide 20 . The properties of the selected file are displayed. click Add All. Depending on the platform type and the product version of the selected file. Depending on the predefined schedule. click Remove All. You can schedule the update time independently for each server: o As soon as possible: is the default mode o Specific: if you want to start the update at the date and time you set here by using the calendar in the dialog box: specify the date by clicking the up/down arrows in the format hh:mm (time of the Modeling server) 6. Click Create to create the update or Cancel to abort. the update starts or stays in Scheduled status: Axway Automator Configuration Guide 21 . Use the filter and enter the first characters of the server names to display. Introduction to configuration To remove all servers. it may be necessary to use the management console and synchronize them from the List of servers. If some domain or production servers do not appear in the available list. 5. Launch the script update. 3. When the update starts. 2. Axway Automator Configuration Guide 22 .sh (located in the bin directory for the Domain server and in the scripts directory for the Production server). Download the Service Pack from the modeling server. A notification is automatically sent to the modeling server to record the current update session. Stop of the server (without killing this script). 4. Application of service pack or patch via the Axway Installer product (unattended mode). Restarting the server. Introduction to configuration Automatic process to update a Domain Server or a Production server The performed stepsto update a Domain or a Production server are the same : 1. the JAR files are stored in a specific directory of the target servers (Patchs).bat or update. Application of service pack or patch via the Axway Installer product (unattended mode). Restarting the server. Stop of the server (without killing this script). some errors cannot be returned to the modeling server. however some messages are displayed in the Comments field of the GUI: Axway Automator Configuration Guide 23 . 2.bat or update. Introduction to configuration Automatic process to update the Modeling Server The performed steps to update a Modeling server are: 1. 4. Launch the script update. Error management Due to the independent execution of the script. 3.sh (located in the scripts directory). you can check the procedure’s execution details in the file “update. Axway Automator Configuration Guide 24 .log” located in the logs directory of the target server. Introduction to configuration Examples of available messages:  Service name not set  Wait update of domain servers (all domain servers must be at last in the patch version) Whatever the type of servers. Then select New or Open. To display the corresponding screen: 1. double-click the object. right-click the Modeling Server object in the left panel. applications and jobs. Modeling Server screen The modeling server is the system where users configure all scheduling rules (calendars. 4 Configuring the modeling server This chapter shows how to configure the modeling server. where processing is based. Or. It is also used to establish a link between the GUIs and production servers to track processing. Axway Automator Configuration Guide 25 . The server is used to develop all charts. The graphs created are put into production via the server on user request from the tracker module in the GUI. 2. resources. Click the Configuration tab.) for the jobs to be scheduled. etc. a user has to be in a group with at least one profile. at which the Automator server was last started up. the modeling and production server are able to connect to an LDAP service to identify connection users. on which Console Server is located. Number of charts Displays the number of available charts for statistical purposes. There is no more Focal server to define by default for the Modeling server definition.  When activating LDAP in Automator.  The “Rights Management (LDAP)” panel is activated.  A user disabling LDAP will have a configuration without user groups and login users (Except OPADMIN). Number of applications Displays the number of available applications for statistical purposes. Using LDAP If this option is enabled in the modeling server configuration screen. on which the server is installed. Audit messages and statistics are sent to Axway Sentinel instead of Focal. IP Port Server IP port.  Login fails if the LDAP server is not available. Configuring the modeling server Field Description Server Name Name of the modeling server. Monitor Server Name of the server. only submit users are available in the Automator GUI. (Cf Rights management) To be allowed to connect. Alert Server Name of the server. Axway Automator Configuration Guide 26 . Console Server Name of the server. Description Freeform text of up to 132 characters. Behavior There are several behavior modifications when using LDAP authentication:  The login users are no longer shown in the configuration tree. The LDAP plug-in replaces the standard authentication method. The LDAP plug-in is used to simplify the management of login users. the name of the system. Automator will use it to authorize the connection of a user. instead of defining users within Automator. on which Monitor Server is located. that is. In case a LDAP repository exists on the network. Internal mechanisms You have to associate one or more profiles to a user group. to a group or to a user. Number of jobs Displays the number of available jobs for statistical purposes. You can also associate context(s). by opening a session on the specified LDAP repository when a user connects to an Automator server. on which Alert Server is located. unless you are logged in with OPADMIN. Last Startup Date and time. all existing groups and login users are removed (Except OPADMIN). and defaults to 389. the following parameters are required: Field Description LDAP Server LDAP URI : Specifies the LDAP server to connect to. Clean LDAP cache Force the clean of the LDAP cache To activate the use of the LDAP plug-in.example. Field name for the description. Group fields Group root mapping Field name for the group name. Examples of valid URI  ldap://ldap. User Password The password for the service account used to establish the connection to the LDAP server. Cache TTL Timestamp of definition save.com  ldap://ldap. and must be provided as a Parameter URI. The port number is optional. Connection User The specific name of the service account to use for binding to the LDAP server. Requests LDAP search filters to obtain the list of users. User fields mapping User root Field name for the user name. simply check the checkbox. the list of user groups and the groups of a specific user. Field name for the description.example. LDAP authentication method The protocol must be ldap. ldaps is not supported. Configuring the modeling server Configuration For Automator to be able to connect to LDAP.com:1234 Axway Automator Configuration Guide 27 . Automator replaces the %TOKEN% with a user name.  List groups of user LDAP search filter for listing groups of a user. “sn”  Description is LDAP field for the user description. ou=people. dc=com"  Login is the LDAP field for the user name. “(&(objectClass=person)(sn=%TOKEN%))" The search filter must contain ONLY one” %TOKEN%”. dc=com ))" The search filter must contain ONLY one” %TOKEN%”. Example. replacing %TOKEN%. Only read-only requests are performed. dc=com"  Name is the LDAP field for the group name. “description” Requests  List users LDAP search filter for the user. Example.DC=example. a wildcard can be used. Example. For a group search requests. the search must return ONLY one result. For a given name. Axway Automator Configuration Guide 28 . Example. dc=example. Example. User fields mapping  The user root section contains the root specific name for LDAP user searches. “cn”  Description is the LDAP field for the group description. Example "ou=groups. For a given name replacing %TOKEN% the search must return ONLY one result. “(&(objectClass=groupOfUniqueNames)(cn=%TOKEN%))" The search filter must contain ONLY one” %TOKEN%”. 'CN=ldap.OU=Administrators. “(&(objectClass=groupOfUniqueNames)(uniqueMember=cn=%TOKEN%. Example. “description” Group fields mapping  The group root section contains root distinguished name for LDAP group searches. Example. dc=example. a wildcard can be use. "ou=people. Do not put wildcard directly before or after %TOKEN%. Example. For a user search requests. Do not put a wildcard directly before or after %TOKEN%. Automator replaces the %TOKEN% with a user name.DC=com' No write rights are required. The performance of LDAP search depends on the complexity of these requests. Automator replaces the %TOKEN% by a group name.  List groups LDAP search filter for the group. dc=example. Configuring the modeling server LDAP connection parameter Example. Configuring the modeling server Cache  Cache TTL Time To Live. Example for Active Directory management Axway Automator Configuration Guide 29 . To improve performance. values are read from the cache. Otherwise they are retrieved again from LDAP server. If the user connects again before the end of the TTL. when a user connects to Automator. You can now access the Rights management panel in the Action Menu bar to define the Automator rights.  Clean LDAP cache This button is to force clean the LDAP cache so that all user values will be retrieved from the LDAP server even if the cache entry did not expire. its definition is retrieved from the LDAP server and put in a cache. Configuring the modeling server User fields mapping  The User root field contains the root specific name for LDAP user searches. dc=com"  The Login field is the LDAP field for the user name. dc=example. Automator replaces the %TOKEN% with a user name.  The List groups of user field contains LDAP search filter for listing groups of a user.  The List groups field contains LDAP search filter for the group. Do not put wildcard directly before or after %TOKEN%. “(cn=%TOKEN%))" The search filter must contain ONLY one” %TOKEN%”. Example: “(&(objectClass=group)(member=CN=%TOKEN%. dc=example. Automator replaces the %TOKEN% by a group name. “name” Requests  The List users field contains LDAP search filter for the user.ou=people. Example. Example.dc=axway. "ou=people. “cn”  The Description field is the LDAP field for the group description. For a user search request. Example. “name”  The Description field is the LDAP field for the user description. Example. “(name=%TOKEN%)" The search filter must contain ONLY one” %TOKEN%”. a wildcard can be used. Example "ou=groups. the search must return ONLY one result. dc=com"  The Name field is the LDAP field for the group name. Example. “name” Group fields mapping  The Group root field contains root distinguished name for LDAP group searches. Example. Do not put a wildcard directly before or after %TOKEN%. Example. For a given name replacing %TOKEN% the search must return ONLY one result.dc=com))" Axway Automator Configuration Guide 30 . For a given name. For a group search request. a wildcard can be used. replacing %TOKEN%. Advanced Tab Axway Automator Configuration Guide 31 . To display the corresponding screen: 1. Click the Configuration tab. License verification: It is impossible to create a new Production Server if the max number is closed. _ and @). 3. Right-click the Production Servers object in the left pane. 5 Configuring production servers This chapter describes how to configure the production server. Select New. Production server screen The production servers are the systems where jobs are executed. Field Description Name Network name of the server where the jobs are to be executed. Description Freeform text of up to 132 characters. 2. using up to 128 alphanumeric characters without any special characters (except –. TCP Port Number of the server's communication IP port. If the Enable server box is not checked. Enable This definition is activated for the redirection. uncheck this box to reset the command to XXSBMJOBYY. To modify the duration. so that they can be directed to a predefined jobq. which renames the XXSBMJOBXX command of the unique library to SBMJOB. AS/400 production server If you are using a 0S/400 production serveryou must define the default parameters for the SBMJOB command. for example). a generic user name or *ALL (you do not have to create the generic name or *ALL in the user list). The default duration for request storage is 72 hours. Library Name of the jobq library. a generic job name or *ALL. Conversely. no transactions can be performed between the modeling server and relevant production server (instantiating a Chart. Job name Enter a 10-character job name. In this case. you can define intercepted jobs. A checkbox is used to specify that the log files are to be automatically deleted on a periodic basis according to a number of days between 1 and 99. Redirection Tab If the production server can submit AS/400 jobs. Click the Redirection tab to display the following columns: Field Description Execution Group This execution group must already exist in the configuration and be associated with the execution user. select the AS/400 tab. This parameter is useful when you create a new production server. Axway Automator Configuration Guide 32 . The name of the unique library is stored in the OPSUNIQ dtaara. transaction requests are stored and sent only when you check this box. one which is not yet installed or started. Pending The job is redirected to the jobq and suspended. JOBQ Name of the queue. To do so. use the TO_NOTIF_FREQ=Number_of_seconds preference variable in OPSchedule. User Enter a 10-character user name. If you have a AS/400 production server. you can check the Intercept manual jobs box.ini. Configuring production servers The Advanced tab is used to enter the Job Log directory where the logs of executed jobs are to be stored. TRKApiHome UniversalAgent Installation environment Questionnaires Tab This tab is used to specify the Questionnaires to be inherited by the jobs submitted on the production server. QMGRName Queue Manager MQseries. RDJLang English/French. The first Questionnaire applied is also the first one in the list. you must first define the physical AS/400 users in the user definition and associate them with an execution group. The list on the right shows the available Questionnaires. The list on the left shows the Questionnaires assigned to the production server. Accounting Integrator connector Define the environment variables to execute the three AccountingIntegrator job types: Field Description RDJHome Installation environment. QMGRPrefix TRKHome Sentinel server Installation environment. RDJExec Execution environment. TRKExec Files subdirectory & Script of audit file indexation. Configuring production servers Note: To intercept jobs and redirect them to the jobq. irrespective of the job and chart. The order in which the questionnaires are applied can be modified by selecting a questionnaire in the left-hand list and then using the up-arrow and down-arrow buttons. Axway Automator Configuration Guide 33 . License verification: It is impossible to create a new domain server with inactivated connectors. Select New.6. Axway Automator Configuration Guide 34 . Click the Configuration tab.0. To display the corresponding screen: 1. management of the external applications (ERPs or Axway products) is performed via the Domain server objects and Connections objects. TCP Port Number of the server's communication IP port. the Connectors tab is used to select the connectors to run and monitor. using up to 128 alphanumeric characters without any special characters (except –. 2. Refer to the Automator Reporting Tool User’s Guide. 6 Configuring domain servers This chapter describes how to configure the domain server. From version 3. Connectors Tab A Domain server can communicate with multiple ERP and Axway products. Field Description Name Network name of the server where the jobs are to be executed. Right-click the Domain Server object in the left pane. Description Freeform text of up to 132 characters. 3. It’s possible to create a domain server without any connectors for Reports generation. Domain server screen The domain servers are the systems which communicate with the ERPs interface or other Axway products. _ and @). Configuring domain servers To add one or more connectors to the selection: 1. Axway Automator Configuration Guide 35 . To remove one or more connectors from the selection: 1. Click the Add button. Select the relevant connector(s) in the list on the left. To add all connectors. Audit Messages can be generated:  XOS_CFG_DSRV_NEW: Domain server creation  XOS_CFG_DSRV_UPD: Domain server update  XOS_CFG_DSRV_DEL: Domain server deletion These messages can be activated from the configuration panel of the modeling server. Select the relevant connector(s) in the list on the right. Click the Remove button. 2. To delete all connectors. 2. click Add All. click Remove All. Connection Objects tab This object enables to configure connections to any kind of external application supported by the product. Refer to the Automator Advanced User’s Guide. Click the Configuration tab. You can verify the validity of the JDE connector key in the Console Management or check via API. 7 Configuring connection objects This chapter describes how to configure the different connection objects. Right-click the JDE object in the left pane. 2. JDE Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector. To display the corresponding screen: 1. Select New where you enter the required information. Select the Connection Object type in the left pane. 2. Field Description Environment JDE working environment Role JDE role Axway Automator Configuration Guide 36 . To display the corresponding screen: 1. To display the corresponding screen: 1. Nothing is done if the selected server is the last in the server list Add Add the values of the fields “Application Server” and “Port Number” as a new server in the server list Modify Modify the selected server with the values of the fields “Application Server” and “Port Number” Delete Delete the selected server from the server list Axway Automator Configuration Guide 37 . Refer to the Automator Advanced User’s Guide. Nothing is done if the selected server is the first in the server list Down The selected server takes the place of its successor in the server list. Refer to the Automator Advanced User’s Guide. Right-click the MOVEX object in the left pane. To display the corresponding screen: 1. Right-click the PEOPLESOFT object in the left pane. Select New to enter connection parameters. Field Description Application Server Application Server host to add/modify/delete Port Number JSL Application Server port Server List List of Application Server hosts Button Description Up The selected server takes the place of its predecessor in the server list. You can verify the validity of the PeopleSoft connector key in the Console Management or check via API. You can verify the validity of the Movex M3 connector key in the Console Management or check via API. Select New where you enter the required information. Configuring connection objects Movex M3 Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector. Field Description Server Movex M3 server name Port Movex port number Encryption key PeopleSoft Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector. 2. 2. The Axway Automator production server does not require the same operating system as the SAP/R3 server and can be located on another system. Refer to the Automator Advanced User’s Guide. Bad values may cause the PeopleSoft connector not to run. The application server selected is in the group specified during the connection (PUBLIC by default)  The second mode (Direct Connection) involves connecting directly to a specific application server. You can verify the validity of the Pericles connector key in the Console Management or check via API. You can verify the validity of the SAP connector key in the Console Management or check via API. Select New to enter connection parameters: Host – Network domain – User – Pericles domain. Axway Automator Configuration Guide 38 . The same production server can therefore submit SAP jobs to different SAP instances. Multiple-Instance Principle Each Automator environment configured to submit SAP jobs can connect to one or more SAP systems at the same time. Refer to the Automator Advanced User’s Guide. the name and system number must be specified In either case. Pericles Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector.  2: The servers are tested by list order: the job is submitted to the first reachable server (and low- loaded in the case of PeopleSoft load balancing system).ini files. All the SAP R/3 connection parameters are specified in Axway Automator. To display the corresponding screen: 1. the application server does not use the saprfc. Configuring connection objects Rules  1: At least one Application Server host and port must be added to the server list. However. A TCP/IP connection is used via the standardized SAP/R3 BC-XBP interface. which selects the least-loaded application server for the connection. Load Balancing and Direct Connection There are two modes for connecting to SAP R/3:  The first mode (Load Balancing) involves connecting to a message server. Refer to the list in the SAP prerequisites document. SAP Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector. (The displayed format in the server list is host:port).  3: No verification is performed on these fields. Right-click the PERICLES object in the left pane. only specific operating systems are supported for SAP. In this case. 2. System name or port System name. Configuring the SAP connection object Field Description User The Login User to be specified when logging into SAP/R3. up to 50 alphanumeric characters or Port number. You can choose between two connection modes:  Directly to the application server  Via a message server that selects a connection system known to the group (Load Balancing mode) Field Description Message server name SAP message server name. The Connecting parameters screen displays the fields below. Batch Input Program Allows you to specify a program other than the one normally used to submit input batches. Application server name SAP server name. When load balancing mode is used. Applications server group Applications server group name. up to 50 alphanumeric characters. Client ID System. Configuring connection objects Submitting an SAP Job When a job is submitted. Advanced Parameters Click here to display the additional connection parameters described below. the SAP R/3 connection used is the one creating the job. up to 50 alphanumeric characters. Axway Automator Configuration Guide 39 . SAP selects the application server in the group specified during the connection. This program submits background jobs without waiting for any other jobs submitted to finish. SysNum Two-digit system number (00). up to 50 alphanumeric characters. The user must exist on the SAP/R3 system and have sufficient rights to create jobs and request their execution (including for another user). This additional information is not mandatory. 2. To display the corresponding screen: 1. Refer to the Automator Advanced User’s Guide. Connection control Enable the connection control. User language This field may contain up to two upper-case alphanumeric characters .either two characters for an international code or one character for a SAP language code. This field may contain up to 50 alphanumeric characters. Refer to “Production server and ERP” in the Axway Installation and Prerequisites Guide. Web Services Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector. You can verify the validity of the Web Services connector key in the Console Management or check via API. Configuring connection objects Advanced parameters: Field Description SAP route Name of the SAP route to be used if applicable. A Web Server has to be installed to be able to launch a web service. Right-click the Web Services object in the left pane. Select New where you enter the required information. You can install and deploy a Web Service to test the Automator connector. ABAP debug Enable the ABAP debugger. Debug Enable the SAP RFC traces. Axway Automator Configuration Guide 40 . Field Description WSDL Url Web Service Description Language file localization. 2. Port number Product port number Group For UNIX systems only Process Manager Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector. You can verify the validity of the MFT connector key in the Console Management or check via API. 2. Right-click the Process Manager Event object in the left pane. Retry timeout If the domain server encounters one of the following errors. Select New where you enter the required information. Channel Name of the channel the domain server will use. To display the corresponding screen: 1. Right-click the MFT object in the left pane. Refer to the Automator Advanced User’s Guide. To display the corresponding screen: 1. You can verify the validity of the Process manager connector key in the Console Management or check via API. 3. Refer to the Automator Advanced User’s Guide. there will be no retry. Right-click the Process Manager object in the left pane. Field Description MFT Monitor host name Name of the MFT Suite monitor in charge of the transfer. Refer to the Automator Advanced User’s Guide. You can verify the validity of the Process manager connector key in the Console Management or check via API. Axway Automator Configuration Guide 41 . it will retry until the timeout is reached: Connection error. If the timeout is set to 0. Select New where you enter the required information. Select New where you enter the required information. Configuring connection objects MFT Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector. network error or login error. To display the corresponding screen: 2. Field Description Handler Name Name of the Handler queue to post or get the Process Manager Events Process Manager Event Connector License verification: Refuse the Connection Object definition saving if it is not defined as an authorized connector. Field Description User Process Manager connection user. Axway Automator Configuration Guide 42 . Configuring connection objects Audit Messages can be generated:  XOS_CFG_OBJCNX_NEW: Connection object creation  XOS_CFG_OBJCNX_UPD: Connection object update  XOS_CFG_OBJCNX_DEL: Connection object deletion These messages can be activated from the configuration panel of the modeling server. 2. Password Left-click the key to enter a password with up to 16 characters. To display the corresponding screen: 1. Note: If you are defining an AS/400 user and wish to perform manual job interception for either jobq redirection or manual jobs. Field Description Name User name. 3. Description Freeform text of up to 132 characters. It is a selection criterion for manual job interception. AS/400 Context Exclusively for AS/400. Note: The submit user of a SAP job must be written correctly with the correct case (uppercase or lowercase). you must associate an execution group with the system on which the manual jobs are to be intercepted. Select New. User groups Manage user rights for a login user. If the LDAP plug-in is activated. _ and @). it defines a unique execution group for each system. Context Manage rights on Automator objects. there is no longer access to the Login user configuration (Refer to Rights management chapter). up to 64 characters without any special characters (except –. Users Axway Automator works with three types of users:  Login users can log into the GUI  Submit users can submit jobs  AS/400 users can be intercepted (name. Otherwise. 8 Configuring users This chapter describes how to configure users. *ALL) Login users have a list of chart rights (View/Modeling/Processing Tracker) and a default chart view enabling them to access this view directly when browsing. submission problems could occur. Right-click the Users Login or Submit object in the left pane. Click the Configuration tab. Default View Name of the default view to be selected from a list. Axway Automator Configuration Guide 43 . a user can be allowed to delete any calendar object. Other users will be able to see it but not use it. A context is defined by its name. Modeling server or Production server). which means they are not associated with the connected user. a description and a color. For example. How to associate a context and an object Objects you can associate with a context Objects you cannot associate with a context  Actions  Profiles  Calendars  Charts  Variable dates  Execution groups  Global resources  Instances  Production servers  Domain servers  Connection Objects  Questionnaires  Scheduling rules  Macros  Users  Users Groups  Chart Views You can only associate objects with a context that belongs to the current user (the connected user). some contexts are grayed out. Giving users access to the context only allows the definition of a security policy to restrict access. Configuring users Context object and user rights Context usage Contexts are used to group and to keep some Axway Automator objects safe inside the global scheduling environment. or global. Thus. it is said to be in the global context. calendars that do not belong to the user’s context will be grayed out in the GUI. When an object is not attached to a context.  Deleting a context is possible if it is not attached to an object. But.  Object/context association implies access limitation to the object.  A global object can be used by every user. A change in a context can be tracked by using an audit message. It is possible to include an object in more than one context in order to prevent multiple definitions for the same object (for example. In the following example.  Object and context association is not mandatory. But user rights on the object can restrict usage. Axway Automator Configuration Guide 44 . Rules Keep the following points in mind as you associate objects with a context:  It is not mandatory to create a context in order to be able to use the product. Contexts are made to group objects with some common characteristics. user members of the contexts are the only ones allowed to work with the object.  Write right (W) An object can be created or modified. Context audit messages Messages are generated to track each action of the context. When a change is made to an object used in an instance. one for testing and one for SAP. simply add the context SAP to that user. Some objects like calendars are the same for the three environments. Configuring users Example: How to associate a context with a calendar Note: When a context is added to or deleted from an object. Therefore. resources. Context usage example A production administrator wants to secure its production at the highest level. charts. you might need to synchronize it.  XOS_CFG_CTX_NEW: New context created  XOS_CFG_CTX_UPD: Context updated  XOS_CFG_CTX_DEL: Context deleted These three messages can be activated from the configuration panel on the modeling server. it is possible to allow access only to certain objects of the context SAP. but it cannot be modified. In this way. so they belong to the three contexts. and SAP). Some significant objects like users. synchronization is required to propagate the change to the production servers. can be attached to the context they were created for. Thus. Axway Automator Configuration Guide 45 . but it needs read access. Alternatively. It is enough to add the context "production" for these objects. you can access all the objects in this context. Main rights Four rights have been defined:  Read right (R) An object can be read. A domain exists for production. production servers. if it is necessary to have access to the other context. knowing that there are different environments. a user who is "an administrator" on the context of production does not have any rights on the context SAP and vice versa. test. Three contexts can be created: production. Profiles Profiles allow you to define access rights according to object types.  Execution right (X) This right is dedicated to specific actions. Object type rights Note: Rights may depend on the context where the object belongs. you need to be able to delete the form and to read the questionnaire.  To create an instance. Profile audit Tree messages can be generated to see any change in the profiles.  Red indicates it is not allowed. Object Type Rights Setting Modeling server Chart Views  R Contexts Execution group to let this user read (display) objects of Production servers Charts this type Domain servers Archives  W Connection Objects Questionnaires Profiles Reply cards to let this user write (modify. It is sometimes mandatory to have more than one right to carry out a task. or create) Users group Instances objects of this type Users Actions  D Calendars Forecast planning to let this user delete objects of this Macros Joblogs type Scheduling rules Notifications  X Date variables Console management to let this user shutdown objects of this Global resources Reports generation type (or create Instances from Actions. Axway Automator Configuration Guide 46 . For example:  To delete a response form. like instance and server management. or perform Actions on Instances) Updating profiles A user with sufficient rights can modify a profile. Profile object Description This object is designed to define rights on the Automator object types:  Green indicates that the right is activated. you need to be able to create an instance and to read the chart. But the behavior will not be the same depending on the profile being not used or used. Configuring users  Delete right (D) An object can be deleted and read access is not mandatory. Profile not used The profile is updated and database changes are taken into account.  Grayed out indicates that this object type does not support that right.  XOS_CFG_PRF_NEW: profile creation  XOS_CFG_ PRF _UPD: profile change  XOS_CFG_ PRF _DEL: profile deletion These messages can be activated from the configuration panel on the modeling server. a synchronization operation forwards the changes to the production servers. Rules  At least one profile must exist  The Admin profile is automatically created  An update in the profiles is immediately reported to the users  It is possible to create a profile without any rights. The modification of the profile involves a new calculation of the rights and an update of the permissions granted to the various concerned users. users using this profile will not be able to do anything  A change in the profile can be seen through the audit message sent User group Definition A user group is defined by its name. User group update When a user group is not used The user group is updated. A user group is the simplest way to group login users with the same profile. In production. Configuring users Profile used If the profile is used it will impact all the user groups using this profile and all the users associated with this group. The behavior for Admin is the same as if it was associated with a profile including all rights. Nothing will be in effect on the Production server until synchronization is done. The Admin group is associated with the following profiles: RW (Read and Write). User groups are created to simplify access rights management. Exec_only (Execute) and Delete_only (Delete). no more access to the User group configuration (Refer to Rights management chapter). description and one or more profiles that result in a main profile. If the LDAP plug-in is activated. Axway Automator Configuration Guide 47 . Audit Messages can be generated:  XOS_CFG_UGRP_NEW: User group creation  XOS_CFG_UGRP_UPD: User group update  XOS_CFG_UGRP_DEL: user group deletion These messages can be activated from the configuration panel of the modeling server. Object user group Definition The main profile results from the profiles associated with the group. Note about OPADMIN: The OPADMIN user is a full administrator of Axway Automator and has all rights to everything. Change its password (Modeling server definition panel) and restrict this user usage to maintenance operation. Thus. depending on their type: Login or Submit. either login (can connect to the GUI) or submit (used by the production server to submit a job). choose the following user type: Default View box On startup. Users are displayed in the left-hand tree under two nodes. Each user has a type. Setting Basic Fields In the User screen complete the following fields to define an individual user:  Name  Password  Description Then. the user inherits all the rights given to all the profiles associated with the group. When a user is used in production. you can assign multiple User Groups to a login user.0. each user can have a specific view by default. Rules  A user group must be associated with at least one profile  More than one profile can be associated with a user group  Including more than one profile in a group creates a virtual profile called main profile that corresponds to the sum of all the profiles of the group  It is possible to create one or more user groups  It is not possible to delete a user group used by a user  At least one user group must be created in order to use Axway Automator User A user group can be associated with a login user. User Group box From version 3. Click the field to display the dropdown list of possible views. It does not belong to any user group. in the Parameters tab. as specified here. Configuring users When a user group is used The users using this group are impacted. Rights for the users are calculated. synchronization is needed in order to propagate information to the production servers.6. only submission users are displayed. Axway Automator Configuration Guide 48 . Note: When LDAP is enabled. rights for the users are recalculated. Changing the group When a user’s groups are changed it modifies the rights associated with the user. Conversely. If the users are used in production. a reduction of context also reduces the user’s scope of activity on the product. Any addition of a context makes a larger view of the product available. A change will impact all the users in the group. Context tab The Inherited context list displays contexts which are defined for the user groups. It inherits the rights associated with the new group and loses all the old ones. Groups can be used to define roles. The association of contexts to a user primarily makes it possible to restrict that user’s perimeter of action. a request for synchronization is made to update the known users on the production servers. users can only act on global objects. Configuring users When associated with groups. Axway Automator Configuration Guide 49 . the users will not inherit the modifications made by the new group. Until synchronization is done. Thus. a user inherits the group's rights. When updating a group. or on the objects in their contexts. This modification of a group involves a new calculation of the rights and an update of the permissions granted to the various users concerned. You may need to synchronize again (using the pencil icon). verifications are made in order to not use objects which are not in the user’s context  One or more contexts can be associated with the chart  It is not obligatory to associate a context with a chart. User rights in Modeling Field Description Charts Rights also apply to charts. The rules are as follows:  One or more contexts can be associated with a questionnaire  It is not mandatory to associate a context with a questionnaire. The management of the basic rights (reading. writing and suppression) is handled in a simple way. Configuring users Rules  Login user/group association is mandatory. It will be global and visible to all users  It is impossible to associate a context with a response form.  It is not possible to specify the context when archiving  Archive inherits context(s) associated with the chart Questionnaires Rights are applied during the management of the questionnaires and the response cards.  Any change of group involves a modification of the rights associated with the user.  While modeling a chart. In this case.  The user inherits the rights of the user groups. It inherits the contexts which are associated with the questionnaire Axway Automator Configuration Guide 50 . it will be global and visible by all the users Archives Rights are applied during archiving and with management of the archives. the action will be global and visible to all users  It is not possible to specify a specific context to instances when generated with an action. opscmd API The opscmd API integrates the concept of safety. When no context is given. The API uses the user id to check the rights associated with that user. When the user does not have the rights an error message is generated. the servers are able to detect if the action is protected or allowed. as well as reading rights to be able to open the tracker graph  The instance must belong to the user context or to the global context to act on it Report Rights are applied to reports generation. The rules are:  Verifications are done in order not to be able to use objects resulting from the configuration or modeling and not forming part of the context user in the action  One or more contexts can be associated in action but it is not mandatory. When attempting to connect to a production server or modeling server through the API. the API connects to the modeling or production server to verify that the user has enough rights to execute and connect to the API. Before executing. Axway Automator Configuration Guide 51 . Configuring users User rights in the Processing Tracker Field Description Actions Rights are applied to actions management. Principle of operation A change to the API is not visible. The rules are:  The user must have execution rights on the instance to be able to act on it. All the instances inherit the action context Instances Rights are applied to instance management. 2. Description Freeform text of up to 132 characters. You can define an unlimited number of calendars. Axway Automator Configuration Guide 52 . etc. such as January 1. _ and @). National State Holidays Check this box to automatically integrate holidays (marked in red) into the current year. Year Year currently being configured. To display the corresponding screen: 1. Left-click the Configuration tab. Field Description Name Calendar name. Displaying the calendar Calendars use basic processing rules. 9 Configuring calendars This chapter describes how to configure calendars.. up to 32 alphanumeric characters without any special characters (except –. Carry Forward Specific Days Check this box to automatically integrate specific days in the calendar when carrying it forward to the following year (refer to Specific Workday and Specific Holiday). They define the workdays and holidays. May 1. Right-click the Calendars object in the left pane. which can be renewed for subsequent years. according to the country selected from the list above it. then select New. Configuring calendars Modifying the calendar What the calendar shows  Green: Workday  Red: Holiday  Blue: Holiday forced as a workday  Violet: Workday forced as a holiday The days selected are displayed in light blue. Click the Non-Specific icon. To select a set of consecutive days (from February 9 to February 13 for example): 1. Axway Automator Configuration Guide 53 . 00:00 to 23:59 is considered to be a full workday. Click the first day in the range (February 9). Specific Holiday and Non-Specific icons To define workdays or holidays: 1. 3. for example) for all the months in the year. You can check several days (every Saturday and Sunday for example). To cancel a forced workday or holiday: 1. 2. by specifying as a workday every first or last day of the:  Week  Fortnight  Month  Year Check the relevant boxes to make your selection. check the day of the week in the Closed days group. Modifying multiple days There are several methods to select a number of days to be modified. Closed days To define the same day of the week as a holiday for the whole year (every Saturday for example). Select the relevant day (which turns light blue). 2. Open Periodic column This column is used to define a calendar based on a recurrence method. To select all the days in the year. Specific Workday. To select the same day of the month (the third. click the button in the top left of the calendar table. By default. click the month label in the column header. Select the relevant day. Hold down the mouse button and drag the pointer to the last day in the same range (February 13). Release the mouse button (the selection is limited to a given month). click the appropriate row header in the calendar table. 2. To select a month. Click either the Specific Workday or Specific Holiday button. Configuring calendars This is an additional selection method. the previous workday is selected. if the last recurring day is already defined as a holiday. so that Monday. which takes into account the days that have already been defined. Likewise. Axway Automator Configuration Guide 54 . then the following workday is automatically selected. January 3 can be considered to be the first day of the month of January 2011. if the first recurring day is already defined as a holiday. For example. Click the Configuration tab. Select the Macros object in the left pane. Introduction to 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 keywords and arithmetic operators (+ and -). To display the corresponding screen: 1. Accented characters can be used. 2. Description Freeform text. Keywords The objects available when defining a macro are lower-case keywords. Formula Text expressing the rule. up to 20 characters. Axway Automator Configuration Guide 55 . 10 Configuring macros This chapter describes how to configure macros. Field Description Name Macro name. without any special characters (except – _ and @). nm3 Entering the Formula The macro definition area is divided into two panes:  The left pane displays the list of predefined keywords  The right pane is a working area used to create. To define the macro working area: 1. view or modify the text of the macro. Directly enter the keyword or its abbreviated form in bold characters. Double-click the selected keyword. you will need to create a macro like: last. Configuring macros English keywords are divided into six groups: Days Types Lengths Months Orders Operators day work year January first = today closed nan1 February last + Monday calendar pan1 March - Tuesday month April > Wednesday nm1-12 May >= Thursday pm1-12 June < Friday fortnight July <= Saturday week August <> Sunday September October November December The nm1-12 and pm1-12 stands for next month (1 to 12) and previous month (1 to 12). 2. Refer to the paragraph Formula editing tab for further details on the syntax. 3. Axway Automator Configuration Guide 56 . To select the last day of the previous quarter. Select the keyword and clicking the Insert icon.work.calendar. The syntax is checked and an error window is displayed if necessary. Axway Automator Configuration Guide 57 . Left-click the Configuration tab. Check the Formula box to access the Formula Editing feature. Right-click the Scheduling Rules object in the left pane. 4. without any special characters (except –. Check the Rules or Formula box to access both features. Apply Check the Rules box to access the Rule Editing feature. You cannot create a rule if no calendar has been defined. To display the corresponding screen: 1. Description Freeform text. 11 Configuring scheduling rules This chapter describes how to configure scheduling rules. or select the All box (using the red or green check mark) The combination of these selections is expressed as a logical AND. 2. You can define both rules and formulas to determine the scheduling slot. up to 62 characters. on which scheduling is to be based. _ and @). Note: A scheduling rule must be associated with a calendar. Complete the fields on the resulting window as follows: Field Description Name Name of the rule. Select New. or check the corresponding All box (using the red or green check marks)  Weeks: Select the execution weeks or check the All box  Month of the year: Select the execution months or check the All box  Number of days: Select days by their number in the month of the current year as workdays and/or holydays. Rule Editing Tab Use the Rule Editing tab to enter specific rules to fine-tune application or job scheduling with respect to the calendar and frequency defined by:  Days: Select the execution workdays and/or holidays. Initial Rules tab You can define rules associated with the calendar definition to apply restrictions when scheduling the jobs to be executed. 3. The result obtained is expressed as a logical OR. Calendar To be selected from a list: name of the calendar. and click the Insert button. The objects available when entering the formula are keywords or macros (that have already been defined – refer to Section). 2. Configuring scheduling rules Once defined. Formula editing tab The Formula Editing tab is used to define more complex scheduling rules. Define the working area To define the formula working area: 1. Enter the keyword or macro directly. 3. you can perform a quick real-time test on a scheduling rule for better adjustment. Select the keyword or macro. Axway Automator Configuration Guide 58 . Double-click the selected keyword or macro. tuesday. march. february. day[.work.day. august. pm1-12 Month_label january.day..calendar.month + 1.month} test {today=2.yy] or dd-mm[-yy] day_label month_label type Expr_op + or – Complement nnn.day. day_label Day_label monday.1. <=. july.day} test {today=last.day.day. november. wednesday.calendar.fortnight} test {today=monday} test {today=3.month} test {today=2. friday.day. it displays a window that informs you that the formula syntax is invalid. may.day.month} Axway Automator Configuration Guide 59 .work.work.work.work} test {today=last.mm[. thursday.type] Order first. calendar Period year. nm1-12.work} test {today=3. saturday.type. december Lines that begin with the hash symbol (#) are treated as comments.week . Configuring scheduling rules Formula syntax The formula syntax is as follows: Formula test { comparison [ and/or comparison ] } [ formula ] Comparison expression operator expression Operator =.work.month + 3.month} test {today=last.week} test {today=last. Examples test {today=last.work.day.day.month} test {today=1.work.day. The syntax is checked. fortnight.work. <.1. september. >.work. closed. week.day.work. <> Expression base [ expr_op complement ] Base Six possible options: today order.day.friday. Sunday Type work.work.day.work} test {today=first. Parentheses can group comparisons to establish priorities between ANDs and ORs.3. The nm1-12 and pm1-12 periods allows you to select a previous (pm) or coming month (nm). april. october.pan1. last.length dd.week .month. If the system finds a problem. >=. june. xxx (day of the year in the associated period) Day day. nan1. 12.month .pm1 + 7.day.day.calendar.7.friday.01} test {today=work and today<>last.year} test {today>15.calendar.work.01. Configuring scheduling rules test {today=3.day} test {today=january or today=february} test {today=last.calendar} Axway Automator Configuration Guide 60 .00 and today < 01.work.day.month} test {today = last.calendar.day.day. _ and @). without any special characters (except –. Then select New. Schedule Type Schedule button: the schedule date is taken as the reference date. Date variables Date variables can be passed to jobs as parameters. Click the Configuration tab. up to 32 characters. there must be at least one calendar and one macro. to which the variable applies. 2. Right-click the Date Variables object in the left pane. 12 Configuring date variables This chapter describes how to configure date variables. Format To be selected from a list. Calendar To be selected from a list: name of the calendar. 3. You can do testing to evaluate the variable date. System button: the system date is taken as the reference date. Macros To be selected from a list: name of the macro used. Description Freeform text of up to 132 characters. To create a date variable. To display the corresponding screen: 1. Field Description Name Resource name. Axway Automator Configuration Guide 61 . Complete the fields on the resulting screen display as follows: Field Description Name Resource name. Global resources Used in Charts. Select New. up to 32 characters. Description Freeform text of up to 132 characters. 13 Configuring global resources This chapter describes how to configure global resources. Resources enable you to:  Determine how applications or jobs are started up  Pass values to the applications or jobs as parameters There are two types of resource:  Global resources common to all charts  Resources local to a chart In the Configuration module. The various resources are of the following types:  Numerics  Texts  Weights  FIFO lists Possibility to duplicate an existing resource to create a new resource. >. _ and @). <. It is a text area that only contains digits. Numeric resources This type of resource is used to trigger applications or jobs when the resource has a given numeric value. Right-click Numerics. <>. without any special characters (except –. Value Instant resource value. To display the corresponding screen: 1. this information is dynamically updated by the GUI or online Automator commands. Axway Automator Configuration Guide 62 . 4. Global production server resources Global production server resources work in the same way as conventional global resources. The execution criteria are =. 3. 2. Select the Global Resources object in the left pane. Click the Configuration tab. except that they are managed directly by the production servers and not the modeling server. only global resources are processed. >= and <=. up to 32 characters. Right-click Texts. Select the Global Resources object in the left pane. To display the corresponding screen: 1. For example. <> and an expected value. 4. processing is submitted with the first domain name. To display the corresponding screen: 1. Example: If a FIFO list contains domain names. FIFO List resources This type of resource is used to perform several requests for the same application or job. Description Freeform text of up to 132 characters. 2. 5. Example: Four processing operations are to be submitted to a system that can only accept two concurrently. 2. It is only a text area. without any special characters (except –. Weight Initially set to 0. a job must be performed if another Automator job has given the OK. Value This information is dynamically updated by the GUI or online Automator commands. Complete the fields on the resulting screen display as follows: Field Description Name Resource name. on completion. without any special characters (except –. Description Freeform text of up to 132 characters. The criteria are =. 4. _ and @). this information is automatically incremented and decremented by the Automator engine. Click the Configuration tab. Weight resources These resources are used to manage job exclusivity or the overall job load. Select the Global Resources object in the left pane. Configuring global resources Text resources This type of resource is used to trigger applications or jobs when the resource has a given alphanumeric value. Click the Configuration tab. Processing is performed in sequence for each element in the FIFO list. 3. the second domain name is used and so on until the end of the list is reached. 3. Maximum Value Threshold value. up to 32 characters. Right-click Weights. Select New. _ and @). Select New. 5. Click the Configuration tab. Complete the fields on the resulting screen display as follows: Field Description Name Resource name. Axway Automator Configuration Guide 63 . To display the corresponding screen: 1. It is impossible to manage a global resource for a production server if this production server is managed by a Frontal processor. After you select the server. there are two possibilities:  Either the production server knows the resource and returns its value. Modifying the value of a global production server resource Display a global production server resource via the configuration tab on the GUI. with one element per line. and use them within production charts. Note: A global resource (that is. Complete the fields on the resulting screen display as follows: Field Description Name Resource name. 5. the GUI prompts you to specify the production server where you want to retrieve the value. Description Freeform text. Global production server resources A global production server resource is a global resource with a specific value for each production server. This section describes how to create them. it is known by all production servers after you have created an instance on each server. _ and @). up to 32 characters. without any special characters (except –. If you create a global production server resource. 3. Configuring global resources 2. FIFO List Current stack. When you open its definition. Select the Global Resources object in the left pane. Right-click FIFO Lists. a resource that is not specific to the production server) is known to the entire information system (all instances on all production servers). It is stored on the modeling server and can therefore only be accessed if the modeling server is active. retrieve their value in the configuration. Creating a global production server resource When you create a global resource (configuration tab on the GUI). a checkbox is available to specify whether it is a conventional global resource (managed by the modeling server) or specific to the production server (as illustrated). 4. The list is limited to 65500 characters. Select New. The instances on the same production server can therefore access the same data. Axway Automator Configuration Guide 64 . The instance must be created after the resource. In this case. Configuring global resources  Or. Therefore. an error message is displayed. Axway Automator Configuration Guide 65 . open the resource definition on the relevant server and then modify its value and save. the production server does not know the resources. No instance was created on the production server since the resource was created. To set the value of the resource on a specific production server. the same resource on different production servers can have different values. Multiple-system chart In the case of multiple-system charts. when you assign a value for a global production server resource. you are modifying the value of the resource on the main production server. request the statuses of the instances in the processing module on the GUI and then click the Parameters tab). you are testing the value of the resource on the main production server. all the relevant operations are performed on the main server for the instance (to determine which is the main server for an instance. Similarly. Consequently. Configuring global resources For a global production server resource the FIFO list is limited to 65500 characters. when you need to evaluate or assign a value to a global production server resource. and the values are saved by the production servers and not the modeling server. a global production server resource works in the same way as a conventional global resource only (such as for assigns. when you test a global production server resource. Operation of global production server resources Single-system chart In the case of single-system charts. Axway Automator Configuration Guide 66 . test and expression objects). To add one or more charts to the view: 1. To display the corresponding screen: 1. Field Description Name View name. Chart views Chart views are full or partial logical groups of all charts. To add all graphs. without any special characters (except –. Click the Configuration tab. click Add All. _ and @). Description Freeform text of up to 132 characters. Select New. up to 30 alphanumeric characters. 2. Select the relevant chart(s) in the list on the right. 3. Click the Add button. 2. Right-click the Chart Views object in the left pane. so that users can only work on relevant graphs. Axway Automator Configuration Guide 67 . 14 Configuring chart views This chapter describes how to configure the chart views. The default view appears with a specific icon (star). groups all existing charts automatically. named AutView. Axway Automator Configuration Guide 68 . The change is only applied when you restart the GUI. the connection user is able to set the default view. click Delete All. Select the relevant chart(s) in the list on the left. Set my default view On the views tree. A default Chart view. To delete all charts. 2. Click the Delete button. Configuring chart views To delete one or more charts from the view: 1. HSB Color shades. the execution group is an important selection criterion for manual job interception. To display the corresponding screen. but with a start time of H2 = 8:00 p. RGB Color shades. On AS400 systems.  Execute the same chart with the Evening execution group according to the same scheduling rule. The execution group concept can therefore be assimilated with the scheduling session concept. but once a month. It is only significant if associated with the instances. Field Description Name View name.m. Group Color Color selected for the execution group. The execution group is represented only by a name and color. a MONTHLY execution group action processes all the objects (several execution groups can be assigned to an object). _ and @). For example. you must associate an execution group with each user (name. Description Freeform text of up to 132 characters. Consequently.m. Example: A user defines a chart with an execution group object (MONTHLY). without any special characters (except –. the chart is executed without the MONTHLY group object. To intercept manual jobs. Then select New. but with two different execution groups. Execution group The execution group concept is used to dissociate the various execution instances in the same chart. 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). up to 30 alphanumeric characters. Swatches Choice of colors. which is different from the other group objects (DAY). right-click the Execution group object in the left pane. *ALL) on an AS400 system. You can thus 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. left-click the Configuration tab. When the action is triggered for the DAY execution group. these actions are used to start all or part of the same chart on the same day. 15 Configuring the execution group This chapter describes how to configure the execution group. Axway Automator Configuration Guide 69 . Documents Similar To Automator_3.6.x_ConfigurationGuide_allOS_en.pdfSkip carouselcarousel previouscarousel nextCitectSCADA 7.0 Service Pack 3 - Release NotesSAPUPgade4General Product Support Assessment (v4.0)Oskar Lange Economia Politica PDFLink Planner Release Notes v3.6.4How to Reduce the Security Risk in Solaris _ - Generic OS Hardening Steps - UnixArena_ENERO_5Abbworld - Step Wise Procedure to Update Customer ListAppsDBA CourseNodeb Lmt User Guide(v200r013_03)(PDF)-EnPSU Patch 12cTI-Nspire_ComputerLink_ENG.pdfR MOD 01-Unisphere Security and Basic ManagementSS110 ADM MAN 08 Deployment Monitoring 04292015nistir-7621Networking Module 1 Ques BankAssistant Enlist of games.docxSLIDES APDE2002 Uren Data DictionaryChapter 2Install Notes (Please Read) (Copy)ActivInspire Readme.txt122ebsmtChange Log01 Installation Advanced Administration Topics 2CON8671 Roncati Naguib-EMOOWSession1026201518475108 Ow to Apply an Oracle PatchWin Ora Upgrade v50ODA 3 PatchingInstructions for Remote Update of UP for IEC104 ParametersMore From Ayman AniKedSkip carouselcarousel previouscarousel nextAutomator_3.6.x_AdvancedUsersGuide_allOS_en.pdf5.2. Bdays Arg Personal - Sran Cran 20150903GreenNets_WhitePaper.pdfAutomator_3.6.x_FrontalUsersGuide_allOS_en.pdfApprentissage Semi Supervidse(788356260) tuto_SP05 CongestionExotec Solutions Internship - Mobile Robot Control (concatenated) (1).pdfAutomator_3.6.x_GuideConfiguration_allOS_fr.pdfAutomator 3.6.x DomainServerUsersGuide AllOS EnAutomator_3.6.x_GuideDeModelisation_allOS_fr.pdfAutomator_3.6.x_GettingStarted_allOS_en.pdfAutomator_3.6.x_GuideDemarrage_allOS_fr.pdfNoel Adultes2016 v2Saclay_13_oct_2014OCW UC3M Digital Communicationds Exercices T5OCW UC3M Digital Communications Exercices T2ThesisdproductFlyerd_978-0-387-22575-3 (1)Correction Exam 2013 20143320 Basics of Spread SpectrumAsee Paper 2d12 r1 Post Draft 34Conv. St Tezch 2015 + Fiche EvalExamen Sari Fioddrinaoct2012v2Exam_2013_2014Rep 2000dKhreis Alaa EnIPv6-1.0b-notesKhreis Alaa FrFooter MenuBack To TopAboutAbout ScribdPressOur blogJoin our team!Contact UsJoin todayInvite FriendsGiftsLegalTermsPrivacyCopyrightSupportHelp / FAQAccessibilityPurchase helpAdChoicesPublishersSocial MediaCopyright © 2018 Scribd Inc. .Browse Books.Site Directory.Site Language: English中文EspañolالعربيةPortuguês日本語DeutschFrançaisTurkceРусский языкTiếng việtJęzyk polskiBahasa indonesiaSign up to vote on this titleUsefulNot usefulYou're Reading a Free PreviewDownloadClose DialogAre you sure?This action might not be possible to undo. Are you sure you want to continue?CANCELOK
Copyright © 2024 DOKUMEN.SITE Inc.