30 Jan, 2013

1 commit


21 Jan, 2013

1 commit


07 Jan, 2013

1 commit


19 Dec, 2012

1 commit


07 Nov, 2012

1 commit


26 Oct, 2012

1 commit

  • - Indicate that changing from one sample to the next constitutes a configuration change and link to the section on changing the config
     - Specify a minimum memory requirement for an evaluation installation
    
    OPENIDM-799 Suggestions on improvement of OpenIDM install guide
    
     - Provide more info on where to find curl if it's not provided with your OS
     - Show comparative commands on Windows where special characters in curl commands needs to be escaped.
    
    This commit also fixes some grammar/style/indentation issues.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@1355 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    Lana
     

10 Oct, 2012

1 commit


31 Aug, 2012

1 commit


14 Jun, 2012

1 commit


14 Mar, 2012

1 commit

  • The doc build plugin injects this content now.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@1026 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     

13 Mar, 2012

1 commit

  • The refactoring affects path names to HTML content. Examples:
    
    Before
    http://openam.forgerock.org/doc/admin-guide/OpenAM-Admin-Guide.html#configure-authn-chains
    http://opendj.forgerock.org/doc/admin-guide/OpenDJ-Admin-Guide.html#chap-account-lockout
    http://openidm.forgerock.org/doc/integrators-guide/OpenIDM-Integrators-Guide.html#security-bootstrap
    
    After
    http://openam.forgerock.org/doc/admin-guide/index.html#configure-authn-chains
    http://opendj.forgerock.org/doc/admin-guide/index.html#chap-account-lockout
    http://openidm.forgerock.org/doc/integrators-guide/index.html#security-bootstrap
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@1024 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     

20 Feb, 2012

1 commit


10 Feb, 2012

1 commit


09 Feb, 2012

2 commits


08 Feb, 2012

2 commits


06 Feb, 2012

1 commit


03 Feb, 2012

2 commits


02 Feb, 2012

4 commits


26 Jan, 2012

2 commits


19 Jan, 2012

1 commit


12 Jan, 2012

2 commits


11 Jan, 2012

1 commit


09 Jan, 2012

1 commit


06 Jan, 2012

1 commit


03 Jan, 2012

1 commit


02 Jan, 2012

4 commits


06 Dec, 2011

1 commit

  • I'd recommend <section> instead of <sect1> <sect2> <sect3> etc. as the stylesheets know how to handled nested <section> elements, and docs are easier to restructure when sections are not numbered.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@572 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     

29 Nov, 2011

1 commit

  • This works around http://code.google.com/p/docbkx-tools/issues/detail?id=36
    allowing links that work in the HTML, and look like this in the source:
    
    refer to the chapter on <link xlink:href="admin-guide#chap-troubleshooting"
    xlink:role="http://docbook.org/xlink/role/olink"><citetitle
    >Troubleshooting</citetitle></link> in the <citetitle>Administration
    Guide</citetitle>.
    
    As the olinkdb files are not currently built for other formats, the
    xlink:role="http://docbook.org/xlink/role/olink" links are
    ignored during output generation.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@542 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     

24 Jun, 2011

1 commit