1. Managing SX.e and TWL with MARC and Scripts Jeremiah Curtis Jcurtis@nxtrend.com

2. Manager’s Administrative Resource Controller - MARC MARC is a tool that is used to assist our customers and our support personnel to manage our product environments in a Unix environment MARC is an application written in the Progress 4GL language It is a character-based application and has its own database called MARC (surprised?)

3. First, A Quick Review What is Progress and how does it relate to SX.enterprise? How is a Progress database managed? What operations need to be performed on a NxTrend product database?

4. Starting MARC MARC is started from the Unix command line –Usually, all that is needed is to type marc Often, there will also be other MARC applications on your system –TWL will have its own MARC and it is started using the twlmarc command –A test environment will have its own MARC and is usually started with testmarc All these MARCs are typically the same version, though they don’t have to be. However, they will all function basically the same Parameters that are in MARC vary depending on the product it is managing.

5. The Main Menu The main menu in MARC contains the following items: –Databases –Installation –Backup –System –Communications –Logs –Exit

7. The Database Menu The database menu contains items for managing your database and related processes –Starting and stopping your database –Starting and stopping your application brokers –Creating dump and load scripts –Application broker and TWL compiles are located here as well

9. Start and Stop Database Severs

10. Start and Stop Application Brokers

11. Databases->Cofigure->Generate Scripts Select the database for the scripts to include

12. Select the Scripts to Generate

13. The Installation Menu The installation menu performs installation and configure functions The environment information is entered here such as file locations This menu also contains functions to compile and library SX.enterprise

15. Installations->Configure

16. Installations->Utilities

17. Installation Programs

18. The Backup Menu The only item on this menu is a function for configuring backup scripts

20. Backup Script Options

21. The System Menu The system menu has other functions One set is for administrating the admin server There are also functions for Clippership and Taxware

23. Admin Server Start and Stop

24. The Logs Menu The logs menu is where you can view logs from various MARC functions Most of these are related to the installation process such as when the product was installed or a code compile

26. Viewing Specific Logs

27. MARC Generated Scripts NxTrend has a standard set of scripts used for Unix environment management All these scripts are generated from MARC which customizes the standard scripts to account for your local environment

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

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

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

31. Parameter Files The following are a new set of parameter files for client connections client.pfadmuser.pf editor.pfauditmgruser.pf batch.pfcluser.pf singleuser.pfrptmgruser.pf connect.pf

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

33. Enterprise To start SX.enterprise, now use sxe sxe sxee

34. The Report Manager These are the Report Manager scripts rptmgr.start rptmgr.shut

35. Binary Dump and Load These scripts are for Dump and Loads easybdsareabd bddriver.psareabddriver.p bddumpall.pbddumparea.p bdloadall.pbdloadarea.p bdscript.psareabdscript.p

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

37. Backups These are new standard backup scripts backup.data backup.full backup.online

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

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

40. TWL TWL adds more scripts specific to that product Some TWL scripts are vital for the product to carry out some functions such as: –Transfer of orders to and from SX.enterprise –End Of Day processing

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

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

43. 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

44. TWL Interfaces The following scripts are used to manage the TWL interfaces twlsend.starttwlrcvpack.sh twlsend.shtwlrcv.sh twlsend.shuttwlrcv.shut twlsend.querytwlrcv.query twlrcvprint.sh

45. The Templates MARC generates scripts using templates These templates contain a framework of the script Dynamic portions of the script are filled in by MARC to create the final script MARC fills in the local information based on what is stored in the MARC database and user input

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

47. 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

48. MARC Generated 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

49. 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 MARC Generated Scripts

50. 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 Custom Scripts

51. 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: The convention is to use tag names that are all capital letters

52. 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

53. 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

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

55. Example Template Here is a simple template echo “Hello, world!” Top three lines are reserved for formatting PERMISSIONS is what permissions the script will have SCRIPTNAME is what the script will be called DESTDIR tells where the script will get created

56. Script Naming 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

57. Destinations The destination directory can be a path The destination can be one of these predefined directories BIN OPSYS RD EXEC

58. Building A Script Here is a simple template “helloworld.sh.tpl” echo “Hello, world!” Should be created in the../cust/base directory Generating script to /rd/bin/ses27

59. 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

60. Questions ? ? ? ? ? ? ? ? ? ? ? ?