Forum Replies Created
-
Posts
-
The Original Poster may need to restart the host instance to pick up the changes.
– the one called "weak architect"
Everything agents run every minutes without errors. Problem occur under relativly light load (I'm not in a stress-load mode).
Are all your SQL Agent jobs running without any errors?
Are you stressing the system or do you see this under light load?
I’m guessing @ is not a valid character for an XML node name. Not sure what you can do for this one. Could always do some type of find and replace inside the pipeline before / after you send it outside of BizTalk.
Version in BizTalk is very difficult. Basically, you need to treat the new version like a totally new schema – which it is. Side by side versioning is extremely hard.
You’ll need to make sure you change the versions on the maps, inside the Orchestrations (message variables and on the ports), and set your pipelines to use the correct schema version.
Inside BizTalk Admin, it might be sticky. If you have removed the older version and still see it. Not really sure there.
Best of luck.
I think it’s a namespace problem… Try to change both the schema you want to import as “Qualified”. It’s a property on the <schema> node I think. It will apply the namespace to all the nodes and not just the root node. I think then you import them, the all have a blank namespace and BizTalk doesn’t know what to do.
Just a guess though, could be way off here.
I’ve seen this before and it was an encoding problem. I don’t think they actually fixed it. Just did a work around.
In your case, assuming everything is correct with the file it should work. Did you try running the 2nd file first after restarting the host?
I’d strongly suggest unconfiguring BizTalk, removing the SQL Express (if desired), and configuring BizTalk fresh.
You probably can move the databases and updated BizTalk to work but it wouldn’t be worth the time / problems you will have.
Note that you’ll have to redeploy all your BizTalk code.
The special character restriction is an Xml restriction, not a Biztalk restriction and cannot be overridden.
Any chance of using aliases or stored procedures to hide the table name
If you'd like to use a web service to interact with BizTalk, it's best to generate one using the "Web Services Publishing Wizard" that gets installed inside Visual Studio. This builds a service for you based on BizTalk schemas or orchestrations, and contains the code necessary to publish a message into the BizTalk infrastructure. Once you have that service, you create a receive location that listens on that service location. When a mesage is posted to the service, it's grabbed by that port.
Emre,
I think you have the same problem we did; XMLs exported from a legacy system were missing the namespace so to BizTalk they were all the same. As we needed to process several XMLs at once, our solution was to split off the metadata from the XML so there were two inbound schemas. Works like a charm! The inbound schema with the metadata goes nowhere, the schema with the data gets processed.
I have some pics but this thing won't let me paste them. Let me figure this out and hopefully I can help you.
Have you seen this … http://www.microsoft.com/technet/prodtechnol/comm/2007/csbizintegrate.mspx ?
See here (http://www.microsoft.com/downloads/details.aspx?FamilyId=B273269C-97E0-411D-8849-5A8070698E4A&displaylang=en) for the install guides which call out the software prereqs you need.
Basically, you need Windows, SQL, .NET Framework, and optionally IIS and SharePoint. You do NOT want VS.NET on the QA server, as the BTS 2006 Admin Console has all the management capabilities that used to be in VS.NET. Most IT depts. don't like dev tools on the server, and now you don't need it.
You can choose to install only the components you want (e.g. no BAM, no BAS, no EDI, etc).
You'll probably have to look at scripting (WMI) the parties update if you want that done automatically.
BizTron,
here's my Sproc that's called by BizTalk:
set ANSI_NULLS ON
set QUOTED_IDENTIFIER ON
goALTER PROCEDURE [dbo].[TranslateLegacyProductNumber]
(
@LegacyProductNumber nvarchar(255)
)
AS
SELECT LegacyProductNumber,
SAPProductNumber,
ProductDescription
FROM ProductTranslation
WHERE LegacyProductNumber = @LegacyProductNumber
FOR XML AUTO
RETURNIf I add the error code variable after the @LegacyProductNumber nvarchar(255) line, my question still stands, how do I read the variable in BizTalk? Maybe I haven't had enough caffeine but I don't see it.
