1.4 Publishing customizations with the wsadmin toolAdded by Amanda J Bauman on November 21, 2011 | Version 1 (Original)
Web pages in IBM Connections are usually cached by the browser to improve performance for users. After you make your customization, override the cache and force web browsers to download the new copies of the changed files. By your overriding the cache, others will see the customization changes you have made. Using the WebSphere Application Server wsadmin tool, update the version stamp on the appropriate configuration files. The wsadmin tool and the scripts that you need are included with IBM Connections.
Before you begin
Disable the customization debugging capability:
- Open the WebSphere Application Server Integrated Solutions Console.
- Click Environment>WebSphere variables and set the scope to the node where IBM Connections is installed.
- Set the variable CONNECTIONS_CUSTOMIZATION_DEBUG to false.
- Stop and restart all IBM Connections application servers.
- Open a command prompt and change to this directory on the system on which you installed the deployment manager: <WAS_home>\profiles\<profile_name>\bin
Start the wsadmin tool with the appropriate command:
- <WAS_home> is the WebSphere Application Server installation directory.
- <profile_name> is the Deployment Manager profile directory.
On Microsoft Windows, the full directory path is usually: C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\bin
To make the feature commands available to the wsadmin tool, enter the command that matches the application you are working with. For example, for common IBM Connections properties, use this command:
- On Microsoft Windows: wsadmin -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>
- On AIX or Linux:./wsadmin.sh -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>
- <admin_user_id> is the user name of and administrator on the IBM WebSphere Application Server
- <admin_password> is the password for that username
- <SOAP_CONNECTOR_ADDRESS Port> is the SOAP port for the WebSphere Application Server. If you have used the default port 8879, you do not need to specify this parameter. For example,
wsadmin -lang jython -user wsadmin -password wsadmin
Tip: If you are 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.
For more information about editing configuration files in other applications, see the IBM Connections documentation and search for Editing configuration files.
Check out the IBM Connections configuration files using the checkOutConfig command: For example, for common IBM Connections properties: LCConfigService.checkOutConfig("<working_directory>","<cell_name>")
Update the value of the versionStamp configuration property using this command: LCConfigService.updateConfig("versionStamp","<gmt_timestamp>") where <gmt_timestamp> is the GMT time. You can provide a value for the GMT time or leave it empty. It is best to provide an empty string and let the client format the time stamp. For example:
- <working_directory> is the directory that IBM Connections uses to store the temporary copies of the configuration files while they are checked out. On Microsoft Windows, use forward slashes to separate directories in the <working_directory>.
- <cell_name> is the case-sensitive name of the WebSphere Application Server cell hosting the IBM Connections application.
On Microsoft Windows:
or to populate the cell name, use AdminControl.getCell():
On AIX or Linux: The directory must grant write permissions or the command does not run successfully.
Attention: Do not exit the wsadmin tool before you check in your changes. You must check in the files during the same wsadmin session in which you checked them out for the changes to take effect.
Optional. To list the configuration settings and values before checking in the configuration files, use the showConfig command. For example,
Check in the configuration files using the checkinConfig command: For example, for common IBM Connections properties use this command:
Deploy the changes with this command:
To exit the wsadmin client, enter exit.
Stop and restart all IBM Connections application servers.
All IBM Connections users see the updated changes.
Parent topic: 1.0 Introduction to customizing IBM Connections