CA-LDAP installation for multiple/redundant server instances
Article ID: 117166
Updated On:
Products
Top Secret
Top Secret - LDAP
Issue/Introduction
We are about to install the latest version of CA LDAP (15.1) at our site. (on our way to migrate to z/OS 2.3).
As we are running several LDAP-instances (server-stc's) spread on different systems within our sysplex, we'd like to ask, whether it is possible to install/deploy such instances, that they use the very same filesystem (shared in r/o mode within that sysplex). How could this be implemented (we do use MSM for software installation and maintenance but NOT for deploy)?
Or the question in other words: Is it absolutely necessary to have a z/FS filesystem for each CALDAP instance (server-stc)?
As we are running several LDAP-instances (server-stc's) spread on different systems within our sysplex, we'd like to ask, whether it is possible to install/deploy such instances, that they use the very same filesystem (shared in r/o mode within that sysplex). How could this be implemented (we do use MSM for software installation and maintenance but NOT for deploy)?
Or the question in other words: Is it absolutely necessary to have a z/FS filesystem for each CALDAP instance (server-stc)?
Environment
Release:
Component: TSSLDP
Component: TSSLDP
Resolution
You can tailor your LDAP STC procedure to target the same LDAP from the same shared ZFS filesystem.
But you must be sure that your stdout, stderr, ceedump files are located on R/W ZFS filesystem, accessible from each LPAR.
E.g:
//CALDAP PROC
//*
// SET VER='T9F1SP00'
// SET DEBUG='ANY'
// SET HOME='/cai/ldap'
// SET STDO='stdout.log'
// SET STDE='stderr.log'
// SET LPAR='xe52'
//*
//LDAP151 EXEC PGM=BPXBATA8,REGION=0M,TIME=NOLIMIT,
//*
// PARM='PGM slapd -d &DEBUG.
// -f &HOME./&VER./slapd151.conf'
//*
//STDOUT DD PATH='&HOME./&VER./&LPAR..&STDO',
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP),PATHDISP=(KEEP,KEEP)
//STDERR DD PATH='&HOME./&VER./&LPAR..&STDE',
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP),PATHDISP=(KEEP,KEEP)
//STDENV DD PATH='&HOME./&VER./slapd.env',
// PATHOPTS=(ORDONLY),
// PATHMODE=SIRWXU,PATHDISP=(KEEP,KEEP)
//CEEDUMP DD PATH='/cai/ldap/T9F1SP00' <=== to change for each lpar or to be parameterized...
*** End Of Data ***
Here you can define the same LDAP STC acid on any LPAR, the same STC procedure and parameterize each one according to the LPAR your ldap runs on.
Also We added a dynamic parm a while back, %zosnode% that can be used in the suffix into the slapd.conf file, so that :
suffix host=%zosnode%,o=ca,c=us and whatever for o= and c= which meet your requirement.
%zosnode% will be replaced by your system name.
But you must be sure that your stdout, stderr, ceedump files are located on R/W ZFS filesystem, accessible from each LPAR.
E.g:
//CALDAP PROC
//*
// SET VER='T9F1SP00'
// SET DEBUG='ANY'
// SET HOME='/cai/ldap'
// SET STDO='stdout.log'
// SET STDE='stderr.log'
// SET LPAR='xe52'
//*
//LDAP151 EXEC PGM=BPXBATA8,REGION=0M,TIME=NOLIMIT,
//*
// PARM='PGM slapd -d &DEBUG.
// -f &HOME./&VER./slapd151.conf'
//*
//STDOUT DD PATH='&HOME./&VER./&LPAR..&STDO',
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP),PATHDISP=(KEEP,KEEP)
//STDERR DD PATH='&HOME./&VER./&LPAR..&STDE',
// PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP),PATHDISP=(KEEP,KEEP)
//STDENV DD PATH='&HOME./&VER./slapd.env',
// PATHOPTS=(ORDONLY),
// PATHMODE=SIRWXU,PATHDISP=(KEEP,KEEP)
//CEEDUMP DD PATH='/cai/ldap/T9F1SP00' <=== to change for each lpar or to be parameterized...
*** End Of Data ***
Here you can define the same LDAP STC acid on any LPAR, the same STC procedure and parameterize each one according to the LPAR your ldap runs on.
Also We added a dynamic parm a while back, %zosnode% that can be used in the suffix into the slapd.conf file, so that :
suffix host=%zosnode%,o=ca,c=us and whatever for o= and c= which meet your requirement.
%zosnode% will be replaced by your system name.
Feedback
Yes
No
Powered by
