INTRODUCTION
Microsoft BizTalk Server 2004 Service Pack 1 supports the Chinese character encoding schema that uses GB18030 characters. This article describes how to set up BizTalk Server 2004 Service Pack 1 to use GB18030 characters.
For additional information about GB18030 characters, visit the following Microsoft Web site:
Because Microsoft SQL Server 2000 does not recognize GB18030 characters, you must configure a computer that is running SQL Server 2000 to use binary collation. When you do this, adjustments may be required to certain adapters. If you use Business Activity Services (BAS), this may affect how you install Microsoft Windows SharePoint Services.
back to the topMORE INFORMATION
Understand SQL Server set up
To use GB18030 characters, you must set the instance of SQL Server to binary collation. You only have to set the collation on the instance of SQL Server that is used by BizTalk Server.
When you set the collation to binary collation, this makes sure that all tables use binary collation. This includes internal tables that are created by BizTalk Server. You have to do this because BizTalk Server does not support mixing databases that use binary sort orders with databases that do not use binary sort orders.
Note When you configure BizTalk Server to use a binary collation in an instance of SQL Server, you cannot configure existing databases. Start with clean databases. Also, if you upgrade your version of BizTalk Server, you must also start with clean databases after you install Service Pack 1 and binary collation. An example of a version upgrade is from BizTalk Server Standard Edition to BizTalk Server Enterprise Edition.
back to the topInstall Windows SharePoint Services
If you use BAS, you must install Windows SharePoint Services (WSS). WSS does not configure correctly when you use binary collation in your SQL Server databases.
To work around this problem, install WSS by using the "server farm" option. Make sure that you specify the SQL Server database that is not using binary collation.
You can also configure WSS to use the Microsoft SQL Server 2000 Desktop Engine (MSDE). This is the default configuration. Make sure that you locate your BizTalk-related SQL Server installation on a different computer. MSDE and BizTalk require different shared memory settings.
back to the topInstall Service Pack 1 with binary collation
- If you have not already installed Windows SharePoint Services, do this now.
Note For additional information, visit the following Microsoft Web site to see the "Administrator's Guide for Windows SharePoint Services:" - Configure your computer that is running SQL Server to use binary collation.
Note For additional information about how to set up you computer that is running SQL Server, visit the following Microsoft Web site: - Run the Setup program for BizTalk Server 2004. Do not run the Configuration Wizard right now.
- On the final page of the Installation Wizard, click to clear the Start Configuration Wizard check box.
Note This prevents the Configuration Wizard from automatically starting. Do not run the Configuration Wizard until you install Service Pack 1. - Install BizTalk Server 2004 Service Pack 1.
- Run the BizTalk Server Configuration Wizard. To run the Configuration Wizard, follow these steps:
- Locate the BizTalk Server installation directory.
Note The default location for the installation directory follows:
%ProgramFiles%\Microsoft BizTalk Server - Double-click ConfigFramework.exe.
back to the topUninstall Service Pack 1 with binary collation
- To uninstall the BizTalk Server configuration, click Start, click Run, type "%ProgramFiles%\Microsoft BizTalk Server\configframework.exe /u", and then click OK.
- Uninstall Service Pack 1.
- Rebuild your instance on the computer that is running SQL Server to use standard collation.
- Rerun the BizTalk Server 2004 Configuration Wizard to use standard collation databases.
Note If you uninstall Service Pack 1 with binary collation, and then you reinstall it, you cannot use your old databases.
back to the topUnderstand known issues
The following are known issues in BizTalk Server Service Pack 1.
FTP Adapter
Because of the limitations of the FTP protocol, you cannot use GB18030 characters in user names, in passwords, or in file names that are used by the FTP adapter. However, these characters may appear in messages that are processed with the adapter.
SQL Adapter names and schemas
Sometimes you cannot use the following special characters in schema generation:
- space
- +
- :
- Unicode surrogate pairs
For additional information about valid characters, see "XMLConvert class" in the Microsoft .NET Framework Class Library Help files.
You can work around some of these problems by using an alias in the SQL statement. For example, an alias can be used to enable GB18030 characters in a table name by using the
SELECT statement in the following code example.
SELECT x FROM tableNameWithGB18030 aliasedTableNameWithoutGB18030
For additional information about creating schemas and about using schemas with the SQL adapter, see "Adding SQL Adapter Schemas to a BizTalk project" in the BizTalk Server 2004 Help files.
Working with Business Activity Monitoring
The Business Activity Monitoring (BAM) Excel worksheet does not work with GB18030 characters. You have to restrict BAM data items to Unicode 2.0 characters.
back to the top