You must edit each configuration XML file to provide the property values for your environment. You can use any text editor to open and edit the files.
Be sure that you have available the Installation and Upgrade Worksheet that was completed during your planning activities.
To edit values in the configuration XML files:
Do not edit the configureloginmodules.xml, configurejdbcos.xml, or deployapplication.xml files at this time.
configmgr_cl storepasswords [-task task_type | -taskfile task_file_name] -profile myprofile
where:
Task | Configuration file | Description |
---|---|---|
omitted | applicationserver.xml configurebootstrap.xml configurejdbc.xml configureldap.xml deployapplication.xml |
When you omit the -task task_type parameter, you are prompted to enter the passwords for each configuration XML file in the profile. Each password is encrypted before it is added to the XML file. |
configurebootstrap | configurebootstrap.xml | Encrypts the password for the BootstrapPassword property that is used to create the Global Configuration Data and to start Content Engine. |
configurejdbcgcd | configurejdbcgcd.xml |
Encrypts the password for the DatabasePassword property that Content Engine uses to access the GCD database. |
configurejdbcos | configurejdbcos.xml configurejdbcos.n.xml, where n is an integer starting with 2 |
Encrypts the password for the DatabasePassword property that Content Engine uses to access the object store database. If you have more than one configurejdbcos.n.xml file, run the command for each task file. |
configureldap | configureldap.xml configureldap.n.xml, where n is an integer starting with 2 |
Encrypts the password for the LDAPBindPassword property that Content Engine uses to connect to the directory server for authenticating Content Engine users. If you have more than one configureldap.n.xml file, run the command for each task file. |
If only one task file exists for the task_type, then the -taskfile task_file_name parameter is optional.
If more than one task file for the task_type exists, then you must include the -taskfile task_file_name parameter. You can omit the -task task_type parameter when you specify the -taskfile task_file_name parameter.