Configure the vCard export application for ProfilesConfigure settings in the profiles-config.xml file to specify the character set encoding options used to export vCards. The table below lists the character set encoding options that work best.
Before you beginTo use administrative commands, use the IBM WAS wsadmin client. See Starting the wsadmin client for details.
About this taskProfiles users can export vCards from people's profiles and then import the profiles into their email client as contacts. You can configure the profiles-config.xml file to specify the encoding options that are available when exporting vCards from Profiles and determine which options are most appropriate for your users.
ProcedureTo configure the vCard export application...
- From the dmgr host:
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.
- Check out the Profiles configuration files:
- <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.
Note: AIX and Linux only: The directory must grant write permissions or the command does not complete successfully.
- <cell_name> is the name of the WAS cell hosting the Profiles application. This argument is required. It is also case-sensitive, so type it with care. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor: print AdminControl.getCell()
- AIX or Linux:ProfilesConfigService.checkOutConfig("/opt/prof/temp","foo01Cell01")
- Microsoft Windows:ProfilesConfigService.checkOutConfig("c:/prof/temp","foo01Cell01")
Open the Profiles configuration file, profiles-config.xml, using a text editor and locate the <vcardExport> section, which looks like the following:
<vcardExport> <charset name="UTF-8"> <label key="label.vcard.encoding.utf8"/> </charset> <charset name="ISO-8859-1"> <label key="label.vcard.encoding.iso88591"/> </charset> <charset name="Cp943c"> <label key="label.vcard.encoding.cp943c"/> </charset> </vcardExport>
To provide an export encoding that is specific to your language, include the following lines of code within the <vcardExport> tags:
<charset name="<character_encoding>"> <label key="<ui_label>"/> </charset>
- <character_encoding> is the name of the character encoding to export.
- <ui_label> is the label for the character encoding in the user interface.
For example, to add an export setting for Arabic, include the following element:
<vcardExport> ... <charset name="Windows-1256"> <label key="label.vcard.encoding.windows.arabic"/> </charset> </vcardExport>
The following character set encoding options work best:
Table 1. Export character set encodings
Character encoding Description Windows-1250 Central European languages that use Latin script (Polish, Czech, Slovak, Hungarian, Slovene, Serbian, Croatian, Romanian, and Albanian) Windows-1251 Cyrillic alphabets Windows-1252 Western languages Windows-1253 Greek Windows-1254 Turkish Windows-1255 Hebrew Windows-1256 Arabic Windows-1257 Baltic languages Windows-1258 Vietnamese
Complete this step for every language for which you require encoding support. There is no limit to the number of character set encodings that you can specify.
After making changes, check the configuration files back in, and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Apply property changes in Profiles for information about how to save and apply your changes.
Parent topicAdminister Profiles
Apply property changes in Profiles
Add custom strings for widgets and other specified scenarios