1 / 57

Managing SX.e and TWL with scripts and MARC

Managing SX.e and TWL with scripts and MARC. 02/12/04 Jeremiah Curtis. Assumptions. You should understand: MARC -- What it is and generally what it does Unix -- what it is and basic commands Shell Scripts -- what they are and what they are used for

rinah-solomon
Télécharger la présentation

Managing SX.e and TWL with scripts and MARC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Managing SX.e and TWL with scripts and MARC 02/12/04 Jeremiah Curtis

  2. Assumptions You should understand: • MARC -- What it is and generally what it does • Unix -- what it is and basic commands • Shell Scripts -- what they are and what they are used for • Basic understanding of TWL (for the TWL specific portions – you can nap during these portions if you are not concerned with TWL)

  3. Once upon a time… • … customers as well as NxTrend personnel identified the need to have a standard set of scripts • MARC would generate the standard set • Everyone would be happy

  4. The Shadow... • NxTrend support identified needs that the MARC scripts did not address • The product evolved, but MARC was not well suited to this change • So, there became two sets of scripts • GFI for Go For It • MARC

  5. Confusion Reigned... • There was confusion • Which scripts should be used? • Which were getting installed?

  6. An Alliance was Forged... • The decision came that there should be only one set of scripts • MARC should generate these scripts • MARC should be flexible enough to handle future needs

  7. Harmony was Restored... • All scripts will be generated by MARC and are stored as templates • No longer hand editing scripts • Script issues will begin by regenerating all scripts • New scripts are easily added and existing ones easily updated

  8. The End

  9. The Changes • The next section describes the current set of scripts

  10. New Scripts and New Names • Many new scripts have been added to MARC’s script base • Many more scripts had a name change to standardize names and functions

  11. The Progress Admin Server • These scripts help manage the Progress Admin and Name Servers admin.start admin.shut admin.query nameserver.query

  12. The Database • These scripts help manage the database brokers dbbroker.start dbbroker.shut dbbroker.query • These are database utilities dbstats truncate.bi

  13. The Application Broker • These scripts help manage the Progress Application Brokers appbroker.start appbroker.shut appbroker.query

  14. Parameter Files • The following are a new set of parameter files for client connections client.pf editor.pf batch.pf singleuser.pf connect.pf

  15. The Environment • These scripts help manage this particular environment nxt.env nxtall.start nxtall.shut

  16. Enterprise • To start SX.enterprise, now use sxe sxe sxee

  17. The Report Manager • These are the Report Manager scripts rptmgr (or rptmgr.start) rptmgr.shut

  18. Binary Dump and Load • These scripts are for Dump and Loads easybd sareabd bddriver.p sareabddriver.p bddumpall.p bddumparea.p bdloadall.p bdloadarea.p bdscript.p sareabdscript.p

  19. After Imaging • These scripts are for AI aimage.start aimage.shut aimage.backedup aimage.list aimage.archive aimage.new aistats rollforward.ai truncate.ai

  20. Backups • These are new standard backup scripts backup.data backup.full backup.online backup.files

  21. RxServer • RxServer scripts are now generated by MARC rxsfax.sh rxsprint.sh emailout.sh

  22. Other Scripts • These don’t fit anywhere else rdclean sassi.sh shutuser showuser config_rpt

  23. TWL • TWL scripts have been mostly rewritten • MARC generates all of the needed TWL scripts • TWL scripts now follow a standard naming convention

  24. Additional TWL Application Broker • These scripts help manage the Application Broker that manages TWL connections to the SX.enterprise database twlentappbroker.start twlentappbroker.shut twlentappbroker.query • TWL also uses the normal appbroker scripts which are generated from TWLMARC. These appbrokers are for connections to the TWL database

  25. TWL RF Units • These scripts are used to start the TWL application on RF units twlrf twlentrf twlentrf.pf

  26. Additional TWL Environment • Since TWL integrates with SX.enterprise, an additional environment is available using: twlsecondary.env

  27. TWL End of Day • These scripts are used to run TWL End of Day processing. These are usually called from the backup scripts • The first script performs processing that requires a single-user connection to the DB while the second performs tasks using a normal multi-user connection to the DB twleod1 twleod2

  28. TWL Interfaces • The following scripts are used to manage the TWL interfaces twlsend.start twlrcvpack.sh twlsend.sh twlrcv.sh twlsend.shut twlrcv.shut twlsend.query twlrcv.query

  29. The Templates • The next section describes the new Script Generator in MARC

  30. MARC Generate Scripts • MARC • Databases -> Configure -> Generate Scripts • Select the database(s) to generate scripts for • Select the scripts to generate

  31. Script Template • All scripts generated by MARC are stored as templates • These templates contain the form of the final script • Critical portions of a template contain tags • These tags get substituted with real values to generate a script

  32. MARC Generate Scripts • All of the templates reside in subdirectories under /rd/marc/scripts/template • All templates must end with a .tpl • These subdirectories are: base dg hp ibm sco intchan taxware twl

  33. MARC Generate Scripts • All of the templates in base are added to the list • One system directory is included based on the selected machine type in Installations -> Configure (e.g. ibm) • If optional products are setup in MARC, then those templates are also included in the list (e.g. twl) • The custom directory is always checked first and overrides a standard template of the same name

  34. Custom Scripts • Script templates may also be in /rd/marc/scripts/cust in the same subdirectories • Copy the template from the directory under /rd/marc/scripts/template

  35. Template Tags • There are two types of template tags • System tags (defined by MARC) • Custom tags (defined by the user) • Tags are names enclosed in ‘< >’ • Example: <ENVNAME> • The convention is to use tag names that are all capital letters

  36. System Tags • System tags are defined during the installation of MARC • System tags contain values that MARC can get from the information in its own database • System Tags can not be edited directly with the tag editor

  37. Custom Tags • Users may use the Tag Editor to create and edit tags. • Custom tags are created by users or may be in some delivered scripts (e.g. rxsprint.sh) • Values for the tags can be assigned in two ways: • By answering the prompt when MARC finds an undefined tag • By using the tag editor in Databases -> Configure -> Tag Editor

  38. The Tag Editor • The tag editor allows the user to: • Create new custom tags • Modify existing custom tags • Delete custom tags

  39. Example Template • Here is a simple template <SCRIPTNAME=ENV”helloworld.sh”> <DESTDIR=BIN> echo “Hello, world!” • Top two lines are reserved for formatting • SCRIPTNAME is what the script will be called • DESTDIR tells where the script will get created

  40. Script Naming <SCRIPTNAME=ENV”helloworld.sh”> • All scripts should be prefaced with the environment name • Use ENV before the script name to substitute in the environment name in the MARC that is generating the script

  41. Destinations <DESTDIR=BIN> • The destination directory can be a path • The destination can be one of these predefined directories BIN OPSYS RD EXEC

  42. Building A Script • Here is a simple template “helloworld.sh.tpl” <SCRIPTNAME=ENV”helloworld.sh”> <DESTDIR=BIN> echo “Hello, world!” • Should be created in the ../cust/base directory • Generating script to /rd/bin/

  43. Script Templates - Summary • All scripts will be generated by MARC and are stored as templates • Should no longer hand edit scripts • Script issues will begin by regenerating all scripts • New scripts are easily added and existing ones easily updated

  44. MARC Enhancements The next section describes some changes in Progress 9 and changes in MARC 10.1

  45. First, Some Background • With the advent of Progress 9, there are some new concepts to understand • MARC 10.1 also contains many changes to accommodate the new version of Progress as well as a few enhancements

  46. Storage Areas • The Progress database has changed to incorporate a new concept of storage areas • Storage areas are a logical grouping of tables • Storage areas are also in their own files on disk and have extents • Oh, and by the way, all Progress 9 databases are multi-volume and will have extents

  47. Progress Admin and Name Servers • MARC can now configure the ports used by the Progress Admin and Name Servers • Admin Server Port • Admin Server Admin Port • Name Server Port • Allows for multiple installs of Progress • Live: /rd/dlc • Test: /test/rd/dlc

  48. Installation Configure Screen • New Environment Name • Online Backup Directory • AI Save Directory • Layout Changes

  49. Database Configuration • With storage areas, MARC has the ability to configure extents for the storage areas • Each storage area can be configured to have a certain number of fixed extents plus the size for the fixed extents

  50. AppServer Changes • The AppServer source code is not on the Unix server anymore • Therefore the AppServer is not compiled from MARC anymore • The AppServer is pushed from the Staging Client

More Related