Configuring properties by using the Properties tool

Settings for system properties are stored in an encrypted properties file. The file is managed through the use of the Properties tool or the WebSphere® Application Server administrative console. When using the Properties tool, properties are displayed by folder, and most folders contain subsections that consist of groups of related properties.

About this task

During installation, a base properties file is installed and configured to reference the event runtime database and JMS provider. You can use the Properties tool to change property settings to accommodate your environment and preferences for system operation. There is no validation of the property that you have set. By default, a field holding a property values has a length of 64 characters. When you reach the limit, press ENTER and click to the end of the field to reset the focus. Properties then gives you up to five lines of 72 characters (by repeatedly pressing ENTER). Therefore, the maximum usable length is 360 characters.

Properties provides two entry modes:

Newly-configured property settings do not become operational until the next time you start the wberuntimeear application. You can make additional changes to property settings as required. Apply those changes by stopping this application and restarting it.

Procedure

  1. Start Properties by invoking the properties script (propertiesui.bat on Windows, propertiesui.sh on Linux and UNIX).

    The syntax is :

    propertiesui.bat/propertiesui.sh 
    
    [-conntype 
    SOAP [-host host_name] [-port port_number] |
    RMI [-host host_name] [-port port_number] |
    NONE]
    
    [-jndiName jndi_name]

    Where conntype specifies the type of connection to be used, the default value being "SOAP"

    A conntype of "NONE" means that no server connection is made and certain operations are performed in local mode

    host specifies the name of the host used for the SOAP or RMI connection, the default value being "localhost"

    port is the number of the port used for the SOAP or RMI connection

    jndiName is the JNDI name that is in the entry for event runtime properties, as shown under the Resource environment entries section of the WebSphere Application Server administrative console.

  2. Enter a user ID and password:
    • If security is enabled on WebSphere Application Server, you must enter a valid user ID and password.
    • If the user specified is not an Administrator, the user must have one of the following security roles:
      • adminsecuritymanager
      • deployer
      • configurator
    • If security is disabled on WebSphere Application Server, you can enter a user ID of your choice or leave the field blank. A password is not required.
  3. Modify the existing properties as required. For information about system properties, see Properties.
  4. To add a custom property:
    1. Select Full Configurator
    2. Click Edit > Add a Custom Property
    3. Click A new property and change it to the name of the custom property.
    4. Click value? and enter the value of the custom property.
    5. If you want to remove a custom property, right-click the property name and click Delete Custom Property. The property is deleted without confirmation.
  5. Click File > Save Properties to save your changes.
  6. Restart the event runtime to apply your changes.

Results

When the event runtime restarts, the changes you made to the properties are applied.