How to Switch TIBCO BusinessWorks Collaborator ICDBA Schema from ISO-8859 database to UTF-8 database. Deployment of BWC application over UTF-8 database.
Article ID: KB0088920
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessWorks Collaborator | - |
| Not Applicable | - |
Description
Description:
Configuration of TIBCO InConcert (IC) server when switching from ISO-8859 database to UTF-8 database. Required steps for configuration in TIBCO Administrator to deploy the TIBCO BusinessWorks Collaborator (BWC) application follows.
Configuration of TIBCO InConcert (IC) server when switching from ISO-8859 database to UTF-8 database. Required steps for configuration in TIBCO Administrator to deploy the TIBCO BusinessWorks Collaborator (BWC) application follows.
Issue/Introduction
How to Switch TIBCO BusinessWorks Collaborator ICDBA Schema from ISO-8859 database to UTF-8 database. Deployment of BWC application over UTF-8 database.
Resolution
The following are steps to configure TIBCO InConcert (IC) server when switching from an ISO-8859 database to a UTF-8 database. Additionally, configuration of TIBCO Administrator to deploy the BWC application.
1). For the IC server, the encoding could be switched if done correctly but first test to make sure the procedure is correct before changing in production. Creating a few objects and reading back attributes strings using the batch registry should be sufficient.
2). Copy the entire set of tables from the ISO-8859 database to the UTF-8 database.
3). Change the environmental variable 'NSL_LANG' in “env.sh” and “env.csh” (located at <IC_HOME>/config) to new character set. This is currently set to "AMERICAN_AMERICA.WE8ISO8859P1". You need to update the correct value for UTF. For that, coordinate with your DBA.
4). Change the '<OR_TWO_TASK>' in "icconfig.xml" to point to the new server.
5). Once done with the database migration, point the Workflow server with the new migrated database. Configuration information such as DB user, password, database name, etc. for the Workflow server will be stored in the "Icconfig.xml" file located under the <BWC_Home>\5.5\server\Server_Name\config directory.
6). Change the encoding setting in the "tibcoadmin_<domain-name>.tra" file ( locate in <admin-home>/domain/<domain-name>/bin). This file has two encoding settings with the following parameters which should be changed to UTF-8. By default they are set to the ISO character set.
repo.encoding=ISO8859-1 / change to UTF-8
tibcoadmin.client.encoding=ISO8859-1 / change to UTF-8
1). For the IC server, the encoding could be switched if done correctly but first test to make sure the procedure is correct before changing in production. Creating a few objects and reading back attributes strings using the batch registry should be sufficient.
2). Copy the entire set of tables from the ISO-8859 database to the UTF-8 database.
3). Change the environmental variable 'NSL_LANG' in “env.sh” and “env.csh” (located at <IC_HOME>/config) to new character set. This is currently set to "AMERICAN_AMERICA.WE8ISO8859P1". You need to update the correct value for UTF. For that, coordinate with your DBA.
4). Change the '<OR_TWO_TASK>' in "icconfig.xml" to point to the new server.
5). Once done with the database migration, point the Workflow server with the new migrated database. Configuration information such as DB user, password, database name, etc. for the Workflow server will be stored in the "Icconfig.xml" file located under the <BWC_Home>\5.5\server\Server_Name\config directory.
6). Change the encoding setting in the "tibcoadmin_<domain-name>.tra" file ( locate in <admin-home>/domain/<domain-name>/bin). This file has two encoding settings with the following parameters which should be changed to UTF-8. By default they are set to the ISO character set.
repo.encoding=ISO8859-1 / change to UTF-8
tibcoadmin.client.encoding=ISO8859-1 / change to UTF-8
7). Change the parameter "-character_encoding " to UTF-8 in "hawkagent.cfg" (locate in <tra-home>/domain/<domain-name>).
8). If the BWC application is already deployed then undeploy the application. Open the project in Designer and Save the project as UTF-8 and Create the shared archive.
9). Deploy the application in Administrator.
10). Verify encoding value for components pas, pps, workflow archive, process archive and the top most project level in the Advanced tab. If the encoding parameter exists for any component, then make sure the encoding value is UTF-8.
11). Stop the Services Administrator, Hawk and Tomcat.
Feedback
Yes
No
Powered by
