Change common configuration property values 


Overview

Use wsadmin connectionsConfig to interact with the IBM Connections configuration file: LotusConnections-config.xml.

Changes to common configuration settings require node synchronization and a restart of the all application servers.

Some properties in LotusConnections-config.xml cannot be edited using this procedure. They cannot be edited using updateConfig command nor displayed using the showConfig command. Instead, check out the configuration file using the checkOutConfig command, and then edit the property values by opening the checked out property file from the temporary directory using a text editor. After editing the property file, be sure to save the file, and then open it in a web browser to make sure you did not introduce any errors. XML files that are well formed display in a web browser; if there are errors, the web browser reports that an error was encountered. After fixing any errors, check the file back in using the checkInConfig command.

How do you determine which properties you can edit using the wsadmin commands and which you cannot? Use the showConfig command. This command returns a listing of all the properties that can be edited using the updateConfig command and their current values.


Change common configuration settings using wsadmin

  1. From the dmgr host, start the wsadmin client...

      cd $DMGR_PROFILE/bin
      ./wsadmin.sh|bat -lang jython -user lcadmin -password lcpassword -port soap_connector_address

    Run from this specific directory to access Jython files. If you try to start the client from a different directory, then the execfile() command that you subsequently call to initialize the administration environment for an IBM Connections component does not work correctly. Default SOAP port is 8879. To look up the SOAP port number, from the WAS console...

      System Administration | dmgr | Additional properties | Ports

  2. Use the wsadmin client to access and check out the IBM Connections configuration files:

    1. To access the IBM Connections configuration file:

        execfile("connectionsConfig.py")

      If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.

    2. Check out the IBM Connections configuration files:

        LCConfigService.checkOutConfig("<working_directory>","<cell_name>")

        where:

        • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.

            AIX and Linux only: The directory must grant write permissions or the command does not run successfully.

        • <cell_name> is the name of the WAS cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. To obtain the cell name:

            print AdminControl.getCell()

        For example:

        • AIX or Linux:LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
        • Microsoft Windows:LCConfigService.checkOutConfig("c:/temp","foo01Cell01")

  3. To find the current value of a property, list configuration settings and values using...

      LCConfigService.showConfig()

  4. Change a common configuration setting:

      LCConfigService.updateConfig("<property>","<value>")

    ...where <property> is one of the editable IBM Connections configuration properties and <value> is the new value with which you want to set that property. See Common configuration properties for a complete list of editable properties. For example:

      LCConfigService.updateConfig("versionStamp","")

  5. Optional: Repeat the previous step once for each property setting that you want to change.


What to do next

Check the configuration files back in during the same wsadmin session in which you checked them out. For more information, see the Apply common configuration property changes topic.


Parent topic

Administer applications


Related tasks


Post-migration tasks
Starting the wsadmin client
Apply common configuration property changes
Customize the navigation bar
Add styles to the IBM Connections stylesheet
Customize the footer
Add a section to the footer
Making extensive color and style changes
Exposing email addresses
Turning off active content filtering
Disable an application
Hiding email addresses
Enable virus scanning
Disable the social analytics service
Configure the 4-in-1 bookmark form

Related reference
IBM Connections configuration files