Article ID: 817923
Article Last Modified on 11/15/2007
APPLIES TO
- Microsoft BizTalk Accelerator for RosettaNet 2.0 Enterprise Edition
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
BizTalk Server Accelerator for RosettaNet uses XLANG schedules intensively to implement business-to-business processes. It uses only a single XLANG host (the default XLANG Scheduler) to host all schedules. This scenario limits the scalability of the application.
RESOLUTION
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name --------------------------------------------------------- 21-Apr-2003 23:18 3.0.0.551 381,029 Pipadaptersdk.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
How to Apply This Hotfix
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. Note This hotfix adds the capability for BizTalk Server Accelerator for RosettaNet to use multiple XLANG hosts. You can create any number of XLANG hosts for the Accelerator to use.
- Install BizTalk Server Accelerator for RosettaNet 2.0 Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
811186 INFO: BizTalk Accelerator for RosettaNet 2.0 QFE Rollup
- Create some empty COM+ applications such as RNApp1, RNApp2, and RNApp3.
- Add a dummy component to each COM+ application because COM+ requires at least one component in each application.
- For each of the COM+ applications that you created in step 2, open Properties. On the XLANG tab, click to select the check boxes for This application is a host for XLANG schedule instance and Use file DNS.
- Copy and rename the XLang Scheduler.dsn file for each of the XLANG host applications. XLANG host applications require that the DSN and the XLANG host application name be the same. The final file names are RNApp1.dsn, RNApp2.dsn, and RNApp3.dsn. The DSN files are located in the C:\Program Files\Common Files\ODBC\DataSources folder.
- Make the following changes in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server Accelerator for RosettaNet\1.0\Registration\QFES
Value Name: ComplusAppNames
Value Type: String
Value Data: RNApp1;RNApp2;RNApp3;XLANG Scheduler
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Keywords: kbhotfixserver kbqfe kbfix kbbug KB817923
