Leverage the power of pdm_edit

Idea created by frank.earnhardt on Jun 22, 2015
    Not planned
    Score3
    • frank.earnhardt
    • J_W
    • GuanHua1378

    2015.12.03 10:29 Support Integration
    Created By: Frank Earnhardt   (12/03/2015 10:29:09.000)

    Let me elaborate:

    Before update was made to store pdm_startup configuration in database, pdm_edit was used to build configuration.
    This was 'VERY EASY' in comparison to verify as the entire configuration, as everything could be stored in single file as follows:

    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    VERSION::2
    DOMSRVR::DOMSRVR:USHOST81V.com:1::USHOST81V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST82V.com:1::USHOST82V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST83V.com:1::USHOST83V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST84V.com:1::USHOST84V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST85V.com:1::USHOST85V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST86V.com:1::USHOST86V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST87V.com:1::USHOST87V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST88V.com:1::USHOST88V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST89V.com:1::USHOST89V.com::none::.::
    DOMSRVR::DOMSRVR:USHOST90V.com:1::USHOST90V.com::none::.::
    DOMSRVR::DOMSRVR:primary:1::primary::none::.::
    WEBENGINE::WEB:USHOST81V.com:1::USHOST81V.com::domsrvr:11::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST82V.com:1::USHOST82V.com::domsrvr:21::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST83V.com:1::USHOST83V.com::domsrvr:31::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST84V.com:1::USHOST84V.com::domsrvr:41::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST85V.com:1::USHOST85V.com::domsrvr:51::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST86V.com:1::USHOST86V.com::domsrvr:61::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST87V.com:1::USHOST87V.com::domsrvr:71::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST88V.com:1::USHOST88V.com::domsrvr:81::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST89V.com:1::USHOST89V.com::domsrvr:91::::pdmweb::http:::8080
    WEBENGINE::WEB:USHOST90V.com:1::USHOST90V.com::domsrvr:101::::pdmweb::http:::8080
    WEBENGINE::WEB:primary:1::primary::domsrvr::::pdmweb::http:::
    REP_DAEMON::USHOST81V.com
    REP_DAEMON::primary
    BOPLGIN::primary
    KT::USHOST90V.com
    LDAP::primary
    DEFAULT_PROCSET::_REMOTE_PROCSET
    VIZTOM::USHOST81V.com
    VIZTOM::USHOST82V.com
    VIZTOM::USHOST83V.com
    VIZTOM::USHOST84V.com
    VIZTOM::USHOST85V.com
    VIZTOM::USHOST86V.com
    VIZTOM::USHOST87V.com
    VIZTOM::USHOST88V.com
    VIZTOM::USHOST89V.com
    VIZTOM::USHOST90V.com
    RESTTOM::USHOST81V.com
    RESTTOM::USHOST82V.com
    RESTTOM::USHOST83V.com
    RESTTOM::USHOST84V.com
    RESTTOM::USHOST85V.com
    RESTTOM::USHOST86V.com
    RESTTOM::USHOST87V.com
    RESTTOM::USHOST88V.com
    RESTTOM::USHOST89V.com
    RESTTOM::USHOST90V.com

    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

    As you can see, it would not take much effort to verify every server's configuration in detail from single point of view.

     

    **With new constructs, admins have to first add servers via one interface form, then add configuration in another form,
    then add objects in another form, and webengines in yet another form.
    I think you get the point 8pt; padding: 0px;"> 

    Please consider leveraging pdm_edit utility with above configuration file format to build all data required for database configuration.

     

    Regards