AppWorx Configuration in Support of LDAP/EDIR Related Jobs
Original Author: Beth Mercer - 20081031
We run jobs for EDIR support on three platforms:
- RPTP Cluster as sxldap
- IDMP-3 Cluster as iplanet
- "E" boxes as ldapgw
We do not have AppWorx clients on the "e" boxes where the Enterprise Directory and AUTHSERV/EDIR web interfaces are hosted or for that matter on the IDMP-3 cluster that supports all LDAP registry operations. None the less, AppWorx is used to schedule batch jobs on those boxes. This is accomplished via the AppWorx client on RPTP (currently talkeetna) and UNIX accounts that ssh from RPTP to the corresponding account on either IDMP-3 or an "e" box.
AppWorx Associations Between Server and EDIR Account
RPTP Cluster to processes on "E" boxes
ldapgw: Jobs associated with maintenance of the AUTHSERV/EDIR web gateways are scheduled to run under the ldapgw account.
RPTP Cluster to processes on IDMP-3
iplanet: Jobs associated with maintenance of the LDAP directory or daily updates
RPTP Cluster to Local Oracle Processes
sxldap: Jobs associated with the Oracle registry are scheduled to run under the sxldap account.
Multiple 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 "E" box in which the ssh statement is server specific. The "E" box scripts are currently restricted to
- <"E"box instance>_static_list_maint.ksh
The RPTP ~sxldap/appworx directory has a comparable wrapper for IDMP-3. All scripts managing the LDAP repository are directed through IDMP-3.
To utilize an RPTP wrapper to execute a specific script on an "E" box" or IDMP-3, create a link to the wrapper with the name of the script residing in the corresponding appworx directory on the remote host. Create an AppWorx module that executes the named script. AppWorx will pass runtime parameters to the RPTP script in a manner that allows the wrapper to pass the same runtime arguments to the script on the remote machine. Scripts on the remote machine should log status. The wrapper scripts perform no logging unless a specific flag file is touched (see scripts).
Note: Because the ldapgw and iplanet appworx directories support execution of scripts on multiple "E" boxes, prefix each link name (and script name on corresponding server) with the name of the server on which the script will execute.
edgar_appworx_wrapper.pl edgar_static_list_maint.ksh -> edgar_appworx_wrapper.pl
########################################################
LEGACY CHANGE HISTORY - NOTE: All subsequent changes are recorded in TracWiki
########################################################
20081031 elm corrected typos
NOTE: To preserve the history of old summit Appworx jobs to toklat when the summit Appworx agent was deleted, historical summit batch job scripts currently reside in the ~sxldap/appworx_summit directory.
