Editing configuration filesAdded by IBM | Edited by IBM on March 15, 2012 | Version 3 (Show original)
|You can edit configuration files in two ways: by editing configuration settings in the wsadmin client, or by editing the configuration XML files directly. In both cases, you must first check out the configuration files and later check them back in using the wsadmin client.
You can edit configuration files in two ways: by editing configuration settings in the wsadmin client, or by editing the configuration XML files directly. In both cases, you must first check out the configuration files and later check them back in using the wsadmin client.
- Start the wsadmin client by completing the following steps:
- Open a command prompt, and then change to the following directory of the system on which you installed the deployment manager:
is the WebSphere Application Server installation directory and <dm_profile_root>
is the Deployment Manager profile directory, typically dmgr01. For example, on Windows:
You must run the following command to start the wsadmin client from this specific directory because the Jython files for the product are stored here. 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.
- Enter the following command to start the wsadmin client:
- AIX or Linux:
./wsadmin.sh -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>
- Microsoft Windows:
wsadmin -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>
Use the following command to access the application configuration files:
- <admin_user_id> is the user name of a person in the Administrator role on the IBM WebSphere® Application Server.
- <admin_password> is the password of the WebSphere Application Server administrator.
- <SOAP_CONNECTOR_ADDRESS Port> is the SOAP port for the WebSphere Application Server. The default value of the SOAP port is 8879. If you are using the default port value, you do not need to specify this parameter. If you are not using the default and you do not know the port number, you can look up its value in the WebSphere Application Server Integrated Solution Console. To look up the SOAP port number, perform the following steps:
- Open the WebSphere Application Server Integrated Solution Console for the deployment manager, and then select System Administration -> Deployment Manager.
- In the Additional properties section expand Ports, and then look for the SOAP_CONNECTOR_ADDRESS port entry to find the port number.
- AIX or Linux:
./wsadmin.sh -lang jython -username primaryAdmin -password p@assword -port 8879
- Microsoft Windows:
wsadmin -lang jython -username primaryAdmin -password p@assword -port 8879
Check out the configuration file for the application using the following command:
is one of the following:
- IBM Connections-wide: connectionsConfig.py
- Activities: activitiesAdmin.py
- Blogs: blogsAdmin.py
- Bookmarks: dogearAdmin.py
- Communities: communitiesAdmin.py
- Files: filesAdmin.py
- Forums: forumsAdmin.py
- Home Page: homepageAdmin.py
- News: newsAdmin.py
- Profiles: profilesAdmin.py
- Search: searchAdmin.py
- Wikis: wikisAdmin.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, you must pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.
Optional: If you want to see what the current values of the configuration properties are, use the following command to retrieve a list of them:
- <service_name> is one of the following:
- IBM Connections-wide: LCConfigService
- Activities: ActivitiesConfigService
- Blogs: The configuration settings for the Blogs application are not made in a configuration file, so no files need to be checked out, updated, and checked back in for Blogs. Unlike the other applications, when you edit Blogs configuration properties, the changes are written directly to the Blogs database tables.
- Bookmarks: DogearCellConfig
- Communities: CommunitiesConfigService
- Files: FilesConfigService
- Forums: ForumsConfigService
- Home Page: HomepageCellConfig
- News: NewsCellConfig
- Profiles: ProfilesConfigService
- Search: SearchCellConfig
- Wikis: WikisConfigService
- <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied by the checkOutConfig command. The XML file contains the configuration settings and the corresponding XSD files is used to validate the XML file. The files are kept in this working directory while you make changes to them using the updateConfig command. When you run the checkInConfig command, the updated configuration file is copied from the temporary directory to where these files are located and overwrites the existing XML file. When you specify a path to the working directory on a system running Microsoft Windows, use a forward slash for the directory. For example: "C:/temp".
Note: AIX and Linux only: The directory must grant write permissions or the command will not run successfully.
- <cell_name> is the name of the WebSphere Application Server cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. If you do not know the cell name, type the following command while in the wsadmin command processor:
This input parameter is case-dependent.
- Common IBM Connections properties:
- Home Page:
- News repository:
Edit the values of the configuration properties that you want to change. Some properties must be edited using the wsadmin client; others can only be edited by editing the configuration XML file directly.
is one of the service names defined in step 4.
Update the value of the version stamp configuration property to force users' browsers to pick up this change. See Required post-customization step for more details.
After making edits, check the configuration files back in using the following command:
See the documentation for the individual application sections to see a list of the configuration properties you can edit for that application.
After making updates, type the following command to deploy the changes:
is one of the service names defined in step 4. You do not need to perform this step for the Blogs application.
You must run the checkin during the same wsadmin session in which you ran the checkout command.
To exit the wsadmin client, type exit at the prompt.
Stop and restart the servers hosting the edited IBM Connections applications.
Parent topic: Administering applications
Exporting LTPA keys
Importing LTPA keys
Starting the wsadmin client
Turning off active content filtering
Using the Profiles database as the user directory
Restrict forum topic editing to creators
Required post-customization step
If you changed any Blogs configuration settings, the changes were written directly into the Blogs database tables. Therefore, you do not need to stop and restart the server hosting the Blogs application for the changes to take effect.
IBM Connections configuration property values
Find out what configuration properties you can edit for each application.
IBM Connections configuration files
Configuration files are XML-formatted files that store configuration information for IBM