Changes between Version 3 and Version 4 of ALL__appworx_config


Ignore:
Timestamp:
11/14/14 15:17:06 (10 years ago)
Author:
lttoth@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ALL__appworx_config

    v3 v4  
    22 
    33    Original Author: Beth Mercer - 20081031 
     4 
     5We run jobs for EDIR support on three platforms: 
     6* RPTP Cluster as sxldap 
     7* IDMP-3 Cluster as iplanet 
     8* "E" boxes as ldapgw 
    49 
    510We do not have !AppWorx clients on the "e" boxes where the Enterprise Directory and  
    … …  
    1015== !AppWorx Associations Between Server and EDIR Account == 
    1116 
    12 === RPTP Cluster to processes on "e" boxes === 
     17=== RPTP Cluster to processes on "E" boxes === 
    1318'''ldapgw:'''  Jobs associated with maintenance of the AUTHSERV/EDIR web gateways are scheduled to run  
    1419under the ldapgw account. 
    … …  
    2025'''sxldap:'''  Jobs associated with the Oracle registry are scheduled to run under the sxldap account. 
    2126 
    22  
    2327Multiple generic wrapper scripts under the toklat ~ldapgw/appworx or ~|iplanet/appworx directories facilitate  
    2428execution of a variety of scripts the "e" boxes".  There is one wrapper script for each  
    2529"e" box in which the ssh statement is server specific. 
    2630 
    27 The toklat sxldap appworx directory has a comparable wrapper for summit.  However, due to  
    28 the history of migrating old summit Appworx jobs to toklat when the summit Appworx agent was  
    29 deleted (during !AppWorx upgrade), existing summit batch job scripts currently reside in the  
    30 appworx_summit directory. 
     31The RPTP sxldap appworx directory has a comparable wrapper for IDMP-3.   
    3132 
    32 To utilize a toklat wrapper to execute a specific script on an "e" box" or summit, create a  
     33'''NOTE:'''  To preserve the history of old summit Appworx jobs to toklat when the summit Appworx agent was  
     34deleted, historical summit batch job scripts currently reside in the ~sxldap/appworx_summit directory. 
     35 
     36To utilize a RPTP wrapper to execute a specific script on an "E" box" or IDMP-3, create a  
    3337link to the wrapper with the name of the script residing in the corresponding appworx directory  
    34 on the remote host.  Create an !AppWorx module that executes the named script.  Appworx will  
    35 pass runtime parameters to the toklat script in a manner that allows the wrapper to pass the  
     38on the remote host.  Create an !AppWorx module that executes the named script.  !AppWorx will  
     39pass runtime parameters to the RPTP script in a manner that allows the wrapper to pass the  
    3640same runtime arguments to the script on the remote machine.  Scripts on the remote machine  
    3741should log status.  The wrapper scripts perform no logging unless a specific flag file is  
    3842touched (see scripts). 
    3943 
    40 Note: Because the ldapgw and iplanet appworx directories support execution of scripts on  
    41 multiple "e" boxes, prefix each link name (and script name on corresponding server) with the  
     44'''Note:''' Because the ldapgw and iplanet appworx directories support execution of scripts on  
     45multiple "E" boxes, prefix each link name (and script name on corresponding server) with the  
    4246name of the server on which the script will execute. 
    4347