|
| 1 | +//// |
| 2 | + |
| 3 | + The contents of this file are subject to the terms of the Common Development and |
| 4 | + Distribution License (the License). You may not use this file except in compliance with the |
| 5 | + License. |
| 6 | + |
| 7 | + You can obtain a copy of the License at legal/CDDLv1.0.txt. See the License for the |
| 8 | + specific language governing permission and limitations under the License. |
| 9 | + |
| 10 | + When distributing Covered Software, include this CDDL Header Notice in each file and include |
| 11 | + the License file at legal/CDDLv1.0.txt. If applicable, add the following below the CDDL |
| 12 | + Header, with the fields enclosed by brackets [] replaced by your own identifying |
| 13 | + information: "Portions Copyright [year] [name of copyright owner]". |
| 14 | + |
| 15 | + Copyright 2015-2016 ForgeRock AS. |
| 16 | + Portions Copyright 2024 3A Systems LLC. |
| 17 | + |
| 18 | +//// |
| 19 | +
|
| 20 | +The `dsconfig` command provides many subcommands. |
| 21 | +
|
| 22 | +Subcommands let you create, list, and delete entire configuration components, and also let you get and set component properties. Subcommands therefore have names that reflect these five actions. |
| 23 | +
|
| 24 | +* create-__component__ |
| 25 | +
|
| 26 | +* list-__component__s |
| 27 | +
|
| 28 | +* delete-__component__ |
| 29 | +
|
| 30 | +* get-__component__-prop |
| 31 | +
|
| 32 | +* set-__component__-prop |
| 33 | +
|
| 34 | +Here, __component__ names are names of managed object types. Subcommand __component__ names are lower-case, hyphenated versions of the friendly names. When you act on an actual configuration component, you provide the name of the component as an option argument. |
| 35 | +For example, the Log Publisher component has these corresponding subcommands. |
| 36 | +
|
| 37 | +* `create-log-publisher` |
| 38 | +
|
| 39 | +* `list-log-publishers` |
| 40 | +
|
| 41 | +* `delete-log-publisher` |
| 42 | +
|
| 43 | +* `get-log-publisher-prop` |
| 44 | +
|
| 45 | +* `set-log-publisher-prop` |
| 46 | +
|
| 47 | +When you create or delete Log Publisher components and when you get and set their configuration properties, you provide the name of the actual log publisher, which you can find by using the `list-log-publishers` subcommand. |
| 48 | +
|
| 49 | +[source, console] |
| 50 | +---- |
| 51 | +$ dsconfig \ |
| 52 | + list-log-publishers \ |
| 53 | + --hostname opendj.example.com \ |
| 54 | + --port 4444 \ |
| 55 | + --bindDN "cn=Directory Manager" \ |
| 56 | + --bindPassword password \ |
| 57 | + --trustAll |
| 58 | +
|
| 59 | +Log Publisher : Type : enabled |
| 60 | +------------------------------:------------------------:-------- |
| 61 | +File-Based Access Logger : file-based-access : true |
| 62 | +File-Based Audit Logger : file-based-audit : false |
| 63 | +File-Based Debug Logger : file-based-debug : false |
| 64 | +File-Based Error Logger : file-based-error : true |
| 65 | +File-Based HTTP Access Logger : file-based-http-access : false |
| 66 | +Replication Repair Logger : file-based-error : true |
| 67 | +
|
| 68 | +$ dsconfig \ |
| 69 | + get-log-publisher-prop \ |
| 70 | + --publisher-name "File-Based Access Logger" \ |
| 71 | + --property rotation-policy \ |
| 72 | + --hostname opendj.example.com \ |
| 73 | + --port 4444 \ |
| 74 | + --bindDN "cn=Directory Manager" \ |
| 75 | + --bindPassword password \ |
| 76 | + --trustAll |
| 77 | +Property : Value(s) |
| 78 | +----------------:-------------------------------------------------------------- |
| 79 | +rotation-policy : 24 Hours Time Limit Rotation Policy, Size Limit Rotation |
| 80 | + : Policy |
| 81 | +---- |
| 82 | +Many subcommands let you set property values. Notice in the reference for the subcommands below that specific options are available for handling multi-valued properties. Whereas you can assign a single property value by using the `--set` option, you assign multiple values to a multi-valued property by using the `--add` option. You can reset the values of the multi-valued property by using the `--reset` option. |
| 83 | +Some property values take a time duration. Durations are expressed as numbers followed by units. For example `1 s` means one second, and `2 w` means two weeks. Some durations have minimum granularity or maximum units, so you cannot necessary specify every duration in milliseconds or weeks for example. Some durations allow you to use a special value to mean unlimited. Units are specified as follows. |
| 84 | +
|
| 85 | +* `ms`: milliseconds |
| 86 | +
|
| 87 | +* `s`: seconds |
| 88 | +
|
| 89 | +* `m`: minutes |
| 90 | +
|
| 91 | +* `h`: hours |
| 92 | +
|
| 93 | +* `d`: days |
| 94 | +
|
| 95 | +* `w`: weeks |
| 96 | +
|
| 97 | +Use the following options to view help for subcommands. |
| 98 | +-- |
| 99 | +
|
| 100 | +`dsconfig --help-all`:: |
| 101 | +Display all subcommands |
| 102 | +
|
| 103 | +`dsconfig --help-core-server`:: |
| 104 | +Display subcommands relating to core server |
| 105 | +
|
| 106 | +`dsconfig --help-database`:: |
| 107 | +Display subcommands relating to caching and back-ends |
| 108 | +
|
| 109 | +`dsconfig --help-logging`:: |
| 110 | +Display subcommands relating to logging |
| 111 | +
|
| 112 | +`dsconfig --help-replication`:: |
| 113 | +Display subcommands relating to replication |
| 114 | +
|
| 115 | +`dsconfig --help-security`:: |
| 116 | +Display subcommands relating to authentication and authorization |
| 117 | +
|
| 118 | +`dsconfig --help-user-management`:: |
| 119 | +Display subcommands relating to user management |
| 120 | +
|
| 121 | +-- |
| 122 | +For help with individual subcommands, either use `dsconfig subcommand --help`, or start `dsconfig` in interactive mode, without specifying a subcommand. |
| 123 | +
|
| 124 | +To view all component properties, use the `dsconfig list-properties` command. |
0 commit comments