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