Difference: BackgroundProcessing (1 vs. 11)

Revision 112016-02-19 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="SystemAdministration"

APPX Background Processing

Line: 20 to 20
  JOB-OUTPUT-001.gif
Changed:
<
<
If the user clicks the 'Submit to BG' button on the Disposition screen, the report will run in background. Alternatively, the Designer coudl set --- SUBMIT PROCESS to Y in the Pre-invocation step of the Output, and the report would always run in background regardless of the user's selection.
>
>
If the user clicks the 'Submit to BG' button on the Disposition screen, the report will run in background. Alternatively, the Designer could set --- SUBMIT PROCESS to Y in the Pre-invocation step of the Output, and the report would always run in background regardless of the user's selection.
 

Setting APPX_BG_SCRIPT

You can customize the processing by setting APPX_BG_SCRIPT to your own script. On Linux/Unix platforms, we recommend copying the existing appx_submit script and changing your copy. If you customize appx_submit directly it will get replaced when you upgrade APPX and you customizations will be lost. On Windows, there is no existing script or batch file, so you will have to create your own. Either way, you must set APPX_BG_SCRIPT to point to your script file. See Setting Environment Variables for more information on settting environment variables. The script is assumed to be in the $APPXPATH folder,

Changed:
<
<
The script will receive 8 arguements: -image, -session, -mode, -notify, -date, -priority, -queue, and -user. In Release 5.4.4 & higher, the script will also receive -options which will contain whatever data is in the --- SUBMIT OPTIONS PDF. This might have been entered by the user on the Submit to Background screen in the 'Submit Options' field, or set by the Designer directly.
>
>
The script will receive 8 arguements: -image, -session, -mode, -notify, -date, -priority, -queue, and -user. In Release 5.4.4 & higher, the script will also receive -options which will contain whatever data is in the --- SUBMIT OPTIONS PDF and -appxuser which contains the 3 character APPX user id. This might have been entered by the user on the Submit to Background screen in the 'Submit Options' field, or set by the Designer directly.
 

Example appx_submit.cmd Windows batch file

The following is an example of a Windows script that will invoke the background job. We are using a .cmd script, but it could a .bat file as well.

Revision 102016-02-12 - JeanNeron

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="APPXAdministrator"

APPX Background Processing on a Windows Server

>
>
META TOPICPARENT name="SystemAdministration"

APPX Background Processing

 
Changed:
<
<
This document will demonstrate the setup of APPX background processing when APPX is installed on a Windows server.
>
>
This document discusses APPX background processing.
 

Overview

Changed:
<
<
Background processes refers to the ability of APPX to spawn another session to run a report or finish other processing. This will free the foreground session immediately and allow the user to do something else. If you run somethign in backgroud that requires any user interaction, APPX wil behave as if the user pressed the END key.

Steps

APPX Designer

  • Modify the JOB's OUTPUT process type to have Separate Task (Sep. Task) checked as shown in the figure below.
  • JOB-OUTPUT-001.gif

APPX Server

If all you wish to do is submit an APPX JOB's OUTPUT process to the background, you do not need to set the APPX_BG_SCRIPT environment variable, nor do you need to have an appx_submit.cmd batch file. If however you wish to take specific action based on one of the arguments APPX passes to the appx_submit.cmd script , then you should set APPX_BG_SCRIPT=appx_submit.cmd and create an appx_submit.cmd file that can act on the 8 argument pairs that are past. They are (-image, -session, -mode, -notify, -date, -priority, -queue, and -user) These configuration files (appx.env file containing APPX_BG_SCRIPT environment variable, and appx_submit.cmd batch script) need to be placed on the APPX Windows server.

  • Place the following inside your appx.env file, which should be in %APPXPATH or C:\Appx\data\appx.env
>
>
Background processes refers to the ability of APPX to spawn another session to run a report or finish other processing. This will free the foreground session immediately and allow the user to do something else. If you run something in background that requires any user interaction, APPX wil behave as if the user pressed the END key. This is true on all Linux/Unix platforms, but in some versions of APPX on Windows the background process will hang waiting for user input, therefore on Windows platforms you should ensure your backgound job does not require any user input.
 
Changed:
<
<
APPX_BG_SCRIPT=appx_submit.cmd
>
>
Before a job or process can be run in background the designer must check the 'Separate Task' flag on the job step. Without this setting the job will always run in foreground, regardless of anything else. NOTE: A side effect of checking this flag is that you cannot get any values back from the job or process, even if it is run in foreground.

Next, either the user has to request background processing on the Disposition screen by clicking the 'Submit to BG' button or the Designer can set --- SUBMIT PROCESS to Y in the Pre-Invocation Event Point. There are other --- SUBMIT fields available, but those are intended for use with any 3rd party job queue managers, APPX does not use them.

On Linux/Unix platforms, APPX runs the appx_submit script to invoke a background job. This script in in the $APPXPATH folder. On Windows platforms, the engine invokes the background session directly without using a script or batch file. If you want APPX to use a script on Windows so that you can customize the behaviour, set the APPX_BG_SCRIPT environment variable (see below).

On all platforms the engine will spawn another APPX session, passing the -session flag. This flag points to a temporary file that contains the context, i.e., any open files, any work fields and anything the background session needs to continue processing.

APPX Designer

For example, we can modify the SALESREP LISTING job in DMO by checking the 'Sep. Task' option:

JOB-OUTPUT-001.gif

If the user clicks the 'Submit to BG' button on the Disposition screen, the report will run in background. Alternatively, the Designer coudl set --- SUBMIT PROCESS to Y in the Pre-invocation step of the Output, and the report would always run in background regardless of the user's selection.

Setting APPX_BG_SCRIPT

You can customize the processing by setting APPX_BG_SCRIPT to your own script. On Linux/Unix platforms, we recommend copying the existing appx_submit script and changing your copy. If you customize appx_submit directly it will get replaced when you upgrade APPX and you customizations will be lost. On Windows, there is no existing script or batch file, so you will have to create your own. Either way, you must set APPX_BG_SCRIPT to point to your script file. See Setting Environment Variables for more information on settting environment variables. The script is assumed to be in the $APPXPATH folder,

 
Changed:
<
<

The appx_submit.cmd Windows batch file

>
>
The script will receive 8 arguements: -image, -session, -mode, -notify, -date, -priority, -queue, and -user. In Release 5.4.4 & higher, the script will also receive -options which will contain whatever data is in the --- SUBMIT OPTIONS PDF. This might have been entered by the user on the Submit to Background screen in the 'Submit Options' field, or set by the Designer directly.

Example appx_submit.cmd Windows batch file

 
Changed:
<
<
The appx_submit.cmd file is a Windows batch file that you can parse the 8 argument pairs that APPX passes it.
  • The appx_submit.cmd command should contain
>
>
The following is an example of a Windows script that will invoke the background job. We are using a .cmd script, but it could a .bat file as well.
 
Changed:
<
<
::APPX_SUBMIT.CMD
:: A Typical Argument list will be 8 Arguments passed from APPX

>
>
::APPX_SUBMIT.CMD
:: A Typical Argument list will be 8 Arguments passed from APPX

 :: -image, -session, -mode, -notify, -date, -priority, -queue, and -user :: Windows will break on the equals sign giving us 16 arguments in total :: We will ignore all but the -image and -session pairs to submit
Line: 64 to 70
 %2 %3=%4
Changed:
<
<

APPX Run Time

  • On the JOB's output disposition screen select SUBMIT to BG.
  • JOB-OUTPUT-002.gif
  • NOTE: If you do not wish to present a Disposition screen, you can specify background processing in ILF code:
    • SET --- SUBMIT PROCESS = Y

Bugs:

  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.

Comments:

>
>

Comments:

  Read what other users have said about this page or add your own comments.
Line: 81 to 79
 
META FILEATTACHMENT attachment="JOB-OUTPUT-001.gif" attr="" comment="JOB OUTPUT - Notice the Sep. Task value is checked." date="1236715995" name="JOB-OUTPUT-001.gif" path="JOB-OUTPUT-001.gif" size="39785" stream="JOB-OUTPUT-001.gif" user="Main.JoeOrtagus" version="2"
META FILEATTACHMENT attachment="JOB-OUTPUT-002.gif" attr="" comment="JOB OUTPUT - Notice Submit to BG button" date="1236716030" name="JOB-OUTPUT-002.gif" path="JOB-OUTPUT-002.gif" size="24911" stream="JOB-OUTPUT-002.gif" user="Main.JoeOrtagus" version="1"
Added:
>
>
META TOPICMOVED by="JeanNeron" date="1455301986" from="Main.SubmittingAJobToTheBackgroundInAPPXOnWindowsServers" to="Main.BackgroundProcessing"

Revision 92016-02-12 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Background Processing on a Windows Server

Changed:
<
<
This document will demonstrate the setup of APPX background processing when APPX is installed on a Windows server.
>
>
This document will demonstrate the setup of APPX background processing when APPX is installed on a Windows server.
 

Overview

Changed:
<
<
JOB is the only APPX process type you can make available for back ground processing. At the end of this document you will have made all the demo (DMO) JOB output reports candidates for background processing.

Required software components

APPX Desktop Client

  • You can get the APPX Desktop Client from here.

APPX Server

  • You need a functioning APPX installation. Follow instructions in this document to install APPX on Windows if you don't already have APPX installed.
  • You should also have the variable APPX_BG_SCRIPT=appx_submit.cmd. You can place this variable setting inside your appx.env file. The appx.env file should go into your %APPXPATH directory (C:\Appx\data\appx.env)

DMO Demo APPX Application

DMO is demonstration application that is included with APPX on default installations.

>
>
Background processes refers to the ability of APPX to spawn another session to run a report or finish other processing. This will free the foreground session immediately and allow the user to do something else. If you run somethign in backgroud that requires any user interaction, APPX wil behave as if the user pressed the END key.
 

Steps

APPX Designer

  • Modify the JOB's OUTPUT process type to have Separate Task (Sep. Task) checked as shown in the figure below.
Line: 23 to 13
 

APPX Server

If all you wish to do is submit an APPX JOB's OUTPUT process to the background, you do not need to set the APPX_BG_SCRIPT environment variable, nor do you need to have an appx_submit.cmd batch file. If however you wish to take specific action based on one of the arguments APPX passes to the appx_submit.cmd script , then you should set APPX_BG_SCRIPT=appx_submit.cmd and create an appx_submit.cmd file that can act on the 8 argument pairs that are past. They are (-image, -session, -mode, -notify, -date, -priority, -queue, and -user) These configuration files (appx.env file containing APPX_BG_SCRIPT environment variable, and appx_submit.cmd batch script) need to be placed on the APPX Windows server.

Changed:
<
<

The appx.env file.

The appx.env file is a file that is referenced by all appx processes. The file contains environment variables that you want to be present for APPX sessions. Any line that starts with # is a comment line and is not used by APPX. The other lines have a syntax of VARIABLE=VALUE, where VARIABLE is an environment variable such as APPXPATH, and VALUE is the text that you want to assign to the variable, such as C:\Appx\Data. Here is an example appx.env file.

###############################################################################
#
#  APPX Configuration File
#  -----------------------
#
#  This file can be used to configure your APPX environment.  Upon startup, 
#  APPX will read this environment file, then it will look for an environment 
#  file in the user's home directory (or c:\ for Windows) for any overrides.
#
#  Comments are denoted by a leading "#" symbol, blank lines, and
#  lines not containing an = symbol.  The only exception is an "include"
#  which looks like this:
#
#  include=/etc/appx.env
#
#  The following file contains a list of the valid environment settings that
#  can be used with APPX.  To active any of these settings just remove the
#  comment symbol from the first column and then make any edits needed to the
#  environment variable value.
#
#  For this release, no substitution or expansion is done.  Every value is
#  taken as a literal value.
#
##############################################################################

#=============================================================================
#  GENERAL BASE CONFIGURATION SECTION
#=============================================================================

#  APPXPATH can be set here.  The default path is the APPX executable location
#  appended with a "data" subdirectory.
#
#APPXPATH=

#  APPX_MSG can be set to display a constant text message at the bottom of all 
#  of the APPX screens during an APPX session.
#
#APPX_MSG=Message text goes here

#  APPX_KEYMAP can be set to the name of the default keymap you would like to 
#  load.  This is the same as using the -m= command line option.
#
#APPX_KEYMAP=vt320-k

#  APPX_SHOW_PROGRESS will activate a running status message during Query
#  and related Output and Update processes.  This message will keep you
#  informed as to the progress of the batch process.  Number of records
#  processed, number of records selected, etc.  The message is updated
#  every record until it reaches 10, then it updates every 10 records
#  until it reaches 100, then it is updated every 100 records, etc.
#
#APPX_SHOW_PROGRESS=true

#  APPX_MAX_FILES will set the maximum number of physically open files
#  APPX can have open during an APPX session. If APPX tries to open more
#  files than this, it will start closing stale files that have no
#  records locked to make way for new files. If an closed file is
#  required to do I/O, it will automatically be re-opened without the
#  Application knowing anything has happened. We call this Open File
#  Descriptor Caching.
#
#APPX_MAX_FILES=80 

#  APPX_PIVOT_YEAR controls how APPX will "synthesize" the century
#  component of date fields.  "Synthesizing" a century is the process of
#  defaulting it based upon the two digit year and the pivot year value,
#  when the century is not explicitly available.  See the y2k Implementation
#  Guide for details.  Pivot year is implemented in APPX release 3.2.83
#  and greater.  By default, pivot year logic is disabled.  It is enabled
#  by setting this variable.
#
#APPX_PIVOT_YEAR=50

#=============================================================================
#  PRINTING AND JOB SUBMISSION CONFIGURATION SECTION
#=============================================================================

#  APPX_PRT_FI_DIR is used to set the disk location for creating print files
#  on your system.  The default location in unix is /tmp/.  The default 
#  location in Windows is $APPXPATH\print\{userID} #
#APPX_PRT_FI_DIR=/tmp/

#  APPX_PRT_SCRIPT points to the name of the script used to spool APPX reports
#  to a print device or queue manager.  The default is appx_print in the
#  APPXPATH directory.
#
#APPX_PRT_SCRIPT=appx_print

#  APPX_BG_SCRIPT points to the name used to submit batch jobs into background
#  or a job scheduling system.  The default is appx_submit.
#
# APPX_BG_SCRIPT=appx_submit.cmd

#=============================================================================
#  KEA INTERFACE CONFIGURATION SECTION
#============================================================================

#  APPX_KEYMAP can be set to the name of the default keymap you would like to 
#  load.  This is the same as using the -m= command line option.
#
#APPX_KEYMAP=keaterm

#  APPX_KEATERM controls how APPX talks to the KEA Terminal emulation package.
#
#APPX_KEATERM=Buttons
#APPX_KEATERM=NoButtons

#=============================================================================
#  SCRIPTING & REGRESSION TESTING CONFIGURATION SECTION
#=============================================================================

#  APPX_SCRIPT_OUT will record all enduser keystrokes (and selected 
#  Processes executed in the program flow) into an output file.  This 
#  file is quite readable, and is editable for the use of APPX_SCRIPT_IN 
#  (described below).  It is initialized upon entering APPX.  It is not 
#  populated until APPX is successfully exited.
#
#APPX_SCRIPT_OUT=/tmp/appx.script

#  APPX_SCRIPT_IN will "play back" all keystrokes recorded in it, 
#  into the invocation of the APPX engine, as if the enduser had 
#  manually pressed these keys.
#
#APPX_SCRIPT_IN=/tmp/appx.script

#  APPX_SCRIPT_STEP if set will cause APPX to pause before each APPX OPTION
#  key is sent from the script.  While paused, you can press certain keys
#  to do special processing.  Here is a list of the actions and keys that
#  work while you are paused.
#
#  c = continue running remainder of script without stepping.
#  p = pause and you take over the keyboard until you press ^r
#  e = terminate script playback and take control of the session.
#
#  any other key will step forward in the script until the next APPX OPTION
#  key is encountered in the script and then it will pause again.
#
#APPX_SCRIPT_STEP=true

#  APPX_TST_DIR points to a directory to capture screen images.  If this is
#  set, APPX will record every screen image it comes to into this location.
#  If you are running with APPX_SCRIPT_OUT set, then it will store the
#  images in a subdirectory of "expect" and if you are running with
#  APPX_SCRIPT_IN set, then they will be stored in a subdirectory of
#  "actual".  The screens themselves will be saved with a file name starting
#  with "screen000" and incrementing the last three digits.
#
#APPX_TST_DIR=/tmp

#=============================================================================
#  DESIGNER AIDS CONFIGURATION SECTION
#=============================================================================

#  APPX_DB_TRAPS when set will cause APPX to stop for TRAPs regardless
#  of who is running a process or how the process was started.  Without
#  this set, APPX will only execute traps when a process was started
#  from within Application Design.
#
#APPX_DB_TRAPS=true

#  APPX_PORTABLE_DATE when set will force the Import/Export utility to 
#  hide the bad_portable_date error that can sometimes come up quite
#  often when dealing with data from a SpeedII migration.  Speed would
#  allow you to store invalid dates in a date field via ILF code where
#  APPX will reject any invalid date during import.
#
#APPX_PORTABLE_DATE=true
  
#=============================================================================
#  VISION DATABASE CONFIGURATION SECTION
#=============================================================================

#  APPX_PD_SIGNS will tell APPX what byte pattern to use for the sign bits
#  of packed decimal numbers.  The default is "CD" which is how APPX
#  is normally distributed.  Vision uses a default of "FD" which can be
#  overridden when the vision programs are compiled.  This setting also
#  affects the APPX EMs which store some packed decimal information.  This
#  setting also affects files stored as native APPX files.  So, to use this
#  setting of "FD", you must install a special set of APPX internal EMs,
#  and if you have and existing data in "CD" format, you must export the
#  data, set the APPX_PD_SIGNS=FD, then import.
#  
#APPX_PD_SIGNS=FD

#=============================================================================
#  APPX FOR WINDOWS CONFIGURATION SECTION
#=============================================================================

#  APPX_0SA_PATH will tell APPX to look at this path for its System 
#  Administration files.  This is handy for running several copies
#  of APPX on networked PCs while sharing one common set of System
#  Administration settings.
#
#  You can also store shared design files on a common shared drive while
#  storing local copies of all of the EMs on a local drive.  To do this,
#  you create a FMS group for your design files and set the FMS Path to
#  the shared location while setting the FMS Controls fields to the local
#  path for storing EMs.
#
#  FMS Path     [r:\appx\data           ]
#  FMS Controls [EM=c:\appx\data        ]
#
#APPX_0SA_PATH=r:\appx\data

#=============================================================================
#  TECH SUPPORT DEBUGGING CONFIGURATION SECTION
#=============================================================================

#  APPX_UNIXIO_STATS and APPX_UNIXIO_PROCS work together to help 
#  debug file access and performance problems.  If you set APPX_UNIXIO_STATS
#  to a log file name, Appx will log all file i/o's performed.  The
#  format of the report is:
#    open_count read_count readnext_count start_count write_count rewrite_count filename
#  The statistics are written as each file is closed so if a file is closed and 
#  reopened, it will appear more than once in the log file.
#
#  Setting APPX_UNIXIO_PROCS will cause Appx to include the current process name
#  in the logfile.
#
#APPX_UNIXIO_STATS=/tmp/file_stats
#APPX_UNIXIO_PROCS=1
>
>

 
  • Place the following inside your appx.env file, which should be in %APPXPATH or C:\Appx\data\appx.env
Deleted:
<
<
 
APPX_BG_SCRIPT=appx_submit.cmd

Changed:
<
<
>
>
 

The appx_submit.cmd Windows batch file

The appx_submit.cmd file is a Windows batch file that you can parse the 8 argument pairs that APPX passes it.

  • The appx_submit.cmd command should contain
Deleted:
<
<
 
::APPX_SUBMIT.CMD
:: A Typical Argument list will be 8 Arguments passed from APPX

Line: 302 to 62
 ::

%2 %3=%4

Changed:
<
<
>
>
 

APPX Run Time

  • On the JOB's output disposition screen select SUBMIT to BG.
Line: 310 to 70
 
  • NOTE: If you do not wish to present a Disposition screen, you can specify background processing in ILF code:
    • SET --- SUBMIT PROCESS = Y

Bugs:

Changed:
<
<
  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.
>
>
  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.
 

Comments:

Read what other users have said about this page or add your own comments.


Changed:
<
<
<--/commentPlugin-->
-- JoeOrtagus - 10 Mar 2009
>
>

<--/commentPlugin-->
-- JoeOrtagus - 10 Mar 2009
 
META FILEATTACHMENT attachment="JOB-OUTPUT-001.gif" attr="" comment="JOB OUTPUT - Notice the Sep. Task value is checked." date="1236715995" name="JOB-OUTPUT-001.gif" path="JOB-OUTPUT-001.gif" size="39785" stream="JOB-OUTPUT-001.gif" user="Main.JoeOrtagus" version="2"
META FILEATTACHMENT attachment="JOB-OUTPUT-002.gif" attr="" comment="JOB OUTPUT - Notice Submit to BG button" date="1236716030" name="JOB-OUTPUT-002.gif" path="JOB-OUTPUT-002.gif" size="24911" stream="JOB-OUTPUT-002.gif" user="Main.JoeOrtagus" version="1"

Revision 82013-07-24 - AlKalter

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Background Processing on a Windows Server

Added:
>
>
 This document will demonstrate the setup of APPX background processing when APPX is installed on a Windows server.

Overview

Line: 16 to 19
 

Steps

APPX Designer

  • Modify the JOB's OUTPUT process type to have Separate Task (Sep. Task) checked as shown in the figure below.
Changed:
<
<
  • JOB-OUTPUT-001.gif
>
>
  • JOB-OUTPUT-001.gif
 

APPX Server

Changed:
<
<
If all you wish to do is submit an APPX JOB's OUTPUT process to the background, you do not need to set the APPX_BG_SCRIPT environment variable, nor do you need to have an appx_submit.cmd batch file. If however you wish to take specific action based on one of the arguments APPX passes to the appx_submit.cmd script , then you should set APPX_BG_SCRIPT=appx_submit.cmd and create an appx_submit.cmd file that can act on the 8 argument pairs that are past. They are (-image, -session, -mode, -notify, -date, -priority, -queue, and -user) These configuration files (appx.env file containing APPX_BG_SCRIPT environment variable, and appx_submit.cmd batch script) need to be placed on the APPX Windows server.
>
>
If all you wish to do is submit an APPX JOB's OUTPUT process to the background, you do not need to set the APPX_BG_SCRIPT environment variable, nor do you need to have an appx_submit.cmd batch file. If however you wish to take specific action based on one of the arguments APPX passes to the appx_submit.cmd script , then you should set APPX_BG_SCRIPT=appx_submit.cmd and create an appx_submit.cmd file that can act on the 8 argument pairs that are past. They are (-image, -session, -mode, -notify, -date, -priority, -queue, and -user) These configuration files (appx.env file containing APPX_BG_SCRIPT environment variable, and appx_submit.cmd batch script) need to be placed on the APPX Windows server.
 

The appx.env file.

Changed:
<
<
The appx.env file is a file that is referenced by all appx processes. The file contains environment variables that you want to be present for APPX sessions. Any line that starts with # is a comment line and is not used by APPX. The other lines have a syntax of VARIABLE=VALUE, where VARIABLE is an environment variable such as APPXPATH, and VALUE is the text that you want to assign to the variable, such as C:\Appx\Data. Here is an example appx.env file.
>
>
The appx.env file is a file that is referenced by all appx processes. The file contains environment variables that you want to be present for APPX sessions. Any line that starts with # is a comment line and is not used by APPX. The other lines have a syntax of VARIABLE=VALUE, where VARIABLE is an environment variable such as APPXPATH, and VALUE is the text that you want to assign to the variable, such as C:\Appx\Data. Here is an example appx.env file.
 
Changed:
<
<
###############################################################################

>
>
###############################################################################

 # # APPX Configuration File # -----------------------
Line: 135 to 137
 #APPX_KEATERM=NoButtons

#=============================================================================

Changed:
<
<
# SCRIPTING & REGRESSION TESTING CONFIGURATION SECTION
>
>
# SCRIPTING & REGRESSION TESTING CONFIGURATION SECTION
 #=============================================================================

# APPX_SCRIPT_OUT will record all enduser keystrokes (and selected

Line: 248 to 250
 # #APPX_UNIXIO_STATS=/tmp/file_stats #APPX_UNIXIO_PROCS=1
Changed:
<
<
>
>
 
  • Place the following inside your appx.env file, which should be in %APPXPATH or C:\Appx\data\appx.env
Changed:
<
<
APPX_BG_SCRIPT=appx_submit.cmd
>
>
APPX_BG_SCRIPT=appx_submit.cmd
 

The appx_submit.cmd Windows batch file

Added:
>
>
 The appx_submit.cmd file is a Windows batch file that you can parse the 8 argument pairs that APPX passes it.
  • The appx_submit.cmd command should contain
Line: 264 to 264
 
  • The appx_submit.cmd command should contain
Changed:
<
<
::APPX_SUBMIT.CMD

>
>
::APPX_SUBMIT.CMD

 :: A Typical Argument list will be 8 Arguments passed from APPX :: -image, -session, -mode, -notify, -date, -priority, -queue, and -user :: Windows will break on the equals sign giving us 16 arguments in total
Line: 303 to 302
 ::

%2 %3=%4

Changed:
<
<
>
>
 

APPX Run Time

  • On the JOB's output disposition screen select SUBMIT to BG.
Changed:
<
<
  • JOB-OUTPUT-002.gif
>
>
  • JOB-OUTPUT-002.gif
  • NOTE: If you do not wish to present a Disposition screen, you can specify background processing in ILF code:
    • SET --- SUBMIT PROCESS = Y
 

Bugs:

Changed:
<
<
  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.
>
>
  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.
 

Comments:

Added:
>
>
 Read what other users have said about this page or add your own comments.
Changed:
<
<
<--/commentPlugin-->
-- JoeOrtagus - 10 Mar 2009
>
>
<--/commentPlugin-->
-- JoeOrtagus - 10 Mar 2009
 
META FILEATTACHMENT attachment="JOB-OUTPUT-001.gif" attr="" comment="JOB OUTPUT - Notice the Sep. Task value is checked." date="1236715995" name="JOB-OUTPUT-001.gif" path="JOB-OUTPUT-001.gif" size="39785" stream="JOB-OUTPUT-001.gif" user="Main.JoeOrtagus" version="2"
META FILEATTACHMENT attachment="JOB-OUTPUT-002.gif" attr="" comment="JOB OUTPUT - Notice Submit to BG button" date="1236716030" name="JOB-OUTPUT-002.gif" path="JOB-OUTPUT-002.gif" size="24911" stream="JOB-OUTPUT-002.gif" user="Main.JoeOrtagus" version="1"

Revision 72012-04-05 - BredaHennessy

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Background Processing on a Windows Server

This document will demonstrate the setup of APPX background processing when APPX is installed on a Windows server.
Line: 203 to 203
 # of packed decimal numbers. The default is "CD" which is how APPX # is normally distributed. Vision uses a default of "FD" which can be # overridden when the vision programs are compiled. This setting also
Changed:
<
<
# effects the APPX EMs which store some packed decimal information. This # setting also effects files stored as native APPX files. So, to use this
>
>
# affects the APPX EMs which store some packed decimal information. This # setting also affects files stored as native APPX files. So, to use this
 # setting of "FD", you must install a special set of APPX internal EMs, # and if you have and existing data in "CD" format, you must export the # data, set the APPX_PD_SIGNS=FD, then import.
Line: 215 to 215
 # APPX FOR WINDOWS CONFIGURATION SECTION #=============================================================================
Changed:
<
<
# APPX_0SA_PATH will tell APPX to look at this path for it's System
>
>
# APPX_0SA_PATH will tell APPX to look at this path for its System
 # Administration files. This is handy for running several copies # of APPX on networked PCs while sharing one common set of System # Administration settings.
Line: 280 to 280
 :: echo %%A >> c:\Appx\arglist.txt :: )
Changed:
<
<
:: You would likekly see something like this in arglist.txt
>
>
:: You would likely see something like this in arglist.txt
 :: -image :: C:\Appx\Appx.exe :: -session

Revision 62009-03-10 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"
Deleted:
<
<
 

APPX Background Processing on a Windows Server

Changed:
<
<
This document will APPX background processing when APPX is installed on a Windows server.
>
>
This document will demonstrate the setup of APPX background processing when APPX is installed on a Windows server.
 

Overview

JOB is the only APPX process type you can make available for back ground processing. At the end of this document you will have made all the demo (DMO) JOB output reports candidates for background processing.
Line: 19 to 18
 
  • Modify the JOB's OUTPUT process type to have Separate Task (Sep. Task) checked as shown in the figure below.
  • JOB-OUTPUT-001.gif

APPX Server

Changed:
<
<
This configuration needs to be done to files placed on the APPX Windows server.
>
>
If all you wish to do is submit an APPX JOB's OUTPUT process to the background, you do not need to set the APPX_BG_SCRIPT environment variable, nor do you need to have an appx_submit.cmd batch file. If however you wish to take specific action based on one of the arguments APPX passes to the appx_submit.cmd script , then you should set APPX_BG_SCRIPT=appx_submit.cmd and create an appx_submit.cmd file that can act on the 8 argument pairs that are past. They are (-image, -session, -mode, -notify, -date, -priority, -queue, and -user) These configuration files (appx.env file containing APPX_BG_SCRIPT environment variable, and appx_submit.cmd batch script) need to be placed on the APPX Windows server.
 

The appx.env file.

The appx.env file is a file that is referenced by all appx processes. The file contains environment variables that you want to be present for APPX sessions. Any line that starts with # is a comment line and is not used by APPX. The other lines have a syntax of VARIABLE=VALUE, where VARIABLE is an environment variable such as APPXPATH, and VALUE is the text that you want to assign to the variable, such as C:\Appx\Data. Here is an example appx.env file.

Revision 52009-03-10 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"
Added:
>
>
 

APPX Background Processing on a Windows Server

This document will APPX background processing when APPX is installed on a Windows server.
Line: 13 to 14
 
  • You should also have the variable APPX_BG_SCRIPT=appx_submit.cmd. You can place this variable setting inside your appx.env file. The appx.env file should go into your %APPXPATH directory (C:\Appx\data\appx.env)

DMO Demo APPX Application

DMO is demonstration application that is included with APPX on default installations.
Changed:
<
<

Quick steps

>
>

Steps

 

APPX Designer

Changed:
<
<
  • Modify the JOB's OUTPUT process type to have Separate Task (Sep. Task) checked.
>
>
  • Modify the JOB's OUTPUT process type to have Separate Task (Sep. Task) checked as shown in the figure below.
  • JOB-OUTPUT-001.gif
 

APPX Server

This configuration needs to be done to files placed on the APPX Windows server.

The appx.env file.

Line: 104 to 106
  # APPX_PRT_FI_DIR is used to set the disk location for creating print files # on your system. The default location in unix is /tmp/. The default
Changed:
<
<
# location in Windows is $APPXPATH\print\{userID}#
>
>
# location in Windows is $APPXPATH\print\{userID} #
 #APPX_PRT_FI_DIR=/tmp/

# APPX_PRT_SCRIPT points to the name of the script used to spool APPX reports

Line: 134 to 135
 #APPX_KEATERM=NoButtons

#=============================================================================

Changed:
<
<
# SCRIPTING & REGRESSION TESTING CONFIGURATION SECTION
>
>
# SCRIPTING & REGRESSION TESTING CONFIGURATION SECTION
 #=============================================================================

# APPX_SCRIPT_OUT will record all enduser keystrokes (and selected

Line: 258 to 258
 APPX_BG_SCRIPT=appx_submit.cmd
Added:
>
>

The appx_submit.cmd Windows batch file

The appx_submit.cmd file is a Windows batch file that you can parse the 8 argument pairs that APPX passes it.
 
  • The appx_submit.cmd command should contain
Line: 274 to 277
 :: following loop:

:: FOR %%A IN (%*) DO (

Changed:
<
<
:: echo %%A >> c:\Appx\arglist.txt
>
>
:: echo %%A >> c:\Appx\arglist.txt
 :: )

:: You would likekly see something like this in arglist.txt

Line: 303 to 306
 

APPX Run Time

Changed:
<
<
  • On the JOB's output disposition screen select SUBMIT to BG

>
>
  • On the JOB's output disposition screen select SUBMIT to BG.
  • JOB-OUTPUT-002.gif
 

Bugs:

  1. Fixed - Bug Description 1.
Line: 315 to 317
 
<--/commentPlugin-->
-- JoeOrtagus - 10 Mar 2009 \ No newline at end of file
Added:
>
>
META FILEATTACHMENT attachment="JOB-OUTPUT-001.gif" attr="" comment="JOB OUTPUT - Notice the Sep. Task value is checked." date="1236715995" name="JOB-OUTPUT-001.gif" path="JOB-OUTPUT-001.gif" size="39785" stream="JOB-OUTPUT-001.gif" user="Main.JoeOrtagus" version="2"
META FILEATTACHMENT attachment="JOB-OUTPUT-002.gif" attr="" comment="JOB OUTPUT - Notice Submit to BG button" date="1236716030" name="JOB-OUTPUT-002.gif" path="JOB-OUTPUT-002.gif" size="24911" stream="JOB-OUTPUT-002.gif" user="Main.JoeOrtagus" version="1"

Revision 42009-03-10 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Background Processing on a Windows Server

This document will APPX background processing when APPX is installed on a Windows server.
Line: 17 to 17
 

APPX Designer

  • Modify the JOB's OUTPUT process type to have Separate Task (Sep. Task) checked.

APPX Server

Added:
>
>
This configuration needs to be done to files placed on the APPX Windows server.

The appx.env file.

The appx.env file is a file that is referenced by all appx processes. The file contains environment variables that you want to be present for APPX sessions. Any line that starts with # is a comment line and is not used by APPX. The other lines have a syntax of VARIABLE=VALUE, where VARIABLE is an environment variable such as APPXPATH, and VALUE is the text that you want to assign to the variable, such as C:\Appx\Data. Here is an example appx.env file.

###############################################################################
#
#  APPX Configuration File
#  -----------------------
#
#  This file can be used to configure your APPX environment.  Upon startup, 
#  APPX will read this environment file, then it will look for an environment 
#  file in the user's home directory (or c:\ for Windows) for any overrides.
#
#  Comments are denoted by a leading "#" symbol, blank lines, and
#  lines not containing an = symbol.  The only exception is an "include"
#  which looks like this:
#
#  include=/etc/appx.env
#
#  The following file contains a list of the valid environment settings that
#  can be used with APPX.  To active any of these settings just remove the
#  comment symbol from the first column and then make any edits needed to the
#  environment variable value.
#
#  For this release, no substitution or expansion is done.  Every value is
#  taken as a literal value.
#
##############################################################################

#=============================================================================
#  GENERAL BASE CONFIGURATION SECTION
#=============================================================================

#  APPXPATH can be set here.  The default path is the APPX executable location
#  appended with a "data" subdirectory.
#
#APPXPATH=

#  APPX_MSG can be set to display a constant text message at the bottom of all 
#  of the APPX screens during an APPX session.
#
#APPX_MSG=Message text goes here

#  APPX_KEYMAP can be set to the name of the default keymap you would like to 
#  load.  This is the same as using the -m= command line option.
#
#APPX_KEYMAP=vt320-k

#  APPX_SHOW_PROGRESS will activate a running status message during Query
#  and related Output and Update processes.  This message will keep you
#  informed as to the progress of the batch process.  Number of records
#  processed, number of records selected, etc.  The message is updated
#  every record until it reaches 10, then it updates every 10 records
#  until it reaches 100, then it is updated every 100 records, etc.
#
#APPX_SHOW_PROGRESS=true

#  APPX_MAX_FILES will set the maximum number of physically open files
#  APPX can have open during an APPX session. If APPX tries to open more
#  files than this, it will start closing stale files that have no
#  records locked to make way for new files. If an closed file is
#  required to do I/O, it will automatically be re-opened without the
#  Application knowing anything has happened. We call this Open File
#  Descriptor Caching.
#
#APPX_MAX_FILES=80 

#  APPX_PIVOT_YEAR controls how APPX will "synthesize" the century
#  component of date fields.  "Synthesizing" a century is the process of
#  defaulting it based upon the two digit year and the pivot year value,
#  when the century is not explicitly available.  See the y2k Implementation
#  Guide for details.  Pivot year is implemented in APPX release 3.2.83
#  and greater.  By default, pivot year logic is disabled.  It is enabled
#  by setting this variable.
#
#APPX_PIVOT_YEAR=50

#=============================================================================
#  PRINTING AND JOB SUBMISSION CONFIGURATION SECTION
#=============================================================================

#  APPX_PRT_FI_DIR is used to set the disk location for creating print files
#  on your system.  The default location in unix is /tmp/.  The default 
#  location in Windows is $APPXPATH\print\{userID}\
#
#APPX_PRT_FI_DIR=/tmp/

#  APPX_PRT_SCRIPT points to the name of the script used to spool APPX reports
#  to a print device or queue manager.  The default is appx_print in the
#  APPXPATH directory.
#
#APPX_PRT_SCRIPT=appx_print

#  APPX_BG_SCRIPT points to the name used to submit batch jobs into background
#  or a job scheduling system.  The default is appx_submit.
#
# APPX_BG_SCRIPT=appx_submit.cmd

#=============================================================================
#  KEA INTERFACE CONFIGURATION SECTION
#============================================================================

#  APPX_KEYMAP can be set to the name of the default keymap you would like to 
#  load.  This is the same as using the -m= command line option.
#
#APPX_KEYMAP=keaterm

#  APPX_KEATERM controls how APPX talks to the KEA Terminal emulation package.
#
#APPX_KEATERM=Buttons
#APPX_KEATERM=NoButtons

#=============================================================================
#  SCRIPTING & REGRESSION TESTING CONFIGURATION SECTION
#=============================================================================

#  APPX_SCRIPT_OUT will record all enduser keystrokes (and selected 
#  Processes executed in the program flow) into an output file.  This 
#  file is quite readable, and is editable for the use of APPX_SCRIPT_IN 
#  (described below).  It is initialized upon entering APPX.  It is not 
#  populated until APPX is successfully exited.
#
#APPX_SCRIPT_OUT=/tmp/appx.script

#  APPX_SCRIPT_IN will "play back" all keystrokes recorded in it, 
#  into the invocation of the APPX engine, as if the enduser had 
#  manually pressed these keys.
#
#APPX_SCRIPT_IN=/tmp/appx.script

#  APPX_SCRIPT_STEP if set will cause APPX to pause before each APPX OPTION
#  key is sent from the script.  While paused, you can press certain keys
#  to do special processing.  Here is a list of the actions and keys that
#  work while you are paused.
#
#  c = continue running remainder of script without stepping.
#  p = pause and you take over the keyboard until you press ^r
#  e = terminate script playback and take control of the session.
#
#  any other key will step forward in the script until the next APPX OPTION
#  key is encountered in the script and then it will pause again.
#
#APPX_SCRIPT_STEP=true

#  APPX_TST_DIR points to a directory to capture screen images.  If this is
#  set, APPX will record every screen image it comes to into this location.
#  If you are running with APPX_SCRIPT_OUT set, then it will store the
#  images in a subdirectory of "expect" and if you are running with
#  APPX_SCRIPT_IN set, then they will be stored in a subdirectory of
#  "actual".  The screens themselves will be saved with a file name starting
#  with "screen000" and incrementing the last three digits.
#
#APPX_TST_DIR=/tmp

#=============================================================================
#  DESIGNER AIDS CONFIGURATION SECTION
#=============================================================================

#  APPX_DB_TRAPS when set will cause APPX to stop for TRAPs regardless
#  of who is running a process or how the process was started.  Without
#  this set, APPX will only execute traps when a process was started
#  from within Application Design.
#
#APPX_DB_TRAPS=true

#  APPX_PORTABLE_DATE when set will force the Import/Export utility to 
#  hide the bad_portable_date error that can sometimes come up quite
#  often when dealing with data from a SpeedII migration.  Speed would
#  allow you to store invalid dates in a date field via ILF code where
#  APPX will reject any invalid date during import.
#
#APPX_PORTABLE_DATE=true
  
#=============================================================================
#  VISION DATABASE CONFIGURATION SECTION
#=============================================================================

#  APPX_PD_SIGNS will tell APPX what byte pattern to use for the sign bits
#  of packed decimal numbers.  The default is "CD" which is how APPX
#  is normally distributed.  Vision uses a default of "FD" which can be
#  overridden when the vision programs are compiled.  This setting also
#  effects the APPX EMs which store some packed decimal information.  This
#  setting also effects files stored as native APPX files.  So, to use this
#  setting of "FD", you must install a special set of APPX internal EMs,
#  and if you have and existing data in "CD" format, you must export the
#  data, set the APPX_PD_SIGNS=FD, then import.
#  
#APPX_PD_SIGNS=FD

#=============================================================================
#  APPX FOR WINDOWS CONFIGURATION SECTION
#=============================================================================

#  APPX_0SA_PATH will tell APPX to look at this path for it's System 
#  Administration files.  This is handy for running several copies
#  of APPX on networked PCs while sharing one common set of System
#  Administration settings.
#
#  You can also store shared design files on a common shared drive while
#  storing local copies of all of the EMs on a local drive.  To do this,
#  you create a FMS group for your design files and set the FMS Path to
#  the shared location while setting the FMS Controls fields to the local
#  path for storing EMs.
#
#  FMS Path     [r:\appx\data           ]
#  FMS Controls [EM=c:\appx\data        ]
#
#APPX_0SA_PATH=r:\appx\data

#=============================================================================
#  TECH SUPPORT DEBUGGING CONFIGURATION SECTION
#=============================================================================

#  APPX_UNIXIO_STATS and APPX_UNIXIO_PROCS work together to help 
#  debug file access and performance problems.  If you set APPX_UNIXIO_STATS
#  to a log file name, Appx will log all file i/o's performed.  The
#  format of the report is:
#    open_count read_count readnext_count start_count write_count rewrite_count filename
#  The statistics are written as each file is closed so if a file is closed and 
#  reopened, it will appear more than once in the log file.
#
#  Setting APPX_UNIXIO_PROCS will cause Appx to include the current process name
#  in the logfile.
#
#APPX_UNIXIO_STATS=/tmp/file_stats
#APPX_UNIXIO_PROCS=1
 
  • Place the following inside your appx.env file, which should be in %APPXPATH or C:\Appx\data\appx.env

Revision 32009-03-10 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Background Processing on a Windows Server

This document will APPX background processing when APPX is installed on a Windows server.
Line: 6 to 6
 

Overview

JOB is the only APPX process type you can make available for back ground processing. At the end of this document you will have made all the demo (DMO) JOB output reports candidates for background processing.

Required software components

Changed:
<
<

APPX Desktop Client Java Web Start Bundle

>
>

APPX Desktop Client

 
  • You can get the APPX Desktop Client from here.

APPX Server

  • You need a functioning APPX installation. Follow instructions in this document to install APPX on Windows if you don't already have APPX installed.

Revision 22009-03-10 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"
Added:
>
>

APPX Background Processing on a Windows Server

This document will APPX background processing when APPX is installed on a Windows server.

Overview

JOB is the only APPX process type you can make available for back ground processing. At the end of this document you will have made all the demo (DMO) JOB output reports candidates for background processing.

Required software components

APPX Desktop Client Java Web Start Bundle

  • You can get the APPX Desktop Client from here.

APPX Server

  • You need a functioning APPX installation. Follow instructions in this document to install APPX on Windows if you don't already have APPX installed.
  • You should also have the variable APPX_BG_SCRIPT=appx_submit.cmd. You can place this variable setting inside your appx.env file. The appx.env file should go into your %APPXPATH directory (C:\Appx\data\appx.env)

DMO Demo APPX Application

DMO is demonstration application that is included with APPX on default installations.

Quick steps

APPX Designer

  • Modify the JOB's OUTPUT process type to have Separate Task (Sep. Task) checked.

APPX Server

  • Place the following inside your appx.env file, which should be in %APPXPATH or C:\Appx\data\appx.env
 
Added:
>
>
APPX_BG_SCRIPT=appx_submit.cmd
  • The appx_submit.cmd command should contain
 
Added:
>
>
::APPX_SUBMIT.CMD
:: A Typical Argument list will be 8 Arguments passed from APPX
:: -image, -session, -mode, -notify, -date, -priority, -queue, and -user
:: Windows will break on the equals sign giving us 16 arguments in total
:: We will ignore all but the -image and -session pairs to submit
:: an APPX session with syntax that will be similar to
:: c:\APPX\Appx.exe -session=BY2Z7JDC

 
Added:
>
>
:: If you were to view each argument passed to APPX_SUBMIT.CMD with the :: following loop:
 
Deleted:
<
<
-- JoeOrtagus - 10 Mar 2009
 \ No newline at end of file
Added:
>
>
:: FOR %%A IN (%*) DO ( :: echo %%A >> c:\Appx\arglist.txt :: )

:: You would likekly see something like this in arglist.txt :: -image :: C:\Appx\Appx.exe :: -session :: BY2Z7JDC :: -mode :: SPOOL :: -notify :: Yes :: -date :: 2009031201020202 :: -priority :: 1 :: -queue :: A :: -user :: Administrator

:: The following command should execute APPX with the session data as :: an argument ::

%2 %3=%4

APPX Run Time

  • On the JOB's output disposition screen select SUBMIT to BG

Bugs:

  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.

Comments:

Read what other users have said about this page or add your own comments.
<--/commentPlugin-->
-- JoeOrtagus - 10 Mar 2009
 \ No newline at end of file

Revision 12009-03-10 - JoeOrtagus

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="APPXAdministrator"

-- JoeOrtagus - 10 Mar 2009

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback