Changes between Initial Version and Version 1 of ALL__appworx_config


Ignore:
Timestamp:
11/14/14 13:31:40 (10 years ago)
Author:
lttoth@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ALL__appworx_config

    v1 v1  
     1= !AppWorx Configuration in Support of LDAP/EDIR Related Jobs = 
     2 
     3We do not have !AppWorx clients on the "e" boxes where the Enterprise Directory and  
     4AUTHSERV/EDIR web interfaces are hosted or for that matter on summit which hosts the  
     5Oracle registry.  None the less, !AppWorx is used to schedule batch jobs on those boxes.   
     6This is accomplished via the Appworx client on toklat and UNIX accounts that ssh from  
     7toklat to the corresponding account on either summit or an "e" box. 
     8 
     9== !AppWorx Associations Between Server and EDIR Account == 
     10 
     11toklat -> "e" boxes 
     12=================== 
     13iplanet 
     14ldapgw 
     15 
     16toklat -> summit 
     17================ 
     18sxldap 
     19 
     20Jobs associated with maintenance of the AUTHSERV/EDIR web gateways are scheduled to run  
     21under the ldapgw account. 
     22 
     23Jobs associated with maintenance of the directory or the UPDATE web gateway are scheduled  
     24to run under the iplanet account. 
     25 
     26Jobs associated with the Oracle registry are scheduled to run under the sxldap account. 
     27 
     28Multiple generic wrapper scripts under the toklat ~ldapgw/appworx or ~|iplanet/appworx directories facilitate  
     29execution of a variety of scripts the "e" boxes".  There is one wrapper script for each  
     30"e" box in which the ssh statement is server specific. 
     31 
     32The toklat sxldap appworx directory has a comparable wrapper for summit.  However, due to  
     33the history of migrating old summit Appworx jobs to toklat when the summit Appworx agent was  
     34deleted (during !AppWorx upgrade), existing summit batch job scripts currently reside in the  
     35appworx_summit directory. 
     36 
     37To utilize a toklat wrapper to execute a specific script on an "e" box" or summit, create a  
     38link to the wrapper with the name of the script residing in the corresponding appworx directory  
     39on the remote host.  Create an !AppWorx module that executes the named script.  Appworx will  
     40pass runtime parameters to the toklat script in a manner that allows the wrapper to pass the  
     41same runtime arguments to the script on the remote machine.  Scripts on the remote machine  
     42should log status.  The wrapper scripts perform no logging unless a specific flag file is  
     43touched (see scripts). 
     44 
     45Note: Because the ldapgw and iplanet appworx directories support execution of scripts on  
     46multiple "e" boxes, prefix each link name (and script name on corresponding server) with the  
     47name of the server on which the script will execute. 
     48 
     49        edgar_appworx_wrapper.pl 
     50        edgar_static_list_maint.ksh -> edgar_appworx_wrapper.pl 
     51 
     52 
     53####################### 
     54DOCUMENT CHANGE HISTORY 
     55 
     5620081031 elm    corrected typos 
     57 
     58# eof