Forum Replies Created
-
AuthorPosts
-
When you rebuild and deploy a Biztalk project you must restart the host instances that this application uses.
For in-process hosts instances (as in your case), use the Biztalk Admin Console, Biztalk Group,Platform Settings, Host Instances.The host instance is a running service that loads the BizTalk assemblies, if you redeploy an assembly the host instance will continue to use the original assembly until restarted.
When I try to match the filename (created using the default %MessageID% macro) of the message that was sent with the message(BTS.MessageID) they are not the same. Am I doing anything wrong?
Note: In my orchestration I create the message, send the message, and then I check Message(BTS.MessageID)
May 22, 2009 at 2:34 AM in reply to: BizTalk CRM 4.0 Adapter, error while invoking using send port 401:Unauthorized #22453Also checkout the CRM4 adapter installation guide
Steps to deploy CRM4 Adapter
—————————–STEPS 1 & 2 to be completed on BIZTALK Application SERVER
1. Install CRM3 Adapter
2. Download hot fix for CRM4 Adapter and install it (Can be installed only where CRM3 adapter is already installed).STEP 3 to be completed on CRM APPLICATION SERVER
3. Now to deploy CRM4 adapter do the following (VERY IMPORTANT FOLLOW THE STEPS ACCURATELY).
I. Create a folder called ‘xsd’ in the ‘SDK’ folder under ‘CRMWeb’ sub folder under CRM Server installation root directory i.e “Drive\Program files\Microsoft Dynamics CRM Server\CRMWeb\sdk”.
For Example “C:\Program files\Microsoft Dynamics CRM Server\CRMWeb\sdk”II. Copy “entity.aspx(3KB)” from the STEP 1 i.e “DRIVE\Program files\BizTalkAdapter\KB946649” to the above xsd (create in step 3 of I) folder
May 22, 2009 at 2:28 AM in reply to: BizTalk CRM 4.0 Adapter, error while invoking using send port 401:Unauthorized #22452Adapter is developed for CRM 3.0 but with minor tweaks can be used with CRM4 so, it doesnot support Organisation in the URL so u should use
http://<CRM server>/msCRMServices/2006/
in the CRM adapter URL
When you are specifying Distinguished Fields you are unable to modify the name.
You can use promoted properties instead.
1. Create a property schema and define a property called SourceID
2. In the schema promote the property and specify your property schema and link the <source-id> node to the SourceID property
3. Assign a value: QofDATFile(MyProperties.SourceID) == “ABC”Alternatively you can follow Guo Ming Li’s suggestion of using the xpath function
You could use the built-in xpath function to set the value of any element. You could find more information here: http://msdn2.microsoft.com/en-us/library/aa561906.aspx
May 21, 2009 at 7:54 PM in reply to: Call a custom .NET component to move large file from one file location to another #22449If your goal is only to move a file from one location to another, you can setup a FILE send port with filter to subscribe any message/file that’s coming from a specific send port, location that meets certain criterias.
Otherwise, you could write all your code in a helper .net class and call your function to write move the file to the new location. Hope this helps.
May 21, 2009 at 1:17 PM in reply to: CSV flat file in and a xml file out with a different schema must use mapping #22447Hello!
So if I just want to have a map to the output xml file I assume that I can chose
the receive port or the send port. It seems to me that it doesn’t matter.//Tony
May 21, 2009 at 12:34 PM in reply to: CSV flat file in and a xml file out with a different schema must use mapping #22446There are three standard ways you can use a map in Biztalk.
1. Use a transform shape in an orchestration.
2. Add the map to the Receive Port
3. Add the map to the Send portAn orchestration is probably not suitable for your messaging only solution.
You can use the Biztalk Admin Console to specify a map on the ReceivePortMay 21, 2009 at 12:28 PM in reply to: Move csv file from one folder to another when output should be xml file #22445This depends on how you define your flat file schema.
If your structure contains a root element with an unbounded record element the you will get one output file.
If your strusture on defines a single record element then the flat file diassembler will debatch the incoming flat file into multiple messages.May 21, 2009 at 2:57 AM in reply to: Move csv file from one folder to another when output should be xml file #22443Thanks very much very good explained!
I understand all of it but I just wonder if this will create one xml file with all the detail records from the csv flat file or
if it will create one single xml file for each detail record in the csv flat file.I want to have one xml file with all the detail record from the csv flat file within
//Tony
May 21, 2009 at 2:56 AM in reply to: Move csv file from one folder to another when output should be xml file #22442Thanks very much very good explained!
I understand all of it but I just wonder if this will create one xml file with all the detail records from the csv flat file or
if it will create one single xml file for each detail record in the csv flat file.I want to have one xml file with all the detail record from the csv flat file within
//Tony
May 21, 2009 at 2:36 AM in reply to: Move csv file from one folder to another when output should be xml file #22441You need to parse the flat file into an Xml message. This is done by the Flat File Disassembler (FFDASM), a standard pipeline component.
1. In your Biztalk project, add a receive pipeline.
2. From the tool box, drag the FFDASM into the Disassemble stage of your pipeline.
3. Select the FFDASM component in the pipeline, and in the properties window set the Document property to your flat file schema that your have created.
4. Build and deploy your assembly.
5. In your receive location, set the receive pipeline to the custom pipeline you have just created.
6. Restart the host instanceThe problem is not in your schemas, but in some odd behaviour in the XmlDisassembler. This could be worth a bug report.
When you promote the RegWaitID value as both a promoted property and distinguished field in a single message both are promoted into the message context.
However, if your message is part of a debatched interchange only the distinguished field is put in the message context.If you remove the distinguished field and only use the property promotion, then the property is promoted.
Error #1: use of unconstructed message
This indicates you are using a message that has not been constructed. This is usually cause by one of the followigs:
- message is not constructed before it’s used, i.e. not constructed inisde a “Construct Message” shape, or it’s not constructed inside a construct statement. You can use one of the methods described here: http://blogs.objectsharp.com/cs/blogs/matt/archive/2004/11/09/1009.aspx
- “an activatable receive must be the first executable statement in a service”: the first shape has to be a receive shape with “Activation” property equal to true if the orchestration is to be started by an arrival of a certain message
-
AuthorPosts