Overview of Add-on Services in Convergence

Skip to end of metadata
Go to start of metadata

Overview of Add-on Services in Convergence

Beginning with Convergence, you can use the add-on framework to add third-party services to the Convergence UI. These services include:

  • advertising
  • click-to-call service
  • multinetwork IM
  • SMS (both one-way and two-way)
  • social media applications (Facebook, Twitter, and Flickr)
  • video and voice calling capability

This information describes the add-on framework, the add-on configuration files, and instructions for adding or removing these third-party services in the Convergence UI.


About the Add-on Framework

The add-on framework provides access from Convergence to the third-party service through the use of an ID. The ID is provided by the service. The method of getting the ID differs from service to service. See the individual services sections for information on how to obtain the ID.

The add-ons are configured through Convergence configuration files. The available add-on services are listed in the Add-on Services table. The names of the add-on services, as used in the configuration files, are given in parentheses. For example, the properties file for configuring the multinetwork instant messaging add-on is imgateways.properties:

Add-on Service Description
Displays banner ads, text ads, and contextual ads in the Convergence UI.
For more information, see Configuring the Advertising Add-On Service in Convergence.
Allows for audio calling by clicking contact information in Instant Messaging or Address Book services in Convergence.
For more information, see Configuring Audio and Video Add-On Services in Convergence.
Video and audio calling
Provides video and audio calling through Convergence.
For more information, see Configuring Audio and Video Add-On Services in Convergence.
Multinetwork Instant Messaging
Provides access to all of a user's instant messaging accounts in a single place.
You can currently chat with Facebook buddies when you set up Facebook with the social add-on service.
Provides one- and two-way SMS through Convergence.
For more information, see Configuring One-Way SMS for Convergence and Configuring Two-Way SMS for Convergence.
Social Media
Provides access to social media, such as Facebook, Flickr, and Twitter, through a Social tab in the Convergence UI. Social media applications can only be added to the Social tab.
For more information, see Configuring Social Add-On Services in Convergence.

About the Add-On Configuration Files

The configuration files for supported add-ons are installed in the /var/opt/sun/comms/iwc/config/ directory. There are three types of configuration files:


The add-ons.properties file specifies the add-ons that are to be enabled. The following file lists the add-on services that are available in the add-ons.properties file that comes with the installation.

  1. Add on configuration.
  2. A sample entry will look like this :

Verify that the service you want to add to your Convergence deployment is in the add-ons.properties file before going onto configuring that service.


Each add-on has its own addon_name.json file, containing client configuration parameters for the add-on. You must enable the add-on service in addon_name.json in order for the service to be active in your Convergence deployment.

In the following sms.json file, the SMS service is enabled enabled: true. The comments describe each parameter:

To disable an add-on service, set enabled:false in the addon_name.json file.


The addon_name.properties file contains server access parameters for add-on services. At this time, only the social add-on service uses an addon_name.properties file: social.properties. The following example shows the authentication configuration for Twitter in the social.properties file:

s s Delete
-l -l Delete
administering administering Delete
convergence convergence Delete
addon addon Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.

The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.