Understand the use of the portal property files

As i mentioned in the previous post Portal has concept of Configuration template files that defines set of properties that must be set for particular configuration task. In addition to that you might want to create set of configuration .properties file for your own environment. Ex. Instead of setting the user name and password wkplc.properties file you can set in your own .properties file and protect that file or you can create .properties file that has values specific to your environment.

Once you have your own .properties file you can ask ConfigEngine to use that .properties file using these two command line parameters

1. parentProperties: Value of this command line parameter should be a path to the .properties file that should be used as parent of wkplc.properties file. If same property is present in both parentProperties file and wkplc.properties then the value in parentProperties take precedence


2. SaveParentProperties: If you set SaveParentProperties to true then ConfigEngine will take the values from the parentProperties and set them in wkplc.properties file if the configuration task is completed successfully.

ConfigEngine.bat -DparentProperties=/helper_file_directory/helper.properties -DSaveParentProperties=true

Configuration Templates

The Configuration Task i.e. ConfigEngine.sh/.bat depends on different set of properties depending on the configuration task that your running as well as your configuration. Ex. The Database transfer task would depend on the database related properties such as DB User Name and password where as the Configuring LDAP would need host name of the LDAP server, user name and password.

The WPS server provides set of helper .properties files under wp_profile/ConfigEngine/config/helpers directory that you can use as template depending on the configuration task that your running. These are the configuration helper files that ship with WPS 6.1.0.1 version

cluster.properties
stepup.properties
virtual_portal.properties
wp_add_DB.properties
wp_add_federated_ad.properties
wp_add_federated_domino.properties
wp_add_federated_ids.properties
wp_add_federated_novell.properties
wp_add_federated_sunone.properties
wp_add_LA.properties
wp_security_ad.properties
wp_security_domino.properties
wp_security_federated.properties
wp_security_ids.properties
wp_security_novell.properties
wp_security_sunone.properties

If you open any of the configuration template file you will notice that it has similar structure. At the top of the file it will have some help information such as what is the helper file for what type of configuration tasks depend on this,..etc. Second part is that it defines set of properties and provides default values for some of the properties.

If you want to run particular configuration task check in the infocenter if it suggest particular helper file that you should use. If yes open that file check values for each of the properties if the property has default value you can make sure that value is correct in your environment if no set the value. Once your done changing the template file execute

./ConfigEngine.sh -DparentProperties=/helper_file_directory/helper.properties -DSaveParentProperties=true