Common configuration properties

Common configuration properties
The common configuration properties for IBM Connections are stored in the LotusConnections-config.xml file. The properties are represented as XML elements.
You can change the values of the properties in the following ways:

Use the updateConfig command from the wsadmin client. This is the preferred method for editing values of properties in the configuration file. When you use the wsadmin client to edit a property value, validation is performed on your change before the change is applied, which helps to prevent errors.
Note: Not all properties can be edited this way.

Edit the XML elements in the file directly using a text editor. This method is potentially more error prone. If you choose to edit the XML elements directly, you still must use the checkOutConfig wsadmin command to check out the configuration files and the checkInConfig wsadmin command to check the LotusConnections-config.xml file back in after you have made your updates. When you check the file in, validation runs on the edited file and you are informed if you introduced any errors. Fix any errors, save the file, and try to check it in again.

While it is better to use the updateConfig command from the wsadmin client to edit the properties in the configuration file, some of the properties cannot be edited this way. The values of those properties must be changed by editing the XML file directly.
How do you determine which properties you can edit using the wsadmin commands and which you cannot? You can use the showConfig wsadmin command. This command returns a listing of all the properties that can be edited using the wsadmin client.
This topic outlines those properties that you can edit using the updateConfig command from the wsadmin client and those that you cannot.

Properties that you can edit using the wsadmin client

The following list defines the configuration properties that can be edited using the updateConfig command from the wsadmin client.
activities.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

activities.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

activities.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

activities.enabled
Specifies whether the ability to access the Activities application over HTTP is enabled. The property accepts the following values: true or false.

activities.href
Web address from which to access the Activities application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

activities.href.prefix
Context root from which to access the application. For example: /activities.

activities.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

activities.pcs.name.js.eval
Defines the label of the link that you click to access the Activities application from the business card.

activities.pcs.url.pattern
Web pattern of the link to the Activities application from the business card.

activities.ssl.enabled
Specifies whether the ability to access the Activities application over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

activities.ssl.href
Web address from which to access the Activities application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

allowedContent.contentType.enabled
Specifies whether the active content filter removes flash animation files from entries in the Blogs and Wikis applications. Accepts the values: true or false. However, editing this value has no effect. See Configure the active content filter for Blogs and Wikis for information about how to prevent flash from being added to entries in those applications.

blogs.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

blogs.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

blogs.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

blogs.enabled
Specifies whether the ability to access the Blogs application over HTTP is enabled. The property accepts the following values: true or false.

blogs.href
Web address from which to access the Blogs application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

blogs.href.prefix
Context root from which to access the application. For example: /blogs.

blogs.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

blogs.pcs.name.js.eval
Defines the label of the link that you click to access the Blogs application from the business card.

blogs.pcs.url.pattern
Web pattern of the link to the Blogs application from the business card.

blogs.ssl.enabled
Specifies whether the ability to access the Blogs application over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

blogs.ssl.href
Web address from which to access the Blogs application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

communities.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

communities.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

communities.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

communities.enabled
Specifies whether the ability to access the Communities application over HTTP is enabled. The property accepts the following values: true or false.

communities.href
Web address from which to access the Communities application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

communities.href.prefix
Context root from which to access the application. For example: /communities.

communities.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

communities.pcs.name.js.eval
Defines the label of the link that you click to access the Communities application from the business card.

communities.pcs.url.pattern
Web pattern of the link to the Communities application from the business card.

communities.ssl.enabled
Specifies whether the ability to access the Communities application over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

communities.ssl.href
Web address from which to access the Communities application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

customAuthenticator.name
Specifies the short name for the code to use to secure server to server communication. The options are:

DefaultAuthenticator: Uses the IBM LTPA token to secure the connection. This option is the default option.
SiteMinderAuthenticator: Uses a SiteMinder token to secure the connection.
TAMAuthenticator: Uses a Tivoli Access Manager token to secure the connection.

Note: The customAuthenticator.ConnectionTimeout, customAuthenticator.CookieTimeout, customAuthenticator.DefaultMaxConnectionsPerHost, customAuthenticator.MaxTotalConnections, and customAuthenticator.SoTimeout properties were deprecated in version 3.

deployment.id
Unique identifier of the current deployment. This deployment ID is used by plug-ins and other API clients after the address of a deployment changes to determine whether the new address is the same deployment or not. The deployment ID is a unique value that is generated by the installer. Alternatively, you can assign an ID to a deployment. If you decide to assign the ID instead of using the ID generated by the installer, do the following things:

Use the naming convention: the reversed domain name of the IBM Connections installation. For example: com.example.social-intranet.
If the deployment moves from one installation or hostname to another, set the value of the new deployment ID to the same value as the original deployment.

The deployment.id value is exposed within the atom:id of the /serviceconfigs API feed available from all IBM Connections services.

dogear.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

dogear.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

dogear.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

dogear.enabled
Specifies whether the ability to access the Bookmarks application over HTTP is enabled. The property accepts the following values: true or false.

dogear.href
Web address from which to access the Bookmarks application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

dogear.href.prefix
Context root from which to access the application. For example: /dogear.

dogear.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

dogear.pcs.name.js.eval
Defines the label of the link that you click to access the Bookmarks application from the business card.

dogear.pcs.url.pattern
Web pattern of the link to the Bookmarks application from the business card.

dogear.ssl.href
Web address from which to access the Bookmarks application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

dogear.ssl.enabled
Specifies whether the ability to access the Bookmarks application over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

dynamicHosts.enabled
Specifies whether a reverse proxy is configured for IBM Connections. The property accepts the following values: true or false.

dynamicHosts.href
Web address from which to access IBM Connections through a reverse proxy over HTTP.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

dynamicHosts.ssl_href
Web address from which to access IBM Connections through a reverse proxy over secure HTTP (HTTPS).
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

email.expose.enabled
Specifies whether or not to display user email addresses in the product user interface, and product-generated notifications or URLs. The property accepts the following values: true or false.

files.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

files.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

files.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

files.enabled
Specifies whether the ability to access the Files application over HTTP is enabled. The property accepts the following values: true or false.

files.href
Web address from which to access the Files application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

files.href.prefix
Context root from which to access the application. For example: /files.

files.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

files.pcs.name.js.eval
Defines the label of the link that you click to access the Files application from the business card.

files.pcs.url.pattern
Web pattern of the link to the Files application from the business card.

files.ssl.enabled
Specifies whether the ability to access the Files application over secure HTTP is enabled.The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

files.ssl.href
Web address from which to access the Files application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

force.conf.comm.enabled
Specifies whether access to the IBM Connections applications can only be reached over a secure HTTP channel (HTTPS).The property accepts the following values: true or false. If you set the value of this property to true, the value of the profiles.directory.service.extension.href or communities.directory.service.extension.href properties, if Profiles or Communities directory service integration is enabled, must be specified as a secure HTTP (HTTPS) web address.

forums.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

forums.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

forums.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

forums.enabled
Specifies whether the ability to access the Forums application over HTTP is enabled. The property accepts the following values: true or false.

forums.href
Web address from which to access the Forums application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

forums.href.prefix
Context root from which to access the application. For example: /forums.

forums.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

forums.pcs.name.js.eval
Defines the label of the link that you click to access the Forums application from the business card.

forums.pcs.url.pattern
Web pattern of the link to the Forums application from the business card.

forums.ssl.enabled
Specifies whether the ability to access the Forums application over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

forums.ssl.href
Web address from which to access the Forums application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

help.enabled
Specifies whether the ability to access the help system over HTTP is enabled. The property accepts the following values: true or false.

help.href
Web address from which to access the help system over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

help.href.prefix
Context root from which to access the help system. For example: /activities.

help.interService.href
Web address from which other IBM Connections applications access the help system. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

help.ssl.enabled
Specifies whether the ability to access the help system over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

help.ssl.href
Web address from which to access the help system over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

homepage.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

homepage.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

homepage.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

homepage.enabled
Specifies whether the ability to access the Home page application over HTTP is enabled. The property accepts the following values: true or false.

homepage.href
Web address from which to access the Home page application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

homepage.href.prefix
Context root from which to access the application. For example: /homepage.

homepage.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

homepage.ssl.enabled
Specifies whether the ability to access the Home page application over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

homepage.ssl.href
Web address from which to access the Home page application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

mobile.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

mobile.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

mobile.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

mobile.enabled
Specifies whether the ability to access IBM Connections from a mobile device over HTTP is enabled. The property accepts the following values: true or false.

mobile.href
Web address from which to access IBM Connections from a mobile device over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

mobile.href.prefix
Context root from which to access IBM Connections from a mobile device. For example: /mobile.

mobile.interService.href
Web address from which IBM Connections applications access one another from a mobile device. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

mobile.ssl.enabled
Specifies whether the ability to access IBM Connections from a mobile device over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

mobile.ssl.href
Web address from which to access IBM Connections from a mobile device over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

news.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

news.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

news.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

news.enabled
Specifies whether the ability to access Home page Updates over HTTP is enabled. The property accepts the following values: true or false.

news.href
Web address from which to access Home page Updates over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

news.href.prefix
Context root from which to access the application. For example: /news.

news.interService.href
Web address from which other IBM Connections applications access Home page Updates. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

news.ssl.enabled
Specifies whether the ability to access Home page Updates over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

news.ssl.href
Web address from which to access Home page Updates over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

personTag.href
Web address from which to access the business card service over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

personTag.href.prefix
Context root from which to access the business card.

personTag.interService.href
Web address from which other IBM Connections applications access the business card. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

personTag.enabled
Specifies whether the ability to access the business card over HTTP is enabled. The property accepts the following values: true or false.

personTag.ssl.enabled
Specifies whether the ability to access the business card over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

personTag.ssl.href
Web address from which to access the business card service over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

profiles.directory.service.extension.enabled
Identifies whether Profiles directory service integration is enabled. When Profiles directory service integration is enabled, IBM Connections retrieves user information from the Profiles database instead of the LDAP server. The property accepts a value of true or false. It is set to false by default. If you install the Profiles application and specify that you want to use the Profiles database as the user directory during the installation, this value is automatically set to true.
Note: Group information can be retrieved from the LDAP directory only.
Note: The profiles.directory.service.extension.auth, profiles.directory.service.extension.auth.alias, communities.directory.service.extension.auth, communities.directory.service.extension.auth.alias, and communities.directory.service.extension.enabled properties can not be edited using wsadmin commands starting in version 3.

profiles.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

profiles.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

profiles.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

profiles.enabled
Specifies whether the ability to access the Profiles application over HTTP is enabled. The property accepts the following values: true or false.

profiles.href
Web address from which to access the Profiles application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

profiles.href.prefix
Context root from which to access the application. For example: /profiles.

profiles.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

profiles.pcs.name.js.eval
Defines the label of the link that you click to access the Profiles application from the business card.

profiles.pcs.url.pattern
Web pattern of the link to the Profiles application from the business card.

profiles.ssl.enabled
Specifies whether the ability to access the Profiles application over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

profiles.ssl.href
Web address from which to access the Profiles application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

quickr.enabled
Specifies whether the ability to access a link to a Lotus Quickr™ place from the business card over HTTP is enabled. The property accepts a Boolean value; the options are true and false. See Use business cards in the Administer Profiles section of the product documentation for more information about these Lotus Quickr properties.

quickr.href
Web address from which to access a Lotus Quickr place over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

quickr.href.prefix
Context root from which to access Sametime awareness services. For example: /quickr.

quickr.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

quickr.pcs.name.js.eval
Defines the label of the link that you click to access the Lotus Quickr place from the business card.

quickr.pcs.url.pattern
Web pattern of the link to the Lotus Quickr place from the business card.

quickr.ssl.enabled
Specifies whether the ability to access a link to a Lotus Quickr place from the business card over secure HTTP (HTTPS) is enabled. The property accepts the following values: true and false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

quickr.ssl.href
Web address from which to access a Lotus Quickr place over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

sametimeLinks.anonymousLogin.enabled
Boolean. Specifies whether the ability to access the Sametime Links resources anonymously is enabled. Options are true and false.
Note: Do not edit this value. For information about how to add Sametime awareness to IBM Connections, see Add Sametime awareness to IBM Connections.

sametimeLinks.enabled
Boolean. Specifies whether the ability to connect to the Sametime Links resources over HTTP is enabled. Options are true and false.
Note: Do not edit this value. For information about how to add Sametime awareness to IBM Connections, see Add Sametime awareness to IBM Connections.

sametimeLinks.href
Web address from which the Sametime Links resources, which support the display of presence awareness information in IBM Connections, can be accessed over the HTTP protocol. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Do not edit this value. For information about how to add Sametime awareness to IBM Connections, see Add Sametime awareness to IBM Connections.

sametimeLinks.href.prefix
Context root from which to access the application. For example: /sametime.

sametimeLinks.interService.href
Web address from which the Sametime Links resources, which support the display of presence awareness information in IBM Connections, can be accessed from other IBM Connections applications.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

sametimeLinks.ssl.enabled
Boolean. Specifies whether the ability to connect to the Sametime Links resources over HTTPS is enabled. The property accepts the following values: true or false.
Note: Do not edit this value. For information about how to add Sametime awareness to IBM Connections, see Add Sametime awareness to IBM Connections.

sametimeLinks.ssl.href
Web address from which the Sametime Links resources, which support the display of presence awareness information in IBM Connections, can be accessed over the HTTPS protocol. Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Do not edit this value. For information about how to add Sametime awareness to IBM Connections, see Add Sametime awareness to IBM Connections.

sametimeProxy.enabled
Boolean. Specifies whether the ability to connect to the Sametime proxy resources over HTTP is enabled. Options are true and false.

sametimeProxy.href
Web address from which the Sametime proxy resources, which support the display of presence awareness information in IBM Connections using the Sametime proxy, can be accessed over the HTTP protocol. Specify the protocol (HTTP), server name, and optionally the port number.

sametimeProxy.interService.href
Web address from which the Sametime proxy resources, which support the display of presence awareness information in IBM Connections using the Sametime proxy, can be accessed from other IBM Connections applications.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

sametimeProxy.ssl.enabled
Boolean. Specifies whether the ability to connect to the Sametime proxy resources over HTTPS is enabled. The property accepts the following values: true or false.It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

sametimeProxy.ssl.href
Web address from which the Sametime proxy resources, which support the display of presence awareness information in IBM Connections using the Sametime proxy, can be accessed over the HTTPS protocol. Specify the protocol (HTTPS), server name, and optionally the port number.

sand.enabled
Boolean. Specifies whether the ability to connect to the Social Networking and Discovery resources over HTTP is enabled. Options are true and false.

sand.href
Web address from which the Social Networking and Discovery resources can be accessed over the HTTP protocol. Specify the protocol (HTTP), server name, and optionally the port number.

sand.href.prefix
Context root from which to access the application. For example: /sand.

sand.ssl.enabled
Boolean. Specifies whether the ability to connect to the Social Networking and Discovery resources over HTTPS is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

sand.ssl.href
Web address from which the Social Networking and Discovery resources can be accessed over the HTTPS protocol. Specify the protocol (HTTPS), server name, and optionally the port number.

search.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.
Note: This property has no default value and typically should not be modified from installed defaults in a cluster configuration.

search.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This property has no default value.

search.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.
Note: This property has no default value.

search.enabled
Specifies whether the ability to access Advanced Search over HTTP is enabled. The property accepts the following values: true or false.

search.href
Web address from which to access Advanced Search over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

search.href.prefix
Context root from which to access the application. For example: /search.

search.ignore.punctuation.enabled
Specifies whether to ignore punctuation when performing a search. This property should always be set to false. Do not change its value.

search.interService.href
Web address from which other IBM Connections applications access Advanced Search. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

search.language.sensitivity.enabled
Specifies whether or not to turn on language sensitivity in search. The property accepts the following values: true or false. When set to true, the product supports accent insensitive searches, which means that for an occurrence of ált, the product stores ált and alt. This configuration results in a larger index. If you choose to change this option, complete the steps in the topic Delete the index.

search.Queue_Max
Number of connections refused before a subsequent transaction is allowed. This property is used only when Search is installed on a different server from the server hosting the application in which a search is being performed. If the Search server is not responding, a queue of requests is created. The length of the queue is defined by the value of this property. Only the last search request in the queue is sent to the Search server. When the search server starts responding, the queue is no longer used. The default value is 10.

search.ssl.enabled
Specifies whether the ability to access Advanced Search over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

search.ssl.href
Web address from which to access Advanced Search over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

search.Transaction_Max
Maximum number of transactions allowed. This property is used only when Search is installed on a different server from the server hosting the application in which a search is being performed. This setting prevents the server that is preforming the search from running out of memory due to the Search server not responding. The default value is 20.

use.richTextEditor.inBookmarklet.enabled
Specifies whether the description field on the Edit Bookmark form that is displayed when you create a bookmark using the Add Bookmark button is a rich text or plain text field. The form loads more quickly with a plain text description field. The field is plain text by default. The property accepts the following values: true or false.

versionStamp
Defines a version number that is stored as an internal URL reference for static content on the product's web pages. After customizing the product or installing an interim fix, the administrator increments the value of this property to prevent end users from having to clear their web browser cache to see the latest changes. When updating the value of this property, pass a null value to make the server assign a time stamp value to it. If you choose to specify your own time stamp, use the following syntax: yyyyMMdd.HHmmss For example: 20090720.034448.

wikis.ejb.cluster
Name of the cluster on which the application is running in a network deployment. This property is used for JNDI lookups in cluster environments to ensure failover and load balancing on lookups.

wikis.ejb.port
WAS port number of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups. This value is usually 2809, but may be different if port 2809 is already in use.

wikis.ejb.server
Fully qualified domain name of the application server instance running on the first node of the cluster that hosts this application. This information is used during JNDI lookups.

wikis.enabled
Specifies whether the ability to access the Wikis application over HTTP is enabled. The property accepts the following values: true or false.

wikis.href
Web address from which to access the Wikis application over HTTP. Specify the protocol (HTTP), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

wikis.href.prefix
Context root from which to access the application. For example: /wikis.

wikis.interService.href
Web address from which other IBM Connections applications access this application. Specify the protocol and server name.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

wikis.pcs.name.js.eval
Defines the label of the link that you click to access the Wikis application from the business card.

wikis.pcs.url.pattern
Web pattern of the link to the Wikis application from the business card.

wikis.ssl.href
Web address from which to access the Wikis application over secure HTTP (HTTPS). Specify the protocol (HTTPS), server name, and optionally the port number.
Note: Provide a fully-qualified domain name. This parameter is case-sensitive.

wikis.ssl.enabled
Specifies whether the ability to access the Wikis application over secure HTTP is enabled. The property accepts the following values: true or false. It is set to true by default, and should only be changed to false if you are disabling ssl in your environment. Disabling ssl is a complex, multi-step process that you should consult with IBM Support before attempting.

Properties that can only change by editing the XML file directly

The following properties are also stored in the LotusConnections-config.xml file, but cannot be edited using the updateConfig command from the wsadmin client. Instead, check out the configuration file using the wsadmin client LCConfigService.checkOutConfig command. Then, navigate to the temp directory and open the checked-out file, and then edit the property in a text editor. When you have finished editing the file, check in the updated file using the LCConfigService.checkInConfig command. Validation runs on the file. If an error is found, you are notified and can make any necessary changes, save the file, and try to check it in again.
Virus scanning properties:
 <avFilter> </avFilter> 
The XML elements and attributes function as follows:
av.chunk.size
Transfer rate. Specify an integer in bytes. This property is not displayed in the configuration file by default. If you want to specify a value for it, add it.

av.scanner.servers
Defines the virus scanning server to use to scan uploaded files for viruses. Replace my.virus.scanning.server.com with a list of one or more of the virus scanning servers used by your organization. Separated multiple servers with a comma. For example:
<property>av.scanner.servers=ssoc.acme.com</property> or <property>av.scanner.servers=ssoc1.acme.com,ssoc2.acme.com</property>

av.scanner.service
Defines the service name used by the anti virus scanner. Set this to AVSCAN for Symantec, and RESPMOD for McAfee.

exception.on.virus
Defines what to do when a virus is found. This property should always be set to yes.

first.read.timeout
Length of time for the timeout. Specify an integer in milliseconds. This property is not displayed in the configuration file by default. If you want to specify a value for it, add it.
Display language customization support:
<languageSelector 
enabled="true" defaultLanguage="" cookieName="conxnsCookie" cookieDomain=".acme.com" usePermanentCookie="true"> <language lang="en">English</language> <language lang="zh">\u4e2d\u6587\uff08\u7b80\u4f53\uff09</language> <language lang="zh_tw">\u4e2d\u6587 (\u7e41\u9ad4)</language> <language lang="ja">\u65e5\u672c\u8a9e</language> <language lang="ko">\ud55c\uad6d\uc5b4</language> <language lang="fr">Fran\u00e7ais</language> <language lang="de">Deutsch</language> <language lang="it">Italiano</language> <language lang="es">Espa\u00f1ol</language> <language lang="pt_br">Portugu\u00eas (Brasil)</language> <language lang="cs">\u010ce\u0161tina</language> <language lang="da">Dansk</language> <language lang="nl">Nederlands</language> <language lang="fi">suomi</language> <language lang="el">\u0395\u03bb\u03bb\u03b7\u03bd\u03b9\u03ba\u03ac</language> <language lang="hu">Magyar</language> <language lang="no">Norsk (Bokm\u00e5l)</language> <language lang="pl">polski</language> <language lang="pt">Portugu\u00eas (Portugal)</language> <language lang="ru">\u0420\u0443\u0441\u0441\u043a\u0438\u0439</language> <language lang="sl">slovenščina</language> <language lang="sv">Svenska</language> <language lang="tr">T\u00fcrk\u00e7e</language> <language lang="iw">\u05e2\u05d1\u05e8\u05d9\u05ea</language> <language lang="ar">\u200f\u0627\u0644\u0639\u0631\u0628\u064a\u0629\u200f</language> <language lang="ca">Catal\u00e0</language> <language lang="kk">\u049a\u0430\u0437\u0430\u049b\u0448\u0430</language> <language lang="th">\u0e44\u0e17\u0e22</language> </languageSelector>
The following table identifies the languages based on the lang property value:
Table 1. Language code values

Lang property value Language
ar Arabic
ca Catalan
cs Czech
da Danish
de German
en English
el Greek
es Spanish
fi Finnish
fr French
hu Hungarian
it Italian
iw Hebrew
ja Japanese
kk Kazakh
ko Korean
nl Dutch
no Norwegian
pl Polish
pt Portuguese
pt_br Brazilian Portuguese
ru Russian
sl Slovenian
sv Swedish
th Thai
tr Turkish
zh Simplified Chinese
zh_tw Traditional Chinese
The XML entries and attributes function as follows:
cookieDomain
Optional. Defines a cookie domain which enables the language setting to work across multiple servers. Specify a valid, fully qualified domain name of the server where the cookie resides. For example: .acme.com. Note that the domain name begins with a period (.). If you specify this cookie domain, the language setting would work for Profiles on profiles.acme.com and for Activities on activities.acme.com. By default, no cookie domain is used.

cookieName
Optional. The default cookie name is lcLang. If you want to use a different name for the cookie, specify a new name in this attribute.

defaultLanguage
By default, the product user interface is displayed in the language specified as the preferred language by the web browser. You can use the defaultLanguage attribute to define a fallback language in which to display the user interface if the preferred language specified by the browser is not included in the language elements list. It there are no language elements specified, the language specified in this attribute is the only language in which IBM Connections is displayed. Specify the language using the exact strings listed in the example above.

enabled
Specifies whether to allow users to change the display language of the product. This attribute accepts a Boolean value; the options are true and false.

language
Each <language> element represents a language that you want users to be able to select from the language selector drop-down list in the product navigation bar. Add and remove language elements to create a full list of the languages you want to make available. Include a lang attribute that specifies the ISO country code associated with the language. Provide the language name as it should be displayed in the list as the value of the language element. Specify non-Latin characters in Javascript-escaped unicode format. You can only specify languages that the product supports. For a list of languages, see Supported languages.
Also, remove any of the language elements that are included in the languageSelector element by default if you do not want them to be displayed from the drop-down list of language options in the product menu bar. They are English, French, Chinese, and Arabic.

usePermanentCookie
Optional. Specifies whether you want the cookie to persist for longer than the duration of the web browser session. This attribute accepts a Boolean value; the options are true and false. If you set the attribute to true, it creates a persistent cookie that has an expiry date of ten years from the date it was created.

Active content filter:
For some applications, you can customize the configuration file that is used by the active content filter. To do so, manually edit the acf_config_file attribute of the <sloc:serviceReference> element representing the application. See Configure the active content filter for Blogs and Wikis or Configure the active content filter for Activities, Communities, and Forums for more details.
Parent topic
Change common configuration property values
Related concepts
Use Profiles and Communities business cards
Supported languages

Related tasks

Add Sametime awareness though the Sametime client
Starting the wsadmin client
Apply common configuration property changes
IBM Connections configuration property values
Disable the social analytics service
Delete the index
Troubleshooting inter-server communication
Related reference
IBM Connections configuration error messages

+
Search Tips | Advanced Search

Lang property value	Language
ar	Arabic
ca	Catalan
cs	Czech
da	Danish
de	German
en	English
el	Greek
es	Spanish
fi	Finnish
fr	French
hu	Hungarian
it	Italian
iw	Hebrew
ja	Japanese
kk	Kazakh
ko	Korean
nl	Dutch
no	Norwegian
pl	Polish
pt	Portuguese
pt_br	Brazilian Portuguese
ru	Russian
sl	Slovenian
sv	Swedish
th	Thai
tr	Turkish
zh	Simplified Chinese
zh_tw	Traditional Chinese