| ITS Manager |
| BizTalk Tips (Links) |
| 10.02.2010 11:01:05 | |
|
Biztalk Server tips http://msdn.microsoft.com/en-us/magazine/cc163423.aspx#S5 SCOM 2007 PACK 4 Biztalk Server Post Build Event in Visual Studio to GAC the assembly "$(DevEnvDir)..\..\SDK\v2.0\Bin\GacUtil.exe" /i "$(TargetPath)" /f Tags: soap | tips | monitoring | BizTalk Hits: 8378 | Lire la suite... |
| ITS Manager |
| Walk through : using Oracle Function to poll Oracle Advanced Queueing |
| 24.10.2009 07:27:00 | |
|
This article will come soon, with explanations from installing the adapter to calling a polling function all this, by using the Oracle Advanced Queueing Tags: Microsoft | Polling | function | Oracle | OracleESB | OracleDB | LOB | WCF | OAQ | BizTalk | Oracle Advanced Queuing Hits: 2452 | Lire la suite... |
| ITS Manager |
| SAP BizTalk Adapter |
| 01.11.2008 22:34:46 | |
|
I am trying to configure Microsoft SAP Adapter 2.0. I created send and receive ports as for documentation, RFC programs +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I have to generate Idoc XSD from SAP Adapter. The Microsoft SAP Adapter V2 works with the SAP .NET Connector V1.0.3. If you have V2 of the .NET Connector then you get the error you have seen. Try removing the V2 .NET connector and replacing with 1.0.3.The results you get seem to vary with the installations that have beeninstalled. Some folks report success with the .NET Connector V2 Tags: SAP | BizTalk | Adapter | Connection | IDoc | schema | Generation Hits: 7802 | Lire la suite... |
| ITS Manager |
| BizTalk SQL Server -> Login Failed user Null |
| 01.11.2008 22:27:32 | |
|
I already experienced several times the error : "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection" Could any one explain to me to what this is related? This time there was no impact, but it could have in the future? For information purposes only, we found what was going wrong. The BizTalk Server is not the same as the SQL Server A user belonging to the Active Directory was used by BizTalk Server to access SQL Server Tags: user null | Error | Connection | BizTalk | Active Directory | SQL Server Hits: 11951 | Lire la suite... |
| ITS Manager |
| Sharepoint BizTalk Minimum Rights |
| 01.11.2008 22:13:23 | |
|
We are trying to connect BizTalk 2006 R2 to Sharepoint 2007, What are the rights the BizTalk User should have (within Sharepoint) in order to retrieve and save documents to Sharepoint? I guess Site Owner is To Save: Contribution Rights Also the BizTalk user must be part of the SharePoint Enables Host group on the SharePoint Server. Tags: Sharepoint Enables Host | Contributor | Minimum | Rights | Sharepoint | BizTalk Hits: 12068 | Lire la suite... |
| ITS Manager |
| Routing Failed Messages |
| 01.11.2008 22:11:35 | |
|
I'm trying to use enable routing for failed messages, I specify my send port with a filter on the existence of a failure code (everything is ok till here, the failed messages are correctly routed) Then I add a filter on errors that come specifically from a receive port. And here nothing, the message is not routed and this acts as if no routing existed, when I see the context of the failed message the receive port is a promoted property ! If you look closely at your suspended Error Message (The non-resumable instance), you will see that the regular ReceivePortName (BTS.) is marked "Not Promoted", whereas the ErrorReport.ReceivePortName is. So you need to change your subscription to: Tags: Routing | failed messages | BizTalk | Receive | Port | Error | schema Hits: 11906 | Lire la suite... |
| ITS Manager |
| Validating FlatFile Schema (Positional) Date & space characters |
| 28.10.2008 15:13:18 | |
|
Some weeks ago I was faced with a problem, as entry, I had a flatfile schema with positional fields. Before processing this file I needed to validate that every field is ok. I had a problem with dates, since if I received let's say 10 space characters (representing and empty date) then the schema was not valid. So how the hell could we have resolved the problem? How could we say to BizTalk that for space characters on the Date it is ok, and it should go forward? Here we needed BizTalk Server to stop processing any wrong file, we did not want BizTalk to continue any further. Every solution must be on the schema, solutions in other parts of BizTalk (mapping, custom pipeline, orchestration, ...etc.) was not a state of the art solution. So What I did was simple :
These two actions were enough and solved my problem
Tags: schema | BizTalk | flatfile | mapping | orchestration | custom pipeline | dates | empty data | padding Hits: 13592 | Lire la suite... |
.png){kind=logo}
Tag: BizTalk