Changes between Version 5 and Version 6 of ALL__appworx_config


Ignore:
Timestamp:
11/14/14 16:39:47 (10 years ago)
Author:
lttoth@…
Comment:

Updated format for TracWiki. With respect to content: removed references to summit, modified language to reflect IDMP-3 as being the sole Master for the LDAP directory while the "E" Boxes managed the web interface for EDIR self-service updates and AUTHSERV.

Legend:

Unmodified
Added
Removed
Modified
  • ALL__appworx_config

    v5 v6  
    2525'''sxldap:'''  Jobs associated with the Oracle registry are scheduled to run under the sxldap account. 
    2626 
    27 Multiple generic wrapper scripts under the toklat ~ldapgw/appworx or ~|iplanet/appworx directories facilitate  
    28 execution of a variety of scripts the "e" boxes".  There is one wrapper script for each  
    29 "e" box in which the ssh statement is server specific. 
     27Multiple generic wrapper scripts under the RPTP cluster ~ldapgw/appworx or ~iplanet/appworx directories facilitate execution of a variety of scripts the "E" boxes".  There is one wrapper script for each  
     28"E" box in which the ssh statement is server specific.  The "E" box scripts are currently restricted to 
    3029 
    31 The RPTP sxldap appworx directory has a comparable wrapper for IDMP-3.   
     30* <"E"box instance>_static_list_maint.ksh 
     31 
     32The RPTP ~sxldap/appworx directory has a comparable wrapper for IDMP-3.  All scripts managing the LDAP repository are directed through IDMP-3. 
    3233 
    3334'''NOTE:'''  To preserve the history of old summit Appworx jobs to toklat when the summit Appworx agent was  
    3435deleted, historical summit batch job scripts currently reside in the ~sxldap/appworx_summit directory. 
    3536 
    36 To utilize a RPTP wrapper to execute a specific script on an "E" box" or IDMP-3, create a  
     37To utilize an RPTP wrapper to execute a specific script on an "E" box" or IDMP-3, create a  
    3738link to the wrapper with the name of the script residing in the corresponding appworx directory  
    3839on the remote host.  Create an !AppWorx module that executes the named script.  !AppWorx will