Forum Replies Created
-
Posts
-
Hello.
Side by side versioning with biztalk is doable but difficult.
In your case, I would look at using direct binding. If you need side by side versions of your schema you need to make sure you include the schema assembly version or another custom set property that can be used for your subscriptions inside the Orchestration.
You need to make sure if you version your schema you can not use the default Xml Disassembler or Assembler.
Basically, you need to think of side by side versioning as really a full, new solution you want to deploy.
Hope this helps.
Hello.
I have always done the promotion inside the Execute method like this:
IBaseMessageContext myContect = inmsg.Context;
myContect.Promote(this.ProElementName, this.ProNameSpace, this.ProValue);This will put the value into the context. You can need to get at the value inside the Orchestration like this:
yourMessage(PropertyName);
Also, make sure you have a Property Schema deployed with the correct namespace and element name.
I have a sample that shows this in a little more detail include with the Limit Running Orchestration sample: http://www.biztalkgurus.com/Samples/Limit-Running-Orchestration.html
Hope this helps.
I’ve gone throug the creation of correaltion again. No error messages or compilation failures. OrganizationNumber is of type xs:string and should not be problem.
I’m starting to think it’s the format of the schema that is autogenerated from the webservice that is the problem. You said something about the OrganizationNumber had to be unique in the schema. Well, the schema shows all the classes that are used throughout all the webservice-methods. I’m using only two of those web-methods. The class I’m using to correlate on, lets call it ClassA has an inherited ClassAExtended that of course also holds the OrganizationNumber. Could that be the problem ? In the Schema, it’s looks like this.
<Schema>
ClassSomething
…
ClassSomethingElse
…
ClassA
____<Equivalent>
______<ClassAExtended>
_______<Sequence> (This one is grey and contains all the info of ClassA)
_______<Sequence>
__________AdditionalAttribute1
__________AdditionalAttribute2
______<ClassA>
_________<Sequence>
____________Name
____________OrganizationNumber
____________AnotherAttribute1
____________AnotherAttribute2The XML look like this
…
<xs:complexType name=\”ClassA\”>
<xs:sequence>
<xs:element minOccurs=\”0\” maxOccurs=\”1\” name=\”Name\” type=\”xs:string\” />
<xs:element minOccurs=\”0\” maxOccurs=\”1\” name=\”OrganizationNumber\” type=\”xs:string\” />
…
</xs:sequence>
</xs:complexType>
…
– <xs:complexType name=\”ClassAExtended\”>
– <xs:complexContent mixed=\”false\”>
– <xs:extension base=\”tns:ClassA\”>
– <xs:sequence>
<xs:element minOccurs=\”0\” maxOccurs=\”1\” name=\”ExtraAttribute\” type=\”tns:ExtraType\” />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType><xs:complexType name=\”ExtraType\”>
<xs:sequence>
<xs:element minOccurs=\”0\” maxOccurs=\”1\” name=\”ExtraAttribute1\” type=\”xs:string\” />
<xs:element minOccurs=\”0\” maxOccurs=\”1\” name=\”ExtraAttribute2\” type=\”xs:string\” />
</xs:sequence>
</xs:complexType>…
There is automatically generated Request and Response Message Types for all the webmethods. I have used these Message Types to define all my messages.
The messages I defined are
1. AddReq
2. AddRes
3. UpdateReq
4. UpdateResAddReq is used in 1a) and 1b)
AddRes is used in 1c)
UpdateReq is used in 2a) and 2b)
UpdateRes is used in 2c)Another thought. Could there be a namespace problem ? The DatabaseWS has the namespace \”http://project.domain.com/portal/ws/\”. The BizTalkWS is deployed with the namespace \”http://project.domain.com/portal/biztalk/\”
I’m really lost here, can anyone verify if this orchestration should even work, or maybe how You would constructed an orchestration based on the same functionality.
Hello.
The code should be in the c:\\ConvoyDeepDive directory.
Let me know if you do not see it there.
1) Thanks for your reply. Process 2 updates the record with some info that is not provided during process 1, hence giving two states. State1 record created but infoA is not yet provided. State2: record is created and infoA is provided. To have the 2 processes being handled by the same orchestration process (I think it’s called a sequencial process or something simular) the second receive message needs to be correlated to the a send message of process 1.
2) I’ll try creating the correlation again posting back the results. FYI: The correlation property is associated to the OrganizationNumber AND Name from the referenced webservice-schema.
I’m still doing something wrong.
I created a distinguished field inside my Disassemble custom pipeline, within the Probe method.
[code:1:6dcccc6188]public bool Probe(pContext, pInMsg) {
…
pInMsg.Context.Write(\"CallChainID\", namespace, System.Guid.NewGuid());
…
}[/code:1:6dcccc6188]Then within my Orchestration I try to reference the distinguished variable
[code:1:6dcccc6188]msgTimeLoadXML.CallChainID[/code:1:6dcccc6188]But, it says that [quote:6dcccc6188]identifier \”CallChainID\” does not exist in \”msgTimeLoadXML\”; are you missing an assembly reference?[/quote:6dcccc6188]
What am I doing wrong?
Thanks
Scott
Hello.
I think you might want to look at using Orchestration exposed as Web Services. This way, you can get a synchronous response from your call.
Biztalk will generate a web service front end based on your Input and Return schema. It sounds like that would work better for you.
Using the file adapter, you would need some type of correction and that would get messy.
Hope this helps.
I should have said that once your guid is in the message context, you will access it by using msg(yourpropname) in an expression shape. You will need to create a property schema that defines your property.
Yes, you can simply write this guid to the message context using the Write method. If you need to route on it, you would ensure it is promoted.
Hi thanks for your reply. Yes, I’m sure it’s < > chars that are causing the issue. If I take them out or make sure they are equal in pairs then no problem, if unequal I get the following error when I try to test the Map:
\”Invoking component…
C:\\DOCUME~1\\aknott\\LOCALS~1\\Temp\\mapTLogDataToStorescanData_output.xml: error btm1048: Native serialization error: There is an unclosed literal string. Line 1, position 266.
E:\\Documents and Settings\\aknott\\My Documents\\Storescan\\Biztalk\\TLogData_To_Storescan\\TLogData_To_Storescan\\mapTLogDataToStorescanData.btm: error btm1054: Test Map failure for map file <file:///E:\\Documents and Settings\\aknott\\My Documents\\Storescan\\Biztalk\\TLogData_To_Storescan\\TLogData_To_Storescan\\mapTLogDataToStorescanData.btm>.
Component invocation succeeded. \”The problem is that my data will most certainly have unequal numbers of < > chars.
I have been trying to set the CDATA setting in the Map properties but this doesn’t seem to work either!!
Any ideas??Hmmm – I haven’t tried this, but I’d be extremely surprised if the flat file disassembler didn’t provide escaping of all xml characters it found in a flat file data stream. Are you sure the presence of < > is really the issue ? What is the error your are getting ?
A couple of thoughts –
1) Is correlation really necessary in this case? Is there state that needs to be preserved across the calls?
2) When you associated the correlation property with ‘com.domainname.project.portal.schemas.OrganizationNumber’ did everything seem to work? (Does this property occur just once in the schema? Is it of a datatype that biztalk is happy with? etc.)
You can use the \”Index\” functiod from the \”Advanced functiods\” to take the desired instance (In your case the index would be \”1\”) and map it.
Hello.
I have not worked with BAS at all but I think it is just a front end to Parties and Roles.
If so, the Names for the parties are not limited to the pre-defined list. You can just type in your own value.
Qualifiers. If you select a Name of the list, the Qualifier should be populated for you.
If you create a custom name, like Foo, you can get the qualifier to anything you like, Foo2In the past, we used qualifiers to route message inside the Orchestration to a Party.
Hope this helps.
