Forum Replies Created
-
Posts
-
i am correlating the send and receive using the field \”MQSeries.MQMD_CorrelId\”. This field is populated with a value inside the orchestration.
If i put the send shape outside the loop i wont be able to resend the request in case of a failure.
The objective of this loop is to resend the request.
i have an orchestration that sends a request and retrieves the response msg via MQ. i have initialized a correlation set in the send port. Whenever an invalid response is obtained i want to resend the request again thru the same send shape. But when i try to do so by putting necessary loop it gives me an error \”a correlation may be initialized only once\”.
Can anyone help me… any other method for solving this other than creating a separate orchestration for sending and receiving.
i am using Biztalk 2004.
Thanks in advance… 😀Sajas
Thank you for your answer.
I solved the problem by working on the Oracle side, I created (in my Oracle database) :
– a view based on my table,
– an INSTEAD OF INSERT trigger on the view. The trigger gets the next value of the sequence and inserts the data into my table.=> in the Biztalk orchestration, I insert into the view
(the value for the identity column is added by the trigger)To Insert Data to SQL-Server you should use the SQLAdapter. There are lots of examples how to use the sql-adapter.
Hi All,
we have fixed the problem by installing he biztalk service pack -1
this service pack renders to fixing the delay problem.
i thank all for atleast viewing the problem.Thanks a lot…… 😆
1. I set a rule that had an ‘OR’ then 2 ‘EQUAL’ predicates.
The second argument of each EQUAL is set by right clicking and selecting ‘BLANK STRING’ and ‘NULL’.2. I used a ‘Regular expression’ to exclude any values not in 0-9 or has to include A-Z !@#$^&*() etc To do this I used a ‘MATCH’ expression.
Hey it worked for me.
Cheers
JMan[quote:e6d318d632=\”Stephen W. Thomas\”]Not real sure on this one.
Did you make sure you have the pipeline components inside the correct folder? I think for an upgrade, the pipelines still reside inside the BizTalk Server 204 directory. Did you look in the BizTalk Installation – Update guide? Maybe that might have some hints.[/quote:e6d318d632]
I recompiled the pipeline components in VS 2005, and put them in the C:\\Program Files\\Microsoft BizTalk Server 2006\\Pipeline Components folder
Also, just for giggles, I put the newly compiled components in C:\\Program Files\\Microsoft BizTalk Server 2004\\Pipeline Components as well
I looked through the BizTalk Installation/Upgrade guides and the only reference to pipelines was that one must recompile them – which I did.
Does anybody know when this cast actually takes place? Is there a way to debug this?
I do not think you can do this from within the orchestration.
MY_SEQUENCE.NEXTVAL is a function that is evaluated by Oracle while processing the SQL.
You cannot put the text in the ID field as that is numeric.
One possibility would be an attribute on the field such as: <ID oracle:function=\”MY_SEQUENCE.NEXTVAL\”/> but the adapter would need to support this and I cannot see anywhere in the documentation where anything like this is supported.
You could use a stored procedure call.
Or adding the data to a temp table, with a trigger to populate the real table.Yes, this can be done using binding files
You need to export the bindings from a machine with the parties and role links defined.
You may need to export bindings not related to an assembly to get the parties.
You should end up with something like this:
[code:1:d5d1f6e7a4]<BindingInfo …>
<ModuleRefCollection>
<ModuleRef …>
<Services>
<Service Name=\"ServiceName\">
<Ports>
<Port …/>
</Ports>
<Roles>
<Role Name=\"Forward\" RoleLinkTypeName=\"Supplier.PurchaseOrder.PurchaseOrderType\" RoleType=\"Uses\">
<EnlistedParties>
<EnlistedParty Name=\"Joe Smith Corp\">
<Mappings>
<Mapping PortTypeName=\"Supplier.PurchaseOrder.SendPurchaseOrderType\" OperationName=\"Send\">
<SendPortRef Name=\"PurchaseOrder Via Hub\" />
</Mapping>
</Mappings>
</EnlistedParty>
</EnlistedParties>
</Role>
</Roles>
<Host Name=\"BizTalkServerApplication\" NTGroupName=\"BizTalk Application Users\" Type=\"1\" />
</Service>
</Services>
</ModuleRef>
</ModuleRefCollection>
<SendPortCollection>
<SendPort Name=\"PurchaseOrder Via Hub\" IsStatic=\"true\" IsTwoWay=\"false\">
</SendPort>
</SendPortCollection>
<DistributionListCollection />
<ReceivePortCollection/>
<PartyCollection>
<Party Name=\"Joe Smith Corp\">
<Aliases>
<PartyAlias Name=\"Organization\" Qualifier=\"OrganizationName\" Value=\"Joe Smith Corp\" IsAutoCreated=\"true\" />
<PartyAlias Name=\"Supplier Identifier\" Qualifier=\"PMSupplierId\" Value=\"368440\" IsAutoCreated=\"false\" />
</Aliases>
<SendPorts>
<SendPortRef Name=\"PurchaseOrder Via Hub\" />
</SendPorts>
<SignatureCert xsi:nil=\"true\" />
<CustomData xsi:nil=\"true\" />
</Party>
</PartyCollection>
</BindingInfo>[/code:1:d5d1f6e7a4]Did you change the Application Pool used by the web service? If you check inside the Virtual Directory, you should see and be able to change the Application Pool the WS is running under. Maybe that is still set to the default. Just a guess.
I recently inherited a Biztalk 2004 project, and I am also a complete novice to Biztalk. I upgraded the code successfully to Biztalk 2006, and deployed all of the necessary assemblies to start up Biztalk. Binding files imported succesfully, and I thought all was well, until I began to drop files into the system for Biztalk to process.
We use file adapter receive locations, that send the files through a custom pipeline component (in the decode stage), then the flat file disassembler (in the disassemble stage). One of our pipelines is named:
ClientName.Pipelines.ReceivePipeline_CONR_Dy
After dropping a file that should be picked up by this pipeline, the following error appeared in the event log.
[code:1:8010eec48e]
Unable to cast object of type ‘ClientName.Pipelines.ReceivePipeline_CONR_Dy’ to type ‘Microsoft.BizTalk.PipelineOM.Pipeline’.
[/code:1:8010eec48e]Can anybody suggest what the problem is, and possible solutions? I am under the assumption that this is due to the upgrade to 2006, as everything works fine under 2004.
Let me know if I should post any additional information.
Thanks!
